What the roadmap says
The roadmap entry is short. Admins set an amount limit. Expenses below it can be created in Expense Agent without a receipt or supporting document. Microsoft's stated benefits are:
- Qualifying expenses can be created without an attachment at submission time.
- Admins choose the threshold.
- Small expenses can still be recorded when no receipt exists.
The entry does not say the following:
- Which currency the limit uses.
- Whether an amount exactly equal to the limit qualifies.
- Whether limits can differ by category or user.
- Whether users get a warning when they submit without evidence.
- Whether the setting applies to every way of entering expenses or only to agent-created ones.
- What happens above the limit.
- Whether approval, reimbursement or posting rules change.
I'd treat all of those as open questions until Microsoft publishes documentation. The feature title doesn't answer them.
Why this matters: the current behavior
Today's documentation shows why a threshold is useful. Expense Agent takes receipts through its web app, mobile app and a monitored shared mailbox. Uploading a receipt triggers extraction and AI processing, and a new Expense record is created. The workflow is built around the receipt. Each receipt costs 50 Copilot Credits to process.
Business Central's own documentation treats the receipt as optional on the expense itself. It says each expense has a category, date, amount and optionally a receipt attachment. There is also an existing control that works the other way. A community walkthrough of the 2026 release wave 1 documentation lists an Attachment Enforcement setting on expense categories. That setting specifies whether a receipt is required for expenses in a category. I haven't verified whether the new threshold would override it, sit beside it, or replace part of it. Check how the two interact once the feature reaches preview.
Setup already has related controls. The assisted setup's rules and controls area covers a required receipt number, a required merchant name, the default approver and anti-corruption attestation visibility. The new limit would sit alongside these. I haven't confirmed which setup page will hold it. The roadmap names Expense Agent Setup. Current documentation uses Expense Management Setup, and it does not mention the new field.
Practical impact for administrators
If it ships as described, it removes a common bit of friction. Think of a parking meter, a toll, or a taxi slip someone has lost. Without an exception, the user has to either hunt for proof or leave the expense unrecorded. A threshold lets finance accept small, low-risk items.
The trade-off is weaker documentary evidence for those items. Here is how I'd prepare, based on general finance-operations practice rather than Microsoft guidance:
- Check your internal expense policy and local tax and audit requirements before choosing a threshold. Microsoft's entry doesn't address these.
- Decide which expense types should qualify, and tell employees.
- Keep the other controls on: required merchant name, receipt number rules, category checks and approvals. Each expense already records the amount, date, category and supporting details such as receipts or merchant information.
- Start with a conservative limit in the preview. Review the no-receipt expenses for a few cycles, then adjust.
- Watch for the interaction with VAT reclaim. VAT reclaim is a separate feature that captures VAT from receipts. I haven't seen documentation on how a missing receipt affects it, so test that case before enabling both.
Timing and caveats
Preview is expected in December 2026 and general availability in April 2027. Roadmap entries can slip or be removed. The record doesn't give a staged rollout, licensing changes, localization limits or a per-tenant date. Don't tell users the option exists yet. Expense Agent itself is documented as a preview feature, and the documentation for it is marked prerelease.
Bottom line
This is a small but useful change for Business Central finance teams using Expense Agent. It trades some receipt evidence for faster entry of low-value expenses, and you control how much. Whether it suits your organization depends on details Microsoft hasn't published yet, so test the threshold's behavior in the preview before you rely on it.