We Make EDI Integration Easy

Below you will essential information in regards to this EDI. If you have any specific questions about integrating your EDI with your ERP and eCommerce please reach out. Take advantage of our "start planning" feature to map out your integration needs. 

>>  Request a Demo
>>  Map Your Ideal Integration

What is a 426 - Rail Revenue Waybill document?

The 426 EDI document type contains information regarding the Rail Revenue Waybill Transaction Set (426) for use within the context of an Electronic Data Interchange (EDI) environment .Standard EDI formats include X12, ANSI, EDIFACT and its subsets.

What makes up the 426 - Rail Revenue Waybill document?

An EDI 426 - Rail Revenue Waybill document is organized into segment and data elements. A segment can contain at least one data element. Each data element contains a data field. Examples of data elements on the 426 EDI document includes, movement, rates, and charges information required to collect revenue from the paying party or parties. There are an infinite number of possibilities available for a company to include data on an 426 - Rail Revenue Waybill.

How is a 426 - Rail Revenue Waybill used?

The 426 Rail Revenue Waybill can be used to respond to a request for a rail revenue waybill.

How is a 426 - Rail Revenue Waybill processed?

An EDI solution is required to process the EDI documents received into an ERP or accounting system or into a readable format for manual entry. Each trading partner will have an EDI Implementation guide outlining the specific segments, data elements, values accepted, and the applicable business rules to be followed.

eBridge Connections has pre-built maps for all EDI transaction documents including 850 purchase orders, 810 invoices, and 856 advance shipping notices.