Finance & ERP · Integration
SAP
Add SAP to your product for your customers, and give your AI agents governed access to it.
An embedded SAP integration lets your product write into the system of record a large enterprise runs its business on, covering financial documents, purchase orders, cost centres, business partners and material master data. SAP resists standardisation more than anything else in this category, because no two landscapes match: a customer may sit on S/4HANA Cloud, S/4HANA on-premise or ECC, be reachable through OData services or older RFC and IDoc interfaces, sit behind a gateway, and carry company codes, chart of accounts variants and custom Z fields nobody else has. fastn absorbs that variation as per-tenant configuration and carries the credentials, retries and interface upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own SAP landscape so your product reads and writes financial documents without a bespoke middleware project.
Post costs against the correct company code and cost centre, using that customer's own account determination.
Read business partner and material master records so your product references what SAP already holds rather than a duplicated list.
Serve S/4HANA and ECC customers from one integration, with the deployment differences handled as configuration.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up a purchase order and its goods receipt status before it replies to a supplier query.
An agent posts a document within governed permissions, with the company code it used recorded on the call.
An agent reconciles what your product believes was billed against what SAP actually posted, reading one tenant's data.
Example prompt
Find purchase orders for this vendor with no goods receipt yet and tell me which are overdue.
Set up SAP in 4 steps
- 01Enable the SAP connector from your fastn dashboard.
- 02Have each customer authorise their own SAP account, so calls run under their credentials rather than a shared key.
- 03Decide which invoices, payments and vendors your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the SAP integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an SAP integration without building it. Your customers connect their own SAP 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 update is not your on-call problem.
- One integration serves your product and your agents. The same governed SAP 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
SAP Business One
Oracle ERP Cloud
NetSuiteOften used alongside
Tools the same teams tend to run next to SAP, across other categories.
Shopify
Stripe
BigCommerce
AfterShipSAP integration FAQ
How do I add an SAP integration to my product?
Enable the SAP connector in your fastn dashboard, then let each customer authenticate their own SAP account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no SAP 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 account?
Yes. Every connection is scoped to the individual customer, so each authorises their own SAP 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 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 looks up a purchase order and its goods receipt status before it replies to a supplier query.
Who maintains the SAP integration?
fastn does. When SAP 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 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 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 integration?
A common starting point: let a customer connect their own SAP landscape so your product reads and writes financial documents without a bespoke middleware project. 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 integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding SAP does not change your per-connector cost. You can start free with 3 connected accounts.
Add SAP to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.