Who Approves the Robot’s Journal Entry?

A few weeks ago I would have told you AI in your ERP meant a chatbot. You’d ask it a question, it’d draft something, and you’d still be the one who clicked “post.” That’s not true anymore, and I don’t think most controllers have caught up to it yet.

The Headline

In June, a trade publication called ERP Today put out a piece that used one word to describe everything happening in enterprise software that month: execution. Not intelligence. Not insight. Execution.

In the span of about three weeks, four companies bought their way into AI execution capability. Asana bought a company called StackAI. Coupa bought Rossum. Salesforce bought Contentful. Vertice bought Vendr. Four completely different software categories, and every single deal had the same underlying logic — buying the specific capability an agent needs to actually do something, not just talk about it.

The one that should get your attention the most: Priority ERP shipped version 26 to 75,000 customers across 70 countries, with agents that create journal entries, post receipts, process invoices, and run inventory checks — inside the system. Not next to it.

So if you’ve got a client on an ERP, the agent posting their entries might already be live. And nobody asked the controller to sign off.

From Calculator to Checkbook

Here’s the shift, in plain terms. A calculator makes you faster at the math — you’re still the one who decides the number’s right and signs your name. A checkbook is different. Whoever’s holding it can act on your behalf, with your money, without asking first. We’ve spent the last two years handing out calculators. What shipped this month are checkbooks.

The vendors are saying this out loud now, too. At a conference in San Francisco this month, the CMO of a company called Nominal put it bluntly: chatbots explain, agents execute. That’s not a tagline. That’s the thing they’re selling against.

What’s Actually Changed

A few concrete examples, beyond Priority:

• Nominal — agentic performance management for reconciliation and intercompany transactions, sold specifically on “determinism and auditability built into the workflow design, not bolted on afterward.”
• Coupa + Rossum — AP document intelligence trained on tens of millions of real invoices and source documents, because even the vendors don’t trust a generic model with this kind of execution.
• Vertice + Vendr — an agent named Ana that actually negotiates vendor contracts directly, before a human ever sees the deal.

Different corners of the business. Same underlying move: agents that act, not just agents that advise.

What This Means for You

I want to keep this narrow, because the controls questions here matter more than the hype.

First — segregation of duties doesn’t disappear because the preparer is software. It gets redesigned. If an agent drafts and posts an entry, a human still has to be the reviewer, and that boundary needs to be defined before the agent goes live, not discovered after something gets posted wrong. Ask any vendor, point blank: who’s the preparer, who’s the reviewer, and is that enforced by the system — or just written down somewhere nobody checks?

Second — “auditable” is a claim right now, not a control. Every vendor in this wave uses that word. Your job is to test it. Ask for the actual log. What did the agent post, what triggered it, who reviewed it, and when. If they can’t produce that on request, the control doesn’t exist yet — the word in the pitch deck does.

Third — find out where the exception threshold is set, and who owns it. Every one of these tools claims it handles the routine 90% and kicks the unusual stuff to a human. Fine. But if that threshold is set too loose, the agent is quietly clearing things that should’ve stopped for review — and right now, in a lot of rollouts, that threshold is being configured by an implementation consultant, not your finance team.

Key Takeaways

• The move from “AI helps me work faster” to “AI executes the transaction” changes what your controls review needs to test. Don’t apply the old checklist.
• Before any agent gets posting authority, get a specific, written answer on who’s the preparer and who’s the reviewer — and confirm it’s enforced in the system.
• Treat “auditable” as something you test, not something you accept.
• Find out who owns the exception threshold. That single setting is doing more control work than almost anything else in the system.
• This isn’t an enterprise-only conversation. Priority’s rollout alone covers 75,000 customers. Assume someone else’s client has already turned this on.

Want the CPE credit? Take the full lesson on EverydayCPE and earn 0.2 CPE credits: Who Approves the Robot’s Journal Entry?