Acumatica and SAP Concur integration

What moves between them

The main flow runs from SAP Concur into Acumatica. ml-connector polls the Concur Financial Integration v4 endpoint for documents in READY state, then creates the matching AP bill or journal transaction in Acumatica, mapped to the right vendor, GL account, and cost center. After Acumatica accepts each record, ml-connector posts a posting confirmation back to Concur carrying the Acumatica reference number, which moves the Concur document to acknowledged so it is not pulled again. Vendor master data is aligned so Concur vendor codes match Acumatica VendorID values, and this reference data can be kept in step in both directions.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Concur side it exchanges the one-time App Center auth token for a refresh token at first connect, then rotates the one-hour access token on its own and always calls the geolocation base URL from the token response rather than a hardcoded datacenter. On the Acumatica side it accepts the full tenant URL and the endpoint version per customer, since Acumatica publishes no shared base URL and the version is locked to the ERP release, and it wraps every field value in the value object Acumatica requires. Because Acumatica cloud sync is most reliable as a pull, it polls Concur Financial Integration documents on your schedule and can also receive Concur Event Subscription Service notifications where they are enabled. Vendor codes and GL accounts are mapped first, so every posted invoice references a vendor and account that already exist in Acumatica. The Concur acknowledgement endpoint reports documents that were already acknowledged, and the connector checks Acumatica for an existing bill by VendorRef before creating, so a retry after a failure does not post a duplicate. Concur and Acumatica both return HTTP 429 under load, so ml-connector backs off and retries, and every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized professional services firm with about four hundred employees runs Acumatica for accounting and uses SAP Concur for employee expenses and supplier invoices. Before the integration, the AP team exported approved invoices and expense reports from Concur each week and keyed the totals into Acumatica by hand, then reconciled the two systems at month-end to find documents that were paid in Concur but never posted to the ledger. With Acumatica and SAP Concur connected, each approved document flows into Acumatica as an AP bill against the matching vendor and cost center, and a posting confirmation returns to Concur so its status reflects that the entry was recorded. The manual export and re-keying step is gone, and the two systems agree at close.

What you can do

• •Post approved SAP Concur invoices and expense reports into Acumatica as AP bills or journal transactions.
• •Send posting confirmations back to Concur with the Acumatica reference so each document is marked as recorded.
• •Keep Concur vendor codes aligned with Acumatica VendorID values so invoices land on valid vendors.
• •Bridge Concur company-level OAuth on the correct datacenter and Acumatica OAuth on the version-locked tenant URL.
• •Poll the Concur Financial Integration v4 service on your schedule, with retries and a full audit trail on every record.

Questions

Which direction does data move between Acumatica and SAP Concur?

The main flow is SAP Concur into Acumatica. Approved invoices and expense reports move from Concur into Acumatica as AP bills or journal entries, and a posting confirmation is sent back to Concur with the Acumatica reference number. Vendor master data is aligned in both directions so codes match on each side.

How does ml-connector handle Concur company-level auth and the geolocation requirement?

At first connect, ml-connector exchanges the one-time App Center auth token for a long-lived refresh token, since that token is only valid for a short window. It then rotates the one-hour access token automatically and always uses the geolocation base URL returned in the token response, so an EMEA or China company is never sent to the wrong datacenter.

What stops duplicate AP bills when a sync is retried?

Concur's Financial Integration acknowledgement step reports documents that were already acknowledged, so an already-processed invoice is not pulled again. On the Acumatica side, ml-connector checks for an existing bill by the vendor reference before creating one, and every record carries an audit trail so a failed post can be replayed safely rather than duplicated.