How to Build an AI Agent for Reconciliations

A reconciliation agent is only trusted if you can show why it matched. This walks through the data it needs, how to test match accuracy against a known month, and where a reviewer approves before anything posts. AI for month end close.
- A reconciliation agent has five building blocks: data ingestion, a matching engine, an exception workflow, auto-clearing with controls, and an immutable audit trail.
- Start with deterministic matching rules (amount, date, reference) and layer AI fuzzy-matching on top to catch the messy 10-20% that rules miss.
- Auto-clearing must be governed by confidence thresholds and materiality limits, so the agent only posts what it can defend and routes everything else to a human.
- Exception handling is where the agent earns its keep: it groups, explains, and proposes a resolution for each break rather than just listing it.
- ChatFin builds these agents on top of your existing ERP, NetSuite, SAP, Acumatica, Oracle, so reconciliations run continuously without a rip-and-replace migration.
Bank, GL, subledger, and intercompany reconciliations all follow the same shape: pull two (or more) sources of truth, match them, investigate what does not agree, and document the outcome. That structure is exactly what an AI agent is good at, a well-defined, high-volume, rules-plus-judgment workflow where most items are obvious and a few need reasoning.
The goal is not to remove the controller from reconciliation. It is to remove the controller from the 80-90% of matches that are mechanical, so their attention goes entirely to the exceptions that actually carry risk. This guide breaks the build into seven sequential steps you can follow on any ERP.
Step 1: Map the Reconciliation and Its Sources
Before building anything, define exactly what is being reconciled and where the data lives. A bank reconciliation compares the bank statement to the GL cash account. A subledger reconciliation ties AP, AR, or fixed assets back to their control accounts. Intercompany reconciliation matches the receivable on one entity to the payable on its counterpart. Each has different sources, different keys, and different tolerances.
No room for creativity here
A reconciliation agent has one acceptable behaviour: apply the same rule to the same data and get the same result. Anything inventive is a finding.
When you are creative in accounting or finance, most of the time you go to jail.
Chris Ortega, on the AgentCFO podcast
That is why mapping the sources comes first. An agent can only be consistent about a reconciliation someone has defined precisely.
Step 2: Build the Data Ingestion Layer
The agent needs clean, normalized data from both sides before it can match anything. The ingestion layer connects to the bank, the ERP, and any subledgers, then standardizes everything into a common schema, dates, amounts, currencies, and reference fields aligned regardless of source format.

Step 3: Design the Matching Engine
The matching engine is the core of the agent, and it works in layers. Start deterministic, then escalate to AI only where rules fall short.
Layer 1, Deterministic rules
Match on exact criteria first: amount, date, and reference number. These one-to-one matches clear the bulk of volume instantly and are fully explainable, which auditors require.
Layer 2, AI fuzzy matching
For the messy remainder, partial references, split payments, batched deposits, transposed digits, or timing differences, AI scores candidate matches on similarity and proposes the most probable pairing with a confidence value. This is where one-to-many and many-to-many matches get resolved.
"The point of an AI matching engine is not to match everything, it is to match everything that is obvious, so the team only ever looks at what is genuinely unclear."
Step 4: Set Auto-Clearing Rules and Controls
Once items are matched, the agent decides which it can clear on its own and which it must escalate. This is governed entirely by controls, not by the model's enthusiasm. A match clears automatically only when it exceeds a confidence threshold, falls under a materiality limit, and violates no policy rule. Everything else routes to a person.
“The close process can be automated 80 to 90 percent. Automate everything, but still have the transparency and visibility for a controller to see where things are.”
Step 5: Build the Exception Handling Workflow
Unmatched and low-confidence items are the real work. A good agent does not just dump a list of breaks, it investigates each one. It groups related exceptions, retrieves supporting context, classifies the likely cause (timing difference, missing entry, error, fraud signal), and proposes a resolution for the reviewer to approve or override.
Step 6: Post to the ERP and Lock the Audit Trail
Approved clearings and adjusting entries are posted back to the ERP automatically, no re-keying. Every action the agent takes is recorded: what was matched, on what rule, at what confidence, who approved it, and when. That immutable trail is what turns automation into something an auditor will accept.

Step 7: Monitor, Tune, and Move to Continuous Reconciliation
Once live, the agent improves with use. Track auto-clear rate, exception volume, and time-to-resolve, then tune thresholds and rules as patterns emerge. Over time the reconciliation stops being a month-end event and becomes continuous, balances are matched daily, breaks surface the moment they appear, and the close shortens because there is nothing left to catch up on.
Build Your Reconciliation Agent on the ERP You Already Run
ChatFin deploys reconciliation agents for bank, GL, subledger, and intercompany matching directly on your existing ERP, ingesting the data, matching under your rules, auto-clearing what is clean, escalating the rest with a proposed resolution, and leaving a complete audit trail behind every action.
A reconciliation that runs continuously and clears 80-90% of items untouched is not just faster, it is a shorter close, a calmer audit, and a finance team focused on exceptions instead of ticking and tying.
Related Articles
What Should an AI Reconciliation Tool Do?
An AI reconciliation tool takes two or more sources, such as a bank feed and the general ledger, matches the items that agree, and explains the ones that do not. Rule-based reconciliation software handles exact matches well and leaves everything else as a list. The AI layer groups the leftovers, suggests the cause and proposes the entry that would clear them.
Whether you build or buy, test it on a month you have already closed and know the answers for. Check that every match shows the rule or score behind it, that low-confidence items go to a reviewer, and that nothing posts to the ledger without an approval. A tool that cannot explain its matches will not satisfy an auditor.
Caitlin Haberberger, CFO of Verdant, on reconciliation work.
“Easy, low hanging fruit is just lots of things where you're matching things together to reconcile. Whether it's expense reporting or things like that, reconciling data between different systems. Gosh, I'd love to not be spending that kind of time.”
Reconciliations Where an AI Agent Pays Off
Beyond the standard bank rec, these are the matches that eat time when done by hand.
- Payment processor payouts. One deposit covers a day of card sales net of fees and refunds. The agent splits it across the underlying orders and posts the fee, so the accountant is not rebuilding the payout in a spreadsheet.
- Intercompany balances in two currencies. One entity carries the receivable in dollars and its counterpart carries the payable in euros. The agent restates both at the agreed rate and shows what difference is left.
- Card statements against expense reports. Statement lines are matched to submitted expenses, and a charge with no report or receipt goes back to the cardholder to explain.
- Subledger that does not tie to the control account. The AP aging and the GL balance differ because a manual journal hit the control account directly. The agent points to that entry, so the difference is explained rather than hunted.
- A bank statement with a hiccup. A duplicate line or a missing day in the feed is flagged as a data problem instead of being forced into a match. The accountant knows to call the bank rather than adjust the ledger.
Jason Yocum, a fractional CFO and former CFO of Vivino, on AI and the ERP.
“I think it's ironic that these big ERPs, there's a lot of tools that we buy externally from Oracle to sit on top of NetSuite to do the things that NetSuite can't do. And maybe AI will just be one more layer that sits on top of our ERP system.”
Samantha Singer-Guindi, a hospitality CFO and controller, on bank statements and problem solving.
“It's easy to feed in a bank statement, but if there's a hiccup, are they gonna have the know-how to answer those tough questions or do that problem solving?”
Quick Answers on AI Reconciliation Tools
What is an AI reconciliation tool?
Software that compares two or more data sources, such as a bank statement and the ledger, matches what agrees, and uses AI to investigate and explain the differences. It proposes the resolving entry and leaves approval to a person.
How is an AI reconciliation tool different from rule-based reconciliation software?
Rule-based software matches on exact criteria such as amount, date and reference, and lists the rest. An AI tool also scores similar items, handles one-to-many matches and timing differences, and suggests why a break exists.
Should we build a reconciliation agent or buy an AI reconciliation tool?
Building gives control over rules and data but needs engineering time to maintain. Buying gets you running sooner. Either way, test on a closed month and require an audit trail for every match.
Which reconciliations can AI handle?
Bank, credit card, payment processor, subledger-to-control-account and intercompany reconciliations all follow the same pattern of matching two sources and investigating differences. Account reconciliations that depend on judgment, such as estimates, still need an accountant.
How do I know the AI matched correctly?
Each match should show its rule or confidence score and link to the source documents. Review a sample of auto-cleared items every cycle, and track how often reviewers overturn a match.
Does an AI reconciliation tool need to replace the ERP?
No. It reads from the ERP and bank data and posts approved entries back. What matters is that the posting is controlled, so only approved clearings reach the ledger.
Should a reconciliation agent run daily or only at month end?
Daily or real-time. The ingestion layer pulls scheduled feeds from bank APIs and ERP tables so reconciliation runs continuously, not just at month end. Running daily is what lets a day-five close replace the day-fifteen scramble, because less work is left waiting when the period ends.
Questions engineers ask when building a reconciliation agent
What does an AI reconciliation agent actually need to run?
Read access to the two records being compared, usually a general ledger and either a subledger or an external statement, plus whatever identifies a transaction on each side. Nothing is written back to produce a first result, which is what makes a pilot possible without a change programme.
Why do matching rules break in production?
Because they are written against clean examples and meet identity and timing problems. The same transaction carries different references in each system, arrives on different days, is split across several lines on one side, or is netted on the other. Rules that match on a reference field fail on all four.
Should the agent post the correcting entry?
No. Matching, ageing and classifying are determinate and safe to automate. Accepting a residual, agreeing a write off and concluding a balance is fairly stated are judgements. Proposals go to a person to release, which is also what keeps the audit trail meaningful.
How do you know the agent is right?
By what it hands back. A finding that cites the ledger lines and documents it came from can be checked in seconds. A confidence score cannot be checked at all, only trusted or ignored, and in practice it gets ignored.