Finance and performance
Recovery Audit
Every invoice reconciled against contracts, rates, shipments, and payments, with anomaly scoring to block, short-pay, or dispute it, backed by an evidence pack.
The problem
Invoices arrive in volumes no team can check line by line. Freight bills carry wrong rates and charges, the same supplier invoice is paid twice under different references, and prices drift from what the contract says. Recovering the money later costs more than stopping it.
Who owns it
The CFO or controller, with accounts payable and procurement.
What it learns from
- Supplier and freight invoices
- Contracts, rate cards, and price agreements
- Purchase orders, receipts, and shipment records
- Payment history
- Supplier master data
How it works
Predict, decide, act, measure
The same four steps in every solution, in this order, each one visible to the team that owns it.
- 01
Detects overpayment risk on every invoice
Each invoice is reconciled against its contract, rate, shipment, and payment records, and anomaly models score what reconciliation cannot settle, such as near-duplicates and unusual charges.
- 02
Decides block, short-pay, or dispute through a policy
Thresholds by amount and confidence decide whether an invoice is paid, held, short-paid to the contract price, or disputed. Holds above a set value and every supplier dispute need a named approver.
- 03
Acts in accounts payable
Holds and short-pays land in the accounts payable workflow, and disputes go to the supplier with an evidence pack: the contract term, the record, and the difference.
- 04
Measures verified cash recovered or prevented
Only amounts verified by the supplier credit, the corrected payment, or the closed dispute are counted. False flags are tracked so good suppliers are not held up.
What it moves
The business levers
Cash recovered
Overpayments returned through supplier credits.
Cash prevented
Overpayments stopped before they are paid.
Contract compliance
Prices held to what was agreed.
Audit effort
Reviewers work the exceptions instead of sampling.
Proof
How the return is proven
The return is the verified cash recovered or prevented, net of the cost of holds that turned out to be correct invoices, stated against the return model agreed up front. Payment delays to correct suppliers are reported beside it.
What you see: the ROI readout
Every solution produces the same readout, assembled from the system's own records rather than built by hand.
Correctness
The checks the pipeline passed on your own data: leakage, point-in-time, and entity resolution.
Incrementality
The incremental effect against the holdout or equivalent design, with its confidence interval.
Return
The measured return against the investment, set beside the return model agreed before work started.
Guardrails
Complaints, cost, margin, fairness, and contact limits, each shown against its bounds.
Audit extract
Every score, action, and outcome, with the model and policy versions behind it.
Governance
What is governed
Access, approvals, and the audit trail are part of the solution, not a review step added at the end.
Identity-scoped access
Invoices, contracts, and supplier data are visible by role through your single sign-on.
Approval gates
Holds above a set value, short-pays, and every supplier dispute need a named approver.
Audit trail
Every flag, decision, and outcome is logged with the evidence behind it.
Financial controls
Segregation of duties is preserved: the identity that flags an invoice never releases its payment.
Why it holds up
Trained on your data, framed by the outcome
This solution trains models on your own data, checks every stage from data to decision, and is measured against the outcome it was built for. Because its predictive power is measured, it also shows the drivers behind the metric, so your team can fix causes as well as act on scores.
Why solutions hold upStart with one decision
Bring the problem and the systems your team works in. We scope the first solution with you, agree how its return will be measured, and run it in production with your people.