TL;DR
An employee expense policy usually has a lot to say about travel and almost nothing about hardware. So people buy their own. A monitor here, a keyboard there, occasionally a whole laptop. Each claim is small and defensible. Collectively they become an unmanaged procurement channel with no asset record, no warranty position and no way to get anything back.
- Silence on hardware turns expenses into an unmanaged buying channel.
- Expensed devices have no asset record, so they never appear in any audit.
- Decide whether a device bought this way is company property or the employee’s.
- Name the excluded categories rather than relying on a spend limit.
- A claim under the approval threshold is invisible by design.
- Give people a real route to request kit, or they will keep using expenses.
How an employee expense policy starts buying hardware
Nobody designs this. It happens because the alternative is worse.
Somebody needs a second monitor. The request process is slow, or unclear, or they are not sure one exists. They buy a monitor for 180 pounds, claim it, and their manager approves it in about four seconds because it is obviously reasonable.
Best tools for HR Operations
That is a sensible decision by everyone involved. Repeat it two hundred times and you have bought a lot of hardware you cannot see.
What makes it invisible
Approval thresholds. Most policies route anything under a few hundred pounds straight to the line manager, which is correct for lunch and wrong for durable goods.
So the spend never reaches procurement, never reaches IT, and never reaches an asset register. It appears in the accounts as an expense line and nowhere else.
Why it matters more than the money
The spend itself is rarely the problem. A few hundred pounds a head is not what makes this worth fixing.
Four other things are.
| Consequence | Why it happens | When you notice |
|---|---|---|
| No asset record | Never entered any system | At audit, or never |
| No warranty position | Bought on a personal account | When it breaks |
| Unclear ownership | Policy silent | When the person leaves |
| No security posture | Device never enrolled | After an incident |
Row three produces the most friction and row four produces the most risk.
If somebody expensed a laptop and nobody said who owns it, the conversation at exit is genuinely ambiguous. They paid for it on their card. The company reimbursed them. Reasonable people disagree about what that means, and the policy should have decided in advance.
The security half
A monitor is harmless. A laptop bought this way is a machine holding company data that was never enrolled, never encrypted to your standard and never visible to your tooling. That is a different category of problem and it deserves an explicit exclusion rather than a cap.
Our note on where a BYOD policy fits covers the related case where the device was never company-funded at all.
For what a managed device is expected to do in the first place, the NCSC device security guidance sets out the baseline, and almost none of it is achievable on a machine your tooling has never seen.
Exclude categories, not amounts
The instinct is to lower the approval threshold. That does not work, because it catches legitimate small spend and still misses a 150 pound keyboard.
Name the categories instead. An employee expense policy should say plainly that certain things are never claimed through expenses regardless of value.
- Computing devices of any kind, including tablets and phones.
- Storage, including external drives and memory cards.
- Networking hardware.
- Software and subscriptions, which have their own procurement path.
- Anything that will hold company data.
Monitors, keyboards, mice, headsets and desk accessories are the grey zone. Many companies allow those within a cap and it works fine, because none of them stores data and the ownership question is low stakes.
Tax treatment of reimbursed equipment varies by jurisdiction. the UK guidance on homeworking expenses and benefits covers the UK position on homeworking expenses and benefits, and it is worth checking the equivalent wherever you employ people before writing a cap that creates a taxable benefit by accident.
Give people a route that works
An exclusion without an alternative produces one of two outcomes. People stop asking and work with what they have, or they find a creative expense category.
Neither is what you wanted. So the exclusion has to arrive alongside a request route that is genuinely faster than buying it themselves.
Faster means days, not weeks. If a monitor request takes three weeks, the expense route wins on merit and the policy loses.
Clear means one place. People use expenses partly because they know how. If the equipment request lives in a form nobody can find, the policy is theoretical.
What good looks like
A short standard list that needs no approval at all, a named person for anything outside it, and a stated turnaround. Published somewhere people already go.
Teams supporting staff across several countries often find the bottleneck is delivery rather than approval. RemoAsset handles procurement and delivery into the markets where people actually live, which is usually the step that makes the official route slower than a personal card.
The decision table
Match the row to how the leak is actually happening.
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| No equipment request route | Under 50 staff | Everything through expenses | Nothing is tracked | Build the route first, then exclude |
| Route exists but is slow | 50 to 200 | Ticketing in place | People route around it | Publish a turnaround, measure it |
| Laptops appearing on expenses | Any | Policy silent on devices | Unenrolled machines | Exclude computing devices outright, today |
| Distributed across countries | Series A+ | No local supply | Delivery is the blocker | Fix supply, not the approval rule |
| Ownership disputes at exit | Any | Historic expensed kit | Genuinely ambiguous | State the rule forward, do not apply it backwards |
Row five matters. A new ownership rule should apply from its publication date. Applying it retroactively to equipment somebody bought two years ago under a silent policy is both unfair and unenforceable.
What to add to the document
Four lines, in the section people already read.
The excluded categories, stated as categories rather than amounts. The cap for the permitted grey-zone items. The ownership position for anything reimbursed. And the route to request what is excluded, with a name and a turnaround attached.
That last one is the line that makes the other three work. An exclusion is a rule. A route is an answer.
Then look backwards once
Run a single query over the last two years of expense data for the excluded categories. Not to claw anything back, but to find out how large the untracked fleet actually is.
Most teams are surprised, usually by the number of monitors rather than the number of laptops. That figure is also the honest starting point for the register reconciliation described in our piece on equipment depreciation.
What to do with what you find
Nothing punitive. The people who bought this equipment followed a policy that permitted it, and several of them did so because the alternative route did not work.
The useful actions are narrower. Enrol any computing device that is not already enrolled, which is the only genuinely urgent item. Add the larger items to the asset register with an estimated in-service date rather than pretending the history exists. And look at which teams generated the most claims, because that is usually a signal about which locations your supply chain does not reach rather than a signal about those teams.
That last point is the one worth acting on. A cluster of expense claims in one country almost always means equipment cannot easily be delivered there, and tightening the policy without fixing the supply simply moves the problem somewhere less visible.
Where the gap is genuinely geographic, a partner that ships into those markets closes it faster than a policy change does. RemoAsset handles recovery of equipment from remote staff as well as supply, which matters for the expensed devices you are now trying to bring back under management.
RemoAsset supplies and recovers equipment in the markets where your people live, so the official route is the fast one. More on equipment policy at HROpsLab.
Frequently asked questions
Should an employee expense policy cover IT equipment?
It should explicitly exclude most of it. Computing devices, storage, networking hardware and anything that will hold company data belong in a procurement route with an asset record attached, not an expense claim approved by a line manager in four seconds. Monitors, keyboards, mice and headsets are a reasonable grey zone to permit within a stated cap, because none of them stores data and the ownership question is low stakes.
Why not just lower the expense approval threshold?
Because it fails in both directions. A lower threshold catches a lot of legitimate small spend and creates approval work nobody wanted, while still missing a 150 pound keyboard that sits under whatever the new limit is. Naming the excluded categories works better, since the problem is not the amount of money but the fact that durable, data-holding goods are entering the company with no record and no security posture.
Who owns a laptop an employee expensed?
Genuinely ambiguous if the policy never said, which is why it causes trouble at exit. They paid on a personal card and the company reimbursed them, and reasonable people read that differently. Decide the rule and publish it, then apply it from that date forward. Applying a new ownership position retroactively to kit bought two years ago under a silent policy is both unfair and difficult to enforce.
What is the real risk from expensed hardware?
For a monitor, almost none. For a laptop, it is a machine holding company data that was never enrolled in your management tooling, never encrypted to your standard and is invisible to every security control you run. That is a different category of problem from the spend, and it is the reason computing devices deserve an outright exclusion rather than a higher cap or tighter approval.
How do we stop people using expenses for equipment?
Give them a route that is genuinely faster. An exclusion without an alternative produces either people working with inadequate kit or creative expense categories, and neither is the outcome you wanted. The route needs a short standard list that needs no approval, a named person for anything outside it, a published turnaround measured in days, and a location people can actually find.
Is reimbursed equipment a taxable benefit?
It depends on the jurisdiction, what was bought and who owns it afterwards, so it is worth checking rather than assuming in either direction. The UK publishes guidance on homeworking expenses and benefits, and the equivalent rules elsewhere are often a different shape. The practical risk is writing a generous cap that unintentionally creates a benefit in kind, which is a question for your own payroll and tax advisers before publication.
How do we find out how much hardware went through expenses?
Run one query over the last two years of expense data filtered to the categories you are about to exclude. The point is not to claw anything back, which would be unreasonable under a policy that was silent at the time. The point is to size the untracked fleet before you start reconciling the asset register, and most teams are surprised, usually by the number of monitors rather than laptops.