Why Business Central Needs EDI
Microsoft Dynamics 365 Business Central is built for small and mid-sized businesses that need a comprehensive ERP for financials, supply chain, inventory, and operations. But BC on its own does not handle electronic data interchange with external trading partners. That is where EDI integration comes in. Unlike a simple packing slip, the EDI 856 transaction is sent via Electronic Data Interchange before the physical goods arrive. This allows the receiver to prepare their warehouse management system for the incoming delivery.
Most major retailers, including Walmart, Target, and Costco, require their suppliers to exchange business documents through EDI. Without integration, your team is left manually entering EDI 850 purchase orders into BC, manually generating invoices, and manually creating shipping notices. This leads to manual data entry errors, delays, and compliance penalties that directly erode your margins.
Integrating EDI with Business Central eliminates these redundant tasks and enables your team to process orders, invoices, and shipments at the speed your trading partners expect.
How EDI Data Flows Between Business Central and Trading Partners
The technical architecture of a Business Central EDI integration involves three layers working together:
- Trading partner layer: Your customer or retailer sends and receives EDI documents (850, 810, 856, etc.) through their own systems using EDI communication protocols such as AS2, SFTP, or a VAN
- EDI provider layer (middleware): An EDI provider like Vantree sits between your trading partners and your ERP. The provider receives inbound EDI documents, translates them from X12 format into a structure BC can consume, validates the data against your trading partner's specifications, and delivers it to BC via an API connector. For outbound documents, the process reverses: BC data is extracted, translated into EDI format, validated, and transmitted to the trading partner.
- Business Central layer: The ERP receives translated data through the API and creates the appropriate BC objects automatically: sales orders from incoming 850s, posted shipments from outbound 856s, posted sales invoices from outbound 810s, and so on.
This middleware approach means Business Central never needs to understand raw EDI format. The EDI provider handles all translation, validation, and transmission. Your team works entirely within the familiar BC interface while documents flow automatically to and from your trading partners.
For cloud-based Business Central (SaaS), the connection between the EDI provider and BC uses Microsoft's standard APIs. For on-premises deployments, file-based or API-based approaches are both available depending on your infrastructure.
Key EDI Documents Automated in Business Central
When EDI is integrated with Business Central, the most common EDI document types are mapped to specific BC objects. Here is how the core documents flow:
Purchase Order — Inbound: Creates a Sales Order in BC with line items, quantities, prices, ship-to addresses, and requested delivery dates already populated.
Purchase Order Acknowledgment — Outbound: BC generates and sends a confirmation that the order has been received and accepted.
Advance Ship Notice — Outbound: When goods are shipped, BC generates the ASN with carton details, SSCC-18 label data, and tracking information.
Invoice — Outbound: BC generates and sends the invoice from the posted sales invoice, referencing the original PO number for automatic matching.
Remittance Advice — Inbound: Payment details from the trading partner are received and can be applied against open invoices.
Functional Acknowledgment — Both directions: Confirms receipt of any EDI document.
Warehouse Shipping Order / Advice — For businesses using 3PLs, BC generates the 940 to instruct shipment and receives the 945 as confirmation.
The Order-to-Cash Workflow in Business Central with EDI
Here is what a fully automated order-to-cash cycle looks like inside Business Central with EDI:
Retailer sends EDI 850
The purchase order arrives at your EDI provider, is translated and validated, and flows into BC as a new Sales Order with no manual entry.
BC sends EDI 855
An order acknowledgment is generated automatically and transmitted to the retailer.
Warehouse picks and packs
Staff fulfill the order using BC's inventory and warehouse functions.
BC sends EDI 856
The advance ship notice is generated from the posted shipment, including carton-level detail and tracking.
BC sends EDI 810
The invoice is generated from the posted sales invoice and transmitted to the retailer, referencing the original PO for seamless matching.
Retailer sends EDI 820
Payment remittance is received and applied in BC.
Each step that previously required manual data entry, email follow-up, or spreadsheet tracking now happens automatically. The result is faster order processing, fewer errors, reduced chargebacks, and better visibility into every transaction from within your BC environment.
Cloud vs. On-Premises: EDI Considerations for Business Central
Business Central is increasingly deployed as a cloud (SaaS) solution, which affects how EDI connects to the system.
Cloud Business Central does not allow direct file system access. All integrations must use Microsoft's published APIs or web services. This means your EDI provider's connector must be API-based. The advantage is that updates to BC happen automatically, and the API approach is scalable and secure. Vantree's connector is designed for this architecture.
On-premises Business Central offers more flexibility. EDI data can flow through APIs, file drops to monitored folders, or direct database integration. Some businesses prefer file-based integration for simplicity, while others use APIs for real-time data synchronization.
Regardless of deployment type, the EDI provider handles the translation and transmission layer outside of BC. Your ERP configuration stays clean, and your team does not need to manage EDI standards or trading partner specifications directly.
Migrating EDI from Dynamics NAV to Business Central
Many current Business Central users migrated from Microsoft Dynamics NAV. If your EDI was working with NAV and you are moving to BC, here is what to expect:
Trading partner connections stay intact
If you use a managed EDI provider like Vantree, your VAN connections, AS2 certificates, and trading partner relationships remain unchanged. The EDI provider manages the external communication layer independently of your ERP.
EDI maps need reconfiguration
The connector between EDI and your ERP must be updated. NAV often used file-based integration (XML or flat file drops), while cloud BC requires API-based connectors. Vantree reconfigures the data mapping between EDI fields and BC objects as part of the migration.
Document flow logic is preserved
The business logic (which documents trigger which responses, validation rules, compliance requirements) carries over. Only the technical connection method changes.
Working with an EDI provider that has experience with both NAV and BC ensures the migration does not disrupt your trading partner relationships or compliance status.
How Vantree Integrates EDI with Business Central
Vantree's EDI solution for Dynamics 365 Business Central connects your ERP to any trading partner through a single, fully managed integration platform.
Vantree's Vantree Connectivity Suite (VCS) sits between your Business Central environment and your trading partners. VCS handles all translation, validation, and transmission of EDI documents through an API connector designed for both cloud and on-premises BC deployments.
What Vantree's managed service covers:
Full document automation
Inbound 850s create sales orders, outbound 856s and 810s are generated from posted shipments and invoices, all without manual intervention.
Custom mapping per trading partner
Each trading partner has different EDI requirements. Vantree configures and maintains separate maps for each partner.
NAV-to-BC migration support
If you are moving from NAV, Vantree reconfigures your EDI connector while keeping your trading partner connections live.
Ongoing compliance management
When trading partners change their EDI specifications, Vantree updates your maps proactively.
Team-based support
Dedicated solution agents who understand your BC environment and your trading partner relationships.
Vantree supports 35+ ERP integrations beyond Business Central, so if your organization runs multiple ERPs, your EDI can be managed from a single platform. For businesses starting with EDI, Vantree also offers a web-based EDI solution and full EDI automation as upgrade paths.
For full details on Vantree's Business Central EDI capabilities, visit our Business Central EDI integration page.
Talk to an EDI ExpertFrequently Asked Questions About Business Central EDI
What EDI documents can be automated in Business Central?
The most commonly automated documents include EDI 850 (Purchase Order), EDI 855 (PO Acknowledgment), EDI 856 (Advance Ship Notice), EDI 810 (Invoice), EDI 820 (Remittance Advice), and EDI 997 (Functional Acknowledgment). Warehouse documents such as EDI 940 and 945 can also be automated for businesses working with 3PLs. The specific documents depend on your trading partners' requirements.
Do I need a separate EDI provider for Business Central?
Yes. Business Central does not include built-in EDI translation or trading partner communication. You need an EDI provider or managed service that handles document translation, validation, and transmission between your BC system and your trading partners. Vantree's VCS connector integrates directly with BC through APIs, so your team works entirely within the ERP interface.
Can I keep my EDI connections when migrating from NAV to Business Central?
Yes. If you use a managed EDI provider, your external trading partner connections (VAN, AS2, certificates) remain unchanged during the migration. Only the connector between the EDI provider and your ERP needs to be reconfigured from NAV's file-based approach to BC's API-based architecture. Vantree handles this reconfiguration as part of the migration process.
Does Vantree support cloud and on-premises Business Central?
Yes. Vantree's API connector is designed for cloud Business Central (SaaS) using Microsoft's published APIs, and also supports on-premises deployments through API or file-based integration. Both deployment types receive the same managed service, document automation, and trading partner support.
