Business Central Expense Agent to Create Trip-Based Expense Reports in November 2026

What the roadmap says​

According to the roadmap entry (ID 573257), administrators will choose on the Expense Agent Setup page whether the company groups expenses by trip as well as by period. If they do, the agent should:

• Create expense reports on its own, without a person starting and organizing one after a travel requisition is approved.
• Link eligible expenses to the right trip using information in the travel requisition.
• Group expenses by context, not only by location.
• Leave non-trip expenses on the existing period-based grouping.

The entry is a short description. It does not say how the contextual matching works, what happens when the agent is unsure, or whether an employee can move an expense between reports. Those details are open until the feature ships and the documentation is updated.

What Business Central does today​

Microsoft Learn documents Expense Agent as an AI agent that handles receipt intake, data extraction, categorization, itemization and expense line creation. The documented workflow includes a "Monthly expense report creation" step. The overview page also says the agent creates monthly expense reports per employee, grouping all expenses for the period into a single report.

Trip-based reports would therefore change how reports are organized. They would not add receipt reading or expense creation, which the agent already does.

Some manual grouping exists already. Microsoft's documentation on submitting reports in Expense Agent says related expenses can be grouped for batch review and approval, for example as a report for a specific business trip or a monthly set of expenses. The roadmap item is about the agent doing that grouping for trips without anyone setting it up by hand.

The travel request gap​

Travel requests are the other half of this story. Microsoft documents them as a way to review planned travel before employees spend money. A request records the purpose, travelers, dates, estimated costs and policy acknowledgment. After approval, it can be linked to an expense report so posted spending can be compared with the expected amount.

The current documentation sets some limits that the roadmap feature would have to work around:

• In version 29, travel requests are managed in Business Central. They aren't available in the Expense Agent web or mobile experience.
• Version 29 doesn't automatically create an expense report from a travel request.
• Linking is done on the expense report by choosing an approved request in Travel Request No. The report's expense user must be a traveler on the request, and only refundable lines can be linked.
• With Expense Agent disabled, submitting a request approves it automatically. With the agent enabled, the request stays Submitted until the configured approver decides.

The roadmap feature would remove a manual step between an approved request and a trip-specific report. Today, version 29 doesn't create that report automatically.

Why finance teams may care​

Anyone who has reconciled a month of mixed spending knows the problem. A hotel, two flights, a client dinner and a parking charge from last week all land in one monthly report, and someone has to work out which trip each one belongs to. Trip-level reports make it easier to:

• Compare a trip's actual cost with the amount requested.
• Review one travel episode as a unit.
• Spot cost overruns by trip.

Business Central already warns, without blocking, when spending linked to a request exceeds the expected amount. Cleaner trip reports could make that comparison more useful. This is my analysis, not a Microsoft claim.

Cautions​

• Human review stays. The documentation says users must review all expenses before submitting a report, because extraction and categorization are done by the agent. Nothing in the roadmap entry suggests that changes.
• Contextual grouping can be wrong. Matching by context is more flexible than matching by location, and it can also misassign an expense. A conference-city dinner or a stopover could be filed under the wrong trip. Finance teams should plan a spot-check period during preview.
• Don't confuse products. Microsoft's Dynamics 365 Project Operations documentation describes a separate Expense Agent with a Group Reports by setting that offers Trip or Project. That is a different product context and says nothing about when this Business Central feature will arrive or how it will behave.
• Costs and prerequisites still apply. Current documentation says existing rules, permissions and workflows continue to apply. It also says the agent consumes Copilot Credits, at 50 per receipt, and that billing must be set up first. Setup needs the right permissions, an available Microsoft 365 mailbox, and the agent capability enabled. Whether the trip option changes any of this isn't stated.

What admins can do now​

1. Check whether Expense Agent is enabled and activated in your environment.
2. Make sure approved travel requests contain accurate travelers, dates and purposes, since the roadmap says matching will draw on the requisition.
3. Look at how your people currently link requests to expense reports, so you can compare results after the feature arrives.
4. Watch the roadmap and Business Central release notes for changes to the November estimate.
5. Test in a sandbox first, when preview becomes available.

Bottom line​

Microsoft plans to let Business Central's Expense Agent create reports per trip, using travel requisition data and context. It would leave non-trip expenses on period-based grouping. The feature is in development, with a November 2026 estimate for preview and general availability. Current version 29 documentation describes monthly grouping and manual request-to-report linking. The roadmap entry is thin on details such as accuracy handling and configuration options.