X12 108 — Response to a Motor Carrier Rate Proposal

The shipper accepts, refuses, or counter-proposes the carrier rate. Closes the 107 → 106 → 108 cycle.

Purpose

The 108 closes the trucking RFP cycle: accept, reject, or counter. On accept, the rate is applicable on the lane at the stated effective date. On counter, a new 106/108 cycle starts. Once accepted, operational 204 (Load Tender) transactions use the agreed rate.

Envelope structure

The 108 travels inside the three X12 envelope levels (ISA/IEA, GS/GE with functional group PJ, and ST/SE). Didactic example in 004010:

ISA*00*          *00*          *ZZ*SHIPPERINC    *ZZ*ACMECARRIER   *260517*0900*U*00401*000000108*0*P*>~
GS*PJ*SHIPPERINC*ACMECARRIER*20260517*0900*1*X*004010~
ST*108*0001~
BPR*04*RFP-2026-001-RESP*20260517~
REF*BM*RFP-2026-001~
SC*AC*ACCEPTED~
RTE*FR*2.85*MI~
SE*5*0001~
GE*1*1~
IEA*1*000000108~

Common segments

• Header — ST, BPR.
• Reference — REF pointing the 106 being answered.
• Decision — SC Service Characteristics with accept/reject code.
• Counter rate — RTE if counter-proposal.
• Summary — SE.

Common pitfalls

• No REF to the 106: the reply is no longer correlated to the original proposal.
• Ambiguous SC code: use AC (Accept), RJ (Reject), CT (Counter) explicitly.
• Counter without new RTE: empty counter-proposal, rejected.

Related transactions

• 106
• 107
• 204
• X12 — Hub

Documentation

The 108 code and the Response to a Motor Carrier Rate Proposal name are public and listed at x12.org/products/transaction-sets. The full loops/qualifiers/code-lists structure is distributed by DISA via proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.