For years, Dynamics 365 Business Central customers who wanted proper expense management had one real option: bring in an outside app. Native expense tracking inside BC was thin at best, so most companies bolted on a third party tool just to handle receipts and reimbursements. Microsoft's new Expense Agent changes that story. It brings a full capture, categorize, and post pipeline directly into Business Central, sitting right next to the general ledger with no outside software required.
At Reach, we spend a lot of our time helping clients get more value out of the Microsoft business applications they already own, and this is exactly the kind of feature that quietly changes what a Business Central rollout can do. Here is how it actually works, from the moment an employee snaps a photo of a receipt to the moment it lands as a posted entry in the GL.
Capturing receipts without a Business Central license
The Expense Agent web app is where most employees will interact with this feature, and one of the smarter design choices is that casual users do not need a full Business Central license to use it. Instead, they consume Copilot Credits, roughly 50 credits per processed receipt. That keeps cost tied to actual usage rather than forcing every field employee onto a license just so they can submit a coffee receipt.
The flow itself is simple. A user opens the web app and drops in a receipt, whether it is a photo or a PDF. Email forwarding to a shared mailbox, Microsoft Teams, and Microsoft 365 Copilot chat all feed the same backend, so people can submit from whatever channel is closest at hand.
Once submitted, the expense sits in a processing status while the agent runs extraction. Worth flagging early for any security or compliance team involved in the rollout: Microsoft uses Anthropic models as a subprocessor for this step, which needs to be enabled through the Microsoft 365 admin center before any of this works.
From there, the agent pulls out merchant, date, total, currency, payment method, receipt number, and a suggested category, then drops the expense into a drafts tab for review. If the category needs itemization, hotel stays are the classic example, with room, breakfast, and minibar treated as separate lines, an itemization tab appears already filled in. Categories tied to group events, think morale outings or client entertainment, open a participants tab so the user can add internal employees or outside guests.
Mileage expenses skip the receipt entirely. The user enters a start and end point, the agent works out route options, and a screenshot of the chosen route attaches itself to the record automatically. Per diem works on similar logic, calculated from itinerary details with partial day rules applied based on setup.
Once everything looks right, the user groups expenses into a report and submits. Policy gets enforced along the way too, with soft warnings a user can override with a note, and hard blocks that stop submission until something is actually fixed.
Where all of this lands inside Business Central
The real strength of Expense Agent is that none of this data sits off in a separate silo. It flows into structures that already exist inside BC.
An expense is the basic unit. One receipt becomes one expense record, carrying category, subcategory, amount, currency, payment method, date, merchant, the attached receipt file, participants where relevant, and any itemized lines.
An expense report groups individual expenses into a single submission, moving through draft, submitted, and approved stages, much like how purchase and sales documents already move through BC.
Expense categories and subcategories get configured by an administrator and mapped to posting groups, and this is where the integration really earns its keep. Posting groups decide which GL accounts an expense hits once the report posts, so how something gets categorized at the point of capture directly shapes the journal entries that follow.
Approval workflow lives on the Expense Agent Setup page. Once the agent is turned on, BC automatically uses a newer workflow path, and the older, classic approval setup only comes into play for scenarios where the agent is not involved.
When a report posts, standard GL entries get created, and where reimbursement applies, vendor ledger entries post against the employee treated as a vendor. Whether something is refundable is configurable at the category and subcategory level, so a hotel bill with a room charge that is refundable and a minibar charge that is not gets split correctly without anyone touching it line by line.
Setup for all of this lives on one Expense Agent Setup page, organized into sections covering general settings, rules and controls, number series, communication, mileage and per diem, posting groups, and agent access control. Microsoft recommends starting with the assisted setup, called Configure Expense Agent, and only moving to the manual page once you need to fine tune something.
What to know before you turn it on
A few practical notes for anyone evaluating this. The preview is currently limited to the US and to English, with more regions expected in July 2026. The agent requires the Agent Admin and Expense Mgmt. Admin permission sets, a configured shared mailbox, and Anthropic enabled as a subprocessor in the admin center.
For partners and customers weighing this against an existing third party expense tool, the real question is not whether Expense Agent is objectively better. It is whether being native to BC, built around AI from the start, and light on licensing for casual users changes the math for your organization. For most midsize BC tenants, we think it does.
This is also a good example of why a periodic assessment of your Microsoft business applications setup pays off. Features like this ship quietly, and a lot of organizations do not find out they are sitting on new capability until someone goes looking. That is a core part of what our Project Assessments and Audits work is built to catch, alongside the AI Enablement work we do to help clients actually operationalize tools like Copilot once they are turned on. And once a feature like this is live, someone still needs to own the ongoing configuration, permission sets, and posting group logic behind it, which is exactly the kind of ongoing support our Managed Services team handles day to day.
Whether you are planning a fresh Business Central implementation, mid migration, or trying to get more out of a system that is already live, Reach has been through this across eight industries and counting. If you want a second set of eyes on whether your current setup is ready for something like Expense Agent, we are happy to take a look.
