# How much do companies overpay on freight and 3PL

> Freight and 3PL invoices carry accessorials, fuel surcharges, and rate errors that escape review. Here is how to size the overpayment, not guess it.

Source: https://valuexpa.com/insights/how-much-do-companies-overpay-on-freight-and-3pl
Publisher: ValueXPA (https://valuexpa.com)
Updated: 2026-09-04

---

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. On a freight and 3PL invoice that gap hides inside accessorial codes, fuel surcharge tables, and detention clauses that almost nobody on the AP team was trained to read against the tariff.

Asking "how much" without a company's own contract and invoice data produces a guess dressed up as an answer. This page gives you the components that create the overpayment and the arithmetic to size it yourself, rather than a number pulled from nowhere.

## Executive Summary

Freight overpayment is not one error. It is several distinct mechanisms: a fuel surcharge that lags the index it is supposed to track, an accessorial charge applied without the condition that triggers it, a rate that reverts to a default tier instead of the negotiated one. Each produces a real dollar gap between contract and invoice. None of them shows up in a three-way match, because a three-way match confirms the invoice ties to a purchase order and a receipt, not that the rate applied is the rate agreed.

Freight input costs move independently of any single contract, which makes a stale surcharge table more expensive to leave unchecked. When the underlying index used in a surcharge formula moves and the formula is never re-checked against it, the gap between what the index says and what the invoice charges widens with every billing cycle.

The honest answer to "how much" is computed from a company's own lane rates, accessorial log, and fuel surcharge schedule, matched line by line against what carriers actually billed. This page sets out where to look and how to build that arithmetic.

## 1. What creates freight overpayment in the first place?

**Freight overpayment comes from three mechanisms operating independently: a fuel surcharge calculated off the wrong index or base rate, an accessorial charge billed without the condition that should trigger it, and a negotiated lane or tier rate that the carrier's system reverts to a published default for. Each requires a different check, and a single reconciliation process rarely catches all three at once.**

A three-way match confirms an invoice ties to a purchase order and a receipt of service. It says nothing about whether the rate charged on that line matches the rate card, or whether an accessorial condition was actually met.

Fuel surcharges are volatile because the input they track, diesel or gasoline pricing, moves on its own schedule, separate from the freight contract. A surcharge schedule set at contract signing and left unchecked accumulates drift every time the underlying index moves and the invoice formula does not catch up.

Accessorial charges (detention, liftgate, residential delivery, redelivery) are billed by code, and the code does not carry proof that the triggering condition occurred. A rate card default is the quietest of the three: nothing about the invoice looks wrong unless someone holds it against the actual negotiated tier.

## 2. How do you tell if a fuel surcharge is wrong?

**A fuel surcharge is wrong when the invoice formula no longer matches the contract's stated index, lag period, or base rate. Confirming it requires pulling the contract clause, the index value for the invoice's billing week, and recalculating the surcharge independently, then comparing that figure to what was actually billed. A mismatch on a recurring lane compounds across every shipment on that lane.**

A fuel surcharge clause names a public index, a lag (the surcharge for this week's shipment is set from an index reading one or two weeks prior), and a base rate below which no surcharge applies. Any one of those three terms can be wrong on the invoice without the invoice looking wrong on its face.

A surcharge table that has not been recalculated since prices last moved understates the correct charge in some periods and overstates it in others. The only way to know which is to run the calculation independently for a sample of invoices, using the index value the contract actually specifies.

The check itself is arithmetic, not judgment: pull the contract clause, look up the index value for the billing week specified, apply the formula, and compare. Discrepancies on a recurring lane are the ones worth chasing first, because they repeat on every shipment.

## 3. Which accessorial charges get billed without the condition being met?

**Detention, liftgate, redelivery, and residential delivery charges are billed by code on the invoice, and the code carries no evidence that the triggering condition, a wait time threshold, a lack of dock access, a failed first delivery attempt, actually occurred. Verifying the charge means matching it against a proof-of-delivery record or a dispatch log, not against the purchase order, which never carries that detail.**

An accessorial code is a shorthand. The invoice line says "detention, 2 hours," and the dollar amount that follows is calculated correctly against the detention rate in the contract. What the invoice line does not carry is proof that the truck actually waited two hours at the dock.

That proof lives in a different system: a dispatch log, a driver's electronic logging device record, a signed bill of lading with timestamps. Contract compliance work on freight means pulling that record for a sample of accessorial-coded invoices and confirming the condition was met, not just that the rate applied to the stated duration is arithmetically correct.

A fuller breakdown of specific accessorial codes and the conditions that should trigger each one is covered in the [accessorial charge audit](/guides/accessorial-charge-audit-the-surcharges-nobody-validates).

## 4. How does a stale rate card produce an overcharge?

**A negotiated rate card sets a specific price per lane or per weight break. When a carrier's billing system is not updated to reflect that negotiated rate, or when a shipment falls into a tier the rate card did not anticipate, the system bills its own published tariff instead. The invoice is internally consistent and still wrong, because it is priced against the wrong reference table entirely.**

Rate card enforcement failures are hard to spot by eye, because the invoice does not look unusual. The math is done correctly against a tariff. It is simply the wrong tariff.

This happens at contract renewal, when a new negotiated rate takes effect on a signed date but the carrier's rating engine keeps billing the prior schedule afterward. It also happens on shipment types the original negotiation did not anticipate: expedited service, an unusual weight break, a new lane, where the system has nothing to fall back to except its own default.

Catching this requires holding a sample of invoices against the current, signed rate card line by line, not trusting that the carrier's system was updated when the contract was.

## 5. Why doesn't AP automation catch this on its own?

**AP automation platforms confirm an invoice matches a purchase order and a receipt of service. They were built to prevent duplicate entry and catch coding errors, not to interpret a fuel surcharge formula or a detention threshold that lives in a contract PDF outside the ERP. The rate logic they need to enforce those terms has to be built and kept current by someone, and that work is not automatic.**

A three-way match is a structural check: does this invoice correspond to a real order and a real delivery. It cannot tell you whether the rate applied on that delivery is the rate negotiated, because the negotiated rate lives in a contract document the automation tool was never given.

Freight contracts carry embedded logic that other spend categories do not always carry in the same form: index-linked surcharges, accessorial trigger conditions, tiered volume commitments. Turning that logic into rules an automation platform can enforce going forward requires first knowing what the rules actually are, which means reading the contract, not the invoice.

A retrospective audit of freight and 3PL invoices is the step that surfaces which rules are being broken before any forward control can be configured to enforce them.

## 6. How do you size your own freight overpayment?

**Sizing the overpayment requires three inputs: the freight and 3PL spend for a defined period, the negotiated rate cards and surcharge clauses for the carriers billed against that spend, and a sample of invoices large enough to recompute each charge independently. Extrapolating from a small sample to the full spend is reasonable once the sample shows a consistent, recurring error, not a one-off.**

Start with the invoice population for a fixed period. Twelve months is long enough to cover seasonal freight volume and short enough to stay current. Pull the rate cards and accessorial schedules in force for that period, not the current ones if a renewal happened partway through.

Recompute a sample of invoices line by line: the base rate against the rate card, the fuel surcharge against the contract formula and the index value for that billing week, and each accessorial charge against a proof-of-delivery or dispatch record.

Errors that repeat on a recurring lane or a recurring carrier are the ones that scale when extrapolated across the full period; a one-off error does not. This is the method the diagnostic runs at engagement scale. A company can run the same logic on a smaller sample internally before deciding whether a full audit is worth commissioning.

- **Define the period:** Pull 12 months of freight and 3PL invoices, long enough to cover seasonal volume swings.

- **Pull the reference documents:** Gather the rate cards, accessorial schedules, and surcharge clauses in force for that same period.

- **Recompute a sample:** Recalculate the base rate, fuel surcharge, and accessorial charges line by line against those documents.

- **Flag recurring errors:** Separate errors that repeat on a lane or carrier from one-off exceptions before extrapolating.

For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. See also [rate card enforcement: why approved timesheets still produce wrong invoices](/guides/rate-card-enforcement-why-approved-timesheets-still-produce) and [off-contract resources: people billed outside the agreement](/guides/off-contract-resources-people-billed-outside-the-agreement).

## 7. Frequently Asked Questions (People Also Ask)

### What is the fastest way to spot a freight overcharge without a full audit?

Pull a handful of invoices from your most frequently used lane and recompute the fuel surcharge and base rate against the signed contract. A mismatch on a recurring lane is a strong early signal, since it repeats on every shipment rather than appearing once.

### Do freight brokers introduce different overpayment risks than asset-based carriers?

A broker's invoice reflects whatever the underlying carrier billed plus a markup, so an error in the carrier's rate or surcharge calculation passes through the broker's invoice unchanged. Checking a broker invoice still means verifying the underlying rate and surcharge terms, not just the broker's markup.

### Can a company recover a freight overcharge after the invoice has already been paid?

Recovery depends on the carrier contract's terms for billing disputes and the carrier's own claims window, which vary by carrier. Identifying the error with a line-by-line recomputation against the contract is the necessary first step regardless of whether recovery is still available.

### Does switching carriers fix rate card enforcement problems?

Switching carriers resets the relationship but does not change the underlying mechanism: a new carrier's billing system can still default to a published tariff instead of a negotiated rate until someone confirms the negotiated terms are actually loaded and applied.

### What documents does a freight rate audit actually require?

The signed rate card or tariff agreement, the fuel surcharge clause with its index and lag terms, the accessorial rate schedule, and the invoices themselves alongside proof-of-delivery or dispatch records for any accessorial charges being checked.

### How often should a fuel surcharge formula be checked against the contract?

The formula itself does not change unless the contract is renegotiated, but the index value it references changes on its own schedule. Recalculating a sample of invoices against the current index value is what catches drift, independent of any fixed calendar interval.

### Is a freight rate audit different from a general AP recovery audit?

A freight rate audit applies the same line-by-line logic, invoice against contract, but requires freight-specific reference documents: rate cards, surcharge index terms, and accessorial trigger conditions that a general AP recovery process does not typically pull in.

### What is the difference between an accessorial charge and a fuel surcharge?

An accessorial charge bills for a specific service or condition, such as detention or liftgate use, tied to an event on a given shipment. A fuel surcharge applies a formula across shipments based on an external index rather than a discrete event.

### Is contract complexity quietly draining your operating margin?

A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit.

**[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)**

## Executive Summary

Freight overpayment is not one error. It is several distinct mechanisms: a fuel surcharge that lags the index it is supposed to track, an accessorial charge applied without the condition that triggers it, a rate that reverts to a default tier instead of the negotiated one. Each produces a real dollar gap between contract and invoice. None of them shows up in a three-way match, because a three-way match confirms the invoice ties to a purchase order and a receipt, not that the rate applied is the rate agreed. Freight input costs move independently of any single contract, which makes a stale surcharge table more expensive to leave unchecked. When the underlying index used in a surcharge formula moves and the formula is never re-checked against it, the gap between what the index says and what the invoice charges widens with every billing cycle. The honest answer to "how much" is computed from a company's own lane rates, accessorial log, and fuel surcharge schedule, matched line by line against what carriers actually billed. This page sets out where to look and how to build that arithmetic.

## 1. What creates freight overpayment in the first place?

Freight overpayment comes from three mechanisms operating independently: a fuel surcharge calculated off the wrong index or base rate, an accessorial charge billed without the condition that should trigger it, and a negotiated lane or tier rate that the carrier's system reverts to a published default for. Each requires a different check, and a single reconciliation process rarely catches all three at once. A three-way match confirms an invoice ties to a purchase order and a receipt of service. It says nothing about whether the rate charged on that line matches the rate card, or whether an accessorial condition was actually met. Fuel surcharges are volatile because the input they track, diesel or gasoline pricing, moves on its own schedule, separate from the freight contract. A surcharge schedule set at contract signing and left unchecked accumulates drift every time the underlying index moves and the invoice formula does not catch up. Accessorial charges (detention, liftgate, residential delivery, redelivery) are billed by code, and the code does not carry proof that the triggering condition occurred. A rate card default is the quietest of the three: nothing about the invoice looks wrong unless someone holds it against the actual negotiated tier.

## 2. How do you tell if a fuel surcharge is wrong?

A fuel surcharge is wrong when the invoice formula no longer matches the contract's stated index, lag period, or base rate. Confirming it requires pulling the contract clause, the index value for the invoice's billing week, and recalculating the surcharge independently, then comparing that figure to what was actually billed. A mismatch on a recurring lane compounds across every shipment on that lane. A fuel surcharge clause names a public index, a lag (the surcharge for this week's shipment is set from an index reading one or two weeks prior), and a base rate below which no surcharge applies. Any one of those three terms can be wrong on the invoice without the invoice looking wrong on its face. A surcharge table that has not been recalculated since prices last moved understates the correct charge in some periods and overstates it in others. The only way to know which is to run the calculation independently for a sample of invoices, using the index value the contract actually specifies. The check itself is arithmetic, not judgment: pull the contract clause, look up the index value for the billing week specified, apply the formula, and compare. Discrepancies on a recurring lane are the ones worth chasing first, because they repeat on every shipment.

## 3. Which accessorial charges get billed without the condition being met?

Detention, liftgate, redelivery, and residential delivery charges are billed by code on the invoice, and the code carries no evidence that the triggering condition, a wait time threshold, a lack of dock access, a failed first delivery attempt, actually occurred. Verifying the charge means matching it against a proof-of-delivery record or a dispatch log, not against the purchase order, which never carries that detail. An accessorial code is a shorthand. The invoice line says "detention, 2 hours," and the dollar amount that follows is calculated correctly against the detention rate in the contract. What the invoice line does not carry is proof that the truck actually waited two hours at the dock. That proof lives in a different system: a dispatch log, a driver's electronic logging device record, a signed bill of lading with timestamps. Contract compliance work on freight means pulling that record for a sample of accessorial-coded invoices and confirming the condition was met, not just that the rate applied to the stated duration is arithmetically correct. A fuller breakdown of specific accessorial codes and the conditions that should trigger each one is covered in the [accessorial charge audit](/guides/accessorial-charge-audit-the-surcharges-nobody-validates).

## 4. How does a stale rate card produce an overcharge?

A negotiated rate card sets a specific price per lane or per weight break. When a carrier's billing system is not updated to reflect that negotiated rate, or when a shipment falls into a tier the rate card did not anticipate, the system bills its own published tariff instead. The invoice is internally consistent and still wrong, because it is priced against the wrong reference table entirely. Rate card enforcement failures are hard to spot by eye, because the invoice does not look unusual. The math is done correctly against a tariff. It is simply the wrong tariff. This happens at contract renewal, when a new negotiated rate takes effect on a signed date but the carrier's rating engine keeps billing the prior schedule afterward. It also happens on shipment types the original negotiation did not anticipate: expedited service, an unusual weight break, a new lane, where the system has nothing to fall back to except its own default. Catching this requires holding a sample of invoices against the current, signed rate card line by line, not trusting that the carrier's system was updated when the contract was.

## 5. Why doesn't AP automation catch this on its own?

AP automation platforms confirm an invoice matches a purchase order and a receipt of service. They were built to prevent duplicate entry and catch coding errors, not to interpret a fuel surcharge formula or a detention threshold that lives in a contract PDF outside the ERP. The rate logic they need to enforce those terms has to be built and kept current by someone, and that work is not automatic. A three-way match is a structural check: does this invoice correspond to a real order and a real delivery. It cannot tell you whether the rate applied on that delivery is the rate negotiated, because the negotiated rate lives in a contract document the automation tool was never given. Freight contracts carry embedded logic that other spend categories do not always carry in the same form: index-linked surcharges, accessorial trigger conditions, tiered volume commitments. Turning that logic into rules an automation platform can enforce going forward requires first knowing what the rules actually are, which means reading the contract, not the invoice. A retrospective audit of freight and 3PL invoices is the step that surfaces which rules are being broken before any forward control can be configured to enforce them.

## 6. How do you size your own freight overpayment?

Sizing the overpayment requires three inputs: the freight and 3PL spend for a defined period, the negotiated rate cards and surcharge clauses for the carriers billed against that spend, and a sample of invoices large enough to recompute each charge independently. Extrapolating from a small sample to the full spend is reasonable once the sample shows a consistent, recurring error, not a one-off. Start with the invoice population for a fixed period. Twelve months is long enough to cover seasonal freight volume and short enough to stay current. Pull the rate cards and accessorial schedules in force for that period, not the current ones if a renewal happened partway through. Recompute a sample of invoices line by line: the base rate against the rate card, the fuel surcharge against the contract formula and the index value for that billing week, and each accessorial charge against a proof-of-delivery or dispatch record. Errors that repeat on a recurring lane or a recurring carrier are the ones that scale when extrapolated across the full period; a one-off error does not. This is the method the diagnostic runs at engagement scale. A company can run the same logic on a smaller sample internally before deciding whether a full audit is worth commissioning. 1. Define the period: Pull 12 months of freight and 3PL invoices, long enough to cover seasonal volume swings. 2. Pull the reference documents: Gather the rate cards, accessorial schedules, and surcharge clauses in force for that same period. 3. Recompute a sample: Recalculate the base rate, fuel surcharge, and accessorial charges line by line against those documents. 4. Flag recurring errors: Separate errors that repeat on a lane or carrier from one-off exceptions before extrapolating. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. See also [rate card enforcement: why approved timesheets still produce wrong invoices](/guides/rate-card-enforcement-why-approved-timesheets-still-produce) and [off-contract resources: people billed outside the agreement](/guides/off-contract-resources-people-billed-outside-the-agreement).

## Common questions

### What is the fastest way to spot a freight overcharge without a full audit?

Pull a handful of invoices from your most frequently used lane and recompute the fuel surcharge and base rate against the signed contract. A mismatch on a recurring lane is a strong early signal, since it repeats on every shipment rather than appearing once.

### Do freight brokers introduce different overpayment risks than asset-based carriers?

A broker's invoice reflects whatever the underlying carrier billed plus a markup, so an error in the carrier's rate or surcharge calculation passes through the broker's invoice unchanged. Checking a broker invoice still means verifying the underlying rate and surcharge terms, not just the broker's markup.

### Can a company recover a freight overcharge after the invoice has already been paid?

Recovery depends on the carrier contract's terms for billing disputes and the carrier's own claims window, which vary by carrier. Identifying the error with a line-by-line recomputation against the contract is the necessary first step regardless of whether recovery is still available.

### Does switching carriers fix rate card enforcement problems?

Switching carriers resets the relationship but does not change the underlying mechanism: a new carrier's billing system can still default to a published tariff instead of a negotiated rate until someone confirms the negotiated terms are actually loaded and applied.

### What documents does a freight rate audit actually require?

The signed rate card or tariff agreement, the fuel surcharge clause with its index and lag terms, the accessorial rate schedule, and the invoices themselves alongside proof-of-delivery or dispatch records for any accessorial charges being checked.

---

ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us
