EOR vs Global Payroll

Picture the moment a CFO drops a one-line message into your Slack: “We just closed the Series C.

Hire ten engineers in Berlin, four in Lisbon, two in São Paulo, and the first three need to start in six weeks.” You have a payroll bureau in the UK that handles your existing thirty staff.

You have no German entity, no Portuguese tax registration, and no idea what a Brazilian eSocial filing looks like. Now choose: do you stand up local payroll in each country, or do you hire through an Employer of Record? Both options will get bodies behind keyboards.

They will not get you there at the same speed, the same cost, or with the same risk on your balance sheet.

This guide walks the trade-offs the way a head of People Ops would, with the numbers and friction points your CFO and General Counsel will press on.

The core difference: who holds the employment contract

The single fact that separates these two models is whose name appears on the employment contract. Under a global payroll arrangement, your company is the legal employer.

You have a registered entity in the country, you sign the contract with the worker, and you carry every employer obligation that flows from that: tax withholding, social contributions, statutory leave, dismissal protections, pension auto-enrolment, the lot.

The payroll provider runs the calculations, files the returns, and pushes the net pay. They are a service provider, not the employer.

Under an EOR, a third party owns the legal entity in the country and signs the employment contract with the worker. The worker reports to your managers day to day, but on paper they are employed by the EOR’s local subsidiary.

You pay the EOR a service fee plus the loaded cost of the employee. The EOR carries the employer-of-record liabilities, including the messy ones: wrongful dismissal claims, works council disputes, social-security audits.

If you remember nothing else from this guide, remember this: global payroll is a service for companies that have already taken on the cost and risk of being a foreign employer. EOR is a way to skip that step.

What global payroll actually covers, and what it leaves to you

Global payroll takes your gross-pay inputs, applies local tax tables and social-contribution rules, files statutory returns, and arranges bank payment. In a multi-country deployment, your finance team gets one consolidated variance report.

What stays on your side is substantial: a registered entity in every country, all the corporate-governance overhead (local directors in some jurisdictions, annual filings, statutory audits), employment contracts drafted by your counsel, and termination management including severance calculations that vary by country.

What an EOR covers, and why the scope matters

An EOR bundles all employer obligations into a single per-head fee: tax and social-security registration, statutory benefits, payslip generation, year-end filings, employment-law compliance, and contract drafting.

You are not paying for payroll calculations; you are paying for the entity, the local employment lawyer, the benefits scheme, and the indemnity. When a German works council demands a redundancy consultation, the EOR leads it.

What an EOR does not cover is the work itself. Performance management, day-to-day direction, equipment provisioning, and the cultural integration of the hire are yours.

Most EORs will not let you treat the worker as a free agent: the employment contract sits with them, so they enforce notice periods, they vet termination decisions for legal risk, and they may push back if you try to shortcut a process that exposes them to a claim.

That friction is the EOR doing its job, not getting in your way, but it surprises managers who expected a frictionless extension of their existing org chart.

How the cost comparison actually works at different headcounts

Setting up a foreign subsidiary runs $5,000 to $25,000 in registration fees, plus $3,000 to $15,000 a year in ongoing costs; add an in-country HR contact and you are past $50,000 per year before a single payslip runs. Global payroll fees on top: $20 to $40 per employee per month.

EOR pricing varies by country and provider but typically lands between $400 and $700 per employee per month for white-collar hires in OECD markets, with higher rates in jurisdictions where the employer liability is heaviest (France, Germany, Brazil) and lower rates in lower-cost markets.

There is no fixed entity overhead because the EOR amortises its infrastructure across hundreds of clients. The crossover: at one to four employees, EOR is almost always cheaper fully loaded. At five to fifteen, it depends on the country. Above twenty, owning the entity usually wins, sometimes by a factor of three.

Compliance responsibility: where the risk sits under each model

Under global payroll, the provider is liable for calculation errors and filing failures within their service scope. They will indemnify you against penalties caused by their mistake.

Under an EOR, the employer-of-record liability sits with the EOR’s entity. If a German court orders the employer to pay six months’ severance, the EOR is the employer. The catch is the indemnity cap and the carve-outs.

Most EOR contracts cap liability at twelve months of fees or a fixed dollar amount, exclude consequential damages, and exclude claims arising from your direction of the worker’s day-to-day activities. Read the limits before you assume the risk has moved.

Permanent establishment risk under both models

Permanent establishment (PE) risk sits separately from employment compliance and bites under either model.

If a senior salesperson based in Singapore is signing contracts on your UK company’s behalf, the Singaporean tax authority may assert that you have a taxable presence in Singapore regardless of who runs payroll.

Owning the entity does not solve this; using an EOR does not solve this. Both models require you to think carefully about what the worker is doing, where, and on whose behalf.

Speed to hire: EOR vs global payroll in practice

With an EOR, a candidate can sign a contract within a week and start within two. The EOR has the entity, the tax registration, and the contract template ready.

Standing up your own entity to run global payroll takes three to nine months in most countries, and longer in some. Germany is roughly four to six months from kickoff to first payslip if you have a clean structure and a responsive notary. France is similar.

Brazil can stretch to nine months. The UK is fast at four to eight weeks for a standard limited company, but the bank-account opening adds a month and the PAYE registration adds another. India is its own conversation.

For a leadership hire who needs to start in six weeks, the choice is made: EOR. For a planned expansion in six months, start the entity work immediately and do not assume migration from EOR is painless.

When global payroll is the right choice

Global payroll wins when the headcount is large enough to amortise entity overhead, the country is one where you have strategic reasons to be a registered employer, and the time to stand up the entity is acceptable. Specifically:

• You already have a registered entity in the country, or are committed to setting one up for non-payroll reasons (sales presence, regulatory licence, manufacturing, IP holding).
• Headcount in the country will exceed fifteen to twenty within twelve months and stay there.
• Your brand matters at the contract level: candidates expect to be employed by your company, not a third party, and the recruitment funnel suffers when they are not.
• You need flexibility on benefits, equity grants, or non-standard contract terms that an EOR’s template will not accommodate.
• The country has a stable labour-law regime your in-house team can manage with a local employment counsel on retainer.

When an EOR is the right choice

EOR wins when the headcount is small, the timeline is short, the country is not strategic enough to justify entity setup, or the country is one where setting up an entity is genuinely punishing. Specifically:

• You are hiring one to five people in a country and have no other reason to be there.
• The hire needs to start in under three months and the entity setup timeline is longer than that.
• You are testing market entry and want to be able to wind down within twelve to eighteen months without dissolving an entity.
• The country has a complex employer regime (Brazil, France, Germany at small scale, parts of Latin America) where EOR pricing is competitive against fully loaded entity costs.
• The hire is a remote knowledge worker, the role does not create permanent-establishment risk, and the worker is comfortable being employed by a third-party entity.

The honest middle case: when neither is obviously right

The genuinely difficult cases are countries where you will have eight to fifteen employees within two years. EOR is expensive at that headcount. Entity setup is slow and the ongoing overhead is meaningful.

The right answer is often to start on EOR, set the entity up in parallel from month three, and migrate when the entity is operational. That requires committing budget to the entity work before the headcount justifies it, which finance teams resist.

Make the case with a five-year cost model, not a three-month one.

A decision framework you can use this week

Run your hiring plan through this sequence before talking to vendors:

• Country by country, what is the three-year headcount trajectory? Anything below five for the duration is EOR territory. Anything above twenty is entity territory. The middle band needs the cost model.
• Do you have a non-payroll reason to be a registered employer in the country? Sales, regulated activity, IP, manufacturing. If yes, owning the entity is the default and global payroll is the right service layer.
• What is the time pressure on the first three hires? Under three months means EOR, almost regardless of the long-term plan.
• What is your in-house tolerance for employment-law risk? If your General Counsel is one person who already has too much on, EOR moves the heaviest cases off the desk. If you have a global mobility and employment team, you can absorb more in-house.
• What does the five-year fully loaded cost look like under each model? Build the model with entity setup, ongoing overhead, EOR fees, and migration costs. Pick the lower curve, not the lower starting price.

If still unsure, the safer first move is EOR. You can migrate to an owned entity later. Standing up an entity prematurely is more expensive and harder to unwind than the reverse.

Frequently asked questions

Is global payroll cheaper than EOR?

Per-employee, yes, often by a factor of ten on the headline price. Fully loaded against entity overhead, it depends on headcount: below five employees, EOR is almost always cheaper; above twenty, global payroll on your own entity wins.

Can I use an EOR for a single contractor?

You can, but you usually should not. EOR carries full employment cost loadings. For a genuine independent contractor, an Agent-of-Record service is cheaper; EOR is right when the worker would fail the local independent-contractor classification test.

Does using an EOR affect my ability to grant equity?

It complicates it. EOR-employed workers are technically employed by a third party, not your granting entity. Reputable EORs have processes to support equity grants, but your plan documents and tax counsel need to bless the structure before the offer goes out.

Can I switch from EOR to my own entity later?

Yes, and it is a common path. The migration is a contractual termination on the EOR and a fresh hire on your entity, with implications for tenure-based benefits. Budget two to three months for the migration of a small team.

What about countries where EOR is legally restricted?

China is the prominent example: the practical workaround (FESCO-style dispatch) is not the same as Western EOR. Press on the legal mechanism in the specific country before you sign, and get a second opinion from local counsel if the answer is vague.

Where does HR sit in an EOR model?

Strategic HR (performance management, culture, compensation philosophy) stays with you. Transactional HR (contracts, leave administration, statutory consultations, terminations) sits with the EOR or is shared. Map the responsibilities in the implementation phase, not after a problem lands.