Courier Invoice Audit: How to Find Hidden Overcharges

The Overcharges Hiding in Plain Sight

Weight and zone errors get the attention because they are the largest per shipment. But the most systematic leaks are the ones that touch every order quietly. Here is what a real audit surfaces, beyond the obvious two.

Fuel surcharge drift

Couriers add a fuel surcharge as a percentage on base freight and revise it regularly, often monthly, with fuel prices. The leak: the billed percentage creeps above what your contract specifies, or it gets applied on a base that already includes other fees. Because it sits on every shipment, even a one or two point error compounds across your full volume into real money. This is the single most systematic overcharge an audit catches. [EXTERNAL: hidden shipping cost audit guide]

Wrong remote-area charges

Every courier has a serviceability map that flags certain pincodes as remote or extended-area and adds a surcharge. The maps differ between couriers and are frequently out of date, so the surcharge lands on pincodes that are perfectly serviceable. One focused D2C audit reportedly recovered over ₹42,000 from wrong remote-area charges alone. [VERIFY: remote-area surcharge recovery example India] Check every remote-area line against the actual delivery pincode.

Billing for undelivered or cancelled shipments

Orders get cancelled before dispatch, or a shipment is created and never picked up, yet the freight still appears on the invoice. An audit that matches the billing report against your actual dispatched-and-delivered orders catches charges for shipments that never moved.

Duplicate charges

The same AWB billed twice, or a forward charge plus an RTO charge plus a re-attempt fee that double-counts one movement. Rare per shipment, but a clean, self-evident win in the invoice itself.

GST mismatches

GST computed on a wrong base, or at a mismatched rate, quietly inflates the total. It is easy to miss because tax feels non-negotiable, but a wrong tax base is still a wrong charge. [VERIFY: GST mismatch frequency on courier invoices India]

Missed SLA refunds

This one is not an overcharge you paid, it is money the courier owes you and never paid out. Many couriers credit a partial or full refund when they miss a committed delivery timeline, but the claim has to be filed inside a window, and almost nobody files it. An audit that tracks delivery SLAs against the promise surfaces refunds you are entitled to but never claimed.

The pattern across all six: they are individually small, scattered, and invisible in a lump sum. Only a line-by-line audit makes them show up, and only at the portfolio level does the total become worth chasing.

How to Run a Courier Invoice Audit

Here is the process, end to end. The first cycle is the slowest because you build the rate-card baseline once. After that, each cycle is an hour or two for most brands.

Step 1: Structure your rate card once

Turn your contracted rate card into a usable lookup: weight slab by zone gives base freight, plus the COD fee logic, RTO logic, the contracted fuel surcharge percentage, the remote-area pincode list, and any fixed accessorials. Do this once per courier. This is the baseline every audit compares against, and it is the step most brands skip, which is exactly why they cannot prove their overcharges.

If you ship across Delhivery, Shiprocket, Bluedart and Ekart, you need one structured rate card each. They price, zone, and surcharge differently.

Step 2: Pull the billing report and your order manifest

Export two files for the billing period:

• The courier billing report: every charge line by AWB, including forward freight, COD fee, RTO, fuel surcharge, remote-area and other surcharges, and GST.
• Your order manifest: AWB, declared weight, dimensions, destination pincode, payment mode, order value, and dispatch / delivery status.

The AWB is the key that ties what you shipped to what you were billed. If your manifest does not carry the AWB cleanly, fix that first, because the whole audit depends on the match.

Step 3: Match on AWB and catch the easy wins first

Join the billing report to the manifest on AWB. Two checks give you the fastest wins before any recompute:

• Orphan charges: any AWB on the invoice with no matching dispatched shipment in your manifest. That is billing for something that did not ship.
• Duplicates: any AWB billed more than once for the same movement.

These need almost no evidence beyond the invoice itself, so clear them first.

Step 4: Recompute the expected charge, line by line

For every matched shipment, compute what it should have cost from your structured rate card:

Expected = forward freight(chargeable weight slab, correct zone)
         + COD fee (if COD, correct slab/percent)
         + RTO fee (if returned, correct rate)
         + fuel surcharge (contracted % on correct base)
         + remote-area charge (only if pincode is genuinely remote)
         + valid accessorials only
         + correct GST

Flag every line where  Billed − Expected > 0

Chargeable weight is the higher of dead and volumetric weight. Correct zone comes from the destination pincode. The flagged lines, where billed beats expected, are your recovery pipeline.

Step 5: Classify each flag by overcharge type

Sort the flags into weight discrepancy, zone mismatch, COD or RTO fee error, fuel surcharge drift, wrong remote-area charge, GST mismatch, duplicate, and undelivered billing. Group them, because each type takes the same evidence, and batching by type is far faster than handling each AWB cold.

Grouping also tells you where your structural leak is. If 60% of your recoverable value is one wrong fuel-surcharge rate, that is a single contract conversation, not a thousand disputes.

Step 6: Dispute in-window, then verify the credit

File each dispute inside its window, which is often as short as 7 working days, with the right evidence: a scale-and-tape photo for weight, the pincode-to-zone mapping for zone, the rate card line for fee and surcharge errors, the two invoice lines for duplicates. Then log every dispute and confirm the approved amount actually lands back in your wallet or next invoice. An approved dispute is not recovered until the money is back. [INTERNAL LINK: Shiprocket weight discrepancy dispute process]

Step 7: Fix the source so it stops recurring

Every recurring overcharge is a process bug. A repeated weight discrepancy on a SKU means its catalogue weight is wrong. A repeated remote-area charge on a pincode means the serviceability map is stale and worth escalating to your account manager. A wrong fuel surcharge means the contract is not being applied and needs fixing at the source. Recovery returns money already lost; fixing the source stops the leak.