In-period rebate software or a recovery audit
Both look for rebate leakage: money a supplier contract promised that never arrived. The difference is when they look, and that decides what can still be done about it.
Last reviewed . Written by Techinquest, which makes the first kind. We have tried to describe the second fairly, and we say when an audit is the better call.
The two approaches
- In-period rebate software
- Software your team runs through the year. It calculates what each supplier contract has earned from your own purchase data while the period is still open.
- A recovery audit
- A review of closed years of paid history, usually by an outside firm, looking for money owed back. Rebates are one part of it. Duplicate payments, tax and other accounts payable errors are others.
Where each approach acts
One contract year, from signature to the audit that may follow it. Found while the period is open, a missed tier can still be reached. Found after the period closes, what was earned can only be claimed.
One contract year
Signature to the audit that may follow it
Contract signed
Tiers, commitments, dates and forms are agreed in writing.
- In-period software
- Loads the agreement as written, so every later check starts from the clause itself.
Purchasing
Purchases post through the period, direct and through distributors.
A missed tier can still be won from here until the period closes.
- In-period software
- Recalculates each rebate from your own purchase files as they load. Checks run on a schedule and on demand.
A tier crossed or a commitment slipping
Purchasing reaches a threshold, or falls behind a promise.
The last point to act: the tier can still be reached and the commitment still met.
- In-period software
- Flags a next tier close enough to reach, or a commitment going short, with the purchasing it would take and what it is worth.
Quarter close
The measurement period ends, and the tier is decided.
The window closes. From here, what was earned can be claimed and what was missed stays missed.
- In-period software
- Books the quarter as earned or lost, with the reason written down for each figure, including a zero.
Payment due
The rebate is owed by the date the contract sets.
- In-period software
- Flags the payment as overdue once the contract’s date passes.
Supplier statement
The supplier pays, or does not, by its own calculation.
- In-period software
- Proposes how a recorded payment splits across the periods it covers, and prepares a statement of any difference, with invoice-level evidence, for your team to send.
Year end
Annual tiers and true-ups settle, and the books close.
- In-period software
- Books annual tiers and year-end true-ups the same way, while the people and records behind them are still at hand.
Recovery audit
Often a year or more later, across several closed years.
- In-period software
- Already calculating the next year.
- Recovery audit
- Looks back over several closed years for rebates paid short, and for duplicate payments, tax and other accounts payable errors.
Can a missed tier still be won?
Stage 1: Nothing earned yet
Stages 2 to 3: Yes. Purchasing can still change, and a slipping commitment can still be met.
Stages 4 to 8: No. What was earned can still be claimed. What was missed stays missed.
In-period software, scheduled and on demand
Stage 1: Loads the contract as written
Stage 2: Re-runs as purchase files load
Stage 3: Flags the gap and what it is worth
Stage 4: Books the quarter as earned or lost
Stage 5: Flags the payment once it is late
Stage 6: Checks the payment against what was earned
Stage 7: Books annual tiers and true-ups
Stage 8: Already on the next year
Recovery audit
Stages 1 to 7: Not involved yet. Later, it looks back over all of these stages.
Stage 8: Reviews closed years of paid history
Side by side, one question at a time
What each approach does with the same contract. Products and engagements differ, so read each line as typical rather than universal.
| Question | In-period rebate software | Recovery audit |
|---|---|---|
| When a gap is found | While the period is still open. Each rebate is recalculated as purchase files load, and checks run on a schedule and on demand, so a gap shows up once the purchase data that reveals it has loaded. | After the fact, often a year or more after the period closed, when the review reaches that year. |
| Whether a missed tier can still be reached | Yes, until the period closes. The team sees how far away the next tier is, what it is worth and where the volume could come from, such as off-contract spend in the same category, and decides whether moving purchases is worth it. | No. The tier was settled when the period closed. An audit can claim what was earned and not paid, but it cannot change what was bought. |
| Who holds the data and the calculation | Your team works with it directly. The contracts, the purchase files and every calculation sit in software your staff use day to day, and anyone with access can see how a figure was reached. | The auditor, for the length of the engagement. It works from extracts of your records with its own tools and reports what it finds. How much of the working you see depends on the engagement. |
| The audit trail behind each figure | Each figure should show its working: which purchases counted, which did not and why, including when the answer is zero. Ask any vendor to show you one. | Each claim comes with the invoices and contract clauses behind it, because the supplier will ask for both. An audit reports exceptions, so lines found in order are not usually written up one by one. |
| Staff time it needs | An owner. Someone loads the files, reads what is flagged and acts on it. The software does the arithmetic; people decide what to pursue and send it. | Less. The auditor does the review from extracts your team provides. Your team answers questions and helps confirm and settle what it finds. |
| What else it covers | The rebate contract and the terms around it: tiers, commitments, admin fees and prices billed above contract. It will not find a duplicate payment or a tax error. | Much more than rebates. A recovery audit can cover duplicate payments, unapplied credits, sales and use tax and other accounts payable errors, across every vendor. |
| What changes for next year | The contracts are already loaded and running, so next year is checked from its first day. A set-up fault found this year, such as a facility missing from a contract, is fixed where it starts. | A good audit report names root causes, such as a contract term never set up or one vendor paid under two records, and those fixes carry forward. Checking next year usually waits for the next audit. |
| Effect on the supplier relationship | Differences come up close to when they happen, while both sides remember the deal and the records are fresh. The conversation is about this quarter. | Claims can reach back several years, and a supplier may treat an old claim as a dispute rather than a correction. Many settle without friction. Some come down to goodwill, especially where the contract set a window for challenges. |
When an audit is the right call
Audits do things rebate software cannot, and in these situations they are the better choice.
- The years in question have already closed
- Nothing in a closed year can be reached any more. The only question left is what was paid short, and a look-back review is built for exactly that. The sooner it runs, the more of the records, and the people who knew the deals, are still around.
- There is no one to run software
- In-period software needs an owner who loads the files, reads what is flagged and acts on it. If nobody can take that on, a service that does the work will find more than a tool nobody opens.
- You want a one-off look back
- Before a renegotiation, after a merger, or simply to learn whether there is a problem at all, a single review answers the question without a standing commitment.
- You want more than rebates checked
- Duplicate payments, unapplied credits, tax and other accounts payable errors sit outside rebate software entirely. An audit looks at all of them, across every vendor.
Using both
Software for the periods that are still open, an audit for the years before go-live. They cover different ground, so running both is often the sensible answer.
- Before go-live
- A look-back review of the closed years: rebates paid short, plus the duplicate payments, tax and other accounts payable errors that rebate software does not look at.
- From go-live
- Each contract in the software is checked while its period is open, so a tier can still be reached and a late payment is flagged once it is late.
- Where they meet
- Agree who owns each contract year, so a supplier is never asked twice for the same money. Give the audit’s root causes to whoever sets up contracts in the software. If an audit later finds a gap in a year the software covered, treat it as a set-up fault to fix as well as money to claim.
Further reading
The other revenue recovery: the rebate money your supply chain already earned
Revenue recovery usually means denied claims. This is the supplier-side version: rebates and credits your purchases earned that never arrived, and how to size the gap yourself.
Seven ways hospitals lose supplier rebates they already earned
A lifecycle map of where earned supplier rebates disappear, from contract setup to the general ledger, with a test for each leak that you can run on your own data.
Rebate tier attainment: how to know where you will land before the period closes
How to read a tiered rebate ladder, project where your current purchasing pace will land, price the gap to the next tier, and decide whether closing it is worth it.
Check this year while it is still open
One supplier agreement and a recent purchase extract are enough. In a working session we load them and show what the contract has earned so far, what has arrived, and what is still open before the period closes.