PentaInvoiceConnector to SAP Concur - Customer Implementation Guide

 

 

Support

For issues related to this solution, please log a ticket via the Service Desk.

Timeline

Implementation, including installation of PentaConnect service and configuration of PentaInvoiceConnector and SAP Concur is estimated to take 1-2 hours, assuming all necessary information is supplied to Penta.

Requirements

  1. Signed PentaConnect contract (with PentaConnectAP and PentaInvoiceConnector)

  2. PENTA v24.1 or up

  3. SAP Concur

    1. Signed Letter of Authorization (LOA) - or eLOA via the Terms & Conditions when Connecting in the App Center - a required agreement by which a customer authorizes SAP Concur to securely share their data with App Center partners.

  4. Web server with PentaConnect v22.05 or up

  5. Concur Invoice workflow must include a “Send to Financial ERP System” step.

Customer to supply

Internal email addresses/mailbox for Customer-facing notifications from PentaInvoiceConnector.

  1. PENTA User ID and Password to be used for transactions from PentaConnect to PENTA.

  2. Company ID provided by Concur which uniquely identifies the organization

  3. Custom Field mapping in Concur at both the Invoice Master and Invoice Line Item levels. Penta must know which numbered custom field is mapped to which PentaInvoiceConnector custom value. Possible values include:

    OrganizationUnitId (Master)

    PaymentTermNumber (Master)

    DiscountAmount(Master)

    DiscountPercent(Master)

    DiscountDate(Master)

    RetentionAmount(Master)

    RetentionPercent(Master)

    HoldCode(Master)

    FreightAmount(Master) DebitOrganizationUnitId

    DebitAccountNumber

    FixedAssetId

    FixedAssetExpenseCategoryNumber

    JobId

    CostTypeCode

    Costcode

    SubcontractJobId

    SubcontractNumber

    SubcontractLineNumber

    WorkOrderId

    WorkOrderOrganizationUnitId

    WorkOrderCostTypeCode

  4. List of fields physically displayed on the Concur Payment Request Line Item Details and Payment Request Header entry forms.

  5. Frequency in which each entity will be synced between Concur and PENTA.

    1. Frequency CAN be as often as minutes, but will likely be limited to hours or days.

    2. This information must be synced in order to successfully integrate invoices.

    3. This includes required information:

      Invoices

      Vendors

    4. And at least one distribution type, depending on the nature of your invoices:

      Fixed Assets

      Jobs

      Ledger Accounts

      Purchase Orders

      Subcontracts

      Work Orders

    5. And there are other types of information that can be synced from Penta for use in Concur as well:

      Balance Sheet OUs

      Payment Terms