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 · Catalogs and pricing

EDI 129 Vehicle Carrier Rate Update

The X12 document a carrier or vehicle manufacturer uses to send new freight rates, from a rate adjustment or as a proposal for new business.

Sent by
Carrier or vehicle manufacturer
Received by
Vehicle manufacturer or carrier
Standard
ANSI ASC X12

What is an EDI 129?

The EDI 129 Vehicle Carrier Rate Update is the ANSI X12 transaction set either a carrier or a vehicle manufacturer uses to transmit new freight rates, as the result of a rate adjustment or as a rate proposal for new business.

Vehicle freight is paid per vehicle by lane, often with adjustments for fuel and vehicle size. Exchanging rates electronically keeps the manufacturer's payment system and the carrier's billing aligned, so payments released after delivery match expectations. Rates may vary by vehicle type and distance.

How the EDI 129 worksDiagram of the EDI 129 Vehicle Carrier Rate Update. Carrier or vehicle manufacturer sends it to vehicle manufacturer or carrier. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: VR (Rate Origin), G62 (Date/Time) and the required RT loop with RT (Rate Destination) and RT1 (Rate Detail). 0 optional loops are listed by their first segment.How the EDI 129 worksVehicle Carrier Rate Update: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 129SENDERCarrier or vehiclemanufacturerRECEIVERVehicle manufactureror carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code VHGS … GETransaction set 129ST … SEHEADINGVRRate OriginG62Date/TimeRequired loop RT · repeats up to 99RTRate DestinationRT1Rate DetailBlue 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 008010 listing for the 129. Your trading partner's implementation guide adds its own requirements.
How the EDI 129 worksDiagram of the EDI 129 Vehicle Carrier Rate Update. Carrier or vehicle manufacturer sends it to vehicle manufacturer or carrier. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: VR (Rate Origin), G62 (Date/Time) and the required RT loop with RT (Rate Destination) and RT1 (Rate Detail). 0 optional loops are listed by their first segment.How the EDI 129 worksVehicle Carrier Rate Update: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 129SENDERCarrier orvehiclemanufacturerRECEIVERVehiclemanufacturer orcarrier997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code VH (GS … GE)Transaction set 129 (ST … SE)HEADINGVRRate OriginG62Date/TimeRequired loop RT · repeats up to99RTRate DestinationRT1Rate DetailBlue 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 X12008010 listing for the 129. Your trading partner'simplementation guide adds its own requirements.

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

  • Updating rates after an adjustment
  • Proposing rates for new lanes
  • Synchronizing rate tables between partners

Where it fits in the document flow

This document 129 Vehicle Carrier Rate Update
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 129 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • VR
  • G62
  • RT
  • RT1
  • SE

Practical example

The 129 in practice

A truck carrier wins new delivery lanes from a regional ramp. The manufacturer sends the carrier a 129 with the per-vehicle rates for each dealer zone and the effective date. Both companies load the rates, and later payments for those lanes match the carrier's expectations.

Implementation

Implementation considerations for the 129

  • State the effective date for each new rate.
  • Distinguish proposals from agreed rates.
  • Reconcile rates with the payments released.
  • Identify lanes with codes both parties use.

How ECOM helps

Automate the 129 with ECOM

Industry

Automotive

Schedules, ship notices, labels, self-billing and multi-plant routing for automotive suppliers.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Industry

Trucking and Transportation

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

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

Related transactions

Related catalogs and pricing documents

All 21 catalogs and pricing documents

Need help with the EDI 129?

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

Request a Demo Contact us