Enterprise AI is creating plenty of discussion around models, data, security and regulation. All of those matter. But I think the harder issue is showing up in the decision.

As AI moves from answering questions to recommending, preparing, coordinating and eventually executing work, governance has to move with it. The question is no longer only whether an AI system can access the right data or produce a reliable answer. It is whether that system has the authority to act, under what conditions and who remains responsible when it does.

That is a different governance problem. AI does not replace governance. It exposes whether the enterprise ever had it. Disclosure: KramerERP provides paid research, advisory and consulting services to technology companies, including ERP and data vendors listed in this article.

For years, enterprise governance focused heavily on information. Who can see the data? Who can change it? Where can it be stored? How long should it be retained? Those controls still matter. But once software participates directly in business decisions, enterprises also have to govern authority.

ERP has traditionally been where many business transactions are recorded and controlled. A purchase order gets approved. Inventory is allocated. A journal entry posts. A production order changes.

AI changes that sequence. Instead of a person reviewing information and initiating the next step, software may identify the situation, evaluate the options and prepare or execute the response. ERP is moving from a system of record toward becoming part of the enterprise execution layer , as I highlighted in a previous Forbes article. That creates value, but it can also expose decision rights that were never as clear as organizations thought.

Consider a supply disruption. An AI system sees that a critical component will arrive five days late. It identifies an alternate supplier, compares price and lead time, determines available inventory and recommends moving the order. That sounds straightforward until the questions start.

Is the alternate supplier approved? Does the price increase exceed a sourcing threshold? Is inventory already committed elsewhere? Does the substitution create a quality or regulatory issue? Can the agent change the supplier or only prepare the recommendation? Who owns the outcome if production is interrupted?

The AI may be technically correct that Supplier B can deliver faster. That does not automatically make switching suppliers the right business decision. Governance now has to sit inside the decision.

The harder problem is turning decision rights into runtime controls. An AI system can answer, recommend, prepare, coordinate, approve or execute and each level needs a different control model. I have written about those decision rights in ERP before. The broader governance question is how the enterprise enforces them as agents move across systems.

In finance, identifying an unusual revenue transaction is relatively low risk. Preparing the supporting analysis adds value with limited additional risk. Preparing a journal entry goes further. Posting it without review is a different level of authority.

The same is true in procurement. Recommending an alternate supplier is different from preparing a purchase order, and preparing it is different from releasing it. A $5,000 order is also very different from a $5 million commitment.

This is why I keep coming back to the decision as the unit of design. The enterprise has to decide what technology can do on its own, what needs approval and what stays with a person. That depends on financial and operational impact, confidence, policy, regulatory exposure, reversibility and the cost of being wrong. Autonomy should follow the decision, not the capability.

The platforms are starting to reflect that model. Microsoft Copilot Studio, Salesforce Agentforce and its new AI Control Plane, Oracle AI Agent Studio and SAP Joule Agents collectively bring permissions, guardrails, approval steps, observability and auditability closer to agent execution. Different implementations, same direction. Governance is moving from policy documents into runtime authority.

Context Is Part Of Control

In an earlier InfoWorld article, I positioned that trusted context is becoming the currency for enterprise AI . More data does not automatically produce a better decision. AI needs to understand the relationships, policies, commitments and operating conditions around that data. The same is true for governance.

Suppose the system sees 8,000 units of inventory. That is data. But how many units are available? How many are already committed? How many are sitting in the wrong distribution center? How many are on quality hold? Which customer orders have priority?

Now add the governance context. Who has authority to reallocate inventory? What customer commitments apply? At what margin threshold does an exception require approval? Can a local planner make the change or does it need regional approval?

Trusted context tells AI what is happening. Governance determines what it can do. Policy, identity, permissions and process state need to travel with the decision across ERP, data platforms, workflows and agents.

Google and IFS show the same pattern from different angles. Google’s Agent Gateway uses agent identity and IAM-based policy enforcement, supports Model Armor and generates observability telemetry, while IFS Loops Agent Studio uses approval gates, escalation paths, versioned releases and human-in-the-loop queues. Different architectures, same requirement. Control has to travel with the action.

Governance cannot become a separate layer that somebody checks after the action has already occurred. That is part of what I mean by decision architecture . Data, context, authority and execution need to connect around the business decision rather than live in separate technology silos.

Accountability Must Stay Visible

As AI takes on more work, organizations cannot let automation blur ownership. “The AI did it” is not an operating model. If an automated process changes a supplier, adjusts a customer commitment, modifies production, posts a financial transaction or makes a workforce recommendation, somebody still owns that business process and its outcome.

Ownership can span several roles. The process owner defines the decision, IT operates the platform, security governs identity and access, risk and audit define controls and the business owner remains accountable for the financial or operational result.

The exact model will vary, but ownership has to stay visible. The more authority software receives, the more explicit human accountability needs to become. Enterprises can delegate execution to software. They cannot delegate responsibility for the business outcome.

Not every AI decision carries the same consequence. A recommendation can be rejected and a draft can be changed. A transaction that has already been executed may be much harder to undo.

Think about an AI system preparing a journal entry versus posting it, or recommending a supplier change versus releasing the purchase order. In manufacturing, changing tomorrow’s schedule may be reversible. Stopping a line, rerouting materials or initiating a physical action can carry much greater cost.

Observability and reversibility have to be designed before autonomy expands. Enterprises need to know what happened, why it happened, what information the system used, what policy applied and who or what authorized the action. They also need escalation paths, fallback processes and a way to stop or reverse activity when something goes wrong.

The real test is not whether a control appears in a governance document. It is how quickly the organization can detect a bad action, understand it, stop it and recover. Autonomy without reversibility is not governance. It is exposure.

Governance cannot mean sending every AI decision to another committee. That would erase much of the value. The goal is bounded autonomy. Routine, lower-risk and reversible decisions can move faster, while higher-impact, ambiguous or unusual situations move to people.

That operating model is starting to show up in customer deployments. SAP says Aeropuertos Argentina’s SNOW agent operates within defined safety thresholds, service levels and playbooks across winter operations at eight Patagonian airports. SAP reports a 16% reduction in direct costs and a 90% reduction in administrative time. IFS reports Kodiak Gas Services projects about $3 million in annual ROI and more than 90,000 hours returned to the workforce from its Material Replenisher Digital Worker.

Salesforce reports Live Nation’s Venue Agent handles 95% of fan questions without a team-member handoff, while requests outside the agent’s knowledge are routed to people.

These are vendor-reported results. The percentages are useful, but the operating model matters more. Routine work moves faster inside defined boundaries, while exceptions and higher-impact decisions stay visible to people. That is the point of bounded autonomy.

The measures have to reflect both sides. Agent count is not a business outcome and neither is policy count. Measure what changed in purchase cycle time, service levels, working capital, throughput, downtime, close time and error rates. Then measure the control with exception rates, overrides, approval frequency, recovery time and repeat failures.

Business performance and control performance have to improve together. Moving faster while creating more unexplained decisions is not progress.

I would start small and stay close to the decision when advising CIOs, technology leaders and business executives. Pick three to five real decisions where ownership is known and the outcome can be measured. Define what AI can recommend, prepare, approve or execute, then identify the trusted context and thresholds required around it.

Name the person who remains accountable, then design intervention before expanding autonomy. Decide what happens when confidence drops, information conflicts, a threshold is crossed or the system gets it wrong. Then expand.

Enterprise AI will not make governance less important. It will make governance operational. As AI becomes part of the enterprise execution layer, authority, context and accountability have to travel with the decision.

Done well, governance should not slow the business down. It should make clear where AI can act, where people need to remain involved and what happens when the technology is wrong.

Technology enables transformation. People determine the outcome.