What Microsoft has put on the roadmap
The entry is titled "Expense Agent - Add tags for expenses as submitter" and carries roadmap ID 573606. According to the roadmap record, submitters will be able to add one or more custom tags when they create or edit an expense in the web application. The stated purpose is to capture business, project, event or other dimensional context that the standard expense fields don't hold. The aim is to make expenses easier to organize and categorize.
Key details from the roadmap metadata:
- Status: In development
- Product and platform: Dynamics 365 Business Central, Web
- Cloud instance: Worldwide (Standard Multi-Tenant)
- Preview target: February 2027
- General availability target: April 2027
Microsoft says roadmap descriptions and dates are estimates. The roadmap page also says they are subject to change. It adds that entries can be removed once a feature ships, or if it is cancelled or postponed. Treat February and April 2027 as planning targets, not commitments.
Where tags would fit in the current workflow
Microsoft's Learn documentation, which is labeled prerelease, describes how the agent works today. The agent extracts the merchant, date, amount, currency, payment method and, where relevant, line items. It then creates draft expense lines. Users must review everything before submitting. The agent fills in fields such as category, amount, currency, merchant, payment method, date, receipt number and a context-based description.
Submitters can already see and edit those values in the web app. That is the natural place for a tag field, but the roadmap entry doesn't describe the screen layout.
The agent also groups expenses into reports. Microsoft's report documentation says it creates monthly reports per employee. Users can rename a report, add receipts to a draft, or move an expense to another report. The roadmap item is about tagging individual expenses. It says nothing about tagging reports.
Tags are not dimensions, as far as we know
Business Central already has structured ways to add context. Microsoft's expense documentation covers project numbers, project task numbers and dimensions. The expense card can use global dimensions, and the Dimensions action lets you add more. Expenses inherit default dimensions from the expense user's linked employee, or from the selected project. Controllers and approvers can adjust dimensions and project fields during review.
The roadmap describes tags as a way to capture context beyond standard fields. It does not say they replace dimensions, and it does not say they affect posting. This distinction matters. Posting an expense report creates ledger entries, and filling in project fields creates project ledger entries. Nothing on the roadmap suggests tags will do either. Until Microsoft documents otherwise, assume tags are labels and not accounting controls.
What the roadmap does not say
The roadmap entry leaves several practical questions open:
- Whether tags are free-form text or come from an administrator-defined list
- Whether tags can be reused across users, and whether there is a limit on how many an expense can carry
- Whether tags can be searched, filtered or reported on, or whether approvers and finance staff can see them
- Whether tags carry over into Business Central itself, or appear in the mobile app
- Whether tags feed any approval rules, policy evaluation or integrations
I would not plan reporting or governance around tags until documentation answers these.
What admins and finance teams can do now
- Check the agent is enabled and set up. The Expense Agent is a Business Central online capability. Admins turn it on from the agent icon and the Configure Expense Agent assisted setup.
- Review how you capture context today. If submitters put project or event information in descriptions, consider whether project fields or dimensions already cover it. Microsoft says project fields are only visible when an administrator enables them in the setup.
- Plan a pilot around the February 2027 preview window. Test whether tags help with the labels you care about, such as events or internal initiatives, before relying on them.
- Watch the release plan and Learn pages. They are where setup steps, limits and reporting behavior should appear when the feature ships.
Licensing matters too. Microsoft says submitters using the web app or mailbox don't need a Business Central license unless they process expenses inside Business Central. The agent also consumes Copilot Credits, at 50 per receipt processed, according to the current overview page.
Analysis
This is an incremental change, but a sensible one. Fixed expense fields rarely capture every label finance teams want, such as a conference, a client pitch or an internal initiative. Dimensions are powerful but are usually governed by finance. Letting submitters add lightweight tags could reduce the pressure to cram context into the description field.
The risk is inconsistency. Free-form tags tend to multiply, with "Q1-Offsite", "q1 offsite" and "Offsite Q1" all in use. If Microsoft allows free-form entry without governance, tag-based filtering could be unreliable. That is speculation about a feature whose rules aren't published, but it is worth testing when the preview arrives.
Bottom line
Microsoft plans to let Business Central Expense Agent submitters add one or more custom tags to expenses in the web app, with preview targeted for February 2027 and general availability for April 2027. The feature is still in development. Its effect on reporting, approvals and accounting is undocumented, so don't treat tags as a replacement for dimensions or project fields.