Owned Entities
EOR owned entities, where the EOR is the legal employer in its own right rather than contracting through a local partner, matter most when compliance risk is high and indemnification expectations are strict. G-P, Atlas, and Deel operate owned entities across the largest country networks (G-P: 187 countries; Atlas: 160+; Deel: ~250 owned across 150+ countries). Remote operates a hybrid model with owned entities in key markets and partner networks in others.
For buyers in regulated industries or with enterprise-level compliance requirements, the distinction between owned and partner entities is contract-critical. Partner-network arrangements typically involve a longer liability chain and weaker indemnification terms. For a full comparison, see our best employer of record providers guide.
A People Ops lead at a Series C SaaS company told us about a Friday afternoon call with their legal team. The Brazilian labour authority had opened an audit on one of their employees and demanded payroll records, employment contracts, and tax filings within 48 hours.
The EOR provider acknowledged the request, then went quiet. The records were not held by the EOR. They were held by a local Brazilian partner who handled the actual employment relationship.
The partner came back ten days later. The fine for late production of records was paid by the company.
That gap between what the EOR appeared to do and what it actually controlled is the question this page exists to answer. Owned entities versus partner networks is the single most consequential architectural difference inside the EOR category, and it is the one most comparison content treats as a footnote.
Check current provider details
What EOR owned entities mean in an EOR context
An owned entity is a wholly-owned local subsidiary of the provider, registered as an employer in the country, holding its own tax ID, payroll registration, and statutory filings. Remote operates this way in every country it covers. Deel claims roughly 250 owned entities globally.
Pebl publishes around 65 owned entities alongside a partner network covering the rest. The question is not the headline number. It is whether the entity that legally employs your hire in Lagos, Hanoi, or Bogota is the EOR brand on your contract, or a third-party company you have never heard of.
When the EOR runs an owned entity, payroll runs through the provider’s own bank account in the local jurisdiction. Employment contracts are issued in the provider’s name. When an audit lands, the records are inside the provider’s own systems.
There is no third party with copies, no extra layer of cross-border transfer mechanics, and the indemnity language in your MSA actually covers the employer of record, because the EOR brand is the employer of record.
In a partner-network arrangement, the EOR brand is your contract counterparty, but the legal employer in-country is a separate company. That partner holds the employer registration, runs the bank account, and carries the primary statutory exposure. The EOR provider sits between you and the partner as a coordination layer.
Anything that requires the legal employer to act has an extra hop. Most of the time the hop is invisible. When something breaks, the hop is the whole story.
How the models differ in practice
Compliance flow in an owned entity is single-actor: the provider’s local team runs payroll, files taxes, registers new hires, and answers audits using internal systems. In a partner network, the EOR brand collects your instruction, validates it, and forwards it to the partner. The partner executes.
Each step has its own SLA, its own internal queue, and its own holiday calendar.
Service delivery timelines track this directly. Onboarding in Remote’s owned-entity countries runs 1 to 3 working days for standard hires. Oyster reports 48-hour onboarding in its Direct+ markets.
In partner markets, the same providers report onboarding times of 7 to 14 working days. A salary change or benefits enrolment runs a few hours in an owned-entity market and sits in a queue in a partner market.
Data flow follows the same architecture. In owned-entity setups, employee personal data moves from your platform to the provider’s local entity inside one corporate group: one DPA chain. In partner-network setups, data moves from your platform to the EOR, then onward to the partner: two transfers, two processors, two sets of sub-processor disclosures.
Your DPO will notice.
Audit response is where partner-network gaps become operational failures. Brazil’s eSocial requires ad hoc record production within tight windows. France’s URSSAF can request payroll records within five days.
Germany’s Finanzamt audits within seven. Those windows were designed for employers operating their own infrastructure, not for a coordination layer phoning a partner who phones an accountant. Two People Ops leads we spoke with in 2025 and 2026 described the same pattern: audit notice arrives, EOR brand acknowledges, partner takes a week to retrieve records, the deadline expires, the fine lands, the company pays.
How EOR providers compare on owned entity coverage
| Provider | Entity model | EOR countries | Disclosure level |
|---|---|---|---|
| Remote | 100% owned | 85+ | Full, every country owned |
| Deel | Mixed (approx. 250 owned) | 150+ | Headline number, no per-country split |
| Pebl | Mixed (approx. 65 owned) | 185+ | Owned count published, partner countries unnamed |
| Oyster | Mixed (Direct+ in major markets) | 120+ | Direct+ markets partially named |
| Multiplier | Mixed | 150+ | Limited per-country disclosure |
| Rippling | 100% partner | 80+ | Disclosed, all countries via partners |
| Papaya Global | 100% partner | 160+ | Disclosed, all countries via partners |
| Gusto | Third-party (Remote) | 12 | Disclosed, white-labelled Remote |
Source: provider documentation and Whichapp cross-provider analysis, April 2026.
Remote is the only provider we cover running 100% owned entities. Deel confirms owned-entity status for major Western European markets, the US, Canada, Mexico, Brazil, India, and Singapore in writing without resistance; smaller markets often surface as partner-served when asked. Rippling and Papaya Global are transparently 100% partner-network, and both compete on platform and payments infrastructure rather than entity depth.
Gusto’s international EOR runs through Remote as a white-label arrangement.
The diagnostic test for any provider: ask in writing to confirm whether your three target hire countries are served by an owned entity or a partner. Compare the written answer to the homepage marketing language. The gap between the two is your information about the provider’s disclosure culture, regardless of which way the answer falls.
What to ask your EOR provider before signing
Ask for a country-by-country entity statement covering your target hires: the entity name, entity registration number, and whether it is owned by the EOR’s parent or operated under a partner agreement, on company letterhead. Ask whether the entity model can change after contract signature: some providers reserve the right to switch a country from owned to partner mid-contract. Ask for the partner’s name in every country where one is used.
Ask for the master service agreement between the EOR and the partner, or a redacted summary: the contractual indemnity from the EOR to you is only as strong as the indemnity the partner gave the EOR. Ask about onboarding and amendment SLAs by entity type: the operational data reveals owned-versus-partner variance even when the contract language does not.
Whichapp view
Owned entities are not better than partner networks in the abstract. They are better in specific situations: regulated industries, complex employment law markets, audit-heavy jurisdictions, and procurement processes where legal will not sign without naming the legal employer.
If your plan covers fewer than 15 countries in Western Europe and stable APAC markets, owned entities are a defensible hard requirement. If your plan covers 30+ countries with a long tail of low-volume markets, a partner-network provider may be the only economically viable option, and your job becomes auditing the partner relationships rather than wishing them away.
Check current provider details
Frequently asked questions about EOR owned entities
Which EOR provider uses 100% owned entities everywhere?
Remote. It is the only major EOR we cover that runs 100% owned entities across all 85+ countries it serves. Deel, Pebl, Oyster, and Multiplier operate mixed models.
Rippling and Papaya Global are 100% partner-network. Gusto’s international EOR is white-labelled Remote.
Does the entity model affect employee experience?
Yes, in operational ways your employees notice. Owned-entity markets typically deliver onboarding in 1 to 3 working days, amendments within hours, and audit responses within 24 to 48 hours. Partner markets typically deliver onboarding in 7 to 14 working days, amendments in days, and audit responses constrained by the partner’s queue.
Is a partner-network EOR model legally risky?
Not inherently. Partner networks are legally valid and widely used. The risk is operational rather than structural: service quality, escalation speed, and audit responsiveness depend on the partner, which the EOR cannot fully control.
The risk is highest in countries with complex employment law and short audit windows, including Brazil, France, Germany, Italy, and India.
How do I verify which countries an EOR actually owns?
Ask in writing for a country-by-country statement naming the entity used in each of your target hire countries, on letterhead. Cross-check named entities against public corporate registries where available. If the provider redacts partner names, record the redaction in your procurement file as a risk to evaluate.
Do owned-entity providers cost more than partner-network providers?
Often, yes. Remote’s per-employee fees sit at the higher end of the EOR market, partly reflecting the cost of running owned entities everywhere. Total cost of ownership should include the time cost of slower amendments, longer audit response, and more complex DPA mapping in partner markets, which usually narrows the gap.
Can an EOR change from owned to partner mid-contract?
Some can. Providers occasionally exit owned entities in unprofitable markets and migrate employees to a partner relationship. Ask whether your contract permits unilateral entity-model change, and whether you have notice rights or termination rights if the model changes materially.
Should owned entities be a hard requirement for my shortlist?
If your plan covers fewer than 15 countries mostly in Western Europe and stable APAC, owned entities are a defensible hard requirement. If your plan covers 30+ countries with a long tail, requiring owned entities everywhere will eliminate every viable provider; the requirement should be relaxed for low-event markets and held firm for high-stakes ones.
Methodology and disclosure
Whichapp is an independent comparison site. This page assesses 8 EOR providers on entity-model architecture, disclosure quality, and the alignment between marketing claims and operational reality. Entity counts and country footprints reflect provider disclosures available in April 2026 and may change.
We may earn a commission from provider links on this page. Specific entity-model assignments should be verified in writing for your target hire countries during procurement.
Related guides
- EOR compliance guarantees: what providers actually cover
- EOR data security and processing chains explained
- EOR onboarding speed across owned and partner markets
- EOR offboarding and termination handling
- Best EOR providers 2026: ranked shortlist
Last reviewed: April 2026