Three things: what each governed action costs, who approves money leaving when an agent prepares it, and what evidence auditors will be shown. Agents change the finance function’s unit costs and its control environment at the same time. A CFO who understands depth, held payments and the record can sign off both with confidence.
How should a CFO think about cost?
Per governed action, not per seat or per model call. An agent that drafts a supplier payment, checks it against limits and files the verdict has done a unit of work. Some of that work is allowed outright, some is held for a person, some is refused. Each outcome has a cost: platform usage, plus the minutes of the reviewer who decides held items.
That second cost is easy to miss. If limits are set so tight that most actions are held, the business pays for the agent and for nearly the same review time as before. If they are set too loose, review time falls but so does control. The right setting comes from evidence on the business’s own cases, not from the vendor’s brochure.
A useful question for the finance team: for each agent, what share of actions ended allowed, held or refused last month, and what did the held ones cost in reviewer time?
Who approves payments when an agent prepares them?
A named person, almost always. Moving money is depth 4 on the scale agents work to: hard to undo, so it is the last capability an agent earns and the one most businesses keep held.
| Payment step | Typical depth | Who decides |
|---|---|---|
| Matching invoice to order and receipt | 3, within tolerance | Agent; exceptions to a clerk |
| Drafting the payment run | 2 | Agent drafts, finance checks |
| Releasing payments within a low limit to verified payees | 4, if certified | Agent, within the limit set |
| Paying a new payee or changed bank details | Held | Named approver after verification |
| Reversing a settled payment on the firm’s own rail | Withheld | Not available to any agent |
The key control is provenance. A bank detail change that arrives by email is an external claim, and an external claim cannot authorise a payment. It must be verified through a known channel. That rule stops the most common payment fraud regardless of how good the agent is.
Approvers also need the right to say no. The argument is made well in reviewers need authority, not just access: a person who can see held payments but cannot block them is not a control.
What will auditors ask, and what can finance show them?
Auditors will ask how a payment came to be made, who approved it, and whether the control operated every time. With governed agents, the answer is in an append-only record. Each verdict shows the facts used and where they came from, which of the five bounds decided the outcome (role scope, certificate, sources, the firm’s own limits or the platform guardrails), and who approved any held action.
That is stronger evidence than most manual processes produce. It only helps if finance knows it exists and how to pull it. The CFO should ask for a sample walk-through before the first audit, not during it.
Certification matters to auditors too. Certificates lapse after 90 days, and a run that clears no depth drops the agent to depth 1 the same day. An agent that paid invoices on a lapsed certificate would be a finding.
What does onboarding and verification have to do with finance?
More than it seems. Supplier and customer onboarding feed the payee records agents pay. If know your business checks on suppliers or know your customer checks on customers are weak, an agent will pay the wrong party efficiently. The CFO should know which records agents treat as sealed and who keeps them accurate.
Which decisions should stay with the CFO’s team?
Payment limits and approver rules for agents, write-offs, provisions and estimates, period close sign-off, and any change to the chart of accounts. The CFO should also sign off which finance capabilities may move above depth 2, and see the certification evidence first.
Other executives look at the same agents from different angles. The CIO’s view focuses on integration and access; the compliance team’s view on refusals, red lines and testing. The full set is in AI agent skills by role.
How should the finance team be trained?
Approvers first. Anyone who can release a held payment should understand depth, the four verdicts and provenance, and be tested on real held items before go-live. Pryme Intelligence Academy offers a free readiness assessment for teams of up to 25 people, which reports scores by concept and the gaps to close.
Questions people ask
Should the CFO approve every agent that touches money?
The CFO should approve the policy and limits for finance agents, and see certification evidence before any capability moves to depth 4. Individual payments follow the approver rules.
Can agents help with month-end close?
Yes, at draft depth: reconciliations, accrual proposals and variance commentary. Posting manual journals above a threshold and signing off the close stay with people.
Is the agent’s record good enough for external audit?
It can be strong evidence because it is append-only and shows every verdict. Agree with the auditors early how they will sample it.