What should a Controller ask about vendor invoice accuracy?

Executive Summary

A Controller's exposure to vendor invoice accuracy is structural, not personal. Three-way matching confirms an invoice ties to a purchase order and a receipt. It says nothing about whether the rate on that invoice matches the rate in the contract, whether a promotional discount expired on schedule, or whether a volume tier moved without anyone updating the billing system.

Those checks live outside the ERP, in PDF contracts nobody re-reads after signature.

The fix is not more automation at the point of invoice receipt. It is a defined set of questions asked on a schedule: at contract signing, at each invoice cycle, and at renewal. Each question below targets a specific place where a contract term and a billed amount can diverge silently.

Answering them consistently turns invoice accuracy from an assumption baked into the close into a control the Controller can actually defend when asked.

1. Does the invoice match the rate card the contract specifies?

A Controller should ask whether every line item on a vendor invoice ties back to a specific, current rate card clause, not just a purchase order number. Three-way matching confirms quantity and receipt; it does not confirm the unit price against the contract's rate table. Ask AP to name the contract clause that authorizes each rate, not just the PO that authorized the purchase, before the invoice clears for payment.

A purchase order confirms that a purchase was authorized. It rarely carries the rate table itself, which usually lives in a separate contract document, an appendix, or an amendment. The invoice can match the PO number and quantity perfectly while still billing a rate that expired, was superseded by an amendment, or never matched the signed schedule.

Ask AP directly: when a new vendor contract is signed or an existing one amended, who updates the rate reference AP uses to check invoices, and how quickly does that happen. If the answer is vague, the rate check is not happening. That gap is exactly where margin drift accumulates, quietly, invoice after invoice.

2. Are volume tier discounts applying at the right threshold?

A Controller should ask whether the vendor recalculates pricing each time purchase volume crosses a contracted tier threshold, and who confirms the recalculation happened on the correct invoice. Volume tiers are usually self-reported by the vendor with no independent check on the buyer's side, which means a threshold crossed in month four can go unrecognized in billing until month nine, or never.

Volume-tiered contracts assume the vendor will apply a lower rate once cumulative purchases cross a stated threshold. In practice, that recalculation depends on the vendor's own tracking, which the buyer rarely audits independently.

Ask: does anyone on the buyer's side track cumulative volume against the contracted tiers, on a schedule, independent of the vendor's own reporting? If the tracking exists only on the vendor's side, the buyer has no way to know when a threshold was crossed and missed.

3. Is a surcharge still valid once its trigger condition has passed?

A Controller should ask whether each surcharge line on a recurring invoice still meets the condition that justified it originally, such as a fuel index level or an expedited service request, or whether it is simply carrying forward from a prior invoice. Surcharges are typically added correctly at the point a condition is met and then never re-tested as billing continues month over month.

A fuel surcharge, an emergency service fee, or an expedite charge is added to an invoice because a specific condition existed at that billing cycle. Nothing in most AP workflows re-tests that condition on the next invoice. The surcharge line simply repeats.

Ask: for each recurring surcharge, what is the underlying trigger, and when was it last independently verified against current conditions rather than assumed from the prior invoice? A surcharge with no stated expiration or re-verification step is a candidate for persistent overbilling.

A. Fuel and index-linked surcharges

These reference an external index, such as a diesel price benchmark named in the carrier contract. Ask whether the invoiced surcharge percentage still matches what the named index and the contract's formula would produce today, not what it produced when the surcharge was first applied.

B. Condition-based surcharges

These attach to a one-time event: an emergency order, an after-hours service call, a rush fabrication run. Ask whether the invoice documents the specific event each time, or whether the charge simply repeats from the prior cycle without a corresponding event on this one.

4. Who owns the not-to-exceed cap on this contract, and is anyone checking it?

A Controller should ask which specific person is accountable for flagging an invoice that exceeds a contracted not-to-exceed cap, and whether that check happens before or after payment. NTE caps are common in contract labor and professional services agreements, but the cap is a contract term, not a system field, so nothing stops an invoice from clearing above it unless someone is assigned to check.

A not-to-exceed clause sets a ceiling on what a vendor can bill for a given scope, typically in staffing, consulting, or project-based service contracts. The ERP has no native field for that ceiling. It lives in the contract text.

Ask: for each active NTE contract, who is the named owner responsible for comparing cumulative billing against the cap, and on what cadence? If the answer is nobody, or 'AP will catch it,' the cap is not being enforced. AP matches invoices to POs, not to contract ceilings.

5. How far back has anyone actually tested invoice accuracy, not just this month's batch?

A Controller should ask when the last full retrospective test of vendor invoice accuracy against contract terms occurred, since routine AP review tests each invoice as it arrives but rarely revisits a full year of prior billing for the same drift. Duplicate payments, missed credit memos, and unapplied rebates accumulate in exactly the months nobody re-checks.

Standard AP review is forward-looking by design: it processes the invoice in front of it. That leaves 12 to 18 months of historical spend across ValueXPA diagnostics unexamined for the same drift types that recur going forward, including duplicate payments and rebates the vendor never issued without being asked.

Ask: has anyone tested a full period of historical vendor billing against the underlying contracts, rather than just this cycle's invoices? If the answer is no, that is a defined, boundable piece of work, not an open-ended one, and it is worth scoping before assuming the number is small.

6. What would a full contract compliance review actually cost to run, and what would it likely find?

A Controller weighing whether to commission a full review should ask for a fixed-scope engagement rather than a contingency arrangement, since a fixed-scope diagnostic lets the company keep 100% of what it recovers, delivering a prioritized roadmap in 2 to 4 weeks across ValueXPA diagnostics. That scope and timeline question matters more than the vendor's marketing claims about accuracy rates.

Once a Controller suspects drift exists but cannot quantify it internally, the next question is not whether to look, but how to commission the look. Traditional contingency-fee recovery audit firms take 25% to 50% of whatever they recover, which sounds free until the recovery is realized and the fee comes out of it.

A fixed-scope diagnostic prices the engagement upfront, independent of what it finds, and the company keeps the full recovery. Ask any vendor proposing this work: is this priced on contingency or fixed scope, and does the engagement cover contract compliance forward as well as recovery backward, or only one of the two?

For the wider pattern this sits inside, start with the margin drift guide.

7. Frequently Asked Questions (People Also Ask)

Is three-way matching enough to catch vendor overbilling?

No. Three-way matching confirms the invoice ties to a purchase order and a receipt, meaning quantity and authorization are correct. It does not test the unit price against the contract's rate card, a volume tier threshold, or a surcharge's trigger condition. Those checks sit outside standard AP matching entirely.

Who should own the not-to-exceed cap on a services contract?

Someone specific, named at contract signing, not AP by default. AP matches invoices to purchase orders; it has no visibility into a contract clause like an NTE cap unless someone builds and maintains that comparison separately, on a defined cadence.

How often should a Controller re-check a surcharge line item?

Each time it appears on an invoice, the underlying trigger condition, whether an index level or a one-time event, should be re-verified rather than assumed to still apply from the prior cycle. A surcharge added correctly once can persist on invoices long after its condition has lapsed.

What is margin drift, in plain terms for an AP conversation?

It is the gap between what a vendor contract specifies and what the invoice actually bills. It covers stale rates, missed volume discounts, surcharges that outlived their trigger, and NTE caps nobody tracked.

Should a Controller ask for a contingency or fixed-scope review?

Fixed-scope, when the option exists. Traditional contingency-fee recovery audit firms charge 25% to 50% of recoveries. A fixed-scope engagement prices the work upfront and the company retains 100% of whatever it recovers.

Does AP automation software answer these questions on its own?

AP automation prevents forward-looking errors at the point of invoice receipt. It does not interpret unstructured contract terms like rebate clauses or NTE caps living in PDFs outside the ERP, and it does not quantify leakage already embedded in historical spend.

How far back should a historical invoice review go?

Across ValueXPA diagnostics, a useful retrospective window covers 12 to 18 months of historical spend, since that is typically how far drift accumulates before anyone notices it in the close.

What size company should be asking these questions formally?

This checklist applies most directly to industrial manufacturers and distributors above $100M in revenue, where indirect spend volume and contract complexity make manual, ad hoc checking unreliable.

Is this a legal question or a finance operations question?

It is primarily operational: matching billed amounts to contracted terms. Where a contract dispute or regulatory question arises from what is found, that requires separate legal review; this is general information, not legal advice.

What's the fastest single question to add to an existing AP review?

Ask which contract clause, not which PO, authorizes each rate on the invoice. That one question exposes whether AP is checking price against contract terms at all, or only against the purchase order.