+1 480 485 7373
Microsoft Teams
The X12 documents trading partners usually require
Where the translator sits between you and each buyer
EDI has three layers. Communication moves files between companies, through a value-added network (VAN), AS2 connections or SFTP. Translation turns X12 segments into readable data and back. Integration turns that data into Business Central sales orders, shipments and invoices. Some providers cover all three; others only translate and leave the Business Central side to you or your partner.
Ownership needs to be clear. Business Central owns customers, items, prices, stock and posted documents. The trading partner owns its purchase order and its specification. The EDI provider owns the envelopes, partner IDs and the archive of files sent and received. Your item references in Business Central store the partner's item numbers or UPCs, so an incoming 850 finds your item without guesswork.
Price disagreements deserve a rule too. Sometimes an 850 arrives at a price that differs from yours. Decide in advance whether the order holds for review or takes the buyer's price. The 810 must match what the buyer expects to pay.
EDI provider app, managed service or in-house translation
EDI app inside Business Central
Several EDI providers publish apps on AppSource that create documents directly in Business Central.
- ✓Trading partner maps often maintained by the provider
- ✓Users work EDI exceptions from Business Central pages
- ✓Check which of your partners the provider already supports
Fully managed EDI service
A provider runs translation and partner onboarding and exchanges flat files or API calls with Business Central.
- ✓Little EDI knowledge needed in house
- ✓The Business Central connection still needs designing and testing
- ✓Per-partner and per-document charges vary widely, so compare quotes
Own translator with custom integration
You license translation software and build the Business Central side through APIs or AL.
- ✓Full control over maps and timing
- ✓Needs someone who reads X12 fluently
- ✓Makes sense with many partners and in-house technical staff
Onboarding a new trading partner
- 1
Read the specification
Collect the partner's implementation guide and routing guide, and note required segments, label formats, ship windows and allowed changes.
- 2
Set up identifiers
For each Business Central EDI integration partner, record the ISA and GS identifiers, ship-to codes and item cross-references in both places.
- 3
Test file exchange
Exchange test 850s and send back 855, 856 and 810 files until the partner's testing portal or analyst passes each one.
- 4
Ship pilot orders
Run the first live orders with extra checks on carton labels and ship notice timing before switching the partner to production.
- 5
Monitor every day
Watch for missing 997s, orders that failed to import and ship notices not sent within the partner's window.
Compliance mistakes that become retailer chargebacks
- ✓Ship notices sent after the truck arrives, or not at all
- ✓Carton labels whose SSCC numbers do not match the 856
- ✓Invoice quantities that differ from what the ship notice said
- ✓Unit of measure confusion between eaches, inner packs and cases
- ✓Shipping to a distribution center when the order named a store
- ✓Ignoring PO changes and shipping the original quantities
EDI questions from distributors and manufacturers
Does Business Central include EDI?
No, standard Business Central has no built-in X12 translation. It has the documents EDI needs, such as sales orders, shipments, invoices and item references, and an API that providers use. The translation and communication come from an EDI provider app, a managed service or your own software. That is normal for ERPs in this size range.
Do we need a VAN?
Only if a trading partner requires one or your provider uses one. Many large retailers accept AS2 connections, and many EDI providers include network access in their service. Some buyers still insist on a particular VAN or interconnect. Your partners' specifications answer this, which is why we read them first.
How do carton labels and ship notices come out of Business Central?
They come from the packed shipment. Someone, or a warehouse app, records which items went in which carton. The system assigns SSCC numbers and prints GS1-128 labels. Then it builds the 856 from the same data. Standard Business Central does not do carton-level packing on its own, so this usually comes from the EDI app or a warehouse add-on. Getting packing right is most of the effort in 856 compliance.
More Business Central EDI integration questions
Can EDI orders flow in without anyone checking them?
Clean orders can, and exceptions should stop. We set rules so an 850 with a known customer, known items, expected prices and a valid ship-to becomes a released sales order automatically. Anything else waits in a review list with the reason shown. Buyers accept that, as long as acknowledgments still go out on time.
We already use EDI with our old system. What changes when we move?
Your trading partners should see as little change as possible. Partner IDs and connections normally stay with your EDI provider. We rebuild the maps between EDI data and your ERP for Business Central. Every partner still needs retesting, because a small difference in the 856 or 810 can trigger chargebacks. We schedule that retesting as part of the migration plan.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.