.avif)
AI in Accounting: Shifting the Question From if to How.
For a few years, the conversation about AI in accounting stayed stuck on a single word: if. Should we even be using this? The profession asked that question longer and more carefully than most, and that caution got read the usual way. Accountants being slow. Behind. Late to something everyone else had already embraced.
I think that reading misses what was actually happening. The hesitation less about resistance to change, and more about a reflex earned through years of closes, audits, and hard lessons.
The assurance instinct behind the hesitancy
That reflex has a name, even if we rarely say it out loud. Call it the assurance instinct, and it is the thing that defines good accounting. You do not put your name on a number you cannot trace. You do not sign off on something you cannot defend months later when an auditor asks. Every figure carries a lineage, and your job is to be able to walk anyone back through it. That instinct is the whole profession compressed into a reflex.
Now hand that person an AI that produces a confident answer and cannot show its work. Of course they hesitated. A black box that will not reveal what it saw, what it touched, or why it decided what it decided is, by definition, the one thing an accountant is trained never to accept. The “if” question was the assurance instinct refusing to certify something it could not audit. That was the correct professional response.
What actually changed
Here is what I want accounting leaders to hear: the question about AI in accounting has moved from “if” to “how,” and it did not move because anyone lowered their standards. It moved because AI can finally meet them.
That shift is the real story of where we are in 2026. McKinsey’s State of AI Trust survey put clear language to it. Organizations can no longer worry only about AI saying the wrong thing. They now have to manage AI doing the wrong thing, taking actions inside live systems. The same research found that nearly two-thirds of organizations name security and risk as the top barrier to scaling agentic AI, ahead of regulatory or technical concerns.
Read that and the picture sharpens. We know the technology works. What slows adoption is whether teams can let it act without losing the traceability they are accountable for. Which is to say: the rest of the business is now wrestling with the exact instinct accountants have had all along.
Why AI in accounting hits this profession first
Accounting carries an advantage and a target at the same time. The McKinsey work found that financial services are among the more mature sectors for responsible AI, helped by years of risk discipline. But it also found that only about a third of organizations have reached real maturity in governance and agentic controls, even as the capabilities race ahead.
We feel it first because our work is unforgiving. A developer can let AI write code and catch the failures in testing before anything reaches production. A close team is reconciling to the penny against a trail someone will examine later. Point an agent at ten disconnected spreadsheets and a handful of stale exports and it will not hesitate. It will give you a clean, confident, wrong answer, fast. Point it at one reconciled source of truth and you have something you can stand behind.
The “how” is just the standard you already hold
So what does it look like to adopt AI without betraying the instinct that makes you good at the job? You hold the agent to the same standard you would hold a staff accountant in their first week. Real work, real limits, and a person who signs off on anything consequential before it touches the ledger.
That standard has three plain requirements, and they are the same ones you already enforce on the humans in your department.
It has to operate inside your permissions. If a staff accountant cannot post to a subsidiary, the agent should not be able to either. Modern ERPs are now shipping AI connectors built for exactly this, usually on an open standard so you are not locked to one vendor’s model. They let you bring your own AI into the system under the same role-based permissions your people already work within. The agent inherits the controls instead of working around them.
It has to show its work. Every action an agent takes should leave a trace: what it saw, what it did, who approved it. That is what turns a black box into something you can defend when the auditor asks. It is also, not coincidentally, the same evidentiary discipline behind a clean close process.
It has to stop bad data at the door. If invalid account combinations can enter your GL in the first place, no amount of AI oversight downstream will save you. Once an agent is reasoning over your numbers, stopping bad data at the point of entry, through something like cross-validation rules, is the foundation it stands on.
None of that is new to you. It is the assurance instinct, written down as a spec.
The instinct can finally say yes
McKinsey’s conclusion was blunt: trustworthy AI has to be built from policies, people, and technology working together over time. There is no product that switches it on for you. That sounds like work because it is. But the first step is getting your financial data into one trusted, reconciled, validated place before you let any agent near it. For most teams, that place is their ERP.
When your ERP is also your single source of truth, an agent reasons over numbers that have already been reconciled and controlled, under permissions your people already operate within, leaving a trail you can defend. Every condition the assurance instinct was holding out for is finally met.
That is the resolution I want to leave accounting leaders with. You were not wrong to wait. The hesitancy was the right reflex pointed at a tool that could not yet earn your signature. The standard stayed exactly where it was. AI is what moved, and it can finally clear that bar. The same instinct that made “if” the right question is the instinct that can now, on its own terms, say yes.
