What does the Expense Agent do in Business Central, and is it available in Germany yet?

The Expense Agent is the third Microsoft agent in Business Central after the Sales Order Agent and the Payables Agent. Employees submit receipts by photo, web app or email, the agent extracts merchant, amount, date and category, bundles the expenses into expense reports, checks them against your policy and hands them over for approval and posting in Business Central. As of September 2026 it is available in Germany and Austria, in German, as a production-ready preview. Each receipt consumes 50 Copilot Credits. It delivers where expense categories, posting groups and policy have been clarified beforehand.

What the agent takes over

1. Capture: receipts arrive as a photo from the mobile app, as an upload in the web app or forwarded to a mailbox. Whoever submits needs no Business Central licence, only an account in the company's Microsoft Entra directory.
2. Extract and classify: the agent recognises merchant, amount, currency, date, payment method and receipt number, assigns the expense to an expense category and splits combined receipts into individual items. It calculates per diems from travel documents and mileage from origin and destination.
3. Check: duplicates and anomalies are flagged, policy violations reported. Without a violation, the report can go to approval automatically.
4. Hand over: approval and posting run in Business Central, with the permissions, posting groups and dimensions that apply there. The agent does not post around your rules.

New since summer 2026 are mobile receipt capture and the assignment of expenses to projects in the web app. Microsoft has announced travel requisitions before the trip for September 2026.

Availability: Germany and Austria yes, Switzerland not yet

Microsoft lists the Expense Agent as a production-ready preview, that is with supplemental terms of use but released for productive use. As of 9 September 2026 the country list covers Australia, Austria, Canada, Denmark, France, Germany, New Zealand, Spain, the United Kingdom and the United States. Supported languages are German, Danish, English, French and Spanish. Switzerland is not on the list yet.

Anyone using the feature in a language or region not listed may do so, but Microsoft then makes no commitment on quality. For companies with Swiss entities this means: Germany and Austria first, Switzerland to follow once it is released. Availability changes with every release, Microsoft keeps the current list in its country and language availability overview.

What it costs

The Expense Agent is included in the Business Central online licence, what is billed is consumption: 50 Copilot Credits per processed receipt, regardless of how many items result from it. Your company buys credits as a pack of 25,000 credits for 200 US dollars per month or pays as you go at around one US cent per credit (Microsoft price list, as of 9 September 2026).

A worked example: 200 receipts a month are 10,000 credits. In the pack that works out at 80 US dollars, pay as you go at roughly 100 US dollars. So the price is not the hurdle. The hurdle is the preparation described in the next section. How the credit model works overall and what the biggest cost block of AI in ERP is can be found in What does Copilot cost in Business Central?

What it needs from your data foundation

The agent works with the master data you give it, and it works only as well as that data. Four things must be in place before the start:

• Expense categories and subcategories with meaningful descriptions, because that is exactly what the agent uses to classify every receipt. Vague categories produce vague assignments.
• Posting groups and dimensions per category, so that the approved report becomes a clean posting and the cost centre does not have to be corrected afterwards.
• A written policy with limits: maximum amounts, allowances, receipt requirements, approval levels. What is not formulated as a rule, the agent cannot check.
• Clean employee and approver data, because the web app signs in via the company directory and approvals are tied to people.

This is the same logic as with every agent: it accelerates what it finds. If it meets categories that have grown over time and unwritten exceptions, it produces rework faster. Why this applies to all agents is explained in Do AI agents in Business Central need a clean data foundation?

When getting started pays off

The Expense Agent is a good first agent when three things apply: there is a noticeable receipt volume (from around 100 receipts a month the manual work becomes visible), the policy already exists in writing, and accounting wants to keep the approval, not hand it over. Then the process is small enough for a clean pilot and large enough for the result to be measured.

The sequence that has proven itself: clarify policy and categories, check posting groups, let the agent run alongside in one department and measure correction rate and cycle time for three months. Only then roll out. Who is responsible for approval and what happens when the agent misclassifies should be settled beforehand: Who is responsible when AI makes mistakes in your ERP?