Rail audit

Railinc UMLER: How Car Records Drive Your Bill

Published June 3, 2026

UMLER (Universal Machine Language Equipment Register) is the master equipment registry the rail industry runs on. If the UMLER record for your car carries the wrong tare weight, every bill that prices off net weight is wrong by the same number. The math inside the invoice is right; the input is stale. The audit catches it. Your first audit with Eller Audit is free.

What UMLER actually is

UMLER is the registry. Every Class I, regional, short-line, and private fleet that wants its equipment to interchange on the North American rail network has to register it with Railinc and keep the record current. The population sits at roughly 1.7 million railcars, plus about 25,000 locomotives, intermodal chassis, and Container-on-Flatcar (COFC) / Trailer-on-Flatcar (TOFC) containers. The exact count moves every quarter as cars are built, retired, scrapped, or rebuilt, but the order of magnitude is the same.

Railinc itself is the AAR's data subsidiary. Cary, NC. Around 700 people. It runs UMLER plus a stack of downstream products that depend on UMLER being right — CarMonitor for fleet visibility, Asset Health Strategic Intelligence (AHSI) for equipment condition, the interline settlement system that pays railroads for the foreign cars on their network. All of those products start from the UMLER record. If UMLER is wrong, the rest of the rail data layer inherits the error.

For a shipper, the practical reality is that you do not own UMLER and you do not maintain it — the railroad or private-fleet owner does — but you pay the bill that prices off it. That asymmetry is the whole reason this page exists.

What fields UMLER carries that affect billing

A UMLER record for a single railcar runs 50+ data fields across mechanical, dimensional, and regulatory categories. Not all of them touch billing. These do:

• Carmark + serial number. The car's reporting mark (BNSF 412998, GATX 110564, etc.). This is the key the bill uses to find every other field.
• Owner code. Identifies who Railinc bills for car-hire and who the railroad pays for foreign-car use under the interline settlement system. Wrong owner code, wrong settlement.
• Tare weight. The light weight of the empty car. Net-weight billing depends on this exactly.
• Load limit (LD LIMIT) and carry load weight (CLW). The legal maximums. Tariffs use these to determine whether a car is overweight and subject to a weight-bump rate.
• Inside dimensions. Length, width, height of the loading envelope. Drives cubic-capacity pricing on covered hoppers and boxcars.
• AAR mechanical designation. The 4-character car-type code (LO, XM, GS, FB, etc.). Tariffs frequently price differently by designation, and a wrong designation can route the car onto the wrong rate table entirely.
• Brake system data. Air brake type, equipment status. An out-of-service brake record can produce out-of-service or repair-track charges on a car that is actually fine.
• Restrictions and capabilities. HM-216 hazmat eligibility, interchange restrictions, route-specific exclusions. Drives whether a per-trip restricted-route surcharge is supposed to apply.
• Last inspection / rebuild date. Triggers car-hire credit adjustments and capacity ratings under AAR rules.

Any one of those fields, if wrong, can propagate to the invoice through the rate engine on the railroad's billing side. The carmark and serial pull the record; the record decides the rate; the rate prints on the bill.

How UMLER errors become bill errors

After reviewing several years of rail invoices against the corresponding UMLER records, four failure modes account for most of the recoverable overcharges. Each is small per-car. Each compounds across a fleet.

(a) Wrong tare weight → wrong net weight → wrong CWT rate. A covered hopper rebuilt with new draft gear gains 1,800 lb of tare. UMLER is not updated. Every subsequent move of that car at a per-100-lb (CWT) net rate of $1.85 overbills by ~$33 per car. Quiet. Per car, nobody catches it. Across 3,200 trips a year on that single car, it's roughly $1,056 a year, on one car. Multiply by a 400-car private fleet and the number is real.

(b) Wrong AAR designation → restricted-route surcharge that shouldn't apply. A car was reclassified from a general boxcar (XM) to a specialty-equipped boxcar (XP). The carmark didn't change; the AAR code did. The new code triggers a route-restriction surcharge in the railroad's rate engine because XP-coded cars need special handling. The car can physically run the route. The UMLER record says it can't. Surcharge prints.

(c) Outdated brake-system data → out-of-service or repair-track charges. Brake equipment is upgraded in the shop. The shop bills the upgrade. The UMLER record is not updated for 60 days. During that window, AAR rule-based billing flags the car for unscheduled inspection charges that wouldn't apply against a current record.

(d) Carmark or serial reassignment after rebuild not reflected in UMLER. A scrapped car's reporting mark is reassigned to a newly-built car of a different type. The new car runs under the old code until UMLER catches up. Every bill in that window prices the new car as the old car. Sometimes the new car is cheaper to run; sometimes it's more expensive. Either way, the bill is wrong.

Worked example: chemical shipper, ~$8,300 disputable per year on a single UMLER fault pattern

A US specialty chemicals shipper moves 8,500 cars per year across BNSF and UP under a multi-lane contract with quarterly tariff updates. Annual rail spend: $48M. A routine cross-check of the billed tare weights on each waybill against the corresponding current UMLER records turns up a tare-weight discrepancy on 0.8% of cars — about 68 cars per year — at an average $145 per-car overbilling.

That's $9,860 of disputable billings on the UMLER tare-weight fault pattern alone. Recovery rate runs 85% with the current Railinc record and the contract tariff in hand — ~$8,300 recovered per year for this one shipper on this one fault pattern. Small per-shipper. Compounds across categories.

The same shipper carries roughly three other UMLER fault patterns at similar magnitudes (AAR designation, brake data, carmark reassignment), bringing total UMLER-driven recovery into the $25K–$35K per year range. For Fortune 500 enterprise rail shippers moving 35,000+ cars per year across more lanes and more car types, recoverable UMLER-driven errors routinely run $50K to $120K per year — not the headline category, but real, and almost never caught by AP review or by the railroad's own billing audit.

How to verify UMLER data yourself

Three access paths exist, and most shippers use none of them:

• Railinc Customer Center login. The web-based portal. Subscription required. Once authenticated, the EquipmentInquiry tool returns the current UMLER record for any carmark + serial. Tare weight, LD LIMIT, AAR designation, brake data — all visible.
• EDI 161 equipment inquiry. The programmatic version. Submit a 161 message with a list of carmarks; receive a 162 (equipment inquiry advice) response with current UMLER fields. The integration that most large shippers should have but most don't.
• Asset Health Strategic Intelligence (AHSI). Railinc's downstream condition-monitoring product. Less directly tied to billing fields, but useful for catching brake-system and inspection-status discrepancies before they print on a bill.

The cost of subscription access is real but not enormous — in the low five figures per year for most shippers. The cost of not having access is the leakage above.

UMLER vs other rail equipment records: what's what

The acronym soup around rail equipment data gets confused often enough that it's worth a brief disambiguation. UMLER is one of several registers, and only one of them drives billing.

Registry	What it tracks	Touches the freight bill?
UMLER (Railinc)	Operational equipment data: tare, capacity, dimensions, mechanical specs, restrictions	Yes — directly. Net-weight rates, capacity surcharges, restricted-route fees all key off UMLER.
Mark Register (AAR)	Reporting-mark ownership: who owns the BNSF / GATX / TILX prefix	Indirectly. Drives interline settlement and car-hire payments, not the shipper's freight rate.
Equipment Trust Certificate	Legal ownership / lease record of the physical car	No. Financial instrument. Does not touch billing.
FRA Locomotive ID / Federal Railroad Administration records	Locomotive safety and inspection compliance	No. Regulatory only.

What your contract should say about UMLER

Most rail contracts are silent on UMLER. They cite the tariff for rate mechanics and the AAR Office Manual for inspection rules, and they leave the equipment-data layer assumed. That works until the data is wrong. Two clause patterns close the gap.

Tare-weight verification clause. “For shipments billed on a net-weight basis, the tare weight used in the calculation shall be the value carried in the Railinc UMLER record effective on the date of shipment. In the event of a discrepancy between the UMLER tare weight and a certified scale weight measured at origin, the certified scale weight shall control.” This pins the data source. Without it, the railroad can default to whatever its rate engine happens to have cached.

UMLER-discrepancy dispute carve-out. “Where Shipper can demonstrate, with the current Railinc UMLER record or a Railinc-approved scale ticket, that a billed charge is based on a UMLER field that does not reflect the actual condition of the equipment at the time of shipment, the charge shall be disputable through the carrier's standard claims process, without prejudice to the 49 USC 11706 overcharge claim statute.” This preserves your dispute right and names the evidence the carrier has to accept.

What we can't tell from the bill alone

A UMLER-driven overcharge does not announce itself on the invoice. The bill prints a tare weight, a net weight, and a rate. The math between those three is usually right. The question is whether the tare weight came from a current UMLER record or a stale one — and the bill does not say. The same goes for the AAR designation field. The surcharge line names the surcharge; it does not name the designation that triggered it.

That is why the audit needs the Railinc record alongside the bill. Without it, a UMLER fault looks identical to a correct charge. A line item that reads “NET WT BILL — 198,400 LB @ $1.85/CWT — $3,670.40” is not enough to dispute and not enough to approve. The bill is the question; the Railinc record is the answer.

The audit also can't tell, from the bill alone, whether the discrepancy is recent or chronic. A tare-weight error in UMLER on a single car survives for years across thousands of moves before someone notices. The bill that triggers the audit is rarely the bill that contains the largest overcharge; the largest overcharge is the cumulative variance across the entire history of moves on that car since the record went stale. Statute (49 USC 11706) caps the lookback at 3 years for overcharge claims against rail carriers.

How Eller Audit handles UMLER-driven errors

We maintain Railinc Customer Center access for our rail shippers and pull current UMLER records for every car that appears on a waybill. For net-weight-billed cars, we cross-check the billed tare against the current UMLER tare and against any available origin scale ticket. For AAR-designation-driven surcharges, we verify the current designation against the surcharge basis cited on the bill. For brake-system and restriction-driven charges, we confirm the underlying UMLER field is current as of the shipment date.

When the data layer doesn't match the bill, we draft the dispute citing the UMLER record, the controlling contract tariff, and 49 USC 11706, 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 UMLER-driven disputes resolve inside the carrier's 60–90 day claims window because the evidence — a current Railinc record — is unambiguous.

Frequently asked questions

Related reading