Nobody Asks to See the SQL
A demo request landed this week asking for a detailed, nuts and bolts walkthrough for a finance team. Every screen. Every transaction keyed in while they watch, from the purchase order through to the payment run. My first reaction was that this is about as useful now as walking them through the SQL statements that update the database.
Nobody asks to see the SQL in a finance demo. The INSERT behind a vendor invoice is somebody else’s problem, and the controller in the room is perfectly happy to trust that the row got written. Screens got different treatment for decades, because the screen was where the work happened. If the work happened on the form, then the form was the product, and we demoed it field by field (tab, tab, dropdown, tab). That logic held up fine while a person had to type every line.
I don’t think the request is unreasonable, for what it’s worth. Finance people have been shown a lot of slides, and most of them have heard some version of “and then it just posts” from a presenter who never opened the voucher. Asking for every screen is a way of saying prove it. I respect the instinct, even when the method has gone stale.
The front door moved
Microsoft now offers an MCP server for Dynamics 365 ERP, in preview, that gives AI agents access to the data and business logic of the finance and operations apps. The first version was a static set of thirteen tools, mostly on the supply chain side. That one is being retired during 2026 in favor of a dynamic server that exposes far more of the application, and Microsoft has said its new ERP agents will run through MCP. Read that as the vendor building a front door for software that will never look at a form. The forms are still there. So is the SQL.
This is what people mean by headless ERP. I think it settles what a finance demo should be about, and it isn’t the screens.
The click-through demo was measuring the wrong thing anyway. What an audience actually watches is how well the presenter knows the menus, which says a lot about the presenter and almost nothing about the posting logic underneath. It also outruns anybody’s memory. By the time the vendor payment journal comes up, the purchase order is a vague recollection and the product receipt has blurred into it.
Headless puts the plumbing on stage
The headless argument usually stops one step too early. Taking the screens away doesn’t make the nuts and bolts irrelevant; it makes them the only thing left to show. Nobody audits the SQL, but finance gets audited every year, and the auditors are going to want to know who approved what. In a headless system that question turns into what an agent was allowed to do. An agent that touches Dynamics 365 through that MCP server has to authenticate as a valid Dynamics 365 user, so the security role assigned to that identity is the user interface now, in every way a controller should care about. Segregation of duties used to be a conversation about which clerk could create a vendor and which one could pay it. It is about to become the same conversation about a piece of software that works at 3 a.m. and never asks the person at the next desk whether something looks off.
So yes, I’d still give finance a nuts and bolts demo. Different bolts. I’d let an agent process a batch of invoices with nothing on the projector but a chat window, and then stop and open up what it did. The vouchers first, and the posting profile that decided which accounts they hit. Then the subledger against the general ledger, because a fast agent posting to the wrong account just gets you to a bad close sooner. And the one invoice it couldn’t match, since exceptions are where a headless system has to hand something back to a human being.
Then I’d try to break it. Give the agent an invoice with the wrong unit price, or one against a purchase order that was only half received, and see what it does. If it posts anyway, that is the most useful thing anybody in the room will learn all day. If it stops and routes the invoice to a person, I want to see who gets it and what the agent recorded about why it stopped. Better still, ask the finance team to bring one of their own ugly invoices and feed it in cold.
The harder questions are about boundaries. Which actions get exposed to agents at all, and who notices when one of them is confidently wrong about a three-way match? None of that is visible on a form, and all of it is more technical than the click-through demo ever was. It’s also the part most vendors would rather not rehearse in front of a controller.
The people still at the screens
Headless describes an architecture, though. It doesn’t describe the AP clerk whose entire job, right now, is the invoice screen, and who will be sitting in that demo trying to work out whether the person at the projector thinks that job is the part being skipped. Say “the screens don’t matter” to that person and it lands as news about their job, whether anyone meant it that way or not.
I’d still show them a form. One. The exception queue, where the agent hands its problems to a human, because that is the screen a clerk is most likely to be living in a year or two from now. It’s a smaller job than keying every invoice, and probably a harder one, since the easy invoices are gone by the time anything reaches that queue.
Most finance teams still run on people working the forms. Nobody has told them which of their screens the agent gets first.
My book, Gamifying the Enterprise: Game Mechanics for Continuous Proficiency, is on Amazon. All my books are on my Amazon author page.
The AD&D365 configuration guides are at adnd365.com/start.
Connect with me on LinkedIn.
