972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Finance

EDI 223 Consolidators Freight Bill and Invoice

The X12 document a freight consolidator uses to send invoice and freight bill data for consolidated shipments.

Sent by
Freight consolidator
Received by
Shipper or bill-to party
Standard
ANSI ASC X12

What is an EDI 223?

The EDI 223 Consolidators Freight Bill and Invoice is the ANSI X12 transaction set a freight consolidator uses to send invoice and freight bill data to the responsible party. The freight bill services may be performed by the consolidator itself or by a motor carrier unrelated to it.

The 223 always carries the consolidator's invoice; it must not be used to send freight bill data on its own. Consolidators combine small shipments from several shippers into fuller loads, so the invoice allocates charges back to each shipment.

How the EDI 223 worksDiagram of the EDI 223 Consolidators Freight Bill and Invoice. Freight consolidator sends it to shipper or bill-to party. It usually starts the exchange. It is usually followed by 820 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B3A (Invoice Type) and B2A (Set Purpose). 3 optional loops are listed by their first segment.How the EDI 223 worksConsolidators Freight Bill and Invoice: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 223SENDERFreight consolidatorRECEIVERShipper or bill-to party997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY820PaymentOrder/Remittance Advice997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code MQGS … GETransaction set 223ST … SEHEADINGB3AInvoice TypeB2ASet Purpose+ 2 optional loops, starting with:N1N7DETAIL+ 1 optional loop, starting with:CSDBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 223. Your trading partner's implementation guide adds its own requirements.
How the EDI 223 worksDiagram of the EDI 223 Consolidators Freight Bill and Invoice. Freight consolidator sends it to shipper or bill-to party. It usually starts the exchange. It is usually followed by 820 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B3A (Invoice Type) and B2A (Set Purpose). 3 optional loops are listed by their first segment.How the EDI 223 worksConsolidators Freight Bill and Invoice: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 223SENDERFreightconsolidatorRECEIVERShipper orbill-to party997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY820Payment Order/Remittance Advice997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code MQ (GS … GE)Transaction set 223 (ST … SE)HEADINGB3AInvoice TypeB2ASet Purpose+ 2 optional loops, starting with:N1N7DETAIL+ 1 optional loop, starting with:CSDBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 223. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 223, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 223 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Billing shippers for consolidated freight
  • Invoicing charges allocated from a consolidated load
  • Passing through linehaul charges from an underlying carrier

Where it fits in the document flow

This document 223 Consolidators Freight Bill and Invoice
Usually followed by 820 Payment Order/Remittance Advice997 Functional Acknowledgment

Structure

Mandatory segments in the 223 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • B3A
  • B2A
  • N1
  • N7
  • CSD
  • OID
  • LX
  • SE

Practical example

The 223 in practice

A consolidator combines pallets from eight apparel vendors into full truckloads bound for a retailer's distribution center. It sends each vendor a 223 for its shipments, with the consolidated load reference, the vendor's share of the linehaul charge based on weight and the handling fee. The vendors' payables teams audit and pay the invoices.

Implementation

Implementation considerations for the 223

  • Explain how consolidated charges are allocated to each shipment.
  • Reference both the consolidated load and the shipper's own shipment identifiers.
  • Remember the 223 must carry invoice data, not just freight bill detail.
  • Audit allocations against the agreed consolidation rates.

How ECOM helps

Automate the 223 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related finance documents

All 58 finance documents

Need help with the EDI 223?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us