X12 transaction code
X12 410 Rail Carrier Freight Details And Invoice
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 410
- Trading partners
- 4
Specification summary
X12 410 Rail Carrier Freight Details And Invoice at the element level
The X12 410 specification defines 32 segments carrying 224 data elements, 55 of which are mandatory.
- Segments
- 32
- Data elements
- 224
- Mandatory elements
- 55
| 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 |
- Invoice Number
- Shipment Method of Payment
- Date
- Net Amount Due
- Standard Carrier Alpha Code
- Transportation Method/Type Code
- Reference Identification Qualifier
- Equipment Number
Trading partners that support X12 410
4 partners, 4 channels. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 410 Rail Carrier Freight Details And Invoice
410 is used most heavily in logistics & transport.
The X12 410 carries a rail carrier's freight invoice: the detailed charges associated with a specific rail movement, including waybill references, equipment, origin and destination stations, line-item weights, rates, and total charges. Freight payers require it to audit rail charges against the governing price authority and to feed freight payment systems without rekeying paper invoices. 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. A rail movement is completed or reaches a billing milestone and the carrier rates the waybill and issues the invoice to the freight payer.
By industry
- logistics & transport 4 channels
FAQ
X12 410 questions
What is X12 410 Rail Carrier Freight Details And Invoice?
X12 410 (Rail Carrier Freight Details And Invoice) is an EDI transaction set defined by ANSI ASC X12 for exchanging rail carrier freight details and invoice between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 4 Stacksync trading partners support this code across 4 channels.
Which trading partners use X12 410?
4 Stacksync partners accept X12 410: Burlington Northern Santa Fe Railway (BNSF), Canadian National Railway, CSX Transportation, Union Pacific Railroad. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 410 with my ERP?
Stacksync handles the full X12 410 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
