What Is an Employer of Record?

An employer of record (EOR) is a third-party local employer that hires a worker on behalf of a client company and administers agreed employment duties — the local employment contract, payroll, tax withholding, statutory benefits, and employment records — while the client company still directs the worker's day-to-day work. That sentence describes the common service model, not a single statutory category recognized everywhere: the exact responsibilities, legal effect, and risk allocation depend on the country, the provider's operating model, and the service agreement.

Used for the right situation, an EOR may let a company employ someone in a country where it has no local employing entity — typically for a small number of hires, an uncertain time horizon, or a near-term start. It is not automatically the best long-term structure, and it is not a way around local law.

Before requesting quotes, confirm the facts that decide everything else: the worker's country and actual work location, intended employee status, work-authorization position, your own entity position, and how the arrangement would end. And hold one rule fixed throughout: an EOR is a hiring structure, not a risk waiver. Corporate tax, permanent establishment, immigration, data protection, intellectual property, and worker-classification questions can remain with your company, and some of them call for qualified counsel or a tax adviser before you proceed.

The short answer, in one screen. The structure choice is general. The rules that settle it are national, so every branch below ends at a country check.

• Choose an EOR if you need a lawful employee relationship in a country where you have no employing entity, headcount is small, the horizon is uncertain, and a provider verifiably supports the country and the role.
• Choose direct employment through your own entity if the country is becoming a durable operation with local revenue, leadership presence, or control needs that outgrow a service arrangement.
• Keep a contractor relationship only if the working reality genuinely satisfies that country's classification rules — a contract label alone does not.
• Choose neither yet if you cannot state the worker's country, intended status, authorization position, and your entity position: those facts decide which structures are even available to you.

On cost: the service fee is only one line. Gross salary, statutory employer contributions, mandatory benefits, deposits or prefunding, FX, and one-time charges are separate items driven mainly by the destination country and your own pay decisions, which is why the country, not the provider, sets most of the budget. The EOR pricing guide carries the fee structures and what a complete quote contains.

On this page:

• Verify the arrangement before shopping providers
• Who does what: the responsibility split
• How an EOR works, step by step
• Who owns what in practice
• What an EOR does not solve
• When an EOR fits and when it does not
• EOR alternatives and how they differ
• Which structure fits which situation
• What to verify before choosing an EOR
• Choosing a provider at a glance
• Frequently asked questions

Verify the arrangement before shopping providers

Use an EOR only after the facts below are clear. This is a planning gate, not a legal eligibility test, but a quote cannot fix an unknown fact, and every row changes what "compliant" means for your hire.

Confirm this first	Why it matters
Where the person will actually work — country, and region where relevant	Employment terms, payroll, social security, and registration duties follow the place of work; in EU countries, for example, they are governed by national employment rules within EU minimums.
Whether they are intended to be an employee or a genuinely independent business	Classification is decided by the facts under the applicable country's rules, not by the contract label. If this is still an open question, start with contractor classification risk before structuring anything.
Whether your company already has a suitable entity or registration in that country	If you do, PEO, payroll-only, or direct employment may fit better than an EOR; if you do not, the EOR's employing entity becomes the load-bearing fact to verify.
Whether the worker needs authorization to work there	Eligibility depends on nationality, status, and national immigration rules; provider sponsorship support varies by country and case.
Headcount, benefits, start date, payroll cadence, time horizon, and exit plan	These drive cost, provider fit, and the contract terms you must negotiate — and they determine when an EOR stops making sense.
Whether the role is regulated or subject to collective, works-council, data, or IP constraints	Some roles, sectors, and agreements carry duties a standard EOR workflow does not cover; surface them before you commit.

If any row is unclear, resolve it before comparing providers. That is the first action this page asks of you.

The six country layers that decide your hire. This page is country-neutral by design; the rules that decide your hire are national. Whichever country you land on, these are the layers to go and find, and the kind of authority that governs each:

• Employer contributions and payroll taxes — set by the national tax authority and social-security institution, often with floors, ceilings, or bands.
• Notice, severance, and lawful grounds for dismissal — set by national employment statute, and in many countries by collective agreements on top of it.
• Probation — an initial period of employment that many countries regulate separately, including how it may end.
• Mandatory benefits, leave, and any additional-month pay — statutory minimums set nationally, and sometimes sector by sector.
• Licensing of the arrangement itself — usually a labor ministry, employment agency, or business register; see below.
• Immigration and work authorization — set by the national immigration authority, and specific to the worker rather than the role.

Ask a provider which of these it administers and which it merely reports on, and get the answer per country in writing.

Where the model itself is restricted

One question deserves separating out, because vendor content rarely raises it: whether the arrangement is permitted in the destination country at all. Several countries regulate the supply of workers to work under another company's direction — through licensing, registration, or a restriction outside a defined framework. Whether a particular EOR arrangement falls inside those rules is a question for local counsel, not for a sales team.

Country	How the country regulates supplying workers	Governing source	Effective / as of	Verification status
Germany	Hiring out employees to work under another company's direction generally requires a licence from the Federal Employment Agency under the Arbeitnehmerüberlassungsgesetz (AÜG); a notification suffices only in defined cases. The AÜG also caps a single assignment at 18 consecutive months with the same user company, counting earlier assignments in full where the gap between them is three months or less, unless a collective agreement in the user's industry sets a different maximum	Arbeitnehmerüberlassung — Bundesagentur für Arbeit; § 1 Arbeitnehmerüberlassungsgesetz — Gesetze im Internet; Fachliche Weisungen AÜG — Bundesagentur für Arbeit	AÜG consolidated text as in force at the date checked; agency guidance valid from July 1, 2026	Verified — checked August 1, 2026
France	Operations for profit whose exclusive object is the supply of workers are prohibited, outside listed frameworks including licensed temporary work (travail temporaire)	Article L8241-1, Code du travail — Légifrance	Version in force since April 4, 2015	Verified — checked August 1, 2026
Netherlands	Businesses that supply workers for payment must record this in the KVK Business Register under the Waadi, including foreign businesses with no Dutch branch. A separate admission system is being introduced under the Wet toelating terbeschikkingstelling van arbeidskrachten (Wtta): lenders may supply workers only once admitted to the lending market, admission is assessed by the Nederlandse Autoriteit Uitleenmarkt, and from January 1, 2028 hirers may engage only lenders on its public register	Waadi registration and Waadi check — Business.gov.nl; Wet toelating terbeschikkingstelling van arbeidskrachten — Nederlandse Arbeidsinspectie	Waadi in force; Wtta in force January 1, 2027, with assessment of applications beginning July 1, 2027	Verified — checked August 1, 2026

These three are examples, not the boundary of the issue, and each is stated at the level the governing source supports rather than as a verdict on any particular arrangement. Treat the model's local footing as a per-country question: ask which framework the provider operates under in your destination country, and take the answer to local counsel wherever the arrangement is anything other than routine. A provider's willingness to serve a country is not evidence that the model is permitted for your case.

Who does what: the responsibility split

The matrix below is this page's single reference for who does what; the sections that follow interpret the friction points rather than repeating the cells. The "EOR typically" column reflects how providers describe their own service scope — see, for example, the employer-of-record glossary entries published by Deel and Remote — which are vendor statements of a service, not statements of law.

Responsibility	EOR typically	Client company typically	Worker	Verify / notes
Local employment contract; formal employer	Issues and administers the local contract as formal employer for the covered arrangement	Approves terms; provides role and pay facts	Signs; holds statutory employee rights	Confirm in writing, per country: which legal entity is named as employer there
Payroll and payslips	Runs local payroll; issues payslips	Funds payroll; approves inputs by cutoff	Reviews pay; flags errors	Confirm in the agreement: cutoffs and funding deadlines
Withholding and employer contributions	Calculates and remits within the agreed scope	Funds employer-side costs	Bears employee-side deductions	Varies by country: registration and remittance rules
Statutory benefits and leave records	Administers statutory items; keeps records	Sets supplemental benefits; approves leave operationally	Requests leave	Varies by country: which items are mandatory and which optional
Day-to-day work direction	Not the manager	Leads: assigns work, sets priorities, manages output	Performs the role	Client obligation: keep direction lawful and consistent with the contract
Performance management	Supports formal steps	Leads assessment and feedback	Participates	Varies by country: formal warnings and dismissal steps usually run through the legal employer
Company policies and conduct	Employment policies within local law	Commercial and conduct policies for the work	Follows both	Client obligation: resolve conflicts between client policy and local law
Expenses and time-off workflow	Processes through agreed tools	Approves	Submits	Confirm in the agreement: the workflow and the system of record
Immigration and work authorization	Support varies by provider and country	Cannot start the worker without authorization	Personal status facts	Confirm in writing, per country: eligibility and the provider's sponsorship scope
Corporate tax and permanent establishment	Does not remove the analysis	Retains it; assesses local activities and authority	Not a party	Take advice: where activity exceeds ordinary remote work
Data protection, IP, confidentiality	Processes employment data under agreed terms	Owns commercial IP terms and data purposes	Handles client data per policy	Confirm in the agreement: the DPA, transfers, and the IP assignment chain
Classification history	A new arrangement does not cure the past	Retains exposure from prior contractor periods	Not a party	Take advice: jurisdiction-specific
Termination and exit	Executes the local process	Decides and funds; provides grounds and facts	Holds notice and severance rights	Varies by country: lawful grounds, notice, severance, and timing

Typical allocation — confirm the country, the employing entity, and the service agreement before relying on any row.

Two rows carry most of the friction. Day-to-day control stays with the client even though the EOR is the formal employer, which is exactly what makes the model useful, and what makes lawful, consistent management the client's job. And termination is a shared act: the client decides and funds it, but the formal steps run through the legal employer under local rules, so exit planning belongs at the start, not the end.

How an EOR works, step by step

Every EOR arrangement runs through the same sequence, even though the governing detail is country-specific. Each step below carries the failure point where arrangements most often go wrong.

1. Confirm the facts. Pin down the country and actual work location, intended employee status, start date, role, salary, benefits expectations, and any work-authorization need. The status decision leads because it changes the legal frame entirely: an employee needs a lawful employer, while a genuinely independent business needs neither an EOR nor an employment contract. Failure point: shopping fees before the facts. A quote built on the wrong country or status assumption is worthless, and correcting it later reopens everything.

2. Verify the employing entity and operating model. Ask, in writing and per country, which local legal entity will be named as the employer, and whether the provider operates a direct (owned-entity), local-partner, mixed, or undisclosed model there. The answer determines who you are actually relying on when something goes wrong. Failure point: treating a country-availability list as proof of an owned entity or a uniform service model. It proves neither.

3. Compare like-for-like quotes and negotiate the agreement. Request quotes on identical inputs — same country, salary, currency, benefits, start date, and term — and read past the headline fee to setup charges, deposits, FX treatment, and one-time items. The service agreement is where responsibilities, indemnities, liability caps, funding mechanics, response commitments, and exit terms are actually set, and it is far easier to negotiate before signature than mid-employment. Failure point: comparing headline monthly fees whose inclusions differ.

4. Complete the local contract and onboarding. The EOR prepares the country-compliant employment contract and collects what local rules require — identity, tax and social-security details, qualifications where relevant — and local rules commonly prescribe what must be documented in writing, in which language, and by when. As the local employer, the EOR's entity must be registered with the authorities and must register the employee in the country of work, as EU rules illustrate. Failure point: promising a start date before required contracts, registrations, funding, or work authorization are complete.

5. Fund payroll; the EOR runs it. The client funds salary, employer costs, benefits, and fees ahead of cutoffs; the EOR runs the agreed payroll, withholding, and remittance workflow and issues payslips. In the EU, for example, employer social-security contributions are typically owed in the country where the employee works, whatever the client's home country, the general rule set by Regulation (EC) No 883/2004 on the coordination of social security systems. A narrow exception covers posted workers holding an A1 certificate, which is not the ordinary EOR case. Build the provider's funding calendar into your own monthly close so the deadline is never a surprise. Failure point: missed funding deadlines, which surface to the worker as late pay.

6. Manage changes through defined handoffs. A raise, a parental-leave request, a disputed expense, a complaint about a manager — each moves between client and EOR on a path that should be agreed before it is needed, with a named owner and a response time on both sides. Failure point: nobody having clear ownership of an employee-relations problem until it has already escalated.

7. Exit deliberately. Termination, transfer to your own entity, a provider switch, or a country exit each follow a local process with its own notice, documentation, and cost. Transfers in particular are not automatic: moving the employee onto your new entity or a new provider typically means a new local contract and the worker's agreement, on a timeline local rules shape. Failure point: assuming an at-will-style exit exists everywhere, or discovering the transfer path only when you need it.

What an exit actually involves. Ask for these five before you sign, not when you are leaving:

• Two notice clocks, not one. The service agreement sets what you owe the provider; the employment contract and local law set what is owed the worker. They are different periods and both bind you.
• Sequence the two arrangements. The new employment contract, the worker's agreement to it, and the end of the old arrangement have to line up, so the worker is never left between employers.
• Continuity of service is a question, not an assumption. Whether accrued service length and entitlements carry across depends on the destination country's rules and on what is agreed — settle it before the move.
• Records and data outlive the engagement. Payroll records, employment documents, and personal data carry retention, access, and transfer obligations that do not end when the contract does.
• Accrued liability stays yours to fund. Notice, severance, untaken leave, and entitlements accrued during the engagement remain your cost, whoever administers the payment.

Operating models: owned entity, local partner, mixed, or undisclosed

Providers deliver EOR service through different structures, and the differences run to cost, data flow, and accountability, not just branding.

Model	Who is the employer	What it changes for you	How to evidence it
Owned / direct entity	The provider's own local company	One accountable company; typically the shortest data path and escalation chain	The provider's own current documentation naming the local entity in that country
Local partner	A third-party in-country employer, with the provider running the platform and client contract	A partner adds a margin, a second holder of employee data, and a second company in every escalation	The service agreement, plus a written statement naming the partner for that country
Mixed	Owned entities in some countries, partners in others	The model — and everything it changes — must be confirmed per country, not per provider	A per-country list in writing; a global claim does not settle it
Undisclosed	Not documented	Record it as "Operating model not verified" and treat it as an open due-diligence item, not a detail	Nothing to evidence — the absence is the finding, and it belongs in your comparison
What a country count is not	Not a statement of who employs anyone	A published country list is a service-availability claim. It is not evidence of an owned entity, a uniform service model, or a consistent liability chain in any one country	Ask for the employing entity's name in each country you need, in writing; a global figure does not answer it

Treat the model as a per-country fact to verify in writing: state a provider's model only when its own current documentation supports it. Step 2 above and the verification checklist below both turn on this distinction.

Who owns what in practice

The defining feature of the arrangement is that formal employment and operational management deliberately coexist. The EOR's entity signs the contract and carries the named employer's administrative duties; the client keeps the working relationship. Most day-to-day questions resolve cleanly once you see which of three recurring handoffs they belong to, and most disputes trace back to one of them being left undefined.

Daily management

The client assigns work, sets targets, runs the meetings, supplies role-specific tools and processes, and escalates problems. The EOR is not the operational manager and should not be treated as one. The working boundary is simple to state: the client leads the work; anything that touches the terms of employment routes through the EOR. A manager can change a project deadline unilaterally; a manager cannot unilaterally change pay, contracted hours, or job scope, because those are contract matters belonging to the formal employer's process.

That freedom carries an obligation. Mandatory local law and the real working facts can govern beyond what the service agreement says, so the client's conduct matters legally: discriminatory treatment, unsafe practices, or instructions that conflict with the local contract create exposure regardless of whose name is on the employment paperwork. The practical control is unglamorous: brief the managers who will direct the worker, before day one rather than after the first incident, on one rule: a manager who would check with HR at home should check with the EOR abroad, because the threshold for asking is lower, not higher, in a country whose rules they do not know.

Payroll and benefits inputs

Administration is only as good as its inputs, and the inputs are the client's job: compensation changes, bonuses and variable pay, approved expenses, recorded time where relevant, and timely funding. The EOR calculates, withholds, remits, and documents within the agreed scope, but a late or wrong input becomes a worker-facing failure that arrives under the employer's name with the client's fingerprints on it. Late pay is the fastest way to lose a new hire's trust, and it is almost always an input or funding failure rather than a processing one. Agree in writing who submits what, by when, through which channel, and who checks the first payslip in each new country. That first-payslip check matters because it validates every assumption at once — gross-to-net, benefits enrollment, cost coding, and currency — while an error is still cheap to fix.

Budget with the components separate, the way the quote should present them: gross salary, employer-side statutory costs, benefits, and the service fee are different lines with different behavior. Employer-side statutory costs are the contributions and payroll taxes an employer owes on top of gross pay; employee-side deductions come out of gross pay rather than adding to your cost. Treat the funding calendar as cash-flow discipline — the money must land before cutoff, in the right currency, every cycle — and agree in advance how off-cycle items like a mid-month correction or a final pay are handled. Agree, too, on the system of record for leave balances, expenses, and compensation history, so client and EOR are not reconciling two versions of the same employee at year end.

Formal changes and termination

Compensation changes, discipline, accommodations, complaints, and termination combine accurate client facts with an EOR-led local process, and the combination only works when both halves show up. The client cannot bypass the EOR on formal employment decisions: a dismissal executed outside the local procedure is the classic failure, and it can convert a manageable exit into a dispute. The EOR, in turn, cannot act soundly on facts it never received or received late, so a documentation habit on the client side (what happened, when, who was told) is the raw material every formal step consumes.

Plan the exit at the start. Notice periods, severance exposure, and lawful-grounds requirements vary widely by country, and they are knowable at hire time — ask the EOR to walk you through the realistic termination path for this role in this country before you sign, not when you need it. Keep the terms distinct when you ask, because notice, severance, and any additional statutory payment are separate obligations that can all apply at once. The definitions below set them out. One caution on vocabulary: terms like "joint employer" or "co-employment" carry specific legal meanings that differ by jurisdiction, so describe the split by task, as the matrix does, rather than reaching for a universal label.

Terms that mean different things in different countries

Six terms do most of the work in an EOR conversation, and each of them means something different depending on where the worker is. Settle the definitions before you settle the terms.

• Notice. The warning period the law or the contract requires before employment ends. It is a period, not a payment, and its length is set nationally and often by collective agreement on top.
• Severance. A payment obligation arising on termination, set by statute, collective agreement, or contract. Notice and severance can both apply to the same exit and are calculated separately.
• Statutory termination pay. An additional payment some countries require on their own conditions, over and above notice and severance. Ask whether the destination country has one before you model the cost of an exit.
• 13th-month pay. An extra month of pay required by statute in some countries and customary in others. Where it is statutory it is part of employer cost, not a discretionary bonus.
• Collective bargaining agreement. An agreement between an employer or employers' association and a trade union setting terms for the workers it covers. Where one reaches your role or sector it can raise pay, lengthen notice, or add benefits above the statutory floor, whoever the formal employer is.
• Dependent agent. In tax treaties following the OECD model convention, a person acting in a country on a company's behalf who habitually concludes contracts there, or habitually plays the principal role leading to contracts the company then concludes without material change. That pattern can create a taxable presence for the company even though someone else formally employs the person, which is why a senior commercial hire raises the tax question the next section opens with. The applicable treaty and the country's own law govern.

What an EOR does not solve

This is the section vendor explainers keep short. An EOR administers an employment relationship. Several risk domains sit partly or wholly outside that administration, and they need their own analysis on their own timetable. Hold the six do-not-assumes:

Do not assume:

1. An EOR does not make your company invisible to tax authorities or erase permanent-establishment analysis created by your activities, authority, or local presence.
2. An EOR does not guarantee work authorization or visa sponsorship; country and worker facts control.
3. An EOR does not erase works-council, collective-bargaining, sector, workplace-safety, or employee-representation duties where they apply.
4. An EOR does not remove data-transfer, security, confidentiality, or IP implementation work.
5. An EOR does not validate an employee-versus-contractor decision or cure past misclassification.
6. An EOR does not replace the client's responsibility for lawful management, accurate payroll inputs, business conduct, or a workable exit plan.

Permanent establishment and corporate tax

Corporate tax and permanent establishment come first because they are the most commonly misunderstood. A permanent establishment is a taxable presence a company can create in a country through its own activities there, assessed under that country's rules and any applicable treaty. Whether your company's presence in a country becomes taxable there turns on what the company actually does — sales activity, authority to conclude contracts, senior decision-making, a fixed place of business — not on who signs the employment contract. A quietly instructive test: if the hire's job description includes closing local deals or leading local operations, the tax question exists whether or not an EOR is involved. Escalate to a qualified tax adviser when the role goes beyond ordinary remote work, and treat that analysis as parallel to, not replaced by, the hiring decision.

Immigration, works councils, and collective agreements

Immigration is a worker-specific gate. Whether someone may lawfully work in a country depends on their nationality, status, and the national rules of that country, and provider sponsorship support — where it exists at all — varies by country, case, and entity model. If authorization is not already clearly in place, get immigration advice before setting a start date, and treat a provider's "immigration support" claim as a scope to verify, not a promise.

Collective and sector rules can also reach the arrangement. Works councils — employee-representation bodies with consultation or information rights where local law provides for them — along with collective agreements, other forms of employee representation, workplace-safety duties, and regulated-role requirements apply where local law applies them, and a standard cross-border EOR workflow does not automatically account for a sector overlay. Ask specifically whether any apply to this role in this country, and who — client or EOR — carries each resulting duty in practice.

Data protection, intellectual property, and classification

Data protection and intellectual property need implementation, not assumption. Employee data will flow between worker, EOR, and client, and employer-side obligations — under the EU's GDPR framework, for example — attach to how that data is collected, transferred, and secured. Confidentiality and IP assignment must run through an unbroken contractual chain from worker to employing entity to client; verify the chain in the actual documents — the local employment contract and the service agreement — rather than assuming the platform handles it, because an invention assigned to nobody is a problem discovered at the worst possible time.

Classification is the boundary that follows you, and misclassification means treating someone as an independent contractor when the destination country's rules would treat the relationship as employment. Whether someone is an employee or a contractor is decided by jurisdiction-specific tests applied to the real relationship, and the frameworks differ in structure rather than merely in detail. In the United States, the IRS looks at the facts of control and independence rather than the paperwork. In the United Kingdom, the law recognizes a third status between employee and self-employed — the "worker" — carrying its own set of rights, with courts and tribunals making the final determination. Neither test travels. Moving a previously misclassified contractor onto an EOR changes the future arrangement; it does not automatically settle what already happened. If there is a history, take the contractor classification risk question to qualified counsel in that jurisdiction before assuming it is closed.

Finally, the ordinary duties of being the business remain yours: lawful and consistent management, accurate and timely payroll inputs, honest business conduct in the market, and an exit plan that works. None of this makes the model unusable. It makes the model what it is — an administration structure that removes a defined set of burdens while your company keeps running, and answering for, the business around it.

When an EOR fits and when it does not

Fit is qualitative at this stage; the numbers come later, on their own page. What the model rewards is a specific shape of situation, and what it punishes is using it past that shape.

An EOR often fits when:

• You need one or a few employees in the country, not a workforce.
• Market duration is uncertain, or you need a near-term start.
• You have no suitable local entity and no independent reason to create one yet.
• The role is an ordinary employee role without heavy regulatory overlay.
• A provider verifiably supports the country, the role, and the workflow you need.
• You accept a recurring service fee and a shared, process-driven way of working.

Read that list as a description of what you are buying: flexibility. The arrangement lets you employ lawfully without building local infrastructure, start quickly, and leave cleanly if the market test fails. You pay for that optionality through recurring fees and a process you share with a provider rather than control outright.

Test another path when:

• Headcount and duration point to a durable, scaled operation.
• You are building local revenue, contracts, or broader commercial presence.
• You need direct control of benefits design, policies, or employment terms.
• Provider restrictions exclude the role, sector, worker type, or contract form.
• The activity is regulated, or the immigration picture is complex.
• Acquisitions, local licensing, or equity plans are in view.
• The termination or transfer path a provider offers is poor or unclear.
• The full cash requirement — salary, employer contributions, benefits, fees, and any deposit — exceeds what the role is budgeted for, in which case the honest answers are a different country, a different level of role, or not yet.

None of those rows forbids an EOR — companies knowingly run scaled EOR headcount for their own reasons — but each one raises the price of the trade. Durable operations turn recurring fees into a permanent tax on flexibility you no longer need; local revenue and authority push the tax and permanent-establishment questions to the front regardless of hiring structure; and control needs collide with the reality that employment terms sit with the formal employer's process. A small headcount does not automatically make an EOR lawful or optimal, and a large one does not automatically require an entity — the lists are direction, not verdict.

A practical way to run the test: write the one-page fact sheet the gate card asked for, mark which rows of each list apply, and give every applicable "test another path" row a named owner and a date. A row like "complex immigration" or "regulated activity" is not a reason to abandon the model; it is a workstream that must close before the model can carry your hire.

The honest way to hold the decision is as a standing question rather than a one-time choice. Re-run it when any of these switching triggers appears:

• Headcount is growing and cumulative fees with it.
• The local operation has settled into a long-term one.
• You need registrations or licences in your own name.
• The employee-experience limits are ones you cannot fix through a provider.
• A service-agreement renewal is due.
• The provider shows signs of exit risk.

Any one of them is a prompt to re-run the structural decision rather than renew by default. The break-even and control analysis lives in EOR versus opening an entity.

Scenario: one hire, uncertain market. A company with no entity in the destination country wants to employ one account manager there for a market test. The role is ordinary, work authorization is already confirmed, the horizon is one to two years, and standard statutory benefits are acceptable. An EOR is a plausible path — pending verification of the country's rules, the provider's employing entity, and the agreement's funding and exit terms.

EOR alternatives and how they differ

An EOR is one of several structures, and the names get collapsed into each other constantly, partly because providers sell more than one of these services under one brand, and partly because the terms genuinely mean different things in different countries. The table separates them at the decision boundary; the dedicated comparison pages own the depth.

Structure	What it is	Who is the legal employer	Decision boundary	Compare in depth
Your own local entity (direct employment)	You form or register locally and employ directly	You, through your local entity	Strongest control and permanence; requires setup, registrations, governance, and ongoing filings and compliance	EOR versus opening an entity
Employer of record	A third-party local employer hires the worker on your behalf and administers agreed employment duties, while you direct the day-to-day work	The provider's local employing entity, for the covered arrangement	Fits where you have no local entity, headcount is small, and the horizon is uncertain; the employing entity and its operating model are the facts everything else rests on	EOR Verification Card
PEO (often described as co-employment)	Generally supports or assumes a client employing entity; terminology and legal effect vary by country	Typically you (model varies by country)	If you lack an entity, most PEO models do not apply	EOR vs PEO
Payroll-only provider	Processes payroll and filings; is not necessarily the legal employer	You, through your local entity	You still need an employing entity and registrations of your own	Weigh it alongside the entity and PEO comparisons above
Independent contractor	A business-to-business relationship, not employment	No employer — a business-to-business relationship	Lawful only where the working reality satisfies the applicable country's classification rules; the label is not enough	Contractor classification risk
Staffing or temporary agency	Supplies labor under a distinct commercial and regulatory model, often licensed and sector-bound	The agency, under its own regulatory model	Built for temporary supply, not for your long-term hire; not interchangeable with an EOR arrangement	Specialist procurement and legal review

The same six structures differ again on what they leave you holding. Setup time is deliberately absent below: it is country-specific enough that any general figure would mislead.

Structure	Cost basis	What you still carry	Termination exposure	Trigger to reassess
Your own local entity (direct employment)	Formation, governance, filings, and ongoing compliance, plus salary and statutory employer costs paid directly	Every employer obligation in that country, from registrations and filings to employment terms and payroll	Yours in full, under that country's rules	The cost of maintaining the entity outweighs the control it buys, or you leave the market
Employer of record	A recurring per-employee service fee, on top of salary, statutory employer costs, benefits, and any deposit or one-time charges	Lawful management, accurate payroll inputs, tax and permanent-establishment analysis, the IP chain, data purposes, and classification history	You decide and fund it; the formal process runs through the legal employer under local rules	Any of the switching triggers above — headcount, duration, local revenue, control needs, or a weak transfer path
PEO (often described as co-employment)	A service fee on top of your own entity's running costs	Your entity's obligations, plus whatever the arrangement leaves with you as legal employer	Typically yours, as the legal employer	The model's local effect changes, or the entity is no longer the right base
Payroll-only provider	A processing fee on top of your own entity's running costs	Every employer obligation except the processing itself	Yours in full	You need employment administration rather than payroll alone
Independent contractor	Invoiced fees, with no employer contributions where the classification genuinely holds	The classification decision and its consequences under that country's rules	Contract termination rather than dismissal — unless the classification was wrong all along	The working reality starts to look like employment
Staffing or temporary agency	An agency margin on top of the cost of the assignment	Your duties as the user business under the applicable regulatory model	Sits with the agency under its own model	The need is a permanent role rather than temporary supply

Both tables are an editorial framework for orienting the decision, not a statement of law. Terminology, legal effect, and availability vary by country: verify each row against the destination country's rules before relying on it.

The map is easiest to use as a sequence of questions rather than a menu. First: is this relationship employment or genuinely independent business, under the destination country's rules? That answer is made by the facts, not chosen. Second, if it is employment: does an employing entity of yours exist or belong in that country? If yes, direct employment — supported by payroll or PEO-style services as needed — is the natural frame; if no, the EOR conversation begins. Only after those two answers does provider selection mean anything.

Two clarifications keep the map honest. Contractor-management platforms — including "agent of record" services, a label providers use for contracting with and paying independent businesses on your behalf — help you contract, invoice, and pay independent businesses; they are not EORs, and using one does not make an employment-shaped relationship lawful as a contractor arrangement. And no structure on this list is a classification device: the employee-versus-contractor question is answered by the destination country's rules applied to the facts, whichever platform processes the payments.

Scenario: the operation has taken root. Two years on, the same company has five employees in the country, local customers and contracts, and a country lead with authority to negotiate. Those facts point beyond a hiring structure: entity and tax and permanent-establishment analysis should come before renewing an EOR-only arrangement, because the company's local activity — not its hiring paperwork — now drives the risk picture.

Which structure fits which situation

Situations are defined here by footprint and constraint together, because either one alone points the wrong way: a single hire in a regulated sector and a single hire in an ordinary role are not the same decision. Find the row closest to yours, and note that two of them do not end in a hiring structure at all.

Situation	Best-fit structure	Why	Not ideal when	Residual risk to manage	Next action
First international hire, market test: one country, one to three employees, one to two years	Employer of record	No entity exists and none is yet justified; what you are buying is the option to leave	The model is licensed or restricted in that country, or the role carries a regulatory overlay	Permanent establishment created by the role's own activity; work authorization; the IP chain in the local contract	Work the fact table at the top of this page, then the first three fields of the verification card
Cost-constrained hire: one or two countries, small headcount	Employer of record, if the full cash requirement clears the budget	The country, not the provider, sets most of the budget, so the fee is the wrong place to start	The full cash requirement exceeds what the role is budgeted for	Deposits and prefunding as cash flow rather than expense; FX treatment; refundable against nonrefundable	Price the full cash requirement before shortlisting anyone
Scaling with a mixed workforce: several countries, employees alongside contractors	Employer of record now, entity assessment running in parallel	Consistency and one accountable escalation path matter more than per-hire speed at this size	Local revenue, contracts, and contracting authority are building in one country	Classification history from the contractor population; operating model per country; who owns an escalation across a partner chain	Get the employing entity named per country in writing; open the classification review separately
Prior contractor relationship, exposure suspected: any footprint	None yet: qualified counsel first	Conversion changes the future arrangement and does not settle what already happened	Always: a vendor demo is not the first move here	Accrued liability under the destination country's rules; jurisdiction-specific consequences	Read contractor classification risk, then take the history to counsel in that jurisdiction
Durable local operation, entity in view: one country, growing headcount, local revenue	Your own local entity, direct employment	Recurring fees become a standing charge for flexibility the operation no longer needs	Headcount and duration are still genuinely uncertain	Continuity of employment on transfer; two notice clocks; accrued liability funded at exit	Run the break-even at EOR versus opening an entity, and ask your current provider for transfer terms now rather than later
Acquired team or single senior hire in a new market	Employer of record, with continuity and equity terms documented before signature	Continuity of service is a question rather than an assumption, and a senior commercial role raises the tax question by itself	The provider will not commit continuity or equity treatment in writing before contract	Service length and accrued rights carrying across; equity treatment; dependent-agent exposure for a commercial role	Request written continuity and equity terms, and open a parallel tax-adviser track

Two rows deserve their own note. The classification row is the only one where the correct first move is a lawyer rather than a structure, and it stays that way until the history is assessed. The budget row is the one buyers most want to argue with: where the full cash requirement genuinely does not fit, no provider choice fixes it.

What to verify before choosing an EOR

Once the structure points to an EOR, evaluation is a verification exercise, and the fields below are the EOR Verification Card — nine fields, reused later as your per-provider scorecard. Put the same questions to every provider, insist on written answers, and note where the answer lives — the service agreement, the quote breakdown, the data-processing agreement, a per-country confirmation — so you can hold the provider to a document rather than a call.

• Country and employing entity. Which local legal entity will employ your worker in each country, and is the operating model direct, partner, mixed, or undisclosed there? Get it in writing, per country, and ask what changes if the model changes mid-contract. This is the single fact the rest of the arrangement stands on.
• Scope and exclusions. Which worker types, roles, regions, immigration cases, benefits, and contract forms are excluded or restricted? Exclusions surface late by default; force them early.
• Full cash requirement. Salary, statutory employer costs, benefits, the service fee, setup and one-time charges, deposits or prefunding, FX treatment, and any service taxes — separated, with refundable cash requirements distinguished from nonrefundable fees. The full EOR cost and quote inputs guide shows what a complete quote contains.
• Workflow and deadlines. Payroll cutoffs, funding deadlines, onboarding prerequisites and their realistic timeline, change workflows, and termination lead times. Vendor-stated onboarding times are conditional claims, not guarantees.
• The agreement itself. Indemnities, liability limits, client obligations, notice and refund terms, and transfer or exit rights — read for what happens when something goes wrong, not just when it goes right.
• Support and escalation. Channels, hours, and who owns an issue end to end — especially across a partner model, where two companies sit between you and the worker.
• Data and security. The data-processing agreement, subprocessors, cross-border transfer mechanics, and any certification's actual scope and date — a badge on a website proves neither.
• Employee experience. How the worker will actually experience onboarding, payslips, leave, benefits, expenses, support, and offboarding. Ask to see it from the employee side, not just the admin dashboard.
• Exit. How termination, transfer to your own entity, or a provider switch works in practice, what it costs and takes in lead time, and how the worker's continuity of employment — whether service length and accrued rights carry over — is handled. A structure you cannot leave cleanly is a structure you do not control.

Hold every answer to an evidence standard. Where a provider will not or cannot document a field, record it as not publicly disclosed or quote required rather than assuming the favorable reading — undisclosed is an answer, and it belongs in your comparison as one. Then compare on identical inputs: the same country, salary, currency, benefits, start date, headcount, and term. A quote comparison only means something when the inputs match, and a headline fee is not a total cost. This page deliberately recommends no provider; ranking belongs where methodology, symmetric evidence, and disqualifiers can be shown.

Choosing a provider at a glance

This page names no provider, deliberately: named picks belong on the methodology-led shortlist, where inclusion gates, symmetric evidence, and a disqualifier for every option can be shown. This section follows the structure matrix for a reason: provider selection is the second-order question, and it only becomes real once a row above has pointed you to an EOR. What this page can give you is the shortlist architecture: which provider profile fits which buyer situation, and what to ask before believing anything.

Buyer situation	Shortlist move	Ask in the demo
Startup: one to three hires, one or two countries, uncertain horizon	Two or three providers confirming an owned entity in each target country, with published, itemized pricing	Which entity employs in this country? What is the full first-year cash requirement, itemized? What are funding cutoffs — and what happens if we miss one?
Cost-sensitive hiring in one or two countries	Providers that publish list fees and one-time charges rather than quoting only — you cannot compare what you cannot see	Which charges recur and which are one-time? What is refundable and what is not? What moves the price up in this country?
Scaling company: several countries, employees plus contractors	Providers documenting both product lines, with the same operating-model disclosure for every country	Which countries run on partners? Who owns an escalation end to end? How do contractor conversions work — and what do they not fix?
Regulated sector or sponsorship-dependent hire	Providers that will state support for this role and immigration case in writing before quoting	Have you handled this case type in this country? What is excluded? Who carries the sector-specific duties day to day?
Entity transfer planned	Providers whose contract shows exit and transfer terms up front	What does transfer to our own entity cost and require? What notice binds us? What happens to employee data at exit?
Acquired team or single senior hire in a new market	Providers that will document continuity terms, equity handling, and bulk or executive onboarding for your exact case, in writing before quoting	How does continuity of employment work for transferred staff? How is equity handled here? What comparable case have you run in this country?

A provider that answers in writing before the contract is telling you how it will behave after it.

Frequently asked questions

Is the EOR or the client the worker's employer?

Under the local employment contract, the EOR's employing entity is typically the formal legal employer for the covered arrangement, and the worker's statutory rights run against that entity. But labels are not the whole story: some jurisdictions examine the real working facts when disputes arise, so confirm the named entity and how the destination country treats the arrangement.

Can an EOR hire someone in any country?

No. Availability depends on the provider's structure and the destination country's rules, and some roles, sectors, worker types, or contract forms may be excluded. In some countries the model itself is licensed, registered, or restricted — see where the model itself is restricted for verified examples and the questions that follow from them. Work authorization is a separate, worker-specific question that no provider can waive. Confirm country availability, the employing entity, and any exclusions in writing before committing.

Does using an EOR create permanent-establishment or tax risk?

Using an EOR does not settle the question either way. Permanent-establishment exposure turns on what your company actually does in the country — activities, contracting authority, presence — not on who signs the employment contract. Treat tax analysis as a parallel workstream, and involve a qualified tax adviser when local activity goes beyond ordinary remote work.

Can a contractor be moved to an EOR?

Often, operationally: many providers support converting a contractor to an employee. But conversion changes the future, not the past — it does not automatically cure earlier misclassification exposure, and the consequences are jurisdiction-specific. Review the history with qualified counsel before or alongside the conversion, especially where the prior relationship already looked like employment.

How long does hiring through an EOR take?

There is no universal timeline, and any advertised one is conditional. Onboarding commonly runs from days to a few weeks, because the clock is set by the slowest dependency: the local contract and required documents, employer and employee registrations, first payroll funding, and — where it applies — work authorization, which can extend matters substantially. A provider can commit to a date only once those dependencies are known.

How much does an EOR cost?

The service fee is one component, not the answer. Providers price EOR service per employee per month; some publish a list fee and some quote only, and a published fee can still vary with billing term, headcount, or country. Whatever the fee, it is not the total cost — salary, statutory employer costs, benefits, deposits or prefunding, FX, and one-time charges sit on top of it. The EOR pricing guide carries the dated fee breakdown and what each component means; compare figures only on identical inputs.

Your next step

Country and worker facts come first, because they decide which structures are lawful and workable. An EOR is a hiring structure that administers a defined employment scope. It is not a universal risk waiver, and the six do-not-assumes above, from tax and immigration to data, IP, and classification, keep their own owners. Providers come last. Split the work by owner: HR assembles the fact sheet and checklist answers, finance builds the funding-calendar and full-cash view, and legal takes the classification and permanent-establishment tracks in parallel.

So gather the facts now: the worker's country and location, intended status, work authorization, your entity position, salary and benefits, timing, and the exit you would want. Then work through the EOR Verification Card. When the structure is settled, compare EOR providers against those same fields, in writing, on identical inputs. If a classification history or a permanent-establishment question surfaced along the way, route it to qualified counsel or a tax adviser in parallel; those tracks should inform provider selection, not wait for it.

This page is general information for planning, not legal, tax, or immigration advice for a specific case.

How this page is maintained. EOR Hub is an independent editorial publisher. It is not an employer of record, a PEO, a payroll processor, an employment agency, a law firm, or a tax or immigration adviser. Provider inclusion, ordering, and description follow buyer fit and evidence, never a commercial relationship; where a commercial relationship exists it is disclosed for that provider. Country-law and licensing statements here are taken from the governing statute, ministry, or authority rather than from any provider's country guide, and a provider fact is stated only where that provider's own current documentation supports it. Country-law and licensing sources on this page are rechecked at least semiannually and on any known legal change, and provider-facing sources at least quarterly and before publication.

Sources and last verified date

Last verified: August 1, 2026

Next review: November 1, 2026

Where a source line carries its own checked date, that date is the most recent review of that source.

• General employment terms and conditions in the EU — Your Europe, European Union — EU-level orientation showing that employment terms are governed by national rules within EU minimum standards; supports the country-first gate.
• Registering as an employer and registering employees in another EU country — Your Europe, European Union — supports the statement that the local employer must register with local authorities and register employees in the country of work (checked August 1, 2026).
• Paying social security contributions — Your Europe, European Union — supports the statement that employer social-security contributions are typically owed in the country where the employee works (checked August 1, 2026).
• Regulation (EC) No 883/2004 on the coordination of social security systems — EUR-Lex, European Union — the governing instrument behind that rule, and the source of the posted-worker exception (checked August 1, 2026).
• Work permits — Your Europe, European Union — supports the statement that work authorization depends on nationality, status, and national rules.
• Data protection under GDPR — Your Europe, European Union — supports the employer-side data-protection and cross-border data-handling boundary.
• Model Tax Convention on Income and on Capital: Condensed Version 2017 — OECD — the model convention on which many bilateral tax treaties are based; supports the definition of the dependent-agent test used in the terms section (text as it read on 21 November 2017; checked August 1, 2026).
• Independent contractor (self-employed) or employee? — Internal Revenue Service — U.S. example that classification depends on the facts of control and independence; cited as one jurisdiction's test, not a global standard (checked August 1, 2026).
• Employment status: overview — GOV.UK, United Kingdom — supports the statement that UK law recognizes a "worker" status between employee and self-employed, with courts and tribunals making the final determination (checked August 1, 2026).
• Arbeitnehmerüberlassung (labor leasing) — Bundesagentur für Arbeit, Germany — supports the statement that hiring out employees to another company in Germany generally requires a licence from the Federal Employment Agency under the AÜG, with a notification sufficing in defined cases (checked August 1, 2026).
• § 1 Arbeitnehmerüberlassungsgesetz (AÜG) — Gesetze im Internet, Germany — consolidated statutory text; supports the licence requirement and the 18-consecutive-month cap on a single assignment under § 1(1b), including the three-month counting rule and the collective-agreement variation (checked August 1, 2026).
• Fachliche Weisungen Arbeitnehmerüberlassungsgesetz — Bundesagentur für Arbeit, Germany — the agency's current administrative guidance on the AÜG, cited for the effective date of the guidance applied to the German row (valid from July 1, 2026; checked August 1, 2026).
• Article L8241-1, Code du travail — Légifrance, France — supports the statement that operations for profit whose exclusive object is the supply of workers are prohibited in France outside listed frameworks, including licensed temporary work (checked August 1, 2026).
• Hiring and posting staff: Waadi registration and Waadi check — Business.gov.nl, Netherlands — supports the Waadi Business Register requirement for businesses supplying workers, including foreign businesses without a Dutch branch (checked August 1, 2026).
• Wet toelating terbeschikkingstelling van arbeidskrachten (Wtta) — Nederlandse Arbeidsinspectie, Netherlands — supports the Dutch admission system for lenders, the role of the Nederlandse Autoriteit Uitleenmarkt in assessing admissions and keeping the public register, and the phased dates including the restriction on hirers from 1 January 2028 (checked August 1, 2026).
• Employer of Record (EOR) glossary — Deel — first-party example of how providers describe typical EOR service scope; cited as a vendor statement, not governing authority (checked August 1, 2026).
• Employer of record (EOR) — HR glossary, Remote — second first-party example of how providers describe typical EOR service scope; cited as a vendor statement, not governing authority (checked August 1, 2026).