Can three-way match catch rebate gap?

Executive Summary

Three-way matching answers one question: does this invoice match what was ordered and received, at the price on the PO? A rebate obligation lives somewhere else entirely, in a separate clause that references cumulative volume or spend across a period, not a single transaction. Three-way match has no mechanism for tracking a running total against a threshold, and no trigger that fires when that threshold is crossed.

That mismatch is structural, not a gap in effort. The control was built to stop a bad line item on one invoice. A rebate gap does not show up on one invoice: it is the absence of a credit memo that should exist across many. Nothing in a three-way match looks for something that is missing.

What actually closes the gap is a separate process that reads the rebate clause, tracks the qualifying metric against the contract's period, and checks whether a credit was issued when the threshold was met. That is contract compliance work, not invoice matching, and it runs on its own schedule.

1. What does three-way match actually check?

Three-way matching compares three documents for one transaction: the purchase order, the receiving record, and the invoice. It confirms that the vendor billed for what was ordered, that the goods or services were actually received, and that the price on the invoice matches the price on the PO. It is a control against overbilling and phantom charges on a single transaction.

It says nothing about obligations that span multiple transactions over time, which is exactly where a rebate clause lives.

The control runs at the invoice level because that is where AP systems are built to operate. Each invoice arrives, gets matched against its own PO and its own receipt, and clears or gets flagged based on that one comparison.

A rebate clause does not attach to a single invoice. It attaches to a period: a quarter, a contract year, a rolling twelve months. The metric it tracks, cumulative volume or cumulative spend, only has meaning once you sum across many invoices.

Three-way matching has no field for cumulative spend to date and no step that asks whether a threshold defined elsewhere in the contract has been crossed. It was not built to, and extending it to do so would mean rebuilding it into something else.

This is why a rebate can go unclaimed for a full contract year while every invoice that fed into it passed three-way match cleanly. The invoices were correct on their own terms. The credit they should have added up to was never checked against.

2. Why does a rebate gap slip past invoice-level controls?

A rebate gap slips past invoice-level controls because it is an absence, not an error. Three-way match is built to catch a wrong charge on a document that exists. A missed rebate has no document: there is no invoice line for a credit that was never issued, and nothing for the matching engine to flag.

The gap only becomes visible when someone compares actual purchasing activity against the contract's rebate schedule directly, independent of any single invoice.

Every control designed around matching documents shares this blind spot. It can only evaluate what was submitted. A missing credit memo produces no submission, so there is nothing on either side of the match to compare.

Compare this to an overbilled accessorial charge, which does leave a trace: a line item on the invoice that a reviewer can price against the contract's rate table. A rebate gap leaves no equivalent line item anywhere. The evidence it should have produced simply does not exist.

Finding it requires starting from the contract's obligation and working forward, not starting from the invoice and working backward. That is a different direction of check entirely, and it is why the two controls catch different things by design rather than by oversight.

3. What would a control actually have to check to catch it?

Catching a rebate gap requires three separate elements: the rebate clause itself, read for its qualifying metric and threshold; a running total of that metric across every relevant invoice in the contract period; and a comparison of whether a credit memo was issued once the threshold was crossed. None of the three sits inside a purchase order or a receiving record, so no control built around those two documents can perform the check without adding this logic on top.

Bringing these pieces together means treating the rebate as a standing obligation to be checked, not a line item to wait for. That reframing is the entire difference between an invoice-level control and a contract-level one.

A. Reading the clause

Rebate terms sit in the contract document itself, often in an addendum or a pricing schedule attached separately from the master agreement. The threshold might be a unit volume, a dollar spend, or a tier that steps up partway through the year. Someone or something has to extract that condition before any tracking can start, because the ERP has no native field that stores it.

B. Tracking the running total

Once the metric is known, it has to be summed across every invoice in the period, not evaluated invoice by invoice. This is arithmetic a general ledger can support but does not perform on its own: nothing runs it automatically against a rebate threshold unless it is configured specifically to do so.

4. Is contract compliance auditing different from AP matching?

Yes. AP matching checks a transaction against its own supporting documents at the moment it is processed. Contract compliance auditing checks accumulated activity against contract-wide terms, including rate cards, volume tiers, rebate clauses, and surcharge schedules, over the life of the agreement.

The two controls answer different questions, run on different schedules, and require reading different source material: one reads the PO and receipt, the other reads the contract text itself.

AP matching is transactional and near-real-time. It runs as invoices arrive and clears them for payment within days.

Contract compliance auditing is periodic and retrospective by nature. It has to wait for enough activity to accumulate before a threshold-based clause like a rebate can even be evaluated, so it runs on the contract's own cadence rather than the AP department's.

The two are complementary, not competing. A business that runs only AP matching has full coverage of transaction-level errors and no coverage of period-based ones, regardless of how well the matching control performs its own job.

5. How can an AP or finance team check for a rebate gap without new software?

Pull every contract with a rebate or volume incentive clause and list the qualifying metric and threshold for each. Sum the actual purchasing activity against that metric for the period the clause covers. Check the vendor's credit memo history for that same period.

If the threshold was crossed and no matching credit appears, the rebate was earned and not applied. This is a spreadsheet exercise: the constraint is finding every applicable clause, not the arithmetic once found.

The hardest part of this exercise is rarely the math. It is locating every contract that contains a rebate provision in the first place, since these clauses are often buried in an addendum, a side letter, or a pricing amendment that was never filed alongside the master agreement AP staff work from day to day.

Once the clause is in hand, the calculation is straightforward: total the qualifying purchases for the period, compare against the threshold, and check the vendor's issued credits for a match. A spreadsheet with one row per contract handles this without any new tooling.

The work does not scale well by hand across a large vendor file, which is why it tends to get done once, retrospectively, rather than as a running check. That is a resourcing problem, not a technical one.

6. Where does a rebate gap fit relative to other drift types?

A rebate gap is one of several drift types that live outside what invoice-level matching can see. Volume tier misapplication and minimum commitment shortfall share the same shape: both depend on activity summed across a period rather than a single transaction. Duplicate payment and accessorial charge creep, by contrast, are visible on individual invoices and closer to what three-way match is built to catch.

Knowing which category a drift type falls into determines which control has to find it.

Grouping drift types this way is a matter of mechanism, not severity. A period-based obligation like a rebate clause or a volume tier needs a control that reads the contract and tracks a running total. A transaction-level error needs a control that reads one invoice against its own supporting documents.

This is also why a contract compliance audit and an AP recovery audit are usually run as separate workstreams inside a broader review: they read different source material and answer different questions, even when looking at the same vendor.

• Period-based drift: Rebate gap, volume tier misapplication, and minimum commitment shortfall all depend on activity summed across a contract period, so they need a control that reads the contract and tracks a running total.
• Transaction-level drift: Duplicate payment and accessorial charge creep show up on a single invoice, so a document-matching control like three-way match is positioned to catch them.
• Mixed visibility: Missed credit memo can arise from either category, since a credit can be owed for a single transaction error or for a period-based threshold like a rebate.

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

7. Frequently Asked Questions (People Also Ask)

Does three-way matching check rebate clauses at all?

No. Three-way matching compares the purchase order, receipt, and invoice for a single transaction. A rebate clause is a period-based obligation tracked across many transactions, which sits outside what the three documents in a three-way match can show.

Why doesn't my ERP flag a missed rebate automatically?

Most ERP systems post rebate credits only when a credit memo is manually entered against a vendor. If the vendor never issues that memo, there is no transaction for the system to record or flag, so nothing appears missing from inside the ERP.

What documents do I need to check for a rebate gap?

You need the contract or pricing addendum containing the rebate clause, a summary of purchasing activity against the metric it references for the relevant period, and the vendor's credit memo history for that same period. Comparing the three shows whether an earned credit was ever issued.

Is a rebate gap the same as a missed credit memo?

They overlap but are not identical. A missed credit memo can result from any unapplied credit, including a pricing correction or a returned-goods credit. A rebate gap specifically means a volume or spend threshold in the contract was crossed and the resulting rebate credit was never issued.

Can accounts payable staff catch this during normal invoice processing?

Invoice processing evaluates one invoice at a time against its own PO and receipt, so it has no natural point at which to check a cumulative contract-wide threshold. Catching a rebate gap requires a separate review that looks across invoices for a vendor over the full contract period.

How often should a business check for rebate gaps?

The check should run at least once per contract period, aligned to whatever cadence the rebate clause specifies, such as quarterly or annually. A clause with a rolling threshold needs more frequent review, since the qualifying window moves continuously rather than resetting at fixed points.

Does this only affect large vendors?

Rebate clauses can appear in agreements of any size, but the qualifying threshold and the resulting credit tend to matter more where the underlying spend volume is large enough for a rebate tier to be meaningful in dollar terms.

What is the difference between a rebate gap and volume tier misapplication?

A rebate gap is a rebate that was earned and never credited. Volume tier misapplication is a pricing tier that should have stepped down as volume increased but was never applied to the invoiced rate. Both depend on cumulative volume tracking rather than a single-invoice check.