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

EDI 425 Rail Waybill Request

The X12 document a rail carrier uses to request a copy of a revenue or movement waybill it cannot locate from the origin or previous carrier.

Sent by
Rail carrier missing the waybill
Received by
Origin or previous rail carrier
Standard
ANSI ASC X12

What is an EDI 425?

The EDI 425 Rail Waybill Request is the ANSI X12 transaction set used to request a copy of a revenue or movement waybill from the origin or previous rail carrier. It is used only when the requesting carrier cannot locate the original transmission.

Without a waybill, a railroad cannot move a car correctly or collect its revenue. The request identifies the car and shipment so the other carrier can resend the waybill data, often as a 426 revenue waybill. It is a recovery tool for exceptions.

How the EDI 425 worksDiagram of the EDI 425 Rail Waybill Request. Rail carrier missing the waybill sends it to origin or previous rail carrier. It usually starts the exchange. It is usually followed by 426 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required ZT loop with ZT (Waybill Request Information). 0 optional loops are listed by their first segment.How the EDI 425 worksRail Waybill Request: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 425SENDERRail carrier missingthe waybillRECEIVEROrigin or previous railcarrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY426Rail Revenue Waybill997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code WTGS … GETransaction set 425ST … SEHEADINGRequired loop ZT · repeats up to 255ZTWaybill Request InformationBlue 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 425. Your trading partner's implementation guide adds its own requirements.
How the EDI 425 worksDiagram of the EDI 425 Rail Waybill Request. Rail carrier missing the waybill sends it to origin or previous rail carrier. It usually starts the exchange. It is usually followed by 426 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required ZT loop with ZT (Waybill Request Information). 0 optional loops are listed by their first segment.How the EDI 425 worksRail Waybill Request: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 425SENDERRail carriermissing thewaybillRECEIVEROrigin orprevious railcarrier997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY426Rail Revenue Waybill997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code WT (GS … GE)Transaction set 425 (ST … SE)HEADINGRequired loop ZT · repeats up to255ZTWaybill RequestInformationBlue 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 425. Your trading partner'simplementation guide adds its own requirements.

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

  • Requesting a missing movement waybill
  • Requesting revenue waybill data for billing
  • Recovering lost transmissions

Where it fits in the document flow

This document 425 Rail Waybill Request
Usually followed by 426 Rail Revenue Waybill997 Functional Acknowledgment

Structure

Mandatory segments in the 425 (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
  • ZT
  • SE

Practical example

The 425 in practice

A car arrives at a railroad's yard from a connecting carrier, but no waybill was received. The yard cannot route the car, so the railroad sends the previous carrier a 425 identifying the car and requesting the waybill. The previous carrier resends it, and the car continues on its way.

Implementation

Implementation considerations for the 425

  • Use the request only when the original cannot be found.
  • Identify the car and shipment precisely.
  • Investigate why waybills go missing in the first place.
  • Track each request until the waybill data is received.

How ECOM helps

Automate the 425 with ECOM

Industry

Trucking and Transportation

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

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

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

Related transactions

Related transportation documents

All 80 transportation documents

Need help with the EDI 425?

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

Request a Demo Contact us