EDI fundamentals

X12 vs EDIFACT: differences between the two EDI standards

How ANSI X12 and UN/EDIFACT differ, where each is used, and how organizations trading globally support both.

2 min read · Updated October 19, 2026

The short answer

ANSI X12 and UN/EDIFACT are the two most widely used EDI standards. X12 dominates in North America and identifies documents by number, such as 850 for a purchase order. EDIFACT is the international United Nations standard used widely in Europe and Asia and names documents with six-letter codes, such as ORDERS. Both carry the same kinds of business documents with different syntax.

X12 and EDIFACT at a glance

CriteriaANSI X12UN/EDIFACT
Governing bodyAccredited Standards Committee X12United Nations (UN/CEFACT)
Primary regionsUnited States and CanadaEurope, Asia and international trade
Document namingThree-digit transaction set numbers, such as 850Six-letter message names, such as ORDERS
EnvelopeISA/IEA, GS/GE, ST/SEUNB/UNZ, optional UNG/UNE, UNH/UNT
Typical delimitersElement *, segment ~ (set in ISA)Element +, component :, segment ' (set in UNA)
Acknowledgment997 or 999CONTRL
Same purchase order, two syntaxesComparison of X12 and EDIFACT. Purchase order: 850 versus ORDERS. Interchange envelope: ISA to IEA versus UNB to UNZ. Group envelope: GS to GE versus optional UNG to UNE. Document envelope: ST to SE versus UNH to UNT. Delimiters are defined in the ISA segment versus the optional UNA segment. Sample segments: BEG*00*SA*PO123456**20261015~ versus BGM+220+PO123456+9 followed by an apostrophe.Same purchase order, two syntaxesHow X12 and EDIFACT package the same kind of business documentANSI X12Documents named by numberUN/EDIFACTMessages named by six lettersPurchase order850ORDERSInterchange envelopeISA … IEAUNB … UNZGroup envelopeGS … GEUNG … UNE (optional)Document envelopeST … SE (transaction set)UNH … UNT (message)Delimiters defined inThe ISA segmentThe optional UNA segmentTypical segmentBEG*00*SA*PO123456**20261015~BGM+220+PO123456+9'Both standards build documents from segments made of elements. The business content is the same; the names,envelopes and separators differ.
Same purchase order, two syntaxesComparison of X12 and EDIFACT. Purchase order: 850 versus ORDERS. Interchange envelope: ISA to IEA versus UNB to UNZ. Group envelope: GS to GE versus optional UNG to UNE. Document envelope: ST to SE versus UNH to UNT. Delimiters are defined in the ISA segment versus the optional UNA segment. Sample segments: BEG*00*SA*PO123456**20261015~ versus BGM+220+PO123456+9 followed by an apostrophe.Same purchase order, twosyntaxesHow X12 and EDIFACT package the same kindof business documentANSI X12Documents named bynumberUN/EDIFACTMessages named bysix lettersPurchase order850ORDERSInterchange envelopeISA … IEAUNB … UNZGroup envelopeGS … GEUNG … UNE (optional)Document envelopeST … SE (transactionset)UNH … UNT(message)Delimiters defined inThe ISA segmentThe optional UNAsegmentTypical segmentBEG*00*SA*PO123456**20261015~BGM+220+PO123456+9'Both standards build documents fromsegments made of elements. Thebusiness content is the same; thenames, envelopes and separatorsdiffer.

Read across each row to see how the two standards express the same idea. In the sample segments, X12 separates elements with * and ends segments with ~, while EDIFACT uses + and ends segments with an apostrophe.

Expand diagram Download SVG

Two standards, one purpose

Both X12 and EDIFACT define how business documents are structured so that trading partners’ systems can exchange them without custom formats for every relationship. They cover the same core processes, such as ordering, shipping, invoicing and payment, and both are maintained and versioned over time.

The differences are mostly about where they are used and syntax, not what they can express.

Where each standard is used

  • X12 is the default for companies trading in the United States and Canada, especially in retail, manufacturing, transportation, finance and healthcare. U.S. healthcare administrative transactions mandated under HIPAA also use X12.
  • EDIFACT is standard across Europe and in much of Asia, the Middle East and international trade, including automotive, logistics, customs and retail.

A company with both North American and European customers will often support both.

Structural differences

Both standards organize documents into segments (lines of related data) made up of elements (individual fields), separated by delimiters. In X12, delimiters are defined in the ISA envelope; a typical segment looks like BEG*00*SA*PO123456**20261015~. In EDIFACT, an optional UNA segment defines delimiters, and a segment looks like BGM+220+PO123456+9'.

Envelopes differ too. X12 uses ISA/IEA around the interchange, GS/GE around functional groups and ST/SE around each transaction set. EDIFACT uses UNB/UNZ for the interchange, optional UNG/UNE groups, and UNH/UNT around each message.

Equivalent documents

Business documentX12EDIFACT
Purchase order850ORDERS
Order response855ORDRSP
Order change860ORDCHG
Despatch advice / ship notice856DESADV
Invoice810INVOIC
Remittance advice820REMADV
Delivery forecast830DELFOR
Delivery just-in-time862DELJIT
Inventory report846INVRPT
Syntax acknowledgment997CONTRL

See the EDIFACT reference for a longer list.

Supporting both standards

A modern integration platform keeps one internal representation of each business document and maintains separate maps for X12 and EDIFACT partners. That way, adding an international customer means building a map, not a new process. Version differences, such as X12 4010 versus 5010 or EDIFACT D96A versus D01B, are handled the same way.

Frequently asked questions

Can one EDI platform handle both X12 and EDIFACT?

Yes. Modern translators support both standards, so the same platform can serve North American and international partners with separate maps.

Which standard should we use?

Your trading partners decide. North American retailers and manufacturers mostly use X12, while European and international partners often use EDIFACT.

Are there other EDI standards?

Yes. Examples include TRADACOMS in UK retail, VDA and Odette in European automotive, HL7 in healthcare data exchange and industry XML standards.

Have an EDI question we did not answer?

ECOM's integration specialists can review your partners, documents and systems and recommend next steps.