How to onboard a new financial controller to an AI agent workspace

Your new financial controller takes over approval of the agents' journals and reconciliations, so their first two weeks should teach what those agents may post alone, what they must hold, and how to read the record behind each entry. By the end they approve held entries, run the correction review and know every agent's certificate date.

What has the controller inherited?

In a finance team that runs agents, the agents typically reconcile bank and balance sheet accounts, propose matches and draft adjusting journals (depth 2), prepare accruals and prepayments from contract registers, draft variance commentary for management accounts, and post routine recurring journals within set limits (depth 3) where certified. Nothing material posts without a person, and period-end sign-off is the controller's.

A new controller is not taking over a team that keys journals. They are taking over a set of agents, the people who review them, and the evidence trail that auditors will read. How the role shifts is set out in what changes in a financial controller's day when AI agents arrive. The finance director owns onboarding, ideally timed so the controller's second week includes part of a month-end close.

What does the plan look like?

1. Day 1. Person (finance director): hands over the agent register: each finance agent, its capabilities, its certified depth, certificate expiry and owner.
2. Day 1 to 2. Agent, depth 1: summarises the last two closes from the record: entries drafted, held, approved, corrected, and by whom.
3. Day 2 to 3. Person (new controller): reviews the customer limits set on each agent: materiality thresholds, accounts the agent may not post to, approval routes.
4. Day 3 to 4. Person (new controller): traces three entries end to end: from source document through the agent's draft and verdict to approval and posting, reading provenance at each step.
5. Day 5. Person (new controller): meets the agent owner to agree the correction review rhythm and the re-certification calendar.
6. Week 2. Person (new controller): approves held entries during the close, with the outgoing controller or the finance director checking a sample.
7. End of week 2. Person (finance director): confirms handover of approval rights in writing.

What should the controller look for in the trace?

Provenance of every input. The bank feed and the general ledger are sealed sources. A supplier statement is signed if it came through a verified portal; an emailed spreadsheet is external. An accrual built on an emailed estimate from a budget holder is resting on a declared figure, and the controller should know that before approving it.

Which bound decided. When an entry was held, the record names the bound: materiality limit, restricted account, unfamiliar counterparty, missing source. A controller who reads this learns where the agent's limits sit faster than from any document.

Segregation of duties. The person who corrects an agent's entry should not be the only person approving the change to that agent's brief. Check that this holds in the team.

What does the controller own from week two?

Approvals, the correction review and the certificate calendar. Every agent certificate lapses after 90 days, and a re-certification that clears no depth drops the agent to depth 1 the same day, so every recurring journal comes back to people. A controller who does not know these dates risks the drop landing mid-close. Plan re-certification for quieter weeks.

The correction review matters as much. Reviewers correct the agents' drafts every close. Without a monthly slot to turn those corrections into changes to the agents' brief, sources or bounds, the same errors recur. The controller chairs this.

Which controls and evidence should onboarding leave?

• Reviewed limits. Evidence: the controller's sign-off on each agent's customer limits.
• End-to-end traces. Evidence: the three traced entries and notes.
• Sampled approvals in week two. Evidence: the sample and the reviewer's comments.
• Certificate calendar. Evidence: agent expiry dates against the close calendar.

What should the controller measure from then on?

Entries held per close and the share approved unchanged. Corrections by reason code, and repeat corrections after changes. Days to close. Audit queries on agent-drafted entries. And any approval made by someone without a current certificate, where the business has tied approval rights to one.

Where does it usually go wrong?

Starting mid-close with no preparation. A controller thrown into approvals before reading the limits approves by instinct, and instinct from a manual team does not tell you why the agent held something.

Ignoring the record. Auditors will read it. A controller who has not read it cannot answer their questions.

Letting re-certification fall on the close.

Credit control is often the first team a new controller depends on for cash; the plan for a new credit controller and what changes in a credit controller's day show their side. The AI agent training plan template for financial controllers sets the learning out, and the wider approach is in training teams for AI agents.

Where the Academy fits

Pryme Intelligence Academy's Operator track covers how a governed agent decides, human review, reading the workspace and running the rhythm, which matches the controller's new job closely. Certified Pryme Operator is valid 12 months, renewed through an update module and a short quiz, and anyone, including auditors, can check it at source through VerifyDoc.ai.