EDI standards explained: a practical guide for enterprises

EDI standards exist for one reason: to make business systems understand each other.

Orders, invoices, credit notes, delivery notes, and shipment messages all need structure. Without a shared structure, every trading partner becomes a custom integration project.

That is what EDI standards solve.

But the landscape isn't simple. Enterprises operating across Europe and globally may need to support EDIFACT, ANSI X12, Peppol, OIOUBL, TRADACOMS, KSeF, and PDP models at the same time.

The important point is this:

You don't choose one EDI standard for your entire business.
You choose the right standard for each market, partner, and document flow.

What is an EDI standard?

An EDI standard defines how business data should be structured so it can move between systems automatically.

It answers questions like:

• What fields are required?
• Where should buyer and seller information appear?
• How should order lines be structured?
• What format should invoice totals, VAT, and delivery data follow?
• How should the receiving system validate the document?

EDI standards are what make automated document exchange possible.

Without them, companies fall back to PDFs, emails, spreadsheets, and manual re-entry.

EDIFACT: the global enterprise standard

EDIFACT is one of the most widely used EDI standards in the world, especially across Europe and international supply chains.

It is common in:

• retail
• manufacturing
• logistics
• wholesale
• cross-border trade

Typical EDIFACT messages include:

• ORDERS — purchase order
• ORDRSP — order response
• DESADV — despatch advice
• INVOIC — invoice
• PRICAT — price catalogue

EDIFACT is powerful because it's mature, flexible, and globally understood. But that flexibility also creates complexity. Different partners often implement the same message type differently.

That means EDIFACT is rarely “plug and play”. It requires mapping, validation, and partner-specific handling.

Best fit: large enterprises, international supply chains and complex B2B document flows.

ANSI X12: the North American standard

ANSI X12 is the dominant EDI standard in the United States and much of North America. ANSI X12 and EDIFACT are described as two of the most important global EDI standards, with X12 especially common in the US market.

Typical X12 transaction sets include:

• 850 — purchase order
• 855 — purchase order acknowledgement
• 856 — advance ship notice
• 810 — invoice
• 997 — functional acknowledgement

If your enterprise sells to American retailers, distributors, healthcare organisations, or logistics networks, X12 is often unavoidable.

For European companies expanding into the US, this is usually the first major format shift they encounter.

Best fit: North American retail, manufacturing, healthcare, logistics, and enterprise supply chains.

Peppol: not just a format, but a network

Peppol is often discussed as if it were an EDI format. That's not entirely correct.

Peppol is a network and interoperability framework for exchanging structured electronic documents. It uses common specifications such as Peppol BIS Billing 3.0, built around European e-invoicing standards.

Peppol is increasingly important because it supports:

• cross-border e-invoicing
• public sector invoicing
• B2B e-invoicing mandates
• standardised document exchange across Europe and beyond

OpenPeppol maintains formal documentation for the network, including technical specifications and governance documents.

The strength of Peppol is interoperability.

Instead of building one connection per partner, companies connect through a certified access point and exchange documents with other participants in the network.

Best fit: e-invoicing, public sector trade, European B2B compliance, and cross-border document exchange.

OIOUBL: Denmark’s national e-invoicing standard

OIOUBL is Denmark’s national document standard, closely connected to NemHandel.

In Denmark, electronic invoicing is mandatory when supplying goods and services to public authorities. OpenPeppol notes that invoice senders can use either Peppol or the national OIOUBL format, while public sector recipients must support both.

OIOUBL covers more than invoices. The official OIOUBL material describes standards for key business documents across the trade process, from catalogue to invoice.

For companies trading in Denmark, OIOUBL remains important because many public and private workflows still depend on it.

Best fit: Danish public sector invoicing, NemHandel, Danish B2B document exchange, and local compliance.

TRADACOMS: still relevant in UK retail

TRADACOMS is an older UK EDI standard, historically used in retail and grocery supply chains.

It has been partly replaced by EDIFACT in many areas, but it is still found in legacy retail environments. TRADACOMS is listed alongside ANSI X12, EDIFACT, EANCOM, and XML as one of the major EDI standards used worldwide.

For enterprises working with UK retailers, TRADACOMS may still appear in:

• orders
• invoices
• delivery notes
• product data
• retail-specific document flows

The challenge with TRADACOMS is not popularity. It's legacy dependency. Some partners still require it because their internal systems and workflows were built around it.

Best fit: UK retail, grocery, wholesale, and legacy trading partner requirements.

KSeF: Poland’s national e-invoicing platform

KSeF isn't a traditional EDI standard. It's Poland’s national e-invoicing system.

KSeF stands for Krajowy System e-Faktur, or the national e-invoicing system. It's a central government platform for issuing, receiving, and storing structured invoices in Poland.

Invoices in KSeF are structured XML documents and several sources note that Poland is moving to the FA(3) XML schema as part of the mandatory e-invoicing rollout.

This matters because companies trading in Poland can't simply send a PDF or generic invoice file. They must comply with the KSeF model and its structured invoice requirements.

Best fit: Polish B2B and B2G e-invoicing compliance.

PDP: France’s e-invoicing model

PDP refers to France’s partner dematerialisation platform model.

Like KSeF, PDP isn't an EDI standard in the classical sense. It's part of a national e-invoicing and e-reporting infrastructure.

France is moving toward mandatory B2B e-invoicing and e-reporting. The French model requires invoices to move through accredited platforms. The French public service portal states that invoices must transit through a platform used by the issuer and recipient, and that this platform must be a partner dematerialisation platform accredited by the tax authorities.

France’s rollout begins with mandatory receiving requirements from September 2026, according to the European Commission’s country information.

For enterprises, the key point is that France introduces a compliance infrastructure layer. You're not only choosing a format. You're choosing how invoices are routed, validated, and reported.

Best fit: French B2B e-invoicing, e-reporting, and tax compliance.

How enterprises choose the right EDI standard

Enterprises usually don't choose standards based on preference.

They choose based on five practical questions.

1. Where are you trading?

Geography matters.

• Europe often means EDIFACT, Peppol, local UBL variants, and national platforms.
• Denmark may require OIOUBL and NemHandel.
• Poland means KSeF.
• France means PDP/approved platform requirements.
• North America often means ANSI X12.
• UK retail may still mean TRADACOMS.

The first step is always market mapping.

2. Who are your trading partners?

Large customers often dictate the standard.

A retailer, public authority, or marketplace may require a specific format, protocol, or validation rule. Trading partners define guidelines that specify required transaction structures, mandatory fields, and allowed values.

That's how EDI works in practice.

The “standard” is only the starting point. The partner implementation guide is what usually decides the final mapping.

3. Which documents do you need?

Different standards are stronger in different flows.

For example:

• Peppol is strong for invoices and increasingly broader e-procurement.
• EDIFACT is strong for full supply chain flows.
• X12 is essential for US retail and logistics.
• OIOUBL is important for Danish public and local business documents.
• KSeF and PDP are compliance-driven invoice models.

If your business only sends invoices, the decision may be simpler.

If you exchange orders, confirmations, shipping notices, catalogues, labels, and invoices, you need a broader EDI architecture.

4. Is this about operations, compliance, or both?

Classic EDI standards often solve operational exchange.

National e-invoicing systems solve compliance.

The future is a combination of both.

An enterprise may use EDIFACT for logistics and order flows, Peppol for e-invoicing, KSeF for Polish compliance, and X12 for US trading partners.

That's not unusual.

It's the normal reality of enterprise EDI.

5. Can your EDI provider translate between standards?

The real question is not whether your business can “choose” between EDIFACT, X12, Peppol, or KSeF.

The real question is whether your EDI setup can handle all of them.

Modern enterprises need a translation layer that can:

• convert formats
• validate documents
• apply partner-specific rules
• route through the correct network
• maintain compliance as standards change
• integrate cleanly with ERP systems

This is where provider choice matters.

Practical comparison: which standard should you use?

The most important lesson: standards don't remove complexity

EDI standards reduce complexity.

They don't remove it entirely.

Why?

Because every enterprise still has:

• different ERP systems
• different partner requirements
• different country rules
• different validation logic
• different document flows
• different compliance obligations

That's why EDI isn't just about supporting a list of formats.

It's about managing the translation between them.

Multi-format support can be described as a way to simplify format complexity, stay compliant with trading partner requirements, and deliver validated data for each transaction.

That's the practical challenge enterprises need to solve.

Final thought: choose infrastructure, not just a format

The future of EDI isn't one global standard.

It's a multi-standard reality.

Enterprises need to support:

• Classic EDI for supply chain operations
• Peppol for interoperable e-invoicing
• National platforms for tax compliance
• ERP integration for automation
• Partner-specific rules for real-world trading

The right question isn't:

“Which EDI standard should we choose?”

The better question is:

“Can our infrastructure support every standard our business needs — without creating a new project every time?”

That is where modern EDI should be heading.

Speak to an EDI expert

If your business needs to support EDIFACT, X12, Peppol, OIOUBL, TRADACOMS, KSeF, PDP or other local requirements, we can help you map the right setup.

Speak to our iEDI expert and see how one infrastructure can support every standard your partners require.