Chicago freight accessorial charges to watch

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. In freight, that gap shows up fastest where lane volume is highest, and Chicago carries more of it than almost anywhere else in the country.

This guide covers what is specific to freight billing in and around Chicago: the accessorial charges the region's congestion and dock density make easy to justify and hard to verify, and what the current cost data says about why a surcharge schedule that was correct in January may not be correct now.

Executive Summary

Chicago is the busiest intermodal hub in the country, and that density is exactly what makes its accessorial charges hard to audit. A carrier serving a Chicago-area facility can apply a congestion or detention charge that would never survive scrutiny on a rural lane, because the traffic and dock queue that justify it are real. The problem is not that these charges are fake. It is that most contracts never define the threshold that triggers them, so the carrier's operations team decides case by case what "excessive wait" means, and AP has no rate card line to check it against.

The mechanism is cost-side too. Fuel and linehaul input costs have moved sharply this year, per BLS PPI data read September 6, 2026, and a fuel surcharge schedule that was accurate in January can already be running ahead of or behind the index it is supposed to track. On a high-frequency Chicago lane, that gap compounds fast because the invoice volume is higher than on thinner lanes elsewhere in a typical network.

What changes it is treating Chicago-area freight invoices as a distinct audit lane rather than folding them into a generic freight review: pulling the accessorial definitions out of the contract, checking the fuel surcharge formula against a current index, and testing detention and congestion charges against a stated, dated threshold rather than a carrier's word.

1. What is different about freight billing in Chicago?

Chicago combines the country's largest intermodal rail hub with some of its densest industrial dock activity, so carriers serving the area apply congestion, detention, and layover charges more readily than on lower-density lanes, and each one can be individually defensible. The audit problem is not that these charges are invented. It is that the contract rarely states the wait-time threshold, the rail-ramp cutoff, or the zone boundary the carrier is measuring against, so AP has no fixed line to test.

A carrier quoting a Chicago-area lane is pricing against real conditions: dock queues at distribution facilities, chassis shortages at intermodal ramps, and drayage windows that miss their target more often here than on a lane with lighter traffic. None of that is unique to any one shipper's contract. It is a property of the metro.

What is missing from most contracts is a stated definition of when a congestion or detention charge applies. "Reasonable detention" and "excessive dwell" are not numbers. Without a stated free time, a per-hour rate after that, and a dated reference for what counts as a delay caused by the facility versus the carrier, every invoice bearing one of these charges is effectively self-certified by the carrier that issued it.

This is the specific gap a Chicago-focused audit closes: pulling the actual accessorial definitions out of the contract or tariff, dating them, and testing invoiced charges against that text rather than against the carrier's own explanation on the invoice.

2. How much have freight input costs actually moved this year?

Per the US Bureau of Labor Statistics Producer Price Index, read September 6, 2026, the index for general freight trucking, long-distance truckload service (series PCU484121484121) stood at 195.575 in July 2026, up 8.1% year over year. The broader truck transportation of freight commodity index (WPU3012) reached 170.984, up 10.9% year over year. Both measure national trucking cost movement, not a Chicago-specific rate, but they establish the direction and scale a fuel and linehaul surcharge formula is.

These are national indices, not a Chicago lane rate. No fetched source in this research gives an origin-specific Chicago rate, and none is asserted here. What the indices do establish is the scale of movement a surcharge formula is supposed to be following.

A fuel or linehaul surcharge clause typically references an index and a lag period: the invoice this month should reflect the index reading from some stated prior period, not today's spot cost and not last year's contract rate. When the underlying index has moved 8% to 11% year over year, a surcharge formula with a stale reference point or an unstated lag produces a gap that compounds with every invoice, and a high-frequency Chicago lane produces more invoices per month to compound across than a thin one.

The audit question is not whether costs moved. They did, and the index confirms it. The question is whether the invoiced surcharge is calculating off the reference period the contract actually specifies.

3. Why does fuel surcharge drift show up faster on a high-volume Chicago lane?

Per BLS PPI data (WPU0571, gasoline, not seasonally adjusted, read September 6, 2026), the index reached 302.759 in July 2026, up 37.1% year over year, a sharper move than either trucking cost series. A fuel surcharge table tied to a stale reference point produces an error on every invoice, and a lane carrying more shipments per month multiplies that same per-invoice error across more invoices than a low-frequency lane would.

The mechanism is arithmetic, not judgment. If a fuel surcharge clause updates monthly against an index reading that is itself a month or two behind, the formula either overcharges or undercharges by a fixed percentage until the next reset. That percentage is the same whether the lane ships twice a month or twenty times a month.

What differs is exposure. A facility running frequent Chicago-area moves, whether inbound to a distribution center or outbound from a plant near the rail ramps, generates more invoices carrying that same formula error before anyone notices the pattern. The fix is the same regardless of volume: confirm the index the contract cites, confirm the lag period, and recompute the surcharge for a sample of recent invoices against that stated formula rather than against what the carrier billed.

Gasoline PPI moving 37.1% year over year while trucking-service PPI moved roughly 8% to 11% is itself worth checking against: a surcharge clause referencing the wrong underlying index, or blending diesel and gasoline benchmarks incorrectly, produces a mismatch a line-by-line check will surface quickly.

4. What accessorial charges are worth checking first on a Chicago-area invoice?

Detention and layover charges, congestion or metro surcharges, and chassis or drayage fees at intermodal ramps are the charges most tied to Chicago's specific traffic and dock conditions, and each has a mechanism that can be checked without a dataset: does the invoice cite a wait time against a stated free-time allowance, and does the zone or ramp named on the charge match the tariff's own boundary definition?

These four checks form the starting point for a line-level review of accessorial charges on a Chicago-area freight invoice, before any broader rate-card reconciliation begins.

• Detention and layover: Checked against a stated free-time allowance in hours, not against the carrier's own account of the delay. No stated allowance means no basis for the charge.
• Congestion or metro surcharge: Tested against the zone boundary the tariff actually defines. A charge applied outside that boundary is out of scope regardless of real traffic conditions.
• Chassis and drayage fees: Verified against the rail ramp named on the bill of lading, since ramp-specific fee schedules vary and a mismatched ramp name signals a rate applied from the wrong schedule.
• Fuel surcharge reference: Recalculated from the index and lag period stated in the contract, not accepted as printed, given the year-over-year movement documented above.

5. Can a shipper renegotiate accessorial terms specifically for a Chicago lane?

Yes, and a lane-specific addendum is more useful here than a blanket contract amendment, because Chicago's congestion and dock conditions genuinely differ from the rest of a shipper's network. A contract can state a free-time allowance, a congestion zone boundary, and a fuel surcharge index and lag period specific to that lane, replacing carrier discretion with terms both sides can check an invoice against.

A national master service agreement written for a shipper's whole network tends to leave accessorial definitions general, because most lanes do not need the specificity. Chicago is one of the few where that generality costs money, given the volume of detention, congestion, and drayage charges the metro's own conditions generate.

A lane addendum does not need to eliminate these charges. It needs to define them: a stated free-time window before detention applies, a named zone map for any congestion surcharge, and an explicit index and lag period for the fuel component, rather than a general reference to "prevailing conditions."

Once those terms exist in writing, the audit becomes mechanical: pull the invoice, pull the addendum, check one against the other. Without them, every invoice is adjudicated after the fact, invoice by invoice, on the carrier's account of what happened.

6. How does a Chicago-focused freight audit differ from a general freight and 3PL review?

A general freight and 3PL audit checks rate cards, accessorial definitions, and duplicate billing across a shipper's whole carrier base. A Chicago-focused pass adds two things a generic review will not catch: whether accessorial thresholds are defined at all for the metro's specific congestion and ramp conditions, and whether the fuel and linehaul surcharge formulas in use are keeping pace with the index movement documented above.

The general audit disciplines still apply here: match the invoice to the contract line, check for duplicate carrier billing across a multi-carrier network, and confirm accessorial charges have a rate-card basis at all. None of that changes by geography.

What a Chicago-specific pass adds is a check the general review has no reason to run everywhere else: does the contract's accessorial language actually contemplate the conditions this metro produces at volume, and is the fuel surcharge formula referencing a current index rather than a stale one. Both are checks worth running once, on the contract language itself, rather than repeatedly on every invoice.

For the broader mechanics of a freight audit, including three-way matching and carrier consolidation, that ground is covered in the freight and 3PL audit guide rather than repeated here.

For the wider pattern this sits inside, start with the margin drift guide.