How to stop IT and professional services overcharges

Executive Summary

The recurring overcharge is not a billing mistake that happens to repeat. It is a one-time error that was never corrected at its source, so it reappears on every invoice cycle until someone intervenes at the level where it was created: the vendor's rate table, the statement of work, or the SLA tracking process. Finding it once in an audit and paying it back does nothing to the underlying record that keeps producing it.

The mechanism is simple. IT and professional services invoices are approved against a purchase order or a manager's sign-off, not against the master service agreement's rate schedule or scope boundaries. Approval confirms the work happened.

It does not confirm the price or the scope matched the contract. Once an incorrect rate or an out-of-scope task clears approval once, it clears every time after, because the approval process has no memory of the contract terms it should be checking against.

Stopping recurrence requires three things: a documented correction sent to the vendor in writing, a reference point AP can check future invoices against, and a named owner for that reference point. Skip any one of the three and the same finding turns up again at the next renewal or the next audit cycle.

1. Why does the same overcharge keep appearing after you've already caught it once?

An overcharge recurs because catching it and correcting it are two different acts, and most AP processes only do the first. Flagging one invoice line and paying the corrected amount fixes that invoice. It does nothing to the vendor's billing system, the rate table, or the internal approval record that generated the wrong figure in the first place, so the next invoice draws from the same uncorrected source and reproduces the identical error.

A vendor's billing system holds a rate, a resource level, or a scope boundary as a stored value. Every invoice pulls from that stored value. When AP corrects an invoice manually and pays the adjusted amount, the correction lives in a spreadsheet or an email thread, never in the system that generated the charge.

The following month, the vendor's system produces the same invoice again, because nothing in it changed. If the reviewer who caught it the first time is on vacation, or the finding was never documented anywhere AP checks routinely, the overcharge clears.

This is why a single audit, however thorough, only ever buys one clean invoice. The fix has to reach the source record, not just the payment.

• Vendor rate table: Stores the billing rate per resource level or service tier; wrong until someone edits it there, not on the invoice.
• Statement of work scope: Defines what counts as in-scope; unchanged scope language keeps authorizing the same out-of-scope task.
• Internal approval record: Confirms work happened, not that the price matched the contract, so it waves through the same rate indefinitely.

2. What has to change at the vendor's end, not just on your invoice?

The vendor's own billing record has to be corrected in writing, with a reference to the contract clause it violated, and an acknowledgment that the change is retroactive to the point the error started. A verbal agreement or an emailed apology does not update the system that generates the next invoice. Only a documented instruction the vendor's billing team actually applies to their record stops the error from repeating on the following cycle.

The correction has to name the contract clause, the incorrect value, and the corrected value, and it has to go to whoever administers the vendor's billing system, not just the account manager who apologizes for the error.

Ask for written confirmation that the change was applied and the date it takes effect. Without that confirmation, you have no way to know whether the next invoice will reflect it or repeat the error a third time.

This step is often skipped because the immediate credit feels like resolution. It is not. The credit settles one invoice. The written correction is what prevents the next one.

3. Which contract terms does approved-invoice review actually check?

Standard invoice approval checks that the purchase order exists, the amount is within its authorized limit, and a manager signed off on the work being done. It does not check the invoiced rate against the master service agreement's rate schedule, does not check a task against the statement of work's scope boundary, and does not check whether an SLA breach entitles you to a credit. Those checks require the contract document itself, which the approval workflow never opens.

A purchase order confirms budget was allocated. A manager's sign-off confirms the deliverable arrived. Neither document contains the negotiated rate card, the resource-level definitions, or the scope exclusions written into the master service agreement.

That means an invoice can pass every internal control your AP team runs and still charge a rate that was never agreed, or bill a task explicitly excluded from the statement of work. The control gap is not a lapse in diligence. It is a structural mismatch between what gets checked and what the contract actually says.

Closing it means adding the contract document itself as a reference point in the review, not adding more people to the existing review.

4. How do you build a reference AP can check every invoice against?

Pull the rate schedule, resource-level definitions, and scope exclusions out of the master service agreement and put them in a single table AP can open next to the invoice: rate by role, what counts as in-scope, and any SLA credit thresholds. It has to be a document AP actually consults during invoice review, not an attachment filed away after the contract was signed and never opened again.

Contracts are written for legal review, not for line-by-line invoice checking. A forty-page master service agreement buries the rate table in an exhibit and the scope boundary in a different section entirely.

Extracting those terms into one table, a role, its approved rate, and the conditions under which it applies, turns a document nobody has time to reread into something AP can check in the time it takes to review an invoice line.

The table needs a named owner responsible for updating it whenever the contract is amended or renewed. An out-of-date reference is worse than no reference, because it gives AP false confidence that a check happened.

What belongs in a checkable rate reference versus what stays in the contract file only.

5. Who should own catching this going forward?

The rate reference and the correction record need one named owner, usually a controller or an AP lead, not a shared responsibility across procurement and the business unit that requested the work. Shared ownership is how a corrected error resurfaces: everyone assumes someone else updated the reference after the contract was amended, and nobody actually did. A single named owner with the update in their job description is what makes the control durable.

Procurement negotiates the contract and moves to the next one. The business unit that requested the IT project cares about the deliverable, not the billing mechanics behind it. Neither has a reason to revisit the rate reference after the ink dries.

An AP lead or controller who reviews invoices routinely is positioned to notice drift and has a direct reason to keep the reference current: their own review depends on it being accurate.

Assign the update explicitly whenever a contract renews, amends, or adds a new statement of work. An owner without that trigger will still let the reference go stale between renewal cycles.

6. When should you escalate a recurring overcharge instead of correcting it again?

Escalate past a routine credit request when the same error has recurred after a documented correction was already sent and confirmed, when it involves an SLA credit the vendor has not honored across more than one billing cycle, or when the vendor cannot show you the corrected value in their own system. At that point the issue is not a billing mistake anymore; it is a contract administration failure that a credit memo does not fix.

A first occurrence is a correction. A second occurrence after a documented, confirmed fix is a different conversation, one that belongs with whoever owns the vendor relationship commercially, not just the AP team processing invoices.

Ask the vendor to show the corrected value in their live billing system, not just confirm it verbally. If they cannot produce it, the correction was never actually applied, regardless of what the email thread says.

Document the recurrence with dates and amounts before the renewal conversation. A vendor negotiating a renewal responds differently to a documented pattern than to an isolated complaint raised for the first time.

For the wider pattern this sits inside, start with the margin drift guide. See also the six categories drift hides in and accessorial charge audit: the surcharges nobody validates.

7. Frequently Asked Questions (People Also Ask)

Why does an approved invoice still contain a wrong rate?

Because approval checks that a purchase order exists and the amount fits its authorized limit. It does not check the invoiced rate against the master service agreement's rate schedule, so an incorrect rate clears the same approval process every cycle until someone checks the contract directly.

Is a credit memo enough to stop the overcharge from coming back?

No. A credit memo settles the invoice it is attached to. It does nothing to the vendor's stored rate or the scope language that generated the error, so the next invoice pulls from the same uncorrected source and repeats it.

Who should own the rate reference AP checks invoices against?

A single named person, usually a controller or AP lead, with the update written into their responsibilities whenever a contract renews or amends. Shared ownership across procurement and the business unit is how the reference goes stale unnoticed.

What should a written correction to a vendor include?

The contract clause it violated, the incorrect value, the corrected value, and a request for written confirmation of the date the correction takes effect in the vendor's own billing system, not just an emailed apology or verbal agreement.

Does this apply to SLA credits as well as rate errors?

Yes. An SLA credit you are entitled to and never claim behaves the same way a wrong rate does: it recurs every cycle because nothing in the invoice review process checks the SLA threshold against actual performance unless someone builds that check in explicitly.

How is a recurring overcharge different from a one-time billing error?

A one-time error is a mistake in a single invoice. A recurring overcharge means the source record, a rate table, a scope clause, or an SLA tracker, was never corrected, so the same wrong figure keeps generating on every subsequent invoice without anyone re-entering it.

Can AP automation software catch this on its own?

AP automation checks invoices against a purchase order and budget limit at the point of receipt. It does not interpret rate schedules or scope exclusions written in a contract PDF, so it will not catch a rate that is wrong but internally consistent with what it was billed last cycle.

When does a recurring overcharge become a contract issue rather than a billing one?

When a documented, confirmed correction has already been sent and the same error recurs anyway. At that point the vendor's billing system was never actually updated, and the conversation belongs with whoever manages the commercial relationship, not AP alone.