Solution · By software

Business Central already ships with Copilot and with agents. And your team is still typing, because the work doesn’t happen inside Business Central: it happens between Business Central and everything else.

Microsoft has done its part: Copilot is included in your license and the Payables and Sales Order agents work end to end inside the ERP. What they don’t cover is what comes in through the odd email, the sales rep’s Excel, the PDF that isn’t a PDF and the industry system that doesn’t talk to Business Central —nor what those agents are going to cost you every month, which is billed by consumption. We build the layer that does that work, and we put a number and a brake on the one you already have running.

Ship it in my business See how it works

The problem

The ERP already ships with AI. The hours still go into the part of the process that happens outside the ERP.

The native agent processes the supplier invoice that arrives as a clean PDF; the one that arrives in an email with the amount in the body, as a photo or in an industry format, someone still keys in by hand.
Copilot helps you inside the screen you’re already on, but the data that needs moving comes from an Excel, a customer portal or an industry system that isn’t connected to Business Central.
Nobody can tell you what the agents cost this month: they’re billed by consumption and the number shows up somewhere else, in the Power Platform admin center, not on your ERP invoice.
One day the agent stops processing emails and nobody flags it: capacity ran out, and the work sits in the inbox waiting for someone to buy more.

Cost of staying the same

You pay for a license that already includes AI and you keep paying your team’s hours for the cases the out-of-the-box AI doesn’t touch —which happen to be the ones that create the most work: the supplier with its own format, the exception, the data that lives elsewhere. And on the other side you run a variable cost with no control: Business Central agents are billed by consumption in Copilot Credits, and Microsoft’s documentation says it without hedging —when the quota runs out, AI capacity isn’t available until more is added—. Without measurement, that isn’t a saving: it’s spend you can’t read and a stoppage you find out about late.

The solution

We govern what Business Central already ships and automate what falls outside it, on your own environment

1We inventory what your Business Central already does: what Copilot solves inside the screen, which native agents you have switched on —Payables, Sales Order, Expense— and which real cases slip past them today. No duplicating what Microsoft already gives you.
2We put a number on the consumption: we measure the Copilot Credits your agents burn per document and per line, we set up the alert before the quota runs out, and we decide with you what stays in the native agent and what ships cheaper outside it.
3We automate the gap through the Business Central API: the invoice that arrives in a format the native agent doesn’t process, the order that comes in through a portal, the data that has to be pulled from the Excel or the industry system, and the exception that today ends up as an email to admin.
4We leave it measured and with a safety net: every flow starts in propose mode with a person validating, and autonomy only gets released by document type when the data backs it up. Dashboard with what % comes in without intervention, what escalates and how much the consumption is costing.

What changes

What you stop losing

The cost of your ERP’s AI stops being a surprise: Business Central agents are billed by consumption in Copilot Credits, with published rates per document and per line, so it can be estimated up front and watched afterwards instead of discovered on the invoice.
[Manage consumption-based billing for agent capabilities](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-manage-consumption-billing), Microsoft Learn, updated July 8, 2026.
The silent stoppage stops being silent: Microsoft warns inside the app itself when the quota is low, but if nobody looks, the work piles up in the inbox. We set up the alert where it does get seen, and the plan for what to do meanwhile.
[Manage consumption-based billing for agent capabilities](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-manage-consumption-billing), Microsoft Learn, updated July 8, 2026.
Your team stops being the fallback for the out-of-the-box AI: the cases the native agent doesn’t process —odd format, data from outside, exception— stop landing back in the admin inbox and get a flow of their own.
Mechanism
What we measure: % of documents that enter Business Central without intervention (native + our layer), which cases slip past the native agent and why, Copilot Credits consumed per document and per line, and processing time versus the previous manual process.
What we measure

Spec sheet

Work it removes: having your team be the fallback for the AI the ERP already ships: keying in the cases the native agent doesn’t process, and not knowing what that agent is costing
Typical setup: 2–4 weeks
Input: what falls outside the native agent today: the email with the amount in the body, the invoice as a photo or in an industry format, the Excel, the customer portal and the industry system; plus your environment’s Copilot Credits consumption
Output: the document dropped inside Business Central through its API with its account and its line, the exception routed to a person with context, and a dashboard with what comes in on its own and what it costs
Works with: Microsoft Dynamics 365 Business Central (online)Payables AgentSales Order AgentExpense Agent (preview)Microsoft 365 (Outlook, Excel, SharePoint)Power Platform admin center
Can connect to: Your online Business Central environment through its APIThe shared mailbox of your native agentsYour outside-the-ERP sources: email, folders, Excel, portals and industry systems
What we measure: % of documents that come in without interventioncases that slip past the native agent and whyCopilot Credits per document and per lineprocessing time versus the previous manual process
Good fit for: companies already on Dynamics 365 Business Central online that have switched on Copilot or a native agent and still burn hours typing the exceptions, or that don’t know what the consumption is costing them
Not a fit for: on-premise Business Central installs, where Copilot and the native agents aren’t available; and processes the native agent already covers well, which we don’t touch

Frequently asked questions

No, and that’s exactly why we don’t replace them. With your Business Central license everyone gets a copilot at no extra cost, and the autonomous agents —the Payables one is the example Microsoft itself uses— run the process end to end with human supervision. You already have that, and it would be absurd to pay us to rebuild it. We do two things that package doesn’t: automate what happens OUTSIDE the ERP —the email with its own format, the Excel, the portal, your industry system— and govern what’s already running inside, starting with its cost. Source: Copilot and agents in Business Central, Microsoft Learn, updated August 27, 2026.

It depends on volume, and the good news is Microsoft publishes the rates, so you can estimate before switching them on. Billable agents are charged by consumption in Copilot Credits: the Payables one burns 50 credits to process an invoice plus 5 for each line, and the example in Microsoft’s own documentation —100 invoices a month with 3 lines— works out to 6,500 Copilot Credits a month. The Sales Order one goes by events: 2 credits to analyze the email, 5 to check availability, 5 to create or update the order, 2 to generate the reply. There are two billing models, prepaid capacity and pay-as-you-go. The number isn’t the point —it changes with your volume—: the point is that almost nobody looks at it until it lands. Source: Manage consumption-based billing for agent capabilities, Microsoft Learn, updated July 8, 2026.

The AI stops. Microsoft’s documentation says it literally: when the quota runs out, AI capacity isn’t available until more is added. Business Central checks capacity regularly and warns inside the application when it’s low, but that warning is seen by whoever happens to be looking at that screen —not necessarily whoever runs admin on a Friday afternoon—. What we build is the alert where it does get seen, a threshold with room to react, and the plan for what happens meanwhile: what gets routed to a person and what waits. Source: Manage consumption-based billing for agent capabilities, Microsoft Learn, updated July 8, 2026.

For the native part, no: Copilot and the agents are only available to Business Central online customers, so on-premise there’s nothing to govern because there are no agents. For the other half —automating what comes in through email, Excel or your industry system and dropping it inside the ERP— it can be built, but it’s a different project: the connection route changes and the scope changes, so it gets estimated separately. We tell you that before the first meeting, not after. Source: Copilot and agents in Business Central, Microsoft Learn, updated August 27, 2026.

Want it running in your business?

You’ve pinned the problem. We ship the fix and leave it measured.

See the service