Introduction
The Payables Agent caps at 100 emails a day. Attachments have to be under 5MB and no longer than ten pages.Whether that works for you depends entirely on your AP volume, and those numbers appear nowhere near the announcement.
Most of what has been written about Business Central AI agents this year skips that kind of detail. The launch posts list capabilities, the partner blogs restate the launch posts, and what goes missing is the part that decides whether any of it survives contact with your data. Which agents are generally available. Which are still pilots with a US-only footprint. What happens to the bill when volume climbs.
The three agents Microsoft actually ships in Business Central
Three agents, all built by Microsoft. Everything else you will hear about is either Copilot, which is assistive, or something you build yourself.
Sales Order Agent
Start here if you are in wholesale or distribution. It is the most mature of the three by a wide margin.
The agent watches a mailbox, opens incoming orders including PDFs, matches line items to your item catalog, runs a capable-to-promise check, and leaves draft sales orders for someone to approve.
Catalog matching is the whole ballgame. Feed it an email reading navy crew, med, 24 units, point it at a catalog where the same product exists as NVY-CRW-M, as Navy Crewneck Medium, and as item 4471, with no consistent unit of measure across the three, and you get drafts that take longer to correct than the order would have taken to key. The failure gets blamed on the agent, but it belongs to the catalog.
Payables Agent
Core invoice registration is generally available. Purchase order matching and confidence-level prioritization went to public preview in early 2026, which is awkward, because those are the two things finance teams ask about first.
Extraction runs on Azure Document Intelligence. Every document lands in the Inbound E-Documents table, so there is an audit trail when someone asks how a payable came to exist.
The vendor handling is the part worth copying. An invoice arrives from a vendor the agent cannot find, it builds a vendor card from the OCR output, and it saves that card in Blocked status. Nothing posts against it until a person has looked. Somebody at Microsoft clearly lost an argument about autonomy and won the right one.
Expense Agent
Announced April 2026. The iOS and Android apps reached the App Store and Google Play in July.
In practice it is a US pilot, and non-English receipts do not work. If you have people expensing in Manchester or Ho Chi Minh City, leave this one alone for now.
The licensing is more interesting than the feature. Expense Agent reaches employees who hold no Business Central license, which Microsoft has not done with an agent before. If 40 of your 300 people touch the ERP and the other 260 only file expenses, that changes the math.
What Copilot already does, and where it stops
Copilot helps someone already working in the system. Agents go off and do work. Both vendors and partners blur the two, usually to their own advantage.
Business Central’s native Copilot list runs longer than most buyers realize. Copilot chat queries your data. Analysis Assist runs ad-hoc analysis on list pages so nobody exports to Excel. Marketing text generation writes item descriptions. Bank account reconciliation proposes matches. Sustainability journals picked up Copilot-suggested gas emissions in public preview back in February.
Learn that list before you approve a development estimate. A partner quoting hours to build something Business Central already ships is either behind on releases or padding.
The limit is simple enough. Copilot answers; it starts nothing. Nothing in the feature set will work your inbox overnight and leave you something in the morning.
Copilot Credits change how you budget for automation
Every named agent burns Copilot Credits, and so does anything you build in Agent Designer. This is consumption billing, and it is the detail most likely to cause an uncomfortable conversation six months in.
Credits come prepaid or pay-as-you-go. What you burn depends on the agent and the action, so a Payables Agent drafting one clean invoice costs less than a Sales Order Agent working through a multi-turn exchange with capable-to-promise lookups. The bill follows transaction volume rather than headcount.
Usage and limits live on the Copilot and AI Capabilities page in the Business Central Admin Center. Set the limits during the pilot.
Underneath the technical point sits an organizational one. Per-seat pricing gets approved once and then nobody thinks about it again. Consumption pricing needs somebody looking every month, and mid-market finance teams rarely have a spare person to assign. When nobody owns it, the first anyone hears is a variance that needs explaining to a board.
Microsoft’s current licensing and capability documentation sits at learn.microsoft.com/en-us/dynamics365/release-plan/2026wave1/smb/dynamics365-business-central/planned-features and moves faster than any blog can track.
Agent Designer and the Business Central MCP server
Agent Designer reached general availability in May 2026, after a preview that opened February 6. It covers the processes the three built-in agents do not.
Microsoft also shipped an MCP server for Business Central. Model Context Protocol is a standard connection point, and it lets AI clients including Copilot Studio, GitHub Copilot, Claude, and ChatGPT read Business Central data and, where you allow it, write to it.
MCP matters more than Agent Designer does. It turns Business Central into something other tools can operate rather than an application people log into, which opens up the seams between systems where most of the manual work actually lives. Anyone running Business Central alongside a PLM system and a 3PL portal knows the seams in question.
The phrase carrying the weight there is where you allow it. Agents run inside Agent Permission Sets and Profiles that an administrator assigns, so there is no blanket access. There is also no default configuration that happens to be right for you.
Who owns the agent when it breaks
Almost nobody raises this during evaluation, and it shapes the outcome more than the feature comparison does.
Built-in agents are Microsoft’s code. The model or the logic underneath can change, and it changes on Microsoft’s schedule. You trade timing control for robustness and no maintenance burden.
Custom agents built in Agent Designer or orchestrated through Copilot Studio join your extension estate. Same change management, same testing, same version control you already apply to AL. The failure mode is treating one like a report layout, configuring it once, then finding out three weeks later that a process change upstream quietly broke an assumption the agent had been making.
The release wave calendar is going away
Microsoft is ending release waves. From September 2026 everything publishes continuously on the AI at Work roadmap. No Wave 2 plan this September. Release Planner shuts down on November 15, and saved views in My Release Plans do not survive it.
Product schedules are unaffected. Your planning process is not. If a steering committee sits down every spring and fall to review the release plan and decide what to adopt, that meeting has just lost its input.
What we tell clients before turning any of this on
Four things shape how Volt approaches agents. Vertical expertise in apparel, footwear, home furnishings, consumer products, manufacturing, and distribution. A hands-on engagement model, which means consultants with real industry backgrounds working inside your process instead of delivering to it from a distance. Enterprise methodology at mid-market scale and cost. And 24/7 follow-the-sun support, because supply chains keep no office hours.
ERP is a decade-plus commitment and agents now sit inside that horizon. The Sales Order Agent you switch on this quarter will still be running against a catalog you have restructured twice by 2036. That timeframe changes what ready means.
Three things we insist on before an agent goes live:
- Master data first. Standardized item descriptions, consistent units of measure, clean dimensions. This is unglamorous and it is the entire foundation.
- One process, measured. A single agent against a single workflow, with touch time and error rate baselined before you switch anything on. A pilot named automate AP produces nothing anyone can act on.
- A named owner for consumption, with the authority to change limits.
Our clients run Volt 365®. Volt 365® Apparel handles SKU complexity, seasonal planning, and wholesale plus DTC operations for fashion and footwear brands, and the same foundation carries across the manufacturing, distribution, furniture, and consumer products businesses we work with.
If you are weighing which agents fit your operation, our Business Central practice page covers the data foundation that has to come first. The apparel practice and consumer products practice show what this looks like for brands running wholesale and retail together.
Frequently Asked QuestionsÂ
Business Central ships three Microsoft-built agents: the Sales Order Agent, the Payables Agent, and the Expense Agent. The Sales Order Agent and core Payables Agent invoice registration are generally available. Expense Agent is newer, with mobile apps released in July 2026 and availability still concentrated in the US. Additional agents can be built using Agent Designer, which reached general availability in May 2026.
Copilot capabilities are part of Business Central, but the agents bill separately through Copilot Credits on a consumption basis rather than per-seat. Credits are provisioned prepaid or pay-as-you-go and monitored from the Copilot and AI Capabilities page in the Business Central Admin Center. Consumption depends on which agent runs and what actions it takes.
No. Copilot and agent capabilities require Business Central online. On-premises and hybrid deployments have no access to them, so organizations still on-premises need to complete a cloud migration first.
Copilot assists a person already working in the system, answering questions, drafting text, and suggesting matches when asked. An agent works autonomously, monitoring an inbox or process and preparing transactions for approval without a person opening the record first. Copilot waits to be asked, while an agent starts the work itself.
No. Customer service agents belong to Dynamics 365 Customer Service, a separate application. Business Central's agents cover sales orders, payables, and expenses. Organizations needing both run the two applications together.
The Model Context Protocol server is a standardized connection point allowing AI clients including Copilot Studio, GitHub Copilot, Claude, and ChatGPT to read Business Central data and, with permission, write to it. It lets external AI tools act on ERP data without custom point-to-point integrations. Access is governed by Agent Permission Sets and Profiles that administrators assign.
