Most expense management improvements over the years have been incremental. Better OCR. Faster receipt capture. A mobile app instead of a desktop form. The underlying workflow stayed the same: employee collects receipts, employee manually enters data, finance team chases what’s missing, someone reconciles everything at the end of the month.

On the flip side, all we hear is AI this, AI that.

That’s the difference with the Dynamics 365 Business Central Expense Agent. It’s AI-native, not AI-enhanced and it changes how expense reporting in Business Central actually works.

Read more about What AI Agents in Dynamics 365 Actually Do

What Is the Business Central Expense Agent?

The Business Central Expense Agent is a new AI-native feature in Dynamics 365 Business Central that automates the full expense reporting lifecycle from receipt capture to policy validation to expense report submission without requiring employees to manually enter data or open an ERP screen. It is part of the 2026 Release Wave 1 and is currently available in public preview for US-based environments.

The Real Problem With Traditional Expense Reporting

Most employees don’t hate expense policies. They hate the administrative friction around following them.

Receipts pile up. Expenses get submitted weeks late. Finance teams chase missing documentation. Employees forget project details, attendees, or categories. Managers approve reports with incomplete information because nobody wants to hold up reimbursement over one missing receipt.

And nearly every finance team has at least one employee who waits months to submit expenses not because they’re avoiding the process, but because the process itself is tedious.

Why Traditional Expense Reporting Slows Down Your Team

The manual coordination, the back and forth, the babysitting. It isn’t for the faint of heart.

Employees often need to:

• Save and organize receipts
• Remember who attended a client dinner
• Categorize expenses correctly — is this “Travel – Meals” or “Client Entertainment”?
• Match expenses to projects or customers
• Understand reimbursement policies
• Reconstruct business purpose days or weeks later
• Build and submit reports manually

Meanwhile, finance and AP teams spend time:

• Chasing missing receipts
• Correcting inconsistent categorization
• Reviewing incomplete submissions
• Validating policy compliance
• Following up on missing justifications
• Cleaning up reporting inconsistencies during month-end close

The administrative overhead adds up quickly on both sides. This is one reason Microsoft’s new Expense Agent feels meaningful. It addresses a workflow employees and finance teams already deal with constantly.

How Business Central’s Expense Agent Automates Expense Reporting

This is where the day-to-day value becomes obvious.

You’re traveling. You have a client dinner. You take a photo of the receipt, which you’re already doing, and forward it to your company’s shared expense mailbox. That’s your part of the process. The idea is simple: the moment of purchase becomes the moment of capture. No pile of receipts on your desk. No reconstructing a trip from memory two weeks later.

Behind the scenes, the Expense Agent:

• Extracts the merchant, amount, date, currency, and payment method
• Categorizes the expense against your configured expense categories
• Checks it against company expense policies automatically
• Pulls relevant context (meeting, attendees, business purpose) where available
• Creates a draft expense record fully populated

It doesn’t just read a receipt. It categorizes the expense, maps it to the right GL category, checks it against your expense policies, matches it to a calendar appointment or meeting description, and groups it into a Business Central expense report. All before you’ve opened BC.

That’s not incremental. That’s a different class of automation.

When you get back to the office, you’re not starting from scratch. You open the Expense Agent web app (or Teams, or M365 Copilot Chat) and review what’s already been built. Most items are ready to submit. If something needs attention, an amount that exceeds policy, a missing participant, a charge that isn’t reimbursable, the agent flags it and gives you clear options to resolve it.

You review exceptions. You submit. That’s it.

That shift, from doing the work to reviewing the work, is the real value.

What Expense Agent Changes for Finance and AP Teams

The employee experience gets most of the attention in demos, but the finance-side impact is just as significant maybe more so.

Receipt chasing goes away. The single biggest time drain in business central expense management is following up with employees who haven’t submitted. When the barrier to submission is “take a photo, forward to an email address,” that backlog shrinks dramatically. Month-end close gets easier when expense data is flowing in real time instead of arriving in a last-minute flood.

Data quality improves automatically. When AI is categorizing expenses at the point of capture, consistently, against defined policies, you get cleaner GL coding, fewer miscategorized entries, and better policy compliance across the board. Finance teams shift to managing by exception reviewing only what the agent flags, not every line of every report.

Read about Why Waiting for Perfect Data Means Never Starting with AI

Compliance is built in, not bolted on. The agent validates every expense against your configured rules before it ever reaches an approver. Policy violations, missing justifications, non-reimbursable charges, all flagged proactively, not discovered during review.

The new model is much closer to:

• Employees capture receipts immediately at the moment of purchase
• AI extracts, categorizes, and prepares expenses
• Policy exceptions surface automatically
• Users review flagged items only
• Approvals become more streamlined
• Finance teams manage by exception instead of by administration

That’s a massive operational difference for lean finance teams.

Built for Employees Who Don’t Use Business Central Every Day

This is an important design distinction. Most Business Central agents are built for ERP users: people who live in BC daily. The Expense Agent was designed for everyone else: field workers, drivers, technicians, travelers, occasional office staff. People who need to submit business central employee expenses but shouldn’t have to understand financial systems to do it.

As a result, no Business Central license is required to submit expenses. Employees access the agent through a dedicated web app, through Outlook, or through Microsoft Teams. Usage is metered through Copilot Credits instead (50 credits per receipt) covering the full process from extraction through approval.

For organizations where not every expense submitter has a full BC license, that changes the economics considerably.

This Is What AI-Native Looks Like in ERP

Microsoft is using expense management as a proving ground for what agentic AI looks like inside a business system, where the agent operates across Outlook, Teams, and the ERP backend without requiring users to context-switch into BC at all. For growing companies especially, that kind of low-friction automation has historically been out of reach. It isn’t anymore.

The most valuable AI use cases may not be the flashiest ones. They may simply be the workflows that quietly remove operational friction employees deal with every single week.

Expense reporting in Business Central is one of those workflows.

And while the Expense Agent is still in public preview, it represents a broader shift happening across ERP systems: business applications are becoming more conversational, contextual, and agent-driven not to replace finance teams or employees, but to reduce the repetitive administrative work surrounding everyday operations.

For organizations already using Business Central, this may be one of the most practical examples yet of what AI expense management can actually look like in the real world.

Ready to enable it in your environment? Set up Expense Agent →

Want to see how the Expense Agent fits your current BC setup?

D365 Business Central Expense Agent Frequently Asked Questions

Does Business Central have native expense management? Yes, as of 2026 Release Wave 1, Business Central includes a native Expense Agent. Prior to this release, BC did not have built-in expense management; organizations typically relied on third-party apps or manual processes. The Expense Agent was built AI-first from the ground up, not adapted from existing functionality.

What’s the difference between the BC Expense Agent and receipt capture? Receipt capture (OCR) reads a receipt and pulls in basic fields like merchant and amount. The Expense Agent goes further: it categorizes the expense, applies company policies, matches context from calendar meetings, and builds a complete Business Central expense report automatically. The employee’s role shifts from data entry to exception review.

Does the Expense Agent require a Business Central license? No. Employees can submit expenses through a dedicated web app or by forwarding receipts via email without a BC license. The agent uses Copilot Credits for AI processing (50 credits per receipt). A BC license is only needed for users who want to work directly inside Business Central.

What does the Business Central Expense Agent cost? The agent consumes Copilot Credits rather than a per-seat license. Processing one receipt, including extraction, categorization, policy validation, and expense report creation, costs 50 Copilot Credits regardless of complexity. Copilot Credits billing must be configured in your BC environment before enabling the agent.

Is the Expense Agent available now? The Expense Agent is in public preview as part of Business Central 2026 Wave 1, currently available in English for US-based environments. Additional languages and regions (UK, Australia, New Zealand) are planned for July 2026.