Business Central Expense Agent VAT Number Receipt Checks: April 2027 Preview

The feature is in development. Nothing described here is available today.

What Microsoft says is coming​

The roadmap describes a configurable receipt-validation rule. Organizations set when a valid company VAT number (also called a Tax ID) must appear on a submitted receipt. Expense Agent then checks receipts against that rule. Depending on company policy, a receipt that fails can be:

• flagged for review, or
• stopped from moving forward in the process.

The roadmap lists these details:

Microsoft states that the roadmap gives estimated dates and that all information is subject to change. Items are removed once a feature ships, is cancelled or is postponed. Treat April and May 2027 as planning targets, not commitments.

Why a company VAT number matters on a receipt​

In many VAT regimes, a business that wants to reclaim input VAT needs a receipt or invoice that identifies the company as the buyer. A till slip with no buyer details often won't do. I'm drawing that from general industry knowledge, not from Microsoft's roadmap text. Rules vary widely by country and by expense type, which is why a configurable "required when" setting is more useful than a blanket requirement.

The roadmap does not say the feature enforces any particular country's tax law. It describes organization-defined rules and policies. Your accountant, not the agent, remains the authority on what your jurisdiction requires.

Where it fits in the current Expense Agent​

Microsoft's current documentation describes Expense Agent as an AI agent that automates expense processing in Business Central. Employees submit receipts through the web app, mobile app or email. The agent extracts details, creates expense records and groups them into reports. All financial data, audit trails and posting logic are processed within Business Central, so existing rules, permissions and workflows continue to apply.

There is already VAT-related behavior. If an organization has enabled VAT reclaim, Expense Agent identifies VAT information on an uploaded receipt. For each rate, it captures the VAT percentage, VAT base, VAT amount, total amount and expense category or subcategory. An accountant must review every VAT reclaim suggestion and approve or reject it before the expense report can be posted.

Setup also has existing controls. One option requires a receipt number for every expense. Another, Allow VAT Reclaim, specifies whether VAT reclaim is allowed on expenses.

The planned feature looks like a sibling of these settings. Today's VAT reclaim captures what the receipt says about VAT. The planned rule would check whether the receipt names your company. That is my reading of the roadmap wording. Microsoft hasn't published where the new setting will live.

One caution on older documentation. Microsoft's 2026 release-plan page for Expense Agent is marked archived as of October 2026. Its preview geography list (US, then Australia, New Zealand and the UK) shouldn't be applied to this feature. The new roadmap item lists the worldwide standard multi-tenant cloud.

What the roadmap does not say​

The entry leaves several questions open. Administrators should not assume answers to any of them:

• Where the check runs. It could run at receipt extraction, report submission or approval. Microsoft doesn't say.
• Where it is configured. The setup page, the policy settings and a new rules area are all possible.
• What "valid" means. The roadmap doesn't say whether the check is format-based, a match against your own company's registered number, or something else.
• Country-specific formats. None are described.
• Whether it queries a tax authority. Nothing says it does.
• How flagged receipts are resolved. There is no description of the reviewer experience.
• Licensing, prerequisites and credit use. Microsoft's overview says the Expense Agent consumes Copilot Credits for AI processing. The roadmap says nothing about whether this check changes that.
• Quantified benefits. No time savings or error reductions are claimed.

Practical takeaways for administrators​

1. Decide your policy now. List which expense types need your company VAT number on the receipt. Examples might be supplier invoices over a threshold or specific categories. Also decide whether a missing number should block the expense or only flag it.
2. Confirm your VAT reclaim setup. The check will sit alongside existing VAT reclaim and posting setup. Clean VAT business posting groups and category defaults will help.
3. Plan for the review queue. Flagging receipts creates work. Someone must own resolution, such as asking the employee for a corrected invoice.
4. Don't treat it as compliance. A passing check means the receipt met your configured rule. It does not mean the VAT treatment is right.
5. Watch the roadmap and Learn. Verify setup steps and behavior once preview documentation appears, before changing live processes.

Bottom line​

This is a small, concrete addition. It adds a policy gate to a workflow that is already extracting and validating receipt data. The main value is consistency: the same rule is applied to every receipt rather than depending on a reviewer's attention. Microsoft has not yet published how it works or measured what it achieves, so finance teams should plan around the preview window and wait for documentation.