New: Drop-in replacement for Change Healthcare APIs

EDI 426 Rail Revenue Waybill

Functional Group RW

X12I Transportation Subcommittee

This X12 Transaction Set contains the format and establishes the data contents of the Rail Revenue Waybill Transaction Set (426) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be 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.

Heading

Position
Segment
Name
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 information as specified by the Reference Identification Qualifier

  4. To specify pertinent dates and times

  5. To specify the currency (dollars, pounds, francs, etc.) used in a transaction

  6. To transmit information in a free-form format, if necessary, for comment or special instruction

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

  8. To transmit identification numbers and other basic shipment data

    BX05 contains the Standard Carrier Alpha Code (SCAC) of the original roadhaul carrier receiving the shipment.
  9. 1000 Loop Optional
    Repeat 1
    1. To transmit rail-specific shipment data

    2. To transmit identifying information as specified by the Reference Identification Qualifier

    3. To specify pertinent dates and times

    4. 1100 Loop Mandatory
      Repeat 500
      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 identify the scale type and the location and time a shipment is weighed

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

      6. To specify carrier equipment

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

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

    6. To identify additional station and waybill or station, or waybill information pertaining to revenue waybill

    7. To specify information about a specific event

    8. To identify the rail origin of the shipment

    9. To identify the rail destination of the shipment

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

      2. To specify additional names

      3. To specify the location of the named party

      4. To specify the geographic place of the named party

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

      6. To identify the individual billing segments within a movement when joint rail rates have been established between carriers but do not cover the entire movement

    11. 1300 Loop Optional
      Repeat 12
      1. To identify a stop-off party

      2. To specify location details for a stop-off

    12. To communicate basis of pricing, such as contract number, quote number, or tariff number

    13. 1400 Loop Mandatory
      Repeat 13
      1. To specify carrier and routing sequences and details

      2. 1410 Loop Optional
        Repeat 4
        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 260 Junction on all occurrences after the first.
          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.
        2. To identify the basis for divisions detail for carriers participating in the route

        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.
    14. To specify the route using a single code

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

    16. To specify mechanical protective service and ventilation instructions

    17. 1500 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. 1510 Loop Optional
        Repeat 25
        1. To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data

        2. To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001)

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

        4. To specify pertinent dates and times

        5. To communicate basis of pricing, such as contract number, quote number, or tariff number

        6. To specify condition restrictions or provisions applicable to the rate docket

    18. 1600 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 the 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 the point specified in T1 segment

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

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

    20. To identify the road issuing the freight bill and the amount for which the freight bill was issued

  10. 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.