Business Central AI agents: what the Payables and Expense agents do, and where a custom build takes over

For a long time, "AI in the ERP" was an enterprise conversation — SAP estates, Finance & Operations, the big end of town. Business Central was an afterthought. That's changed. Microsoft is shipping real agents into Business Central, which means the mid-market finance team now has the same decision the enterprise has been chewing on: use the first-party agents, build custom, or both?

Here's the honest map for Business Central specifically.

What Microsoft ships for Business Central

Two named agents aimed squarely at the finance back office:

• Payables Agent — reconciles purchase orders more accurately, using item amounts and expected goods receipts to match invoices to what was actually ordered and received. This is the three-way-match grind, handled by an agent.
• Expense Agent — checks expense reports for policy violations or suspicious entries, so the exceptions surface instead of someone manually reading every line.

The right way to think about both: they clear the routine so your team operates by exception. The Payables Agent handles the invoices that match cleanly and surfaces the ones that don't; the Expense Agent passes the compliant reports and flags the ones that break policy. Your people stop processing and start reviewing — which, in a small finance team, is the whole point.

If your AP and expense processes run close to standard Business Central, start with these. They're native, low-risk, and they target exactly the work a mid-market team has too few people for.

Where the first-party agents stop (and the mid-market still needs more)

Mid-market doesn't mean simple. Business Central estates are customized too — and the gaps are the same three, just at a scale where a small team feels them more sharply:

1. Your customizations and ISV add-ons. Most Business Central companies run industry ISVs and bespoke fields. The first-party agents reason over standard BC; your customizations are invisible to them. Reaching them safely needs governed MCP Action tools.
2. The decisions BC records but can't compute. Payables and Expense are exception-clearing agents. They don't compute the decisions that move margin — pricing, safety stock, the quote. Those are AI optimization apps, a different category, and Microsoft doesn't ship them.
3. Your specific processes and controls. Your approval thresholds, your segregation of duties with a small team wearing several hats — that's your design, and it needs to be codified and governed, not assumed.

When a Business Central team should build

Build — on top of Business Central, never replacing it — when:

• Your AP or expense process carries real customization or ISV logic the agent can't reach.
• You need a decision computed, not just exceptions cleared — pricing, demand/inventory, quoting against your own catalogue (this is where Quote Rabbit fits a BC distributor).
• Your controls need to be tighter and clearer than out-of-the-box, which matters more with a small team where one person often holds several roles.

And a practical mid-market note: the trap is a small team adopting an agent, letting it run on messy data or blurred roles, and quietly trusting output it shouldn't. The readiness that an enterprise does deliberately, a mid-market team has to do too — just lighter. (See agent readiness for Dynamics 365.)

The decision in one line

Use the Payables and Expense agents for standard AP and expense work; build custom for your ISV customizations, the decisions BC can't compute, and the controls a lean team needs. It's not either/or — the custom work sits on top of the first-party agents and often makes them usable on your customized Business Central.

If you run Business Central and want to know which of these your team should turn on first, tell us how your AP, expense or quoting process actually works — including the exceptions, because that's where the real decision is.