- Feature
- Exchange EDI documents
- Availability
- Preview; Microsoft's roadmap lists general availability for April 2027
- Industry focus
- Consumer packaged goods suppliers to major retailers
If you supply a national supermarket chain, a DIY superstore or a large online retailer, EDI isn't optional. It's how your customer sends purchase orders, expects advance ship notices and receives invoices. For Business Central customers, EDI has usually meant a third-party app or service bolted onto the ERP. Microsoft has now signalled a significant change of direction.
The industry challenge
A typical consumer goods supplier, such as a snack manufacturer, household products brand or garden goods producer, trades with several large retailers. Each one brings EDI requirements:
- Purchase orders arrive electronically and must become sales orders quickly
- Order acknowledgements and advance ship notices must be sent on time
- Invoices must match the retailer's format and data rules exactly
- Chargebacks or penalties may apply for late or incorrect messages
Business Central doesn't include full trading-partner EDI out of the box. Its E-Documents framework has focused on electronic invoicing and regulatory scenarios such as Peppol. So suppliers have relied on separate EDI apps, managed services or custom integrations. These work, but they add another system to manage, another set of maps and another place where errors can hide.
What Microsoft is delivering
Microsoft's roadmap describes an extension of the E-Documents framework to support EDI. The aim is to let organizations exchange business documents electronically with vendors and partners using widely adopted industry standards. According to Microsoft, the key capabilities are:
- Using the existing E-Documents framework as one platform for managing electronic document exchange
- Automating the generation, sending and processing of electronic business documents
- Aligning with regulatory, industry and partner requirements for electronic document exchange
Microsoft says this lets organizations modernize supply chain and procurement processes with a consistent, scalable approach to electronic business communication.
The feature is in preview, and Microsoft's roadmap shows general availability planned for April 2027. Detailed specifics, such as which EDI standards, message types and connectivity options will be supported, should be confirmed as the feature matures.
Where the value could show up
| Business area | Potential impact for a retail supplier |
|---|---|
| Order intake | Retailer orders flow into Business Central through one framework |
| Compliance | Messages aligned with partner and industry requirements |
| Systems landscape | Fewer separate tools for e-invoicing and trading-partner EDI |
| Visibility | One place to see the status of electronic documents |
| Scalability | A consistent approach as you add new retail customers |
The strategic point is consolidation. Suppliers that already use E-Documents for e-invoicing could eventually manage EDI in the same framework, rather than in a separate silo.
A worked scenario
Consider a manufacturer of frozen desserts that supplies three supermarket chains and a food-service wholesaler (an illustrative example). Today, it receives orders through a third-party EDI service that drops files into Business Central. Invoices to one chain go via the same service, while e-invoices to public sector customers go through E-Documents.
The finance director wants to know whether this can be simplified. The IT lead sets up a preview environment and tests how the new EDI capability handles one retailer's purchase orders and invoices through E-Documents. The goal isn't to switch in production yet. It's to understand coverage, gaps and the effort of moving each trading partner, so the business can plan a decision for when the feature reaches general availability.
Adoption considerations
- Treat it as preview. Don't move live trading partners until the feature is generally available and fully tested.
- List your trading partner requirements. Document each retailer's standards, message types and connectivity needs, then compare them with what Microsoft supports.
- Check your current EDI contracts. Understand notice periods and costs for any existing EDI service.
- Plan partner testing. Retailers usually require formal testing before accepting messages from a new system.
- Keep finance and logistics involved. EDI touches orders, shipping and invoicing, so it isn't only an IT project.
The bottom line
For suppliers to large retailers, EDI is the price of doing business. Microsoft's move to bring EDI into the Business Central E-Documents framework could simplify that landscape over time, with one framework, more automation and clearer visibility. The right step now is to understand it, test it in preview and prepare a plan, not to rush.
If EDI is critical to your business, it's worth reviewing your current set-up and future options with an experienced Business Central adviser.
Source: Microsoft roadmap 573305