EDIFACT (UN/EDIFACT)

UN/EDIFACT (United Nations Electronic Data Interchange for Administration, Commerce and Transport) is the international standard for electronic business document exchange developed under UN auspices and published by the UN Economic Commission for Europe (UNECE). In use since 1987, EDIFACT defines the syntax rules, message structures, and data elements that allow companies in different countries and industries to exchange structured business documents — purchase orders, invoices, despatch advices — without bilateral format negotiation. It is the dominant EDI standard in Europe, fulfilling the same role that ANSI X12 plays in North America. (edibasics.com, accessed 2026-07-28; commport.com, accessed 2026-07-28)

How it works

Syntax and file structure

An EDIFACT file is organised hierarchically. Data elements (the smallest unit) group into segments; segments form an ordered sequence called a message (e.g. ORDERS, DESADV, INVOIC); one or more messages are wrapped in an interchange. (ecosio.com, accessed 2026-07-28)

The envelope hierarchy is: Interchange envelope (UNB...UNZ) → optional Functional Group envelope (UNG...UNE) → Message envelope (UNH...UNT). UNB and UNH are mandatory; UNG is optional and rarely used in modern practice. (edi.ba; truugo.com, accessed 2026-07-28)

The UNA segment is optional and defines the separator characters when they differ from defaults. By convention, EDIFACT uses + as the data element separator, : as the composite sub-element separator, and ' as the segment terminator. Composite elements (two or more sub-elements combined into one field) are common in EDIFACT — a key difference from ANSI X12 where composite elements are rare. (ecosio.com; astera.com, accessed 2026-07-28)

UN/CEFACT approves two EDIFACT standard versions per year, identified by year + release letter, e.g. D24A or D24B (Directory 2024 release A or B). (commport.com, accessed 2026-07-28)

EDIFACT vs ANSI X12

Dimension	EDIFACT	ANSI X12
Geographic dominance	Europe, international	North America
Message codes	Alphanumeric (ORDERS, INVOIC, DESADV)	Numeric (850 PO, 810 Invoice, 856 ASN)
Envelope structure	UNB → UNG → UNH	ISA → GS → ST
Delimiters	+ : '	* : ~
Composite elements	Common	Rare

The two standards are not mutually compatible; companies with both European and US operations must support both with separate mapping configurations. (astera.com; gerloff.dev 2026, accessed 2026-07-28)

EANCOM — the retail and fashion subset

GS1 EANCOM is a constrained subset of UN/EDIFACT created specifically for the retail and consumer goods sector, subsequently adopted in healthcare and construction. (truecommerce.com/uk-en/faq/eancom/, accessed 2026-07-28)

EANCOM incorporates GS1 identification standards directly into message structures: Global Trade Item Numbers (GTIN), Global Location Numbers (GLN), and Serial Shipping Container Codes (SSCCs). This ensures product identification is unambiguous across trading partners. (support.gs1.org, accessed 2026-07-28)

EANCOM contains 46 message types covering the full commercial transaction lifecycle. It provides only the elements relevant to retail/GS1 users, omitting optional EDIFACT fields not needed by the sector. GS1 publishes maintenance releases approximately every two years; code lists can be updated up to four times per year. (as-of 2026-07-28) (gs1.org; support.gs1.org, accessed 2026-07-28)

Other industry-specific EDIFACT subsets include VDA (automotive), EDILEKTRO (electrical), and EDITEC (HVAC/plumbing). (ecosio.com, accessed 2026-07-28)

Key message types in retail and ecommerce supply chains

The core retail message flow covers the full order-to-cash and delivery cycle.

Order management:

• ORDERS — Purchase Order sent from buyer (retailer) to supplier, specifying products, quantities, and required delivery schedule. (TraceLink, accessed 2026-07-28)
• ORDRSP — Order Response sent from supplier back to buyer, confirming acceptance, rejection, or proposing changes to quantities and delivery dates. (i-effect.com, accessed 2026-07-28)
• ORDCHG — Purchase Order Change, used to amend an existing order mid-cycle.

Despatch and receiving:

• DESADV — Despatch Advice (Advance Ship Notice) sent by the supplier ahead of physical delivery, communicating shipment details including packaging, quantities, GTINs, pallet/package numbers, weights, dimensions, expiry dates, dock locations, and expected delivery date. Retailers use DESADV to prepare warehouse teams before a shipment arrives. The two most widely deployed DESADV versions in European retail are D96A and D01B. (as-of 2026-07-28) (TraceLink; Data Interchange, accessed 2026-07-28; EDICOM, accessed 2026-07-28)
• RECADV — Receiving Advice sent by the retailer to the supplier after physical receipt of goods, confirming what was received and reporting discrepancies in type, quantity, or packaging — enabling the supplier to adjust invoices accordingly. EDICOM identifies DESADV and RECADV as the most-used messages in the retail supply chain. (seeburger.com; edicomgroup.com, accessed 2026-07-28)

Financial:

• INVOIC — Invoice sent from supplier to buyer, enabling automated financial transaction processing and replacing paper invoice processes. (TraceLink, accessed 2026-07-28)
• REMADV — Remittance Advice sent from buyer to supplier communicating the exact amount and timing of an upcoming payment, enabling cash flow planning and account reconciliation. (ecosio.com, accessed 2026-07-28)
• CONTRL — Technical and functional acknowledgment. As a technical ACK it confirms receipt of an interchange; as a functional ACK it indicates acceptance or rejection and lists syntax errors, transforming EDI from a blind data exchange into a verified, auditable communication. (seeburger.com, accessed 2026-07-28)

Catalogue, inventory, and sales:

• PRICAT — Price/Sales Catalogue, communicating product and pricing information between trading partners.
• INVRPT — Inventory Report, communicating stock levels, incoming and outgoing movements, and location-level quantities from retailer to supplier. (EDI2XML, accessed 2026-07-28)
• SLSRPT — Sales Report, communicating POS or distribution-centre sales data (product identification, price, location, quantities for a period) from retailer to supplier or manufacturer. Used in Vendor Managed Inventory (VMI (Vendor-Managed Inventory)|VMI) programmes. (seeburger.com, accessed 2026-07-28)

Logistics:

• IFTMIN — Instruction to Despatch/Transport
• IFTSTA — Transport Status
• IFCSUM — Forwarding and Consolidation Summary (betteredi.com, accessed 2026-07-28)

Transmission protocols (separate layer)

EDIFACT defines the message format — what the document says and how it is structured. Transmission protocols define how that file moves between parties. The two layers are distinct and should not be conflated. (gerloff.dev 2026, accessed 2026-07-28)

Common transmission protocols used to carry EDIFACT files include AS2 (Applicability Statement 2) (most widely used for direct B2B, operates over HTTPS with encryption, digital signatures, and MDNs), SFTP/FTPS, Value Added Network (VAN)|VAN (hub-and-spoke intermediary), AS4, and REST API tunnelling.

Message Disposition Notifications (MDNs) confirm receipt of a file — but not that it was processed correctly in the receiving system. (gerloff.dev 2026, accessed 2026-07-28)

2026 relevance and coexistence with APIs and Peppol

The market trend in 2026 is toward hybrid coexistence rather than replacement. JSON and REST APIs are becoming the format for new integrations and platform-specific connections, but EDIFACT continues to run established enterprise supply chain B2B workflows. The practitioner rule of thumb: API for apps and newer integrations; EDI for legacy ERP-to-ERP connections. (gerloff.dev 2026; zenbridge.io 2025, accessed 2026-07-28)

The first 30–90 days of a new EDI trading partner connection typically generate the most support tickets, indicating that EDIFACT partner onboarding complexity (spec analysis, mapping development, connection setup, certificate exchange, testing, go-live) remains significant regardless of format. (gerloff.dev 2026, accessed 2026-07-28)

The German energy sector's MaKo 2026 initiative illustrates the coexistence model: EDIFACT messages (UTILMD, MSCONS, INVOIC) remain mandatory alongside a new AS4 transport layer (mandatory since April 2024) and JSON API processes (first binding process since June 2025), with the intention to replace EDIFACT step-by-step rather than via a big-bang cutover. This is a regulated-sector example and does not imply a retail deadline, but shows the structural migration pattern. (innobu.com 2025–2026, accessed 2026-07-28)

Peppol operates on a "connect once, reach everyone" model — suppliers connect to a Peppol Access Point and can exchange documents with any enabled partner without rebuilding integrations — contrasting with EDIFACT's point-to-point or VAN-brokered model. (truecommerce.com, accessed 2026-07-28)

Under EU e-invoicing mandates, alternative EDI formats including EDIFACT are permitted for invoicing only when both buyer and seller explicitly agree AND the format remains EN 16931-compliant; Peppol BIS 3.0 is the mandated default pathway in countries such as Belgium (from January 2026). (fiskaly.com 2025, accessed 2026-07-28)

Key terms

Term	Meaning
UNA	Optional EDIFACT service segment defining separator characters
UNB	Interchange Header — identifies sender, receiver, date/time, syntax version
UNH	Message Header — identifies the start of an individual EDIFACT message
EANCOM	GS1-defined retail/consumer goods subset of UN/EDIFACT
DESADV	DESpatch ADVice — advance ship notice
RECADV	RECeiving ADVice — goods receipt confirmation
CONTRL	Control message — technical/functional acknowledgment
D96A	EDIFACT directory release 1996 version A — one of the most widely deployed EANCOM DESADV versions in European retail
D01B	EDIFACT directory release 2001 version B — also widely deployed in European retail DESADV
MDN	Message Disposition Notification — AS2-level receipt acknowledgment