What Should an AP Manager Ask About Vendor Invoice Accuracy?

Executive Summary

An AP Manager's exposure is procedural, not strategic. Your team approves invoices against a purchase order and a receipt. That control confirms quantity and a price field matched something. It does not confirm the price field was ever correct against the underlying contract, because the contract rarely lives inside the ERP.

The fix is not more approvals. It is a short list of standing questions your team asks on a recurring basis, not just at go-live: which vendors get audited against their actual rate card, not their last invoice; which credit memos are owed and unclaimed; which surcharges still meet the condition that justified them.

None of this requires new software to start. It requires someone naming the gap between contract and invoice as a real job, distinct from matching and coding. A CFO or Controller will ask you for the answer to these questions eventually. Better to have already asked them yourself.

1. Does three-way matching actually catch a wrong rate?

No. Three-way matching checks the invoice against the purchase order and the goods receipt: quantity, unit, and PO price agreement. It does not check the PO price against the vendor's current contracted rate card.

If the PO itself was cut at a stale or incorrect rate, the invoice passes every match test while still billing the wrong amount. The control verifies internal consistency, not contract compliance, and an AP Manager needs a separate process to close that gap.

This is a blind spot in an AP function that considers itself well-controlled. The matching engine does exactly what it was designed to do, and it is easy to assume that design covers contract accuracy because the word "match" implies it.

Ask your team directly: when was the last time someone compared a PO price field to the actual signed rate card, line by line, rather than to the previous invoice or the previous PO? If the honest answer is never, that is the finding, not a criticism of the team.

A periodic rate-card reconciliation, even a sampled one, closes a gap that daily matching cannot touch.

2. Which credit memos are owed but never issued?

A credit memo is owed whenever a vendor overbills, ships short, or applies a rebate the contract promises but the invoice omits. Vendors do not issue these on their own initiative. If your AP process only reconciles credits a vendor sends unprompted, the ones a vendor never gets around to sending simply disappear into the general ledger as accepted cost.

Ask who is tracking the gap between credits owed and credits received, by vendor, on a running basis.

Unapplied rebates and missed credit memos are a recurring category of AP recovery finding, because nobody on the vendor side is incentivized to flag them.

A practical starting question: pull your top vendors by spend and ask which of them owe a credit right now that has not been issued. This is difficult to answer without a dedicated review, because the tracking mechanism does not exist by default in an ERP.

Building that tracking mechanism, even a simple spreadsheet log tied to contract terms, is a control an AP Manager can own directly.

3. Are surcharges still meeting the condition that created them?

A fuel surcharge, a small-order fee, or an expedite charge is typically tied to a stated trigger: a diesel price threshold, an order minimum, a lead-time window. Ask whether anyone re-checks that the trigger condition still holds each billing cycle, or whether the surcharge simply continues once it starts appearing on an invoice. A surcharge that persists after its trigger has lapsed is a charge with no contractual basis behind it.

Surcharges are easy to miss because they read as legitimate line items. The invoice looks ordinary. The number is small relative to the total, and nobody questions a small surcharge sitting on top of a much larger shipment cost.

The question to ask is not whether the surcharge is present but whether its condition is still true. A fuel surcharge tied to a published diesel benchmark should move when that benchmark moves. If it has been flat for a year while the underlying index has not, the charge is worth a second look.

This is a mechanism question, not a volume question: does the surcharge respond to its own stated trigger, checked line by line rather than assumed.

4. Who owns invoice-to-contract accuracy versus invoice-to-PO matching?

These are two different jobs, and many AP organizations staff only the second one. Invoice-to-PO matching confirms internal process discipline. Invoice-to-contract accuracy confirms the vendor billed what they actually agreed to charge, which requires reading the contract itself, not the PO derived from it.

If no one on your team or in procurement owns the second job explicitly, it is not happening by accident.

Naming the second role does not require a new hire. It requires assigning the question to someone, even part-time, and giving them contract copies to work from.

Ask your Controller or Procurement Director directly which of you holds this. If the answer is a pause, that pause is the finding.

• Matching owner: Typically AP: confirms PO, receipt, and invoice agree on quantity and price field.
• Contract owner: Often nobody explicitly: confirms the price field itself reflects the signed rate card, tier, or NTE cap.
• Escalation owner: Whoever is named should flag drift to Procurement or Controller, not just code the invoice as received.

5. How would your team catch a not-to-exceed cap violation today?

A not-to-exceed clause caps what a vendor can charge for a given scope, common in contract labor, freight, and professional services contracts. Ask your team to walk through, step by step, how an NTE overrun would actually surface today. For many AP functions the honest answer is that it would not, because the cap value lives in a contract PDF outside the ERP and nothing in the payment workflow checks an invoice total against it.

This is worth testing directly rather than assuming. Pick one active contract with a stated NTE cap and ask AP to show the control point where an invoice exceeding it would be flagged before payment.

If that control point does not exist, the cap is decorative. It sits in a signed document and has no operational teeth, which means every invoice against that contract is trusted on faith rather than checked.

This is a general information point, not legal advice: whether a contract's NTE language is enforceable in a given dispute is a separate question from whether your payment process checks it operationally.

6. What should you ask before proposing a formal spend audit?

Before taking a recommendation upward, an AP Manager should be able to answer three things: which vendor categories have never had their rate cards reconciled against invoices, how large that unreviewed spend is in dollar terms, and how long it has gone unchecked. Those three answers turn a vague concern into a scoped business case a CFO or Controller can act on immediately, rather than a general worry about invoice accuracy.

The strongest internal case is built from specifics you already have access to: vendor names, spend totals, and time since last contract reconciliation. You do not need a finding in hand to justify a review, only evidence that no review has happened.

Framing it this way also protects the request from being read as a criticism of the AP team. The gap exists because contract-to-invoice reconciliation was never assigned as a distinct control, not because anyone did their job poorly.

A Controller or CFO weighing whether to commission a broader diagnostic will want exactly this scoping, so preparing it in advance shortens that conversation considerably.

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 difference between invoice matching and contract compliance?

Invoice matching confirms the invoice agrees with the purchase order and receipt on quantity and price field. Contract compliance confirms that price field reflects the vendor's actual signed rate card, tier, or NTE cap. A vendor can pass matching while still billing off a stale or incorrect rate.

Can an AP Manager start this review without new software?

Yes. A sampled comparison of PO prices against signed rate cards, a tracking log for credits owed versus received, and a checklist for surcharge trigger conditions can all start with a spreadsheet and existing contract files.

Who should own contract-to-invoice accuracy if AP does not?

It can sit with AP, Procurement, or a Controller, but it needs to be named explicitly as someone's job. Left unassigned, it defaults to nobody, because matching and coding do not cover it.

How often should rate cards be reconciled against invoices?

There is no single fixed cadence that fits every vendor. The point is that it happens on a recurring basis rather than only at contract signing, since rates, tiers, and surcharge conditions can drift after go-live without anyone re-checking them.

What is a not-to-exceed cap?

A not-to-exceed, or NTE, clause sets a ceiling on what a vendor can charge for a defined scope of work. It is common in contract labor, freight, and professional services agreements, and it only functions as a control if something checks invoice totals against it.

Why do unclaimed credit memos go unnoticed?

Vendors are not incentivized to issue a credit voluntarily. If AP only processes credits a vendor sends, an overbill or missed rebate that the vendor never flags simply posts to the general ledger as normal cost.

Does a fuel surcharge always need to be checked?

A fuel surcharge tied to a published index should move when that index moves. If the charge stays flat while the underlying benchmark changes, the trigger condition is worth re-checking against the contract.

Is this the same as a legal contract review?

No. This is an operational check on whether the payment process enforces terms already in a signed contract. Whether specific contract language is enforceable in a dispute is a separate legal question, and this is general information, not legal advice.

What evidence helps build the case for a broader audit?

Specifics already available internally: which vendor categories have gone unreconciled, the dollar total of that unreviewed spend, and how long it has been since the last check. That turns a general concern into a scoped request.