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 · Shipping and logistics

EDI 204 Motor Carrier Load Tender

The X12 document a shipper or broker sends to offer a shipment to a motor carrier, with stops, dates and freight details.

Sent by
Shipper, broker or 3PL
Received by
Motor carrier
Standard
ANSI ASC X12
EDIFACT equivalent
IFTMIN

What is an EDI 204?

The EDI 204 Motor Carrier Load Tender is the ANSI X12 transaction set a shipper, broker or third-party logistics provider uses to offer a shipment to a motor carrier. It describes the load, including pickup and delivery stops, dates and times, equipment, weights, commodities, references and payment terms, so the carrier can decide whether to accept it.

The 204 starts the transportation document cycle. The carrier responds with a 990 to accept or decline, sends 214 status messages as the freight moves, and bills with a 210 freight invoice. Tenders can also be updated or cancelled with a new 204 using a different purpose code.

How the EDI 204 worksDiagram of the EDI 204 Motor Carrier Load Tender. Shipper, broker or 3PL sends it to motor carrier. It usually starts the exchange. It is usually followed by 990, 214 and 210. Inside the ISA, GS and ST envelopes, X12 release 004010 requires, in the heading: B2 (Beginning Segment for Shipment Information Transaction) and B2A (Set Purpose) and detail: the required 0300 loop with S5 (Stop Off Details). 6 optional loops are listed by their first segment.How the EDI 204 worksMotor Carrier Load Tender: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 204SENDERShipper, broker or 3PLRECEIVERMotor carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY990Response to a LoadTender214Transportation CarrierShipment Status Message210Motor Carrier FreightDetails and Invoice2 WHAT X12 RELEASE 004010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code SMGS … GETransaction set 204ST … SEHEADINGB2Beginning Segment for Shipment InformationTransactionB2ASet Purpose+ 2 optional loops, starting with:N1N7DETAILRequired loop 0300 · repeats up to 999S5Stop Off Details+ 4 optional loops, starting with:N1L5OIDN7Blue 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 004010 listing for the 204. Your trading partner's implementation guide adds its own requirements.
How the EDI 204 worksDiagram of the EDI 204 Motor Carrier Load Tender. Shipper, broker or 3PL sends it to motor carrier. It usually starts the exchange. It is usually followed by 990, 214 and 210. Inside the ISA, GS and ST envelopes, X12 release 004010 requires, in the heading: B2 (Beginning Segment for Shipment Information Transaction) and B2A (Set Purpose) and detail: the required 0300 loop with S5 (Stop Off Details). 6 optional loops are listed by their first segment.How the EDI 204 worksMotor Carrier Load Tender: who sends it, whereit fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 204SENDERShipper, brokeror 3PLRECEIVERMotor carrier997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY990Response to a Load Tender214Transportation Carrier Shipment StatusMessage210Motor Carrier Freight Details andInvoice2 WHAT X12 RELEASE 004010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code SM (GS … GE)Transaction set 204 (ST … SE)HEADINGB2Beginning Segment forShipment InformationTransactionB2ASet Purpose+ 2 optional loops, starting with:N1N7DETAILRequired loop 0300 · repeats upto 999S5Stop Off Details+ 4 optional loops, starting with:N1L5OIDN7Blue 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 X12004010 listing for the 204. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 204, to whom, and which documents usually come before and after it. The lower part shows what X12 release 004010 itself requires: the envelopes around the 204 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

  • Shippers tendering truckload or LTL shipments to contracted carriers
  • Brokers and 3PLs offering loads to their carrier networks
  • Updating or cancelling a previously tendered load

Where it fits in the document flow

This document 204 Motor Carrier Load Tender
Usually followed by 990 Response to a Load Tender214 Transportation Carrier Shipment Status Message210 Motor Carrier Freight Details and Invoice

Structure

Key segments in the 204

The segments most implementations use, described in plain language. The last column shows what X12 release 004010 itself requires: "Required" marks a segment the standard requires in every 204; "Optional, common" marks a segment the standard leaves optional, or that sits in an optional loop, but that implementations often use. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, makes some optional segments mandatory and restricts the values, and requirements can differ between releases. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

SegmentNameWhat it carriesIn X12 004010
B2Beginning Segment for Shipment InformationCarrier SCAC, shipment identification number and payment method.Required
B2ASet PurposeWhether the tender is original, an update or a cancellation.Required
L11Business Instructions and Reference NumberReferences such as purchase order, bill of lading or customer reference numbers.Optional, common
S5 loopStop Off DetailsEach stop with its sequence, reason (load or unload), party, address and dates.Required
L3Total Weight and ChargesTotal weight and, where used, agreed charges.Optional, common

Example

Sample EDI 204

An original tender (B2A 00) of load LOAD123 to the carrier with SCAC ABCD, prepaid. The load has a pickup stop (LD) and a delivery stop (UL), and L3 gives a gross weight of 20,000.

Illustrative data only, not tied to one X12 release or trading partner. The interchange (ISA/IEA) and functional group (GS/GE) envelopes are omitted for readability.

ST*204*0001~
B2**ABCD**LOAD123**PP~
B2A*00~
L11*PO123456*PO~
S5*1*LD~
N1*SH*Example Shipper~
S5*2*UL~
N1*CN*Example DC~
L3*20000*G~
SE*10*0001~
Reading a sample EDI 204, line by lineAnnotated sample EDI 204 with 10 lines. Notes explain the ST, B2, B2A, L11, S5, L3 and SE segments.Reading a sample EDI 204, line by lineEach numbered note explains the segment on that line. The data is illustrative.ST*204*0001~11Transaction Set Header. Opens the 204 and gives it a controlnumber, which SE repeats.B2**ABCD**LOAD123**PP~22Beginning Segment for Shipment Information. Carrier SCAC,shipment identification number and payment method.B2A*00~33Set Purpose. Whether the tender is original, an update or acancellation.L11*PO123456*PO~44Business Instructions and Reference Number. References suchas purchase order, bill of lading or customer reference numbers.S5*1*LD~55Stop Off Details. Each stop with its sequence, reason (load orunload), party, address and dates.N1*SH*Example Shipper~S5*2*UL~N1*CN*Example DC~L3*20000*G~66Total Weight and Charges. Total weight and, where used, agreedcharges.SE*10*0001~77Transaction Set Trailer. Closes the set with the number ofsegments, including ST and SE, and the same control number.Illustrative data only, not tied to one trading partner. Envelopes (ISA/GS) are omitted for readability.
Reading a sample EDI 204, line by lineAnnotated sample EDI 204 with 10 lines. Notes explain the ST, B2, B2A, L11, S5, L3 and SE segments.Reading a sample EDI 204, lineby lineEach numbered note explains the segment onthat line. The data is illustrative.ST*204*0001~Transaction Set Header. Opens the 204 andgives it a control number, which SE repeats.B2**ABCD**LOAD123**PP~Beginning Segment for Shipment Information.Carrier SCAC, shipment identification numberand payment method.B2A*00~Set Purpose. Whether the tender is original, anupdate or a cancellation.L11*PO123456*PO~Business Instructions and Reference Number.References such as purchase order, bill oflading or customer reference numbers.S5*1*LD~Stop Off Details. Each stop with its sequence,reason (load or unload), party, address anddates.N1*SH*Example Shipper~S5*2*UL~N1*CN*Example DC~L3*20000*G~Total Weight and Charges. Total weight and,where used, agreed charges.SE*10*0001~Transaction Set Trailer. Closes the set withthe number of segments, including ST and SE,and the same control number.Illustrative data only, not tied to one trading partner.Envelopes (ISA/GS) are omitted for readability.

The sample is the same one shown above, with a note beside each segment the first time it appears. Segment IDs are highlighted at the start of each line; the fields after them are separated by asterisks, and each segment ends with a tilde.

Expand diagram Download SVG

Avoid problems

Common 204 errors and how to prevent them

Missing or wrong stop details

Incomplete addresses or appointment times lead carriers to decline tenders or arrive at the wrong time.

Updates sent as new tenders

Changes should use the update purpose code so carriers modify the existing load instead of creating a duplicate.

No follow-up on unanswered tenders

Tenders without a 990 response need monitoring and re-tendering to keep freight moving.

Trading partners

Integration guides that include the 204

  • C.H. Robinson EDI integration
  • Caterpillar EDI integration
  • Hub Group EDI integration
  • J.B. Hunt EDI integration
  • Old Dominion Freight Line EDI integration
  • Ryder EDI integration
  • Schneider EDI integration
  • Starbucks EDI integration
  • XPO EDI integration

How ECOM helps

Automate the 204 with ECOM

Solution

Logistics Automation

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

Industry

Trucking and Transportation

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

Product

PRISM-SCV

Order lifecycle visibility, response monitoring, routed alerts and business-identifier search across your B2B transactions.

EDI 204 FAQs

What is an EDI 204 used for?

A shipper, broker or 3PL uses the 204 to offer a shipment to a motor carrier with all the details needed to accept and plan the load.

How does a carrier respond to a 204?

With a 990 response to a load tender that accepts or declines the load, followed by 214 status messages and a 210 invoice if accepted.

Can a 204 cancel a load?

Yes. The purpose code in the B2A segment indicates whether the tender is original, an update or a cancellation.

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

Related transactions

Related shipping and logistics documents

All 15 shipping and logistics documents

Need help with the EDI 204?

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

Request a Demo Contact us