Adopt agents reconcile, calculate, draft, and gather the evidence for finance, tax, and accounting work on their own. Nothing pays, posts, files, or leaves the building until a person with the right authority signs the finished outcome.
PrincipleBe permissive about intelligence. Be absolute about authority.
Watch it stop at the signature line.
Agent platforms push finance leaders toward one of two extremes. Neither gets you autonomy a controller can sign off on.
PATH 01
Break the work into guarded steps. Approve every prompt. Confirm every transaction. The agent stays safe because it barely does anything, and your team has to learn the harness to get any value out of it.
The hidden cost: your accountants become AI operators, and clicking "confirm" becomes the new job.
PATH 02
Give the agent the access you would give an employee, and let it pay vendors, post entries, file returns, and email customers as it reasons. Accountability rests on controls written for people.
The structural risk: an agent is not an employee. Your authority, identity, and accountability controls were never built for one.
Let the agent finish the work. Keep the authority to make it real with a person.
The line it cannot cross
The agent can reconcile, prepare, simulate, gather evidence, and propose a finished business outcome. Payments, journal postings, filings, external emails, and every other irreversible action stay proposals until a person with the right authority signs off.
Each guarantee closes off a different way agentic finance goes wrong. Together, they give you autonomy you can audit.
The outcome
Finance work you can defend
The five only work together. Agency without boundaries is dangerous. Boundaries without evidence can't be verified. Evidence that doesn't last won't hold up in an audit.
Each one is a property of the product itself: how work is created, reviewed, authorized, executed, and kept on record.
Memory
“The agent can create. It cannot erase.”
Everything the agent does is added to the record, never written over. Source evidence, calculations, working files, exceptions, changes of mind, and corrections all stay attributed and rebuildable.
A correction creates a new version. The old one stays, so the record shows how the work reached the answer, not only the answer.
Agency
Maximum agency, until delivery.
While the work is in progress, the agent can read your systems, reason across evidence, calculate, reconcile, call tools, draft working papers, flag what it isn't sure about, and assemble a complete business outcome.
It doesn't need someone steering every step. But anything with consequences outside the work (pay, post, file, send, change) exists only as a proposal.
Authority
“Humans sign outcomes, not API calls.”
A controller shouldn't have to approve 137 technical operations they can't read. They should approve one business outcome they can: what was asked, what the agent found, what it produced and why, the exceptions, the financial impact, and exactly what happens when they sign.
The outcome is sealed and signed cryptographically by a named person, using biometric authentication on a company-managed device. Change anything in the outcome and the signature no longer matches.
Enforcement
Trust is enforced below the model.
Adopt keeps the agent's judgment separate from the system's authority. The boundaries are machine-checkable, formally verifiable rules enforced by the platform, not instructions the model is asked to remember. No prompt can talk its way past them.
Accountability
Every number stays defensible.
The record links every source to the work done on it, every revision to its reason, every intended effect to a human signature, and every signature to what actually happened in your systems. When an auditor asks you to defend a number years from now, the answer is already there.
Adopt agents carry the work all the way to a finished outcome. They never pick up the authority to make it real on their own.
