)
You control employee expenses by moving each check to the moment money is about to leave the business.
Start with a written policy people can find and a budget for each spend category. Then add company cards with built-in limits, point-of-payment receipt capture, and automated review of anything outside the rules.
Most finance teams already do some of this. The gap is usually timing. Controls that run at month-end find problems after the money has gone, when the only options left are a reimbursement dispute or a journal correction.
Employee expenses cover anything a person spends on the company’s behalf. This includes:
Travel and subsistence.
Client meals.
Software signed up for with a card.
Out-of-pocket purchases claimed back later.
This guide is for finance operations managers and controllers at UK and European companies with roughly 50 to 1,500 employees. In these businesses, card counts, cost centres, and entities have often grown faster than the processes built to track them.
The guide works through eight steps that shift control upstream. It then covers the failure modes that appear when one step is missing.
This is general guidance for UK finance teams, not tax advice. VAT treatment depends on your specific circumstances, so consult a qualified tax adviser before making decisions based on the rules covered here.
Key takeaways
Write the expense policy before configuring any tool, because the tool can only apply rules that already exist.
Set budgets per category so approvers see what a request does to the number they own.
Give employees a company card with a limit instead of asking them to pay first and claim later.
Capture the receipt when the payment happens, not at month-end.
Use automation to review routine transactions and route exceptions, while finance keeps the final call.
What is expense management, and how does AI improve the process?
Expense management is the process of authorising, paying, recording, and reviewing what employees spend on the company’s behalf.
At a small company, that process may involve a shared card and spreadsheet, supported by someone who knows everyone’s habits.
It works because one person can hold the whole picture in their head. It stops working when the picture spreads across:
Card statements.
An inbox of PDF receipts.
Slack approvals.
An accounting export that needs to be re-keyed.
That gap is what spend management solutions exist to close. They create one record per transaction that carries the request and approval, then connects the payment, receipt, and accounting code.
The machine-learning tools now built into these platforms help at the data-entry and review stages, not at the decision stage.
For example:
Optical Character Recognition, or OCR, reads a photographed receipt and extracts the supplier, date, amount, and VAT.
The employee confirms the fields instead of typing them.
Intelligent categorisation suggests the general ledger code and cost centre based on past transactions.
Anomaly and duplicate detection flag a claim that looks like one already paid or an amount well outside the usual pattern for that person and category.
Finance still makes the decisions. What changes is how much of the routine work arrives already prepared.
Control employee expenses in 8 steps
Each step below supplies the rule, budget, or data that the next one depends on, so it pays to work through them in order.
1. Create your employee expense management plan
Start by writing down:
Who can spend company money.
What they can spend it on.
How much they can spend.
What evidence they need to provide afterwards.
That document is your company expense policy, and every later step configures a tool to apply it.
Teams that skip this and go straight to software often end up encoding whatever the old spreadsheet implied, including exceptions nobody formally agreed to.
A plan that will survive contact with the sales team should cover the following points:
Scope: Which categories count as employee expenses, including travel, subsistence, client entertainment, and software an individual signs up for.
Authority: Who approves what, by amount, cost centre, or expense type, and whether a manager can approve their own team’s travel.
Evidence: What documentation a claim needs and what happens to reimbursement when it is missing.
Ownership: Who in finance monitors the process week to week and who updates the policy when a government rate changes.
Share the plan where people spend:
In the card app.
In the request form.
In the onboarding checklist.
In any relevant employee portal.
A policy visible at the moment of purchase gets more adherence than one buried in the HR handbook. It also changes finance’s position in the conversation.
You become the team that explained the rule in advance, rather than the team that rejects claims after the fact.
2. Put clear spend processes in place
A spend process turns the policy into a route.
The system should:
Send a request to a named approver.
Show the budget the request affects.
Allow the employee to pay by an agreed method.
Post the record to accounting without requiring a second data entry.
When any of these steps runs over email or chat, you lose the ability to see:
What is waiting.
Who has it.
How long it has been there.
Whether the budget owner has reviewed it.
Approval workflows carry most of the weight. This is where you control employee expenses before money moves rather than afterwards.
Route requests using combined conditions such as:
Amount.
Cost centre.
Expense type.
Department.
Employee role.
This prevents a £40 taxi from queuing behind the same director who reviews a £4,000 conference sponsorship.
Keep low-value, in-policy spend inside a card limit with no request required. The approver’s attention is the scarce resource in the process, so spend it on decisions that need judgement.
The system should add each step to the same record. When the request and approval sit beside the payment and receipt, an auditor can trace the transaction without you rebuilding the trail from four separate systems.
That is also what makes later automation trustworthy, because a suggestion is only as good as the record it was learned from.
3. Set a budget for each employee expense category
Give each expense category its own budget and a named owner. Then let the owner see actual spend against the budget as it happens.
Without that visibility, the approver in step two is approving blind.
A request can look reasonable on its own. Only the month-end report may show that the team’s travel budget was already spent by the 12th.
The categories worth separating are the ones with different owners or rules. These may include:
Accommodation and transport for business trips.
Meals and client entertainment.
Mileage.
Home-office equipment.
Training.
Software.
A single “travel and expenses” bucket hides the fact that flights ran over budget while training ran under. It also leaves nobody responsible for either.
Government rates set the ceiling for some of these categories, and they can change.
For UK teams, the approved mileage allowance for cars and vans rose from 45p to 55p per mile for the first 10,000 business miles from 6 April 2026. The government’s announcement confirms that this was the first increase in 15 years.
A mileage category still capped at 45p may reimburse employees below the current HMRC approved mileage rate. Check the tax and policy implications before updating it.
Check the current rate on HMRC’s guidance before updating the policy, and confirm with your adviser how it applies to your reimbursement arrangements.
Germany’s Federal Ministry of Finance publishes per diem rates on its own calendar. Multi-country teams therefore need:
A rate table for each country.
A way to update those rates once.
A process that avoids updating every spreadsheet individually.
4. Provide suitable payment methods
Give employees a company card with a limit before asking them to spend. Most expense-control problems begin when people pay with their own money.
When employees pay personally, they carry the cash-flow risk. Reimbursements can arrive late, and some employees may put larger purchases on a personal credit card when no company card is available.
Finance, meanwhile, sees the transaction weeks later and may wait even longer for the receipt. A clear expense claim process helps both sides.
Match the payment method to the type of spend:
Individual business expense cards give finance a named employee against every transaction.
A shared company credit card passed around the office does not.
A physical card suits people who travel and pay in person.
For an online purchase or a supplier you will pay once, issue a single-use virtual card loaded with the exact amount.
For recurring software, issue a virtual card per vendor.
Keep expense claims for costs a card cannot cover, such as mileage and occasional cash payments.
If the virtual card details leak, a single-use card cannot be charged again.
Reimburse out-of-pocket claims quickly enough that employees stop putting them off.
A card product on its own leaves invoices and subscriptions in a separate system, which allows the reconciliation gap to reopen.
Spendesk is an all-in-one spend management platform that consolidates:
Company cards.
Expense management.
Accounts payable.
Procurement.
Budgeting.
This connects the payment method to the wider control process. Its smart company cards include physical Visa cards, as well as single-use, multi-use, and subscription virtual cards.
Finance can apply an individual limit and approval rule to each card. The system can also remind employees to submit receipts, so the payment method and control travel together.
5. Implement smart receipt capture technology
Capture the receipt at the moment of payment.
The employee photographs it on their phone, OCR reads the fields, and the system attaches the image to the matching card transaction.
This closes the gap that creates much of finance’s follow-up work. A receipt requested three weeks later may already be:
Lost.
Faded.
Left in a hotel room or bin.
Difficult to match to the original payment.
The compliance stake is documentation.
For UK VAT-registered businesses, reclaiming input tax generally requires holding a valid VAT invoice or receipt, as set out in HMRC’s employee expense guidance.
Whether a specific claim qualifies depends on the supply and your VAT position, so check the current guidance or ask your adviser. Operationally, a missing receipt can mean a lost reclaim on top of a lost record.
Reminders help, but the reminder that works sits inside the spending workflow. If the card pauses when receipts are overdue, the employee resolves the issue at the next purchase and finance does not have to chase.
The system can also pre-fill:
Supplier.
Amount.
Date.
VAT shown in the receipt photo.
This lets the employee review the information rather than type it manually.
6. Centralise subscription monitoring
Track software subscriptions from the payment side by giving each vendor its own subscription virtual card.
The card becomes the one place every renewal has to pass through.
Subscriptions are the category most likely to drift. Someone signs up for a tool on a personal card, claims it back, and then leaves the company. The renewal continues because the receipt never told anyone it was recurring.
IT cannot see it, the budget owner never approved the second year, and finance discovers it only when a duplicate tool appears in the same cost centre.
A subscription virtual card per vendor gives you levers that a shared card does not:
Attribution: The card belongs to a person and a cost centre, so the renewal has an owner even after the original buyer has left.
A ceiling: A monthly limit on the card stops a price rise or seat expansion from going through unnoticed.
A clean stop: Pausing the card stops the charge, although you should still cancel with the vendor so the contract does not renew on paper.
Review the list of active subscription cards quarterly with each budget owner.
The conversation is shorter when every line already has a name, amount, and limit beside it.
7. Track expense report fraud
Treat expense fraud as a pattern problem, not a receipt-by-receipt hunt. The individual claim is usually small, while the loss accumulates over months.
Expense reimbursement schemes appeared in 13% of the 2,402 cases examined by the Association of Certified Fraud Examiners’ 2026 fraud report. This represented 306 cases across 143 countries.
The median loss per case was approximately USD 35,000 to USD 36,000.
The 2024 edition found that investigators took a median of 18 months to detect an expense reimbursement scheme.
These are global figures in US dollars, drawn from cases that reached investigators, so read them as an indication of the shape of the problem rather than as a UK benchmark.
Eighteen months is the number to design around. A scheme that survives that long is passing a monthly review without triggering anything. This suggests that the review is looking at individual claims while missing the wider sequence.
Configure your checks around patterns such as:
Duplicates: The same receipt submitted twice, perhaps once against a card and once as an out-of-pocket claim, or the same amount recurring across multiple months.
Threshold clustering: Claims that repeatedly sit just under an approval limit.
Timing: Weekend or holiday spending in a business category, or mileage on days with no travel in the calendar.
Altered documents: People can now fabricate convincing receipt images, so a plausible-looking document is a weaker signal than it was. Match it to a card transaction wherever possible.
Cards do most of the prevention before detection is needed. A company-card payment records the merchant and timestamp. It also fixes the amount the receipt has to match, so an inflated figure has nowhere to sit.
That leaves out-of-pocket claims as the area where review should be concentrated. It also frames the work as protecting honest colleagues from suspicion rather than trying to catch people out.
8. Deploy AI-driven automation and analytics
Use machine-learning-based automation to prepare each transaction for review. Then focus your team’s attention on the exceptions the system cannot resolve.
By this step:
Cards have attributed every payment.
Employees have attached receipts at source.
Budgets are live.
Approval workflows are in place.
The remaining work involves coding and matching, followed by identifying what does not fit.
In a well-configured platform, automation can support the following tasks:
Field extraction: OCR reads receipts and invoices and fills supplier, date, amount, and VAT for the employee to confirm.
Coding suggestions: Intelligent categorisation proposes the general ledger code and cost centre, with VAT treatment based on past transactions.
Deterministic rules: Fixed mappings apply rules such as, “If this is the supplier, use this account.”
Exception flags: Duplicate and anomaly detection surface a claim that matches one already paid or an amount outside the usual pattern.
Live analytics: Spend by category, team, and cost centre updates as transactions happen, so a budget owner sees an overrun forming rather than reading about it at month-end.
The word to be careful with is autonomy. None of this requires the machine to make the final decision.
Finance reviews a prepared field instead of typing it. The team confirms or overrides a suggestion rather than surrendering its judgement.
Spendesk’s bookkeeping automation follows that model. Deterministic rules set by finance work alongside machine-learning suggestions to prepare the accounting fields. Finance confirms them before export to Xero, NetSuite, DATEV, or another connected accounting system.
Because support varies by configuration, check the current integration catalogue to confirm which connector fits your stack.
For more detail on each type of automation, see:
Expense automation: How to automate expense claims and approvals
Business automation: Automate these six boring finance processes
Common challenges and how to avoid them
Most expense-control failures come from a check that runs at the wrong time or in the wrong place. Each one maps to a specific step above.
Challenge | Why it happens | How to avoid it |
|---|---|---|
Receipts missing at month-end | Finance asks for the receipt weeks after the payment | Capture receipts at the point of spend and pause the card when receipts are overdue, as described in step 5 |
Employees paying with their own money | There are too few company cards, or cards are reserved for senior staff | Issue individual cards with limits to anyone who spends regularly, as described in step 4 |
Approvals stuck in email or chat | There are no routing rules, so every request goes to the same person | Route by amount, cost centre, and type, and skip approval for in-limit card spend, as described in step 2 |
Budget owners approving blind | Budget-versus-actual reporting is available only at month-end | Use live budgets per category and make them visible inside the approval workflow, as described in step 3 |
Subscriptions renewing unnoticed | Subscriptions are paid on personal cards or a shared card with no owner | Use one virtual card per vendor with a limit and named owner, as described in step 6 |
Policy drift after a rate change | The policy lives in a PDF nobody owns | Name a policy owner and apply rates in the platform rather than in a spreadsheet, as described in steps 1 and 3 |
Exceptions passing silently into the ledger | Automation is configured to post rather than suggest | Use review-and-confirm mode, with exceptions routed to a person, as described in step 8 |
Read down the middle column and one cause keeps recurring: the information finance needs exists at the moment of payment and is gone by the time anyone asks for it.
Each fix moves the request to that moment.
That is also why the steps work better together than in isolation:
A card programme without receipt rules fixes attribution but leaves documentation untouched.
Receipt rules without cards still depend on employees fronting the cash.
Budgets without live transaction data leave approvers working from incomplete information.
Automation without reliable records produces weak suggestions.
Start with the written policy because it defines the rules every later control must apply.
Then:
Configure the approval route and budgets.
Introduce payment methods that apply those decisions at the point of spend.
Add receipt capture and subscription tracking.
Deploy automation once there is reliable data for it to learn from.
Once the checks sit at the point of payment, month-end stops being where problems are discovered and becomes where their absence is confirmed.
Reconciliation turns into a review of exceptions. The reimbursement queue also shortens because fewer people pay out of pocket.
The reports you produce then describe spending the business already understood as it happened. That is a different job from the one most finance operations managers describe today, and these eight steps provide the path between the two.
Get a free tour of Spendesk to see how card limits, receipt rules, and bookkeeping review sit inside one workflow.
Frequently asked questions about controlling employee expenses
These answers cover the record-keeping, VAT, fraud, policy, and process questions that commonly arise when finance teams tighten employee expense controls.
How long do UK employers need to keep employee expense records?
The applicable period depends on the record and tax involved.
HMRC’s PAYE record guidance says to keep PAYE and expense records for three years from the end of the tax year they relate to.
HMRC’s VAT record guidance sets a period of at least six years for VAT records, with a longer period under some schemes.
HMRC’s travel expense guidance also expects employers to retain original documentation where possible, even after transferring it to a computer.
Confirm the current requirement with your adviser before setting a deletion schedule. Also check how the documentation requirement applies to your scanning process.
Can you reclaim VAT on an employee expense without a receipt?
Sometimes, within a narrow limit.
HMRC’s Guidelines for Compliance on employee expenses state that VAT on supplies of £25 or less may be reclaimed without a receipt if you can show that the supplier is VAT-registered.
Above that, a valid VAT invoice or receipt is generally required.
The threshold and conditions can change, and eligibility depends on the supply and your VAT position. Verify the position against current HMRC guidance and with your adviser before relying on it.
What counts as expense reimbursement fraud?
The Association of Certified Fraud Examiners defines expense reimbursement fraud as:
“A fraudulent disbursement scheme in which an employee makes a claim for reimbursement of fictitious or inflated business expenses, for example, an employee files a fraudulent expense report claiming personal travel, nonexistent meals.”
Common forms include:
Claiming a personal purchase as a business expense.
Inflating the amount claimed.
Submitting the same receipt twice.
Claiming for spending that never happened.
Altering a receipt or invoice.
Claiming mileage for a journey that did not take place.
A card programme with receipt matching removes many opportunities for duplicate submissions and mischaracterised personal spend. The card transaction fixes the merchant and amount before an employee makes a claim.
What is the difference between expense management and spend management?
Expense management covers what employees spend and claim back, mainly out-of-pocket claims and card transactions.
Spend management is wider. It includes:
Supplier invoices.
Purchase orders.
Subscriptions.
Company cards.
Budgets.
Employee expenses.
For tool selection:
A team whose main pain is reimbursement may start with expense management.
A team reconciling cards, claims, and invoices across three systems is describing a spend management problem.
How often should you review an employee expense policy?
Review it at least once a year and whenever a government rate you rely on changes.
UK mileage is the current example. The approved rate for cars and vans moved on 6 April 2026 after remaining unchanged for 15 years.
The government has committed to reviewing rates again at Budget 2026, so a policy that hard-codes the number needs an owner who watches for the next change.
Beyond rates, review the policy when the company:
Adds an entity or country.
Changes approval thresholds.
Introduces a new payment method.
Expands into new expense categories.
Changes its reimbursement process.
Curious how Spendesk works?
Try an interactive demo to see spend control and approvals end-to-end.
Get a free tour)
Chris Dunne
Chris Dunne is our Senior Content Marketing Manager. Based in Derry, he brings over 15 years of marketing experience to our content strategy. Outside of work, Chris loves spending time with his two young children, playing football, and exploring Ireland.
)
)
)
)
)