X12 transaction guide · Shipping and logistics

EDI 990 Response to a Load Tender

The X12 document a carrier sends to accept or decline a load tender received in an EDI 204.

Sent by: Motor carrier
Received by: Shipper, broker or 3PL
Standard: ANSI ASC X12

What is an EDI 990?

The EDI 990 Response to a Load Tender is the ANSI X12 transaction set a motor carrier sends to tell the tendering party whether it accepts or declines a load offered in a 204. It references the shipment identification number from the tender and the carrier's SCAC, and it can include a reason when a load is declined.

The 990 is short, but timing matters. Many tendering processes move the load to the next carrier if no response arrives within a set window, so carriers usually automate 990s from their transportation management system. A missing or late 990 is one of the most common causes of lost loads and tendering confusion.

How to read this diagram: the top row shows who sends the 990, 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 990 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

Accepting a load tender so the shipper can confirm the carrier
Declining a tender so the shipper can offer the load to another carrier
Confirming acceptance of updates to a previously accepted load

Where it fits in the document flow

Usually follows 204 Motor Carrier Load Tender

This document 990 Response to a Load Tender

Usually followed by 214 Transportation Carrier Shipment Status Message 210 Motor Carrier Freight Details and Invoice

Structure

Key segments in the 990

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 990; "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.

Segment	Name	What it carries	In X12 004010
B1	Beginning Segment for Booking or Pick-up/Delivery	Carrier SCAC, the shipment identification number from the 204, the date and the accept or decline code.	Required
N9	Reference Identification	Additional references, such as the carrier's own load number.	Optional, common
V9	Event Detail	Event details such as the date and time of the decision, where partners require it.	Optional, common
K1	Remarks	Free-form remarks, such as a reason for declining.	Optional, common

Example

Sample EDI 990

Carrier ABCD accepts (A) load LOAD123 on the tender date. A decline would use the decline code and may include a reason in a K1 remark.

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*990*0001~
B1*ABCD*LOAD123*20261020*A~
SE*3*0001~

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