New: Drop-in replacement for Change Healthcare APIs

EDI 426 Rail Revenue Waybill

Functional Group SR

X12I Transportation Subcommittee

This standard provides the format and establishes the data contents of the Rail Revenue Waybill Transaction Set within the context of an Electronic Data Interchange environment. This transaction set is used to respond to a request for a rail revenue waybill. Revenue waybill information includes movement, rates, and charges information required to collect revenue from the paying party or parties.


Max use
  1. To indicate the start of a transaction set and to assign a control number

  2. To transmit identity and reference information of the waybill

  3. To transmit identifying numbers, dates and other basic data relating to the transaction set.

  4. To transmit identification numbers and other basic shipment data

  5. BNX Loop Optional
    Repeat 1
    1. To transmit rail-specific shipment data

    2. To transmit identifying numbers and descriptive information as specified by the reference number qualifier

    3. To specify pertinent dates and times

    4. N7 Loop Mandatory
      Repeat 255
      1. To identify the equipment.

      2. To define motor vehicle identification and logistics.

      3. To specify the chassis equipment details in terms of identifying numbers, weights and ownership

      4. To transmit in-bond data for a master in-bond bill of lading

      5. To record seal numbers used and the organization that applied the seals.

      6. To specify carrier equipment.

    5. To identify the waybill and to specify the equipment used and the destination details

    6. To specify information about a specific event

    7. To identify the rail origin of this shipment.

    8. To identify the rail destination of this shipment.

    9. N1 Loop Mandatory
      Repeat 10
      1. To identify a party by type of organization, name and code

      2. To specify the location of the named party

      3. To specify the geographic place of the named party

      4. To identify a person or office to whom administrative communications should be directed

    10. S1 Loop Optional
      Repeat 6
      1. To identify a stop-off party

      2. To specify location details for a stop-off

    11. To specify carrier and routing sequences and details

    12. To allow the identification of multiple billing origins and methods of payment on shipments requiring multiple billings

    13. To specify special handling instructions in coded or free-form format

    14. To specify mechanical protective service and ventilation instructions.

    15. LX Loop Optional
      Repeat 25
      1. To reference a line number in a transaction set.

      2. To specify the line item in terms of description, quantity, packaging, and marks and numbers.

      3. To indicate that the next segment begins a loop

      4. LX Loop Optional
        Repeat 25
        1. To reference a line number in a transaction set.

        2. To specify quantity, weight, volume and type of service for a line item including applicable "quantity/rate-as" data.

        3. To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements

      5. To indicate that the loop immediately preceding this segment is complete

      6. To reference details of the tariff used to arrive at applicable rates or charge

      7. Identify basis for pricing authority for shipments moving on a contract

        L7A01 qualifies the remaining data elements in the segment.
    16. T1 Loop Optional
      Repeat 64
      1. To specify origin point and waybill references of movement to transit waybill point

      2. To specify lading description, including weight and rate details applying to associated T1 segment

      3. To specify transit inbound routing including equipment identifications for associated T1 and T2 segments

      4. To identify the transit inbound prior origin point and waybill reference of movement to point specified in T1 segment

      5. To transmit information in a free-form format relating to a specified transit sequence number

    17. To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items

    18. To identify an external reference.

    19. Identify basis for pricing authority for shipments moving on a contract

    20. R2B Loop Optional
      Repeat 15
      1. To identify routing and proportion detail for carriers participating in the route

        One R2B segment is needed for each line haul carrier participating in the route of the shipment.
        When used to convey a Statement of Difference the proportional amount (R2B03) and all divisions (R2C Segments) must be present for the road issuing the SD. For other roads in the route, only the proportional amount is required and the divisions are optional.
        R2B01 must be present and a valid rule 360 junction on all occurences after the first.
      2. To identify the basis for divisions detail for carriers partcipating in the route

        When used to convey a Statement of Difference all divisions must be present for the road issuing the SD. For other roads in the route, the divisions are optional.
      3. To identify miscellaneous charge detail for carriers participating in the route

        When communicating more than one Miscellaneous Charge send subsequent miscellaneous charges on additional R2D segments associated with a road's R2B segment.
    21. To indicate customs information

    22. To transmit the transportation and distribution requirements of grain at Canadian ports.

  6. To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.