Skip to content
roadmark

Glossary

EDI 204: what a load tender is, what's in it and how to answer it

EDI 204 is the X12 load tender a shipper or broker sends a carrier. What it contains, a sample with its segments, the 990 reply and mistakes to avoid.

Definition

What is EDI 204?

An EDI 204 (X12 Motor Carrier Load Tender) is the electronic document a shipper or freight broker sends to offer a truckload to a carrier. It carries the shipment ID, each stop with its dates and times, the weight, the references and usually the rate. The carrier answers with a 990 to accept or decline it.

Also called Motor Carrier Load Tender and load tender

A 204 is where an EDI load starts. Your customer's system puts a load it wants hauled into a standard file and sends it to you, so nobody retypes stops, times or reference numbers from an email. X12, the standards body chartered by ANSI that publishes these documents, defines the 204 as the way a shipper or other party offers a truckload shipment to a carrier, with its schedule, equipment, commodities and shipping instructions.

When it's sent, and by whom

The shipper, or a broker acting for the shipper, sends a 204 when it wants a carrier to take a load. In practice:

  • A shipper tenders to a carrier from its routing guide, usually the first carrier for that lane. If that carrier declines or doesn't answer in time, the next one on the guide gets a 204.
  • A broker receives 204s from its customers and, once it picks a carrier, may send its own 204 to that carrier. One load can mean two 204s.
  • A change or a cancellation is another 204 for the same shipment ID, with a purpose code saying what it is (original, change or cancellation).

The tender often comes with a deadline for the answer. Miss it, and many shippers treat the load as declined and move to the next carrier.

What's in a 204

Every file travels inside an envelope (the ISA and GS segments) that says who it's from, who it's for and which X12 version it follows. Inside, the transaction set runs from ST to SE. These are the segments you'll meet most:

SegmentWhat it holds
B2The carrier's SCAC, the shipper's shipment ID and the payment method (PP prepaid, CC collect)
B2AThe purpose: 00 original, 01 cancellation, 04 change
L11References: PO, bill of lading, order or customer numbers
N1A party (bill-to, shipper, consignee), with N3 and N4 for its address
S5One stop: its sequence number and reason (CL complete load, CU complete unload), weight and quantity
G62A date and time for the stop, such as the earliest and latest pickup
L3Total weight and the charge
SEThe end of the set, with a count of its segments

Which segments are required, which codes are allowed and what goes in each field differ from one customer to the next. That's what their implementation guide is for.

A sample 204

A Monday-morning tender from Prairie Foods to Ashgrove Freight: 26 pallets from Mississauga to Joliet, picked up Tuesday between 06:00 and 08:00 and delivered between 14:00 and 15:00, at $4,215.00. The envelope is left out. The companies, IDs and figures are fictional, and the file is simplified.

ST*204*0001~
B2**ASHG**PF778201**PP~
B2A*00*LT~
L11*4500018821*PO~
N1*BT*PRAIRIE FOODS~
S5*1*CL*26000*L*26*PLT~
G62*37*20261020*I*0600~
G62*38*20261020*K*0800~
N1*SH*PRAIRIE FOODS DC~
N4*MISSISSAUGA*ON**CA~
S5*2*CU*26000*L*26*PLT~
G62*53*20261020*G*1400~
G62*54*20261020*L*1500~
N1*CN*JOLIET DC~
N4*JOLIET*IL**US~
L3*26000*G***421500~
SE*17*0001~

Read it top to bottom: B2 says the tender is for carrier ASHG, shipment PF778201, prepaid. B2A*00 makes it an original tender. Each S5 opens a stop, with the G62 lines giving its window and N1/N4 giving the place. L3 gives the 26,000 lb gross weight and the $4,215.00 charge (X12 amounts often carry two implied decimals, so 421500). SE*17 counts the 17 segments from ST to SE.

How it relates to the 990, 214 and 210

The 204 opens a conversation of four documents about the same load:

  1. 204: the shipper or broker offers the load.
  2. 990: the carrier accepts or declines it, echoing the 204's shipment ID.
  3. 214: the carrier reports status at each stop, with the same shipment ID.
  4. 210: the carrier bills the load, again quoting the shipment ID and the references from the 204.

The shipment ID in B2 is the thread that ties them together. If it's lost or retyped, the customer's system can't match the status or the invoice to its load.

Common mistakes

  • Treating the 204 as a booking. Nothing is booked until your 990 says so. Until then the load is an offer, and a 204 for the same shipment ID can change or cancel it.
  • Missing the response deadline. A tender that sits in a queue overnight is often a tender the shipper has given to someone else.
  • Answering with a 997 only. A 997 says the file arrived. It doesn't accept the load.
  • Dropping references. The PO and order numbers in L11 usually have to come back on the 214s and the 210. If they're not kept with the load, the invoice gets rejected weeks later.
  • Ignoring time zones. A window of 14:00 to 15:00 in Joliet is Central time. Mix that up with the pickup's Eastern time and the appointment is an hour off.
  • Missing changes and cancellations. A change arrives as a new 204 with B2A*04. Match it to the load by shipment ID, or you'll haul to the old address.

How Roadmark handles 204s

When a 204 arrives from a customer, Roadmark turns it into a load, priced at the contract rate, waiting for dispatch to accept. When dispatch accepts or declines, Roadmark sends the 990 straight away, before a truck is assigned. Brokers can work the other way too: when a load is tendered to a carrier by EDI, Roadmark sends the 204 to that carrier and takes its 990 back.

Each customer is set up as its own trading partner, from their implementation guide, and you run one real tender through before turning it on for everything. The EDI integration page covers the setup.

Where it fits in a load.

Four EDI documents carry a truckload from the tender to the invoice, in this order.
  1. 204

    EDI 204

    The shipper or broker offers the carrier a load.

    This page

  2. 990

    EDI 990

    The carrier accepts or declines the tender.

  3. 214

    EDI 214

    The carrier reports where the load is, stop by stop.

  4. 210

    EDI 210

    The carrier bills the load once it's delivered.

EDI 204: common questions

What is an EDI 204?

It's the X12 Motor Carrier Load Tender: the document a shipper or broker sends to offer a truckload to a carrier, with the shipment ID, stops, dates, weight, references and usually the rate. The carrier replies with a 990.

Who sends a 204, and who receives it?

The shipper, or a broker acting for the shipper, sends it. The carrier receives it. A broker can be on both ends: it receives 204s from its customers and sends its own 204s to the carriers it covers loads with.

Is a load booked once the 204 arrives?

No. A 204 is an offer. The load is the carrier's only after it sends a 990 accepting the tender, and the shipper can still change or cancel it with a later 204 for the same shipment ID.

What's the difference between a 204 and a 997?

The 204 is the tender itself. A 997 is a functional acknowledgment: it confirms a file arrived and could be read, and says nothing about taking the load. Accepting or declining is the 990's job.

Is the 204 used for LTL shipments?

X12 says the 204 isn't for LTL bills of lading or pickup notices. It's built for truckload tenders, so LTL carriers usually take shipments through other documents or their own APIs.

How does Roadmark handle an incoming 204?

It turns the tender into a load, priced at the contract rate, waiting for dispatch to accept. When dispatch accepts or declines, Roadmark sends the 990 straight away, before a truck is assigned.

Bring a customer's EDI guide. We'll walk a load through it.

Send us the implementation guide one of your customers gave you. In the call, you'll see how a 204 like theirs becomes a load in Roadmark, and the 990, 214s and 210 that go back.

  • Your customer's implementation guide
  • The IDs you trade under today
  • Beside your current TMS

Thirty minutes. No slides.

We use this to reply to your request. Privacy policy.