X12

American National Standards Institute Accredited Standards Committee X12. The dominant EDI standard in North America since 1979.

What is X12?

X12 refers both to the ASC X12 committee and to the body of standards it publishes: a dictionary of transactions identified by three-digit codes (850, 810, 856, 837…), a vocabulary of segments and elements, and an envelope syntax (ISA/IEA, GS/GE, ST/SE). Where EDIFACT was conceived under the United Nations to cover international trade, X12 emerged from North American industry in 1979 to serve retail and rail freight, then expanded to health care, finance and federal administration.

Both standards address the same use cases — purchase order, acknowledgment, despatch advice, invoice — with a similar grammar of tagged segments and reserved delimiters. They differ in vocabulary (BGM versus ST/BEG, NAD versus N1, LIN versus PO1) and in geography: a transatlantic supply chain almost invariably crosses a gateway between the two standards.

Anatomy of a transaction

An X12 exchange nests three envelope levels: the interchange (ISA / IEA), the functional group (GS / GE) which bundles transactions of one type, and the transaction set itself (ST / SE). The tilde ~ terminates each segment, the asterisk * separates elements. A minimal 850 purchase order looks like this:

ISA*00*          *00*          *ZZ*SENDERID       *ZZ*RECEIVERID    *260513*1430*U*00401*000000001*0*P*>~
GS*PO*SENDERID*RECEIVERID*20260513*1430*1*X*004010~
ST*850*0001~
BEG*00*SA*PO78901**20260513~
N1*BY*ACME RETAIL*92*0001~
N1*ST*ACME WAREHOUSE*92*0042~
PO1*1*2*EA*9.99**UP*012345678905~
CTT*1~
SE*7*0001~
GE*1*1~
IEA*1*000000001~

The ISA envelope is fixed-length and carries the sender and receiver IDs, date, time, interchange control number, the test-or-production indicator, and the character that will itself terminate ISA — here >. The GS states the functional nature of the group (PO for purchase order, IN for invoice, HC for health care claim) and the X12 release in use (here 004010). The ST names the transaction set (850) and assigns it a control number. Each trailer (SE, GE, IEA) repeats a segment or transaction count, which makes arithmetic validation trivial.

Versions

X12 publishes its standards in versioned releases. The release appears in the GS08 segment of every functional group. The milestones every North American integrator meets:

Use cases

The X12 catalogue is split into industry subcommittees that group transactions by domain. The most-deployed in practice:

• Supply Chain (X12M) — purchase order 850, PO acknowledgment 855, ship notice/manifest 856 (ASN), invoice 810, functional acknowledgment 997, product activity data 852, planning schedule 830.
• Health care (X12N / HIPAA) — health care claim 837, benefit enrollment 834, services review information 278, property and casualty loss notification 272. Release 5010 is HIPAA-mandated since 2012 for every health-care transaction in the US.
• Finance (X12F) — payment order / remittance advice 820, consolidated service invoice 811, debit authorization 828, tax return acknowledgment 151.
• Transport (X12I) — air shipment information 104, shipping instructions 304, freight invoice 859, shipment and billing notice 857.
• Communications & controls — text message 864, electronic form structure 868, cryptographic service message 815.

Transaction catalogue

Structured list of transaction sets ediverse.io documents, grouped by X12 subcommittee. Each entry links to a detail page with envelope, structural segments, and common pitfalls.

Supply chain (X12M)

Finance and controls (X12F / X12C)

Mortgage and Real Estate (X12F)

Automotive (X12I)

Transport (X12I)

Insurance (X12N — P&C, Life)

Healthcare (X12N / HIPAA)

Acknowledgments and controls

Tools

To explore X12 in practice:

• X12 Parser — tokenisation and inspection of ISA/GS/ST envelopes, 100% client-side (publication in progress).

Further reading

Public official sources we reference without copying:

• x12.org — the ASC X12 site: public transaction-set index, examples, and the catalogue of Implementation Guides to purchase.
• stedi.com/edi/x12, truugo.com and edi2xml.com — the editorial model ediverse.io follows: document the standards without redistributing the TR3s, building on the public pages and open-source fixtures for examples.
• For health care, cms.gov publishes HIPAA 5010 examples under an open US government license.