EOR vs. PEO: Key Differences and How to Choose

If your company needs to employ someone in a country where it has no legal entity, an employer of record (EOR) is usually the relevant model: the EOR arrangement supplies a local legal employer, while your company directs the day-to-day work. If your company already employs people through its own eligible entity — most commonly in the United States — and wants to share payroll, benefits, and HR administration with a service provider, a professional employer organization (PEO) is usually the relevant model. The two are not interchangeable, and the popular shorthand "PEO is domestic, EOR is global" is an orientation, not an operating rule. The decision turns on two facts before anything else: where the worker will physically work, and which entity can lawfully sign the employment contract there. Some situations call for neither model until a classification, immigration, entity, or country-licensing question is resolved first.

Before you request a single quote, write down the worker's country, the proposed employing entity, employment status, target start date, gross salary and currency, benefits expectations, and any immigration need. Comparable answers require comparable inputs. If a start date is already committed, the constraint that usually binds is work authorization or a statutory pre-start step rather than a provider's onboarding speed — see what actually sets the start date. This guide uses the U.S. PEO and CPEO framework as its clearest regulated reference point, and treats "EOR" as a commercial service label whose exact obligations depend on local law and the service agreement.

Keep this in view from the start: neither an EOR nor a PEO automatically removes permanent-establishment, corporate or employment tax, immigration, works-council or employee-representation, data-protection, intellectual-property, or worker-classification risk. These are separate legal domains. A service arrangement can administer defined parts of them; it does not make them disappear.

Two colleagues reviewing a document together at a shared desk, unlabeled desk globe behind them

On this page

Which model should you choose?

The verdict is conditional, and it is best stated as three fit rules rather than a single winner.

Fit ruleChoose an EORChoose a PEOChoose neither yet
Best forEmploying a worker in a country where you have no suitable employing entity, and a provider can legally support the role and jurisdiction.A company that already employs workers through its own eligible entity — typically in the U.S. — and wants shared payroll, benefits, HR administration, workers' compensation, or risk support.Situations with an unresolved threshold issue: worker classification, immigration or work authorization, a regulated role, permanent-establishment exposure, or entity economics.
Not ideal whenYou already have an eligible employing entity in the worker's jurisdiction and mainly need administration — you would be paying for a legal-employer structure you may not need.You have no entity or registration in the worker's jurisdiction — a U.S.-style PEO arrangement generally cannot employ where you cannot.The temptation is to pick a vendor to make the threshold problem disappear. A service label does not resolve a legal-status question.
First checkConfirm the provider supports the specific country, role, and worker, and identify which entity would actually be the legal employer.Confirm your entity's registrations, which responsibilities the service agreement allocates, and whether IRS CPEO certification matters to you.Name the blocking issue and route it to the right analysis: classification, immigration, tax, or an entity comparison.

The three stakeholders in this decision are usually answering different questions. HR is asking who can lawfully employ this person and when they can realistically start; finance is asking what the fully loaded cost is and what being wrong would cost; legal is asking what the service agreement actually allocates and whether any threshold question is still open. Where those answers point in different directions, the legal one gates the others.

The four-question gate

Answer these before comparing any providers:

  1. Where will the worker physically work? Country and, where relevant, state, province, or city.
  2. Does your company have an entity eligible to employ there, including the registrations that employment would require?
  3. Will the person be an employee, or is independent-contractor status genuinely supportable under that jurisdiction's rules?
  4. Is there a threshold issue to resolve first — immigration or work authorization, a licensed or regulated role, whether the target country licenses or restricts the arrangement itself, or a permanent-establishment or entity-strategy question?

The answers map cleanly: no eligible entity plus an employee hire and no threshold blockers points to evaluating an EOR; an eligible entity plus a need for shared administration points to evaluating a PEO; any unresolved answer to questions three or four means the model choice waits.

Seven criteria decide the rest — which entity is the legal employer, whether you have an eligible entity where the worker will be, whether the model is even permitted in that country, the full set of cost categories rather than the service fee alone, speed measured against the legal gate rather than the sales pitch, control and support scope, and the exit path when the facts change. The sections below take them in that order.

What an EOR and a PEO actually are

Employer of record

An employer of record is a service arrangement in which a local employing entity hires the worker under an employment contract governed by local law, while your company — the client — directs the day-to-day work: tasks, priorities, performance, and the commercial relationship. The client does not vanish from the picture. It retains operational control, and with it a set of responsibilities that no contract can fully transfer, from workplace conduct to business decisions. "EOR" is not a single legal category anywhere; it is a commercial label, and the exact allocation of obligations depends on the country, the provider, and the signed agreement. For the full operating mechanics, see how an employer of record works.

One boundary deserves emphasis because it drives most confusion: who counts as the employer can differ by legal purpose. The entity named as employer for payroll and social-security administration is not automatically the only entity a court, tax authority, or labor inspector would treat as an employer for dismissal protection, discrimination claims, benefits, or tax questions. The governing law and the contract control, not the label on the invoice.

A second boundary sits underneath every country list. An owned entity is a local company the provider itself controls and employs through. An in-country partner model is one where a third-party local firm holds the employment relationship and the provider intermediates. A mixed model uses each in different markets. The distinction changes the liability chain, who holds any license the country requires, and who is left standing if the relationship ends badly — and providers frequently do not publish which model applies in which market, in which case the honest status is operating model not verified.

Three related terms recur below and are worth fixing in place. Permanent establishment is a tax concept: a taxable presence that a company can create in a country through its own activities there, such as sales, contracting, or management, independently of how any individual worker is employed. A dependent agent is the treaty concept most often used to test for that presence — broadly, a person acting on the company's behalf who habitually plays the principal role in concluding contracts there; the exact wording and threshold vary by treaty, which is why permanent-establishment exposure usually turns on what your own people do commercially in a country rather than on how a worker is employed. Misclassification is treating someone as an independent contractor when the governing jurisdiction's tests would treat the relationship as employment. Continuity of employment is the preservation of a worker's accrued service, and the rights that attach to it, when employment moves from one employer to another.

Four more travel together and are routinely merged in quotes and vendor pages, at a cost. Notice is the warning period the law or the contract requires before employment ends, and it can usually be worked or paid. Severance is compensation payable on certain terminations, typically calculated from service and pay. Statutory termination pay is any further sum the governing law fixes for the way the employment ended, separately from notice and severance. A probation period is an initial stretch of employment during which notice or dismissal protection is reduced; in many countries its maximum length and effect are set by statute or by a collective agreement rather than left to the contract, so a longer probation written into a template is not enforceable merely because both parties signed it. Which of these apply, in what combination, and on what formula is a country question, and the answer rarely resembles the U.S. one.

Professional employer organization and co-employment

A professional employer organization, in the U.S. market where the term has its clearest meaning, is a co-employment arrangement. The client keeps employing workers through its own entity and registrations, and the PEO takes on an allocated set of responsibilities under the service agreement: typically payroll processing, employment-tax filings, access to the PEO's benefits plans, workers' compensation program administration, and HR support. Co-employment allocates duties between two parties; it is not a mechanism for outsourcing every employer obligation. Terminology and legal effect vary by state, and outside the United States other legal systems regulate staffing and labor-leasing arrangements under their own distinct rules, so the U.S. meaning should not be exported unexamined.

An ASO, or administrative services organization, sits one step below a PEO: it processes payroll and administers HR tasks without entering a co-employment relationship. A payroll-only provider is narrower still. An AOR, or agency of record, is a fourth commercial label, used for services that contract with and pay independent contractors rather than employees; like "EOR," it is a market term rather than a legal category, and engaging one does not settle whether the relationship is employment under local law. None of these becomes the legal employer.

Certified PEO: what IRS certification does and does not buy

A certified PEO (CPEO) is a specific federal-tax construct. Under 26 U.S.C. § 7705, a PEO can apply for IRS certification, which requires among other things a bond, annual audited financial statements, and quarterly assertions and examination-level attestations regarding federal employment tax payments. The certified organization's written service contract must provide that the CPEO assumes responsibility for paying wages, for reporting, withholding, and paying federal employment taxes on those wages, and for any employee benefits the contract requires it to provide — regardless of whether the customer pays the CPEO — and that it assumes recruiting, hiring, and firing responsibility in addition to the customer's own (§ 7705(e)(2)). Under 26 U.S.C. § 3511, a CPEO is then treated as the employer for federal employment-tax purposes of covered work-site employees, but only with respect to the remuneration the CPEO itself remits.

The limits matter as much as the treatment, and four of them decide real cases.

The treatment is confined to federal employment taxes. Section 7705(g) provides that, except to the extent necessary for purposes of § 3511, nothing in that section affects the determination of who is an employee or employer for purposes of Title 26. The implementing regulation, 26 C.F.R. § 31.3511-1, confirms the scope: for a covered employee who is not a work-site employee, a person other than the CPEO is also treated as an employer for federal employment taxes on CPEO-remitted pay. Specified federal wage credits stay with the customer, not the CPEO (§ 3511(d)). Certification is a meaningful financial-assurance and tax-administration signal; it is not a general employment-law shield, and state law and the contract can add or change obligations. The related definitions and contract requirements are detailed in 26 C.F.R. § 301.7705-1.

Whether your people are work-site employees depends on an 85% test. The exclusive treatment under § 3511(a)(1) applies to work-site employees, and § 7705(e)(3) provides that an individual meets that requirement only if at least 85% of the individuals performing services for the customer at that work site are covered by qualifying CPEO contracts, disregarding excluded employees within the meaning of § 414(q)(5). A company that puts part of one office on a CPEO and keeps the rest on its own payroll may not get the treatment it thinks it bought.

Owner-adjacent arrangements can fall outside the section entirely. Section 3511 does not apply where the customer bears a relationship to the CPEO described in §§ 267(b) or 707(b), applied by substituting 10% for 50%. Separately, an individual with net earnings from self-employment derived from the customer's trade or business, including a partner in a partnership that is a customer, is not a work-site employee with respect to remuneration paid by a CPEO.

Certification is verifiable in one click, and the name on the contract matters. Section 7705(f) requires the Secretary to publish the certified organizations and any suspensions or revocations. The IRS maintains that register on its CPEO public listings page, updated by the 15th day of the first month of each calendar quarter. The IRS also warns that many CPEO names are similar and one brand can represent several entities in a group, and that a CPEO contract must name the exact entity and Employer Identification Number fulfilling the federal employment-tax obligations. That is the same question this guide asks about every model: which entity, exactly, is on the paper.

The practical takeaway from all three definitions: terminology cannot replace the contract. The same provider may sell EOR, PEO, payroll-only, and contractor products under one brand. The questions that cut through the labels are always the same — which entity signs the employment contract, and which obligations does the service agreement actually allocate to whom.

EOR vs. PEO side by side

The matrix below carries the repeated comparison facts. Fields that cannot be universalized are marked verify — the answer depends on the jurisdiction, the provider, or the contract, and a blank or unknown field means "confirm," never "no."

Decision fieldEOR modelU.S.-style PEO (uncertified)Certified PEO (CPEO)
Client entity requiredNo local employing entity required from the client. The provider's entity — or, in some countries, a local partner's entity — employs. Verify which entity signs.Yes. The client generally employs through its own eligible entity and registrations in the relevant jurisdiction.Yes, same as an uncertified PEO. Certification changes federal tax treatment, not the entity requirement.
Legal employerUnder an EOR, the provider's local entity is the named employer under the employment arrangement; its effect can differ by country and legal purpose. Verify in contract and jurisdiction.Under a PEO, the client remains an employer. Responsibilities are allocated by the co-employment agreement.Under a CPEO, the client remains an employer for most purposes. For federal employment taxes on covered work-site employees, the CPEO is treated as the employer with respect to remuneration it remits.
Day-to-day directionThe client directs the work, sets duties, and manages performance.The client directs the work; the PEO supports HR processes.Same as an uncertified PEO.
Payroll and employment taxesThe EOR runs local payroll, withholds employee deductions, and remits employer contributions under local law.The PEO processes payroll and files employment taxes under the service agreement. Verify the allocation.Assumes defined federal employment-tax responsibility for covered wages under the required contract terms, regardless of customer payment.
Whose tax identity appears on filingsThe employing entity's. Where the arrangement runs inside the United States, that means the provider's Employer Identification Number and the provider as the W-2 employer. Verify per country and per entity.Yours, under your own registrations and identifiers, unless the service agreement provides otherwise. Verify the allocation.The CPEO's, for federal employment taxes on covered work-site employees and only for remuneration it remits (§ 3511). Yours for everything outside that scope.
Financial assurance behind the arrangementNone inherent to the model. Verify the provider's own financial standing and any escrow or deposit terms.None inherent to the model. Verify.Bond, annual audited financial statements, and quarterly attestations regarding federal employment tax payments, as conditions of certification.
Independent verification of statusNo public register of EOR providers. Operating model not verified until documented.No federal certification to check. State registration or licensing may apply. Verify per state.Listed on the IRS CPEO public listings page, updated quarterly, including suspensions and revocations.
BenefitsStatutory benefits attach to the local employment; supplemental plans vary by provider and country. Verify plan scope and markup treatment.Access to PEO-sponsored benefit plans is a common reason to buy; plan terms, pricing, and eligibility vary. Verify.Same commercial picture; certification does not govern plan quality or pricing.
Workers' compensation and statutory insuranceLocal statutory schemes attach to the local employment; scope varies by country.Workers' compensation program administration is frequently part of the arrangement; state rules vary. Verify.Same as an uncertified PEO.
Country eligibilityUnder an EOR, provider country lists vary, and availability does not prove an owned entity. Role and worker-type restrictions apply. Verify per country.A U.S.-style PEO arrangement is effectively limited to jurisdictions where the client entity operates and the PEO is registered or licensed — in practice, U.S. states.CPEO is a U.S. federal construct. Not a route to employing outside the United States.
Immigration boundaryA separate prerequisite. EOR availability in a country does not prove visa sponsorship is possible for a given role and worker. Verify.Not addressed by the arrangement; work authorization is a separate legal question.Not addressed by certification.
Setup dependencies and timeCountry onboarding documents, a compliant local contract, benefits enrollment, payroll cutoffs, funding, and any statutory pre-start registration. Vendor timelines are conditional. Not verified — confirm against your facts.Entity records, state registrations, benefits enrollment windows, and payroll transition, often with a parallel payroll run. Not verified — confirm.Same as an uncertified PEO, plus filing Form 8973 to notify the IRS that the contract has started.
Cost componentsUnder an EOR: gross salary, statutory employer costs, mandatory additional compensation, benefits, service fee, one-time fees, deposits or prefunding, and FX on cross-border payments.Under a PEO: gross salary, employer taxes, benefits, and a service or administration fee — commonly per employee or a percentage of payroll. Quote required.Same components as an uncertified PEO. Certification is not a pricing model. Quote required.
Minimum commitmentVaries by provider and country; minimum terms, notice periods, and per-employee minimums are common. Not publicly disclosed — quote required.Varies by agreement. Quote required.Varies by agreement. Quote required.
Support scopeEmployment lifecycle support in the supported country; scope varies by provider and contract.HR, payroll, benefits, and compliance support for a domestic workforce; scope varies by agreement.Same as an uncertified PEO.
Termination exposureUnder an EOR, local statutory notice, grounds, process, and severance attach to the local employment and are funded by the client through the arrangement. Verify how they are billed and whether a reserve or deposit is drawn.Under a PEO, termination exposure sits with the client as employer, supported by the PEO's HR and claims processes. Verify the allocation in the agreement.Same as an uncertified PEO. Certification governs employment taxes, not dismissal liability.
Exit pathLeaving an EOR: offboard the worker, or transfer employment to your own entity if you open one; notice and transfer rules apply locally.Leaving a PEO: terminate the service agreement and take payroll and benefits in-house or to another provider; plan for benefits continuity.Same as an uncertified PEO, plus a Form 8973 filing to notify the IRS that the contract has ended.
What this does not meanCountry availability is not an owned entity; the named employer is not necessarily the employer for every legal purpose; the service fee is not the total cost.Co-employment is not a transfer of every employer obligation; a PEO relationship does not create the ability to employ where you have no entity.Certification is not an employment-law shield, not a quality rating, and not a guarantee that your workers qualify as work-site employees.

The three differences that decide most cases

First, the entity gate: a PEO-style arrangement presumes you can already employ in the jurisdiction; an EOR exists precisely because you cannot, or choose not to, employ there yet. Everything else on the table is downstream of that line. Second, the employer question: under an EOR a different entity is the named local employer, while under a PEO you remain an employer with shared administration. Those are two structurally different responsibility and risk pictures, and the difference shows up hardest at termination, in disputes, and in audits. Third, what you are actually buying: an EOR sells a lawful route to employment in a country; a PEO sells shared administration and, often, benefits buying power for a workforce you already employ. Price each against its own job, which is why "EOR versus PEO pricing" comparisons so often mislead.

What to verify before signing

For an EOR agreement, confirm: which legal entity will sign the employment contract in this country, the provider's own or a local partner's; whether that entity holds any license the country requires for the arrangement, and its license number; exactly what the service fee includes and what is billed separately, including deposits, FX, off-cycle payroll, and termination handling; whether the provider supports this specific role, seniority, and worker, including any immigration need; and what happens at exit — notice, transfer-to-entity support, and final-pay treatment.

Analyst holding a certificate page beside a softly glowing monitor to verify a named employing entity

For a PEO agreement, confirm: which responsibilities the service agreement allocates to each party across payroll, tax filings, benefits, workers' compensation, and HR claims; whether the provider is an IRS-certified CPEO, checked against the exact legal entity name and EIN on the IRS listing rather than the brand; which of your workers would be covered work-site employees, given the 85% test; which state registrations and licenses it holds where your people work; and the full fee and benefits pricing, plus what happens to plans and employee data if you leave.

Where the EOR model itself is restricted

An EOR arrangement is a commercial service, but the underlying act — one entity employing a worker who performs work under another company's direction — is regulated in its own right in many countries, usually under labor-leasing, dispatch, or temporary-agency law. Where those rules apply, they can require the employing entity to hold a license or admission, prohibit the supply of labor for profit outside a defined framework, cap how long the arrangement may run, limit which roles it may cover, or penalize both the provider and the client company. Vendor comparisons rarely mention this, and it is the fastest way for a hiring plan to fail after the contract is signed.

The regimes below are widely encountered and were checked against their governing instruments for this guide, with the EU layer included because it sits beneath every member state's national rules without replacing them. Whether any particular EOR arrangement falls inside a given regime is a question of local characterization, not of what the service is called.

Country or layerWhat is regulatedRequirement or limitRegulatorGoverning instrumentStatus, evidence, and effective date
GermanyHiring out an employee to work under a third party's direction (Arbeitnehmerüberlassung)A permit is required before any assignment begins. The same worker may not be assigned to the same hirer for more than 18 consecutive months unless a collective agreement in the user industry provides otherwise. Where a temporary-work collective agreement deviates on pay, equal-pay entitlement applies after 9 months, and a longer deviation is permitted only under a sector supplement agreement that reaches equivalent pay no later than 15 months. Assignment without a permit is an administrative offense for the provider and the client company alike — and, under §§ 9 and 10, the worker's contract with the provider is void and an employment relationship with the client company is deemed to have arisen, unless the worker declares within one month that they wish to keep the contract with the provider.Bundesagentur für ArbeitArbeitnehmerüberlassungsgesetz (AÜG) § 1; § 8; §§ 9, 10 and 16; § 19 transitional rule; Federal Employment Agency guidanceVerified — governing text and the Federal Employment Agency's own guidance, July 2026 edition. The duration limit and the 9-month equal-pay rule apply as amended with effect from 1 April 2017; under § 19(2) assignment time before that date is not counted, so the 18-month cap could first bind on 1 October 2018.
FranceSupplying labor for profit (prêt de main-d'œuvre à but lucratif)An operation whose exclusive object is supplying labor for profit is prohibited outright. It is lawful only inside a listed framework, principally temporary work (travail temporaire), which may be carried on only by a temporary work undertaking; temporary-work activity outside such an undertaking is prohibited. Illicit supply of labor is punishable by two years' imprisonment and a €30,000 fine, rising to five years and €75,000 in the aggravated cases the article lists and to ten years and €100,000 where the offense is committed by an organized group. The separate offense of marchandage can attach to the same facts and carries two years and €30,000.Ministry of Labour and the labor inspectorate, with criminal enforcementCode du travail art. L. 8241-1; arts. L. 8241-1 to L. 8241-3; temporary work, arts. L. 1251-1 to L. 1251-63; penalties, arts. L. 8243-1 to L. 8243-3; marchandage, arts. L. 8231-1 and L. 8234-1Verified with limitation — the prohibition and its temporary-work exception were confirmed in the consolidated Code du travail on 1 August 2026. The penalty articles are in the version in force since 27 June 2026, as amended by Loi n° 2026-534 of 25 June 2026. Whether a particular arrangement is characterized as supplying labor for profit is decided on the facts in France, not by the service agreement.
NetherlandsMaking workers available to work under another company's direction (ter beschikking stellen van arbeidskrachten)Under the Waadi, an undertaking that makes workers available must be registered as carrying on that activity in the commercial register, and a hiring company that engages an unregistered supplier is exposed alongside the supplier. An adopted admission scheme, the Wtta, replaces that registration with a positive admission: suppliers must be admitted by a new authority, must lodge a deposit and produce a certificate of good conduct, and hirers may engage only admitted suppliers. It reaches payrolling and secondment as well as agency work, and foreign suppliers as well as Dutch ones.Netherlands Labour Authority; Nederlandse Autoriteit Uitleenmarkt under the admission schemeWtta, bill 36446 — Tweede Kamer; analysis of the adopted act and the Waadi it replacesVerified with limitation — the Waadi registration duty is current. The admission scheme was adopted in November 2025, with entry into force stated as 1 January 2027 and enforcement from 1 January 2028 in a dated professional source rather than an official text. Confirm the timetable with the authority before relying on it.
SwitzerlandHiring out employees commercially (Personalverleih)Hiring out employees within Switzerland requires an operating license from the cantonal labor office; carrying the activity across the border additionally requires a federal license from SECO, issued for named states. Article 12(2) goes further than most regimes: leasing personnel from abroad into Switzerland is not permitted. A licensed provider must also lodge a security deposit against wage claims arising from the leasing.State Secretariat for Economic Affairs (SECO), supervising the cantonal enforcement authoritiesArbeitsvermittlungsgesetz (AVG), SR 823.11 — arts. 12 and 14; SECO, private placement and personnel leasingVerified with limitation — the cantonal and federal licensing structure and SECO's supervisory role were confirmed on SECO's own current page on 1 August 2026, and the article 12(2) prohibition in the published federal text. Deposit amounts are fixed by ordinance and were not checked for this guide.
EU and EEA (supranational layer)Temporary agency work, as a floor beneath each national regimeThe German, French, and Dutch regimes above sit within the framework of EU Directive 2008/104/EC on temporary agency work. Each member state transposes it through its own instrument, with different licensing, registration, duration, and equal-treatment rules. The German answer does not transfer to Spain, Italy, or Poland; only the underlying directive does.National authority in each member stateDirective 2008/104/EC (2008), as transposed — implementation confirmed for Germany in the Federal Employment Agency guidanceVerified with limitation — the directive and the German transposition are confirmed. Transposition in member states other than those listed here was not checked for this guide. Switzerland is not an EU or EEA member and is not governed by the directive.
JapanWorker dispatching (haken)A license from the Minister of Health, Labour and Welfare is required to operate a dispatching business; dispatch into port transport, construction, security, and other services set by Cabinet Order is prohibited; assignment-duration limits apply at the receiving company's organizational-unit level.Ministry of Health, Labour and WelfareAct on Securing the Proper Operation of Worker Dispatching Businesses and Protecting Dispatched Workers, arts. 4, 5, 7, 8Verified with limitation — duration limits vary by service category and by the worker's contract type with the agency. The amendment version reflected in the official translation was not verified for this guide; confirm the current text and the specific case.
ChinaLabor dispatch (laowu paiqian)Dispatch agencies require an administrative license; a host company's dispatched workers must not exceed 10% of its total workforce; dispatch is limited to temporary, auxiliary, or substitute positions; breach is penalized against both the agency and the host company.Ministry of Human Resources and Social Security and local HRSS departmentsInterim Provisions on Labor Dispatch (MOHRSS Order No. 22), arts. 3, 4, 11; PRC Labor Contract Law, arts. 57–67 and 92 — see US-China Business Council summary and CMS China analysisVerified with limitation — Order No. 22 was promulgated in January 2014 and took effect on 1 March 2014. The cap and position limits bind the host company, and whether a given arrangement is characterized as labor dispatch is fact-specific. The instrument is named but was verified through two dated professional analyses rather than an official English text.

What the absence of a country from this table means. It means the question was not researched for this guide — not that the arrangement is unrestricted there. Jurisdictions not examined here include the United States, the United Kingdom, Ireland, Spain, Italy, Poland, India, Brazil, Mexico, and Canada, several of which regulate staffing, labor leasing, or contract labor in their own way. Treat every unlisted country as unchecked.

Germany: assign without a permit and the client can become the employer

In Germany, hiring out an employee to work under another company's direction requires a permit from the Bundesagentur für Arbeit before the assignment begins. What makes the German rule decisive for a hiring plan is the consequence rather than the requirement: under §§ 9 and 10 AÜG an unpermitted assignment voids the provider's contract with the worker and deems an employment relationship with the client company to have arisen, subject to the worker's right to declare within a month that they wish to keep the provider's contract. Ask for the permit number before the start date.

France: an operation whose only object is supplying labor for profit is prohibited

In France, an operation whose exclusive object is supplying labor for profit is prohibited outright, and is lawful only inside a listed framework — principally temporary work, which only a temporary work undertaking may carry on. The exposure is criminal rather than administrative, and it reaches the arrangement as it actually operates: whether a service is characterized as supplying labor for profit is decided on the facts by French authorities and courts, not by the description in the service agreement. A French placement therefore needs the framework identified, not just the provider named.

Netherlands: registration today, positive admission from 2027

In the Netherlands, an undertaking that makes workers available must currently be registered for that activity in the commercial register, and a hiring company that engages an unregistered supplier is exposed alongside it — so part of the duty is yours today, not the provider's alone. The adopted Wtta replaces registration with a positive admission requiring a deposit and a certificate of good conduct, and it reaches payrolling, secondment, and foreign suppliers. Confirm the commencement timetable with the authority before planning around it.

Switzerland: leasing into Switzerland from abroad is not permitted

In Switzerland, hiring out employees commercially requires a license from the cantonal labor office, and cross-border activity additionally requires a federal license from SECO. Article 12(2) of the Arbeitsvermittlungsgesetz then goes further than most regimes by not permitting personnel to be leased from abroad into Switzerland at all. The practical consequence is that a Swiss placement has to run through a Swiss-domiciled licensed entity rather than a foreign one, which makes the question "which entity holds the license, and in which canton" the first one to ask.

Japan: dispatch is licensed and some sectors are closed

In Japan, operating a worker dispatching business requires a license from the Minister of Health, Labour and Welfare, dispatch into port transport, construction, security, and other services set by Cabinet Order is prohibited outright, and duration limits apply at the receiving company's organizational-unit level. Because those limits vary by service category and by the worker's contract type with the agency, the useful question is not whether the provider is licensed but whether this role, this duration, and this sector sit inside what the license permits.

China: the cap binds you, not only the agency

In China, dispatch agencies require an administrative license, dispatch is limited to temporary, auxiliary, or substitute positions, and a host company's dispatched workers must not exceed 10% of its total workforce. The cap and the position limits bind the host company, so part of the compliance obligation is yours whatever the service agreement says, and the binding constraint is your own growth rather than the provider's paperwork. Before a second or third Chinese hire, ask how the arrangement is characterized locally and what it counts against.

How to check whether a country restricts the model

For any country not listed, the check is short and worth running before you shortlist providers. Ask which local entity would employ the worker; ask whether that entity holds a license, permit, admission, or registration for hiring out employees in that country, and for the number; ask whether any statutory cap applies to duration, headcount proportion, or role type; and ask the provider to answer in writing rather than in a call. A provider that operates lawfully will have the license number to hand.

Three consequences follow for the model choice. Where the arrangement is licensed and capped, an EOR may be a lawful bridge but not a lawful permanent structure, which moves the entity comparison forward in your plan rather than deferring it. Where a cap or a registration duty binds the client company rather than the provider, as in China and the Netherlands, compliance is partly yours no matter what the service agreement says. And where breach converts the arrangement into a direct employment relationship with your company, as under the German rule above, the failure mode is not a fine you can budget for — it is becoming the employer you engaged a provider in order not to become.

How to choose: EOR, PEO, or neither yet

Apply the gate answers as conditional rules, one branch at a time.

  • If you have no eligible entity in the worker's country — a U.S.-style PEO arrangement is generally not available for that hire. The candidate routes are an EOR, opening an entity, or, only where the status genuinely holds up under local law, a contractor engagement. Check the country against the restriction question above before you shortlist.
  • If you have your own eligible entity and want shared administration or benefits access — a PEO is the candidate, and CPEO certification is worth weighing on its own terms. If what you actually need is payroll processing alone, a payroll-only or ASO arrangement may fit better than paying for co-employment services you do not need.
  • If any threshold question is open — resolve it before shortlisting anyone. A provider decision made on top of an unresolved status question inherits the problem rather than solving it.

It helps to separate three different kinds of "no," because they look similar in a meeting and call for entirely different responses. Call them the three kinds of no, and name which one you are facing before anyone opens a vendor site.

  • Not eligible is structural. No entity means no PEO for that jurisdiction, whatever the budget says; an unsupported role or worker type means that particular EOR is out, though not necessarily the model; a restricted jurisdiction may rule out the arrangement itself. And where no provider supports the market at all, the shortlist is not short but empty, and the real options are an entity, a contractor engagement if the status genuinely holds there, or not hiring in that country yet. Structural problems are solved by changing the structure, not the vendor.
  • Not economical is comparative. The model works legally, but a different route — often an owned entity at sufficient scale — may serve the plan better on cost, control, or both. That is a modeling exercise with your numbers, not a legal one, and it deserves an actual model rather than a rule of thumb. The blunt version of the same finding is worth naming: sometimes the fully loaded cost, built from the statutory floor rather than the fee, simply exceeds what the role is worth. That is a decision to reach before the quote conversation, not after it.
  • Requires specialist review is a stop sign. An unresolved employee-versus-contractor question, an open work-authorization issue, a licensed or regulated activity, or potential permanent-establishment exposure each need qualified analysis before a service contract can responsibly be signed. If contractor status is genuinely supportable in the governing jurisdiction, you can then evaluate contractor-management options — but the platform choice follows the classification analysis, never the reverse, because software administers a relationship without making it lawful.

Match your situation to a shortlist

Your situationProvisional routeWhat to evaluate
First hire in a country with no entity; standard commercial roleEORCheck the country for licensing or dispatch restrictions, then shortlist EOR providers that support the country and role; verify the legal employer and full fee scope.
U.S. company employing through its own entity; wants benefits, payroll, and HR supportPEO or CPEOShortlist PEOs; verify responsibility allocation, state coverage, certification status against the IRS listing, the 85% work-site test, and plan terms.
Own eligible entity; needs payroll processing onlyPayroll-only / ASOVerify the contract is not selling — or charging for — co-employment services you do not need.
Testing three to five markets before any entity setupEOR, multi-countryCheck each target market for restrictions first; compare per-country operating models and exit terms rather than a single headline fee.
Single senior or executive hire, high compensation, one countryEOR, with contract-template diligenceWhether the provider's contract templates can carry the equity, bonus, and notice terms the offer needs, and whether the role is licensed or regulated locally.
Inherited or acquired team in a new marketEOR or entity, depending on transfer lawWhether local transfer rules attach, and whether a provider can take on employees with accrued service preserved. Employment counsel in that country before signing.
Eight or more people in one country, permanent operationEntity comparison firstWhether a duration or proportion cap binds at that scale, and how per-employee fees compare with entity overhead once the presence is permanent rather than exploratory.
Team concentrating in one country, or a worker currently engaged as a contractorNeither yetResolve the entity economics or the classification question first, then re-run the four-question gate.

All six routes on the same fields

Six routes can employ or engage a worker, and a comparison only holds if each is described on the same terms. The matrix above compares the three service arrangements field by field; the table below compresses all six onto the same nine fields, so any two of them can be read against each other without moving between formats. Three of the six — contractor engagement, owned entities, and payroll-only — are analyzed in full on the pages that own them, and are fielded here only at the depth needed for the comparison.

RouteWhat it isWho is the legal employerSetup gated byCost basisCompliance obligations you keepTermination exposureWhen it stops being the right answerTrigger to reassess
EORA local entity employs the worker under local law while you direct the workThe provider's local entity, or a local partner'sCountry onboarding, a compliant local contract, and any statutory pre-start stepSalary, statutory employer cost, benefits, service fee, one-time fees, deposits, FXPermanent establishment from your own activity, classification history, immigration, employee representation, IP chain, data transfersLocal statutory notice, grounds, process, and severance, funded by you through the arrangementHeadcount concentrates, a country caps duration or proportion, or templates cannot carry the termsConcentration, permanence, local commercial activity, or repeated provider refusals
PEO (U.S.-style)Co-employment: you keep employing through your own entity and share allocated dutiesYou, with duties allocated by the co-employment agreementYour entity records, state registrations, benefits windows, and payroll transitionSalary, employer taxes, benefits, and an administration fee per employee or as a share of payrollEverything the agreement does not allocate to the provider; you remain an employerYours as employer, supported by the provider's HR and claims processesYou have no entity where the worker will be, or you need processing onlyYour entity footprint changes, or the allocation stops matching what actually happens
Certified PEOA PEO certified by the IRS, with defined federal employment-tax effectsYou, except that the CPEO is treated as employer for federal employment taxes on covered work-site pay it remitsSame as a PEO, plus a Form 8973 filingSame components as a PEO; certification is not a pricing modelSame as a PEO outside federal employment taxes; state law and the contract can add moreYours. Certification governs employment taxes, not dismissal liabilityYour work sites cannot clear the 85% test, or the workers are outside the United StatesWork-site composition changes, or the certified entity named on the contract changes
Payroll-only / ASOPayroll processing and HR administration without co-employmentYou, entirelyYour own entity records and payroll data, not a new legal structureA processing or administration fee on top of your own payroll costsAll of themYours entirely. The provider administers; it does not share dismissal liabilityBenefits buying power or shared employer responsibility is the actual requirementRisk-sharing or plan access becomes the reason you are buying
Direct contractor engagementA commercial engagement with no employment relationship, if the status genuinely holdsNobody, if the classification holds on the factsThe engagement's own terms — which is why classification has to be settled firstContract fees, plus whatever the engagement providesAll of them, plus the classification question itselfYours, and retrospective: reclassification reaches the periods already workedControl, integration, exclusivity, or duration start to look like employmentAny change in how the work is directed, or in the governing test
Owned local entityA company you incorporate and register locally, employing the worker directlyYour own local entityIncorporation, tax and social-security registration, banking, and any sectoral licenseSalary, statutory employer cost, and benefits with no service fee, against fixed overhead that does not scale with headcountAll of them, with no provider administering any partYours, under local statutory notice, grounds, process, and severance, with nothing standing between you and the liabilityThe footprint stays at one or two people, or the presence stays exploratoryHeadcount falls, the market is exited, or the entity's obligations outgrow the local team

Two of these routes are analyzed in depth elsewhere: contractor engagement turns on jurisdiction-specific classification law, covered at the classification guide, and owned entities turn on setup sequence and break-even math, covered at the entity comparison.

How this comparison was built

EOR Hub is an independent editorial publisher. It is not an employer of record, a PEO, a payroll processor, a law firm, or a tax or immigration adviser, and this page is general information and an editorial decision framework rather than legal, tax, or immigration advice for any particular company or worker. The U.S. CPEO statements describe specific federal tax and contract requirements and were checked against the governing statute, regulations, and current IRS guidance; the statutory and regulatory citations point to the Legal Information Institute's published text of the Internal Revenue Code and the Code of Federal Regulations, chosen for readability, and the governing text is the Code itself. The restricted-jurisdiction entries were checked against the named governing instruments and, for Germany, France, Switzerland, and Japan, the official text or the responsible authority's own published material; the Netherlands entry relies on a dated professional analysis of an adopted act and is labeled accordingly, and the China entry on two dated professional analyses. The entries are not a complete list of restricting jurisdictions, and countries absent from the table were not examined.

The Portugal figures were checked against the Instituto da Segurança Social's own published guidance, and the Portuguese admission and cessation rules against the 2026 amendments to the Código dos Regimes Contributivos and their implementing decree. One government overview page consulted for the cessation deadline still states the pre-2026 admission rule; the admission position in this guide follows Decreto-Lei n.º 127/2025, and the cessation deadline is cited to Decreto Regulamentar n.º 7/2025. EOR responsibilities depend on local law, the employing entity, and the service agreement.

No provider is ranked, scored, or recommended on this page, no scoring rubric is used, and no provider pricing or coverage claim is repeated as fact; where a provider's own published comparison is cited, it is cited only as evidence of what that provider claims. Four such comparisons were read on 1 August 2026. They are a sample rather than a census, and other providers may state the position differently.

Commercial relationships and funding. This page ranks, scores, and recommends no provider. How this page is funded: EOR Hub is supported by advertising and, on some pages, disclosed referral links. No provider has paid for placement, ordering, or inclusion on this page, and compensation never determines what is included or how it is ranked. If a compensated link is added to this page, it will be disclosed here.

All sources were reviewed on the date shown at the end of this page and are re-verified at least semiannually, and sooner on a known change in law, rate, or official guidance. Verify the worker's country, employing entity, status, work authorization, and contract before acting on any of it.

Where this differs from provider-published comparisons

Provider-published comparisons of these two models routinely describe the EOR as absorbing the client's compliance liability. Four were sampled for this guide on 1 August 2026 and all four say a version of it: one states that an EOR is the sole legal employer with no compliance liability left with the client; a second that EORs take on the risk that the client would otherwise carry; a third that the provider carries most of the legal liability, leaving the client less exposed; a fourth that the provider owns the compliance triggers rather than the client. This guide reaches a different conclusion, for a specific reason: liability allocation is set by the governing law of the worker's jurisdiction and by the contract, not by the service label. A provider can assume defined obligations and can indemnify against defined failures. It cannot move a permanent-establishment question that arises from your own activity, a classification question about your own past conduct, or a works-council duty that attaches to your operation. Treat any unqualified liability claim as a contract term to be located and read, not as a property of the model.

Comparing cost, control, risk, and implementation

Cost: what a comparable comparison contains

Cost only compares cleanly when the components stay separate. For either model, an apples-to-apples view lists each of the following on its own line, because blending any two of them is where comparison errors start:

  • Gross salary, in the local currency and pay period, with the annualization assumption stated.
  • Statutory employer contributions and payroll taxes — kept strictly apart from employee deductions, which are withheld from the worker's own pay and are not an employer cost, however often quotes blur the two.
  • Mandatory additional compensation where local law requires it, commonly known as 13th-month or 14th-month pay: an extra monthly payment, or two, owed by statute on top of the twelve.
  • Benefits, separating statutory items from supplemental plans, and noting whether the provider passes plan costs through at cost or applies a markup.
  • The service fee itself — flat per employee or a percentage of payroll. Pricing models vary, quotes are usually required, and a percentage fee grows with every raise while a flat fee does not.
  • Setup or onboarding fees and other nonrefundable one-time charges.
  • Deposits and salary prefunding, which are cash-flow requirements: money you must have available, and — when refundable — not automatically an expense at all. Treat them as a financing question, not a price.
  • FX rates and any markup applied to cross-border payments, which can be a material, quiet cost line on international payroll.
  • Event-driven charges: off-cycle payroll runs, immigration support, and termination handling.
  • Any tax applied to the service fee where the jurisdiction imposes one.
  • The minimum commitment: contract term, notice, and any per-employee or per-account minimum, which set the cost of being wrong.
  • A termination or severance reserve, where local law makes dismissal costs predictable enough to provide for.

A worked example: what the statutory floor looks like in Portugal

The point of a worked example is not to predict your invoice. It is to show how much of the cost is fixed by law before any provider quotes anything, so that the part a provider can compete on is visible as the smaller number it usually is.

Assumptions. Portugal; general contributory regime; one full-time employee on an open-ended contract; employer with no reduced-rate or exemption entitlement; monthly base salary of €4,000, stated in euros with no conversion; contributions modeled on all fourteen payments; figures as of 1 August 2026.

LineAmountBasis and status
Base salary, twelve monthly payments€48,000Modeling assumption
Holiday and Christmas subsidies, one month's pay each€8,000Código do Trabalho, arts. 263.º and 264.º — verified
Annual gross, fourteen payments€56,000Derived
Employer social security at 23.75% of the contributory base€13,300Instituto da Segurança Social general-regime rate — verified
Statutory employer cash on pay€69,300Derived
Insurance and benefit lines the provider pricesQuote requiredNot publicly disclosed
EOR service feeQuote requiredNot publicly disclosed
Setup fee, deposit or prefunding, FX cost, event chargesQuote requiredNot publicly disclosed

Read the three totals as the naive figure, the statutory floor, and the figure that cannot be closed. The naive figure, €48,000, is the one that appears when a comparison is built from monthly salary alone; it is not a lawful employer cost in Portugal and no provider will invoice it. The statutory floor, €69,300, is what the employment costs before a single commercial term is agreed. The third figure cannot be closed from public sources, because every remaining line is quote-required — which is the honest answer, and the reason a comparable quote needs identical inputs.

The line driving the spread is statutory, not commercial. The fourteen-payment pattern and the 23.75% employer contribution together add €21,300, or 44%, to the twelve-month salary figure. A provider's service fee, whatever it turns out to be, is competing for a fraction of that gap. This is why a fee-versus-fee comparison between two providers, or between an EOR and a PEO, tells you very little about total cost. On these assumptions the uplift is a property of the rate and the payment pattern rather than of the salary — both scale with pay, so the same proportion appears at a lower or higher base. Check whether a country caps the contributory base before assuming the same proportionality holds there.

Low, base, and high on the same assumptions. The only variable that moves between these three rows is the salary; every statutory input is identical.

Monthly base salaryAnnual gross, fourteen paymentsEmployer social security at 23.75%Statutory employer cash on pay
€2,500€35,000€8,313€43,313
€4,000€56,000€13,300€69,300
€7,000€98,000€23,275€121,275

Amounts are rounded to the nearest euro. The 44% uplift over the twelve-month salary figure is identical at all three levels, because the contribution rate is flat and the payment pattern is fixed — which is exactly why the same arithmetic cannot be carried into a country that caps the contributory base, applies banded rates, or requires a different number of payments.

Two boundaries on this example. It is Portugal only: contribution rates, ceilings, mandatory payments, and exemptions differ in every country, and nothing here transfers. And it models statutory employer cost, not a quote. For the detailed fee structures, deposit mechanics, and quote math, compare total EOR cost and quote inputs rather than rebuilding that model here.

The same test on the PEO side. A PEO invoice separates a different set of lines, and the same discipline applies to each. Ask for the administration fee and its basis, since per-employee-per-month and percentage-of-payroll behave differently as salaries rise. Ask for benefits premiums separately, and for whether they are passed through at cost or marked up. Ask for workers' compensation, which is priced on classification codes and claims history rather than on the service. And ask for federal and state employer taxes, which attach to the employment and not to the arrangement. This guide publishes no PEO price range: those components are quoted rather than listed — quote required — and a range assembled from marketing pages would be a figure without a governing source.

The single most common comparison error is weighing one provider's service fee against another provider's fully loaded quote. A service fee is not total employment cost, and a low fee attached to a benefits markup and an FX spread can cost more than a higher, cleaner fee.

How much control do you keep under each model?

Control is less different than the marketing suggests. In both models the client directs day-to-day work: assignments, priorities, performance, the commercial relationship. The real differences sit one level down. Under an EOR, employment terms must fit local law and the provider's contract templates and policies, which constrains customization of contracts, policies, and sometimes equity or bonus mechanics. Under a PEO, the client typically keeps more direct control over employment policies because it remains the employing entity, while sharing the administration. Neither arrangement converts operational control into employer status, or the reverse. Those remain separate questions with separate legal answers.

Which risks stay with you under either model?

Risk should be handled domain by domain, because the models touch each domain differently: employment law, payroll and social-security administration, corporate tax and permanent establishment, worker classification, immigration, employee representation, data protection, and intellectual property.

Two of those domains are routinely missed by companies whose experience is U.S.-only. A works council is a body of elected employee representatives with statutory information, consultation, and in some countries co-determination rights over decisions affecting staff; it exists at establishment or company level and is common across continental Europe. A collective bargaining agreement is a negotiated instrument between employers or an employer association and a trade union that can set pay, hours, and termination terms for a whole sector, binding an employer regardless of whether it negotiated the agreement itself. Both attach to the employment and to the workplace, not to the service contract, and neither disappears because a provider is running payroll.

A provider can administer defined pieces — running compliant payroll, issuing a locally valid employment contract, enrolling statutory benefits, maintaining records. What no arrangement does is neutralize the domains it does not touch. The client's own sales, contracting, and management activities in a country can still create a taxable presence there; past worker classification is judged on the facts of the past; work authorization is a prerequisite, not a feature; and IP assignment and data-transfer terms are only as good as the contract chain that carries them, which under an EOR runs from the worker to the employing entity to you and can break at either link. When a hiring plan touches these domains, the escalation is to qualified employment counsel, a tax adviser, or immigration counsel, not to a faster vendor.

The intellectual-property question is worth naming as a chain, because it has two links and either can fail. The first link runs from the worker to the employing entity, under the employment contract that entity issues and under whatever the governing law of that country allows such a contract to assign. The second runs from the employing entity to your company, under the service agreement. Ask to see the assignment language on both links before the first line of code or copy is written, and ask what happens to the first link if the provider changes the local entity or partner it employs through.

Implementation and timelines

Implementation is where vendor promises need the most translation. The dependencies behind an EOR start date are listed in the matrix above; what the matrix cannot show is that one of them is usually a legal step with a fixed deadline rather than a task a provider can accelerate.

Portugal illustrates that category, and also how quickly these rules move. Until the end of 2025, the employing entity had to notify Segurança Social of a new hire in the fifteen days before the contract took effect. Since 1 January 2026, under the amendments made by Decreto-Lei n.º 127/2025 to the Código dos Regimes Contributivos, the communication is due by the start of the contract's execution, keeping a narrow exception that allows it within 24 hours where exceptional and documented reasons prevent it. The runway disappeared but the gate did not: the step still has to be completed before the worker starts, and it exists whether or not the provider mentions it. Effective 1 January 2026 — confirm the current position before any start date is committed.

PEO implementation depends instead on entity records, state registrations, benefits transition windows, and often a parallel payroll run before cutover. In both cases the calendar is set by the slowest required dependency, not by the sales cycle. Treat any advertised onboarding speed as a conditional vendor statement to test against your facts.

What actually sets the start date

No advertised timeline is worth more than the slowest dependency behind it, and the dependencies are knowable in advance. In rough order of how often they bind:

  • Work authorization, where the worker needs it. Nothing further down this list can start the clock earlier.
  • A statutory step that must be completed before work begins. In Germany the provider's permit must be in place before the assignment starts. In Portugal the admission must be communicated by the start of the contract's execution. Neither is a provider service level; both are legal gates.
  • A locally compliant employment contract, translated where the country requires it, and agreed by the worker.
  • Benefits enrollment windows, which are set by insurers and schemes rather than by the provider.
  • Payroll cutoff and funding, which decide whether the first pay run is the one you expected.

Ask any provider which of these binds on your facts, and ask for the answer in writing. A provider that has run the country before will name one without hesitating.

Four scenarios that change the answer

These scenarios test the rules above against realistic facts, because the gate is easy to state and harder to apply when a real hire is waiting. None of them is legal advice; each ends with the verification that matters most before anyone signs anything.

Scenario 1: First foreign employee, no entity

A 30-person software company wants to hire a senior engineer who lives in a country where the company has no presence and, for now, no plans beyond this one role. Likely path: EOR. Why: the entity gate closes the PEO route outright, and a single hire rarely justifies the cost, governance, and ongoing filings of entity setup. The EOR converts a months-long establishment project into a service contract, at the price of a recurring fee and less control over employment terms. Verify next: whether the country licenses or restricts the arrangement at all; that shortlisted providers support this seniority and this specific worker, including whatever documentation the country requires from them; whether the candidate needs work authorization, since sponsorship is a separate question from service availability; and the fully loaded cost using the component list above, not the headline fee.

Scenario 2: Domestic workforce, own entity, administration strain

A U.S. company employs about forty people through its own entity across several states. Payroll runs late, benefits renewals are expensive, and HR is one overloaded generalist. Likely path: PEO, with CPEO certification worth weighing for its bond, audit, and defined federal employment-tax features. Why: the entity already exists, so the problem is not a missing legal employer. It is administration and benefits buying power, which is precisely what the co-employment product packages. Verify next: the provider's registrations in every state where the company employs; if certification matters, the exact CPEO entity name and EIN on the IRS listing and whether your work sites clear the 85% test; the exact responsibility split in the service agreement across payroll, filings, benefits, and workers' compensation; plan pricing against current renewals; and exit terms, including what happens to benefit plans and employee data on departure.

Scenario 3: Several workers concentrating in one country

A company already employs four people through an EOR in one country, plans five more there within a year, and has started signing local customers. Likely path: keep the EOR working today, and start the entity comparison now rather than waiting for renewal. Why: concentration, permanence, and local commercial activity shift both the economics and the risk picture. Per-employee fees scale linearly while entity overhead does not, growing local activity raises permanent-establishment questions that an EOR arrangement does not answer, and where the country caps assignment duration or the proportion of dispatched workers, scale can breach the cap itself. An interim structure can quietly outlive the facts that justified it. Verify next: any statutory duration or headcount cap in that country; the total-cost and control trade-offs between staying on the EOR and opening an entity; a tax review of the company's own local activities; and the transfer mechanics — notice, continuity of employment, and benefits — for the existing employees.

Scenario 4: A "contractor" who works like an employee

A company has paid someone monthly for two years, sets their hours, supplies their equipment, and directs their work, and now wants to "move them onto an EOR" to tidy things up. Likely path: classification analysis first, under the law of the worker's jurisdiction. This is the third kind of no: a stop sign, not a comparison. Why: placing the worker with an EOR going forward does not automatically cure exposure from past periods, which are judged under the rules that applied at the time; and the analysis, not the platform, determines what the relationship lawfully was and what the transition should look like. Moving fast here can convert a quiet risk into a documented one. Verify next: review contractor classification risk with qualified local advice before changing anything, so the transition — the employment offer, any back-pay questions, the timing — is designed with the history in view rather than around it.

When to switch models, and what to write down first

Model choices are made against a snapshot of facts, and the facts move. Revisit the structure when any of these triggers appears:

  • The country stops being a test — headcount concentrates beyond the level the current structure was chosen for, the presence becomes permanent rather than exploratory, or a strategic commitment appears in the form of local customers, local leadership, or local investment. The economics that favored a per-employee fee at one hire look different at eight, and a structure chosen for a test should not carry a commitment by default.
  • A statutory cap comes into view — an assignment-duration limit, a proportion-of-workforce cap, or a role restriction that your growth is about to breach.
  • You enter regulated activities that require a licensed local presence, which a service arrangement may not be able to supply.
  • You need direct control of benefits, policies, or employment terms that the current provider's contract templates cannot accommodate.
  • Provider restrictions repeat — roles, seniority levels, worker types, or contract terms the EOR keeps declining to support.
  • A service-contract renewal arrives, which is the natural, low-friction moment to re-run the numbers rather than rolling forward on inertia.
  • The provider exits, is acquired, or materially changes terms, forcing a decision you would otherwise defer.

When the trigger is concentration, permanence, or control, the next step is to compare an EOR with opening an entity — that page owns the break-even math and the transition mechanics, including moving existing EOR employees onto your own entity. When the trigger is provider-specific, the question may be a different provider rather than a different model; re-run the four-question gate before assuming either answer.

What you are left holding at exit

Every engagement ends, and the notice you owe the provider is rarely the notice that matters. Five items decide how an exit actually goes, and all five are cheaper to negotiate at signing than at departure.

  • Two notice periods, not one. The service agreement's notice runs between you and the provider. The employee's notice, grounds, and process run under local employment law and are usually longer and less flexible. Confirm which one gates the exit date.
  • Continuity of employment. Where employment transfers to your own entity or another provider, accrued service and the rights attached to it may or may not carry over. Local transfer rules can make continuity automatic, optional, or unavailable, and the answer changes the offer you have to make. Provider-to-provider switching and an EOR-to-entity transfer are different transactions here, and the second is far more likely to engage local transfer rules.
  • Accrued liabilities. Untaken leave, statutory severance provisions, bonus accruals, and any deposit held against them. Establish who funds each, and whether a refundable deposit is actually returned or set off.
  • Records and data. Payroll history, tax filings, employment contracts, and personal data. Agree the format, the handover window, and the retention and deletion terms before you need them.
  • Statutory closing steps. Exit is a filing event as well as a commercial one. A CPEO contract ending requires a Form 8973 notification to the IRS. In Portugal, the cessation or suspension of an employment contract must be declared to Segurança Social by the tenth day of the month following the event. Ask which equivalent step applies in your jurisdiction and who is responsible for it.

This list is what you need before you get that far.

The ten-input decision worksheet

Complete this before any quote request or advisor conversation. It exists to make quotes and advice comparable; it is not a calculator and it produces no legal conclusion.

  • ☐ Worker's physical work country and any subnational location.
  • ☐ The entity proposed to sign the employment contract, and its registrations or licenses.
  • ☐ Employee versus contractor status, and any prior engagement history.
  • ☐ Role, duties, regulated-industry constraints, and reporting line.
  • ☐ Target start date and expected duration.
  • ☐ Gross salary, currency, pay frequency, bonus, and equity assumptions.
  • ☐ Required statutory and supplemental benefits.
  • ☐ Immigration or work-authorization need.
  • ☐ Expected headcount in this country over the next 12–24 months.
  • ☐ Exit plan: EOR-to-entity transfer, PEO termination, redundancy, or provider change.

Identical inputs are what make quotes comparable. Two providers quoting different salaries, benefits assumptions, or start dates are not answering the same question, and a quote built on your worksheet is far easier to hold to later, because the assumptions are yours and written down.

Common terminology mistakes

Four recurring label problems distort this decision more than any pricing table does.

When a provider markets a "global PEO," ask which entity would employ the worker and what the contract says. The underlying service is usually an EOR arrangement, sometimes payroll, occasionally something else entirely. The answer is in the agreement, not the product name.

A provider that processes payroll does not thereby become the employing entity, and paying someone through a platform does not change who employs them. If the structure depends on who employs the worker — and it usually does — confirm it expressly in the contract.

Country coverage is not an owned entity

A provider listing a country may operate there through its own entity, a local partner, or a mixed model, and may not disclose which. The distinction can affect accountability, data handling, service consistency, and, where the country licenses the arrangement, which entity actually holds the license. If the operating model matters to you, treat it as unverified until documented in writing.

An EOR is not a compliance cure

Engaging an EOR going forward does not resolve how past periods are classified or taxed, and the IP assignment chain running from worker to employing entity to you is only as strong as its weakest contract link. An EOR solves the specific problem it is built for — lawful employment through a local employer — and should be bought, and trusted, for exactly that.

Frequently asked questions

Can a company use both an EOR and a PEO?

Yes, and at moderate scale it is common: a PEO-style arrangement for a domestic workforce employed through the company's own entity, and an EOR for workers in countries where it has none. They solve different problems and can run in parallel — but they remain separate contracts, with separate costs and separate responsibility maps, and each should be evaluated on its own terms.

Is a CPEO the same as an EOR?

No. CPEO is an IRS certification with defined federal employment-tax consequences for covered U.S. work-site employees within a co-employment arrangement, and it presumes you already employ through your own entity. An EOR provides the local employing entity where you have none. The overlap in vocabulary does not make them substitutes.

Does a PEO require you to have your own entity?

Under the U.S.-style model this page uses, generally yes: the client employs through its own eligible entity and registrations, and the PEO shares allocated responsibilities. A provider claiming otherwise is usually describing an EOR service under a PEO label — read the contract.

Can an EOR sponsor a work visa?

Sometimes, in some countries, for some roles — and sometimes not at all. Sponsorship eligibility depends on the country's immigration rules, the sponsoring entity's status, and the specific role and worker. A provider's presence in a country is not evidence it can sponsor your candidate, and immigration support is often a separately scoped, separately charged service. Confirm the specific case in writing before committing a start date.

Is an EOR always more expensive than a PEO?

The comparison is usually meaningless as posed, because the models price different jobs: a lawful employment route abroad versus shared domestic administration. In Portugal, as the worked example above shows, the 23.75% employer contribution and the two mandatory extra monthly payments together add 44% to a twelve-month salary figure before any provider quotes a fee. Compare fully loaded, like-for-like quotes for the same worker and situation, using the component list above, before drawing any cost conclusion.

No. Several countries regulate the underlying arrangement through labor-leasing, dispatch, or supply-of-labor law — requiring the employing entity to hold a license, admission, or registration, prohibiting the supply of labor for profit outside a defined framework, or capping duration, headcount proportion, or eligible roles. Germany, France, the Netherlands, Switzerland, Japan, and China each do a version of this on different terms, and Switzerland does not permit personnel to be leased into the country from abroad at all. Countries absent from the table above were not checked for this guide, so treat them as unchecked rather than unrestricted, and ask any provider for its local license, admission, or registration number in writing.

Does this page cover notice periods and severance by country?

No. Notice, dismissal grounds, process, severance, and any statutory termination pay are set by each country's employment law and differ enormously; nothing on this page should be read as stating them. This page covers whether the EOR or PEO model itself is available and permitted, and what each model does with the exposure. Country-level employment rules sit on EOR Hub's country guides, which publish only once every figure is verified against an official source, and a live termination decision belongs with local employment counsel.

What to do next

Overhead flat-lay of an open benefits booklet, folded glasses and completed forms on an oak desk

Document the facts the decision actually turns on — worker country, employing entity, status, start date, compensation, benefits, immigration need, headcount plan, and exit path — using the worksheet above. Then follow the route those facts support. The first move differs by who you are:

  • If you lead HR or people: confirm the worker's country and status, check that country for licensing or dispatch restrictions, and identify the dependency that will actually set the start date.
  • If you lead finance: build the fully loaded annual cost for both candidate routes using the component list, starting from the statutory floor rather than the quoted fee, and price the minimum commitment and exit terms alongside it.
  • If you lead legal or compliance: get the local license, admission, or registration number in writing where the country requires one, establish what the service agreement allocates to each party, and settle whether any classification, immigration, or permanent-establishment question needs answering first.

If the route is an EOR, compare EOR providers after choosing the model, taking your completed worksheet into every quote conversation. And where the facts raise classification, tax, immigration, or permanent-establishment questions, put a qualified advisor in the loop before you sign anything.

Sources and last verified date

Last verified: August 1, 2026

Next review: February 1, 2027

Not sure what fits your situation?

Answer a few questions and get a shortlist matched to where you are right now.

Take the 2-minute questionnaire

Keep reading