Skip to content
CheckMyFreightBill.com
Freight AP and Invoice Workflow

Freight Invoice Audit Process: Catch Errors Before You Pay

A freight invoice audit process that works is five gates run in order before payment. Here is each gate, what it checks, and what to do with an exception.

By 11 min read

A working freight invoice audit process is five gates run in a fixed order before any bill gets approved: completeness, duplicate screen, document match, recomputation of the variable charges, and accessorial authorization. Anything that fails a gate becomes an exception with an owner and a clock. Everything that passes all five gets paid without a human reading it line by line.

The order matters more than the tooling. Most freight AP desks do all five checks eventually, but they do them in whatever order the invoice arrives in and they do them inconsistently, so the cheap checks that catch the biggest errors get skipped on busy weeks. A duplicate invoice costs you the full linehaul. It also takes about four seconds to catch if you screen for it before anyone starts reconciling rates.

This is a process post, not a software post. Every gate below can be run in a spreadsheet at low volume. What changes with volume is who runs it and how much of it is automated, not what gets checked.

What a freight invoice audit process is for

You are not trying to find fraud. Assume you will not find any. The overwhelming majority of freight billing errors are process artifacts: an accessorial added at the billing stage by someone who never saw the facility, a fuel surcharge pulled from the wrong index week, a rebill issued under a new number because the first one was short-paid, a load billed twice because it moved between two of the carrier’s operating systems.

Those are all honest mistakes, and they all cost you the same as dishonest ones. A process catches them because a process does not get tired or trust a carrier it has worked with for nine years.

Recovery expectations should be set carefully, because the published numbers vary and most come from firms selling audit services. Darrigo Consulting, a freight audit consultancy, publishes recovery benchmarks of 2 to 5 percent of spend for parcel, 3 to 8 percent for LTL, and 1 to 3 percent for truckload. Treat those as a consultant’s range, not a promise. Your own first pass will tell you more than any benchmark, and the answer for a well-run truckload program with a small carrier base is often “not much,” which is a legitimate and useful result.

The five gates, in order

Run them in this sequence. Each gate is cheaper than the one after it, so a failure at gate two saves you the work of gates three through five.

Gate What it checks Source document Typical failure
1. Completeness The bill contains the fields required to rate and identify it The invoice itself Undescribed charge lines, missing PRO or BOL number
2. Duplicate screen This shipment has not already been paid Your own payment history Same load rebilled under a new invoice number
3. Document match Invoice agrees with the rate con, BOL and POD Rate con, BOL, POD Accessorial with no authorization; weight or class variance
4. Recomputation Variable charges recompute to the same number Rate con formula, DOE index Fuel surcharge on the wrong index week or wrong mileage basis
5. Authorization Every accessorial traces to an approval or a tariff item Rate con, accessorial schedule Charge first appears on the invoice, days after delivery

Gate 1: completeness

Before you reconcile anything, confirm the bill is a bill. Under 49 CFR 373.103, a motor carrier’s freight or expense bill must show consignor and consignee names, the shipment date, origin and destination, package count, freight description, weight or volume, the exact rates assessed, the total charges due with the nature and amount of each charge, the route and each participating carrier, transfer points, and the remittance address.

“The nature and amount of each charge” is the phrase that earns its keep. A line reading “ACC 145.00” with no description does not meet it. Kicking that invoice back for itemization before you spend an hour guessing is both faster and better supported than disputing the amount later.

Note what the rule does not do. It does not entitle you to withhold payment on the whole bill, and it does not make an undescribed charge invalid. It gives you a clean reason to ask for a described one.

Gate 2: duplicate screen

This is the highest-value check per second spent, and it belongs early because it is pure data work with no document review. You are matching the incoming invoice against everything you have already paid, on identifiers that survive a rebill: PRO number, BOL number, load or shipment ID, pickup date plus origin plus destination plus amount.

Invoice number is the one field you cannot rely on, because a rebilled load gets a new one. The mechanics of separating a true duplicate from a legitimate corrected invoice are worked through in how to detect a duplicate freight invoice.

The regulatory backdrop is worth knowing. 49 CFR 378.2 defines a duplicate payment as two or more payments for transporting the same shipment, and 49 CFR 378.9 requires that when the carrier itself discovers an overpayment, duplicate payment or overcollection, it must refund within 30 days. Carriers do find their own duplicates. You should not rely on it.

Gate 3: document match

Gate three is the three-way match: invoice against rate confirmation, bill of lading and proof of delivery. It is the core of the audit and it deserves its own treatment, which is in three-way matching a freight invoice against the rate con, BOL and POD.

The short version: the rate con says what you agreed to pay, the BOL says what was tendered, the POD says what happened. An invoice line has to be traceable to at least one of the three. Lines that trace to none of them are the exceptions.

For invoices that consolidate several loads onto one document, the match runs per load and the totals are checked separately, which is a genuinely different workflow covered in reconciling a consolidated carrier invoice.

Gate 4: recomputation

Some charges are not facts to be verified but formulas to be run. Fuel surcharge is the main one. You cannot check it by looking at it, only by recomputing it from the agreed formula and the published index.

That means your process needs the formula stored somewhere other than the rate con PDF: the index used (national, PADD regional, or a carrier table), the peg price, the miles-per-gallon divisor or the cents-per-mile step, and the effective-date rule. The full recomputation is in how to calculate a truckload fuel surcharge from the DOE index.

The single most common failure is the index week. The EIA On-Highway Diesel Fuel Price Survey captures the cash self-serve pump price as of 8:00 a.m. local time Monday and publishes it around 10:00 a.m. Eastern on Tuesday, per the EIA’s published methodology. Which of those Tuesdays governs a Monday pickup is a contract question, and if your agreement does not answer it you will disagree with the carrier forever. That fight is mapped out in which DOE index week applies to your fuel surcharge.

Gate 5: accessorial authorization

The last gate asks a contract question, not a factual one: was this charge authorized. An accessorial can be entirely real, correctly described, and performed exactly as billed, and still not be owed, because nobody agreed to pay for it.

Three sources of authorization, in descending order of strength:

  1. The charge appears on the rate confirmation with a stated rate.
  2. The charge appears in a signed accessorial schedule or rules tariff that the agreement incorporates by reference.
  3. Someone at your company approved it in writing at the time it happened.

If none of the three applies, the charge is unauthorized and you say so plainly. This is the point where writers overstate. No federal rule prohibits a carrier from billing a liftgate or a detention hour. What decides it is your contract. The clean version of that argument, applied to one charge, is in disputing a liftgate fee on a dock-to-dock delivery.

What happens to an exception

An exception is a queue item with an owner, a document set, and a deadline, not a decision anyone has made yet. Two paths out.

Short-pay and dispute. You pay the undisputed balance and contest the line. This is the stronger position, because it removes the carrier’s past-due leverage while preserving your argument, and it keeps the relationship civil. Send the dispute in writing, attach the documents, and ask for a specific correction by a specific date.

Pay in full, then claim. Sometimes the invoice is already paid before anyone looks at it, or the amount is not worth holding the whole bill for. Then it becomes an overcharge claim. Under 49 CFR 378.4, the claim should be accompanied by the freight bill, the rate, classification, weight or tariff authority relied on, and payment information, and inadequate documentation alone cannot disqualify a claim. Under 49 CFR 378.8, the processing carrier must pay, decline to pay, or settle each written overcharge claim within 60 days of receipt unless you agree in writing to extend.

Either way, the clocks are running from the moment the bill arrives. 49 U.S.C. 13710 gives a carrier 180 days from your receipt of the original bill to add charges beyond what it originally billed, and gives you 180 days from receipt to contest a bill in order to preserve your right to challenge it. Meanwhile 49 CFR 377.203 sets a standard credit period of 15 days beginning the day after the freight bill is presented, extendable by published tariff to no more than 30 calendar days. Your audit cycle has to fit inside the payment terms you actually have. The complete set of these deadlines is collected in the freight billing deadlines reference.

Designing the process for your volume

Be honest about scale, because the wrong process is worse than none.

Under roughly 100 loads a month. Audit everything manually. It is a few hours a week and you will learn your carriers’ billing habits faster than any tool would teach you. Skip the workflow software entirely.

Roughly 100 to 500 loads a month. This is where manual auditing quietly stops happening. The realistic design is gates 1, 2 and 4 automated or semi-automated (they are data comparisons), with gate 3 and gate 5 run only on invoices that fail a threshold test: any invoice with an accessorial, any invoice over a dollar variance from the rate con, any invoice from a carrier with a recent exception history.

Above 500 loads a month. Full-population audit, exception queue with owners and aging, and a recovered-dollar ledger so you can tell whether the process pays for itself. At this volume the question stops being whether to audit and becomes who does it, which is a build-versus-buy decision covered in how freight audit services are priced.

The threshold approach in the middle tier is the one people get wrong. Sampling by percentage (audit 10 percent of invoices) catches almost nothing, because errors are not evenly distributed. Sampling by rule (audit every invoice with an accessorial line) catches most of the money for a fraction of the work.

What to measure

Do not measure the number of invoices audited. Measure these:

  • Exception rate by carrier. A carrier whose invoices fail a gate consistently is a process conversation, not a dispute-by-dispute one.
  • Exception rate by charge type. If detention is your top exception, the fix is in your rate confirmation language, not your AP desk. Where the clock starts is usually the whole argument, as in when detention free time actually starts.
  • Days from invoice receipt to exception raised. If this exceeds your credit period, you are paying before you audit and every finding becomes a claim.
  • Recovered dollars, not flagged dollars. Flagged is a number your process produces. Recovered is a number the carrier agrees to. Only the second one is real.

The build checklist

  1. Get every document into one place: invoice, rate con, BOL, POD, keyed to a load ID that survives a rebill.
  2. Write down your payment terms and the credit period the carrier’s tariff actually claims, then set your audit cycle inside it.
  3. Screen for duplicates on PRO, BOL and load ID before anything else, and screen across months rather than within a batch.
  4. Store the fuel surcharge formula and index rule as structured data, not as a PDF nobody opens.
  5. Define the exception threshold that decides which invoices get a full document match.
  6. Give every exception an owner, an amount, a document set, and a date.
  7. Short-pay and dispute where you can; file a written overcharge claim where you cannot.
  8. Track recovered dollars by carrier and by charge type, and take the top charge type back to the contract at renewal.

Step eight is the one that compounds. An audit desk that only disputes invoices will dispute the same charge forever. An audit desk that feeds its exception data back into the rate confirmation stops the charge from being billable at all, which is worth far more than the recovery.

Sources