TL;DR
- Core decision: The hard part isn't moving money. It's building a paper trail that reads as a contract, not as a job.
- When doing nothing is right: Genuinely short engagements, genuinely part-time work, and a real market of alternative clients on the contractor's side.
- What has to be true: The contractor sets their own hours, serves other clients or holds themselves out as available to do so, and works on outputs rather than on a schedule you set.
- How the options split: Three honest categories. Keep the invoices. Pay through a layer. Or convert the relationship into local employment.
- Decision rule: Read your own payments file. If a stranger could tell you that this person works for you from the pattern alone, the relationship is already documented, just not in the form you wanted.
- Outcome to expect: Cleaner exposure, fewer surprise reclassifications, and an audit trail that holds up when a regulator asks, rather than one you assembled in a panic.
The Friday Before the Audit
A finance lead at a Series B software company opens a shared inbox on a Friday afternoon and finds a note from her general counsel. A former contractor in another country has filed a claim with the local tax authority. The contractor worked for the company for nineteen months, billed on the last business day of each month, and was paid a fixed amount that never changed. The general counsel's note is short. The file looks like employment, and the file is going to be the first thing the authority reads.
She scrolls up the inbox. Above the email are the same monthly messages, nineteen of them, each with the same subject line, the same amount, the same date. She closes the laptop. But the file doesn't close with it.
The company built this arrangement one contractor at a time. Each hire felt small. The payment was a single bank transfer against an emailed invoice, and the only local touchpoint was a signed agreement that someone in legal had templated for a domestic engagement and then never revisited. Nobody had meant to misclassify anyone. The pattern did it for them.
Best tools for Global HR
But the real issue isn't the bank transfer, and it isn't the invoice. The real issue is what the payment record proves. A regular sum on a fixed date, paid for a full-time schedule, reads as salary, regardless of what either party called it. The way you pay quietly documents the relationship you've, and the document a regulator reads first is the document the payments file already is.
When You Can Keep Going As You Are
Four honest stages separate a setup that genuinely works from one that's a problem in waiting. Most readers fall into the second or third. Few fall into the first or the fourth.
You're genuinely fine when the engagement is short, the work is bounded by a deliverable, and the person on the other end of the transfer is one of several people you've hired for similar work in the past year. A freelance designer brought in for a six-week rebrand, paid a fixed project fee, delivering files at the end. They have other clients. The invoice names a project, not a month. If you stopped paying them, they wouldn't lose their main source of income. This is the cleanest shape, and most operations teams don't sit here, because the work they hire for is ongoing rather than project-shaped.
You have friction when the contractor has been on the books for over a year, the monthly amount has crept up, and you find yourself briefing them on the same product meetings every other employee attends. The work is still labelled by project, but the rhythm is salaried. You haven't heard from a tax authority and you may not for some time. The risk here's not that something has gone wrong today. The risk is that the file is being written today, in a form you don't control.
You have real risk when the contractor works close to full time, only works for you, signs into your systems under a personal account that has been there longer than some of your employees, and has been on the same rate for more than a year. A regulator asking to see this file would see an employee. So would a judge. So, frankly, would you. The reason nothing has happened is that no one with standing has asked yet.
The edge case is the contractor you can't replace, in a country where the only credible alternative is a local entity or an EOR, who has done the work for years and is now asking about benefits, paid time off, and a long-term commitment. At this point the question is no longer how to keep the relationship. The question is how to formalise it without triggering a backdated reclassification of the years that have already gone by.
Five Questions You Ask Yourself at 11pm
Does the contract I have actually match the work being done? Usually no, and the gap is the problem. If your contract says project-based deliverables and your messages show daily standups and PTO requests, the contract is the cover, not the truth. A regulator reads both, and weights the operational record.
Is this person genuinely in business on their own? The IRS totality test and the ABC test both ask this in different ways. A second client, a website, a registered trade or profession, and a public-facing presence all count. A registered company through which they invoice you counts for very little if it has no other customers.
What would a stranger conclude from twelve months of payments? If you can show a stranger the AP file with the name and country redacted and they would still know this was a job, the relationship is already documented in the form a regulator cares about. The only move left is to either change the relationship or change the documentation, and you can't change the past.
What happens in this country if a claim is filed? Local advice will tell you. What you can know without advice is that the cost of defending a claim isn't the cost of paying one. The internal time, the management attention, and the reputational drag show up regardless of outcome. The question is whether the relationship was worth defending in the first place.
Am I paying for a person, or paying for outcomes? The honest answer is often both. The shape that protects you is paying for outcomes, with the contractor deciding how to deliver them, when to deliver them, and how much of their week to commit. If you've moved past that shape and into paying for availability, the only honest move is to stop pretending the invoice says what it doesn't.
The Three Honest Categories
The approaches split into three honest categories, and pretending there are more options is a vendor's trick. Each does something real. Each fails in a specific way.
Keep the direct payment and tighten the discipline. This means paying against invoices that name a deliverable, varying the amount where the work varies, using a payment method that doesn't look like payroll, and keeping a record of other clients the contractor serves. The approach is right when the engagement is genuinely short, genuinely part-time, and the contractor has a real practice outside of you. It fails when the relationship has drifted into salaried rhythms that no amount of contract language will disguise. The weakness is that paper produced after a challenge is worth less than paper produced at the time, and most teams only produce paper when challenged.
Pay through a layer. This means a platform that handles currency conversion and invoicing, an umbrella arrangement in a country that uses them, or engaging the contractor through their own limited company in a country where that's normal. The approach is right when the layer is genuinely independent of you and you can show why it's independent, and when the layer's existence isn't a fiction erected to disguise employment. It fails when the layer is just you wearing a different hat. A platform that holds itself out as the employer of the contractor but takes its instructions from you isn't a layer. A contractor's own limited company with no other customers isn't a layer either. It's a payroll substitute without the obligations of payroll.
Convert the relationship into local employment. This means either setting up your own local entity and hiring the person, or going through an employer of record that employs them on your behalf. The approach is right when the work is full time, the work is ongoing, the person is integrated, and the only reason they're not on payroll is inertia. It fails when the work is genuinely project-based and the cost of the conversion exceeds the risk of the original arrangement. The weakness is that conversion doesn't rewrite the past, and the past is what some regulators care about most.
Five Questions to Ask About Your Own Organisation
How many hours per week does this person work, and for how many of your weeks in a row? Read the time zone, the calendar, and the messaging activity. The number is less important than the shape. If the answer is the same number every week, the relationship isn't project-based, regardless of what the invoice says.
What do their invoices actually describe? A deliverable, a milestone, a named piece of work. Not "monthly retainer" with the same amount every time. If the line items are time-based, the invoice is a timesheet in a different font.
What evidence exists that this person serves other clients? A website, testimonials, a registered trade, a second invoice trail, public work under their own name. If the only record of their professional life is their relationship with you, a regulator will treat that as significant.
What does the contractor's own company look like, where one exists? A registered entity with a real address, a real bank account in its own name, a separate signatory, and other customers. Not a shelf company with the contractor as sole director, a single incoming payment per month, and no operating activity.
If a regulator asked tomorrow, what would you hand over, and how long would it take you to gather it? A day, a week, a month. The answer is a rough proxy for how exposed you're. A defensible file is a file you can produce quickly and without scrambling.
Six Ways to Pay, Reviewed
Direct bank transfer against invoices
The smallest setup. You pay a foreign bank account against an emailed invoice, on terms the contractor has set. The bank handles the conversion, the invoice is your only record, and the relationship runs on a document you wrote once and haven't updated.
It earns a place because it's fast, it's cheap, and it doesn't require you to think about local entities, registrations, or layers of intermediation. For a short engagement, paid against a named deliverable, with a contractor who has other clients, it's hard to improve on.
Where it falls short is in the file it leaves behind. The same invoice template, the same amount, the same date, paid for months on end, is a payroll record in everything but name. A regulator reading twelve of these in a row won't be persuaded by the word "consulting" on the line above the figure.
A contractor payment platform
A platform sits between you and the contractor, holds the funds, handles currency conversion, and may issue local-currency payouts through partner banks. You pay one invoice, in your currency, and the platform handles the rest.
It earns a place because it removes the operational drag of paying people in six countries in six currencies, and because it produces a consistent paper trail across contractors and countries. For a finance team that has outgrown the shared inbox and the spreadsheet, it's a real step up.
Where it falls short is that the platform is a payment mechanism, not a legal structure. The same regular payment, on the same date, in the same amount, is still a payroll pattern. The platform can document the relationship accurately. It can't change what the relationship is.
An agency or umbrella arrangement
A local agency or umbrella company engages the worker, bills you a fee, and runs payroll. The worker is on the agency's books for tax and statutory purposes. In some sectors and some countries this is the default, particularly in the UK, where umbrella use is common and where, from 6 April 2026, agencies and end clients can become liable for PAYE underpayments where workers are supplied through umbrellas, even where the umbrella runs payroll.
It earns a place where the sector expects it, where the worker prefers it, and where a local employment relationship is genuinely the right shape. In those cases the umbrella is the answer, not a workaround.
Where it falls short is where the umbrella is being used to convert what is functionally your own employment into a paper arrangement that looks like agency supply. The presence of the layer doesn't change the underlying relationship. And where the umbrella is small, thinly capitalised, and runs payroll in a way that doesn't meet its own obligations, the liability can flow up the chain.
Engaging through the contractor's own company
You contract with a personal service company, limited company, or equivalent in the contractor's country. The PSC invoices you, you pay the PSC, and the worker draws what they need from the PSC under their own tax arrangements. In the UK this is the structure that IR35 is designed to test.
It earns a place where the contractor genuinely runs a business with multiple clients, where the PSC has substance, and where the contractor genuinely takes the risk of being between engagements. In that shape the structure is real, and the relationship is what it looks like.
Where it falls short is where the PSC is a single-customer entity, with no other revenue, no staff, no office, and a sole director who has worked on your projects for the past two years. In that shape the PSC isn't a company. It's a payslip.
An employer of record
An EOR employs the worker through its own local entity, running local payroll, statutory filings, and employee-level obligations. You direct the work. The EOR holds the employment relationship. You don't need your own entity in the worker's country.
It earns a place where the work is genuinely ongoing, where the worker is integrated, where you don't have a local entity and don't want to set one up, and where the relationship is full time. In that shape the EOR is doing what an EOR is for, and the cost is the cost of a real employment relationship without the friction of incorporation.
Where it falls short is where the EOR is being used to keep up the appearance of a contractor arrangement while the work is, in substance, employment. An EOR doesn't turn employment into a contract. It turns a contract into employment, with the EOR as the employer. It also doesn't remove all exposure. Activity beyond employing staff, such as concluding contracts locally, maintaining a fixed office, or holding inventory, can still create a permanent establishment, and an EOR doesn't answer corporate tax.
Converting the person to a local employee
You incorporate locally, or use an existing local entity, and you hire the person as an employee. They're on your payroll, on your benefits, and under your employment law.
It earns a place where the relationship is, in every observable sense, employment, and where continuing to call it a contract is the more expensive option. This is the move that resolves the misclassification exposure at the source, rather than managing it.
Where it falls short is in the back period. A conversion doesn't erase the years in which the relationship was, on paper, a contract. Local law determines how those years are treated. Some jurisdictions look back. Some don't. Either way, the conversion is an admission about the present that a regulator can read backward. The move is right when the work demands it, and it should be taken on the basis of advice about the past as well as the future.
The Decision Table
| Situation | Scale | Setup | Primary Pain | Recommended Starting Point |
|---|---|---|---|---|
| One-off deliverable, contractor with other clients | Under three months | Direct bank transfer against invoices | Operational | Keep the invoices. Add a deliverable description and a real alternative-clients note to the file. |
| Ongoing part-time work, project-shaped | Under ten hours a week, under a year | Direct bank transfer against invoices | Operational | Keep the invoices. Vary the amount where the work varies. Reassess at the year mark. |
| Ongoing full-time work, single country, no local entity | Full time, multi-year | Direct bank transfer against invoices | Misclassification exposure | Convert to local employee through an EOR while you decide whether to incorporate. |
| Multiple contractors, varied countries, varied shapes | One to twenty contractors, several countries | Direct bank transfer and a shared inbox | Operational and documentary | Move to a payment platform and add a contractor intake checklist that records the substance of the relationship, not just the contract. |
| Contractor in a country where PSC engagement is the norm | Part time to full time, ongoing | Engaged through the contractor's own company | IR35 or local equivalent | Test the relationship against the local off-payroll rules, get a status determination, and document the reasoning at the time. |
| Long-tenured contractor, full time, integrated, hard to replace | Full time, multi-year | Direct bank transfer against invoices | Misclassification exposure | Convert to local employee. Treat the back period as a separate question for local advice. |
| Mixed population, some genuinely project-based, some salaried in all but name | Five to fifty contractors | A patchwork of arrangements | Documentary inconsistency | Separate the file. Audit the salaried-in-all-but-name group first. Leave the genuinely project-based group alone. |
What Your Payment Records Actually Show
An auditor reading your AP file doesn't start with the contract. The contract is the last thing they read. They start with the payment record, because the payment record is harder to fake and harder to argue with.
| Pattern | What it suggests | What to do about it |
|---|---|---|
| Same amount, same date, every month, for over a year | Employment, regardless of label | Reassess. If the work is full time, formalise. If it is not, vary the amount and the cadence. |
| Invoice describes time, not outputs | Timesheet, not deliverable | Re-cut invoices around deliverables, milestones, or named pieces of work. |
| Multiple contractors paid on the same day, in similar amounts, for similar work | Workforce, not supplier base | Document why each is genuinely independent. The harder this is to do, the more exposed you are. |
| Contractor has a single customer relationship, visible from the AP file | Single-customer entity | Test the relationship against the local test. Where the test is the ABC test, a single customer is a serious signal against (C). |
| Contractor logs into your systems daily, attends your standups, has an internal email address | Integration | Either accept the integration and formalise, or reduce the integration in ways the work can absorb. The middle position is the worst position. |
| Payments to one country have grown year on year while engagements with locals have shrunk | Local presence, in substance | Take advice on permanent establishment, particularly in light of the OECD's November 2025 update on remote home offices. |
The Documents to Keep, and For How Long
A genuine contractor relationship has paperwork that looks like a contractor relationship. A salaried-in-all-but-name relationship has paperwork that looks like an attempt to describe one after the fact. The difference shows in what was kept, when, and in whose normal course of business it was produced.
| Document | What it shows | Retention |
|---|---|---|
| A signed agreement that names deliverables, milestones, or project scope | The shape of the engagement at the time | Through the engagement, plus a meaningful period after, set by local rules |
| Invoices that describe work done, not time spent | The substance of what was paid for | Same as above |
| Evidence that the contractor served other clients, contemporaneous with the engagement | Genuine independence | Same as above |
| A status determination where the local rules require one | That the question was considered, by the party required to consider it | As required locally, and longer where reasonable |
| Records of expenses reimbursed against receipts, not as part of a fixed fee | That expenses were genuinely expenses, not salary in disguise | Through the engagement and beyond |
| Communications showing the contractor set their own approach to the work | Absence of detailed direction | Through the engagement and beyond |
The longer the file is, and the more of it was produced at the time rather than in response to a question, the more it does what a paper trail is supposed to do. A file assembled under pressure is a file a regulator can read as a file assembled under pressure.
The Cost of Getting This Wrong
The number on the invoice isn't the cost of getting this wrong. The number on the invoice is the cost of getting it right. The cost of getting it wrong is everything that comes after, and most of it doesn't appear on an invoice at all.
There's the internal time. A claim, an audit, or a reclassification pulls in finance, legal, people, and the line manager who hired the contractor in the first place. None of those people are budgeted for this. The work they stop doing is the work they were hired to do. There's the management attention. A founder or a country lead ends up reading case law at midnight, the way you read it now, and the question they're trying to answer isn't how to grow the team. It's how to explain the last eighteen months of payments. There's the reputational drag. A reclassification, once public, becomes a fact about the company, attached to the company name, and surfaced by every future candidate who runs a search before signing a contract. So the cost of getting this wrong is the cost of the work that stops, the cost of the attention that gets pulled, and the cost of a public fact you can't retract.
And the most expensive part is that the cost is paid after the decision, not at the time of the decision. The transfer that created the exposure was cheap. The exposure itself is what is expensive.
So the question isn't what the cheapest payment method is. The question is what the cheapest defensible relationship is, in the country you're paying, for the work you're buying, for the duration you're buying it for.
When You Are Ready to Go Further
If the diagnostic above has surfaced more than one or two contractors in the second or third stage, the next step isn't a vendor selection. The next step is a clearer read on the shape of the exposure, and on which of the three honest categories each relationship actually belongs in. Most teams can do this themselves, with a checklist and a quiet afternoon. Some teams need a structured comparison of the options, with the trade-offs laid out by someone who doesn't sell any of them.
HROpsLab is a review publication, not a vendor, and we sell nothing. Our independent comparison work is designed for the reader who has finished the diagnostic and wants a second view on the path forward, with the vendor-shaped incentives removed. We don't supply software, consulting, or legal advice. We do the work of laying the options side by side, and we let the reader choose.
If that's where you're, the door is open.
Frequently Asked Questions
Is a signed contractor agreement enough?
A signed agreement is a starting point, not an answer. The agreement describes what the parties intended. The payment record, the communications, the calendar, and the operational pattern describe what actually happened. In a challenge, the operational record is what gets read first, and the agreement is read against it. Where the two diverge, the operational record usually wins.
Should I pay in the contractor's currency or mine?
Currency choice affects operational ease more than legal posture. What matters is that the payment record is consistent, the invoice is in the same currency, and the exchange rate is recorded at the time. Where the rate is being chosen to make the amount look variable when it isn't, the variation isn't going to help.
What do I do about a contractor who only works for me?
The honest answer is that the relationship may be employment, and that calling it a contract doesn't change what it's. The first step is a local status test, run on the substance of the work, not the label. The second step is a decision about what to do with the answer, and that decision is one to take with local advice.
Does a payment platform transfer the risk?
No. A platform handles the mechanics of paying a contractor in another country. It doesn't change the substance of the relationship, and it doesn't change how a regulator reads the pattern of payments. The platform can produce a cleaner file. It can't make employment look like contracting.
How should I handle expenses?
Expenses should be reimbursed against receipts, separately from the fee, on submission, and on terms the contractor has agreed in advance. Reimbursing a fixed monthly amount for expenses, paid with the fee, on the same date, blurs the line between fee and reimbursement. Where expenses are genuinely expenses, the record should show that.
Should I be withholding anything from the contractor's payment?
In some jurisdictions, yes. In others, no. The rule depends on the country, the type of payment, and the structure of the engagement. Where local rules require withholding, the failure to withhold is its own exposure, separate from the classification question. This is a question for local advice, and a question to get right before the first payment, not after the last.
When is the right time to convert a contractor to an employee?
When the work is full time, ongoing, and integrated, and the only reason the person isn't on payroll is that the conversion is inconvenient. At that point the relationship is already documented as employment, and the conversion is the move that aligns the form with the substance. The back period is a separate question, and one for local advice.
Do I need a separate agreement for each country?
A templated agreement that has not been opened since it was first used is a liability. The agreement should reflect the law of the contractor's country, the structure of the engagement in that country, and the local test that will be applied if the relationship is challenged. Where the template doesn't do that, the agreement isn't doing its job.
Independent comparisons for people leaders who would rather choose well than choose fast.
