---
title: "What does the Expense Agent do in Business Central?"
canonical_url: "https://cognilium.ai/blogs/expense-agent-business-central"
slug: "expense-agent-business-central"
section: "blogs"
date_published: "2026-09-16"
date_modified: "2026-09-16"
word_count: 1117
reading_time_minutes: 5
author: "Mudassir Marwat"
author_identifier: "0009-0008-1927-2598"
person_same_as:
  - "https://www.linkedin.com/in/mudassir-marwat/"
  - "https://orcid.org/0009-0008-1927-2598"
  - "https://github.com/mudassirmarwat"
  - "https://medium.com/@mudassir-marwat"
  - "https://www.youtube.com/@mudassir-marwat"
  - "https://dev.to/mudassirmarwat"
  - "https://hashnode.com/@mudassirmarwat"
  - "https://huggingface.co/mudassirmarwat"
  - "https://bsky.app/profile/mudassir-marwat.bsky.social"
  - "https://substack.com/@mudassirmarwat"
  - "https://topmate.io/mudassirmarwat"
  - "https://fueler.io/mudassirmarwat"
  - "https://www.instagram.com/mudassirmarwat/"
  - "https://www.facebook.com/mudassir.marwat"
  - "https://www.reddit.com/user/mudassirmarwat/"
  - "https://www.f6s.com/member/mudassir-marwat"
  - "https://cognilium.ai/founder"
entities: []
related:
  - "https://cognilium.ai/blogs/business-central-agent-limitations"
  - "https://cognilium.ai/blogs/agent-designer-business-central-limitations"
  - "https://cognilium.ai/blogs/business-central-agent-drives-the-ui"
---
# What does the Expense Agent do in Business Central?

The Expense Agent handles expense capture end to end within documented boundaries. What it covers, and the point at which a human stays in the loop.

## Key takeaways

- The Expense Agent covers the whole lifecycle, not just extraction — scanning, mileage, tracking, reports, policy and approval.
- Extraction is proposed and reviewed, never applied silently. Microsoft's own wording is that you review the details and change them if needed.
- Submitters do not need a Business Central licence through the web app, email or Copilot chat. That changes who can be in the process.
- Policy compliance is graded — a soft warning lets a submission through with a note; a hard block stops it.
- It handles approval, and the Payables Agent does not. Two agents on one platform with opposite answers, because one flow is internal and the other starts outside your organisation.
- It is a production-ready preview, which is its own status and not the same as general availability.

**It scans a receipt, pulls out merchant, amount, date and category, and carries the expense all the way to approval.** Two details change how you would deploy it: **submitters do not need a Business Central licence**, and — unlike the Payables Agent — **it has approval workflows.**

## What does it actually do?

**Microsoft lists six capabilities, and they cover the whole lifecycle rather than the extraction step alone:**

**Two of those are worth reading twice.**

**The extraction is explicitly reviewed, not applied.** *"You review the details and make changes if needed"* — the same propose-then-confirm shape every Business Central agent uses.

**And policy compliance is graded, not binary.** A soft warning lets the submission through with a note attached; a hard block does not. **That distinction is a configuration decision with real consequences** — a policy set to soft is advisory, and advisory controls are the ones people learn to click past.

## Who actually needs a Business Central licence?

**Not the person submitting the expense, and this is the deployment detail that matters most.**

> *"You don't need a Business Central license to use Expense Agent through the web app, email, or Copilot chat. These channels use Copilot credits instead."*

**Read what that changes.** Expense submission is the classic case of many occasional users and few frequent ones — a company might have twenty finance users and two hundred people who occasionally buy a train ticket. **Historically that meant either licensing everybody or building a side process.** Here the two hundred submit without a licence.

**The submission routes are ordinary ones.** A web app at `app.expenses.dynamics.com`, a mobile app, or simply email: *"Send receipt photos or PDFs as attachments to your organization's expense mailbox. Expense Agent processes the attachments and creates expenses automatically."*

**The mobile app is the one built for the actual moment of expense** — *"capture receipts with your camera, scan multi-page documents, and upload receipts even when offline."*

⚠️ **One documentation inconsistency, reported rather than resolved.** The page says *"You can work with Expense Agent in four ways"* and then lists **three** — web app, mobile app, email. A fourth channel, Teams and Copilot chat, is named in an earlier paragraph and in the licence note. **The capability is clear; the count is not.**

## Does it handle approval — and why does that matter?

**Yes, and that is the sharpest contrast in this cluster.**

**The Expense Agent lists approval workflows as a capability**: *"Approvers can review, approve, or send back expense reports with comments."*

**The Payables Agent names approval flows as unsupported.** Microsoft's own *Feature limitations* heading on that agent lists **Approval flows** and **Anomaly detection** — [the published limits are worth reading in full](/blogs/payables-agent-limits-business-central).

> **Two agents from the same vendor, on the same platform, and one routes approvals while the other refuses to.** That is not an oversight. **Expense is a self-service flow where the submitter and the approver are both people inside your organisation.** Accounts payable is a flow where the document arrives from outside, and Microsoft keeps its agent on the extraction side of that boundary.

**The practical consequence:** if you are designing both, **you cannot assume one pattern.** Expense approval lives in the agent. Payables approval has to live in a Business Central workflow, and that is a separate build.

## How does an expense move through the system?

**Two status tracks, and they are not the same thing.**

**The expense itself:** *"The status is **Processing** while AI scans your receipt"*, then *"The expense moves to the **Drafts** tab once details are extracted and ready for your review."*

**The report:** *"The different phases of an expense report itself moves from **Draft** → **Submitted** → **Approved** as it works through the approval process."*

**So a receipt becomes an expense, expenses are grouped into a report, and the report is what gets approved.** Anyone designing a policy or a reminder needs both tracks, because *"in Drafts"* and *"unsubmitted report"* are different states with different owners.

## What status is this feature, exactly?

**Production-ready preview — and the distinction is not pedantry.**

> *"This is a **production-ready preview** feature."* *"[This article is prerelease documentation and is subject to change.]"*

**A production-ready preview is not a public preview and is not general availability.** Microsoft applies supplemental terms of use to it, and the documentation itself is marked as subject to change. **Anyone writing a statement of work against this feature should use Microsoft's own label rather than a rounder one**, because "preview" and "production-ready preview" carry different commitments.

**The page carries `ms.date` 23 April 2026 and was updated 27 August 2026** — recent, and worth re-checking before you quote it, because production-ready previews are precisely the features that move.

**About Cognilium** Cognilium builds AI optimization apps for Microsoft Dynamics 365 — companion apps that optimize the pricing, inventory, warehouse and planning decisions your ERP manages but can't optimize. Dynamics is your system of record. Cognilium is your system of intelligence. https://cognilium.ai · https://www.linkedin.com/company/37180269/

**Agentic ERP.** We build turnkey AI optimization apps for Dynamics 365 — sidecar applications that run in your own Azure tenancy and solve the calculations a standard ERP is not built to compute. Built on **Azure OpenAI, Microsoft Fabric and Copilot Studio**. We build these on request, against your data and your environment.

**More on the boundary between what Copilot does and what you build:** [Agentic ERP on Dynamics 365](/erp-ai).

If you are designing expense and payables together, the two agents do not follow the same pattern. Bring both flows to a 15-minute call and we will map where each one stops.

## Sources

- [Expense Agent Overview for Business Central](https://learn.microsoft.com/en-us/dynamics365/business-central/expense-management/expense-agent-overview) · `ms.date` 2026-04-23, updated 2026-08-27
- [Payables Agent Overview — Business Central](https://learn.microsoft.com/en-us/dynamics365/business-central/payables-agent) · `ms.date` 2026-05-03

## Fact-check

**Tier summary:** 10 × T1 (all verbatim), 3 × T2 — **0 × T4.**

**🔴 No pricing**, per the founder ruling of 2026-09-15. Copilot credits are named once, in Microsoft's own licence sentence, as **the mechanism that replaces a licence** — not as a cost. **No rate, no currency, no total appears.**

> ### ⚠️ Status: `[PRP]`, and this repo has got that wrong before  Microsoft's words are *"a **production-ready preview** feature"*. **That is not `[PP]` public preview and not `[GA]`.** An earlier article in this repo applied `[PP]` where Microsoft said production-ready preview, and it took three corrections. **The label here is taken from the page and reproduced exactly.**

**Claim 11 is the one to watch.** Microsoft does not explain *why* Expense routes approvals and Payables does not. **The internal-versus-external explanation is ours**, it is marked as ours in the body with *"That is not an oversight"* framing, and **it is not attributed to Microsoft anywhere.**

**No figures of ours.** No count of customers, no accuracy figure, no volume. The only numbers are a date and Microsoft's own status wording.

## Frequently asked questions

### What does it actually do?

Microsoft lists six capabilities, and they cover the whole lifecycle rather than the extraction step alone:

### Who actually needs a Business Central licence?

Not the person submitting the expense, and this is the deployment detail that matters most.

### Does it handle approval — and why does that matter?

The Expense Agent lists approval workflows as a capability: "Approvers can review, approve, or send back expense reports with comments."

### How does an expense move through the system?

The expense itself: "The status is Processing while AI scans your receipt", then "The expense moves to the Drafts tab once details are extracted and ready for your review."

### What status is this feature, exactly?

Production-ready preview — and the distinction is not pedantry.

---

Canonical HTML: https://cognilium.ai/blogs/expense-agent-business-central