Structured business documents exchanged machine to machine — and the onboarding that takes longer than the build.
Electronic data interchange is the exchange of standard business documents between organisations in machine-readable format. Purchase orders, invoices, despatch advices and acknowledgements are sent as structured messages under an agreed standard, removing manual re-keying between trading partners.
EDI is often described as legacy, but it remains how a great deal of retail, automotive and logistics trade is conducted, and large partners mandate it. The technical implementation is rarely the hard part. Onboarding is: each partner has its own interpretation of the standard, its own required fields and its own testing cycle, and that cycle takes weeks per partner.
EDIFACT is prevalent internationally, ANSI X12 in North America. Both define message structures for common documents.
Purchase order, order response, despatch advice, receipt advice and invoice — the core cycle most partnerships start with.
Historically a value-added network; increasingly AS2 or secure file transfer directly between partners.
Between the partner's message and your internal document structure. This is where partner-specific interpretation lives.
Each partner supplies a specification, then runs test cycles before production. Allow weeks per partner, not days.
A supplier sends purchase order acknowledgements and invoices to a large retailer by EDI. The functional acknowledgements come back clean, so the supplier's team treats each exchange as successful.
A month later, a batch of invoices is found unpaid. The functional acknowledgement confirmed only that the message arrived and was syntactically valid — the envelope was well formed. The retailer's application subsequently rejected the invoices for a business reason: a purchase order number that did not match their records. That rejection came back as a separate application-level message that the supplier's system logged and nobody monitored.
The distinction between transport acknowledgement, syntactic acknowledgement and business acceptance is the single most common source of EDI surprises. Monitoring must cover all three, and the one that matters commercially is the last. A clean functional acknowledgement rate of 100 percent is entirely compatible with invoices not being paid.
| Term | What it means |
|---|---|
| Transaction set | A standard message type, such as a purchase order or an invoice. |
| ANSI X12 / EDIFACT | The two dominant standards, prevalent in North America and internationally. |
| VAN | Value added network — an intermediary routing EDI messages between partners. |
| AS2 | A protocol for exchanging EDI directly over the internet with receipts. |
| Functional acknowledgement | A message confirming receipt and syntactic validity, which is not the same as acceptance. |
The build is reusable; onboarding is not. Estimate per partner, including their testing availability.
Functional acknowledgements confirm receipt. Not processing them means silent failures look like successes.
Required fields, qualifiers and code lists differ by partner within the same standard.
Documents sent should be matched to documents acknowledged. Without it, missing messages surface as disputes.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Acknowledgement rate by level | Transport, syntactic and business acceptance tracked separately. | |
| Application rejections by reason | The commercially meaningful failures, and what causes them. | |
| Partner onboarding time | How long to bring a new trading partner live, which varies enormously. | |
| Chargebacks from compliance failures | Retailer penalties for EDI non-compliance, which can be substantial. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.