What should a CFO ask about vendor invoice accuracy?

Executive Summary

The core problem is that invoice accuracy gets checked against the wrong reference document. Three-way matching confirms an invoice against a purchase order and a receipt. It never opens the contract, so a rate card change, an expired surcharge, or a rebate clause never gets tested at all. That gap is where margin drift accumulates, quietly and month over month.

The fix starts with questions, not software. A CFO who asks AP "what document did you check this invoice against" and gets "the PO" as the answer has just found the control gap. The contract, not the PO, is the reference that carries rate tiers, not-to-exceed caps, and rebate triggers.

The sections below give six concrete questions to put to AP, procurement, and vendor-facing teams, what each one is meant to surface, and what a weak answer sounds like. None of them require new software to ask. They require someone to pull the contract file and compare it to twelve months of invoices, which is exactly the gap a diagnostic engagement is built to close in a bounded window.

1. What document does AP actually check an invoice against?

AP almost always matches an invoice to a purchase order and a receipt, confirming quantity and unit price against what was ordered. That three-way match never opens the underlying contract, so it cannot catch a rate card that changed without an update, a volume tier that should have triggered a lower price, or a surcharge that outlived the condition that justified it. Ask AP directly which document is the source of truth for pricing terms.

If the answer is the.

The purchase order usually just repeats whatever price was last entered into the ERP. If that price was wrong when it was entered, or the contract changed since, the PO matches the invoice and the invoice still overcharges.

A useful follow-up question: who owns keeping the ERP's price fields in sync with the signed contract, and how often does that happen? In many mid-market finance teams the honest answer is nobody, or only when someone notices.

This is the single highest-value question on this page because it identifies the structural cause rather than a symptom. Every other question below is really a variant of it, applied to a specific clause type.

• Purchase order: Confirms quantity and unit price against what was entered in the system, not against the contract.
• Goods receipt: Confirms delivery happened. Says nothing about whether the price charged was the price owed.
• Signed contract: Holds the rate card, tier triggers, and caps. Rarely part of the standard invoice check.

2. How would you know if a rate card changed mid-contract?

Ask whether anyone reconciles the rate actually billed on each invoice against the rate schedule in the signed contract, on a recurring basis, for the life of the agreement. Most AP workflows check price consistency invoice to invoice, not invoice to contract, so a rate that drifts upward gradually never trips an exception. The right test: pull one vendor's contract rate card and the last twelve invoices, and compare unit rates line by line rather than trusting that last month's.

A rate can drift for reasons that have nothing to do with fraud. A vendor's system defaults to a list price after a promotional rate expires. A renewal negotiated a lower tier but the old rate stayed in the billing system. Neither shows up in a PO match because the PO was built from the same stale rate.

Ask procurement how contract renewals get communicated to AP and to the ERP. If the answer involves an email that may or may not have been actioned, that is the gap.

What a rate check compares, by control type.

3. Are surcharges still tied to the condition that triggered them?

A fuel surcharge, expedite fee, or peak-season charge is supposed to apply only while its trigger condition holds, and most contracts state an expiration or a review date. Ask whether anyone checks that a surcharge still applies before it is paid, or whether it is paid automatically because it appeared on last month's invoice too. A surcharge that outlived its trigger condition is not fraud.

It is a control nobody assigned.

Surcharges are especially easy to miss because each one, on its own invoice line, looks small and plausible. The gap only becomes visible when you line up the trigger condition in the contract against the billing history and ask when the condition stopped being true.

A useful question for procurement: for each active surcharge on a vendor account, what is the stated trigger and expiration, and who reviews it. If nobody can answer for a given line, that line is running on autopilot in a freight and 3PL audit as much as anywhere else.

4. Does anyone track credit memos and rebates owed but not applied?

A returned shipment, a volume rebate crossing its threshold, or a pricing dispute resolved in the buyer's favor should each generate a credit. Ask whether AP tracks credits owed separately from credits received, and reconciles the two on a schedule. Most systems record a credit memo only once it arrives; they do not flag when one is due and has not shown up.

That asymmetry is where earned money quietly goes unclaimed.

Volume rebates are the clearest example. A contract sets a threshold: cross a certain spend level in a quarter and the rate drops retroactively, or a check follows. Crossing that threshold is a fact the buyer's own purchasing data can prove, independent of whether the vendor ever sends the rebate.

Ask procurement to name every active rebate clause across the top vendor contracts and who is responsible for tracking the buyer's own spend against each threshold. If that answer is vague, the rebate is being tracked, if at all, by the party with no incentive to flag it.

5. Who owns the not-to-exceed cap on contract labor and services?

A not-to-exceed clause caps what a vendor can bill for a project or a period regardless of hours logged. Ask who checks cumulative billing against that cap before an invoice is approved, not after. In practice this check tends to happen only once a project is far enough along that a breach is expensive to unwind.

The right question is whether the cap is checked at invoice time or discovered at project close.

Contract labor and professional services invoices are approved individually, line by line, month by month. An NTE cap is a cumulative figure across the whole engagement, and cumulative figures are exactly what invoice-by-invoice approval is bad at catching.

Ask whichever manager owns the vendor relationship whether they can state, right now, the cumulative billing to date against the contract cap. If that number requires pulling every invoice and adding it up on the spot, the control is not running.

6. What would a 12 to 18 month look-back on service vendor invoices find?

Every question above assumes someone is checking invoices as they arrive. The honest follow-up is what has already gone unchecked. Margin drift across a full diagnostic typically runs 1% to 3% of service vendor spend, across ValueXPA diagnostics, and it accumulates in exactly the categories named in the questions above: rate cards, surcharges, rebates, and NTE caps.

A structured look-back is the only way to find what forward controls already missed.

A CFO asking these questions internally will usually get partial answers. AP checks POs. Procurement tracks renewals loosely. Nobody owns the reconciliation between contract terms and twelve months of billing history end to end, because it sits between departments.

A bounded diagnostic exists to answer exactly this question once, across every service vendor category at the same time, and to hand back a prioritized list of what to fix first rather than a general finding. It runs on the client's own invoice and contract data, not a benchmark, so the figure it produces is specific to that spend base.

For the wider pattern this sits inside, start with the margin drift guide. See also the six categories drift hides in and what is margin erosion? causes and prevention for manufacturers.

7. Frequently Asked Questions (People Also Ask)

What is the single most important question to ask AP about invoice accuracy?

Which document AP checks an invoice against for pricing: the purchase order or the signed contract. If the answer is the purchase order, pricing terms like rate tiers, rebate clauses, and NTE caps are not being tested at all, because the PO only repeats what was last entered into the ERP.

Is three-way matching enough to catch overbilling?

Three-way matching confirms an invoice against a purchase order and a receipt. It checks quantity and price consistency with what was ordered, not with the contract. It does not test whether a surcharge's trigger condition still holds or whether a rate card changed without an ERP update.

How do surcharges cause margin drift if AP checks every invoice?

A surcharge line looks plausible in isolation because it appeared on the prior invoice too. The trigger condition that justified it lives in the contract, not on the invoice, so checking invoice-to-invoice consistency never tests whether the condition still applies.

Should a CFO ask procurement or AP about rebate tracking?

Both, because the gap sits between them. AP records rebates once a credit memo arrives. Procurement or the vendor relationship owner usually holds the purchasing data needed to prove a volume threshold was crossed. Ask who reconciles the two, since most workflows do not assign that reconciliation to anyone.

What does a not-to-exceed cap actually protect against?

It caps total billing on a contract labor or services engagement regardless of hours logged. It protects against cumulative overbilling that individual invoice approvals cannot see, because each invoice is approved on its own, not against the running total.

Can a CFO answer these questions without hiring an outside firm?

Yes, in principle: pull the contract file and twelve months of invoices per vendor and compare line by line. In practice this rarely happens internally because it sits between AP and procurement and neither owns it end to end, which is why it tends to stay undone.

How much money is typically found when these questions are actually answered?

Margin drift across a full diagnostic typically runs 1% to 3% of service vendor spend, across ValueXPA diagnostics, translating to $300K to $4.5M per year across ValueXPA diagnostics for a company above $100M in revenue. The figure depends on the vendor base and cannot be predicted from a single clause type.

Does a contract compliance review replace AP automation software?

No. AP automation prevents forward-looking entry errors at the point of invoice receipt. It does not interpret unstructured contract terms like rebate clauses or NTE caps living in a PDF outside the ERP, and it does not look back across already-paid history, so the two are complementary.

Who inside the company should own the answer to these questions going forward?

Ownership needs to be assigned explicitly, because the current gap exists precisely because no single role owns invoice-to-contract reconciliation. Whether that lands with AP, procurement, or a dedicated controller function is a structural decision the CFO has to make, not a default that already exists.

What is the difference between asking these questions once and asking them continuously?

A one-time look-back finds what has already leaked in the past 12 to 18 months. It does not, by itself, stop the same gap from reopening on the next contract renewal or the next surcharge cycle, which is a separate, ongoing question about who owns the check going forward.