Where the margin holds: governance isn't paperwork, it's profit protection

So far we have argued that AI in professional services has to reason, not just route (Part 2), and that it can only reason if it understands your world (Part 3). This article is about the safeguard that matters most once the AI does understand your world: staying in control of what it is allowed to do.

In services, governance is not paperwork. It is the difference between a margin that holds and a margin that leaks. A project drifts and nobody notices. An invoice is booked to the wrong entity. A revenue recognition call slips past quarter-end. None of those is a dramatic failure. Each is a quiet one, and each lands somewhere no one wants to defend.

A confident system can still be wrong

The instinct with a new AI feature is to let it act and review what it did later. But a log written after the invoice has gone out does not protect the margin. The value has already leaked. And the risk is not only that the AI gets an answer wrong. As Jepsen puts it, the harder problem is that a reasoning system can be sure of itself and still be mistaken:

"A system that evaluates can be confident and still be wrong." — Claus Jepsen, Chief Technology Officer, Unit4 (Diginomica)²

His conclusion is blunt, and it is the line every services leader should hold onto:

"Autonomy without [governance] is not capability. It is exposure."²

The market agrees. In McKinsey's 2026 research on AI trust, security and risk concerns were the single biggest barrier to scaling agentic AI, cited by close to two-thirds of organisations, ahead of regulatory uncertainty and technical limits combined. Inaccuracy worried 74% of respondents and cybersecurity 72%.⁴ Inside the sector, SPI Research reaches the same conclusion: effective AI adoption, its 2026 benchmark notes, depends on "robust data foundations, organizational readiness, governance, security, and long-term change management" rather than enthusiasm alone, and firms will not hand the redesign of their operating models to AI "without human oversight and accountability."⁶ The lesson is not to slow down. It is to build control in before the action, not after it.

How Unit4 approaches it

ERPx treats governance as something that happens before an action executes, not something reconstructed afterwards. A governance layer checks every AI action against your firm's own policies and delegated authority before it runs. It is an active gate, not a passive log. In practice that means four things.

Every action is bounded. The AI operates inside your own thresholds and delegated authority, and cannot act beyond the guardrails you have set.

Uncertainty is routed, not hidden. Confidence scoring reads each decision. When the case is clear it proceeds. When it is not, it goes to the right owner, with the reasoning visible.

Override is always yours. A person can step in at any point, and when they do the reason is logged, so the exception is a decision on the record rather than a gap in the trail.

The trail is ready, not reassembled. Every action can we reconstructed later, with its inputs, its rationale and the governance that was applied, because the rationale was captured as the action happened.

The takeaway

In a services firm, control and value are not in tension. Control is what makes the value bankable. An AI you can rely on is one that makes consistent decisions inside your rules, accepts a human override at any time, and leaves a complete trail behind it. That is not a brake on the margin. It is how you keep it.

The best way to judge the guardrails is to put them to work. If you are already a Unit4 customer, you can try our AI for free and see how it keeps every action inside your rules: https://www.unit4.com/try-our-ai. If you are new to Unit4, find out more about AI at Unit4 at https://www.unit4.com/ai-native-erp.

Next in the series: control keeps AI safe, and understanding makes it useful. We bring it together and ask the only question that really counts. Does the working week get better?