Reconciliation Agent
A break found on the day it happened usually has an obvious cause. The same break found five weeks later is an investigation.
The sub-ledger agrees to the control account every day, not every month.Matching runs continuously, so a break is found on the day it appears rather than at the close, when its cause is a month cold.
What it checks
On every invoice, not a sample.
- Sub-ledger balance against the control account, daily
- Bank lines against booked payments
- Unmatched items, with an age against each
- Breaks that are growing rather than static
What it reads, what it writes
Reads
Sub-ledger and control account balances · Bank statements · Booked payments and receipts
Writes
The break, with its age and probable cause · Matched items cleared automatically · The reconciliation trail
Where it sits in the team
Agents do not work alone. Each one hands its result to the next, so a finding raised here shows up as context downstream rather than being re-derived.
Hands to it
It triggers
When it isn't sure
A probable match is not a match. Where confidence is short of certain, the item stays open with both candidates shown — a wrongly cleared break is worse than an open one, because it stops being visible.
Any check that runs on every transaction will meet cases it cannot settle. What makes a control trustworthy is not that it never hesitates — it is that hesitation produces a named question for a person, rather than a silent pass or a silent block.
See what this one finds in your last 90 days.
One export. No connector. We come back within a working day.
$Check your savings→