How rate schedule violations happen in freight

Executive Summary

A rate schedule violation happens when a carrier or 3PL invoice charges a rate, tier, or surcharge that differs from the rate card in the executed contract, and nothing downstream catches the difference before the invoice is paid. The mechanism is structural: rate cards live in a contract PDF or an addendum spreadsheet, while invoices are generated from the carrier's own billing system. The two are never automatically reconciled against each other.

Three-way matching, the standard AP control, checks an invoice against a purchase order and a receipt of goods. Freight does not generate a purchase order in the conventional sense, and the "receipt" is a bill of lading, not a rate confirmation. That leaves the rate card itself, the one document that actually defines the correct charge, outside the control that is supposed to catch billing errors.

What changes this is a control that reads the contract's own rate table and tests every line of every invoice against it, line by line, rather than trusting that the carrier's system applied its own contract correctly. Until that control exists, a rate schedule violation persists for as long as the carrier relationship does.

1. What is a rate schedule violation in freight billing?

A rate schedule violation is any freight or 3PL invoice line that charges a rate different from the one specified in the carrier's executed rate card: a wrong per-mile rate, a lane charged at the wrong tier, an accessorial fee not listed in the contract, or a fuel surcharge calculated off the wrong index or the wrong base rate. It is a mismatch between the contract's rate table and the number that actually lands on the invoice, regardless of whether.

The rate card is the contract's pricing exhibit. It lists a base rate by lane or by mile band, a table of accessorial charges (detention, liftgate, residential delivery, redelivery), and the formula the fuel surcharge is supposed to follow. Every one of those is a distinct place a violation can start.

A violation is not the same as fraud. Carrier billing systems update rate tables on their own schedule, sometimes annually, sometimes per lane. A rate negotiated down in a contract renewal does not automatically propagate to the carrier's invoicing system on the same day. The gap between the two is the violation, whatever caused it.

The distinction matters for how a shipper responds. A negotiation error gets corrected with a phone call. A structural one, where the carrier's system is charging an old rate table by default, recurs on every invoice until someone changes the input, not just the individual bill.

2. How does a rate schedule violation happen in freight and 3PL?

It happens because the rate card and the invoice are produced by two different systems that never talk to each other. The contract's rate table sits in a PDF or spreadsheet held by procurement or the carrier relationship owner. The invoice is generated by the carrier's own billing engine, built from whatever rate table that engine has loaded, which may be an old renewal, a default tier, or a rate keyed to the wrong customer account.

A shipper signs a new rate agreement. The new rate card exists as a document. Whether it exists as an input to the carrier's invoicing system is a separate question, one the shipper cannot see and the carrier has no independent incentive to verify quickly.

Until someone tests an invoice against the new rate card directly, both sides can believe billing is correct. The carrier's system is producing consistent output. The shipper's AP team is paying invoices that look ordinary: right lane, right weight, plausible rate. Nothing about the invoice signals that it is wrong, because the invoice was never compared to the document that defines correct.

A. Rate card update lag

A renewal or a rate reduction takes effect on a contract date. The carrier's billing system update is a separate operational task, owned by someone on the carrier side, on their own timeline. Until it happens, every invoice bills the prior rate table, correctly from the carrier's system's point of view and incorrectly against the contract the shipper signed.

B. Tier misassignment

Volume-tiered rate cards drop the per-unit rate once a shipper crosses a threshold. If the carrier's system does not track cumulative volume against the right period, or assigns the shipment to the wrong customer account, the invoice bills the prior tier's rate indefinitely, because nothing forces a re-check against current volume.

3. Where do carrier rate schedules and invoices actually diverge?

Divergence concentrates in three parts of the rate card: the base line-haul rate by lane or mile band, the accessorial charge table, and the fuel surcharge formula. Each is calculated differently, stored differently in the carrier's system, and updated on a different schedule, which means a control built to catch one type of divergence will not automatically catch the other two.

Base rate divergence is the simplest to state and the hardest to catch without the contract in hand: the invoice charges a different per-mile or per-lane rate than the rate card specifies, often because the wrong mile band or wrong origin-destination pair was matched.

Accessorial divergence is different in kind. These are fees the contract may cap, exclude, or price at a negotiated rate: detention, liftgate, redelivery, residential surcharge. A carrier's default tariff for these charges is usually higher than a negotiated contract rate, and an invoice built from the default tariff rather than the negotiated schedule looks like an ordinary accessorial fee.

Fuel surcharge divergence is the least visible of the three because the number changes on every invoice regardless of whether it is correct, so a moving number does not look anomalous the way a static wrong number would.

4. Why does fuel and freight cost movement make rate violations harder to catch?

Fuel surcharges and freight rates move constantly in the underlying market, which gives a wrong surcharge cover: a changing number reads as a correctly updating one. Per the US Bureau of Labor Statistics Producer Price Index (read 2026-09-07), the gasoline commodity index rose 37.1% year over year to 302.759 in July 2026, and truck transportation of freight rose 10.9% year over year to 170.984 over the same period.

When the underlying cost index is moving by double digits, a surcharge line that also moves by a large amount does not stand out on visual review. An AP reviewer scanning invoices for anomalies is looking for a number that looks wrong. A fuel surcharge that tracks a real 37.1% year-over-year move in the gasoline index (BLS PPI, series WPU0571, read 2026-09-07) looks exactly like what a correctly functioning surcharge formula should produce, whether or not the formula behind it is actually the one in the contract.

The same logic applies to base rates. General freight trucking, long-distance truckload pricing rose 8.1% year over year to an index value of 195.575 in July 2026 (BLS PPI, series PCU484121484121, read 2026-09-07). A base rate increase on an invoice is plausible on its face in a market moving that fast, which is exactly the condition under which a contract violation is least likely to be questioned by a reviewer working from memory or from a prior invoice rather than from the rate card itself.

5. What does three-way matching miss in a freight invoice?

Three-way matching checks that an invoice agrees with a purchase order and a receipt of goods. It confirms quantity and vendor identity. It does not test whether the rate charged on the invoice matches the rate table in the contract, because the rate table is not one of the three documents the match compares, and freight rarely produces a conventional purchase order in the first place.

Standard AP controls were built for purchased goods, where a PO states a price and a receipt confirms delivery. Freight billing does not follow that pattern. The closest equivalent to a PO is a rate confirmation or a bill of lading, and neither one restates the full rate card: the mile-band pricing, the accessorial table, the fuel surcharge formula.

A three-way match can confirm that a shipment happened, that the carrier is the one contracted, and that the invoice references a real shipment. None of that tests whether the dollar amount charged is the dollar amount the rate card specifies for that lane, weight, and accessorial combination.

That gap is structural, not a failure of the control to do its job. The control was never designed to read a contract's pricing exhibit. Closing the gap requires a separate check, one built specifically to hold the rate card as the reference and test every invoice line against it.

6. How can a shipper catch rate schedule violations before they compound?

Catching a rate schedule violation early means testing invoices against the rate card directly, line by line, rather than relying on a downstream control built for a different purpose. The check has to compare the exact lane, mile band, weight break, and accessorial code on the invoice against the corresponding line in the contract, and flag any charge the rate card does not authorize at that amount.

None of this is a one-time exercise. A rate card tested once at contract signing and never again only confirms that the rate was correct on that day. The carrier's system, the fuel index, and the shipper's own volume all keep moving after that, and any one of them can push an invoice out of agreement with the contract on a later date without anyone changing the contract itself.

A recurring check, run against every invoice rather than a sample, is the only version of this that actually closes the gap rather than spot-checking it.

1. Digitize the rate card: Turn the contract's pricing exhibit into a structured table the invoice can actually be tested against, rather than leaving it as a PDF nobody re-opens after signing.
2. Match every invoice line: Test the base rate, the accessorial code, and the surcharge formula on each line separately, since each one diverges from the contract for a different reason.
3. Recompute the surcharge: Apply the contract's own fuel surcharge formula to the invoice date's index value and compare the result to what was billed, instead of accepting a moving number as self-evidently correct.
4. Track renewal propagation: After any rate renewal, test the first invoices under the new rate specifically, since that is the window where the old rate table is most likely still loaded on the carrier's side.

7. What should a rate schedule violation review actually check?

A rate schedule violation review checks four things on every invoice: the base rate against the correct lane and mile band, the accessorial charges against the contract's negotiated table rather than the carrier's default tariff, the fuel surcharge against the contract's own formula and a current index reading, and the tier or volume threshold against the shipper's actual cumulative volume for the period.

Each row in that table fails independently of the others. A carrier can have the base rate exactly right and the accessorial table wrong, or the fuel formula right and the tier assignment wrong. That is why a review has to check all four rather than sampling one and assuming the rest follow.

A margin drift diagnostic runs this kind of line-by-line rate card comparison across a shipper's full freight and 3PL invoice history, not just the current month, because a rate table error that started at a renewal keeps recurring on every invoice until someone tests against the rate card directly and corrects the input on the carrier's side.

What a rate schedule violation review tests, by rate card component.

For the wider pattern this sits inside, start with the margin drift guide. See also the Margin Drift Diagnostic and our insights.

8. Frequently Asked Questions (People Also Ask)

Is a rate schedule violation the same as a billing error?

It is one type of billing error, specifically defined by a mismatch against the contract's rate card. A billing error can also be a duplicate payment or a math error on the invoice itself. A rate schedule violation always traces back to the rate, tier, or surcharge specified in the contract.

Can a carrier's own system be trusted to bill the current rate?

The carrier's system bills whatever rate table is loaded into it. That table is updated by a separate process from the contract signing, on the carrier's own timeline, and nothing in the shipper's AP process independently confirms the two match unless the invoice is tested against the rate card directly.

Does three-way matching catch rate schedule violations?

No. Three-way matching compares an invoice to a purchase order and a receipt of goods. It confirms a shipment happened and the vendor is correct. It does not compare the invoiced rate to the rate card, because the rate card is not one of the three documents the match uses.

Why does a fuel surcharge error go unnoticed longer than a base rate error?

Fuel surcharges change on every invoice because the underlying fuel index moves. A reviewer scanning for anomalies is looking for a number that stands out, and a moving surcharge does not stand out the way a static wrong number does, even when the formula behind it is wrong.

What is the difference between an accessorial charge and a rate schedule violation?

An accessorial charge is a legitimate fee type, such as detention or liftgate, that a contract may price at a negotiated rate. The violation occurs when the invoice bills that fee at the carrier's default tariff rate instead of the rate the contract actually negotiated.

How far back should a freight rate card review go?

As far back as the contract's rate card has been in effect without being re-tested, since a rate table error introduced at a renewal recurs on every invoice from that date forward until someone corrects the input on the carrier's side.

Does a rate schedule violation mean the carrier is acting in bad faith?

Not necessarily. Many violations trace to a lag between a contract's effective date and when the new rate table is loaded into the carrier's billing system, or to a shipment logged against the wrong account or volume period, rather than an intentional overcharge.

What document should a freight invoice actually be tested against?

The rate card exhibit in the executed carrier contract, structured line by line: base rate by lane and mile band, the accessorial fee table, and the fuel surcharge formula, not the carrier's general tariff or a prior invoice used as a reference point.

Can a shipper catch this without specialized software?

A shipper can test invoices against a digitized rate card manually, line by line, using the contract's own tables. The work is the same regardless of tooling: match rate, tier, and surcharge on every invoice against the contract, not a sample of invoices.