X12 vs EDIFACT vs Peppol: Which Standard Do You Actually Need?

Three standards. 190 countries. One question: which one do you actually need?

The answer depends on two things: where you trade and who you trade with. Not what you prefer, not what your ERP supports natively, not what your consultant recommends. Where you trade and who you trade with.

Here is a regional decision framework that works for most distributors and suppliers.

X12: if you trade with North American retail

X12 is the dominant EDI standard in North America. If you sell to Walmart, Target, Costco, Kroger, Whole Foods, Amazon, or any major US or Canadian retailer, you need X12.

The 850 is the purchase order. The 856 is the advance shipment notice. The 810 is the invoice. The 997 is the functional acknowledgement. These four cover the core order-to-cash cycle for retail supply.

X12 is also used in US healthcare (HIPAA mandates specific X12 transaction sets), US automotive, and US logistics.

If your trading is entirely within ANZ, EU, or UK with no North American component, you probably don't need X12. The exception is if you trade with a US-headquartered business that mandates X12 regardless of where the actual trade occurs. Some US multinationals do this.

EDIFACT: if you trade internationally outside North America

EDIFACT is the international standard. Developed by the United Nations. Used in Europe, Asia-Pacific, Latin America, the Middle East, and Africa.

ORDERS is the EDIFACT equivalent of the X12 850. DESADV is the despatch advice (equivalent to the 856). INVOIC is the invoice. CONTRL is the control message (equivalent to the 997).

If you supply to European retailers, foodservice distributors, or manufacturers — Tesco, Sainsbury's, Carrefour, Metro, Bidfood UK, Brakes — you need EDIFACT.

EDIFACT is also standard for container shipping and international logistics regardless of region. If your supply chain involves ocean freight, you will encounter EDIFACT.

Australian and New Zealand trading partners vary. Some major ANZ retailers and distributors use EDIFACT. Others have moved to Peppol for invoicing while retaining EDIFACT for procurement documents. Check the implementation guide before assuming.

Peppol: if you invoice government or large enterprises in ANZ, EU, UK, or SEA

Peppol is not a traditional EDI standard. It is a network and transport framework that carries structured e-invoices between businesses. The document format is Peppol BIS 3.0, based on the Universal Business Language (UBL) XML standard.

Peppol is mandatory for government invoicing in Australia, New Zealand, Singapore, Malaysia, and increasingly across EU member states. It is the standard that regulatory mandates are converging on globally.

Peppol handles invoices and credit notes well. Its support for procurement documents — purchase orders, advance shipment notices — exists in the standard but is not yet widely implemented by trading partners. Peppol is primarily an invoicing and e-procurement standard, not a full supply chain integration standard.

If you supply to government entities in ANZ, UK, EU, or Southeast Asia, you need Peppol. If you are selling to large enterprises that are mandating Peppol by contract under the Business E-Invoicing Right frameworks, you need Peppol.

You may need Peppol and X12 or Peppol and EDIFACT simultaneously. A foodservice distributor supplying to both a US hotel chain and the Australian government needs both.

The decision tree

Do you sell to North American retailers, manufacturers, or logistics providers?

Yes: you need X12.

Do you sell to European, UK, or international retailers, foodservice distributors, or manufacturers?

Yes: you need EDIFACT.

Do you invoice Australian or New Zealand government entities, or are your buyers mandating Peppol?

Yes: you need Peppol (PINT A-NZ).

Do you invoice EU government entities or large enterprises in Germany, France, Italy, or other EU countries?

Yes: you need Peppol BIS 3.0 plus the country-specific extension (XRechnung, Factur-X, FatturaPA, etc.).

Do you invoice Singapore or Malaysia government entities or large enterprises?

Yes: you need InvoiceNow (Peppol) or MyInvois.

Most distributors and suppliers at meaningful scale need at least two of these. ANZ businesses with any North American exposure need X12 and Peppol. Businesses with European exposure need EDIFACT and Peppol. Businesses trading globally need all three.

The practical implication

The standard you need is determined by your trading partner mix, not by what you would prefer to implement.

The practical question is not which standard to pick. It is how to support multiple standards without running multiple separate integration systems. A distributor that needs X12 for North American retail, EDIFACT for European suppliers, and Peppol for government invoicing should not be running three separate EDI platforms.

The right approach is a single integration layer that supports all three natively and routes each document through the appropriate standard based on the trading partner's requirements. Your internal systems stay in their own format. The integration layer handles the translation.

This is architecturally straightforward. It is not how most EDI was implemented twenty years ago, which is why many distributors are running fragmented stacks today.

Sable supports X12, EDIFACT, and Peppol BIS 3.0 natively. 14 protocols. One platform. Regional coverage across ANZ, UK, EU, US, and Southeast Asia.