Plan on two month-end cycles, or about eight weeks. Financial controllers need roughly 18 hours of learning, but their review work clusters around the close, so the supervised period should span at least one full month end. They also own the limits the agent works within, which adds time that a clerk or analyst does not need.
Why the close sets the timeline
A financial controller's review decisions come in bursts. During the close, an agent may draft dozens of accruals, prepayment releases, reconciliations and journals in a few days. Between closes, there is far less to review. Two weeks of supervised review picked at random may land in a quiet patch and teach very little.
Controllers also carry a second job. They decide the agent's limits: which journals it may post at depth 3, what tolerance applies to reconciliations, and what is always held. That is owner work, not reviewer work, and it needs its own preparation.
What the eight weeks contain
- Weeks 1 to 2: foundations. About four hours on why agents are governed, depth, the decision chain and what the business pays for.
- Weeks 1 to 5: operator learning. About 14 hours, with extra attention on teaching the agent, reading the workspace and keeping knowledge current, such as a changed chart of accounts.
- First month end: shadow close. The controller reviews the agent's drafted close entries alongside the existing process, without relying on them.
- Second month end: supervised close. The controller makes real review decisions on held entries, checked by the finance director or a peer.
- After the second close: exam and sign-off.
What the agent drafts and what the controller keeps
| Close task | The agent | Stays with the controller |
|---|---|---|
| Bank and intercompany reconciliations | Reads balances, matches items, drafts the reconciliation (depth 2) | Unreconciled differences above tolerance |
| Standard accruals and prepayment releases | Posts within set limits (depth 3, where earned) | Judgemental accruals and provisions |
| Journals | Drafts with supporting evidence (depth 2) | Any manual or one-off journal |
| Variance commentary | Drafts first-pass explanations (depth 2) | What goes to the board |
| Payments | Not in scope for the close agent | Release, through the payments process |
The controller's key reading skill is the deciding bound. "Held: customer limit" on a journal means it is above the threshold the controller set. "Held: sources" often means the supporting document is an emailed spreadsheet, which is external, rather than a sealed ledger extract. Both are held for good reasons, but they ask different questions.
An example from a group finance team
Take a mid-sized group with a financial controller, two assistant accountants and an agent drafting reconciliations and standard accruals. The controller completes Foundations and most of the Operator modules in the first five weeks, at around three hours a week.
At the first month end, the controller runs a shadow close. The agent's draft accruals match the team's for all but two lines, both where it used last month's rate card from the shared drive rather than the new contract in the contract register. That becomes a fix to the agent's sources. At the second close, the controller makes the real decisions, with the finance director checking a sample, and sits the exam the following week.
Calibration with assistant accountants on the same entries is covered in calibration sessions for financial controllers. Pressure to post a journal before the evidence arrives, or documents that try to steer the agent, are covered in training financial controllers to spot prompt injection and pressure.
How this compares with nearby roles
Credit controllers can be ready in five to six weeks because their volume is steady across the month; see how long it takes to train credit controllers. Financial controllers take longer because of the close cycle and their ownership of limits. The wider programme is in training teams for AI agents.
Where the Academy fits
The Operator track of Pryme Intelligence Academy suits a financial controller who runs the close with an agent, including its modules on teaching the agent and keeping knowledge current. A controller who goes on to design and certify the finance agents themselves would look at the Builder track, about 24 hours plus a capstone agent certified in Attest to depth 2 or higher.
Questions people ask
Should the agent post anything during the controller's first close?
Only drafts. Keep every close entry at depth 2 until the controller has been signed off and has reviewed the evidence for depth 3.
What happens if the agent's certificate lapses at month end?
A run that clears no depth drops it to depth 1 the same day, and everything it would have posted comes back to the team. Know the certificate's expiry date and plan the close around it.
Do auditors need to know the controller is trained?
They will ask who reviewed the agent's entries and on what basis. A current certificate and the filed review decisions answer that.