EDI 410 Rail Freight Details and Invoice: Auditing Carload Charges

A resin plant receives about forty carload invoices a week from two railroads, all as EDI 410 transactions that land overnight. Accounts payable matches each net amount to an open purchase order and pays inside terms. Six months later a freight audit finds that one lane was billed at tariff for three weeks after the contract renewal, and that the fuel line on every car used a mileage 6% longer than the route on the waybill.

Neither error was hidden. The contract number, the price authority, the billed miles and the per-mile fuel rate were all in the 410, element by element, and nobody recomputed them. A shipper that parses those elements and re-rates each car before approval catches most carload overcharges inside the payment cycle, rather than chasing refunds long after the fact.

• What this guide covers: where the 410 sits in the rail document chain, the header and line segments that matter, rate authority, per-mile fuel surcharge, demurrage billing, and how India's railway receipt differs.
• What it adds: an annotated 410 with a three-way total check, a worked re-rate in dollars and rupees, a timed failure trace and an onboarding checklist for a new railroad feed.

Where the 410 sits between the rail waybill and payables

The 410 is the railroad's freight bill for a movement it has already waybilled. In Canadian National's description, shipping instructions start the movement, a transportation charge is generated, and that charge is sent as an invoice. The invoice therefore inherits whatever the shipping instructions carried: if a purchase order number was not on them, it will not reliably appear on the 410 either.

• Overnight batches: CN's guide says it accumulates each day's invoices and transmits them between 00:00 and 04:00, seven days a week.
• Three invoice types: normal freight invoices, plus optional balance-due and adjusted invoices, each needing its own handling in payables.
• Charges left off: CN does not present ancillary or optional-service charges on the 410; other railroads publish their own scope, so each feed needs its own profile.

Ownership of the data around a 410 is split across logistics, IT and finance. The table sets out who keeps each reference the audit depends on and who approves a change to it.

Reading the header: B3B, N9, N7, N8, F9, D9 and R2

The header tells you which car moved, under which waybill, between which stations, and what the railroad wants paid by when. Its opening segment is B3B, Beginning Segment for Carrier's Invoice, rather than the B3 used on the motor-carrier 210, and the group header carries functional identifier IR. Our article on connecting 214 status to 210 invoice approval covers the truckload pattern; the elements below are the rail-specific ones.

• B3B invoice header: B3B01 invoice number, B3B02 payment method such as PP for prepaid, B3B03 billing date, B3B04 net amount due with two implied decimals, B3B05 due date, B3B06 the railroad's SCAC and B3B11 currency.
• N9 references: qualifiers such as CT for contract number, BM for bill of lading, CO for customer order and PA for price application date, which is the date the price must be valid on.
• N7 equipment: car initial and number, weight with qualifier, tare, equipment description code RR for railcar or CN for container, and the AAR equipment type.
• N8 waybill: waybill number and waybill date, the key that joins the invoice to the movement record.
• F9 and D9 stations: freight station accounting code, city, state or province and standard point location code for origin and destination.
• R2 route: the carrier SCAC and routing sequence, which decides which mileage table applies.

Line detail: L5 commodities, L0 weights and L1 charge codes

Each priced item sits in an LX loop: L5 names the commodity, L0 gives quantity and weight, and one or more L1 segments carry the money. L3 then totals the invoice. The L1 layout is where carload audit happens, because each line states its own rate, its rate basis and the charge, so every line can be recomputed independently of the others.

• L5 commodity: line number, description, and in L503 the seven-digit Standard Transportation Commodity Code with qualifier T.
• L0 weight: weight, qualifier such as N for net or E for estimated, lading quantity and packaging form such as CLD for carload or TKR for tank car.
• L1 rate and charge: L102 rate, L103 rate basis such as PC per car, PM per mile, PW percentage, CT charge based on percentage or MN minimum, and L104 charge with two implied decimals.
• L1 charge code: L108 identifies special charges such as ENS fuel surcharge, SWC switching, STR storage in transit, HAZ hazardous cargo or SOC stop-off; L117 holds the billed quantity, such as miles.
• PI price authority: qualifier TS for tariff number, the tariff agency and the tariff item number used to price the line.

The annotated example below is illustrative, modelled on the 4010 layout in a published railroad guide. It shows the three-way total check that should run before any 410 reaches payables: the L1 charges must sum to the L3 total, and the L3 total must equal the B3B net amount due.

ST*410*0417
B3B*7712045*PP*20261102*565452*20261116*ABCD*R****USD   # B3B04 = $5,654.52 due
N9*CT*K-55120                                           # contract on file, valid to 2026-10-31
N9*PA*20261028                                          # price application date
N7*ABCX*204517*196000*N*63500******RR*ABCD              # car ABCX 204517, net weight 196,000 lb
N8*318842*20261028                                      # waybill 318842 dated 2026-10-28
LX*1
L5*1*PLASTIC RESIN, IN BULK*28XXXXX*T                   # illustrative STCC
L0*1***196000*N***1*CLD
L1*1*5400.0000*PC*540000                                # line haul $5,400.00 per car
L1*1*.2100*PM*25452****ENS*********1212*MR             # fuel $0.21 x 1,212 miles = $254.52
PI*TS*4711***ABCD***2200                                # priced from tariff item, not contract
L3*196000*N*5400.0000*PC*565452
SE*14*0417

Checks before approval
  sum(L104) = 540000 + 25452 = 565452 = L305 = B3B04      -> totals tie
  expected line haul = contract K-55120 rate on PA date  = 498000
  expected fuel      = 0.2100 x 1140 route miles        = 23940
  expected total     = 521940 ; variance = 565452 - 521940 = 43512 ($435.12)

Rail freight invoice audit on an X12 410 starts with a three-way tie: the sum of L104 charges must equal L305 total charge and B3B04 net amount due, all in cents; a 410 that ties can still be wrong, so each L1 line is then re-rated against its price authority within a $1.00 tolerance.

Rate authority: tariff item, contract or quote on the shipment date

The first re-rating question is which price document governs the car. US rail common-carriage rates fall under 49 CFR Part 1300: a railroad must disclose rates and service terms on request and give 20 days' notice of increases to people who asked for them in the prior 12 months. Transportation under a contract authorised by 49 USC 10709 is outside Part 1300, so its price comes from the contract alone.

On the 410, that choice shows up in two places. An N9 with qualifier CT names a contract, and a PI segment names a tariff and tariff item. When the invoice carries a PI tariff item for a lane that should be under contract, either the contract lapsed on the price application date or the railroad's pricing system did not pick it up, and the variance is the gap between the two prices.

• Price application date: compare N9 PA with the contract's effective and expiry dates, not the invoice date in B3B03.
• Contract scope: confirm origin, destination, route, commodity and car type all fall inside the contract's lane definition.
• Tariff fallback: where no contract applies, compare the PI tariff item with the rate the railroad disclosed and check whether a 20-day increase notice reached you.
• Minimums: an L103 value of MN means a minimum charge was applied; check the minimum against the price document before accepting it.

Rail rate authority on an EDI 410 is set by the N9 CT contract or the PI tariff item in force on the N9 PA price application date; under 49 CFR 1300.1(c) contract moves under 49 USC 10709 are outside tariff disclosure rules, so an expired contract can silently reprice a car at tariff.

Fuel surcharge and mileage: rebuilding the per-mile line

A rail fuel line should be recomputable from a rate and a quantity. In its 2007 Ex Parte 661 decision, the Surface Transportation Board treated fuel surcharges computed as a percentage of the base rate as an unreasonable practice, because they did not track the fuel a move actually used. Many carload surcharges are therefore expressed as a rate per mile, which the 410 shows as L103 PM.

That gives the audit two independent checks. The rate in L102 should match the railroad's published fuel rate for the month that applies to the shipment, and the miles in L117 should match the route miles between the F9 and D9 stations for the R2 routing. In the example above, a 72-mile overstatement at $0.21 costs $15.12 per car, small alone but material across a year of cars.

Rail fuel surcharge checks on an EDI 410 rebuild each ENS line as the L102 per-mile rate times L117 billed miles; under the 2007 Surface Transportation Board Ex Parte 661 decision a surcharge computed as a percentage of the base rate is an unreasonable practice, and miles over 1% above route miles justify a hold.

The worked reconciliation below sets the US carload next to an Indian wagon-load, both with illustrative rates. In India the comparable checks are distance, chargeable weight, overloading and GST, because the bill is a railway receipt rather than a 410.

Demurrage comes on its own invoice, under its own data rules

Demurrage is a separate liability with a separate bill, and it should never be netted into the line-haul audit. Under 49 CFR 1333.1 it both compensates the railroad for cars held beyond free time and penalises undue detention. A customer can be charged only if the railroad gave actual written or electronic notice of the demurrage tariff before the cars were placed, unless a contract governs instead.

Class I railroads must put specific data on or with every demurrage invoice, and must offer the same data in a machine-readable, open format under 1333.5. That data is what makes a demurrage bill auditable against your own yard records, car by car.

• Car identity: reporting marks and number for each car, with loaded or empty status and the commodity if loaded.
• Movement context: waybill creation date, shipper, consignee or care-of party, and origin station and state.
• Clock events: original estimated arrival, receipt at last interchange, actual placement, constructive placement and its notification, any order-in time, and release.
• Credits and debits: the number of credits and debits attributed to each car, where an average agreement applies.
• Third-party sites: where a transload or terminal operator and a shipper jointly notify a Class I railroad, it must bill the shipper directly, starting no earlier than 20 days after the notice.

For how those charges should be booked once audited, see our guide to demurrage accounting treatment, which explains why detention is usually a period cost rather than part of inventory.

India's carload bill: railway receipt, chargeable weight and wharfage

X12 410 is a North American standard, and Indian Railways does not bill through it. The Indian counterpart is the railway receipt under Section 65 of the Railways Act 1989, issued when the consignor completes loading or when the railway accepts the goods. Indian Railways also lists electronic transmission of the receipt, eT-RR, among its freight policies on the FOIS RailSAHAY portal.

• Weight on the receipt: Section 65(2) makes the receipt prima facie evidence of weight and package count, but for wagon-loads not checked by the railway and so marked, the burden of proving weight shifts to the consignor or consignee.
• What freight includes: Section 2(17) defines freight as the charge for carriage, including transhipment charges.
• Demurrage and wharfage: Section 2(11) defines demurrage as the charge for detaining rolling stock beyond free time, and Section 30(2) lets the Central Government fix demurrage and wharfage rates and the conditions on which they apply.
• Overloading: Section 73 allows a punitive charge for loading beyond permissible carrying capacity, recovered before delivery, plus unloading and detention costs.
• Refund window: Section 106(3) bars a refund of overcharge unless notice reaches the railway within six months of payment or delivery, whichever is later.

Tax adds one more check. Transport of goods by rail carries 2.5% central tax under serial 9 item (i) of Notification 11/2017-Central Tax (Rate), a 5% total, and the September 2025 rate changes in Notification 15/2025 left that item untouched. The recipient's credit still depends on the conditions in Section 16(2) of the CGST Act being met.

A carload billed at tariff on a contract lane, hour by hour

Most 410 overcharges are not fraud; they are reference-data gaps that repeat until someone re-rates a car. The trace follows one illustrative invoice from receipt to payment, and then the same invoice under a re-rating rule.

1. 2 November, 03:12: the translator receives a 410 batch from railroad ABCD and returns a 997. Invoice 7712045 for car ABCX 204517, waybill 318842, shows B3B04 of $5,654.52.
2. 2 November, 06:40: the freight-pay engine matches waybill 318842 to shipment SHP-88214 and checks only that the total is within 5% of the planned freight. $5,654.52 against a planned $5,400 passes.
3. 3 November, 10:05: the ERP posts the payable to freight-in on the resin purchase order with no variance flag. The PI tariff item and the absent N9 CT segment are never read.
4. 16 November, 17:00: the invoice is paid on its B3B05 due date. Twenty-one similar cars on the lane follow over three weeks, each about $435 over contract.
5. Controlled version: at 06:40 the engine reads N9 PA 28 October, finds contract K-55120 in force, re-rates the line haul and fuel, and holds the invoice with a $435.12 dispute before the ERP posts anything.

Audit rules a freight-pay engine can enforce, and reviews for people

Almost every 410 check is deterministic once reference data is loaded; the human work is resolving why a reference is missing or wrong. The table assigns each task by what it actually involves, including where a model can help read a contract or a carrier dispute reply.

Onboarding a railroad's 410 feed: tests before the first live bill

A new 410 feed is ready when it can reject a bad invoice, not merely accept a good one. Railroads usually offer a test system, as CN's guide does, and the test plan should include deliberately broken invoices. Each line below is a pass-or-fail test; for the acknowledgment side, our guide to the EDI 997 functional acknowledgment covers reconciliation of accepted and rejected groups.

Rail is one invoice type among several, and more integration guides, including ocean and motor-carrier invoices, are on the logistics and supply chain hub. If you are scoping a freight-pay engine that re-rates 410 lines against contracts and fuel tables, you can share your requirements and we will map each check above to a test case.