For fifty years, ERP has been the company's memory: the place where we record what has happened. Orders, invoices, stock levels, journal entries. People do the work; the system keeps the books. That division of labour is now starting to dissolve, and that is what Agentic ERP is really about.
From system of record to system of action
Until now, Copilot in ERP has mostly been a smarter assistant: summarise, suggest, draft. An agent is something else. It reacts to an event, not a login. A supplier invoice arrives, a delivery slips, a balance looks off, and the agent investigates, proposes or acts within boundaries we have defined. People step in at deliberate checkpoints instead of at every step.
The difference is not that the system gets smarter. The difference is that the system starts taking the initiative.
This isn't the future. It's 2026.
This year, every major vendor has made agents part of the core architecture rather than an add-on:
Microsoft: Dynamics 365 2026 release wave 1 moved Copilot from productivity aid to an agent layer embedded across finance, supply chain and commerce. The Dynamics 365 ERP MCP server lets agents built in Copilot Studio talk directly to F&O data and business logic, and Microsoft has announced around two dozen new finance agents.
SAP: At Sapphire, SAP unveiled the Autonomous Enterprise with more than 200 agents and Joule Work, an interface where users describe the outcome they want instead of navigating screens.
Oracle: In October came Fusion Agentic Home, where employees delegate work to agents and monitor execution.
The message from all three is the same: stop interacting with your ERP. Start delegating to it.
How work changes
From where I sit, working on D365 F&O implementations and Power Platform solutions, four shifts are already visible:
From doing to reviewing. The AP clerk no longer matches invoices line by line. They review the agent's proposals and handle the deviations.
Exceptions become the job. When the standard flow runs itself, what remains are the edge cases, the judgement calls and the relationships. That takes more skill, not less.
The process owner becomes an agent manager. Someone has to define mandates, limits and escalation paths, follow up on outcomes and adjust. It's a new role, and it belongs to the business, not IT.
The interface thins out. A lot of ERP work will happen in Teams, Outlook or a chat. The form becomes something you open to understand, not to key in data.
What matters more, not less
It's tempting to read Agentic ERP as the end of implementation work. I think the opposite is true. An agent is never better than what it stands on:
Master data. An agent acting on wrong vendor terms or broken item data makes mistakes faster and at greater scale than a person.
Process design. Automating an unclear process gives you an unclear automaton. Checkpoints have to be designed in deliberately.
Governance and accountability. When an agent posts, orders or pays: who owns the decision? Security roles, traceability and audit trails must work for agents exactly as they do for people, within the bookkeeping and compliance rules that already apply.
Cost. Agents are licensed and consume capacity. The business case has to be proven per flow, not assumed.
Where to start?
My advice to anyone running Dynamics 365 today: don't wait for the grand agent strategy. Pick a contained, repetitive flow with a clear owner, such as supplier invoices, purchasing deviations or questions from buyers. Clean up the data around it. Decide where a human approves. Measure. And build in-house skills in Copilot Studio and MCP, because that is where the integration between agent and ERP is won or lost.
Agentic ERP doesn't replace the ERP system. It turns it into a colleague. For most companies the question isn't whether this will happen, but whether their processes and data are in good enough shape to let that colleague do the work.
Want to discuss how agents could fit into your Dynamics 365 landscape? Get in touch with us at Bubo Consulting.


