Equipment Stipend or Company Laptop: The Decision That Sets Your Offboarding Problem

TL;DR

• An equipment stipend is money given to an employee to buy their own work equipment. It is not a cheaper way of providing hardware. It is a different transaction with a different owner at the end.
• If you can get a configured machine to everybody you hire within a week, you do not need a stipend. You have already solved the problem a stipend exists to avoid.
• The trade is explicit: a stipend removes all your logistics and all your control, and leaves you with nothing to recover.
• Three structures exist, a one-off allowance, a recurring contribution, and reimbursement against receipts, and they behave very differently for tax, for ownership and for what happens at the end.
• How a stipend is treated for tax depends entirely on jurisdiction and on how it is structured. That is a question for your own advisers, in each country, and this page does not answer it.
• Most companies arrive at a stipend because it was easier at the point of hire, not because they chose it. Choosing it deliberately produces a much better version.

The Policy That Was Never Decided

A company hiring across six countries ran into the same problem each time: getting a laptop to a new starter abroad took three weeks, and nobody had the appetite to solve it properly. So for the third international hire, somebody suggested giving the person 1,500 pounds and letting them buy a machine locally. It worked. The starter had a laptop in two days.

Within eighteen months that had become the arrangement for everybody outside the home market, without ever being written down or approved. Then the company started selling to enterprise customers and a security questionnaire asked how it managed company devices. The honest answer was that roughly 40 per cent of its staff were working on personal machines the company had paid for, did not control, could not wipe, and would never get back.

Nobody had decided this. Each individual case had been a sensible response to a real delay. A stipend is a legitimate choice and it was never made here; it accumulated. That distinction matters, because a company that chooses a stipend designs around its consequences, and a company that drifts into one discovers them in front of a customer.

Recommended Tools

Best tools for Device Management

B BambooHR HR management system L Lattice Performance management D Deel Global payroll & EOR

View all recommended tools

This is the decision an equipment stipend is really about.

When You Don't Actually Need to Think About This

When the manual way is genuinely fine

You can get a configured laptop to any new hire within about a week, everywhere you employ people. If that is true, the problem a stipend solves does not exist for you, and taking one on would trade a working arrangement for a loss of control you gain nothing from.

When friction starts appearing

The signal is the workaround becoming routine. One emergency stipend is fine. The third one, for the third hire in a market you now hire in regularly, is not an emergency, it is an undeclared policy. That is the point to decide rather than continue improvising.

When it becomes a liability

The moment somebody outside the company asks about device control. A customer security questionnaire, an auditor, or a prospective acquirer. Each will ask what hardware staff use and how it is managed, and the answer for a stipend population is uncomfortable to give honestly and dangerous to give dishonestly.

The edge case that forces it

A market you genuinely cannot ship into on any reasonable timescale, or a short contractor engagement where issuing and retrieving a machine costs more than the engagement is worth. Both are real, and both are arguments for a deliberate, bounded stipend rather than a general one.

Five Questions People Ask

"Is a stipend cheaper?" Usually slightly, and that is not the reason to do it. You are buying speed and giving up an asset.

"Who owns the laptop?" The employee, unless you have written otherwise at the point of payment, and most companies have not.

"Can we get it back when they leave?" No. That is the defining feature of the arrangement rather than a flaw in it.

"How much should it be?" Enough to buy a machine that meets your specification in that country, which is a different number in different markets.

"Is it taxable?" That depends on jurisdiction and structure, and it is a question for your advisers rather than for a comparison article.

What You Are Actually Trading

Setting out the exchange plainly is the most useful thing anybody can do before choosing, because both sides of it are real.

What a stipend gives you. Speed, in every market, immediately. No customs, no importer of record, no courier, no delivery delay and no logistics relationship to manage. For a company hiring into unpredictable markets this is worth a great deal and it is available on day one.

What a stipend costs you. Four things, and they arrive later than the benefit. You lose the asset, because the machine belongs to the person and there is nothing to recover or reissue. You lose specification control, so your fleet becomes whatever people chose. You lose the configuration baseline, because nobody enrolled the device in anything before it arrived. And you lose the ability to wipe it, which is the one that appears on security questionnaires.

So the honest framing is not cost. It is that a stipend converts a recoverable asset into compensation, and buys delivery speed with the proceeds. For some populations that is clearly correct. For others it is clearly wrong. The mistake is applying one answer to everybody.

The Three Structures, and Why the Difference Matters

These are frequently treated as interchangeable and they are not, particularly where tax is concerned.

A one-off allowance at hire

What it is. A fixed sum paid near the start date, intended to cover a machine and a basic setup.

When it's right. Markets you cannot reach, and contractor populations. Simple to administer and easy to explain.

When it fails. It is a single payment with no replacement position, so a machine failing in year three has no answer. And unless you state otherwise in writing at the time, the equipment is unambiguously the person's.

A recurring contribution

What it is. A monthly or annual amount towards equipment and home working costs.

When it's right. Where the intention is to contribute to ongoing costs rather than to fund a specific purchase, and where you want a replacement mechanism built in.

When it fails. It looks more like regular compensation than a one-off does, which has consequences in some jurisdictions, and it rarely results in people actually buying a better machine. Money arriving monthly is money that gets spent monthly.

Reimbursement against receipts

What it is. The person buys, submits a receipt, and is repaid up to a limit.

When it's right. When you want evidence of what was bought and some control over specification, and where the treatment of reimbursed business expenses is more favourable than a straight allowance.

When it fails. It requires the person to fund the purchase first, which is a genuine barrier for somebody who has not started being paid yet, and it is the most administratively heavy of the three. It is also the structure where ownership is most commonly assumed by both parties to mean opposite things.

And on all three: how any of them is treated for tax, for the company and for the individual, depends on the jurisdiction and on how the arrangement is structured. Take advice for each country you employ in before standardising. The differences are substantial and they are not intuitive.

Setting the Amount Without Guessing

The common approach is to pick a round number that sounds generous in the home market and apply it everywhere. It produces an amount that is lavish in some countries and insufficient in others, and the second of those quietly produces people working on inadequate machines.

A better method takes an afternoon.

Start from your specification, not from a budget. You should already have a floor per role. Price a machine meeting that floor, locally, in each country where you will use the stipend. Local retail pricing varies by considerably more than exchange rates alone, because of import duty and local tax.

Add the cost of the things a laptop does not include. A display or stand, a keyboard, and a headset. If your stipend is intended to cover the full setup, it must actually cover it.

Then decide whether to publish one figure or several. A single global figure is simpler and is wrong in both directions. Several figures are more accurate and invite comparison between colleagues. Most companies that do this properly publish a small number of bands by region, which is a reasonable compromise.

What to do:

• Price your actual specification in each market rather than converting a home-market figure.
• Include the display, keyboard and headset if the stipend is meant to cover a setup.
• Review the figures annually, because hardware prices and duties move.
• State explicitly what the money is for, which changes how it is understood and may affect its treatment.
• Say in writing, at the point of payment, who owns what is bought.

The Clause Most Companies Forget

One sentence decides whether a stipend arrangement is recoverable or not, and it has to be written at the moment the money is paid rather than at the moment somebody leaves.

If you intend the equipment to remain company property despite the employee buying it, say so in writing, at the point of payment, and record what was bought with the serial number. That turns a stipend into a reimbursed company purchase, which is a different arrangement with different consequences and may be treated differently for tax.

If you do not say it, the default position in practice is that the person bought the item with money you gave them, and it is theirs. That is a perfectly reasonable arrangement and most stipends are exactly this. The failure is intending the first and documenting the second, which produces a dispute at the exit that the company will usually lose.

So decide which one you mean, write it at the time, and be consistent. The worst outcome is a policy that is silent, because silence resolves in favour of whoever is holding the laptop.

Segmenting Who Gets What

The single most useful move in this whole area is to stop looking for one answer. A company with 200 people has at least three populations with genuinely different requirements, and applying one arrangement to all of them is what creates the problem.

Segment on two axes only. Any more and the policy becomes unusable.

Axis one: what data do they touch? Somebody with access to customer records, financial systems or source code needs a device the company can control and wipe. Somebody writing marketing copy in a browser mostly does not. This is the axis that decides whether a stipend is acceptable at all, and it is a security judgement rather than a cost one.

Axis two: how long will they be here? A permanent employee justifies the cost of issuing and recovering hardware across several years. A three-month contractor does not, because the administrative cost of equipping and retrieving them can exceed the value of the arrangement.

Three of the four boxes have an obvious answer. The interesting one is the bottom right, and that is where the delivery question decides it: if a configured machine can reach that person within a week, provide it, because you keep the asset and the control for very little extra effort. If it cannot, a stipend is the honest answer for that market until delivery improves.

What to do:

• Write the two axes down and place every current role in a box.
• Apply the matrix to the people you already have, not only to new hires.
• Name the exceptions explicitly rather than leaving them to managers.
• Re-run it when you enter a new market, because the delivery answer changes.
• Record which arrangement each person is on, so you can answer a questionnaire accurately.

That last point matters more than it looks. A company that can state what proportion of its staff are on company-controlled hardware is in a completely different position, during a security review, from one that has to guess.

Migrating a Stipend Population Back

This page has referred to retrospective remediation twice without describing it, and it is worth being concrete, because a surprising number of companies face exactly this after a sales process raises the question.

You cannot simply take people's laptops away. The machines belong to them; you paid for them and that transaction is complete. What you are actually running is a transition, and it takes two or three quarters done well.

Start with the people, not the hardware. Identify who is in the sensitive-data box of the matrix above. That is the population that must move, and it is usually much smaller than the total stipend population. Attempting to move everybody at once converts a focused piece of work into a company-wide disruption.

Issue company hardware alongside, not instead. Give the person a company machine and let them keep the one they bought. Trying to recover or buy back a personal device introduces a negotiation into something that should be an improvement. The old machine is theirs; that was the deal.

Move the accounts, then the data, then revoke. The work is not the laptop, it is everything on it. Access moves to the new device, company data is migrated, and only then is access from the personal machine removed. Compressing this is what makes migrations feel punitive.

Say why, plainly. People react badly to being handed a laptop with no explanation, because the implication is that they were not trusted. The honest reason, that the company now sells to customers who ask how devices are managed, is easy to understand and carries no accusation.

And fix the intake at the same time. A migration that does not also change how new starters are equipped will be repeating itself within a year. The new arrangement has to be live before or alongside the remediation.

So budget for it properly, and expect the provisioning stage to be the long one, because it involves delivery into exactly the markets that caused the stipend in the first place. That is the clearest argument for solving delivery before the question is forced.

How to Choose: Five Questions Before You Decide

Can you actually deliver to the markets in question? Get a real answer rather than an assumption. If a provider can put a configured machine into somebody's hands in that country within a week, the main argument for a stipend has gone, and the control you keep is worth more than the speed you gave up.

What does your security questionnaire say today? Pull the last one a customer sent and read your own answers about device management. If those answers describe company-controlled hardware and a growing share of your staff are on personal machines, the gap is already live and will surface in a sales process.

Which populations does this apply to? Employees handling sensitive data and contractors on a two-month engagement should not be governed by the same answer. Segment first, and expect the result to be company-provided for most employees and stipends for specific, named cases.

What happens in year three? A one-off allowance with no replacement position means somebody's machine fails and there is no mechanism. Decide the replacement answer at the same time as the initial amount, because retrofitting it is harder.

Who reviews the figures? Hardware prices, duties and exchange rates all move. A stipend set once and never revisited becomes inadequate within a couple of years, and the people it fails are the least likely to say so.

When Somebody on a Stipend Leaves

The case the whole arrangement eventually produces, and the one most policies do not address: a person is leaving, the laptop is theirs, and there is company data on it.

There is no device to recover, so everything you can do is at the account layer, and it has to be done properly because it is all you have.

Revoke access first, and completely. Not just the main identity provider. Anything with a token or a saved session: code repositories, cloud consoles, customer systems, password managers, anything with a desktop application that stays signed in. On a company-owned machine a leftover session is a gap you can close by wiping the device. Here it is not.

Assume local copies exist, because they do. Downloads, exports, attachments, a folder of documents saved for convenience. This is not misconduct, it is how people work. The question is not whether company data is on the machine but what you are going to do about it.

Ask, in writing, with specifics. A request to delete company material, naming the kinds of thing you mean and giving a date, gets better results than a general reminder. Most people comply readily. The written request is also the only record you will have that you asked.

And record the limitation honestly. Your asset register should show that this person was on a personal device and that no wipe was possible. An auditor would far rather see a documented limitation than discover an undocumented one, and the record is what lets you answer a later question accurately.

Checklist:

• Revoke every token and session, not only the primary login.
• Send a written deletion request naming the categories of data and a date.
• Record on the asset register that no wipe was possible and why.
• Review what that person had access to, so you know what the exposure actually is.
• Treat the case as evidence when deciding whether this population should be on stipends at all.

So the honest summary is that offboarding a stipend user is a best-efforts exercise rather than a controlled one. That is acceptable for somebody who wrote marketing copy in a browser, and it is not acceptable for somebody who had access to customer records, which is the distinction the segmentation matrix exists to make before you are standing in this situation rather than after.

Six Options Worth Knowing

A stipend needs no vendor, which is part of its appeal. The relevant comparison is therefore between a stipend and the providers that make company-provided hardware practical in the markets where you were tempted to use one. Each was checked against its own pricing page on 6 and 7 October 2026 and none publishes a figure. Two name a model without numbers: GroWrk describes a per-order option alongside a subscription tier, and allwhere refers to pay-as-you-go and fixed rates.

RemoAsset

Disclosure: RemoAsset is owned by the same people who publish HROpsLab. It appears here because it is one of the options that removes the reason to use a stipend, and its limitations are stated in the same detail as every other option.

Best for: companies that would rather keep ownership and control than trade them for delivery speed, in markets where delivery was the obstacle.

Why companies choose it: purchase, delivery, the asset record and retrieval run from one place, so a device reaches somebody abroad without you giving up the asset, and the return is triggered automatically when they leave. For a company drifting towards stipends because logistics were hard, it addresses the actual cause.

Where it struggles: it publishes no price and requires a demo, which is a slower evaluation than deciding to pay somebody 1,500 pounds. Coverage should be confirmed market by market rather than assumed, because the markets where stipends are most tempting are usually the hardest ones to serve. It is not an MDM, so configuration enforcement is separate, and it is not a certified disposition vendor.

Workwize

Best for: multi-region fleets where regional stock makes delivery fast enough to remove the stipend argument.

Why companies choose it: warehousing near people, strong European coverage, domestic shipping rather than imports.

Where it struggles: no published price, and more than a two-country company needs.

Deel IT

Best for: companies already employing internationally through Deel.

Why companies choose it: the countries usually line up with where you already employ people, and the hire signal exists already.

Where it struggles: quote-based, and most compelling alongside an existing Deel relationship.

Firstbase

Best for: companies whose stipend was meant to cover a whole setup rather than a laptop.

Why companies choose it: furniture and peripherals ship alongside the machine, which is the part a stipend is genuinely better at and the part most providers will not touch.

Where it struggles: no published price, and only worth it if you really fund furniture.

GroWrk

Best for: exactly the markets that drive companies to stipends, in Latin America and parts of Asia.

Why companies choose it: in-country presence where others subcontract, which is the difference between a three-week wait and a three-day one.

Where it struggles: publishes nothing, naming its models without figures.

allwhere

Best for: United States-led companies with international staff.

Why companies choose it: deployment depth, so machines arrive configured.

Where it struggles: consultation-only pricing.

What Each One Published

Checked against each vendor's own page on 6 and 7 October 2026.

The Decision Table

The pattern that works for most companies is a split: company-provided for employees, stipends for contractors and for named markets where delivery genuinely fails. A single answer for everybody is what produces the problem in the opening of this piece.

What Getting This Wrong Costs

The cost nobody counts is the asset. Every stipend is a laptop the company will never see again, and at a few hundred machines that is a material number that appears nowhere, because the money was classified as an allowance rather than as hardware. Companies comparing stipend cost against purchase cost are comparing one year against three, and the stipend looks better than it is.

The second cost is the one that arrives in a sales process. A security questionnaire asking how you manage company devices has one honest answer for a stipend population, and it is that you do not. That answer can lose a deal, and the remediation, moving people onto company hardware retrospectively, is slower and more disruptive than provisioning correctly would have been.

The third is the exit conversation. Where a stipend was paid and nobody wrote down who owns the result, the company and the employee frequently hold opposite assumptions, discovered in the final week. The company usually concedes, because the documentation does not support it, and the concession is noticed by everybody who hears about it.

So ask the diagnostic question plainly. Are you solving a delivery problem, a cost problem, or a control problem? A delivery problem has vendors that address it directly, and a stipend is the workaround rather than the solution. A cost problem is not actually improved by a stipend once the lost asset is counted. And if what you need is control, a stipend is the opposite of what you are looking for.

When You're Ready to Decide Rather Than Drift

The signals are specific. Stipends have been used more than twice in the same market. Somebody has asked how you manage devices and you hesitated. You cannot say what proportion of your staff are on company-owned machines. Or a departing employee has kept a laptop and nobody could say whether that was correct.

When those are true, the work is not choosing a vendor. It is writing down which populations get which arrangement, saying who owns equipment in each case, and setting the amounts against a real specification priced in each market.

If the reason you reached for a stipend was that delivery into certain countries was hopeless, that is a solvable problem rather than a permanent condition. RemoAsset addresses it by handling purchase, delivery and the eventual recovery as one loop, which is why it fits companies that want to keep the asset, and why it is the wrong answer if your real constraint is contractor engagements too short to justify issuing hardware at all. It is worth a look alongside the alternatives here.

And on the tax treatment of whatever you choose, take advice per country before you standardise. The structures described here are treated very differently in different places, and that difference is sometimes large enough to change which one you should use.

One last thing worth saying plainly, because it is the part companies find uncomfortable. A stipend is not a worse choice than company hardware. It is a trade that is correct for some people and wrong for others, and the companies that get into difficulty are not the ones that chose it. They are the ones that never chose anything, applied the same answer to a contractor and to somebody with access to customer records, and found out which was which in front of a customer.

Frequently Asked Questions

HROpsLab takes no vendor money and publishes no paid placements, and does not tell you how a stipend is taxed where you are.