Finance teams have been offered automation for decades. Most of it moved work around rather than removing it: someone still had to check the reconciliation the tool produced, because nobody could see how it got there. An AI agent repeats that mistake unless the books themselves are the agent’s working surface, and every number it writes can be followed back to the entry it came from.

What a finance agent does well

• Reconciliation. Matching bank lines to ledger entries, explaining the breaks and drafting the journals that clear them.
• Payables. Reading invoices, matching them to orders and receipts, and preparing the payment run.
• Month-end close. Running the checklist, chasing what is missing and writing the variance commentary from the actual movements.
• Cash forecasting. Building the forecast from what is booked and what is due, with each assumption named.

Capability is a verb, an entity and a depth

A finance agent’s permissions are not “has Xero access”. They are capabilities: post a journal entry at depth 3, prepare a payment at depth 2, release a payment at depth 4. The same capability holds whatever system the books sit in, so adding a system is a new connection in the same class and changes nothing about what the agent may do.

Depth 4, moving money, is reachable only by the Finance agent, only once we grant it moving money, and only up to the working ceiling the customer sets. Above that ceiling the agent may only draft a payment; a person makes it, whatever the agent’s certificate says.

A worked case: the $4.2m invoice

An invoice for $4.2m arrives. The agent matches it to the purchase order and the goods receipt, finds the amounts agree, and drafts the payment. It is certified to prepare payments, so that part is done. Releasing it is above the working ceiling the customer set, so the chain refuses it to the agent and a person releases it, with the invoice, the three-way match and the supplier’s history already in the draft. The ledger records the draft, the refusal and the bound that refused it.

What it does not replace

Judgement on estimates, provisions, tax positions and anything that changes how the business reports stays with the finance team. The agent’s job is to make the routine work complete, traceable and fast, so the team spends its time on the decisions that need it.

The controls your auditor will test

An external auditor looking at a finance function that uses an agent will test the same controls they always have, applied to a new kind of user:

• Access. What can the agent read and write, and who granted it? The answer is its role, which lists what it may touch, and its certificate, which sets the depth.
• Segregation of duties. Can the same actor prepare and approve a payment? Not if the agent prepares and a named person releases.
• Change management. When the agent’s authority changed, who changed it and on what evidence? Certification records answer this with dates.
• Completeness and accuracy. Can every figure in the reconciliation be traced to a source entry? It can, if the agent writes nothing it cannot trace.
• Evidence retention. Is the record of what happened, including holds and refusals, kept for the retention period? It is, on the ledger.

Month-end, before and after

Before: the close starts on day one with a checklist, a shared drive and a chase. Bank reconciliations wait for statements, accruals wait for people to remember them, and the variance commentary is written on the last night from memory.

After: the agent reconciles daily, so day one starts with breaks already explained. It chases missing items as soon as they are due, drafts the accruals it can support from booked data, and writes the first draft of the commentary from the actual movements. The finance team reviews, adjusts and signs. The close is not automated; it is prepared, which is the part that took the time.

Choosing the first capability

Start with bank reconciliation. It is high in volume, every output can be checked against a statement, and mistakes are caught before they reach the books. Accounts payable matching usually comes second. Payments come last, and above the working ceiling you set they stay with a person, however good the record becomes.

Working across systems and currencies

Finance teams rarely run on one system. Because capabilities are defined against entities rather than vendors, the agent reconciles a bank feed in one currency against a ledger in another the same way it does within one system. A group with entities in several countries gets one record of what the agent did across all of them.

Questions people ask