Business Central Expense Agent Plans Global Rollout With Seven New Languages in October 2026

The roadmap lists the item as In development. It estimates both preview and general availability for October 2026, tags the feature for the Web platform, and scopes it to the Worldwide (Standard Multi-Tenant) cloud. Microsoft's roadmap describes its dates as estimates that can change. Until the feature shows up in a tenant, treat this as a plan.

How the Expense Agent got here​

This is the third stage of a rollout that started small. When Expense Agent arrived with Business Central 2026 release wave 1, Microsoft's release plan said the public preview is available in English and in the US only, with Australia, New Zealand, and the UK to follow in July 2026.

The second stage was Microsoft's release-plan entry "Use Expense Agent in German, Danish, French, and Spanish." It went to users automatically in public preview on July 1, 2026. That entry describes a localized experience for users in countries/regions such as Australia, Austria, Canada, Denmark, France, Germany, New Zealand, Spain, and the United Kingdom. It also says the user interface, user interactions, and key expense management workflows such as receipt submission, expense review, report generation, and approval actions are available in the supported languages.

The October roadmap item is the third stage. It moves from a short list of named markets to "all countries/regions" and adds the Nordic, Benelux, Czech, and Italian languages.

Summary: In about five months, Expense Agent has gone from one country and one language to a planned global footprint.

What the Expense Agent does​

The agent automates expense handling inside Business Central. Microsoft's release plan says that once an employee submits a receipt, the agent takes over and autonomously performs receipt extraction, categorization, and itemization of expenses, creating Expense Reports based on them. Microsoft's setup documentation says employees can submit expenses through email or the Expense Agent web app, and the agent creates expense reports and applies configured rules automatically.

Microsoft's overview documentation lists these capabilities:

• Receipt scanning: the AI reads the merchant, amount, date, and category, and the employee reviews the result.
• Mileage expenses: distance and reimbursement are calculated from start and end points and the company's mileage rate.
• Policy checks: soft warnings let a user submit with a note, while hard blocks stop submission until the problem is fixed.
• Approvals: approvers can approve a report or send it back with comments.

An expense goes from Processing to Drafts, and the report moves from Draft to Submitted to Approved. Microsoft labels the feature a production-ready preview, which comes with supplemental terms of use. That label applies to the feature as a whole and is separate from the October dates for this language update.

Why these seven languages matter​

Organizations in the Nordics, Benelux, Czechia, and Italy use Business Central heavily, and they have mostly been left out of Expense Agent so far.

Business Central's other Copilot features already support most of these languages. In Microsoft's Copilot availability table, Analysis assist covers Czech (cs-CZ) Danish (da-DK) Dutch (nl-BE, nl-NL), along with Finnish, Italian, Norwegian Bokmål, and Swedish. The same table lists Czech, Dutch, Finnish, Italian, Norwegian Bokmål, and Swedish for the Payables Agent and, except Czech, for the Sales Order Agent.

So for six of the seven languages, Expense Agent is catching up with features that already have them. Icelandic is the exception. It doesn't appear for any Business Central Copilot feature in Microsoft's current availability table, so it would be new territory for Business Central agents.

There is also a gap between "Norwegian" in the roadmap and the Norwegian Bokmål (nb-NO) entry Microsoft uses elsewhere. The roadmap doesn't specify which, so don't assume Nynorsk is covered until the documentation says so.

Documentation conflicts to check before rollout​

Microsoft's own pages don't currently agree on which languages Expense Agent supports.

• The availability table lists Expense Agent in Australia Austria Canada Denmark France Germany New Zealand Spain United Kingdom United States, with Danish, several English variants, French, German, and Spanish. None of the seven roadmap languages is listed yet.
• The setup page says Expense Agent is validated and supported in English (EN-US) only. It adds that while it can be used in other languages, it might not function as intended.

The pages may simply be out of sync, or they may define "supported" differently. Either way, administrators shouldn't assume a language is validated until the availability table lists it.

Microsoft explains why the label matters. Unsupported languages may work, but Microsoft hasn't fully tested them, there is no official support for language-specific problems, and the risks include mixed-language output and lower accuracy. Its advice for production environments is to use Copilot features only in officially supported languages for business-critical work.

What "all countries/regions" means and doesn't​

The availability table says access to Business Central Copilot features depends on four separate factors:

1. Supported language: the language a user works in, which users and admins can change.
2. Environment country/region: the localization, which is set when the environment is created and can't be changed afterward.
3. Data residency region: set automatically from the country/region.
4. Azure OpenAI geography: where AI processing happens, which Microsoft controls.

Expanding to all countries/regions affects factor 2, and the new languages affect factor 1. The two are independent. A company in Finland could, for example, have a Finnish-localized environment while employees file expenses in English or Swedish.

Some limits follow from the roadmap's own wording:

• Web only: the item is tagged for the web platform. Expense Agent can also be reached through a mobile app, email, and Copilot chat or Teams, but the roadmap doesn't say the new languages extend to all of those.
• No compliance or accounting changes: a localized experience doesn't mean new tax, per-diem, or regulatory logic for a country.
• Licensing and billing: the roadmap says nothing about changes here. Microsoft's current overview says the web app, email, and Copilot chat channels use Copilot credits rather than a Business Central license.
• Multi-tenant cloud only: the item is tagged for the Worldwide (Standard Multi-Tenant) cloud.

How Expense Agent language settings work​

Language settings for the agent's outgoing messages already exist. To find them in Business Central, search (Alt+Q) for Agents, and then select EXPENSE AGENT, then open Agent User Settings.

• Region specifies the regional format used by the agent for dates, times, and numbers in outgoing emails and task details.
• Language sets the language of the agent's generated text in employee emails and task descriptions. If an employee card has a language specified, the agent uses that language instead of the default.

These settings control what the agent writes. They aren't necessarily the language selector for every part of the Expense Agent interface.

A checklist for administrators​

1. Check the availability table first. When Czech, Finnish, Icelandic, or the other new languages appear in the Expense Agent row, the expansion has reached documented support. Microsoft's setup prerequisites already require a country or region version supported by the Expense Agent as listed in Feature availability by country/region and language.
2. Test in a sandbox. Try receipts in the new languages and check how well merchant, date, and amount are extracted before relying on it for reimbursements.
3. Set employee-card languages so outgoing agent emails reach each employee in their own language.
4. Plan for Icelandic separately. Since no other Business Central Copilot feature lists it yet, expect a less proven experience at first.
5. Keep a human reviewing AI output. Microsoft recommends extra review steps whenever a language is new or not fully supported.

Is this real progress?​

Yes. Expense reporting depends on uptake: if employees in Oslo or Prague have to file expenses through an English-only interface, many will keep using spreadsheets. Covering all Business Central countries and adding these seven languages would remove one of the main remaining obstacles for European customers.

There are still open questions. This is a roadmap estimate, the feature is still in preview, and Microsoft's documentation hasn't settled on how many languages Expense Agent supports. Partner blogs have also given inconsistent lists of supported languages, which is another reason to rely on Microsoft's availability table.

Bottom line: If you run Business Central in a market the Expense Agent hasn't reached, October 2026 is the month Microsoft is targeting for preview and general availability. Before you announce it to staff, check the availability table, test in a sandbox, and confirm the setting for each employee's language.