Rail basics

Rail Waybill: What's on It and Why It Matters at Audit Time

Published June 3, 2026

A rail waybill is the rail equivalent of an LTL Bill of Lading (BOL) — but it carries more data and more decisions. The 7-digit Standard Transportation Commodity Code (STCC), the Association of American Railroads (AAR) carmark and car number, the route across any junction, and the controlling tariff cite all live on the waybill. It is the first document a rail audit reads, because almost every billing dispute walks back to a single field on it. Your first audit with Eller Audit is free.

What's actually on a rail waybill

Most rail waybills I've read share one structural quirk: the fields that drive billing are not the fields that draw the eye. The shipper and consignee blocks take up the top third, but the STCC, the AAR carmark, and the route entries are the ones the audit reads first. A standard US waybill carries somewhere between 12 and 18 named fields, depending on whether the move is single-line or interchange.

• Shipper, consignee, and care-of party. Names, addresses, and rail-station identifiers (FSAC / SPLC codes) for origin and destination. Mis-coded SPLC is a quiet source of mis-routed billing.
• AAR carmark + car number. 2 to 4 letters of owner prefix plus up to 6 digits. The carmark pulls tare weight from UMLER. Wrong carmark, wrong tare, wrong net — and wrong rate.
• STCC commodity code. 7 digits. Drives the tariff rate. Replaced the older ICC Transportation Commodity Code (TCC) in 1962 and is now maintained by the AAR under 49 CFR 1090.
• Commodity description. The English-language description of the lading. Required to match the STCC. Mismatch is one of the most common waybill defects.
• Gross weight, tare, and net. Typically printed in pounds, sometimes in net tons (2,000 lb units). The weight basis under the tariff lives here.
• Route. Origin carrier, junction points, and destination carrier. Drives any junction settlement when two or more rails interchange the car.
• Tariff or contract reference. The controlling document for billing. A waybill without a tariff cite is a bill without authority.
• Special instructions, hazmat, and reference numbers. Purchase order, sales order, internal reference, and any UN/NA hazmat code for regulated lading.
• Charges section. Linehaul, fuel surcharge, switching, accessorials. On an electronic waybill, this is usually a pointer to the EDI 410 freight invoice rather than a printed line.

Electronic vs paper waybills

Most US Class I railroads — BNSF, Union Pacific (UP), CSX, Norfolk Southern (NS), CPKC, and Canadian National (CN) — moved to electronic waybill exchange via Railinc's industry network by roughly 2019, exchanging waybill data as the EDI 417 X12 transaction set. The freight invoice that follows the waybill is the EDI 410. A separate EDI 419 is the rate-request message. Paper waybills still exist for short-line interchange moves, for reciprocal-switching events where the line-haul rail hands a car to a switching carrier, and for any legacy lane where one party in the route hasn't onboarded to the Railinc network.

For an audit, the practical implication is that the source data lives in two places. The waybill data is in EDI 417, the billing is in EDI 410, and the two are matched against the tariff library and contract to see whether the bill reflects what was tendered. When a paper waybill exists alongside the electronic message, the paper version usually wins on interpretive disputes — it carries shipper signatures and any handwritten corrections that did not make it into the EDI feed.

Waybill vs LTL Bill of Lading vs freight invoice

The three documents are easy to confuse and constantly mis-cited in dispute correspondence. Each is created at a different moment, by a different party, and carries a different legal weight.

The waybill is the question. The invoice is the carrier's answer. The tariff and contract are the rules. An audit reads all four together — never the invoice alone.

Where waybill errors hide

After reading several thousand rail waybills against the bills that followed them, the same 5 failure modes account for almost all the recoverable overcharges that trace back to waybill data.

• Wrong STCC drives the wrong rate. A waybill that lists STCC 2812410 (sodium hydroxide solution) when the load is actually STCC 2812420 (sodium hydroxide dry) pulls a different tariff rate, often with a different minimum weight. The bill is internally consistent and still wrong.
• Wrong AAR carmark or car number means wrong tare. A typo in the carmark prefix pulls a different car's tare weight from UMLER. On a 286,000-lb gross-rated covered hopper, an 8-ton tare error rolls straight into the rated net weight and the rated charge.
• Junction settlement errors when two rails interchange. A waybill that names the wrong interchange point triggers a junction settlement against a different mileage band. The total bill looks normal; the split between the two roads is wrong, and on contracted lanes the shipper still pays the gap.
• Commodity description doesn't match the STCC. The English description says one thing, the STCC says another. Whichever the carrier's billing system chose to honor is the rate that posted — rarely the one the shipper intended.
• Shipper-applied vs carrier-corrected weight discrepancies. The waybill carries a shipper-applied weight, the carrier corrects it at an in-line scale, and the bill cites the carrier's number. The audit checks whether the carrier has a Railinc-approved scale ticket to back the correction.

Worked example: chemicals shipper, STCC misclassification on $19K–$28K per year

A US industrial chemicals shipper moves 8,500 hopper cars per year across BNSF and UP under a multi-lane contract. The shipping department generates rail waybills in their TMS and transmits them as EDI 417 messages to each carrier's Railinc interface.

STCC misclassification exposure: roughly 1.2% of cars ship with an STCC entry that doesn't match the actual lading or doesn't match the contract-rated STCC for that lane — usually a similar-but-not-identical code that rates at a higher tariff band. Average per-car variance: $185. That is 8,500 × 1.2% × $185 = $19K–$28K of disputable overbillings per year on STCC alone.

Recovery rate on STCC disputes runs 75–85% when the waybill + EDI 417 + contract are presented together. That is $15K–$22K recovered per year from a single waybill field. STCC is not the largest recovery bucket on a rail program, but it is the most preventable — the same misclassification ships every week until somebody catches it, and an audit catches it in the first 30 days.

What we can't tell from the waybill alone

The waybill is a record of what was tendered, not a record of what should have been billed. Two documents have to sit next to it before an audit can call a line right or wrong: the controlling tariff in effect on the date of shipment, and the private contract that overrides parts of the tariff for the lane. A waybill that looks perfectly clean against today's tariff can still be the source of a bad bill if the tariff version that controlled at tender was different.

A waybill line that just reads “STCC 2812410, 197,500 LB, Origin: BNSF Galveston, Destination: UP Geismar” is the question, not the answer. The answer is in the tariff that was in effect for that STCC on that route on that date, and the contract addendum that may have superseded it. The waybill is the starting point of the audit, not the conclusion.

Rail is also the mode most susceptible to legacy waybill data living on after the underlying contract has changed. A waybill template cloned in the shipper's TMS three years ago and never updated will still happily ship today, with a stale tariff cite that nobody reviews. AP doesn't catch it; an audit does.

How Eller Audit uses the waybill

We ingest EDI 417 waybill data alongside the EDI 410 freight invoice and match both against a current tariff library and the controlling contract. STCC, AAR carmark, route, and weight are the four fields we normalize first — they drive most of the cross-document disagreement. When a line has a defensible variance, we draft the dispute citing the waybill, the EDI 410, the tariff, the contract, and 49 USC 11706 for the overcharge claim, file it through the carrier's claims portal, and recover the overage. The engagement is performance-based: you pay a share of what we recover, and nothing on the lines that hold up. Most rail waybill-driven disputes are resolved inside the carrier's 60–90 day claims window.

Frequently asked questions

Related reading