Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
Procurement networks · Supply chain
Connect Microsoft Business Central + SAP Ariba
Automate purchase order, order confirmation, ship notice, invoice, catalogue / price file between Microsoft Business Central and SAP Ariba — with monitoring and managed support from APIWORX.
APIWORX connects the systems your business already uses and takes responsibility for the agreed integration workflows after go-live. The exact objects, direction and cadence are fixed in writing during scoping.
ERP + eCommerce Specialists
Managed & Monitored Integrations
Expert Integration Team
APIWORX Provides the Service
Yes. APIWORX connects Microsoft Business Central and SAP Ariba.
But connecting the applications is only the beginning. The work that costs you time sits in the process running between them.
APIWORX automates that process end to end — the objects moving between Microsoft Business Central and SAP Ariba, the ownership rules that decide which system wins, the exceptions when a record will not post, and the monitoring that tells someone before your team finds out from a customer.
How it works
From requirements to a managed integration
We Design the Integration
APIWORX recommends the integration architecture, mappings and implementation approach.
We Build, Monitor & Support It
APIWORX implements the integration and provides ongoing monitoring and support as applicable.
Who this is for
This page is for supply-chain and finance teams supplying Ariba-enabled buyers while Dynamics 365 Business Central runs orders and invoicing.
What needs to be in place
- An active Ariba supplier account with buyer relationships established.
- Business Central (cloud, or on-premises with a supported connection path agreed in scoping) and a service account permitted to create sales documents.
- Customer, item and pricing mappings per buyer.
- A warehouse or 3PL able to act on released orders and return shipment detail.
When you may not need this
If one buyer sends a few orders a month, the portal is enough. Integration earns its place when duplicate entry across Ariba and Business Central has become someone's recurring job.
What is out of scope
- Scope here is supplier-side: receiving buyer transactions and returning your documents. Buyer-side Ariba procurement configuration is out of scope.
- The transaction path — cXML, EDI or another supported route — is confirmed per buyer in scoping; Ariba buyers differ.
- PunchOut catalogue hosting is not claimed on this page. If a buyer requires it, it is assessed separately before any commitment.
- Ariba Network account fees, supplier programme tiers and buyer terms remain between you and the buyer.
What actually moves, and who owns it
A representative supplier-side scope, confirmed per buyer before build.
Microsoft Business CentralAPIWORX (mapping, retries, exception queue)SAP Ariba
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Purchase order | SAP Ariba | Business Central sales order | Buyer | PO issued | Held in exception queue with the validation error | APIWORX |
| Order confirmation | Business Central | SAP Ariba | Business Central | Order confirmed or amended | Retried, then queued for review | APIWORX |
| Ship notice | Business Central / warehouse | SAP Ariba | Warehouse | Shipment posted | Held with missing detail flagged | APIWORX with your warehouse |
| Invoice | Business Central | SAP Ariba | Business Central | Posted sales invoice | Queued; buyer rejections reported back with reason | APIWORX |
| Catalogue / price file | Your source file | SAP Ariba | Your commercial team | Agreed update cadence | Previous file retained; failure raised | APIWORX |
Three decisions that make or break this integration
A purchase order arrives for a buyer-specific item number
Buyer item numbers are translated to your Business Central items before the order is created, so nobody has to interpret a buyer catalogue by hand.
- Unmapped items held with the line identified.
- Mappings maintained by APIWORX as part of the engagement.
- Original transaction reprocessed once mapped.
The buyer requires a confirmation before you ship
Confirmations are sent from the state of the Business Central order, including amended dates or quantities, so what the buyer sees matches what you plan to ship.
- Confirmation content derived from the Business Central document.
- Amendments resent when the order changes.
- Failures retried, then queued with the reason.
Invoices carry the references matching needs
Invoices are generated from posted Business Central sales invoices with purchase-order and shipment references attached, which is what buyer three-way matching checks.
- References carried through end to end.
- Rejections returned with reason codes.
- Repeat causes escalated as process changes.
Reliability and ownership
The operating rules that apply to this workflow after go-live.
- Every transaction is logged with its reference and the trading partner it belongs to, so a document can be traced end to end.
- Failed transactions are retried on a defined schedule; anything still failing is held in an exception queue rather than partially processed.
- Duplicate prevention keys on the partner's own purchase order or document identifier.
- Exceptions are worked by the APIWORX team and escalated to your named contacts when a business decision is needed.
- New buyers, new transaction types and changed requirements are handled as mapping work inside the ongoing engagement.
- Support windows and response commitments live in your agreement; this page does not state an SLA.
How a transaction is traced
Illustrative — not customer data
An illustrative reference trace across the buyer transaction cycle and Business Central.
| Buyer purchase order number | Business Central sales order number |
|---|---|
| Buyer item number | Business Central item number |
| Business Central posted shipment | Ship-notice reference |
| Business Central posted invoice | Invoice submission reference |
Scope and questions
- Is this buyer-side or supplier-side?
- Supplier-side only. Buyer-side Ariba procurement configuration is out of scope.
- cXML or EDI?
- Confirmed per buyer in scoping; the expected route differs by buyer.
- Does this work with on-premises Business Central?
- A supported connection path is confirmed in scoping. Cloud uses the standard APIs; on-premises requires an agreed access route.
- Who owns exceptions?
- APIWORX works the queue and escalates to your named contacts when a business decision is required.
Your integration plan
Get My Integration Plan
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Ready to map your integration?
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Next step
Scope your SAP Ariba + Business Central integration
Tell us your systems and documents. A specialist confirms scope by email.