Skip to content

X12 EDI transaction sets

Explore 57 X12 document types and references for 822 trading partners. Find the message you need to map orders, shipments, invoices and other business records.

Choose a document by its business purpose

Start with the business records and responses you need. An order process can involve 850, 855, 856 and 810; a load-tender process can involve 204 and 990; a warehouse fulfillment process can involve 940 and 945. Confirm the required subset and sequence for the actual partner and channel.

Open a document below for its mapping identifiers, acceptance tests and related messages. Then choose the relevant partner and channel to review the document requirements for your account.

Start a field mapping workbook · Review production readiness

Primary reference: X12 document directory. Use the release specified by your trading partner.

X12 document reference entries

Click a transaction set for mapping guidance, reference segments and partner references.

FAQ

X12 EDI questions

What do X12 transaction-set codes identify?

X12 uses numeric transaction-set identifiers for business exchanges. For example, 850 is a purchase order, 855 is an order acknowledgment, 856 is a shipment notice and 810 is an invoice. The code identifies the document family; a version and partner implementation guide determine its field-level requirements.

How should I choose the documents for an EDI workflow?

Start with the business records and responses you need. An order process can involve 850, 855, 856 and 810; a load-tender process can involve 204 and 990; a warehouse fulfillment process can involve 940 and 945. Confirm the required subset and sequence for the actual partner and channel.

Does X12 map directly to EDIFACT?

Some messages serve related business purposes, such as X12 850 and EDIFACT ORDERS. Their syntax, field structures, qualifiers and version-specific rules differ. Compare the business data and partner guides before translating; related purposes do not make the messages interchangeable.

Connect EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.