The exception agent
A break is not an alert. It is a question with an answer.
Reconcile tells you a line did not match. Resolve tells you why, what it probably is, what the journal entry should look like, and what evidence it used to get there — so the reviewer is approving a conclusion instead of starting an investigation.
9 min
median time from break raised to break closed
What it does
Inside Resolve
Reason codes, not free text
Every exception is classified against a versioned library — duplicate instruction, unapplied return, unbooked chargeback, aged unsettled, unidentified cash. Codes are stable, so you can trend them.
Root cause in plain language
Two sentences that a new analyst and an external auditor can both read, naming the specific records and the specific signal that produced the classification.
Drafted journal entries
Balanced double-entry postings against your own chart of accounts, ready to approve. Rejecting one teaches the rule; accepting three times makes it eligible for unattended posting.
Evidence, always attached
The statement narrative, the transaction code, the search window, the passes attempted. Nothing is asserted without the record that supports it.
The model never decides
Language models propose classifications and write explanations. A deterministic layer verifies the arithmetic and the account mapping before anything reaches a reviewer.
Ageing that means something
An instruction one day inside its clearing window is timing. The same instruction seven days later is a break. Resolve knows the difference per channel and stops paging you about the first.
In depth
How a proposal earns the right to post itself
Automation you cannot switch off is a liability. Resolve earns autonomy one reason code at a time, and only ever inside limits your team sets.
- 01A new reason code always requires human approval, whatever the model's confidence.
- 02After three consecutive approvals with no edits, the code becomes eligible for unattended posting.
- 03Eligibility is still bounded by a value ceiling and a daily volume cap that you set.
- 04Any edit to a proposal resets the counter and feeds the correction back into the rule.
- 05Classes that touch customer money — chargebacks, returns, unidentified cash — are never eligible.
Specification
- Reason-code library
- 34 codes across 6 families
- Explanation latency
- Under 2s per exception
- Posting format
- Balanced double entry, your chart of accounts
- Model policy
- Proposes and explains only; never authorises
- Feedback loop
- Every edit becomes a rule adjustment
“We were closing on the eleventh working day and everybody had quietly accepted that. The thing that actually changed was not the match rate — it was that every break arrived with a reason code and a drafted entry, so the queue stopped being an investigation and started being a review.”
Aitor Zubeldia
Head of Finance Operations, Kestrel Pay · Ireland