2 Reconciliation AI Agents, Live in Production.
2 live agents automate reconciliation within finance. They all run on a schedule. Each one publishes the inputs it needs, the steps it works through and what it hands back.
-
Bank Transaction Matching
Match bank transactions to ledger entries and leave the genuinely unmatched genuinely unmatched — no forcing, no plugging the difference to make the reconciliation close.
-
Transaction Classification
Classify bank transactions to the right account and cash flow category from what the narrative actually supports — and route the ambiguous ones to a person instead of defaulting them to sundry.
Leaving the genuinely unmatched genuinely unmatched
Bank reconciliation is the process most vulnerable to a well-intentioned shortcut. The objective as everyone experiences it is to make the reconciliation close, and there are several ways to do that which are not the same as reconciling: match on amount alone and accept a coincidence, plug a small residual to a difference account, or classify an unclear transaction to sundry and move on. Each is a rounding error in isolation. Repeated monthly across a large transaction population, they produce a set of accounts where nobody can explain a specific balance, and the investigation to unwind it costs far more than the original resolution would have. Classification has the same failure mode: the narrative on a bank line is often genuinely ambiguous, and the fastest resolution is a default rather than a question.
These agents are built around refusing the shortcut. Bank Transaction Matching matches transactions to ledger entries and leaves the genuinely unmatched genuinely unmatched — no forcing, no plugging the difference to make the reconciliation close. The output is therefore sometimes less tidy than a manual one, and that is the point: the untidiness is information. Transaction Classification classifies bank transactions to the right account and cash flow category from what the narrative actually supports, and routes the ambiguous ones to a person instead of defaulting them to sundry. The volume of judgement calls a human has to make does not go to zero; what changes is that each one arrives already isolated, with the evidence attached, rather than hidden inside a population of two thousand rows.
What this moves
- Reconciliations closed with a plug
- Unmatched items stay unmatched rather than being forced or written to a difference account, so the reconciliation reports a real state.
- Transactions defaulted to sundry
- Ambiguous narratives are routed to a person instead of falling into a catch-all account, which is where classification errors currently accumulate untraced.
- Time to close the bank reconciliation
- Matching runs against the full population rather than by sampling, so the manual effort concentrates on the genuine exceptions.
Finance
How AI agents handle reconciliation
Drawn from the 2 agents above — what they require, how they run, and what comes back.
What they need
- Bank statement
- Ledger entries
- Matching rules
- Unclassified transactions
- Classification rules
- Settings
What comes back
- Does it reconcile
- Reconciliation note
- Unmatched both ways
- Bank line to ledger entry
- Classified with confidence
- Review note
- Needs a person
- Transaction by transaction
How they run
- Runs on a schedule
- 2
- Steps per run
- 4
- Credits per run
- 7
Where reconciliation fits in finance
Matching, reconciling and chasing is high-volume work with very little judgement in it. Moving that to agents is what turns a compressed close into a normal week.
Next Step
Deploying reconciliation agents
These run as-is against the inputs listed above. Most deployments adapt one — a different source system, a different tolerance, a different approval path. The first call establishes which.