--- title: "EDI 417 Rail Carrier Waybill Interchange | X12 | Stacksync" description: "EDI 417 is the X12 Rail Carrier Waybill Interchange, used when rail shipment information passes between carriers. See its key segments and mapping checks." canonical: https://www.stacksync.com/edi/x12/417-rail-carrier-waybill-interchange last_modified: 2026-09-29 --- X12 transaction code # EDI 417 Rail Carrier Waybill Interchange (X12 417) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md EDI 417 is the X12 Rail Carrier Waybill Interchange transaction set, used when rail shipment information passes between carriers. The origin or billing railroad sends the 417 to the connecting railroads in the route. Standard X12 Code 417 Partner references 2 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 417 at a glance What the 417 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 417 Rail Carrier Waybill Interchange summary** | | | | --- | --- | | Document | X12 417 Rail Carrier Waybill Interchange | | Business record | Rail waybill interchange | | Who sends it to whom | The origin or billing railroad sends the 417 to the connecting railroads in the route. | | When it is sent | 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. | | Match on | Waybill, originating carrier and equipment | | Partner references | 2 trading partners in this directory | | Related documents | [X12 404 Rail Carrier Shipment Information](https://www.stacksync.com/edi/x12/404-rail-carrier-shipment-information), [X12 410 Rail Carrier Freight Details and Invoice](https://www.stacksync.com/edi/x12/410-rail-carrier-freight-details-and-invoice) | ### Key segments in an EDI 417 The business segments that appear in at least half of the 2 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send. | Segment | Name | Purpose | Partner references | | --- | --- | --- | --- | | BX | General Shipment Information | To transmit identification numbers and other basic shipment data. | 2 of 2 | | BNX | Rail Shipment Information | To transmit rail-specific shipment data. | 2 of 2 | | N9 | Extended Reference Information | To transmit identifying information as specified by the Reference Identification Qualifier. | 2 of 2 | | DTM | Date/Time Reference | To specify pertinent dates and times. | 2 of 2 | | N7 | Equipment Details | To identify the equipment. | 2 of 2 | | N8 | Waybill Reference | To identify the waybill and to specify the equipment used and the destination details. | 2 of 2 | | N1 | Party Identification | To identify a party by type of organization, name, and code. | 2 of 2 | | F9 | Origin Station | To identify the rail origin of the shipment. | 2 of 2 | | D9 | Destination Station | To identify the rail destination of the shipment. | 2 of 2 | | N3 | Party Location | To specify the location of the named party. | 2 of 2 | Stacksync connects EDI documents such as the X12 417 to your ERP, CRM and databases with two-way sync. Read the [EDI overview](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/book-a-demo) to walk through your partner guide. Implementation guide ## X12 417 mapping and validation X12 417 Rail Carrier Waybill Interchange is used when rail shipment information passes between carriers. Preserve waybill, originating carrier and equipment so the rail waybill interchange in your business system stays connected to the original document. Use the version and implementation guide agreed with your trading partner to confirm required fields and responses. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | Match the business record | **rail waybill interchange** waybill, originating carrier and equipment | Define which combination of waybill, originating carrier and equipment identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the rail waybill interchange** ID assigned by the receiving system and processing result | Preserve originating references when a connecting carrier assigns its own number. Test a waybill correction after interchange and identify which record it supersedes. | | Check the processing result | **Processing status for the rail waybill interchange** Original document reference and matching response | Reconcile the rail waybill interchange with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. | ### How the related documents differ Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately. - [X12 404 Rail Carrier Shipment Information](https://www.stacksync.com/edi/x12/404-rail-carrier-shipment-information) **rail shipment:** rail movement instructions are ready for carrier use. - [X12 410 Rail Carrier Freight Details and Invoice](https://www.stacksync.com/edi/x12/410-rail-carrier-freight-details-and-invoice) **rail-freight payable:** rail transport charges are ready to reconcile. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when rail shipment information passes between carriers. Name the operational owner of the rail waybill interchange and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map waybill, originating carrier and equipment. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier. 3. #### Test failures before launch Run the failure cases in the mapping table against realistic rail waybill interchange data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate. 4. #### Track every document to completion Record transport delivery and document validation separately from successful rail waybill interchange processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 417 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic rail waybill interchange data. - Each submitted document can be traced through delivery, validation and processing in the receiving system. - Your team knows how to investigate and recover a rejected or timed-out rail waybill interchange without processing it twice. ### Related documents and resources - [X12 404 Rail Carrier Shipment Information](https://www.stacksync.com/edi/x12/404-rail-carrier-shipment-information) - [X12 410 Rail Carrier Freight Details and Invoice](https://www.stacksync.com/edi/x12/410-rail-carrier-freight-details-and-invoice) - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) Document structure ## X12 417 Rail Carrier Waybill Interchange at the element level The X12 417 reference contains 63 segment entries and 291 data elements; 76 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 63 Data elements 291 Mandatory elements 76 **Segments with elements marked mandatory in this reference** | 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 ## Find your trading partner for X12 417 2 partners, 2 channels. Choose a channel to inspect its listed document reference and implementation context. - [Canadian National Railway](https://www.stacksync.com/edi/canadian-national-railway) [Canadian National Railway](https://www.stacksync.com/edi/canadian-national-railway/canadian-national-railway/x12-417-rail-carrier-waybill-interchange) - [Canadian Pacific Railway](https://www.stacksync.com/edi/canadian-pacific-railway) [Canadian Pacific Railway](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-417-rail-carrier-waybill-interchange) Catalog breakdown ## Where X12 417 Rail Carrier Waybill Interchange appears in this catalog The largest groups of classified 417 catalog entries are in logistics & transport. ### By industry - logistics & transport 2 channels Partner entries with the most listed channels - [Canadian National Railway](https://www.stacksync.com/edi/canadian-national-railway) - [Canadian Pacific Railway](https://www.stacksync.com/edi/canadian-pacific-railway) FAQ ## EDI 417 questions ### What is an EDI 417? EDI 417 is the X12 Rail Carrier Waybill Interchange transaction set. Trading partners use it when rail shipment information passes between carriers. It carries the data for the rail waybill interchange, and your system matches it on waybill, originating carrier and equipment. ### Who sends an EDI 417 and who receives it? The origin or billing railroad sends the 417 to the connecting railroads in the route. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 417 sent? 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. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 417? Across 2 partner document references listed here, the business segments that appear most often include BX (General Shipment Information), BNX (Rail Shipment Information), N9 (Extended Reference Information), DTM (Date/Time Reference), N7 (Equipment Details), N8 (Waybill Reference). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 417 and EDI 404? The 417 carries the rail waybill interchange and is used when rail shipment information passes between carriers. The 404 carries the rail shipment and is used when rail movement instructions are ready for carrier use. ### What should I map for X12 417? Start with waybill, originating carrier and equipment and the target rail waybill interchange. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats. ### How should I test 417 error handling? Preserve originating references when a connecting carrier assigns its own number. Test a waybill correction after interchange and identify which record it supersedes. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 417? The directory on this page links 2 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires. ## Connect EDI to your business systems See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)