Ungoverned AI Has No Business in Your System of Record
Most organisations are asking the wrong question about AI. The question is not whether AI is powerful enough to act inside an ERP. It is whether the AI is governed enough to be trusted there.
There is a version of AI adoption that is happening right now across mid-market businesses that will cause significant problems in twelve to eighteen months. It is not happening because the technology is bad. It is happening because the question being asked is the wrong one.
The question most organisations ask when evaluating AI for their ERP is: can it do the job? Can it handle the volume, process the data, execute the workflow? These are reasonable questions. They are also insufficient ones. Because an AI system that can do the job but cannot account for what it did, why it did it, or who authorised it is not a solution to an operational problem. It is a liability dressed as one.
The right question — the one that determines whether AI in an ERP delivers value or creates exposure — is: can this AI be governed?
What ungoverned AI looks like in practice
Ungoverned AI is not a dramatic failure. It does not produce obviously wrong outputs in ways that are easy to catch. It produces plausible outputs in ways that are difficult to audit.
A pricing decision is made. The margin is slightly wrong. There is no record of the rule that produced the price, no confidence score that would have flagged the uncertainty, no reason code that would have routed the exception to a human reviewer. The decision was made, the transaction was posted, and the audit trail ends at the output.
An access permission is assigned. Six months later, an auditor asks why a finance team member has access to a module they do not use. There is no record of who authorised the assignment, what rule triggered it, or when it was last reviewed. The answer is: the system did it.
A subscription contract is processed. The terms are almost right — but a renewal date was interpreted differently from what the customer agreed. The error compounds across twelve months of invoices before anyone identifies the source.
None of these are catastrophic in isolation. Together, across an organisation running ungoverned AI at volume, they represent an audit risk, a margin risk, and a customer trust risk that accumulates silently until it becomes visible.
Why the ERP is where governance matters most
AI can be ungoverned in many places without serious consequence. An AI writing assistant that produces an imperfect first draft is corrected before the document leaves the building. An AI that summarises a meeting slightly inaccurately is corrected in the next meeting.
The ERP does not work this way. In the system of record, decisions have downstream consequences that are difficult to trace and expensive to reverse. A wrong price does not stay in a draft — it goes to the invoice. A wrong access assignment does not stay in a proposal — it goes live in the production environment. A wrong subscription term does not stay in a conversation — it determines what the customer is billed for the next three years.
This is why the governance standard for AI in an ERP must be higher than the governance standard for AI anywhere else in the organisation. Not because the ERP is more important than the people who work in it. Because the ERP is where the consequences of AI decisions become permanent.
What a governed AI system looks like
Governance is not a constraint on AI capability. It is a design principle — and when it is built in from the start rather than added afterwards, it does not reduce what AI can do. It determines what AI is trusted to do.
A governed AI system in Business Central operates within a policy framework the business defines. It knows which decisions it may take autonomously — because the business has determined they are low-risk, high-volume, and well-understood. It knows which decisions require a human approval step before execution — because the business has determined that the value or the risk warrants a review. And it knows which decisions are not its to make — because the business has decided they belong entirely with a person.
Within that framework, a governed AI system maintains a complete record of every action. Not a log of outputs, but a structured audit trail: what was decided, what rule applied, what confidence level the system was operating at, what the threshold was for autonomous action, and — where a human was involved — who approved it and when.
That audit trail is not a retrospective report. It is a live operational output. It is what the finance controller sees when they review the AI’s activity for the week. It is what the external auditor reviews when they ask how a pricing decision was made. It is what the board sees when they ask whether the AI is operating within the policy they approved.
This is what it means for AI to be safe to trust with the system of record.
The organisations that get this right
The organisations that will use AI most effectively in Business Central are not the ones who deploy it fastest. They are the ones who define the governance framework before deployment — and build the AI into it, rather than trying to retrofit governance onto AI that is already in production.
That sequence matters. A governance framework designed before AI deployment reflects what the business actually wants the AI to do. A governance framework retrofitted after deployment reflects what the AI has been doing — and the gap between the two is where the audit risk lives.
The conversation about AI in ERP is accelerating. Project MIA, Microsoft’s AI-assisted implementation capability announced at DynamicsMinds in May 2026, signals that AI is not arriving at the edges of the Dynamics ecosystem — it is arriving at the centre of it. The governance question is therefore not a question that can be deferred until after adoption. It is the question that should precede it.
Ungoverned AI has demonstrated its value across many domains. The system of record is not one of them.
Let’s chat further.
"*" indicates required fields
