Business Central EDI that trades orders, ship notices and invoices

How Business Central EDI works

EDI is a set of agreed file formats that companies use to swap business documents. X12 is the common one in North America, and EDIFACT is common in much of the rest of the world. A retailer sends an 850 purchase order. You answer with an 855 acknowledgment, an 856 advance ship notice and an 810 invoice.

Business Central stores the orders, shipments and invoices. A translator turns them into the partner's format and back. That translator is either an add-on in your environment or a hosted EDI service linked through the Business Central API. We help you pick the model that matches your volume and your partners.

Signs your company is ready for Business Central EDI

Most companies start because a customer requires it. Large retailers, grocery chains and distributors publish a partner guide. They expect suppliers to trade electronically, often with charges for late or wrong ship notices. A new account with one of them is the usual trigger. Trading electronically becomes a condition of the account.

Others start from the inside. Does your order desk key the same customer orders from emailed PDFs every morning? Do your buyers retype supplier confirmations? Then EDI removes that typing and the mistakes that come with it. Third-party warehouses also use EDI to swap shipping orders and stock counts.

Our approach to a Business Central EDI project

We begin with your partner list and each partner's guide. For every document, we write a map. It shows which Business Central field feeds which EDI element. It shows how item cross-references turn your item numbers into the partner's. The map also covers units of measure, ship-to codes and pack sizes.

Then we build in a sandbox. We check inbound orders before they become sales orders. So a wrong price or an unknown item lands in an exception list, not in a posted document. We run the partner's test cycle with you. We move to production only after the partner signs off.

What you get from a Business Central EDI project

You receive working document flows for each partner in scope. They run on a schedule through the job queue or the provider's service. Orders arrive as sales orders with the customer's references. Posted shipments and invoices go out with no manual step. Your order desk stops printing and keying.

You also get the written maps and an exception list your team can work from each morning. Also, short instructions cover adding items, ship-to addresses and new partners. We set up carton labels and packing structure for the ship notice where the partner asks for them. Nothing depends on one person's memory.

Business Central EDI pitfalls we steer around

The most common failure is master data. EDI exposes every missing cross-reference, wrong unit of measure and outdated price. No person is there to correct the order on the way in. So we clean this data before the first test file, not after. Cleaning it late delays the partner's test cycle.

However, the second is the ship notice. It must match what staff packed, carton by carton. So the warehouse process matters as much as the map. We also avoid custom code where a standard add-on setting does the job. That keeps the release waves from breaking your flows.

Business Central EDI questions

Does Business Central include EDI out of the box?

No. Business Central holds the orders, shipments and invoices, but it has no built-in X12 or EDIFACT translator. You add EDI through an add-on from Microsoft's marketplace or through a hosted EDI provider linked by API. We help you compare the two models and pick one.

Should we use an add-on or an outside EDI provider?

An embedded add-on keeps everything inside Business Central. That suits teams that want to see and fix documents on familiar pages. A hosted provider takes on partner maps and communications for you. The right answer depends on partner count, document volume and how much your team wants to manage.

Which trading partners can you connect?

Any partner that publishes an EDI guide. That includes large retailers, grocery chains, distributors, carriers and third-party warehouses. Each one has its own rules for the same document. So we map and test partner by partner, and we keep a clear record of each partner's rules.

What do we need to prepare before starting?

You need a list of partners and the documents each one requires. You also need their implementation guides and your item list with the partner's item numbers. Finally, you need a contact on the partner's EDI team. Clean units of measure and ship-to addresses save the most time during testing.

What happens when an inbound order has an error?

The order stops in an exception list with the reason shown. For example, an unknown item or a price that differs from your price list. Someone on your team fixes it or contacts the customer. Then they release it to become a sales order. So bad data never reaches your books.

Services that pair with EDI

EDI touches sales orders, warehouse shipping and invoicing, so it rarely stands alone. The pages below cover the processes and integrations that usually sit next to an EDI project in Business Central. Read them to see where Business Central EDI fits. Then send us your partner list, and we will tell you which documents to map first. For the product detail, see Business Central documentation on Microsoft Learn.