Turning recovery audit findings into controls means tracing each overpayment the audit found to the gap that let it through, then closing that gap before the next payment run. The gap tends to be small and specific: a second record for one vendor, a price that never reached the purchase order, an approval someone skipped under deadline.
In Rever, Investigator traces each finding to its root cause and recommends a correction that also addresses recurrence. The controls that follow sit with named agents: Spend Guard screens bills before payment, Sentinel checks vendor-bank changes and approvals, and Auditor tests that each procedure ran. Your team approves each hold and correction from the Inbox.
What the audit report leaves open
A recovery audit report lists claims: the duplicate, the overcharge, the unclaimed rebate, each with a vendor and an amount. Your team files them, the vendors pay some, and someone files the report in a shared folder. The causes behind the claims stay where they were.
A firm paid on contingency earns from what it recovers, so root-cause work sits outside most fee arrangements. What an AP recovery audit costs covers those arrangements. The controller inherits the list and has to decide which findings point to a broken control and which were one-off errors.
Recovery audit findings into controls, sorted by cause
Group the findings by the gap that produced them, then name the control, its owner and how you will test it. Ten duplicates from one vendor with two master records share one fix. The accounts payable audit checklist gives the evidence to keep for each check.
| Finding | Common cause | Control that stops the next one | Rever agent |
|---|---|---|---|
| Duplicate payment | The same invoice keyed twice under different numbers, or one vendor with two records | Duplicate screening across bills and payments before the payment run | Spend Guard |
| Price above contract | A price change that never reached the order or the price master | Price check on each bill against the order and contract | Spend Guard, with Matcher |
| Unclaimed rebate or credit | A rebate tier tracked in a spreadsheet nobody owns | Recalculation of eligibility against actual purchases | Entitlement |
| Payment to a changed bank account | A bank-detail change accepted from an email | Independent callback to a known contact before release | Sentinel |
| Payment above an approval limit | One purchase split into invoices under the limit | Aggregate test of related payments against the limit | Sentinel |
Investigator does this sorting in Rever. It quantifies the affected population, separates one-off errors from systemic failures, and recommends the immediate correction with an owner and a due date, plus a preventive control or SOP change. If a pattern recurs, Eve proposes the SOP change and publishes it only after your approval.
Before payment: Spend Guard
Spend Guard checks for exact and near duplicates from budget to payment, including different identifiers for the same economic item, and it tells a valid recurring charge or instalment apart from an unintended duplicate. It compares unit prices with the order and the contract and separates price drift from volume and timing changes. If it finds a problem before the money leaves, it requests a hold, and the hold takes effect only after Inbox approval. The Spend Guard agent page lists the full procedure.
A duplicate held before payment needs no claim and no vendor letter. Spend Guard then verifies that the cancellation, credit or revised price took effect, and it reports estimated savings apart from realised ones.
Vendor-bank changes: Sentinel
A bank-detail change sent by email is the classic route to a payment that leaves for good. For a bank-detail change, Sentinel prepares an independent human callback to a contact the company already trusted, using known-good details, and it never relies on contact details supplied with the change. It also tests approval authority and sequencing, conflicting preparer and approver roles, and payments split under a limit. A Sentinel pass never substitutes for a person's authorisation to move funds.
Testing that the control ran: Auditor
Your auditor will ask for evidence that each control ran during the year. Auditor keeps a coverage matrix that links each procedure to its test and its latest result, reperforms selected calculations and matches, and keeps explicit tests for duplicate detection, ungated hand-backs, self-approval and unauthorised hold release. Material untested procedures cannot show as passed. Investigator then rechecks the remedy and a later sample or period to assess recurrence. Sentinel and Auditor come with Growth Pro, alongside Steward.
Identified is never confused with recovered
Rever's site puts the rule in those words. Rever tracks five outcomes and keeps each apart: value identified, value recovered, leakage prevented, cash released and errors corrected. A finding counts as recovered only when cash is received or a credit is applied, and Rever reports the honesty ratio, value recovered divided by value found.
The illustration on rever.ai is a missed rebate: $1,200,000 of eligible purchases at a 2% contractual rebate gives a $24,000 potential recovery. Entitlement checks the contract and the purchases, Evidence links the support, your team approves the claim, and Rever tracks it until the cash or credit lands. It is an illustrative example on rever.ai, not a customer result.
The duplicate Spend Guard held before payment lands in leakage prevented, and an unreversed accrual your team corrects through Journal lands in errors corrected. Neither inflates the recovery figure. The first findings arrive from the zero-day scan, which reveals initial findings with the evidence behind them.
