Connect Dynamics 365 Business Central to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Dynamics 365 Business Central and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with Dynamics 365 Business Central EDI
XEDI connects Dynamics 365 Business Central with retailers, wholesalers and logistics providers so EDI orders, acknowledgements, despatch advice and invoices move between Business Central and your trading partners without manual entry.
One managed platform, no custom code
XEDI maps Dynamics 365 Business Central to your trading partners and validates every document, so data flows straight into the systems your teams already use.
Business Central has the routes; the work is the agreement between two vocabularies
Business Central exposes its records through OData and API pages, and a retailer's order can become a sales order against the right customer, items and location without anything custom. A posted warehouse shipment raises the despatch advice, and the posted sales invoice goes out as the invoice.
The substance is not the connection. It is that a retailer identifies a delivery point by GLN and an item by GTIN, while Business Central identifies them by customer, ship-to code and item number. Reconciling those is the work, and it is ours.
Where an upgrade cadence bites
Business Central moves on a regular release cadence, and extensions or API pages that a previous integration depended on can shift underneath it. An interface built once against a specific tenant tends to need attention every time the platform moves.
Keeping the retailer-specific half outside Business Central limits what an upgrade can disturb. What the ERP sees is one consistent document per type, so a platform update is a change to one interface rather than to every retailer arrangement you have.
What your team sees day to day
You get an EDI mailbox and a portal that behaves like an inbox: retailer orders arrive, your team is notified, and nothing waits on the Business Central work being finished.
The documents then carry forward. The order becomes the despatch advice, amended if you are delivering more or less than ordered, with SSCC labels for the pallets, and becomes the invoice on delivery. Delivery of that invoice is confirmed in the dashboard, so a chase starts from evidence.
The integration sits over that workflow and automates it, so orders land as sales orders and posted shipments raise the outbound documents. Smaller teams work the portal directly; our API is for enterprises wanting finer control; an integration sits between.
Documents you can exchange
- Purchase orders landing as Business Central sales orders
- Order acknowledgements returned to trading partners
- Despatch advice and ASN messages from warehouse shipments
- Sales invoices posted from Business Central
- Item and price data where a partner maintains a catalogue
Built for Dynamics 365 Business Central teams
Whoever owns Dynamics 365 Business Central in your business, XEDI keeps EDI accurate and hands-off.
- Operations and fulfilment teams
- Finance teams
- Retail and wholesale suppliers
- Dynamics 365 Business Central administrators
- Businesses replacing manual order entry
Dynamics 365 Business Central EDI document types
The set varies by retailer, but a Business Central supplier programme is usually built from these flows.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Retailer demand landing as a Business Central sales order against the right customer, items, price and location. | Partner to Business Central |
| Order acknowledgements | What Business Central will actually supply once the order is checked against stock and credit. | Business Central to partner |
| Advanced shipping notices | Despatch and pack detail raised from a posted warehouse shipment, to carton or pallet level where required. | Business Central to partner |
| Invoices | Posted sales invoices referenced to the order and shipment so the retailer can match them. | Business Central to partner |
| Credit notes | Credit memos carried on the invoice message with a credit document code. | Business Central to partner |
| Item and price data | Item, pack and price data published to retailers that maintain a catalogue. | Business Central to partner |
How to connect Dynamics 365 Business Central with EDI using XEDI
Business Central already exposes what an EDI flow needs, so the build is mapping and verification rather than development. The sequence below is what onboarding looks like from your side.
-
01
We scope the Business Central company, locations and retailers in each document flow.
-
02
We build the mapping between each retailer's documents and your customers, items, ship-to codes and posting rules.
-
03
We configure validation so a document is checked against the retailer's rules before it reaches Business Central.
-
04
We prove the order, shipment and invoice flows against what each retailer requires and against how your company is set up.
-
05
You get documents that keep landing correctly through the release cadence, and we keep them aligned as the platform moves.
Ready to connect Dynamics 365 Business Central?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about Dynamics 365 Business Central EDI
Common requirements
- Business Central access
- Company and location structure
- Customer and ship-to records
- Item and unit data
- Which partners you trade with
What we need from you to build it
Only what we cannot hold for you. Every retailer's requirements are already ours, so this list is access and reference data.
- Business Central access
- An integration user with rights to the API pages or web services covering sales orders, shipments and invoices.
- Company and location structure
- Which company and locations each retailer trades against, since numbering and posting follow that.
- Customer and ship-to records
- Each retailer mapped to a customer, with their delivery points resolvable to a ship-to code.
- Item and unit data
- GTINs at each packaging level and the unit a retailer orders in, against the base unit held in Business Central.
- Which partners you trade with
- The retailers you trade with and expect to add. Their requirements are held by us, not chased by you.
Why suppliers choose XEDI for Dynamics 365 Business Central
- Most retailers are already live on our network, so a Business Central build does not gate your first electronic order.
- A new retailer is not an AL extension and a deployment. We take the build on and verify it first.
- Retailer rules live with us rather than inside Business Central, so an upgrade does not put your trading at risk.
- Documents are validated before they are sent, so a rejection surfaces while the order can still be changed.
- One connection covers current and future retailers, each onboarded by us.
- If a retailer flags a problem, we are told, not you, and we rectify it rather than passing it back as a ticket.
Can XEDI connect Business Central to EDI trading partners?
Yes. XEDI maps each retailer's EDI documents to Business Central sales orders, warehouse shipments and posted invoices, and returns acknowledgements, despatch advice and invoices in the format each retailer requires.
Will a Business Central update break the EDI flow?
The retailer-specific rules sit with us rather than inside Business Central, so an update affects one interface rather than every retailer arrangement. We monitor the flows and adjust them as the platform moves.
Does it work with Business Central online and on-premises?
Both are normally reachable, online through API pages and on-premises through web services. Which route applies is settled during scoping rather than being something you need to determine.
Plan your Dynamics 365 Business Central EDI setup
Everything you need to scope, map and go live with Dynamics 365 Business Central, in one place.