Integration Description
The Concur integration connects Zapro AI purchase orders, vendors and goods receipts to SAP Concur Invoice and Expense, so purchase orders raised in Zapro AI are available for purchase order matching on Concur payment requests.
What the SAP Concur integration does
- Invoices get something to match against
- One cost structure across travel and buying
- Receipts close the loop
How your records stay in sync
Skip the double entry. Zapro AI keeps these records matched with SAP Concur, so no duplicates are created and your data stays centralized.
How the connection is set up
- Register the application with SAP Concur
- Obtain a company level token
- Map cost objects and expense types
- Publish purchase orders for one business unit
- Turn on the inbound reads
- Reconcile a closed period
How teams use it
- StartupPurchasing is run in Zapro AI from day one while travel stays in Concur, with one cost structure across both.
- SMBApproved purchase orders and receipts are published to Concur Invoice, so matching happens in the tool instead of the inbox.
- EnterpriseZapro AI holds the category tree, publishes it to Concur allocations, and reports all three spend types together with a traceable approval history.
Automate SAP Concur with Zapro AI
Procurement
Runs the purchase request, approval workflow and purchase order that Concur matches payment requests against.
AP Automation
Handles capture, two and three way matching, exceptions and disputes for invoices that do not go through Concur.
Spend Analytics
Reports expense, travel and purchase order spend by vendor, category, entity and location in one place.
Contract Management
Holds the supplier contract, its versions and renewal dates behind the purchase orders raised against it.
Implementing Zapro improved our vendor coordination significantly, leading to a substantial reduction in costs and faster vendor onboarding.
Questions teams ask
Does Concur integrate with procurement software?
Yes. SAP Concur connects to Zapro AI through the Concur REST APIs with a company level OAuth 2.0 token from a registered application. Zapro AI publishes purchase orders, receipts and vendors into Concur Invoice for matching, and reads payment requests and expense reports back.
Do we still need Concur Requisition?
No, if purchasing runs in Zapro AI. Requests, approval chains, RFQs and purchase orders are raised in Zapro AI and the purchase order is published to Concur Invoice for matching. Teams that already own Concur Request usually keep it for travel only.
How is access to Concur data controlled?
The company level token is held server side and scoped to the endpoints agreed at application registration. Inside Zapro AI, Concur data follows role based permissions, so an expense entry is visible to the employee, their approver and finance, and every sync is recorded in the audit trail.
What breaks most often during setup?
Allocation field mapping. Concur exposes cost center and project as numbered custom fields that differ per tenant, so a map copied from another implementation puts the right value in the wrong field. Confirm them in your own configuration first.
Can purchase orders flow the other way?
In this setup they do not. Zapro AI is the system of record for purchase orders and publishes them to Concur. Running purchase order creation in both systems produces two numbering schemes and a match that fails for reasons nobody can trace.

