How does expense management in Business Central work?

Business Central brings the posting side as standard: employees can be run as vendors, out-of-pocket costs entered through the general journal and reimbursed by payment run. What the standard does not bring is everything before that: receipt photo, automatic extraction, policy checking, credit card matching and an approval path. There are two routes for that, the Microsoft Expense Agent and specialised expense apps. The choice hangs on three numbers: how many receipts come in per month, whether company credit cards are involved, and how complex your travel expense policy is.

Three routes, and you pick one

In almost every conversation on this topic the expectation comes up that Business Central has „that expenses thing“ built in somewhere and you merely have to find it. That expectation is misleading. There are three clearly distinguishable routes, and in practice you decide on one of them.

The standard. Employees are run as vendors or through the employee accounts, out-of-pocket costs enter the system by journal, reimbursement runs through the normal payment suggestion. Cost: none. Effort: someone captures it by hand, usually accounting, working from submitted slips or a spreadsheet.

The Expense Agent. Microsoft’s AI agent takes receipts by photo, web app or mailbox, reads out merchant, amount, date and category, bundles them into expense reports and hands them to Business Central for approval. Cost: 50 Copilot Credits per receipt. Effort: preparing the categories and the policy, after which capture runs without manual work.

A specialised expense app. The Business Central ecosystem offers solutions that cover full travel expense accounting under German law, match company credit cards and steer multi-stage approvals. Cost: usually an amount per submitting person per month. Effort: a real, if small, rollout.

For the agent in detail, including availability in Germany and Austria: What does the Expense Agent do in Business Central?

What the standard can do, and where it stops

The standard is better than its reputation, as long as you take it for what it is: clean posting and reimbursement mechanics. The expense sits on the right account, input tax is claimed, the cost centre is correct, reimbursement rides along with the regular payment run. For a company with twenty receipts a month and three travellers that is a defensible solution, and any software beyond it would cost more than the problem.

The standard stops at a clear point, namely everywhere a check would have to happen. It does not know your travel expense policy. It does not know that a dinner up to a certain amount is fine and above it needs a justification. It does not spot that the same hotel receipt was submitted twice. And it cannot hold a credit card statement against the receipts submitted.

It is exactly these checking steps that cost time today, and not in accounting but with the managers who approve. Anyone who justifies the rollout with „we save accounting some typing“ is counting the smaller half.

When a specialised app is the straighter route

There are three situations in which we regularly advise the app in projects, regardless of how good the agent has become.

Company credit cards. As soon as cards are in circulation the process reverses: it is not the employee who submits an expense, the statement arrives and a receipt has to be found for every transaction. That direction is the real pain, and it needs automatic matching between card transaction and receipt, including a reminder for what is missing.

German travel expense accounting in full depth. Meal per diems, reductions for meals provided, the three-month rule, country per diems abroad: that is a rulebook, not receipt recognition. Anyone who wants to map it properly takes a solution that brings these rules maintained and follows changes in the law.

Multi-stage approvals. When approval depends on the amount, the project and the absence of the line manager, that is a workflow topic. Chains like that belong in a system that knows deputies and escalations.

Conversely: anyone without cards, who gets by on the statutory per diems and runs a single-stage approval, gets a long way with the agent and saves an additional licence line.

What you have to settle first, whichever route you take

This is the part almost everyone skips, and it decides the outcome more than the choice of product. Four points, and they can be settled in a single morning.

• The category list. Which expense types exist, and what are they called? Twenty grown categories, three of which mean the same thing, make any automation unusable, because the assignment cannot be unambiguous.
• The mapping to posting groups and accounts. Every category needs exactly one target account and one input tax treatment. As long as that is not written down, the bookkeeper decides it case by case, and that is not a rule but a habit.
• The policy in numbers. A check can only happen if there are limits. „Reasonable“ is not a limit. Anyone unwilling to set figures gets no automatic check either, only faster capture.
• The dimension. Which cost centre, which project or which customer does an expense run to, and who determines that, the submitter or accounting? This question decides later whether your project reporting is right.

These four points are not a pre-project, they are a decision. Take them and each of the three routes works. Leave them open and you automate an unsettled rule, then wonder about correcting entries later.

The bigger picture behind this question: Why does automation fail on data quality?