By [Author Name] · [Date] · [X] min read · [Table of Contents]
TL;DR
- A home office stipend is money you give people to set up where they work, instead of sending them the equipment yourself.
- If everyone is in one country and you already ship laptops reliably, you don't need a stipend for the computer and probably only want one for the desk and chair.
- It does three things: removes your logistics work, lets people choose, and converts a hardware decision into a payroll and ownership question.
- Three designs dominate: a one-off joining amount, a recurring allowance, and a reimbursement against receipts.
- Choose on who should own the laptop at the end, because that single answer rules out most of the designs immediately.
- Done right, nobody argues about a chair and nobody loses a company laptop to an ambiguous policy.
Somebody leaves and you ask for the laptop back. They reply, politely and with complete confidence, that they bought it with their stipend so it's theirs. You look at the policy. The policy says the stipend is for home office setup, says nothing about ownership, and was written eighteen months ago by somebody who has since moved on. Legal has a view, HR has a different view, and the person has already started a new job.
That conversation happens more than anybody writes about, and it's always the same shape. A stipend gets introduced to solve a real problem, usually that shipping laptops to seven countries was painful and slow. It works. Nobody revisits it until there's an awkward exit, and by then there are forty devices in the field with unclear ownership and no serial numbers recorded anywhere.
Best tools for HR Operations
The real issue isn't the amount. Teams agonise over whether the figure should be 500 or 1,000, and that's the least consequential decision in the whole policy. It isn't close. The real issue is that a stipend quietly moves three things off your plate and onto somebody else's: the purchasing, the ownership and the record. Two of those you wanted to move. The third you almost certainly didn't. This is what a home office stipend policy is supposed to settle.
When You Don't Actually Need a Home Office Stipend
When shipping already works. One or two countries, a supplier who delivers reliably, and a standard machine specification that suits most people without anybody having to negotiate over it. Providing the kit is cheaper per head, keeps the asset in your name and gives you a serial number. Introducing a stipend here trades a working process for a policy you now have to maintain.
When the friction starts showing. The first sign is a pattern of exceptions. Three people in a market your supplier handles badly, a new hire who needs a machine in four days, somebody in a country where your courier wants an entity you don't have. Each of those gets solved individually with a reimbursement, and after the fourth one somebody suggests making it a policy. That instinct is right. The design is what matters.
When it becomes a liability. Two triggers. The first is an exit where ownership is contested, because a single ambiguous case tends to reveal that the policy never addressed it. The second is finance asking which of your assets are actually yours, at which point a fleet of employee-purchased machines sitting in your register is a problem in both directions.
The edge case that breaks everything. A security requirement arriving after the fact. A customer or an auditor asks how you ensure company data sits only on managed devices, and the honest answer is that a proportion of your fleet was bought by individuals, is owned by individuals and was never enrolled in anything. I've seen that discovered during a deal, and retrofitting it across people in nine countries is a quarter of work nobody budgeted.
What People Teams Actually Need from a Stipend Policy
> "Who owns the laptop at the end?" > One sentence in the policy, decided before the first payment goes out. > This single answer determines the tax question, the exit question and the security question, and a policy that omits it has omitted the only part that matters.
> "What is it actually for?" > A named list: computer, monitor, chair, desk, or some subset. > Stipends written for "home office setup" get spent on things nobody anticipated, and the resulting conversation is unpleasant for everybody.
> "How does this appear on somebody's payslip?" > An answer from your own payroll provider and local advisers, per country, before you launch. > Treatment varies by jurisdiction and by design, and getting it wrong is the one failure in this policy that affects individuals personally.
> "What comes back when somebody leaves?" > A clear expectation set at the start, not raised at the end. > Anything you want returned has to have been described as company property at the moment it was bought.
> "What do we do about the person who wants something unusual?" > A route that exists, with a decision maker, separate from accessibility requirements. > Accessibility should never queue behind a preference request, and a stipend design that treats them the same is the most damaging version of this policy.
The Three Designs, and What Each One Costs You
The one-off joining amount. What it is: a fixed sum paid near the start date, for the person to set themselves up. When it's right: when onboarding speed is the problem and the markets are varied enough that you cannot ship reliably. It's the fastest design to operate and the easiest to explain in an offer letter. When it fails: on ownership and on the record. Equipment bought with a joining payment is almost always the individual's property unless you've said otherwise clearly, which means you end up with no serial numbers, no enrolment and nothing to retrieve. For a monitor and a chair, that's fine. For the computer that holds your customer data, it's a problem you've paid to create.
The recurring allowance. What it is: a monthly or annual amount, either as a stipend or as part of a broader benefits budget. When it's right: for the long tail of home working costs that are genuinely ongoing: internet, consumables, a desk refresh every few years. It suits companies that want to support the working environment rather than to provision hardware. When it fails: as a way of funding a laptop. Spreading a device purchase across 24 monthly payments means neither party knows who owns the machine at any point, and the first exit mid-period is the conversation nobody wants. Keep recurring money away from capital items.
Reimbursement against receipts. What it is: the person buys, submits a receipt, you reimburse, usually against a named list and a cap. When it's right: when you want control over what gets bought without doing the buying. The receipt gives you a record, a specification and often a serial number if you ask for it, which makes this the only one of the three designs that produces usable asset data. When it fails: on experience and on speed. It puts the cash flow on the individual, which is a real burden for some people and an unfair one if the amount is significant. And it generates expense admin for both sides, which is small per transaction and tedious at volume.
How to Choose: Five Questions Before You Write the Policy
Who should own the computer? Answer this before anything else and write it down, because every other decision follows from it. If the company should own the laptop, a stipend is the wrong instrument for the laptop and you should provide it, keeping the stipend for furniture and peripherals. If the individual should own it, accept that you will not be retrieving it, cannot assume it is enrolled and should not have it in your asset register. Both answers are defensible. It's having no answer that causes the trouble.
How many countries are you actually paying into? This number drives the complexity more than headcount does. One or two countries and you can get clear advice quickly and apply one design. Nine countries and you are running nine variants of a payroll question, and the honest approach is a single policy with per-country implementation notes written by somebody local. Don't assume a design that works in one market behaves the same way in another.
Is the real problem speed, choice or coverage? These want different answers. If the problem is that laptops take three weeks to arrive, a stipend fixes the symptom and a better logistics arrangement fixes the cause. If the problem is that people want different machines, a stipend is a genuinely good answer. If the problem is that you cannot get hardware into a market at all, a stipend may be the only answer available, and that is the strongest case for using one.
What do you want back? List the items. Most companies want the computer back and genuinely don't want a three-year-old chair, which is a sensible position and should be stated. Once you have the list, every item on it needs to be company-owned from the point of purchase, which usually means you buy it rather than reimbursing it. The items not on the list can be funded however you like.
Who maintains this in eighteen months? Stipend policies drift faster than most. The amount becomes dated as hardware prices move, the country list grows, and the ownership clause that was fine for the first five hires starts producing arguments at the fortieth. Name an owner and a review date, and put the amount in a linked appendix rather than in the policy body so that updating it is a ten-minute job.
The Ownership Question, Which Is the Whole Policy
Everything above circles this, so here it is directly. There are exactly two coherent positions, and the trouble comes from sitting between them.
Position one: the company owns the equipment. You buy it, or you reimburse against a receipt with a written statement that the item is company property held by the employee. It goes in the asset register with a serial number. It gets enrolled in whatever management tooling you run. It comes back when the person leaves, and the retrieval is arranged by you rather than requested of them. This position is more work and it is the only one compatible with having a trustworthy fleet record.
Position two: the individual owns the equipment. You give money, they buy what they want, it is theirs. Nothing goes in your register. Nothing is enrolled, unless you have a separate arrangement for managing personal devices. Nothing comes back. This position is much less work and it means accepting that a portion of your working environment is outside your visibility, which is a legitimate choice for furniture and a serious one for computers.
Then there is the middle. A stipend that funds a laptop with no ownership statement. That produces an asset nobody can claim, a device nobody enrolled, and a record that lists machines you may not own. I'd avoid it in every case, and the fix is one sentence rather than a redesign.
A useful way to make the choice concrete. Write the exit email now, before the policy exists, for a person leaving from the most awkward country on your list. If that email asks for the laptop back, the company owns it and your design has to support that. If it does not, you have chosen position two and should stop carrying those machines in your register. Writing the email takes five minutes and settles an argument that otherwise arrives a year later with a specific person attached to it.
Payroll and Tax, Handled Honestly
This section is deliberately short, because the useful content is a warning rather than an answer.
It depends. The treatment of a home office stipend turns on the jurisdiction, on the design you choose, on whether the item is owned by the company or the individual, and sometimes on whether a receipt exists. Those variables interact, and the answers differ between countries that otherwise look similar. Any article, including this one, that tells you confidently how a stipend will be treated on a payslip in your country is guessing.
So the process is the part worth copying. Before launching, take your chosen design and your country list to your payroll provider and to a local adviser in each market, and ask three specific questions: how is this treated, what documentation is required, and does the answer change if the company retains ownership. Get it in writing. Then write the per-country notes into an appendix rather than into the policy, because the policy should be stable and the notes will change.
One point is yours. Keep the furniture money and the computer provision in separate parts of the policy, with separate mechanisms. They behave differently almost everywhere, they have different ownership answers and they have different useful lives, and bundling them into one figure makes every subsequent question harder to answer. The companies I have seen handle this well all made that separation on day one.
And a note on fairness. A reimbursement design asks individuals to spend their own money and wait, which is a materially different experience depending on somebody's financial position. If you choose reimbursement, the honest mitigations are a short payment cycle and an option to have the company buy directly for anybody who prefers it. That option costs you almost nothing and removes a quiet inequity from the policy.
Setting the Amount Without Overthinking It
The figure gets the most attention and deserves the least, but there is a method that beats intuition.
Work it out from the items. List what the stipend is meant to cover, price each item at a reasonable rather than a premium specification, and add them up. A desk, a chair, a monitor, a keyboard and a mouse priced sensibly gives you a number, and that number is defensible in a way that a round figure copied from another company's careers page is not.
Then decide whether the amount is a cap or a budget, and say which. A cap means people can spend less and the difference is not theirs. A budget implies the whole amount is available and will be spent. Both work. Confusing them produces the situation where somebody buys a chair for a third of the allowance and then asks what happened to the rest, which is a reasonable question that an unclear policy cannot answer.
Two refinements that solve most of the edge cases cheaply. First, split the amount into a joining portion and a refresh portion, with the refresh available after a stated period such as three years. That handles the person who has been with you for five years and whose chair has worn out, without opening an annual conversation. Second, state what happens if somebody already has a perfectly good setup: either they can claim the money anyway, which is simple and occasionally generous, or they cannot, which is cheaper and feels mean. Pick one and publish it. Because the unwritten version of this rule is always applied inconsistently.
| Design choice | Simplest version | What it costs you | Best for |
|---|---|---|---|
| Company provides the computer | Ship a standard machine | Logistics work, per country | Fleet control and security |
| Stipend for furniture only | One joining amount, named items | Almost nothing | Most distributed teams |
| Reimbursement with receipts | Named list, cap, short cycle | Expense admin both sides | Record-keeping with choice |
| Recurring allowance | Monthly amount in payroll | Ownership ambiguity if it funds kit | Ongoing costs, not hardware |
| Mixed: provide the laptop, fund the rest | Two mechanisms, one policy | Two things to maintain | Teams that want both |
The last row is where most well-run distributed companies end up, and it is worth saying plainly that it is not a compromise. Providing the computer and funding the furniture separates the item you need to control from the items you do not, which is the whole design problem solved in one decision.
The Record Problem a Stipend Creates
This is the consequence that surprises people most, so it is worth stating in detail.
When you provide equipment, the record builds itself as a side effect. A purchase order exists, a serial number is captured, a delivery is confirmed, an enrolment happens. None of that requires anybody to remember anything. When you pay a stipend instead, every one of those steps either moves to the individual or disappears, and the individual has no reason to send you a serial number unless you asked for one at the time.
So build it into the payment. For any stipend design that funds a computer, capture the record at the moment the money moves. Make the serial number a required field on the reimbursement claim, or ask for a photograph of the device label as part of the joining process. This feels bureaucratic and takes somebody thirty seconds, and it is the difference between a fleet you can describe and a population of machines you cannot.
The second half of the record problem is enrolment. A device bought by an individual is not in your management tooling unless somebody enrols it, and the enrolment is much harder after the fact than during setup. The practical fix is to make enrolment part of the first week rather than a later task, with a named owner and a check that it happened. Without that check you will have a number of unenrolled machines holding company data and no way to know which ones they are.
And one honest limit. No logistics vendor and no asset platform can fix this retrospectively. Not one of the equipment vendors does network discovery, which means none of them can find a device that was bought privately and never recorded. Workwize, Firstbase, GroWrk and allwhere all publish no rate card and none of them does discovery. RemoAsset publishes $1,499 a year for its Subscription tier and does not do discovery either. Disclosure: RemoAsset is our own product, and the limits belong next to the figure: no network discovery, no software licence management, and only the Subscription tier publishes a figure because the pay-as-you-go side is quoted. If you need to find machines you never recorded, this whole category is the wrong purchase and a discovery tool is the right one.
The Four Questions People Ask, and What to Say
Whatever you publish, four questions arrive within the first fortnight. Having the answers written down saves the policy from being renegotiated in a dozen private conversations.
"I already have a good setup. Can I have the money anyway?" Decide this before launch and publish the answer. Allowing it is simple, feels fair to the person and costs you real money for no change in their working conditions. Refusing it is cheaper and reads as mean to somebody who happens to have bought their own chair last year. There is no correct answer here, only an answer you apply consistently, and the worst outcome is deciding case by case, because the decisions will leak and they will not match.
"Can I buy a better monitor and pay the difference myself?" Almost always yes, and saying so explicitly removes a surprising amount of friction. The complication is ownership. So state it: if an item is part-funded, decide whether it is company property, individual property or split, and pick one rather than leaving it to be worked out later. For furniture the simplest answer is that it belongs to the individual whatever the funding split was, and that answer costs you nothing because you did not want the chair back.
"What if it breaks?" This is the question that exposes a gap in most stipend policies. Company-provided equipment has a repair or replacement route. Stipend-funded equipment that belongs to the individual generally does not, which means a chair failing in month fourteen is their problem. That may be the right answer, and it should be stated rather than discovered. A middle option that works well is to make the refresh portion of the amount available early in the case of a genuine failure, with a named decision maker and no requirement to produce an argument.
"I am moving country. What happens?" Rarer and messier than the others. The equipment usually stays with the person, the payroll treatment may change, and anything the company owns now sits in a different market from the one it was shipped to. The practical advice is to treat an international move as a trigger for a short review rather than as an automatic anything, and to make sure whoever handles the move knows that company-owned equipment is part of the checklist. Otherwise the laptop quietly relocates and the asset register does not.
A fifth question arrives later, usually from a manager rather than an employee, and it is worth pre-empting because the answer is counter-intuitive. It asks whether a stipend can be used as a recruiting lever: advertised in a job post, or raised for a particular hire who negotiates hard. The honest answer is no. The reason is not meanness. A stipend that varies by negotiation stops being a policy and becomes a benefit with an undisclosed range, which means two people doing the same job in the same country end up with different setups for reasons neither of them can see. That is a pay equity problem wearing a furniture costume, and it is much easier to avoid than to unwind afterwards. If you want flexibility for a genuinely unusual role, build it into the published list as a named higher tier rather than into the negotiation.
One general principle behind all five. Publish the answer even when the answer is no, and an unwritten no gets applied inconsistently and read as arbitrary, while a written no gets read as a rule. The cost of writing it down is a sentence.
The Decision Table: Which Approach Fits You
| Situation | Scale / Size | Setup | Primary Pain | Recommended Starting Point |
|---|---|---|---|---|
| One or two countries, shipping works | Under 150 people | Hybrid | None for the laptop | Provide the computer, stipend the furniture |
| Several countries, delivery is slow | 50 to 400 people | Fully distributed | Joiners waiting weeks | Fix logistics first, then stipend furniture |
| Markets you cannot ship into at all | Any | Distributed | No coverage available | Stipend, with ownership stated plainly |
| People want to choose their machine | 20 to 200 people | Any | Spec disputes | Reimbursement with a named list and a cap |
| Security requires managed devices | Any | Any | Unenrolled hardware | Company-provided only, no laptop stipend |
| Long-tenured staff with worn setups | Any | Distributed | No refresh path | Split the amount: joining plus refresh |
| Ongoing costs like internet | Any | Distributed | Not a hardware question | Recurring allowance, never for kit |
Most companies want two of these rows at once, which is exactly why a single blended figure causes problems. Two mechanisms in one policy is simpler to operate than one mechanism trying to do two jobs.
What to Actually Write, Section by Section
A workable stipend policy is one page. Seven short sections, and the ordering matters because people read the first two and skim the rest.
What this covers. The named items, and explicitly what is excluded. If the computer is provided rather than funded, say so here in the first three lines, because that is the question everybody opens the document to answer.
The amount. The figure, whether it is a cap or a budget, and the period it covers, and put the figure in a linked appendix so it can be updated without a review cycle.
Who owns what. One paragraph, unambiguous, covering each category of item, and this is the section that prevents the conversation described at the top of this article.
How to claim. The mechanism, the documentation required including a serial number if a device is involved, and the payment timing. Keep the timing commitment realistic, since a stated cycle that is routinely missed is worse than a longer one that is met.
Exceptions and accessibility. Two separate sentences. One route for preference requests, a different and faster route for accessibility or health requirements, with a named decision maker for each and no requirement for anybody to justify a health need more than once.
What happens when you leave. What comes back, who arranges it and when the arrangement is made, and if the answer is that nothing comes back, say that, because an unstated expectation becomes an awkward request later.
Ownership of the policy and review date. Two lines, and they are the reason the document will still be accurate next year.
What Good Looks Like in Practice: Three Worked Arrangements
Rather than leave this abstract, here are three arrangements that work, with the trade-offs each one accepts. All three are coherent, which is the property that matters.
The split policy, for a distributed team of 60 to 400. The company buys and ships the computer, which stays a company asset with its serial number recorded and its enrolment checked in the first week. A one-off furniture amount goes out near the start date for a named list: desk, chair, monitor, keyboard, mouse, with a refresh portion available after three years. Furniture belongs to the individual and never comes back. The computer is collected on exit by whoever handles retrieval, with the courier arranged before the last day rather than after it.
What this accepts: you still run laptop logistics, which is real work and needs either an internal owner or a vendor. What it buys: a fleet record you can defend, no ownership arguments and nothing unenrolled.
The stipend-only policy, for markets you cannot reach. Everything is funded, the individual owns everything, and the policy says so in the second paragraph. No equipment appears in your asset register. Company data is handled through whatever arrangement you have for personal devices, which is a separate decision that has to be made explicitly rather than assumed. On exit, nothing is requested.
What this accepts: a portion of your working environment is outside your visibility, which is a serious position for computers and needs a security answer rather than a shrug. What it buys: it works everywhere, immediately, with no logistics at all.
Reimbursement with a serial number, for teams that want choice and a record. The person chooses. They buy within a named list and a cap, submit a receipt with the device serial number as a required field, and are reimbursed inside a short and reliable cycle. The written claim states that items above a threshold are company property held by the employee. Anybody who would rather not spend their own money can ask the company to buy directly, and that option is published rather than granted on request.
What this accepts: expense administration on both sides, and a cash-flow burden that the direct-purchase option exists to remove. What it buys: people get the machine they want and you still have a serial number and an ownership statement.
| Arrangement | Who owns the computer | What comes back | Main trade-off |
|---|---|---|---|
| Split: provide laptop, fund furniture | Company | The computer only | You still run laptop logistics |
| Stipend only | The individual | Nothing | Unmanaged devices need a security answer |
| Reimbursement with serial capture | Company, above a threshold | Items above the threshold | Expense admin and cash-flow timing |
| Recurring allowance for running costs | Not applicable | Nothing | Never use it to fund hardware |
Notice what all three share. Each one answers the ownership question in writing, each one has a stated route for accessibility that does not run through the same queue as preference, and each one captures a serial number for anything the company owns. Those three properties are what make a policy survive its first difficult exit, and none of them depends on the amount.
The Cost of Getting This Wrong
The expensive failures here are not financial. They are ownership disputes, unenrolled devices and the inconsistency that comes from a policy applied by memory.
The ownership dispute is predictable. People anticipate it and still fail to prevent it. It costs a small amount of money, a disproportionate amount of time and a measurable amount of goodwill, because the departing person genuinely believed something different and is not being unreasonable. Every such dispute traces back to a policy that funded a computer and did not say who owned it, which is a one-sentence omission with a long tail.
The unenrolled device is the one that actually matters. A machine holding company email and customer data, bought privately, never enrolled, with no serial number recorded, held by somebody who left four months ago. You cannot wipe it, cannot prove it was wiped and cannot even produce a list of how many such devices exist. That is the finding you do not want in a security review, and it is created not by a bad decision but by a policy that was silent on two fields.
The inconsistency is the slowest cost. Without a published figure and a published list, the amount granted drifts according to who asked, when and how persistently. People compare notes. Within a year you have a de facto policy that nobody designed and that differs between teams, and correcting it downwards is much harder than setting it correctly at the start.
So the diagnostic worth sitting with: are you trying to remove logistics work, give people choice, or reach markets you cannot ship into? The first is better solved by fixing logistics, the second is a genuinely good use of a stipend, and the third is often the only option available.
When You're Ready to Move Beyond Reimbursing Things Case by Case
The signals are specific. You have handled more than three equipment reimbursements as one-offs in a quarter, and somebody has asked who owns a laptop and the answer took a conversation. Your fleet record contains machines you are not certain you own. A new market has people in it and no delivery route. Any two of those and the case-by-case approach has run out.
Write the ownership sentence first. Before the amount, before the item list and before any benchmarking, because that one sentence determines every other decision in the policy. Then decide whether the computer is provided or funded, and keep those two mechanisms separate from whatever you do about furniture.
Then it's not a policy problem. If the company should own the computers and the difficulty is getting them to people, that's a logistics purchase rather than a policy one. RemoAsset covers the distributed joiner and leaver cycle with a published annual figure and the three limits named above, and it will not help at all with the devices a stipend has already put into the field unrecorded. That part is a clean-up, and it is easier to start now than after the next twenty hires.
Frequently Asked Questions
What is a home office stipend?
It's money given to employees to set up their working space. Three designs are common. A one-off amount near the start date, a recurring allowance, or reimbursement against receipts for a named list of items. The important variable is not the figure but whether the equipment bought with it belongs to the company or to the individual, since that determines what comes back and what can be managed.
Should a home office stipend cover the laptop?
Usually not. The laptop is the item you most need to own, enrol and retrieve, and funding it through a stipend works against all three of those. The arrangement most well-run distributed companies land on is to provide the computer and use a stipend for furniture and peripherals, which separates the item you must control from the items you do not.
Who owns equipment bought with a stipend?
Whoever the policy says. If the policy is silent, you have a dispute waiting. If you want the company to own an item, buy it or reimburse it with a written statement that it is company property held by the employee, and record its serial number. If the individual owns it, accept that it will not come back and should not sit in your asset register.
How much should a home office stipend be?
Build it from the items. Price a desk, a chair, a monitor and peripherals at a sensible specification, add them up, and you have a figure you can defend in front of anybody who asks. Then state whether it is a cap or a budget. Because that ambiguity causes more questions than the amount does.
Is a home office stipend taxable?
That depends. It turns on the jurisdiction, on the design and on who owns the equipment, and the answer differs between countries that otherwise look similar. Anybody telling you confidently without knowing those three things is guessing. Take your chosen design and your country list to your payroll provider and a local adviser in each market, get the answer in writing, and keep the per-country notes in an appendix.
What happens to the stipend equipment when somebody leaves?
Whatever you stated at the start. Which is exactly why the statement has to exist at the start, written before the first payment goes out rather than after the first resignation. If the company owns an item, arrange the collection rather than asking the person to organise it, because retrieval rates fall sharply once somebody's last day has passed. If the individual owns it, say nothing and let them keep it, since a request made at that point reads as a surprise condition.
Can we run a stipend and still keep an accurate asset register?
Yes, but only if you capture the data at the moment of payment. Make a serial number a required field on the claim, or ask for a photograph of the device label during onboarding. Retrospective capture almost never works. Because no equipment vendor and no asset platform can discover a device that was bought privately and never recorded.
One closing observation, offered because it took me a while to see it. The companies that handle this well are not the ones with the most generous amount or the most carefully benchmarked figure. They are the ones where somebody wrote two sentences about ownership before the first payment went out, and then never had to have the conversation again. Everything else in this article is detail around those two sentences.
Decide who owns the laptop first, and the rest of the policy writes itself.
