Mon – Sat: 9:00 AM – 7:00 PM IST
Integrations

What is EDI?

Structured business documents exchanged machine to machine — and the onboarding that takes longer than the build.

In short

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.

Why It Matters

Why this matters in practice

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.

Removes re-keying of orders, invoices and despatch advices
Often mandated by large trading partners
Standards define structure; partners define the details
Onboarding effort is per partner and dominates the timeline
How It Works

How it works in practice

1

Standards

EDIFACT is prevalent internationally, ANSI X12 in North America. Both define message structures for common documents.

2

Common documents

Purchase order, order response, despatch advice, receipt advice and invoice — the core cycle most partnerships start with.

3

Transport

Historically a value-added network; increasingly AS2 or secure file transfer directly between partners.

4

Mapping

Between the partner's message and your internal document structure. This is where partner-specific interpretation lives.

5

Onboarding and testing

Each partner supplies a specification, then runs test cycles before production. Allow weeks per partner, not days.

Worked example

A worked example: acknowledged is not accepted

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.

Key terms

The vocabulary, briefly

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.
What Goes Wrong

Common mistakes worth avoiding

Timeline estimated on the build

The build is reusable; onboarding is not. Estimate per partner, including their testing availability.

Acknowledgements ignored

Functional acknowledgements confirm receipt. Not processing them means silent failures look like successes.

Partner variations assumed minor

Required fields, qualifiers and code lists differ by partner within the same standard.

No reconciliation

Documents sent should be matched to documents acknowledged. Without it, missing messages surface as disputes.

What to measure

Numbers worth tracking

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.
FAQ

Questions we are asked about this

Extensively, particularly in retail, automotive, logistics and healthcare, where large partners mandate it. API-based exchange is growing alongside it rather than having replaced it.
A value-added network is an intermediary that routes EDI messages between partners and provides mailboxing and audit. Direct AS2 connections are increasingly used instead to avoid per-message charges.
Yes, and it will be for a long time. Retail, automotive, logistics, healthcare and grocery supply chains run on EDI, the standards are deeply embedded, and large buyers mandate it as a condition of trading. Whether you prefer it is not usually the question — if a major customer requires EDI, you implement EDI. APIs are displacing it in newer relationships rather than replacing it in established ones.
The document specifying exactly how you and a partner exchange messages: which transaction sets, which standard and version, the specific field-level requirements, acknowledgement expectations, timing, and the technical connection. Partners frequently require variations from the base standard, which is why implementing EDI with one partner does not mean you have implemented it with the next.
Weeks to months, depending on how many transaction sets are involved and how particular the partner's requirements are. Large retailers typically have detailed specifications, a mandatory certification process and their own testing schedule, and that schedule is theirs rather than yours. Budget for the testing cycle specifically, because it is usually the longest part and the least controllable.
Large buyers commonly impose penalties for non-compliant EDI — late acknowledgements, wrong formats, missing data elements, labels that do not match the message. These can accumulate into meaningful money and are easy to overlook because they appear as deductions rather than as invoices. Monitor them specifically, categorise by cause, and treat a recurring category as a defect to fix rather than a cost of doing business.
Related

Where to read next

What is an IDoc?

Read more

What is an ASN?

Read more

API vs file-based integration

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.