A 5-layer way to think about AI-native ERP.

The framing comes from Andrew Cooper of P3M and his "AI-native ERP architecture" piece. His claim: in the next generation of ERP, AI isn't bolted onto a legacy core — it is the core. He draws it as five layers, each with one job. I keep coming back to it, so here's my working copy.

The five layers

1 · Generative AI — the interface. Natural language in, natural language out: conversational queries, AI-generated reports, document generation. This is the layer everyone can picture, because it's the layer today's copilots already occupy.

2 · Agentic AI — domain agents. Autonomous agents that each own a domain — finance, procurement, supply chain, HR, sales — and execute within it. The design principle is collaboration, not competition: agents work through well-defined interfaces and share context instead of fighting over it.

3 · Symbolic AI — deterministic compliance. Not a model: rules. SOX controls, GAAP/IFRS, tax and regulatory logic, the audit trail. Every action from the layers above passes through this checkpoint before anything is persisted.

4 · Unified data. One converged layer — transactional database, knowledge graph, vector store, event stream — instead of the silo sprawl that produces the integration tax every traditional ERP estate pays.

5 · Integration. The connectors to the outside world: banking APIs, supplier APIs, tax authorities, third-party SaaS.

A request flows top to bottom: the generative layer takes the question, the agent that owns the domain picks it up, the symbolic layer validates it, unified data persists it, and integration reaches out when the outside world is involved.

The stack, sketched — coral marks the deterministic checkpoint and today's system of record:

Why the symbolic layer is the one that matters

Layer 3 is what separates this from "wrap an LLM around your ERP". Finance and compliance can't hallucinate. A VAT rule is not a probability, and an audit trail that's mostly right is worthless. Making the deterministic rule layer first-class architecture — rather than bolted-on configuration — means every AI action is validated before it touches the books and auditable afterwards. Compliance built in, not bolted on. That's the part of the model I'd defend hardest.

Where Business Central sits

BC today is the system of record — the transactional core and most of layer 4, carrying decades of accounting discipline. Microsoft's Copilot story maps roughly onto layer 1. The interesting gap is the middle: I haven't seen anyone building public agentic and symbolic layers on top of BC yet. So the five layers aren't a product you can buy. They're a map of where the value in ERP work is moving — away from screens, towards agents governed by deterministic rules.

What I'm still chewing on

Does the model survive scaling down? On an enterprise D365 footprint, a full symbolic compliance layer plainly earns its keep. On a small or midsize BC tenant, I'm not sure whether Symbolic AI stays a distinct layer or collapses into what we already call configuration — posting groups, VAT setup, approval workflows. If it collapses, then the deterministic layer already exists in every well-implemented BC tenant, and the missing piece isn't compliance at all — it's the agentic middle. I don't have the answer yet. That's what this note is for.