EDI ANSI X12

What is EDI ANSI X12?

ANSI ASC X12 is the EDI standard that dominates electronic business document exchange across North America. It was chartered in 1979 by the American National Standards Institute, which created the Accredited Standards Committee X12 to build a single national format for electronic business documents. The standard is still developed and maintained today by X12, and it remains the format that most US and Canadian retailers, manufacturers, healthcare payers and logistics providers expect their trading partners to use. Where Europe standardised on UN/EDIFACT, North America standardised on X12.

Where is it used?

X12 appears wherever North American supply chains exchange documents electronically: retail and grocery, automotive, manufacturing, transport and logistics, insurance and healthcare. Its position in healthcare is unusual because it is mandated rather than merely conventional. Under HIPAA, US healthcare claims, eligibility checks and remittance advice must be exchanged using specific X12 transaction sets. For a supplier selling into the United States or Canada, X12 capability is very often a condition of trading rather than a nice to have.

What do EDI ANSI X12 documents look like?

Each X12 document is called a transaction set and is identified by a three digit number rather than a name. The ones most suppliers meet first are the 850 purchase order, the 855 purchase order acknowledgement, the 856 advance ship notice, the 810 invoice and the 997 functional acknowledgement, which confirms that a file arrived and was structurally valid.

Inside the file, data sits in a nested set of envelopes. The ISA and IEA segments open and close the interchange, GS and GE group related transaction sets together, and ST and SE mark the start and end of each individual document. Within those envelopes the information is carried in segments built from delimited data elements. The result is compact and quick for machines to read, and close to unreadable at a glance. A purchase order does not look like a purchase order until something translates it.

How is X12 different from EDIFACT?

The two standards solve the same problem with different vocabularies. X12 numbers its documents, so a purchase order is an 850 and an invoice is an 810, while EDIFACT names them, so the same documents become ORDERS and INVOIC. The envelope structures differ, the delimiters differ, and the versions are written differently as well: X12 releases look like 004010 or 005010, whereas EDIFACT uses directory names such as D96A or D01B. A business trading on both sides of the Atlantic often needs both, which is the usual reason companies end up needing translation rather than a single fixed format. TRADACOMS, the older UK retail standard, is a third variation on the same idea, and our guide to EDI standards sets out how the main formats relate to each other.

Do I really need to know EDI ANSI X12 in such depth?

No. Choosing XEDI as your cloud EDI provider means you never have to work at the segment and element level. Our platform translates incoming X12 transaction sets into clear documents that look like the orders and invoices you already recognise, and turns your outbound data back into the exact version and structure each trading partner has asked for. We handle the version differences, the envelope rules and the acknowledgements, so meeting your partner’s specification is our responsibility rather than yours.

Sources and further reading

The references below support the standards, compliance and technical concepts discussed in this guide.

• X12 EDI standards Official X12 standards body for North American EDI transaction standards.
• X12 transaction sets The published list of X12 transaction sets and the numbers that identify them.
• American National Standards Institute The standards body that accredits the ASC X12 committee.
• CMS administrative simplification transactions US guidance on the X12 transaction standards mandated for healthcare.