EDI Transaction Codes Explained

EDI transaction codes (or EDI document types) define the standard format for exchanging key business documents electronically. From purchase orders to invoices and shipping notices, each code serves a specific role in digital supply chains.

While ANSI X12 is primarily used in North America, many UK businesses use these formats when trading internationally. We also support EDIFACT formats widely used across Europe.

Looking for a complete list of EDI transaction codes? Here is every EDI document type you need to know.

Guide to ANSI ASC X12 EDI Transaction Sets

There are many electronic data interchange (EDI) transaction codes that correspond to information in business documents, such as purchase orders and invoices. These can be exchanged with your trading partners and other third parties using EDI. Each document is called a transaction set because it includes a set of data components in a very specific order and format. Keeping the order and format of the data consistent is what enables the receiving computer system to correctly interpret which component corresponds to the sender’s company name, which represents the invoice number, and so on.

Breaking Down a Transaction Set

Every EDI transaction set is made up of three key components:

1. Data Elements

These are the smallest pieces of information – like company name, item number, quantity, or price. Each EDI standard defines:

  • Data type (e.g., numeric, date, alphanumeric)
  • Allowed length (minimum/maximum)
  • Code values (e.g., currency codes)

2. Segments

A segment is a logical group of related data elements. For example, in an EDI 850 Purchase Order, a segment might include item number, quantity, unit, and price.

  • Segments begin with an ID (e.g., IT1 for item detail)
  • Elements are separated by a delimiter (typically an asterisk (*) in ANSI X12)
  • Segments can be mandatory, optional, or conditional

The EDI standard in use (most commonly ANSI in North America or EDIFACT elsewhere) defines:

  • The order of segments
  • Whether segments can repeat
  • Which segments are required for each transaction type

3. Envelopes

Envelopes wrap transaction sets for secure transmission:

  • Message envelope: Wraps an individual transaction
  • Group envelope: Wraps related transactions (e.g., multiple invoices)
  • Interchange envelope: Wraps all groups for the full transmission

Start and end pairs define each envelope type to ensure accurate delivery and processing.

Meeting Trading Partner Requirements

Many retailers and supply chain partners require EDI compliance and provide mapping specifications for the transaction sets they expect. These detailed EDI compliance requirements can span 100+ pages and define:

  • Required EDI documents (transaction sets)
  • Mandatory segments and elements
  • Code values and sequencing rules

Different partners require different sets, but no one expects all possible EDI documents. When onboarding a new partner, your EDI provider should supply or update the required mappings for you – making setup and ongoing compliance simpler.

TrueCommerce Supports ANSI ASC X12 EDI Codes for UK–US Trade

No matter which codes your partners require, TrueCommerce has you covered. Our web-based EDI platform:

  • Supports every ANSI ASC X12 transaction set
  • Handles mapping and compliance updates automatically
  • Integrates with your ERP, accounting, or inventory system
  • Automates backups and version updates – no manual work required

ANSI X12 is the standard EDI format used in the United States. It is commonly required by UK businesses trading with US partners. We also support EDIFACT messages, commonly used in Europe and the UK, including APERAK, DESADV, INVOIC, and more.

We make it painless to send and receive whatever transaction sets your trading partners require. Our web-based EDI software automates backups, eliminates the hassle of updates, and integrates with your accounting software.

Download the Full EDI Transaction Code Guide

Want a downloadable reference? This guide provides information on the ANSI ASC X12 EDI standard and the various documents that can be exchanged using EDI, including transaction sets in the following categories:

  • Order and Financial Series
  • Transportation Air and Motor Series (TAM)
  • Transportation Ocean Series (TOS)
  • Transportation Rail Series (TRS)
  • Warehousing Series (WAR)
Get the Complete EDI Code Guide (Free PDF)

Most Common EDI Codes

While there are hundreds of transaction sets, these are some of the most frequently used in supply chain and logistics:

Full List of EDI Transaction Codes

Here are some of the most widely used EDI transaction codes across industries:

  • Order and Financial Series 
  • Transportation Air and Motor Series (TAM) 
  • Transportation Ocean Series (TOS) 
  • Transportation Rail Series (TRS) 
  • Warehousing Series (WAR) 
  • APERAK Application error and acknowledgement message 
  • DELFOR Delivery schedule message 
  • DELJIT Delivery just in time message 
  • DESADV Despatch advice message 
  • INVOIC Invoice message 
  • INVRPT Inventory report message 
  • ORDERS Purchase order message 
  • RECADV Receiving advice message 
Get a Demo