Business Central AI Agents: What Sales Order, Payables, and Expense Agents Actually Do
Table of Contents
Quick Answer: What Do Business Central AI Agents Do?
Business Central AI agents automate defined parts of sales, payables, and expense management while keeping people involved where review or judgment is required.
The Sales Order Agent turns customer emails into quotes and sales orders. The Payables Agent extracts vendor invoice data, creates draft purchase invoices, and matches invoices to purchase orders and receipts. The Expense Agent captures and categorizes employee expenses and prepares expense reports for review.
Sales Order and Payables are generally available, while Expense Agent remains in production-ready preview. All three work best when Business Central data and processes are clean and consistent.
Introduction
Ask what Copilot does in Business Central, and you’ll still hear a lot about writing product descriptions, summarizing records, or helping someone get through a task faster. Those features are useful, but they’re no longer the interesting part. The bigger shift is toward Business Central AI agents that can take action across defined workflows, with people stepping in where review, approval, or judgment is still required.
Right now, the three agents worth knowing are the Sales Order Agent, the Payables Agent, and the Expense Agent. Sales Order and Payables are generally available, while Expense Agent is still expanding in preview. They solve very different problems, and the distinction matters: one handles incoming sales requests, another handles vendor invoices and purchase-document creation, and the third aims to take much of the friction out of employee expense reporting.
What matters is how much work each agent can take off your team’s plate, where human review still sits, and whether your Business Central data and processes are clean enough for the automation to work well in the first place. Here’s what each agent does, where the limitations sit, and what to look at before turning one on.
What Does the Sales Order Agent Actually Do?
The Sales Order Agent receives incoming customer requests via email and converts them into sales documents in Business Central. It reads the message and supports attachments, identifies the customer, matches requested products against existing item data, checks availability, and creates a sales quote as the starting point.
From there, it can handle follow-up emails, update the quote when a customer requests changes, and convert an accepted quote into a sales order. It doesn’t quietly process everything in the background. Users are brought in when the agent needs assistance or review, and outgoing customer messages require human review before they are sent.
The quality of your Business Central data matters here. The agent has to match whatever a customer writes in an email or purchase order with the customers and products already in the system. Microsoft specifically notes that even product naming can affect the quality of its results. Poor or inconsistent data simply creates more cases where someone has to step in.
What Doesn't the Sales Order Agent Do?
It doesn’t make every sales decision for you. Customer-requested pricing or discount changes require human intervention, and the agent cannot create new customers or items when it can’t find what it needs.
Its role is more specific: take on much of the repetitive work between receiving a customer request and getting a clean sales order into Business Central, while bringing people in when the process requires judgment.
What Does the Payables Agent Actually Do?
The Payables Agent handles one of the more repetitive parts of accounts payable: converting vendor invoices into purchase documents ready for review.
It monitors a designated Microsoft 365 mailbox for PDF invoices, extracts invoice data, identifies the vendor, suggests how invoice line items should be classified, and creates a draft purchase invoice in Business Central. When purchase orders are involved, it can also perform three-way matching across the invoice, purchase order, and receipt, including cases where the vendor invoice doesn’t provide a clear reference to the order.
The agent also uses existing Business Central data rather than treating every invoice from scratch. It can review historical transactions when identifying vendors and suggesting G/L accounts, and it pauses for human input when it encounters uncertainty or higher risk.
What Doesn't the Payables Agent Do?
It doesn’t remove the review step from accounts payable. The agent prepares the purchase document and flags issues that need attention, but users still review the draft before it enters the normal approval and posting process.
And the quality of the process still depends on what it has to work with. Three-way matching is far more useful when purchase orders and receipts are recorded consistently. If the invoice arrives with no usable purchasing trail, the agent can still help with extraction and classification, but there is less for it to match automatically.
What Does the Expense Agent Actually Do?
The Expense Agent tackles the employee side of expense management. Employees can submit receipts through the dedicated Expense Agent web app, from a mobile device, or by forwarding them to a shared mailbox. The agent extracts the receipt data, categorizes and itemizes the expense, creates the expense line, and groups expenses into reports for review and approval.
The aim is to remove much of the manual work that normally happens between keeping a receipt and submitting a complete expense report. Employees can still review and correct the information before submission, while managers remain part of the approval process.
Expense Agent is also expanding beyond basic receipt capture. It can support project expense allocation, and Microsoft is introducing travel requisitions so that employees and managers can request and approve business travel before expenses are incurred.
What Doesn't the Expense Agent Do?
The biggest limitation right now is maturity. Unlike Sales Order and Payables, Expense Agent is still a production-ready preview, and several capabilities are still rolling out.
That makes it worth evaluating, but not something to treat as a settled feature set yet. If expense management is part of your Business Central roadmap, check the current availability of the specific capabilities, languages, and regions you need before building a rollout around them.
What Ties the Business Central Agents Together?
The three agents automate very different processes, but the operating model is similar: each works against data already in Business Central, takes on a defined part of a business process, and brings a person back in when the task needs review, correction, or judgment.
| Agent | Current Status | Starts With | Produces | Where People Step In |
|---|---|---|---|---|
|
Sales Order Agent |
Generally available |
Customer emails and supported attachments |
Sales quote, then sales order |
Missing information, pricing or discount exceptions, customer communications, and configured document reviews |
|
Payables Agent |
Generally available |
Vendor invoice PDFs |
Draft purchase invoice, including PO and receipt matching where applicable |
Uncertain fields, exceptions, document review, approval, and posting |
|
Expense Agent |
Production-ready preview |
Receipts submitted through web, mobile, email, or Copilot |
Categorized expenses and expense reports |
Corrections, policy issues, report review, approval, and posting |
That human-in-the-loop model is important. Business Central keeps agent activity visible rather than treating it as a black box. Tasks that need attention can be surfaced for review, and Microsoft’s agent runtime is designed to keep actions traceable and constrained by the permissions assigned to the agent.
There is also a broader platform story developing around these built-in agents, but it is separate from how Sales Order, Payables, and Expense Agent themselves operate. Business Central’s MCP server can expose approved data and business actions to Copilot Studio and other MCP-compatible AI clients, giving organizations another way to build agent experiences around their own processes.
In other words, the three Microsoft-built agents are the starting point, not the full boundary of what Business Central can support.
Not Sure If Your Business Central Environment Is Ready for AI Agents?
Before enabling an agent, it helps to know whether your data, workflows, permissions, and licensing setup can support it. AlphaBOLD can assess your current Business Central environment and identify what needs attention before rolling out.
Request a ConsultationThe Data Readiness Question Nobody Asks Before Turning Agents On
Agent conversations tend to jump straight to configuration: connecting the inbox, assigning permissions, and setting up the workflow. The harder question comes first: is the data underneath that process clean enough for an agent to work with reliably? That isn’t just a Business Central problem. Gartner has warned that weak semantic context can make AI agents inaccurate and inefficient, increasing both cost and governance risk.
For Sales Order Agent, product data matters immediately. The agent has to take whatever a customer writes in an email or purchase order and find the right item in Business Central. Microsoft specifically notes that product naming can affect the quality of its output, and richer descriptions, attributes, categories, and item references give it more to work with.
Payables Agent has a similar dependency. It uses existing vendor records, transaction history, accounting information, purchase orders, and receipts to identify vendors, classify invoice lines, and match documents. The cleaner and more consistent those records and processes are, the less ambiguity the agent has to resolve.
That doesn’t mean everything has to be perfect before you switch agents. It does mean an agent won’t quietly fix years of inconsistent master data or process shortcuts for you. In many cases, it will expose those problems faster.
Before rollout, look at the records the agent will actually depend on: duplicate customers or vendors, unclear item descriptions, inconsistent identifiers, missing purchase orders, incomplete receipts, and process knowledge that exists only in someone’s head. Fixing those gaps isn’t the exciting part of an AI project, but it can determine how much work the agent actually takes off your team’s plate.
You may also like: 7 Reasons to Adopt Dynamics 365 Business Central Project Management
Where Does Human Judgment Still Sit?
These agents are autonomous enough to move work forward but not designed to make every decision without oversight. Business Central surfaces tasks that need attention, lets users review what the agent changed, and records the steps taken along the way.
For Sales Order Agent, that can mean reviewing customer emails, quotes, orders, or missing information before the task continues. Payables Agent similarly pauses when invoice data or document details require verification, while Expense Agent asks employees or approvers to review extracted and categorized expenses as needed.
Business Central also gives users more than a simple approve-or-reject screen. On supported documents, you can see which fields an agent changed, the reasoning behind a suggestion, and where confidence is lower. If the agent gets stuck, a user can correct the data, give it additional instructions, or stop the task entirely.
That is the most useful way to think about agentic automation in Business Central: automate the predictable work, make exceptions visible, and keep people involved where the business decision actually matters.
How Are Business Central AI Agents Licensed?
Business Central licensing doesn’t automatically cover the usage generated by its AI agents. Sales Order, Payables, and Expense Agent require Copilot Credits, which are consumed as the agents perform AI-powered actions.
Microsoft offers different ways to fund that usage, including pay-as-you-go and prepaid Copilot Credits. The amount consumed depends on what the agent is doing and the complexity of the action, rather than simply how many employees use it.
This is also where a Business Central partner can be useful. You don’t need a partner simply to purchase Copilot Credits, but a partner can help estimate expected agent usage, choose the appropriate billing approach, configure the environment, and monitor consumption once the agents are running. For organizations already buying Business Central through a Microsoft partner, it also makes sense to work through that partner when planning the licensing and rollout together.
Before turning an agent on a scale, work out both sides of the equation: what the process costs to run today and what the agent is likely to consume in Copilot Credits. The point isn’t just to enable an agent. It’s to make sure the work it removes is worth the cost of running.
You may also like: Guide to Microsoft Copilot Pricing & Licensing
Conclusion
Business Central’s AI agents are useful because they take on specific, repetitive parts of a process rather than trying to automate everything at once. Sales Order Agent helps move customer requests into sales documents, Payables Agent reduces manual invoice work, and Expense Agent is beginning to streamline employee expense management.
The harder part is not deciding whether the agents are capable. It is deciding whether the process underneath them is ready. Clean data, consistent workflows, appropriate permissions, human review, and a clear view of Copilot Credit consumption all affect the value an agent can deliver.
Start with the process where the manual work is easiest to identify and measure. If the agent has a clear job, reliable information to work with, and an obvious place for people to step in when judgment is required, it becomes much easier to determine whether the automation is worth scaling.
See Where Business Central Agents Fit Your Processes
AlphaBOLD can help assess your current Business Central setup, identify the processes best suited for agent-driven automation, and plan the licensing, configuration, governance, and rollout around them.
Request a ConsultationFAQs
Sales Order Agent and Payables Agent are generally available. Expense Agent is still available as a production-ready preview, so organizations should confirm the availability of the specific Expense capabilities, languages, and regions they need before planning a rollout.
Not entirely. The agents can move defined tasks forward independently, but users are still brought in when information is missing, an exception occurs, or a business decision requires review. The exact review points differ by agent and workflow.
Yes. Sales Order, Payables, and Expense Agent consume Copilot Credits separately from standard Business Central user licensing. Organizations can use prepaid credits or supported pay-as-you-go options, depending on how their environment and billing are configured.
Yes, but Microsoft’s custom-agent capabilities are still evolving. Business Central can also expose approved data and business actions through its MCP server for use with Copilot Studio and other compatible AI clients, giving organizations options beyond Microsoft’s pre-built agents.
Start with the process and the data behind it. Check whether the customer, vendor, item, purchase order, receipt, and other records the agent depends on are sufficiently consistent to support reliable automation. You should also define where human review is required, how permissions will be handled, and how Copilot Credit consumption will be monitored.
