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 224 Motor Carrier Summary Freight Bill Manifest

The X12 document a motor carrier uses to send multiple freight bills at summary level to a single payer.

Sent by
Motor carrier
Received by
Payer or freight payment provider
Standard
ANSI ASC X12

What is an EDI 224?

The EDI 224 Motor Carrier Summary Freight Bill Manifest is the ANSI X12 transaction set for sending multiple freight bills at summary level to a single payer. Rather than a full detail invoice per shipment, it lists the bills with their key references and amounts so the payer can pay them together.

The 224 suits relationships where the shipment detail is already known to the payer, for example through earlier shipment data, and only a payable summary is needed. Detailed invoices, where required, use the 210.

How the EDI 224 worksDiagram of the EDI 224 Motor Carrier Summary Freight Bill Manifest. Motor carrier sends it to payer or freight payment provider. 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: CF1 (Beginning Segment for Summary Freight Bill Manifest) and the required 0100 loop with CF2 (Summary Freight Bill Detail). 0 optional loops are listed by their first segment.How the EDI 224 worksMotor Carrier Summary Freight Bill Manifest: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 224SENDERMotor carrierRECEIVERPayer or freightpayment provider997 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 MAGS … GETransaction set 224ST … SEHEADINGCF1Beginning Segment for Summary Freight Bill ManifestRequired loop 0100 · repeats up to 9,999CF2Summary Freight Bill DetailBlue 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 224. Your trading partner's implementation guide adds its own requirements.
How the EDI 224 worksDiagram of the EDI 224 Motor Carrier Summary Freight Bill Manifest. Motor carrier sends it to payer or freight payment provider. 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: CF1 (Beginning Segment for Summary Freight Bill Manifest) and the required 0100 loop with CF2 (Summary Freight Bill Detail). 0 optional loops are listed by their first segment.How the EDI 224 worksMotor Carrier Summary Freight Bill Manifest:who sends it, where it fits and what thestandard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 224SENDERMotor carrierRECEIVERPayer or freightpaymentprovider997 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 MA (GS … GE)Transaction set 224 (ST … SE)HEADINGCF1Beginning Segment forSummary Freight BillManifestRequired loop 0100 · repeats upto 9,999CF2Summary Freight BillDetailBlue 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 224. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 224, 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 224 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 many shipments to one payer in a single document
  • Supporting consolidated payment of freight bills
  • Sending summary billing to freight payment providers

Where it fits in the document flow

This document 224 Motor Carrier Summary Freight Bill Manifest
Usually followed by 820 Payment Order/Remittance Advice997 Functional Acknowledgment

Structure

Mandatory segments in the 224 (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
  • CF1
  • CF2
  • SE

Practical example

The 224 in practice

A parcel and LTL carrier bills a retailer's freight payment provider daily. Instead of hundreds of detail invoices, it sends one 224 listing each freight bill number, ship date, shipper reference and amount. The payment provider matches the summary to its shipment records and pays the total, with exceptions held for review.

Implementation

Implementation considerations for the 224

  • Agree with the payer that summary billing is acceptable instead of detail invoices.
  • Make sure each listed bill can be traced to a shipment.
  • Reconcile totals and payments at the bill level.
  • Decide how disputes on individual bills are handled within the summary.

How ECOM helps

Automate the 224 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.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

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 224?

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

Request a Demo Contact us