Finance & ERP · Integration
SAP Concur
Add SAP Concur to your product for your customers, and give your AI agents governed access to it.
SAP Concur covers travel and expense together, and the order of events is what an integration has to respect: a trip is often booked through a travel agency first, so an itinerary exists before any expense does, and the report that eventually goes to finance is built from entries matched against it. An embedded SAP Concur integration reads and writes expense reports, their entries and itemisations, the allocations that split an entry across cost objects, cash advances and travel requests. Authorisation is company level rather than per user, with a token issued per entity, and the pickers finance depends on come from Concur's own lists and connected lists, so cost centre and account values are read rather than invented. Audit rules mean a report can come back with exceptions attached. fastn holds the per-entity credentials and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Concur entity so expense reports created from your product arrive with the coding finance expects.
Create report entries with itemisations and allocations so a single expense can be split across the cost objects a company uses.
Read itineraries and receipt images so your product can match spend to the trip it belongs to rather than to a date.
Read Concur's own lists and connected lists so your pickers show that entity's real cost centres and accounts.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which expense reports are held up by an audit rule exception and what each exception says.
An agent allocates an entry across cost objects within governed permissions, with the write idempotent and logged.
An agent matches a receipt to the itinerary segment it belongs to and explains the match it made.
Example prompt
Which submitted Concur reports are stuck on an exception, and which cost centres would they hit once approved?
Set up SAP Concur in 4 steps
- 01Enable the SAP Concur connector in your fastn dashboard.
- 02Have each customer authorise their own Concur entity, since credentials are issued at company level rather than per user.
- 03Read that entity's lists and connected lists, then map the report, entry, itemisation and allocation fields your product uses.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the SAP Concur integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an SAP Concur integration without building it. Your customers connect their own SAP Concur account inside your product and work their invoices, payments and vendors there, with no per-customer code on your side.
- Handle the part that actually costs time: financial writes must be idempotent and reconcilable, because a duplicate is an accounting problem rather than a bug. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an SAP Concur update is not your on-call problem.
- One integration serves your product and your agents. The same governed SAP Concur connection powers in-product features and gives AI agents scoped, audited access, so you move financial records without hand-keying them between systems without wiring it twice.
Used by these teams
Compare with
Expensify
Rydoo
NavanOften used alongside
Tools the same teams tend to run next to SAP Concur, across other categories.
Shopify
Stripe
BigCommerce
AfterShipSAP Concur integration FAQ
How do I add an SAP Concur integration to my product?
Enable the SAP Concur connector in your fastn dashboard, then let each customer authenticate their own SAP Concur account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no SAP Concur client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own SAP Concur account?
Yes. Every connection is scoped to the individual customer, so each authorises their own SAP Concur account and only ever sees their own invoices, payments and vendors. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this SAP Concur integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which expense reports are held up by an audit rule exception and what each exception says.
Who maintains the SAP Concur integration?
fastn does. When SAP Concur changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the SAP Concur integration safe for financial writes?
Writes are idempotent, so a retry after a timeout does not post a document twice, and every call is logged per tenant so an entry can be traced back to the event that created it. That matters more in finance than anywhere else, because a duplicate is a number somebody has to explain.
Can it handle each customer's own chart of accounts?
Yes. ERP deployments are configured to the business, so account structures, required fields and fiscal calendars differ per customer. Those are mapped per tenant as configuration, not hard-coded.
What about SAP Concur rate limits during a first import?
Backfills are throttled deliberately. ERP limits are often account-wide rather than per-integration, so an unthrottled import can exhaust a customer's allowance and disrupt their other integrations.
What can I build with the SAP Concur integration?
A common starting point: let each customer connect their own Concur entity so expense reports created from your product arrive with the coding finance expects. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the SAP Concur integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding SAP Concur does not change your per-connector cost. You can start free with 3 connected accounts.
Add SAP Concur to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.