Treat those dates as estimates. Microsoft's roadmap page says all information is subject to change. It also says entries are removed once a feature ships, is cancelled or is postponed.
What Microsoft says is coming
The roadmap description covers three controls.
- Per-approver limits. Organizations can set a maximum approval amount for each approver, or give an approver unlimited authority.
- Escalation above the limit. A request that exceeds an approver's limit can go to a designated next approver.
- Alternate approvers. Organizations can name backups for ad hoc needs or planned absences. Requests can route to the alternate while the primary approver is unavailable. Microsoft says they follow the same approval processes and controls.
The listing is for the web platform and the Worldwide (Standard Multi-Tenant) cloud instance. It names both the Preview and General Availability rings. It says nothing about on-premises Business Central.
Why it matters: today's Expense Agent approval model is simple
Microsoft Learn describes the current setup as a simple one-to-many arrangement. An approver is switched on through the Can Approve toggle on the Expense User Card. That approver is then given a list of the expense users they cover. The same documentation says approvers must have a Business Central license. It also says an approver's email must match the Authentication Email on their User Card.
The Learn page for expense users and teams says interim approvals aren't supported. Roadmap item 573260 is a separate planned feature that adds an interim approver who reviews a report before the final approver. Item 573260 shouldn't be confused with this one. Windows Forum has covered that item separately.
The Expense Agent also has its own approval process. The "Enable Approval Workflow" setting applies only when the agent is not enabled. So this roadmap item is about the agent's own approval layer, not the classic workflow engine.
How this compares with approval limits elsewhere in Business Central
Limits and substitutes aren't new to Business Central. The general Approval User Setup page already lets administrators set amount limits for different types of requests, define substitute approvers, and set up notifications. Business Central's standard approval workflows can also use an approver chain. That chain is described as traversing the chain until it finds a qualified approver.
The roadmap item appears to bring a similar idea to the Expense Agent's approval process. Microsoft doesn't say it will reuse the same pages or logic, so that part is my inference. Don't assume the two behave identically.
Third-party expense tools use the same pattern. Continia's documentation says that in its product, an expense over an approver's limit escalates automatically to the next senior approver. It also advises keeping at least one approver with unlimited authority so nothing gets stuck. That is Continia's guidance, not Microsoft's. It shows a design hazard Business Central administrators may want to check for, because a chain with no final unlimited approver could leave large claims unresolved.
What the roadmap doesn't tell you
The listing leaves several things open. Wait for Microsoft's documentation before building a policy around any of them.
- Whether a limit applies per expense line, per report, or per currency.
- Whether escalation can pass through several approvers in sequence.
- Whether an alternate inherits the primary approver's limit.
- Whether alternates act only inside defined dates or can be switched on ad hoc without a schedule.
- How delegated approvals are recorded in the audit trail.
- Whether the feature needs a particular Business Central version or license change.
- Where it will be configured. The roadmap names no setup pages.
What administrators can do now
These steps use only what current documentation confirms.
- Review who is set up as an approver on the Expense User Card, and which expense users each approver covers. You can also see all approval relationships on the Expense Approval Setup page.
- Check that each approver holds a Business Central license. Also check that their email matches the Authentication Email on their User Card.
- Decide on paper who your next approver should be for large claims, and who should be the backup for each approver. This is planning work, not documented setup.
- Watch for the December 2026 preview. Test with non-production data before the February 2027 general availability target.
Bottom line
This is a modest but practical governance feature for finance teams that use the Expense Agent. It tackles the stalled-approval problem, which is the most common complaint about expense workflows. Microsoft hasn't yet published how it works, only what it intends to deliver. Until the preview documentation arrives, treat the details as unconfirmed.