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 426 Rail Revenue Waybill

The X12 document that answers a request for a rail revenue waybill with movement, rate and charge information needed to collect revenue.

Sent by
Origin or previous rail carrier
Received by
Requesting rail carrier
Standard
ANSI ASC X12

What is an EDI 426?

The EDI 426 Rail Revenue Waybill is the ANSI X12 transaction set used to respond to a request for a rail revenue waybill. Revenue waybill information includes the movement, rates and charges needed to collect revenue from the paying party or parties.

On interline moves, each railroad's share of the revenue depends on the agreed rates and divisions. The revenue waybill gives a carrier the rating data it needs to bill its share or settle with the other carriers. It complements the movement waybill.

How the EDI 426 worksDiagram of the EDI 426 Rail Revenue Waybill. Origin or previous rail carrier sends it to requesting rail carrier. It usually follows 425. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: ZR (Waybill Reference Identification) and DTM (Date/Time Reference). 1 optional loops are listed by their first segment.How the EDI 426 worksRail Revenue Waybill: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS425Rail Waybill RequestEDI 426SENDEROrigin or previous railcarrierRECEIVERRequesting rail carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code RWGS … GETransaction set 426ST … SEHEADINGZRWaybill Reference IdentificationDTMDate/Time Reference+ 1 optional loop, starting with:BNXBlue 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 426. Your trading partner's implementation guide adds its own requirements.
How the EDI 426 worksDiagram of the EDI 426 Rail Revenue Waybill. Origin or previous rail carrier sends it to requesting rail carrier. It usually follows 425. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: ZR (Waybill Reference Identification) and DTM (Date/Time Reference). 1 optional loops are listed by their first segment.How the EDI 426 worksRail Revenue Waybill: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS425Rail Waybill RequestEDI 426SENDEROrigin orprevious railcarrierRECEIVERRequesting railcarrier997 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 RW (GS … GE)Transaction set 426 (ST … SE)HEADINGZRWaybill ReferenceIdentificationDTMDate/Time Reference+ 1 optional loop, starting with:BNXBlue 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 426. Your trading partner'simplementation guide adds its own requirements.

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

  • Providing revenue data to connecting carriers
  • Answering waybill requests
  • Supporting interline revenue settlement

Where it fits in the document flow

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

Structure

Mandatory segments in the 426 (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
  • ZR
  • DTM
  • BNX
  • N7
  • N8
  • F9
  • D9
  • N1
  • S1
  • R2
  • R2B
  • LX
  • L0
  • T1
  • SE

Practical example

The 426 in practice

A connecting railroad requests revenue data for a shipment it carried for part of its route. The origin railroad replies with a 426 giving the movement details, the rate authority, the charges and the paying party. The connecting railroad calculates and bills its share.

Implementation

Implementation considerations for the 426

  • Include the rate references needed to divide revenue.
  • Keep revenue data consistent with the original waybill.
  • Protect commercially sensitive rate information.
  • Respond to waybill requests promptly to avoid delays.

How ECOM helps

Automate the 426 with ECOM

Industry

Trucking and Transportation

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

Solution

Financial Document Automation

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

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 426?

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

Request a Demo Contact us