The idea
What that means for a mid-market finance team, and why the AI should never post to your ledger.
Record what fits. Resolve what doesn’t.
Thirty minutes, your data, no slides.
The idea in full
Every business has a system of record, the ERP, and it accepts a transaction only once it fits: an invoice matched to an order and a receipt, a payment matched to the invoices it settles. Reality doesn’t arrive like that. It arrives as PDFs in an inbox, remittances that don’t add up, deliveries that differ from what was ordered. So in most mid-market manufacturers and distributors, the finance team’s real job has quietly become making reality fit the ledger, by hand, and the part that doesn’t fit is where their week goes.
Almost every business has a system of record. Almost none has a system of resolution, the place where everything that doesn’t fit gets sorted before it can be recorded.
Today that system is a person, an inbox and a spreadsheet, and it is why finance headcount rises with revenue.
Apridata built Opnua to be that system. Rules handle what fits, because a rule can be audited and a rule never has a bad day. An AI agent works what doesn’t: it reads the correspondence, contacts the supplier or the customer, resolves the mismatch and logs every step. It never posts to the ledger, and the ERP stays exactly where it is.
We do this because the most qualified people in a finance function shouldn’t be its integration layer. They should be doing the analysis the board keeps asking for.
Rules record. AI resolves. Accountants analyse.
The cost
How many people would your finance team need if every invoice, payment and remittance arrived already matching the ledger?
The gap between the answer and today’s headcount is the resolution tax.
What we think
Rules handle the routine majority, because a rule can be audited. AI belongs on the judgment work: the exceptions and the investigations. Start with measurable problems, not another technology project.
Headcount rising with revenue is the sign that resolution is being carried by hand. Transactions are absorbed by rules and AI; the team grows in analysis, not processing.
For the controller this is control: a ledger trusted sooner. For the director it is commercial: capacity moved from producing information to influencing decisions.
The boundary
Rules post what fits. The agent investigates what doesn’t and recommends a resolution. A person approves it. Every step is logged, so the audit trail shows what was read, which policy applied, what was recommended and who said yes. The AI has no write access to your ledger, and that is a design decision, not a setting.
Deterministic, auditable, and the same answer every time. If it can be a rule, it is a rule.
Reads the correspondence, works out what happened, proposes a resolution with its reasoning and evidence.
Accepts, changes or rejects it. Only then does it post. Every step, by whoever or whatever took it, is logged.
The agent has no write access to your ERP. That is a design decision, not a setting.
Where month-end leaks
Each carries the question that turns agreement into a number. The self-assessment asks all five and does the arithmetic in your browser.
And get keyed into the ledger by hand.
How many documents did someone type into your system last month, and what else could that person have done?
The three-way match clears the clean cases. The rest live in email, phone calls and memory.
Where do your mismatched invoices actually live while they wait, and who knows they’re there?
Payments arrive short or combined. Unallocated cash sits on the account for weeks.
How much cash is sitting unallocated right now, and how long does a remittance that doesn’t tie out take to clear?
Or one spreadsheet. Disputes stall because the paperwork is in three places.
If your credit controller was out for a month, what would happen to your debtor days?
The close lands on the day it lands because of how many bridges there are.
What day does your close land, and which spreadsheet is the reason it isn’t earlier?
Five minutes, your own numbers, nothing leaves your browser unless you send it.
Put a number on it
The gap between that day and today is your resolution tax. Thirty minutes with your data, no slides, and a plain answer on whether a pilot is the right next step.