CONSULTING EXCELLENCE

Connect to Microsoft Dynamics EDI Instantly!

Join thousands of customers that connect to Microsoft Dynamics with XEDI

Try it now Get Started

FEATURES

Getting started with Microsoft Dynamics EDI

XEDI connects Microsoft Dynamics with EDI trading partners, automating order, fulfilment and invoice document exchange for suppliers, distributors and finance teams.

Business Central and Finance & Operations are different projects

Dynamics 365 Business Central and Dynamics 365 Finance & Operations share a brand and very little else that matters here. They expose different entities, different APIs and different extension models, and an integration built against one does not carry across.

Naming the target first avoids the usual scoping problem, where a project quoted against Business Central meets an F&O tenant with different entity names and a different data model.

Data entities, not tables

Dynamics exposes data through entities rather than direct table access, which is good for stability and means the mapping has to work with what the entity actually surfaces. Fields a retailer expects are sometimes on a related entity, or on an extension somebody added.

Customer, item and address mapping is the substantive work. Retailers identify depots by GLN and products by GTIN; Dynamics identifies them by customer, ship-to code and item number, and every document crossing the boundary needs both views reconciled.

Common Microsoft Dynamics EDI documents

Purchase orders
Order acknowledgements
ASN and despatch advice messages
Invoices
Credit notes where required

Typical users

Microsoft Dynamics users
Wholesale and retail suppliers
Operations teams
Finance teams
EDI coordinators

UN/EDIFACT messages behind Microsoft Dynamics EDI

The documents above are exchanged as UN/EDIFACT messages. Each one below links to the D96A specification for that message: the segments it defines, which of them are mandatory, and the fields that most often need attention when a system integration is being mapped and tested.

ORDERS Purchase Order Message
The buyer's instruction to supply: what is wanted, how much, at what price, delivered where and when.
ORDRSP Purchase Order Response Message
The supplier's answer to an order: accepted as sent, accepted with changes, or rejected.
DESADV Despatch Advice Message
Sent when goods leave the supplier, describing exactly what is on the way and how it is packed. Widely known as an ASN.
INVOIC Invoice Message
The supplier's request for payment: what was supplied, at what price, with what tax, and what is owed.

Microsoft Dynamics EDI document flows

The flows below cover most Dynamics supplier programmes on either product.

Document	What it carries	Direction
Purchase orders	Retailer demand creating a sales order against the right customer, items and ship-to address.	Partner to Dynamics
Order acknowledgements	Confirmation of accepted, amended and rejected lines.	Dynamics to partner
Advanced shipping notices	Despatch advice from the Dynamics shipment, with pack structure where required.	Dynamics to partner
Invoices	Posted sales invoices referenced to the order and delivery for automatic matching.	Dynamics to partner
Credit notes	Credit memos against a previously sent invoice.	Dynamics to partner
Product and price data	Item and price data for partners maintaining a catalogue.	Dynamics to partner

How to connect Microsoft Dynamics with EDI using XEDI

Dynamics connections are staged per partner, with the first settling the entity mapping the rest reuse.

Confirm the Dynamics environment, entities and trading partner document flows.
Map EDI data to customers, items, locations, tax and fulfilment records.
Configure validation and partner routing in XEDI.
Test required documents with each partner.
Monitor live transactions and handle exceptions.

What Microsoft Dynamics EDI needs from your setup

Have these confirmed and mapping is configuration rather than discovery.

Which Dynamics product

Business Central or Finance & Operations, with the environment and version, since entities differ between them.

API access

Permission for the entities in scope, and awareness of any extensions that change their shape.

Customer and ship-to mapping

Partners mapped to customers, delivery points mapped to ship-to codes carrying the partner's GLN.

Item and unit data

GTINs per packaging level and the unit conversion between ordering and stocking units.

Posting rules

When an invoice posts relative to shipment, since some retailers reject invoices that arrive first.

Common requirements

Dynamics access or integration method
Customer, item and location mappings
Trading partner EDI specifications
Invoice and tax rules
Connection method and testing requirements

Where Microsoft Dynamics EDI projects usually go wrong

A Business Central mapping applied to Finance & Operations, where entity names and structures differ.
Extensions altering an entity's shape without the integration being told, so fields silently stop populating.
Ship-to codes created without the retailer's GLN, making address resolution manual.
Invoices posting before shipment confirmation, which some retailers reject outright.
Sandbox refreshes resetting identifiers and breaking a mapping that was correct the previous day.

Why suppliers run Microsoft Dynamics EDI on XEDI

One connection covers EDIFACT, TRADACOMS and X12 across both Dynamics products.
Partner rules are validated before documents are sent, so rejections do not surface as payment problems.
Adding a retailer is configuration rather than an extension and a release cycle.
Every message is traceable end to end for dispute resolution.

Microsoft Dynamics EDI integration FAQs

Can XEDI connect Microsoft Dynamics to EDI partners?

Yes. XEDI can connect Dynamics workflows with partner EDI requirements for orders, fulfilment messages and invoices.

XEDI is fully compliant with all of Microsoft Dynamics EDI requirements, which requires suppliers to process orders & invoices.

Get Started

Ready to get started?

Get in touch and one of our experts will take you through a demo

Book a Demo