972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Transportation

EDI 410 Rail Carrier Freight Details and Invoice

The X12 document a rail carrier sends to the freight payer with the detailed charges for a rail movement.

Sent by
Rail carrier
Received by
Freight payer (shipper, consignee or third party)
Standard
ANSI ASC X12
EDIFACT equivalent
IFTMIN

What is an EDI 410?

The EDI 410 Rail Carrier Freight Details and Invoice is the ANSI X12 transaction set a rail carrier uses to provide detailed information about the charges associated with a rail movement. It is sent to the party paying the freight and itemizes charges such as line haul, fuel surcharges and accessorials.

Freight payers load 410 invoices into freight audit and payment processes, matching each charge to the shipment, the equipment and the contract rate before payment. The same references link each invoice back to the original tender.

How the EDI 410 worksDiagram of the EDI 410 Rail Carrier Freight Details and Invoice. Rail carrier sends it to freight payer (shipper, consignee or third party). It usually follows 404. It is usually followed by 997 and 820. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B3B (Beginning Segment for Rail Carrier's Invoice), the required N7 loop with N7 (Equipment Details), N8 (Waybill Reference), F9 (Origin Station), D9 (Destination Station), the required LX loop with LX (Transaction Set Line Number), L5 (Description, Marks and Numbers) and the required L0 loop with L0 (Line Item - Quantity and Weight) and the required L1 loop with L1 (Rate and Charges) and L3 (Total Weight and Charges). 4 optional loops are listed by their first segment.How the EDI 410 worksRail Carrier Freight Details and Invoice: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS404Rail Carrier ShipmentInformationEDI 410SENDERRail carrierRECEIVERFreight payer (shipper,consignee or thirdparty)997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment820PaymentOrder/Remittance Advice2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code IRGS … GETransaction set 410ST … SEHEADINGB3BBeginning Segment for Rail Carrier's InvoiceRequired loop N7 · repeats many timesN7Equipment DetailsN8Waybill ReferenceF9Origin StationD9Destination StationL3Total Weight and Charges+ required LX (LX) and 4 optional loops, starting with:N1S1PIT1Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 410. Your trading partner's implementation guide adds its own requirements.
How the EDI 410 worksDiagram of the EDI 410 Rail Carrier Freight Details and Invoice. Rail carrier sends it to freight payer (shipper, consignee or third party). It usually follows 404. It is usually followed by 997 and 820. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B3B (Beginning Segment for Rail Carrier's Invoice), the required N7 loop with N7 (Equipment Details), N8 (Waybill Reference), F9 (Origin Station), D9 (Destination Station), the required LX loop with LX (Transaction Set Line Number), L5 (Description, Marks and Numbers) and the required L0 loop with L0 (Line Item - Quantity and Weight) and the required L1 loop with L1 (Rate and Charges) and L3 (Total Weight and Charges). 4 optional loops are listed by their first segment.How the EDI 410 worksRail Carrier Freight Details and Invoice: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWS404Rail Carrier Shipment InformationEDI 410SENDERRail carrierRECEIVERFreight payer(shipper,consignee orthird party)997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment820Payment Order/Remittance Advice2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code IR (GS … GE)Transaction set 410 (ST … SE)HEADINGB3BBeginning Segment for RailCarrier's InvoiceRequired loop N7 · repeats manytimesN7Equipment DetailsN8Waybill ReferenceF9Origin StationD9Destination StationL3Total Weight and Charges+ required LX (LX) and 4 optional loops,starting with:N1S1PIT1Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 410. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 410, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 410 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Billing freight for rail shipments
  • Freight audit against contract rates
  • Allocating rail costs to products, plants or customers

Where it fits in the document flow

Usually follows 404 Rail Carrier Shipment Information
This document 410 Rail Carrier Freight Details and Invoice
Usually followed by 997 Functional Acknowledgment820 Payment Order/Remittance Advice

Structure

Mandatory segments in the 410 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • B3B
  • N7
  • N8
  • F9
  • D9
  • N1
  • S1
  • LX
  • L5
  • L0
  • L1
  • PI
  • T1
  • L3
  • SE

Practical example

The 410 in practice

After moving a producer's hopper cars, the railroad sends a 410 invoice for each movement with line haul, fuel surcharge and switching charges. The producer's freight audit system matches each invoice to the 404 tender and the contract rate, approves matching invoices for payment and flags one with an unexpected charge.

Implementation

Implementation considerations for the 410

  • Audit every charge against contract rates before approving payment.
  • Link invoices to shipments by equipment and waybill references.
  • Plan for invoices that cover moves tendered by other parties, such as consignees.

How ECOM helps

Automate the 410 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related transportation documents

All 80 transportation documents

Need help with the EDI 410?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us