EDI: Formats & Standards

UNB/UNH EnvelopeEDIFACT

The EDIFACT equivalent of the X12 ISA/GS envelope. UNB (Interchange Header) identifies the sender and receiver. UNH (Message Header) identifies the message type. Correct UNB/UNH configuration is required for EDIFACT document routing and acknowledgment.

Why UNB/UNH Envelope (EDIFACT) matters in B2B integration

UNB/UNH Envelope (EDIFACT) is part of the edi: formats & standards vocabulary that operators, IT leaders, and integration architects use when scoping ecommerce, ERP, EDI, and fulfillment projects. APIWORX integrates 200+ systems across this landscape — if UNB/UNH Envelope (EDIFACT) touches your stack, we can help you connect it without custom code.

Talk to an integration architect

ANSI X12

The dominant EDI standard in North America, maintained by the Accredited Standards Committee X12. X12 documents use a structured segment-and-element syntax with fixed delimiters. Transaction sets are numbered (850, 856, 810) and versioned (4010, 5010). Required for most US retail, grocery, healthcare, and logistics trading relationships.

EDIFACTUN/EDIFACT

The international EDI standard developed by the United Nations, predominant in Europe, Asia, and global trade. EDIFACT uses a similar segment-based structure to X12 but with different message types (ORDERS, DESADV, INVOIC) and syntax rules. Organizations with both North American and international partners must support both standards.

X12 4010

The most widely deployed version of the ANSI X12 standard in retail and logistics. While technically superseded by 5010, many large retailers and trading networks still mandate 4010 compliance. Migration from 4010 to 5010 requires updated segment maps and acknowledgment handling.

X12 5010

The current version of the ANSI X12 standard, required for HIPAA EDI compliance and increasingly adopted in retail and logistics. 5010 introduced the 999 Functional Acknowledgment and tightened data element requirements compared to 4010.

XMLExtensible Markup Language

A human-readable, tag-based markup language widely used for B2B document exchange. XML is the basis for non-traditional EDI integrations — including cXML, xCBL, OAGIS, and custom supplier schemas. XML documents are larger than EDI flat files but easier to validate with XSD schemas and parse with standard libraries.

cXMLCommerce XML

An XML-based standard developed by Ariba (now SAP Ariba) for catalog, purchase order, and invoice exchange through eProcurement platforms. cXML is the native format of the SAP Ariba Network and is commonly required for suppliers selling to enterprise buyers using Ariba or Coupa.