To start and identify an interchange of zero or more functional groups and interchange-related control segments
Canadian Pacific Railway X12 417 Rail Carrier Waybill Interchange
X12 417 (Rail Carrier Waybill Interchange) is the EDI transaction exchanged between Canadian Pacific Railway (Canadian Pacific Railway) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 43
- Loops
- 7
- X12 417
- All partners ↗
Transaction context
Where 417 Rail Carrier Waybill Interchange fits on Canadian Pacific Railway
- Canadian Pacific Railway channels
- 1 of 1
- Trading partners
- 2
- Channels
- 2
1 of Canadian Pacific Railway's 1 channel carries 417
partners across the Stacksync network trade 417
channels network-wide carry 417
Most common alongside 417
The X12 417 exchanges waybill data and movement instructions between railroads and is used by all Class I rail carriers in the United States and Canada. On interline moves the billing road forwards the waybill to the connecting carriers so each road can move the car and settle its share of the revenue. Railinc's waybilling guidance ties accurate waybill data directly to proper shipment movement, accurate freight bills, and dispute-free settlement between railroads. The origin or billing railroad sends the 417 to the connecting railroads in the route.
When it fires: A billing railroad creates or corrects a waybill for a shipment that moves over more than one railroad and must hand the waybill to the connecting carriers.
Common 417 rejection causes
- Origin (F9) or destination (D9) stations that are not the linehaul carrier's revenue-capable FSAC, for example billing to the serving switch carrier's station, break revenue waybilling.
- Junction settlement carriers not shown as the first or last carrier in the route segment, or their FSAC and city placed in the wrong F9/D9 elements.
- Route segments that do not match the registered interchange junctions between the named roads cause interline settlement disputes.
- Empty-car waybills whose origin or destination stations are not flagged as revenue-type locations in Railinc's Centralized Station Master violate industry waybilling guidance and disrupt the empty movement.
Specification summary
X12 417 Rail Carrier Waybill Interchange at the element level
The X12 417 specification defines 63 segments carrying 291 data elements, 76 of which are mandatory.
- Segments
- 63
- Data elements
- 291
- Mandatory elements
- 76
| Segment | Elements | Mandatory |
|---|---|---|
| ZC1 | 9 | 6 |
| BX | 9 | 3 |
| N9 | 6 | 1 |
| DTM | 4 | 1 |
| N7 | 5 | 1 |
| VC | 4 | 1 |
| N1 | 4 | 1 |
| N3 | 2 | 1 |
| M12 | 7 | 1 |
| M7 | 4 | 1 |
| N8 | 2 | 2 |
| F9 | 4 | 2 |
Key identifiers in 417
- Equipment Number
- Transaction Reference Number
- Transaction Reference Date
- Correction Indicator
- Standard Carrier Alpha Code
- Transportation Method/Type Code
- Transaction Set Purpose Code
- Shipment Method of Payment
Full segment guideline — 43 segments 7 loops · X12 417 Rail Carrier Waybill Interchange
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To transmit identifying numbers, dates, and other basic data relating to the transaction set
To transmit identification numbers and other basic shipment data
To transmit rail-specific shipment data
To transmit identifying information as specified by the Reference Identification Qualifier
To identify specific flight or voyage information for multimodal shipments
To specify pertinent dates and times
N7 Loop Repeat: 500
To identify the equipment
VC Loop Repeat: 36
To define motor vehicle identification and logistics
N1 Loop Repeat: 2
To identify a party by type of organization, name, and code
To identify the waybill and to specify the equipment used and the destination details
To identify the rail origin of the shipment
To identify the rail destination of the shipment
To specify the location of the named party
To specify the geographic place of the named party
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
To specify carrier and routing sequences and details
To specify special handling instructions in coded or free-form format
To specify mechanical protective service and ventilation instructions
LX Loop Repeat: 25
To reference a line number in a transaction set
To specify the line item in terms of description, quantity, packaging, and marks and numbers
L0 Loop Repeat: 25
To specify quantity, weight, volume, and type of service for a line item including applicable \"quantity/rate-as\" data
To communicate basis of pricing, such as contract number, quote number, or tariff number
LS Loop Repeat: 1
To indicate that the next segment begins a loop
LH1 Loop Repeat: 1,000
To specify the hazardous commodity identification reference number and quantity
To specify the hazardous notation and endorsement information
To specify the hazardous material shipping name and additional descriptive requirements
To identify a person or office to whom administrative communications should be directed
To transmit specific hazardous material reference numbers
This segment is used to specify a pro forma invoice and B13 Canadian Customs Export Declaration information, required by U.S. and Canadian customs
To indicate customs information
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To transmit in-bond information
To record seal numbers used and the organization that applied the seals
To transmit the transportation and distribution requirements of grain at Canadian ports
To transmit information contained on an export license
To uniquely identify the variable information required by government regulation covering the transportation of hazardous material shipments
To specify the Environmental Protection Agency (EPA) information relating to shipments of hazardous material
To specify additional Transport Canada requirements covering transportation of dangerous goods in Canada
To specify the placard information required by the second government agency when shipment is to cross into another country
To indicate that the loop immediately preceding this segment is complete
Trading partners
5+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
Canadian Pacific Railway Canadian Pacific Railway EDI 417 FAQ
Common questions about 417 Rail Carrier Waybill Interchange on the Canadian Pacific Railway channel.
What is X12 417 Rail Carrier Waybill Interchange?
X12 417 (Rail Carrier Waybill Interchange) is the EDI transaction set used to exchange rail carrier waybill interchange data. Canadian Pacific Railway's Canadian Pacific Railway channel requires it from trading partners.
Does Canadian Pacific Railway Canadian Pacific Railway require 417 for trading partners?
Yes, Canadian Pacific Railway (Canadian Pacific Railway) supports X12 417 Rail Carrier Waybill Interchange. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Canadian Pacific Railway 417 with Stacksync?
Most companies go live with Canadian Pacific Railway 417 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 417 on Canadian Pacific Railway?
On Canadian Pacific Railway, X12 417 is typically exchanged alongside 824 Application Advice, 404 Rail Carrier Shipment Information, 322 Terminal Operations And Intermodal Ramp Activity, 214 Transportation Carrier Shipment Status Message. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Canadian Pacific Railway EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
