Accounts payable recovery audit without the contingency firm.
We encode your vendor rules — contract rates, fuel surcharges, pass-through terms — into a continuous pre-payment audit that flags overcharges before the money leaves.
Official services partner of the platforms defining AI
NVIDIA
Anthropic
The bills keep coming. The rules live in someone’s head.
From AP inboxes we have sat inside: PE-backed services businesses running thousands of vendor invoices a month, with contract rates nobody re-checks.
Invoices arrive by email, with no PO behind them
Vendor bills land in an inbox, get keyed by hand, and routed into an ERP nobody fully trusts. First, someone works out what the bill even is.
The duplicate that looks different every time
Same vendor, same service, new invoice number, slightly different amount. Catching it means remembering every bill you already paid — thousands a month, no two alike.
Contract rates nobody re-checks
The rate sheet says one number, the invoice says another. Case-vs-each pricing, fuel surcharges, fees that appear mid-contract. Somebody has to know the item to catch it.
Pass-through charges you eat instead of bill
Fees recoverable from customers go unapplied because nobody can tie the charge to the contract clause fast enough. The margin leak is quiet, and it compounds.
The audit that shows up a year late
A contingency firm sweeps last year’s payments, takes a percentage of what it recovers, and leaves. Next month the same leaks reopen, because nothing about the process changed.
The leak is a line item, not a feeling.
What we have measured inside vendor-invoice-heavy AP organizations. Your numbers will differ — the two-week audit puts figures on yours before anything gets built.
From anonymized engagements — waste services, healthcare supply, distribution
We encode your exceptions.
No new system for your team to learn. The rules your best AP person carries in their head become the audit.
- 01
Map the rules
We write down every rule a bill gets judged by: contract rates, surcharge tables, unit-of-measure quirks, expiring credits. Tribal knowledge becomes a rule set — yours to keep.
- 02
Encode the audit
Every invoice line gets read, matched, and checked against your rules before payment runs. Violations land in a review queue — your team approves exceptions, not every bill.
- 03
Run it every week
The audit keeps pace with the inbox: overcharges flagged before the money leaves, price creep caught at the first invoice, a weekly variance report your controller actually reads.
Recovery firms find last year’s leaks. Encoded rules stop this week’s.
Contingency recovery firms audit twelve months of payments, take a percentage of what they claw back, and leave the process exactly as they found it. The leaks reopen before their invoice arrives.
Audit software ships with generic rules; your business runs on exceptions. We are neither: we encode your vendor rules; our AI reads every invoice line against them — a continuous audit inside your AP flow, no percentage of your own money.
We were eating nearly all pass-through charges. Now the surcharge shows up on the customer’s bill instead of our P&L.
Led by Peter Enestrom.
Asked by controllers and CFOs.
The straight answers, before you book anything.
Recovery firms audit payments after the fact, once a year or so, and charge a percentage of what they claw back. We encode your vendor rules into a continuous audit that flags overcharges before payment runs — a fixed fee, and the leak stays closed.
Software ships with generic rules and asks your team to adopt a new system. We encode your exceptions — contract rates, surcharge tables, unit-of-measure quirks — inside the flow you already run. Your team sees a review queue, not a new tool.
Read access to the AP inbox or invoice feed, your vendor contracts and rate sheets, and two hours a week with whoever knows the exceptions. The two-week audit produces the rule map and the payback estimate before you commit to a build.
That is the normal case. Legacy OCR reads 40–50% of fields on bills like these; the systems we build read 97–98%, because they read for meaning against your vendor dictionary, not for characters.
The two-week audit is a fixed fee, credited toward the build if you continue. Builds are scoped per workflow with a payback estimate up front — no percentage of recovery, no per-seat license.
You do. The rule set is documented and handed over, and anything we built keeps running. There is no lock-in designed into the work.
Start with one workflow.
Tell us where your team loses hours. We will come back with a straight answer on whether AI can help, what it would take, and what it would pay.