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 · Acknowledgments

EDI 126 Vehicle Application Advice

The X12 document a vehicle manufacturer uses to tell a carrier the result of processing its transactions, or which payments are being released.

Sent by
Vehicle manufacturer
Received by
Rail or truck carrier
Standard
ANSI ASC X12

What is an EDI 126?

The EDI 126 Vehicle Application Advice is the ANSI X12 transaction set the vehicle manufacturer uses to notify a carrier of the result of processing the transactions received from the carrier during the previous day, of payments being released that day, or both.

Carriers report vehicle movements and services, and those reports drive payment. The application advice tells them which reports were accepted, which were rejected and why, and what will be paid, so carriers can correct errors and reconcile their receivables.

How the EDI 126 worksDiagram of the EDI 126 Vehicle Application Advice. Vehicle manufacturer sends it to rail or truck carrier. It usually follows 121. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required BVA loop with BVA (Beginning Vehicle Advice) and the required VAD loop with VAD (Vehicle Advice Detail). 0 optional loops are listed by their first segment.How the EDI 126 worksVehicle Application Advice: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS121Vehicle ServiceEDI 126SENDERVehicle manufacturerRECEIVERRail or truck carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code VAGS … GETransaction set 126ST … SEHEADINGRequired loop BVA · repeats up to 99BVABeginning Vehicle AdviceRequired loop VAD · repeats up to 99VADVehicle Advice 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 126. Your trading partner's implementation guide adds its own requirements.
How the EDI 126 worksDiagram of the EDI 126 Vehicle Application Advice. Vehicle manufacturer sends it to rail or truck carrier. It usually follows 121. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required BVA loop with BVA (Beginning Vehicle Advice) and the required VAD loop with VAD (Vehicle Advice Detail). 0 optional loops are listed by their first segment.How the EDI 126 worksVehicle Application Advice: who sends it, whereit fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS121Vehicle ServiceEDI 126SENDERVehiclemanufacturerRECEIVERRail or truckcarrier997 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 VA (GS … GE)Transaction set 126 (ST … SE)HEADINGRequired loop BVA · repeats up to99BVABeginning Vehicle AdviceRequired loop VAD · repeatsup to 99VADVehicle Advice 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 126. Your trading partner'simplementation guide adds its own requirements.

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

  • Reporting accepted and rejected carrier transactions
  • Advising payments being released to carriers
  • Supporting daily reconciliation

Where it fits in the document flow

Usually follows 121 Vehicle Service
This document 126 Vehicle Application Advice
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 126 (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
  • BVA
  • VAD
  • SE

Practical example

The 126 in practice

A truck carrier sent 400 vehicle service transactions yesterday. This morning the manufacturer sends a 126 accepting 395, rejecting five for unknown vehicle numbers, and listing the payments released today. The carrier corrects the five transactions and reconciles the payment.

Implementation

Implementation considerations for the 126

  • Process rejections daily and resend corrected transactions.
  • Reconcile released payments with expected amounts.
  • Map rejection codes to corrective actions.
  • Reference the original transactions precisely.

How ECOM helps

Automate the 126 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 acknowledgments documents

All 9 acknowledgments documents

Need help with the EDI 126?

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

Request a Demo Contact us