Cross-Border Staffing: Legal Entity, EOR and Who Actually Employs the Worker
Every international staffing arrangement turns on one question, and firms that answer it after winning the work create liability rather than revenue.
When a staffing firm in one country places a worker into a role in another, somebody has to be the legal employer. That single question determines tax, statutory contributions, employment liability and whether the arrangement is lawful at all. Four structures answer it, they cost very different amounts, and choosing the wrong one is a compliance exposure rather than a pricing error.
Last reviewed August 2026. Structural summary. Take local legal advice in both jurisdictions before contracting.
Key takeaways
- Who employs the worker is the first question, not the last. It determines tax, contributions, liability and legality.
- Four structures exist and they cost very differently. Own entity, EOR, local partner, or genuine independent contractor.
- Misclassification risk lands on both agency and client. Which is why enterprise clients ask about it during procurement.
- Permanent placement across borders is far simpler. Because the client employs the person, not you.
Why permanent placement is straightforward and contract is not
On a permanent placement across borders, the client employs the candidate directly. Your role ends at introduction and fee, and the employment question is the client's rather than yours.
Contract is entirely different. Somebody employs or engages the worker for the duration, and that party carries tax withholding, statutory contributions, employment protections and liability. If that party is you, you need a lawful basis to employ in that jurisdiction.
This is why most offshore firms should enter a new market on permanent placement first, per landing your first overseas client.
The four structures
Your own legal entity. Full control, full cost. Registration, ongoing compliance, local accounting and payroll. Justifiable at scale in a market you are committed to, and rarely justifiable for a first contract.
Employer of record. A third party employs the worker and handles payroll, contributions and compliance for a fee. Fast, no entity required, and the fee comes out of your spread, per contract markup by market.
Local partner agency. They employ and you supply, splitting the margin. Simple, and it makes their compliance your reputational exposure, per partnering with complementary firms.
Genuine independent contractor. Lowest cost, highest risk, and only lawful where the working arrangement genuinely supports it.
Misclassification, and why clients ask about it
Treating somebody as an independent contractor when the working arrangement resembles employment is the most common cross-border compliance failure.
Tests differ by jurisdiction and generally look at control, integration into the organisation, exclusivity, and who provides tools and direction. A worker sitting in the client's team, working their hours, under their supervision, is difficult to characterise as independent regardless of what the contract says.
The exposure typically lands on both the engaging party and the client, which is precisely why enterprise procurement asks about it during onboarding rather than trusting the contract.
Data protection across borders
The second compliance layer, and the one that arrives earlier in the sales process.
Moving candidate data between jurisdictions raises questions of lawful basis, transfer mechanism and retention. Under GDPR that includes how data leaving the EU is protected, and under India's India's DPDP Act framework there are separate obligations on the Indian side.
The practical requirement is a coherent answer on hosting, transfer and retention available in the first substantive meeting, per India's DPDP Act and candidate data.
How to choose a structure
One or two workers, testing a market: employer of record. The fee is high per head and the alternative is an entity you do not need yet.
Growing volume, uncertain commitment: local partner agency. Margin split, no infrastructure, and it produces market knowledge you can use later.
Committed at scale: your own entity, once the volume justifies the ongoing compliance cost.
Genuine independent professionals: contractor arrangements, verified against local tests rather than assumed.
What to have before you contract
Written advice in both jurisdictions. Not one. The rules in your country and theirs both apply.
Clarity on who employs. Stated in the contract with the client, not implied.
The classification test applied honestly. Against the actual working arrangement rather than the one described in the agreement.
Your data position documented. Hosting, transfer, retention, deletion.
None of this is optional at enterprise level and all of it is asked during procurement rather than after.
Frequently asked questions
Who is the legal employer in cross-border staffing?
It depends on the structure: your own local entity, an employer of record, a local partner agency, or nobody if the worker is a genuine independent contractor. That choice determines tax, contributions, employment liability and legality.
What is an employer of record?
A third party that legally employs the worker and handles payroll, statutory contributions and compliance for a fee. It removes the need for your own entity and the fee comes out of your contract spread.
Is permanent placement across borders simpler than contract?
Considerably. On a permanent placement the client employs the candidate directly, so the employment question is theirs. Contract requires somebody to employ or engage the worker for the duration, with all the obligations that carries.
What is misclassification risk?
Treating somebody as an independent contractor when the working arrangement resembles employment. Tests look at control, integration, exclusivity and who provides direction, and the exposure typically lands on both the engaging party and the client.
When should a staffing firm set up a local entity?
Once volume justifies the ongoing compliance, accounting and payroll cost, and once you are committed to the market. For one or two workers testing a market, an employer of record is the sensible alternative.
What data protection issues arise in cross-border staffing?
Lawful basis for processing, the transfer mechanism for moving candidate data between jurisdictions, and retention. Both the receiving jurisdiction's rules and your own country's framework apply simultaneously.
The question to answer before the quote
For any cross-border contract role, answer one question before pricing it: who will legally employ this worker, and what does that cost. Everything else follows from that answer.
Firms that quote first and resolve the structure afterwards discover the cost base in month two, by which point the rate is agreed.
See cost per assignment after structure
Bring a cross-border engagement and we will show you margin after employment costs rather than headline spread.
Book a demoFounder of Sortinghat, an AI-native ATS and CRM for staffing, search and RPO firms. Writes about recruiter capacity, sourcing economics and what actually changes when AI reaches a delivery desk. More about the author
Related reading