Five Ways Vendors Overbill You (and Why Nobody Catches It)

Nobody sends you an invoice that’s obviously wrong. If a supplier billed you double, you’d notice and you’d call. The overcharges that actually cost you money are the ones designed — or simply allowed — to look unremarkable. They’re small. They recur. And they sit on invoices that get approved in thirty seconds by someone with forty more to get through.

This isn’t usually fraud. Most of it is drift, sloppiness, and systems that quietly default in the vendor’s favor. But the effect on your bank account is the same whether it’s malice or mess. Here are the five places the money leaks, and — more useful — why each one survives review.

1. The rate that crept up

You negotiated $11.00 a unit. Eighteen months later the invoices say $13.50, and at some point in between, nobody decided to pay more — it just happened. Maybe an annual escalator that should have been 3% got applied as 8%. Maybe a “temporary” surcharge never came off. Maybe the rate was simply keyed in wrong once and copied forward ever since.

Why it survives: the person approving the invoice doesn’t have the rate card open. They have a number that looks roughly like last month’s number, and last month’s was already wrong. The reference point is the previous invoice, not the contract — so the error validates itself. Each invoice looks fine relative to the one before it, and the gap from the agreed rate widens unwatched.

2. The cap that got quietly exceeded

Your agreement caps detention at four hours. Or it caps monthly spend at a ceiling. Or it limits a usage tier. The limit exists, it’s written down, and it’s sitting in clause 4.2 of a document last opened the day it was signed.

Then an invoice bills six hours of detention, or runs $400 past the monthly ceiling, and it goes through — because the cap isn’t in anyone’s head, and nothing on the invoice itself announces “this exceeds your agreed limit.” The invoice is internally consistent. Six hours times the rate is correct arithmetic. The only thing that makes it wrong is a constraint nobody is holding it against.

Why it survives: caps are the hardest term to enforce manually, because catching a breach requires remembering the limit and tracking cumulative totals across multiple invoices. That’s not a glance; that’s bookkeeping. So it doesn’t happen.

3. The charge billed twice

A service gets invoiced in March. Through a reissue, a carried-forward line, or two people submitting the same job, it gets invoiced again in April under a slightly different description. Now you’ve paid for it twice.

Why it survives: duplicates rarely look like duplicates. The wording differs, the dates differ, sometimes the amounts differ slightly. To a human reviewing invoices in sequence — one today, the related one three weeks later — there’s nothing connecting them. You’d only catch it by comparing across invoices, which nobody has time to do, so the second charge looks like just another line on just another invoice.

4. The fee that appeared from nowhere

A “documentation fee.” A “processing charge.” An “administrative surcharge.” It’s $35, it’s on the invoice, and it is nowhere in your contract. It was never negotiated, never agreed, and never authorized — it simply showed up, the way these things do.

Why it survives: $35 isn’t worth a phone call. It’s below the threshold where anyone fights it. So it gets approved, and then it appears on the next invoice, and the one after that, because nothing pushed back the first time. The fee that’s too small to dispute is precisely the fee that recurs forever. Multiply a $35 phantom fee across a year of monthly invoices across a dozen vendors and you’re no longer talking about pocket change.

5. The line that isn’t in the agreement at all

Broader than a single rogue fee: sometimes an entire service or line item shows up that your reference document simply doesn’t cover. Not overpriced — unaccounted for. There’s no agreed rate to compare it against because you never agreed to buy it.

Why it survives: a reviewer checking whether the numbers add up has no natural prompt to ask “should this line exist?” That question only gets asked when every line is being mapped back to an agreement — and that mapping is exactly the step manual review skips. An unrecognized line and a legitimate one look identical on a PDF.

The pattern underneath all five

Notice what these have in common. Every one is too small to chase individually. Every one is invisible at the invoice-total level. And every one survives for the same structural reason: the invoice is being checked against itself, or against last month, instead of against the agreement.

That’s the real failure. It’s not that reviewers are careless — it’s that catching any of these requires holding each line against the contract that governs it, remembering caps, and comparing across invoices for duplicates. Done by hand, at volume, that’s not a task a person can do reliably every time. So the small, recurring, invisible errors get through, and they get through consistently, which is what turns a $28 overcharge into a number that matters by year-end.

The fix isn’t trying harder. It’s changing the reference point — checking every line against the agreement, not against the previous invoice. That’s what an invoice audit does, and it’s the whole reason InvoRec compares each line against your contract, rate card, or agreed pricing and flags the ones that don’t match: rate creep, exceeded caps, duplicates, and fees that were never in the deal. The errors are small on purpose. Catching them has to be automatic for the same reason.