Account Reconciliation Agent · Use case
How can we use an AI agent to prepare balance sheet account reconciliations on our own infrastructure?
An account reconciliation agent prepares the reconciliation of one balance sheet account for a period: the ledger balance, the items that make it up, the items that are old or have no explanation, and the supporting documents it found for each. The preparer checks and signs the reconciliation and the reviewer approves it. The agent signs nothing, clears no item, proposes no journal for posting and posts nothing.
Hundreds of accounts.
Each one rebuilt by hand at every close.
- ✗ 01At every close each balance sheet account is rebuilt from ledger extracts and spreadsheets, and the time goes on assembling the schedule, not on the items that need a decision.
- ✗ 02An old or unexplained item is carried forward month after month because it sits in a tab no one has time to read.
Where it stops for a person
Always. The preparer signs the reconciliation and the reviewer approves it.Always. It assembles and lists, it does not conclude: whether an item is explained, whether it should be written off or corrected, and whether the account is reconciled are the preparer's and the reviewer's decisions, and the two stay two people. An item it could not match is listed as unmatched; it does not guess at support.
It prepares the reconciliation.
The preparer signs and the reviewer approves.
Step · 01
The preparer names the account, the entity and the period.
Step · 02
The agent reads the balance and the entries behind it, read only.
Step · 03
It sets out what makes up the balance and matches each item to the supporting document it finds among the files uploaded.
Step · 04
It lists the items that are older than the age you set, have no support or have no explanation, with the entry behind each.
Step · 05
The preparer completes and signs the reconciliation, and the reviewer approves it.
Reads from · connectors
Your own APIs
Database
Ledger balances and entries for the account, read through your own APIs with the operations that change something left out, or from a reporting database, read only; and statements, schedules and other support, as uploaded files. It keeps to the accounts and entities the person using it may read.
Acts through · MCP servers
Nothing. It clears no item, writes off nothing, raises no journal in the ledger and marks no reconciliation as complete.
What you set up
- Import the description of the API that holds ledger balances and entries and keep only the operations that read, or connect the reporting database read only.
- Give the agent your reconciliation format and the age after which an item is listed.
- Build the agent in Katonic Studio and test it on accounts your team reconciled at the last close.
- Publish it to preparers, one entity and one group of accounts first.
Where it runs
The agent, its knowledge store and the model run on infrastructure you own or control. You choose the model and serve it yourself, so questions, documents and answers are not sent to a public AI service. Ledger entries and their support stay inside the company.
How you get it today
This page is labelled Use case: the agent is built in Katonic Studio. You describe the job, connect what is named above, add test questions and release the agent once it passes them. When the Catalog holds a tested template for this job, this page will carry the Template label and show how to take it.
Does it sign off the reconciliation?
No. It prepares it. The preparer signs and the reviewer approves, as your close procedure sets out.
Does it post a correcting journal?
No. It has no tool that writes to the ledger. A correction is raised and approved by your accountants.
What does it do with an item it cannot explain?
It lists the item as unexplained, with the entry behind it. It does not guess at a reason.