The AI-Ready ERP Checklist for CIOs and CFOs

Six questions worth answering before the next agent goes live in Dynamics 365.

There was a change in ERP this year. Wave 1 of Microsoft’s 2026 release will be released between April and May.
And in September, Copilot in Dynamics 365 will transition from the suggestion layer into the agentic layer, making agents responsible for reconciling transactions, chasing vendors, rebalancing inventory, and approving processes using existing workflows, existing security framework, and business logic.

That is the good news. The harder news is that more than half of the success of such agents lies outside the release notes. According to Gartner, more than 40% of agentic AI initiatives will be canceled by the end of 2027 due to rising costs, a lack of clarity about their business value, and insufficient risk-control measures. The technology comes out of the box, but not the company.

So, before you launch another agent, run this list through.

01 Are you really up to date?

Agentic capability flows concurrently today. Organizations are falling behind on their updates, delaying them, or adding so many customizations that get broken in every wave, and they never see AI on the roadmap. Staying current is no longer about mundane housekeeping; it is the means by which the capability arrives. The question to ask is how far behind you are in your waves and why?

02 Is your data ready for agent queries?

A tool that generates a summary from master data can handle messy data, but the tool executing the queries cannot. Vendor duplication, variance in the hierarchy of objects, and three different versions of the customer file make independence a cause of identical mistakes.

03 Do you have your business rules documented anywhere?

Agencies exist within certain boundaries that must be clearly defined: thresholds for approval, limits of tolerance, paths for escalation, and exceptions. In many financial and supply chain operations, the rules governing these processes exist in people’s heads and in unwritten email practices. There is no room for autonomy when rules are not explicitly laid out. This is an unglamorous process and often takes the longest time

04  Do your agents have identities?

This is the newest entry on the checklist and also the most likely to be overlooked. As Microsoft Entra Agent ID launches in July 2026, agents will now be assigned identities in the directory, permission visibility, CA (Conditional Access) protection, and logs for their use authentication activities, similar to any other principal in the tenant. Factor in Copilot Control System, connector policies, and DLP, and suddenly, CIOs have an inventory of their non-human employees. Organizations that bypass this process often learn about the agent population only through an audit.

05  Can the CFO endorse the actions of the agent?

Each autonomous transaction within a financial process requires documentation: what the agent saw, decided, and changed, and who might have affected the decision-making process. The requirement for statutory reporting and internal controls does not get waived just because it was entered into the system. The materiality level for independent decision-making must be included in the control system before go-live; it should not be discussed with the auditor.

06  Is there validity to the cost model from a finance perspective?

Consumption by agents will be metered differently from seats. Credits, capacity packages, and governance licensing change the economic dynamic in ERP from a predictable per-user basis to an unpredictable per-transaction basis. CFOs need to build the model based on actual volume, align it with a measurable goal, and create kill criteria for pilots that don’t meet that mark. The finance research at Gartner takes the same approach, stating that the margin benefit does not come from a collection of scattered pilots but from finance technology portfolios.

The intersection is the opportunity.

And this is more than just a technology issue, the very reason it should not be left to any one department alone. The CIO oversees the platform, identities, and the data estate. The CFO oversees the control environment and the business case. The AI-enabled ERP is located right at the crossroads, and in 2026, the crossroads will determine success or failure.

At YASH Technologies, we help organizations build a Dynamics 365 environment for agency operations—from fundamentals, release currency, governance, control design, and careful deployment. Start with the checklist. Then consult our experts. Contact us today at info@yash.com

• AI Transformation
• ERP Modernization
• Microsoft
• Microsoft .ERP