What a long-horizon AI agent actually does in an ERP (and what it shouldn't)

"Agent" is the word of the year, and most of what is said about it is hype. So let me answer the practical question plainly, from building these things: what does a long-horizon AI agent genuinely do inside an ERP — and, just as importantly, what should it not be trusted to do yet?

The difference between a chatbot and an agent

A chatbot answers a question. You ask, it responds, the exchange ends.

An agent does work. It holds a goal across many steps, gathers what it needs from several systems, takes actions, checks the result, and adapts when something is off — over minutes or hours, not one reply. "Long-horizon" is the key phrase: the value is in holding context across a long task, not in a clever single answer.

Inside an ERP, that difference is everything. The interesting problems in an ERP are not single questions. They are multi-step processes that touch several systems and span time — exactly the shape an agent is built for.

What it actually does, concretely

Strip away the hype and a long-horizon agent in an ERP does a handful of very real things:

• Reads across systems to assemble context. The ERP, the documents in a drive, the CRM, the email trail — an agent can pull the scattered pieces together into one picture a person would otherwise assemble by hand across five tabs.
• Takes typed, bounded actions. Not "do anything." A defined set of actions — create the draft quote, flag the clause, update the field, open the case — each one specified and permissioned, so the agent acts within a fence, not across the whole system.
• Checks its own work and escalates. It scores its confidence, and when it is unsure, it stops and hands the decision to a person rather than guessing. That handoff is a feature, not a failure.
• Holds the thread over a long task. It remembers where it is in a multi-step job, so it can carry a process — research to draft to review to sync — instead of forgetting between steps.

The connective tissue for a lot of this is a well-scoped integration surface — for Dynamics that increasingly means an MCP server that lets a model act on ERP data through supported, permissioned actions, not just report on it.

Where a person still decides — by design

Here is the part the hype skips: a good agent in an ERP is deliberately not fully autonomous.

The ones worth deploying prepare the decision and let a person take it. The quote is drafted; a person presses send. The contract clause is flagged; a lawyer makes the call. The reorder is recommended; a planner approves. This is not timidity — it is the correct architecture for a system of record, where a wrong action has a real cost and an audit trail matters. "Human in the loop" is a design choice, and in an ERP it is the right one.

And there is a line you should insist on: an agent should never quietly modify core ERP logic. It reads the system of record and acts through the platform's supported, permissioned surface — beside the ERP, not inside its guts. Anything else trades a demo for a risk your operations team will never accept.

What it shouldn't be trusted to do yet

Honesty matters more than hype here:

• Irreversible actions without approval. Posting the transaction, sending the payment, signing the thing — those stay behind a human step.
• Anything it can't show its reasoning for. If the agent can't cite why it acted, it shouldn't have acted. Evidence over assertion.
• Judgement dressed up as search. An agent is excellent at assembling context and executing bounded steps. It is not a substitute for the commercial, legal or operational judgement that is the actual job.

The honest summary

A long-horizon agent in an ERP is not magic and it is not a replacement for your team. It is a tireless operator that assembles the context, does the routine multi-step legwork, and hands the decision to a person — inside the systems they already use, without touching the core.

That is where the real value is, it is where the market (and the capital) is now moving, and it is exactly what we build on Dynamics 365 and Business Central. See how the pieces fit at agentic ERP, or tell us the multi-step process that is eating your team's time.