EDI with Business Central
How EDI integration works with Business Central — direct EDI vendors, AppSource connectors, document mapping, and the trade partner setup.
EDI — Electronic Data Interchange — remains the backbone of B2B trading between manufacturers, distributors, and retailers. Business Central doesn't ship EDI capability out of the box, but the integration story is well-established and based on a small number of patterns.
The shape of EDI. Trading partners exchange structured business documents — purchase orders (850), order acknowledgments (855), advance ship notices / ASNs (856), invoices (810) in the American X12 format, or ORDERS, ORDRSP, DESADV, INVOIC in EDIFACT. Documents travel over AS2, SFTP, VAN, or AS4 transport. Each trading partner has slightly different requirements; standardised on paper, varied in practice.
The Business Central path. Three real options.
-
AppSource EDI connectors. Several ISVs publish packaged EDI modules — Lanham EDI, EDICOM for BC, Pagero, TIE Kinetix, others — that install into Business Central and provide a configuration UI for partner setup, message mapping, document send/receive, and audit. The most common pattern for SMBs. The connector handles transport, parsing, mapping, and integration with BC's sales/purchase document objects.
-
External EDI service providers. Use a dedicated EDI service (SPS Commerce, OpenText GXS, IBM Sterling, TrueCommerce) that handles transport and translation, and integrate to BC via a lightweight bridge — typically file drops, REST API, or an ISV connector. Common when the trading partners require an established EDI provider, or when the volume is too high for in-platform processing.
-
Custom integration. Write AL code or a Logic Apps workflow that translates EDI documents to BC records. Cheap to start, painful to maintain across hundreds of partner-specific variations. Rarely the right answer beyond a very small footprint.
Trading partner setup. For each partner, the EDI module captures: the trading partner's EDI identifier (DUNS, GLN, custom code), the document types exchanged (PO, ASN, Invoice), the maps from partner format to BC document fields, sequence number ranges, time-of-day expectations, and acknowledgment requirements.
Inbound POs. A partner sends an 850/ORDERS. The EDI module receives it, validates, and creates a sales order in BC with the partner as the customer. Item-number mapping (partner's part number → BC item number) is critical and partner-specific. Errors stage for review.
Outbound ASNs and Invoices. When BC posts a shipment, the EDI module generates an 856/DESADV and sends it; same for invoices.
Compliance. Retail and automotive partners often impose chargebacks for late or malformed EDI — slipped ASNs after shipment, missing fields, incorrect GTINs. Monitoring and exception handling are non-negotiable.
Operational reality. EDI is unglamorous infrastructure. Budget for ongoing partner onboarding and map maintenance — every partner is a small project.
Related guides
- Common Business Central ISV add-onsCategories of Business Central ISV add-ons that customers most often install — country localizations, document automation, EDI, banking, and vertical industry apps.
- Integrating Business Central with Microsoft 365How Business Central plugs into Outlook, Teams, Excel, SharePoint, OneDrive, and the rest of Microsoft 365.
- Integrating Business Central with SalesforcePatterns for connecting Business Central to Salesforce — accounts and contacts, opportunities to orders, and the choice between iPaaS and direct integration.
- Integrating Business Central with ShopifyHow Microsoft's Shopify connector for Business Central works — items, orders, inventory sync, fulfilment, and the operational realities.
- Data integration for real-time marketing in Customer Insights — JourneysHow real-time marketing journeys consume external data — trigger events, custom triggers from external sources, the unified profile integration with Customer Insights — Data.