--- title: "EDI 410 Rail Carrier Freight Details and Invoice | Stacksync" description: "EDI 410 is the X12 Rail Carrier Freight Details and Invoice, used when rail transport charges are ready to reconcile." canonical: https://www.stacksync.com/edi/x12/410-rail-carrier-freight-details-and-invoice last_modified: 2026-09-29 --- X12 transaction code # EDI 410 Rail Carrier Freight Details and Invoice (X12 410) > 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 410 is the X12 Rail Carrier Freight Details and Invoice transaction set, used when rail transport charges are ready to reconcile. A rail carrier sends the 410 to the freight payer, which may be the shipper, the consignee, or a third party responsible for the charges. Standard X12 Code 410 Partner references 4 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 410 at a glance What the 410 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 410 Rail Carrier Freight Details and Invoice summary** | | | | --- | --- | | Document | X12 410 Rail Carrier Freight Details and Invoice | | Business record | Rail-freight payable | | Who sends it to whom | A rail carrier sends the 410 to the freight payer, which may be the shipper, the consignee, or a third party responsible for the charges. | | When it is sent | A rail movement is completed or reaches a billing milestone and the carrier rates the waybill and issues the invoice to the freight payer. | | Match on | Rail invoice, shipment reference and equipment | | Partner references | 4 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 417 Rail Carrier Waybill Interchange](https://www.stacksync.com/edi/x12/417-rail-carrier-waybill-interchange) | ### Key segments in an EDI 410 The business segments that appear in at least half of the 4 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 | | --- | --- | --- | --- | | B3B | Beginning Segment for Carrier's Invoice | To transmit identifying numbers, dates, and other basic data relating to the transaction set. | 4 of 4 | | N9 | Reference Identification | To transmit identifying information as specified by the Reference Identification Qualifier. | 4 of 4 | | N7 | Equipment Details | To identify the equipment. | 4 of 4 | | N8 | Waybill Reference | To identify the waybill and to specify the equipment used and the destination details. | 4 of 4 | | F9 | Origin Station | To identify the rail origin of the shipment. | 4 of 4 | | D9 | Destination Station | To identify the rail destination of the shipment. | 4 of 4 | | N1 | Name | To identify a party by type of organization, name, and code. | 4 of 4 | | N3 | Address Information | To specify the location of the named party. | 4 of 4 | | N4 | Geographic Location | To specify the geographic place of the named party. | 4 of 4 | | LX | Assigned Number | To reference a line number in a transaction set. | 4 of 4 | Stacksync connects EDI documents such as the X12 410 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 410 mapping and validation X12 410 Rail Carrier Freight Details and Invoice is used when rail transport charges are ready to reconcile. Preserve rail invoice, shipment reference and equipment so the rail-freight payable 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-freight payable** rail invoice, shipment reference and equipment | Define which combination of rail invoice, shipment reference and equipment identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the rail-freight payable** ID assigned by the receiving system and processing result | Match one invoice covering several cars to the correct shipments. Test revised charges without duplicating the previously posted payable. | | Check the processing result | **Processing status for the rail-freight payable** Original document reference and matching response | Reconcile the rail-freight payable 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 417 Rail Carrier Waybill Interchange](https://www.stacksync.com/edi/x12/417-rail-carrier-waybill-interchange) **rail waybill interchange:** rail shipment information passes between carriers. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when rail transport charges are ready to reconcile. Name the operational owner of the rail-freight payable and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map rail invoice, shipment reference 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-freight payable 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-freight payable processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 410 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic rail-freight payable 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-freight payable 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 417 Rail Carrier Waybill Interchange](https://www.stacksync.com/edi/x12/417-rail-carrier-waybill-interchange) - [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 410 Rail Carrier Freight Details and Invoice at the element level The X12 410 reference contains 32 segment entries and 224 data elements; 55 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 32 Data elements 224 Mandatory elements 55 **Segments with elements marked mandatory in this reference** | Segment | Elements | Mandatory | | --- | --- | --- | | B3B | 11 | 6 | | N9 | 4 | 1 | | N7 | 21 | 1 | | VC | 6 | 1 | | M7 | 4 | 1 | | M12 | 10 | 1 | | N8 | 2 | 2 | | F9 | 4 | 2 | | D9 | 4 | 2 | | N1 | 6 | 1 | | N2 | 2 | 1 | | N3 | 2 | 1 | Key identifiers in 410 - Invoice Number - Shipment Method of Payment - Date - Net Amount Due - Standard Carrier Alpha Code - Transportation Method/Type Code - Reference Identification Qualifier - Equipment Number ## Find your trading partner for X12 410 4 partners, 4 channels. Choose a channel to inspect its listed document reference and implementation context. - [Burlington Northern Santa Fe Railway (BNSF)](https://www.stacksync.com/edi/burlington-northern-and-santa-fe-railway-co) [Burlington Northern Santa Fe Railway (BNSF)](https://www.stacksync.com/edi/burlington-northern-and-santa-fe-railway-co/burlington-northern-santa-fe-railway-bnsf/x12-410-rail-carrier-freight-details-and-invoice) - [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-410-rail-carrier-freight-details-and-invoice) - [CSX Transportation](https://www.stacksync.com/edi/csx-transportation) [CSX Transportation](https://www.stacksync.com/edi/csx-transportation/csx-transportation/x12-410-rail-carrier-freight-details-and-invoice) - [Union Pacific Railroad](https://www.stacksync.com/edi/union-pacific-railroad) [Union Pacific Railroad](https://www.stacksync.com/edi/union-pacific-railroad/union-pacific-railroad/x12-410-rail-carrier-freight-details-and-invoice) Catalog breakdown ## Where X12 410 Rail Carrier Freight Details and Invoice appears in this catalog The largest groups of classified 410 catalog entries are in logistics & transport. ### By industry - logistics & transport 4 channels Partner entries with the most listed channels - [Burlington Northern Santa Fe Railway (BNSF)](https://www.stacksync.com/edi/burlington-northern-and-santa-fe-railway-co) - [Canadian National Railway](https://www.stacksync.com/edi/canadian-national-railway) - [CSX Transportation](https://www.stacksync.com/edi/csx-transportation) - [Union Pacific Railroad](https://www.stacksync.com/edi/union-pacific-railroad) FAQ ## EDI 410 questions ### What is an EDI 410? EDI 410 is the X12 Rail Carrier Freight Details and Invoice transaction set. Trading partners use it when rail transport charges are ready to reconcile. It carries the data for the rail-freight payable, and your system matches it on rail invoice, shipment reference and equipment. ### Who sends an EDI 410 and who receives it? A rail carrier sends the 410 to the freight payer, which may be the shipper, the consignee, or a third party responsible for the charges. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 410 sent? A rail movement is completed or reaches a billing milestone and the carrier rates the waybill and issues the invoice to the freight payer. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 410? Across 4 partner document references listed here, the business segments that appear most often include B3B (Beginning Segment for Carrier's Invoice), N9 (Reference Identification), N7 (Equipment Details), N8 (Waybill Reference), F9 (Origin Station), D9 (Destination Station). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 410 and EDI 404? The 410 carries the rail-freight payable and is used when rail transport charges are ready to reconcile. The 404 carries the rail shipment and is used when rail movement instructions are ready for carrier use. ### What should I map for X12 410? Start with rail invoice, shipment reference and equipment and the target rail-freight payable. 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 410 error handling? Match one invoice covering several cars to the correct shipments. Test revised charges without duplicating the previously posted payable. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 410? The directory on this page links 4 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)