Recruit
If you’re evaluating an Employer of Record for international hiring, one of the first questions a careful legal or HR team will ask is: does this create co-employment? The short answer is no. Co-employment and EOR are different employment models that get confused because both involve a third party in the employment relationship. The differences matter because they determine who carries the legal liability, who files the taxes, and (in the US specifically) whether your company can be pulled into joint-employer disputes.
This guide explains what co-employment actually is, what an EOR actually is, where the line sits between them, and why almost every reputable EOR will tell you their model is structured precisely to keep you out of co-employment territory.
EOR vs Co-Employment: The 30-Second Answer
|
EOR vs Co-Employment: The 30-Second Answer |
||
|
Aspect |
Co-employment (PEO model) |
Employer of Record (EOR) |
|---|---|---|
|
Legal employer |
Both parties are employers (joint / shared status) |
Only the EOR is the legal employer |
|
Where it works |
US-domestic only (PEO co-employment is a US construct) |
Global (anywhere the EOR holds a registered local entity) |
|
Liability allocation |
Shared, both parties can be named in claims |
Carried by the EOR per the local employment relationship |
|
Payroll filings |
Filed under the PEO’s federal EIN; W-2s issued by the PEO |
Filed under the EOR’s local entity tax IDs in each country |
|
Benefits |
PEO master plans (often better pricing through pooled risk) |
Country-statutory benefits + supplementary plans you choose |
|
Termination decision |
Joint, you decide, PEO executes per US law |
EOR executes per local employment law (notice, severance vary) |
|
Best for |
US W-2 workforce (often 5 to 200 employees) |
International workers in countries where you have no entity |
The cleanest one-line distinction: co-employment is two employers sharing one workforce in the US. EOR is one employer (the EOR) for your workforce abroad. They are not alternatives in most cases because they solve different problems in different geographies.
What Co-Employment Actually Is
Co-employment is the legal arrangement where two parties share employer responsibilities for the same group of workers. In the US, it’s the foundation of the Professional Employer Organization (PEO) industry. Your company controls the work (hiring, firing, pay levels, day-to-day direction). The PEO handles the administrative employer functions: payroll, employee tax withholding, benefits administration, workers’ comp, and unemployment insurance. Both parties show up on different parts of the employment paperwork.
The arrangement is formalized through a Client Service Agreement (CSA) that allocates responsibilities between the two co-employers. The IRS recognizes the model and, since 2014, has had a formal Certified PEO (CPEO) program that limits federal employment-tax liability to the CPEO when the agreement is properly structured.
The Vizcaino Case and Why Co-Employment Has a Bad Reputation
Before 1996, co-employment was largely a back-office construct. That changed when Vizcaino v. Microsoft reached the Ninth Circuit. Microsoft had classified a group of workers as “freelancers” but treated them indistinguishably from employees. The court ruled those workers were common-law employees of Microsoft and therefore eligible for the company’s employee stock purchase plan and 401(k). The settlement reportedly cost Microsoft about $97 million. The case became the defining example of why companies who use staffing agencies, contractors, and PEOs need to be careful about how the relationship is structured: if the practical reality of the work looks like employment, courts and agencies will treat it as employment regardless of what the contract says.
Most modern co-employment risk discussion still traces back to Vizcaino, even though the underlying facts (misclassification of freelancers, not a structured PEO relationship) were quite different from a properly run CPEO arrangement.
What an Employer of Record Actually Is
An Employer of Record is a third-party company that is the sole legal employer of your workers in a given country. The EOR holds a registered local entity, signs the employment contract, runs local payroll, withholds local taxes, pays local statutory benefits, and carries the legal employment liability under local law. Your company is the EOR’s client. You direct the worker day-to-day. You make all hiring, performance, compensation, and termination decisions. The EOR executes the legal employment per the rules of the country.
The model is structurally not co-employment. There is no “shared” employer status. The EOR is the employer. You are the client of the employer. The worker has one legal employer (the EOR), one employment contract (with the EOR), one paycheck source (the EOR’s local entity), and one set of statutory benefits administered by the EOR. From a US joint-employer doctrine standpoint, this matters: most international jurisdictions don’t have an analog to US co-employment, and even where they do, the EOR’s structure isolates the client company from local employer obligations.
For a deeper view of how EOR fits into the broader international employment toolkit, see our EOR services overview.
Why People Confuse the Two (and the Line Between Them)
The confusion makes sense at first glance. Both models put a third party between the worker and the company that directs the work. Both involve payroll being run under someone else’s tax ID. Both reduce the administrative employer burden on the company that’s doing the hiring. The structural difference is whether the legal employer status is shared or exclusive:
- Co-employment: Two legal employers, both with employer obligations to the worker. The worker can theoretically pursue claims against either party (subject to the CSA and the relevant statute).
- EOR: One legal employer (the EOR). The client company is a service customer, not an employer of the worker. The worker’s employment claims run against the EOR.
The line gets blurry only in two situations: when a US company tries to use an EOR for US workers (some do, and the EOR effectively becomes a PEO with co-employment kicking back in), and when a company exercises so much direct control over EOR-employed workers that local labor authorities start asking whether the EOR is a legal fiction. The first is solved by using a PEO instead of an EOR for US workers. The second is solved by following the EOR’s documented escalation and management practices instead of inserting your company name into local employment paperwork.
Liability: Who Carries What
|
Liability: Who Carries What |
||
|
Type of liability |
Co-employment (PEO) |
EOR |
|---|---|---|
|
Federal employment taxes |
CPEO carries federal payroll-tax liability under IRS Section 3511; non-certified PEO does not |
EOR’s local entity files locally; client has no US federal payroll-tax exposure for these workers |
|
State unemployment, workers’ comp |
Shared based on CSA; varies by state |
Country statutory equivalents handled by EOR locally |
|
Wage-and-hour claims (FLSA, state) |
Both parties can be joint employers under FLSA; both can be named |
Local wage-and-hour rules; EOR is the named employer |
|
Discrimination / harassment claims |
Both parties can be named; client typically holds primary exposure for direction-related claims |
EOR is named under local equivalent; client’s exposure depends on country |
|
Wrongful termination |
Joint exposure; PEO usually executes the termination, client carries the underlying decision |
EOR carries local termination compliance (notice, severance, statutory protection) |
|
Misclassification of contractors |
The most common co-employment risk surface; courts look past the PEO at actual control |
Lower because the EOR is the legal employer, not a contractor relationship |
If you only remember one thing from the liability table: co-employment shares risk; EOR contains it within the EOR’s structure. That doesn’t make EOR risk-free. It moves the risk surface to the EOR’s contractual indemnity obligations and the EOR’s local compliance practices.
Co-Employment Risk: The Real List
“Co-employment risk” is one of the most-searched phrases in this category and one of the most-misused. The actual sources of co-employment risk in 2026 are:
- Misclassified contractors who function as employees. Pay someone as a 1099 contractor when they work full-time, get directed by a manager, and use your equipment, and a court (or the IRS) will likely treat them as a common-law employee. If you used a third party (a contractor management firm, a staffing agency) to pay them, both parties may be co-employers.
- Staffing agency workers under your direction for too long. Temp workers placed through an agency who stay for years and integrate into your team are the classic joint-employer fact pattern. The Microsoft Vizcaino case fell here.
- PEO arrangements without a CPEO designation. Without IRS Section 3511 protection, the client company retains federal payroll-tax liability if the PEO fails to remit. CPEO designation matters.
- Direct control of EOR-employed workers documented in your name. If your company signs employment-style paperwork (offer letters under your letterhead, performance plans referencing “your employer obligations”), local authorities can argue you are the employer in fact.
- Benefits administration that bypasses the third party. If you administer local benefits directly to a worker the EOR or PEO is supposed to employ, that direct relationship can pull you into employer status.
Note that a properly structured EOR engagement does not appear on this list. The risk is in the gray areas around contractors, temps, and informal arrangements, not in the EOR model itself.
Geography: Where Each Model Actually Works
Co-employment is fundamentally a US construct. The PEO industry, the IRS Section 3511 CPEO rules, the joint-employer doctrines under FLSA and the NLRA, and most of the case law are US-specific. A handful of other jurisdictions have analogous structures (some Canadian provinces have shared-employer arrangements; some EU countries have temporary work agency rules that look co-employment-adjacent), but the formal “co-employment” framework you’d find in a Justworks or TriNet contract does not exist outside the US.
EOR is a global construct. The EOR holds a local entity in each country, follows local employment law, and operates under that country’s labor framework. Most countries have either a single-employer model (Brazil, India, Germany), a pooled employer model (some staffing-agency frameworks in France and the UK), or a nascent EOR-friendly framework (Singapore, Australia). None call it “co-employment” in the US sense.
This is why the practical answer to “should we use co-employment or EOR?” is usually that you don’t choose between them. You use co-employment (PEO) for your US workforce and EOR for your international workforce. They live in different geographies.
Cost: PEO Co-Employment vs EOR
The pricing models look similar but cover very different scopes. PEO fees in the US typically run 2 to 12 percent of payroll or $50 to $200 per employee per month, depending on services included (payroll only vs full HR + benefits + workers’ comp). EOR fees globally run $300 to $800 per employee per month, depending on country and provider. The EOR fee covers the legal employment relationship in a country where you don’t have an entity, plus payroll, statutory benefits administration, and local compliance.
The fee difference reflects scope, not value. Setting up your own foreign subsidiary as the alternative to EOR runs $20,000 to $60,000 in setup and $1,500 to $3,500 per month in ongoing local accounting and legal, meaning the EOR fee is dramatically cheaper for any company with fewer than 5 to 8 workers in a given country.
Looking at the broader 3-way picture? See PEO vs EOR vs Staffing Agency.
Decision Matrix: Which One Fits Your Situation
|
Decision Matrix: Which One Fits Your Situation |
||
|
Your situation |
You need |
Why |
|---|---|---|
|
US-only company, 10-200 W-2 employees, want better benefits pricing + outsourced payroll |
PEO (co-employment) |
PEO master plans usually beat what you can negotiate alone; CPEO option caps your federal payroll-tax exposure |
|
US company hiring international full-time workers without a local entity |
EOR |
Co-employment doesn’t extend abroad; EOR is the right structure |
|
Mixed US + international workforce |
PEO + EOR (or PEO with EOR partner) |
Different models for different geographies; some PEOs partner with EORs to bundle |
|
Worried about co-employment risk specifically |
EOR for international, ASO for US |
ASO is the non-co-employment US alternative to PEO; EOR is single-employer abroad |
|
Hiring lots of contractors and unsure of misclassification exposure |
Audit + EOR conversion |
The risk is in the contractor relationships, not in co-employment per se; EOR is the conversion path for international contractors who should be employees |
|
Already on a PEO, expanding internationally |
Add an EOR (don’t try to extend PEO abroad) |
PEOs cannot legally co-employ workers in foreign countries; the EOR is a separate engagement |
Common Mistakes Companies Make
- Assuming an EOR creates co-employment. A correctly structured EOR engagement does not create co-employment because the EOR is the sole legal employer in the worker’s country. The confusion usually comes from US-centric legal review applied to a non-US engagement.
- Trying to use a PEO for international workers. A PEO operates under US co-employment law. It cannot legally co-employ workers in countries where it doesn’t hold a local entity (which is most of them). Companies who try this end up with workers paid as US 1099 contractors abroad, the exact misclassification trap that creates real co-employment risk.
- Using a non-certified PEO and assuming federal payroll-tax protection. Only Certified PEOs (CPEOs) get IRS Section 3511 treatment. Non-certified PEOs leave the client company on the hook if the PEO fails to remit federal payroll taxes. If you’re using a PEO, confirm CPEO status.
- Letting the EOR engagement drift toward direct employment. If your team starts issuing offer letters under your letterhead, signing local performance management forms, or paying workers directly, the EOR’s protective structure starts to weaken. Stick to the EOR’s documented processes.
- Mistaking staffing-agency co-employment for the PEO model. A staffing agency that places temp workers under your direction is also a co-employment scenario, but with very different legal mechanics than a PEO. The Vizcaino case was about staffing-style co-employment, not PEO co-employment.
The Bottom Line
Co-employment is a US-specific legal arrangement where two parties share employer responsibilities for the same workers. PEOs run on this model. The EOR model is structurally different: one legal employer (the EOR) in the worker’s country, you as the client. They aren’t direct alternatives because they live in different geographies and solve different problems. Most growing companies use both: a PEO (or ASO) for US workers, an EOR for international.
If your concern is co-employment risk, the practical answer is to look at the actual sources of risk (misclassified contractors, long-term staffing agency placements, non-CPEO arrangements), not to fear EOR. The EOR model is built specifically to avoid co-employment by being the sole legal employer in the worker’s country.
If you’re hiring international workers and want a structure that avoids co-employment by design, see how our EOR works in 150+ countries. We hold owned entities in every market we serve, so the legal employment lives entirely within the EOR’s structure, not yours.
Frequently Asked Questions
No. A properly structured EOR engagement is single-employer by design: the EOR is the sole legal employer of the worker in the worker's country, and your company is the EOR's client (not the worker's employer). Co-employment is a US legal arrangement where two parties share employer status, which the EOR model specifically avoids. The exception is using an EOR for US workers, where co-employment can re-emerge because the EOR is functionally acting like a PEO.
The terms overlap heavily. "Co-employment" is the contractual arrangement between a company and a PEO (or staffing agency) where they agree to share employer responsibilities. "Joint employment" is the legal doctrine that two entities can be employers of the same worker for purposes of a specific statute (FLSA, NLRA, Title VII). Most co-employment arrangements create joint employment for some statutes but not others, depending on the contract and the level of control each party exercises.
The five real ones in 2026: (1) misclassified contractors who functionally work as employees, (2) staffing-agency temps who stay long-term and integrate into your team, (3) PEO arrangements without IRS Certified PEO (CPEO) designation, which leaves you exposed to federal payroll-tax liability, (4) directly controlling EOR-employed workers in ways that create local employer status, and (5) administering benefits or pay directly to workers a third party is supposed to employ. A clean EOR engagement does not appear on this list.
Yes. Co-employment through a PEO is fully legal and the basis of a multi-billion-dollar industry. The IRS formally recognizes Certified PEOs under Section 3511, and state insurance and employment agencies have established frameworks for PEO co-employment. Risk arises not from co-employment itself but from misclassification, non-CPEO arrangements, or staffing-agency relationships that drift into long-term employment-like arrangements.
Not in the formal US PEO sense. Some other jurisdictions (Canadian provinces, certain EU temporary work agency frameworks) have analogous shared-employer arrangements, but the contractual and statutory machinery of US co-employment doesn't translate. This is why companies expanding internationally use EOR (single-employer model) rather than trying to extend a US PEO across borders.
Three practices: (1) keep contractor relationships genuinely independent (multiple clients, own tools, no fixed schedule, no integration into team management), (2) for staffing-agency placements, document the agency as the employer and avoid issuing direction in writing under your company's name, (3) for long-term workers in either category, convert them to direct employment (W-2 in the US, EOR-employed abroad). The Microsoft Vizcaino case showed how dangerous gradual integration can become.
Yes for federal payroll-tax exposure. Under IRS Section 3511, a CPEO assumes sole liability for federal employment taxes on the wages it pays to client workers. With a non-certified PEO, the client company remains liable if the PEO fails to remit. CPEO designation does not eliminate joint-employer exposure under FLSA or state law, but it removes the worst-case federal tax risk.
Yes, and this is a common transition pattern. PEOs cannot legally co-employ workers outside the US, so any international workers a PEO appears to manage are typically being paid as US 1099 contractors (which creates serious misclassification risk in the worker's home country). Moving them to a country-specific EOR engagement gets them onto a compliant local employment contract within 5 to 14 days per worker.
