The short answer
Business Central relies on an integration layer for EDI translation. Partner purchase orders become sales orders through Business Central's REST APIs or OData web services, item references translate customer item numbers, and posted shipments and invoices drive outbound ship notices and invoices. Extensions add partner-specific fields, and job queues schedule background processing.
Read the diagram from top to bottom. Business Central does not exchange X12 itself in this design: the integration layer handles the partner connection and translation, and Business Central creates and posts the business records. Outbound documents are built from what Business Central actually recorded.
How EDI connects to Business Central
Dynamics 365 Business Central serves many small and midsize distributors and manufacturers who sell to retailers requiring EDI. An integration layer handles translation and partner connectivity and exchanges data with Business Central through its APIs.
Document mapping
| EDI document | Direction | Business Central document |
|---|---|---|
| 850 purchase order | Inbound | Sales order |
| 855 acknowledgment | Outbound | Sales order lines and status |
| 856 ship notice | Outbound | Posted sales shipment, warehouse shipment |
| 810 invoice | Outbound | Posted sales invoice |
| 846 inventory | Outbound | Item availability |
Integration options
- Business Central APIs (v2.0): standard REST endpoints for customers, items, sales orders, sales shipments and sales invoices. Suitable for most EDI scenarios.
- OData web services: publish pages or queries for data not covered by standard APIs.
- AL extensions: add partner-specific fields and logic, such as EDI identifiers or original purchase order line numbers.
Partner data
- Item references map customer item numbers to your items.
- Ship-to addresses store retailer store and distribution center codes.
- Customer fields hold EDI identifiers and partner settings, often added through an extension.
Shipping data
Retail ship notices need carton-level detail and GS1-128 labels. Basic shipments can be built from posted sales shipments, but carton contents usually require warehouse functionality, an extension or a WMS. Plan this with the warehouse team before go-live.
Scheduling and limits
- Job queue entries can run background processing, such as posting imported orders.
- Business Central applies API rate limits per environment, so design batch sizes and frequencies accordingly.
- Trigger time-sensitive outbound documents, such as ship notices, promptly after posting.
Best practices
- Validate items, customers and prices before creating sales orders.
- Keep original partner references so outbound documents echo them exactly.
- Keep partner-specific logic in the integration layer or a well-documented extension.
- Monitor each order through acknowledgment, shipment and invoice.
- Start with web EDI for low-volume partners and integrate as volume grows. See web EDI vs integrated EDI.