ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

The EDI standards landscape

Five message standards cover more than 95% of global EDI flows in 2026. This page draws their map — geographic, sectoral and functional — so that when faced with an integration project, you can pick the standard that actually matches the market's constraints.

Five families, two worlds

The landscape can first be grasped by a geographic divide. West of the Atlantic, the dominant standard is ANSI ASC X12, born in 1979. Everywhere else — Europe, Asia, Latin America, Africa — it is UN/EDIFACT, born in 1987 under the United Nations, that shapes the flows. Alongside these two historical heavyweights, three younger standards have each colonised a specific functional or sectoral perimeter: cXML for transactional e-procurement, SAP OCI for catalogue punchout, UBL/PEPPOL for European e-invoicing mandates kicking in from 2025/2026. We review each in turn.

EDIFACT — Europe and rest of world

UN/EDIFACT (Electronic Data Interchange For Administration, Commerce and Transport) is maintained by UN/CEFACT, the United Nations Centre for Trade Facilitation and Electronic Business. Its syntax is etched into ISO 9735 (since 1988) and its message directory is updated twice a year under a stable naming convention D.<YY>A (spring) and D.<YY>B (autumn). The historically dominant directory remains D.96A (1996) in European retail and logistics; D.01B (2001) is second; D.16B (2016) is referenced by EN 16931 (EU e-invoicing); D.24B is the most recent release.

An EDIFACT message is composed of three-letter segments separated by apostrophes: BGM (Beginning of Message), NAD (Name & Address), LIN (Line Item), DTM (Date/Time), QTY (Quantity), etc. Around twenty message types cover the transactional use cases: ORDERS (Purchase Order), ORDRSP (Order Response), DESADV (Despatch Advice / ASN), INVOIC (Invoice), CONTRL (syntactic acknowledgment), IFTMIN (transport booking).

EDIFACT is everywhere shaped by sectoral subsets that restrict or enrich the official directory: EANCOM (GS1) in retail, Odette in European automotive, CEFIC in chemicals, EDIFICE in electronics, PIDX in petrochemicals, EDIFER in steel. Each subset publishes its own implementation rules: an EANCOM ORDERS is not the same as an Odette ORDERS, even though both conform to the D.96A directory. That is why an EDI project always begins by identifying the expected subset.

X12 — North America

The ANSI ASC X12 committee is the American counterpart of UN/CEFACT: it publishes the X12 standard, accredited by the American National Standards Institute since 1979. Transactions are identified by three-digit numbers: 850 Purchase Order, 855 PO Acknowledgment, 856 Ship Notice (ASN), 810 Invoice, 820 Payment / Remittance, 997 Functional Acknowledgment (the CONTRL equivalent).

Releases are semi-annual and cumulative: 003040, 004010 (the most deployed historically in US retail), 005010 (mandated by HIPAA for US healthcare), 006020, 007030, 008010. Each version is a superset of the previous one; migration between versions is rare but heavy when it happens. The standard is shared across six sub-committees: X12M (Supply Chain), X12N (Insurance, including HIPAA), X12I (Transportation), X12F (Finance), X12C (Communications & Controls), X12J (Technical Assessment).

X12 is under strict ANSI X12 copyright; implementation guides (TR3) are paid. Ediverse documents the concepts and structures without redistributing paid specs — see the disclaimer.

cXML — Ariba and SAP Business Network

cXML (commerce eXtensible Markup Language) is Ariba's standard, acquired by SAP in 2012 and now the technical core of the SAP Business Network. Born in 1999, it is an XML standard covering six big transactional categories: Setup (ProfileRequest for capability discovery), Punchout (PunchOutSetupRequest, PunchOutOrderMessage for basket return), Commercial (OrderRequest, ConfirmationRequest, ShipNoticeRequest, InvoiceDetailRequest), Catalog (Supplier, Contract, Index), StatusUpdate, Quote.

Notable versions: 1.0 in 1999, 1.1.x between 2000 and 2004, 1.2.x since 2005, 1.2.069 in circulation today. cXML is documented via public DTDs published on xml.cxml.org; ediverse archives the six core DTDs (cXML.dtd, Fulfill.dtd, InvoiceDetail.dtd, Catalog.dtd, PaymentRemittance.dtd, Quote.dtd) under content/_sources/cxml/1.2.061/ with line-level citations for each assertion. cXML is the standard of choice as soon as a buyer operates on SAP Ariba, Coupa, Jaggaer or Ivalua with Business Network integration.

SAP OCI — punchout to SRM/Ariba

SAP OCI (Open Catalog Interface) is a punchout mechanism standardised by SAP: from a buyer system (SAP SRM, Ariba Buyer, other), a user "jumps" into a supplier's web catalogue, selects items, and the basket content is posted back as NEW_ITEM-<FIELD> values in an HTML POST. The mechanism is purely HTTP, not a message format per se — its simplicity and universality made its success.

Main versions: 2.0B (around 2000), 4.0 (around 2004, still widely deployed), 5.0 (around 2014, federated search). Dominant fields are NEW_ITEM-DESCRIPTION, NEW_ITEM-MATNR, NEW_ITEM-QUANTITY, NEW_ITEM-UNIT (referenced from UNECE Rec 20), NEW_ITEM-PRICE, NEW_ITEM-CURRENCY (ISO 4217), plus vendor and catalogue codes. OCI does not cover post-order — cXML, EDIFACT or X12 take over for the purchase order itself. OCI is therefore complementary to transactional standards, not a substitute.

UBL and PEPPOL — European e-invoicing

UBL (Universal Business Language) is OASIS's XML standard for business documents. UBL 2.1 (2013) then 2.4 define around twenty documents — Invoice, Order, OrderResponse, Catalogue, DespatchAdvice, ReceiptAdvice, CreditNote, ApplicationResponse — covering the entire order-delivery-invoice cycle under a unified semantics.

PEPPOL is the operational ecosystem that makes UBL usable in practice. OpenPEPPOL maintains business profiles (BIS — Business Interoperability Specifications) that constrain UBL for specific use cases. The most used profile is BIS Billing 3.0, which transposes the European norm EN 16931 (semantics of a European electronic invoice, 165 business terms + 150 rules) into usable UBL syntax. Alongside: BIS Catalogue 3.0, BIS Despatch Advice 3.0, BIS Order Only 3.0.

The regulatory stakes are central in 2026:

  • Belgium: PEPPOL BIS Billing 3.0 mandatory for B2B since January 1, 2026.
  • France: mandatory reception of all B2B invoices in September 2026 (PPF + accredited platforms), mandatory emission for large enterprises in September 2027. Allowed formats: Factur-X (CII), UBL, EDIFACT INVOIC.
  • Germany: mandatory reception since January 1, 2025 (XRechnung or ZUGFeRD).
  • Italy: FatturaPA via SdI already mandatory.
  • Spain: Facturae + national hub 2026-2027.
  • Poland: KSeF February 2026 then 2027.

Alongside pure UBL, the hybrid format Factur-X (FR) / ZUGFeRD (DE) combines a human-readable PDF/A-3 with a structured XML in Cross Industry Invoice (CII, UN/CEFACT) format; it is a different syntax from UBL but implements the same EN 16931 norm.

Synthetic comparison

Standard Year Maintainer Syntax Geographic dominance Sectoral dominance
EDIFACT 1987 UN/CEFACT (UNECE) Segments Europe, Asia, Latin America, Africa Retail, automotive, logistics, chemicals
X12 1979 ANSI ASC X12 Segments North America US retail, HIPAA healthcare, US transport
cXML 1999 Ariba / SAP XML Global E-procurement, B2B marketplaces
SAP OCI ~2000 SAP SE HTTP POST (HTML) Global Catalogue punchout into SAP/Ariba
UBL / PEPPOL 2004 OASIS UBL TC / OpenPEPPOL XML Europe + ~50 PEPPOL countries B2B/B2G e-invoicing

Decision tree

To orient the choice in front of a concrete integration project, follow the tree below:

  1. Is the flow a B2B/B2G invoice in Europe? → PEPPOL BIS Billing 3.0 (UBL or CII via Factur-X). No other viable option in the medium term, given converging national mandates.
  2. Does the flow go through SAP Ariba, Coupa, Jaggaer, Ivalua or another B2B marketplace? → cXML for transactions, OCI for catalogue punchout. The ecosystem dictates the standard.
  3. Is the partner in North America requiring an ANSI format? → X12 (version per partner: 004010 in retail, 005010 in HIPAA healthcare, 006020+ in migration).
  4. Is the partner in European automotive? → EDIFACT Odette subset over OFTP2. Renault, Stellantis, VW, BMW require this duo.
  5. Is the partner in European retail? → EDIFACT EANCOM subset (GS1) over AS2 or OFTP2.
  6. Otherwise EDIFACT remains the default option outside North America for transactional order-delivery-invoice flows. The directory pivots on D.96A by tradition, D.01B if recent, D.16B/D.21B when the buyer is modern.

Other standards worth knowing

  • RosettaNet — Partner Interface Processes (PIPs) for electronics and semiconductors; XML format. Official site now under GS1 US.
  • OAGi BODs — Business Object Documents, a generic XML application-integration framework maintained by OAGi.
  • TRADACOMS — historic UK retail standard, in decline but still present in some British distribution chains.
  • HL7 v2 (pipe-delimited, EDIFACT-like) and HL7 FHIR (modern REST/JSON) — healthcare outside US HIPAA.
  • SWIFT MT (legacy) and ISO 20022 / MX (modern) — financial messaging between banks. Global migration to ISO 20022 in progress.

Further reading