This transaction set enables motor carriers to submit a consolidated summary of freight billing and manifest information to shippers, receivers, or billing entities. A motor carrier transmits the 224 to provide an aggregated record of shipments, typically in response to billing inquiries or as part of regular freight settlement procedures. The transaction begins with the ST (Transaction Set Header) segment, which establishes the document type and control information, followed by the CF1 (Beginning Segment for Summary Freight Bill Manifest) segment, which identifies the carrier, billing period, and summary-level details. The core data is conveyed through one or more CF2 (Summary Freight Bill Detail) segments within a repeating loop, with each CF2 capturing individual shipment summaries or billing line items.

Consider a scenario where Midwest Logistics, a regional motor carrier, has completed deliveries for Superior Manufacturing over a two-week period. Midwest Logistics generates an X12 224 transaction containing multiple CF2 segments—one for each freight bill or shipment group—detailing shipment origins, destinations, weights, charges, and reference numbers tied to specific purchase orders or delivery tickets. Within each CF2 loop, optional L11 (Business Instructions and Reference Number) segments cross-reference the shipments to Superior Manufacturing’s internal tracking codes or freight bill identifiers, ensuring accurate reconciliation when Superior Manufacturing’s accounts payable team receives and processes the manifest for payment.