ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 107 — Request for Motor Carrier Rate Proposal

The shipper requests rates: lane, expected volume, freight characteristics, desired effective date. Replies expected in 106.

Purpose

The 107 starts the rate-negotiation cycle between a shipper (big consignor, 3PL) and one or more carriers. Specifies the lane (origin/destination), forecast volume (annual, monthly), freight type (general, refrigerated, hazmat), desired service window. Carriers reply with 106; the shipper accepts/refuses via 108.

Envelope structure

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

x12 example-107.x12 
ISA*00*          *00*          *ZZ*SHIPPERINC    *ZZ*ACMECARRIER   *260516*1330*U*00401*000000107*0*P*>~
GS*PR*SHIPPERINC*ACMECARRIER*20260516*1330*1*X*004010~
ST*107*0001~
BPR*00*RFP-2026-001*20260516~
N1*SH*SHIPPER INC*92*SHIPP~
N1*CA*ACME TRUCKING LLC*92*ACMETRK~
R4*O*UN*CHICAGO*IL*US~
R4*D*UN*DALLAS*TX*US~
QTY*1*500*LD~
L5*1*GENERAL FREIGHT*0~
SE*8*0001~
GE*1*1~
IEA*1*000000107~

Common segments

  • Header — ST, BPR (Beginning of Rate Request).
  • Parties — N1*SH Shipper, N1*CA Carrier.
  • Lane — R4 origin / destination.
  • Volume — QTY expected annual volume.
  • Cargo — L5 commodity description.
  • Summary — SE.

Common pitfalls

  • No time window: without DTM*191 (RFP Response Due), carriers do not know when to reply.
  • Generic commodity: "general freight" prevents precise pricing. Always specify density, value, sensitivity.
  • Volume without unit: 500 with no LD/MO/YR (loads/month/year) is ambiguous.

Documentation

The 107 code and the Request for 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.