| Key Takeaways | |
|---|---|
| Most payroll RFPs start one step too late. The operating model — who is legally the employer, and who runs the entity — decides what a vendor can actually do for you, before any vendor is even shortlisted. | |
| There are four working models: in-house local entities, a global payroll aggregator layered on entities you already own, an Employer of Record (EOR), and a fully outsourced payroll BPO running your own entity for you. | |
| The model question and the vendor question are separate decisions made in the wrong order more often than not — teams compare EOR pricing against payroll-software pricing as if they were substitutes, when they solve different problems. | |
| Headcount per country is the single strongest signal for which model fits: one or two hires in a new market rarely justify entity setup, while ten or more usually do. | |
| Switching operating models later — for example moving from EOR to your own entity once headcount grows — is a real, plannable transition, not a sign the first choice was wrong. Explore our EOR solution → | |
In This Guide
- The Real Question Isn't "Which Vendor" — It's "Which Operating Model"
- The Four Operating Models for International Payroll
- Model 1: In-House Local Entities
- Model 2: Global Payroll Aggregator on Top of Your Entities
- Model 3: Employer of Record (EOR)
- Model 4: Fully Outsourced Payroll (BPO) With Your Own Entity
- A Decision Framework: Matching Model to Company Stage
- Once You've Picked a Model, Here's What to Screen Vendors For
- FAQs
Most international payroll searches start with a spreadsheet of vendors: pricing per payslip, countries covered, integrations, support hours. That spreadsheet answers a real question, but the wrong one to ask first. The question that actually determines whether a vendor can help you is structural — who is the legal employer of record in each country, and who owns the entity the payroll runs through — and it has nothing to do with any single vendor's feature set.
This matters more in 2026 than it used to. The payroll market now blends four genuinely different operating models under similar-sounding marketing language: "global payroll," "employer of record," "payroll outsourcing," and "unified payroll platform" are often used almost interchangeably in vendor decks, even though they describe different legal arrangements with different cost structures and different failure modes.
This guide walks through the four operating models available to you, when each one fits, and how to build a decision framework around headcount, entity ownership, and growth plans before you ever open a vendor comparison sheet. For the product mechanics once you've settled on a model, see our guides to Employer of Record and Global Payroll.
1. The Real Question Isn't "Which Vendor" — It's "Which Operating Model"
The mistake
Most teams evaluating "international payroll providers" are actually comparing across two different layers of the problem at once: the operating model (who is legally responsible for employment and compliance in each country) and the vendor or software running on top of that model. Because both layers get pitched by the same sales teams using overlapping language, it's easy to end up comparing an EOR's all-in monthly fee against a payroll aggregator's per-payslip price as if they were the same purchase decision.
Why the order matters
An operating model decision is structural and expensive to reverse — it involves who signs the employment contract, whose entity carries the statutory liability, and how quickly you can start or stop employing someone in a given country. A vendor decision inside a chosen model — which specific EOR, which specific payroll software — is comparatively low-stakes and easy to revisit. Doing the structural decision first, and the vendor comparison second, avoids the common outcome of picking a vendor that's excellent at a model you didn't actually need.
A company hiring its first two employees in a new country requests proposals from three "global payroll providers." One quotes a per-payslip aggregator fee assuming the company already has a local entity. One quotes an EOR's all-in monthly fee. One quotes a payroll BPO's setup-plus-monthly fee assuming an entity will be incorporated. All three numbers look comparable on a spreadsheet — but only one of the three underlying models is available to a company with no local entity and only two hires.
What to do instead
Answer the operating-model question first, using the framework in Section 7, then shortlist vendors only within that model. This single change in order removes most of the confusion that shows up later in procurement conversations.
2. The Four Operating Models for International Payroll
Every international payroll arrangement reduces to one of four models, distinguished by two questions: does your company hold a local legal entity in the country, and who is the legal employer of record for the people working there.
| Model | Local entity needed | Legal employer | Best fit |
|---|---|---|---|
| 1. In-house local entities | Yes, in every country | Your own entity | High headcount, long-term commitment to the market |
| 2. Global payroll aggregator | Yes — aggregator runs payroll on top of it | Your own entity | You already have entities, want one unified payroll interface |
| 3. Employer of Record (EOR) | No | The EOR | Low headcount, market testing, no entity yet |
| 4. Fully outsourced payroll (BPO) | Yes | Your own entity | You want the entity but not the in-house payroll operations team |
Notice that three of the four models still require you to hold a local entity — the entity question, not the payroll-software question, is what most sharply divides the options. Models 1, 2, and 4 differ mainly in who operates payroll on top of your entity: your own team, a software platform, or an outsourced operations team. Model 3 is the only one that removes the entity requirement entirely, by shifting legal employership to the EOR.
3. Model 1: In-House Local Entities
How it works
Your company incorporates a legal entity in each country, registers with the local tax and social security authorities, and either runs payroll manually or licenses local payroll software, with your own HR and finance staff operating it directly.
What this means in practice
This model gives you the most direct control over employment terms, benefits design, and how closely payroll integrates with your existing HR systems. It also carries the most fixed overhead: entity incorporation, statutory filings, local accounting, and the in-house expertise to keep pace with regulatory change in every country you operate in. The cost of a compliance mistake — a missed filing, a misclassified benefit — sits entirely with your own team.
- Fits when: headcount per country is high enough (commonly cited industry benchmarks put this around 15–20+ employees) to justify the fixed cost of an entity and an internal team.
- Fits when: the market is a long-term, strategic operating base rather than a test.
- Doesn't fit when: you're hiring one or two people to validate a market before committing further.
What to look for
If you're already running this model, the honest question is whether the fixed cost per country is still earning its keep as headcount shifts — a country that made sense in-house at 30 employees may not still make sense at 6, after a reorganization.
4. Model 2: Global Payroll Aggregator on Top of Your Entities
How it works
You keep your own local entities, but instead of running each country's payroll separately, a single aggregator platform connects to local payroll partners or processors in each country and gives you one dashboard, one data format, and often one point of contact across markets.
What this means in practice
This model solves an operational problem — fragmented systems and inconsistent reporting across countries — without changing who's legally responsible for compliance. You (through your entities) remain the legal employer everywhere; the aggregator is a software and coordination layer, not a risk-transfer mechanism. That distinction matters because it's easy to assume "global payroll" means someone else carries the compliance liability, when in this model it doesn't.
Ask any aggregator directly: "In a compliance failure in Country X, whose entity is liable?" A model 2 answer is always "yours." If a vendor's answer is unclear on this point, they may be blending aggregator and EOR services in the pitch — worth clarifying before you sign anything.
- Fits when: you already hold entities in most of your target countries and the pain point is fragmented reporting, not entity ownership.
- Fits when: you want a single vendor relationship for payroll operations without giving up direct entity control.
- Doesn't fit when: you don't yet have an entity in a country you're trying to hire in — the aggregator has nothing to connect to.
5. Model 3: Employer of Record (EOR)
How it works
An EOR is already a registered legal employer in the country. It hires your candidate on your behalf, runs payroll, handles statutory contributions and tax withholding, and carries the compliance liability — while the person works under your day-to-day direction, same as any other employee.
What this means in practice
This is the only one of the four models that removes the entity requirement entirely. That makes it the fastest route to a compliant hire in a new country — often measured in days rather than the months an entity setup can take — and the only model that scales down cleanly if a single hire doesn't work out. The trade-off is a per-employee fee that's usually higher, per head, than running the equivalent hire through your own entity at scale, and less direct control over benefits design in some markets.
Incorporating and maintaining a single-country entity commonly runs from the low tens of thousands of dollars upward in first-year setup and ongoing statutory/accounting costs, before a single employee is hired. An EOR converts that fixed cost into a per-employee monthly fee instead — which is why the crossover point, where an entity becomes cheaper than an EOR, is a headcount question, not a philosophy question.
- Fits when: you're hiring your first one to a handful of employees in a new country.
- Fits when: you're testing a market and want to preserve the option to exit cleanly.
- Doesn't fit when: headcount in that country has grown past the point where a dedicated entity would be cheaper on a per-head basis.
What to look for
Confirm the EOR is a registered legal employer in the specific country you need — not just a reseller sitting on top of a local partner's entity, since that adds a layer of indirection to accountability if something goes wrong.
6. Model 4: Fully Outsourced Payroll (BPO) With Your Own Entity
How it works
You hold the local entity and remain the legal employer, but hand the entire payroll operation — calculation, filings, payslips, statutory submissions — to a specialist outsourced provider, rather than running it with in-house staff or an aggregator dashboard.
What this means in practice
Compliance liability still sits with your entity, so this model doesn't reduce legal risk the way an EOR does — but it removes the operational burden of running payroll day to day, which can matter a great deal in countries with unusually complex or fast-changing filing requirements. It tends to suit companies that have already decided the entity is worth keeping, but don't want to build or retain in-house payroll expertise for every country on the list.
- Fits when: you're committed to the entity but the local payroll rules are complex enough that in-house administration is a poor use of internal headcount.
- Fits when: you want predictable, hands-off payroll processing without giving up the entity or the direct-employer relationship.
- Doesn't fit when: you don't have an entity yet — this model assumes one already exists or is being incorporated regardless.
Not sure which of these four fits your current headcount and roadmap?
Our team can map your specific country list against headcount, timeline, and growth plans before you shortlist a single vendor.
7. A Decision Framework: Matching Model to Company Stage
The four models map reasonably cleanly onto company stage and per-country headcount. Use the table below as a starting filter, then confirm the fit against your specific growth plan for that country — a market you plan to scale aggressively deserves a different answer than one you're only testing.
| Situation | Recommended starting model | Why |
|---|---|---|
| First 1–3 hires in a brand-new country, market still unproven | Employer of Record | Fastest compliant start, lowest fixed cost, clean exit if the market doesn't work out |
| 4–15 hires, market validated, growth plan still uncertain | EOR, reassessed against entity setup cost annually | Headcount is approaching the crossover point but not reliably past it yet |
| 15+ hires, long-term strategic market | In-house entity or outsourced BPO | Fixed entity costs are now spread across enough headcount to beat per-employee EOR fees |
| Already hold entities in most countries, want unified reporting | Global payroll aggregator | Solves the operational fragmentation problem without disturbing entity ownership |
| Committed to the entity, payroll complexity is the pain point | Outsourced payroll (BPO) | Keeps legal employer status in-house while removing day-to-day payroll administration |
Treating the model choice as permanent. Companies routinely start a country on EOR and move to their own entity once headcount clears the crossover point — and just as often move the other way, converting a shrinking entity back to EOR rather than keep absorbing fixed compliance overhead for two remaining employees. Neither direction is a failure; it's the model doing its job as headcount changes.
8. Once You've Picked a Model, Here's What to Screen Vendors For
Only after the operating model is settled does a vendor comparison become a like-for-like exercise. What to check differs by model:
- If EOR: confirm they're a registered legal employer (not a reseller) in every country on your list, ask for their typical time-to-first-payslip, and get clarity on what happens contractually if you later want to convert the employee to your own entity.
- If aggregator: confirm which countries are run on their own processing versus a third-party local partner underneath, since support quality often depends on that distinction.
- If in-house or BPO: ask how the provider (or your own team) tracks regulatory change — filing deadlines and contribution rates shift most years, and the failure mode here is usually a missed update, not a dramatic one-time error.
- Across all models: ask for two reference customers at a similar headcount-per-country profile to yours, not just logos — a vendor that's excellent at 500-person clients may be a poor fit for your 8-person country office.
Choose the Model First, and the Right Vendor Becomes an Easy Call
Map Your Global Payroll Strategy
Book a free consultation with our team to work through the operating model for each country on your hiring roadmap.
International Payroll Provider FAQs: Operating Models, EOR, and Vendor Selection
Q1. What's the difference between an EOR and a global payroll provider?
An Employer of Record (EOR) is the legal employer for your hire in a given country, which means it carries statutory compliance liability and requires no local entity from you. A global payroll provider — often called an aggregator — instead runs payroll on top of an entity you already own, so you remain the legal employer throughout. They solve different problems: an EOR replaces the need for an entity, while a payroll aggregator makes an entity you already hold easier to operate. Comparing their pricing side by side only makes sense once you've decided which of the two structural roles you actually need.
Q2. How many employees justify setting up a local entity instead of using an EOR?
There's no single legal threshold, but the practical crossover point is usually where per-employee EOR fees, multiplied by headcount, exceed the fixed cost of incorporating and maintaining an entity. For many markets this lands somewhere in the range of 10 to 20 employees, though it varies by country's incorporation cost, statutory complexity, and how quickly you expect headcount to keep growing. Companies planning aggressive growth in a market sometimes set up the entity earlier than the pure cost crossover would suggest, to avoid a disruptive mid-growth transition later.
Q3. Can we switch from an EOR to our own entity later without disrupting employees?
Yes, this is a common and plannable transition. It typically involves incorporating the new entity, then transferring each employee's contract from the EOR to the new entity on an agreed date, with continuity of service, benefits, and tenure preserved as part of the transfer terms. The main planning work is sequencing it so payroll, benefits, and statutory registrations are all active on the new entity before the EOR relationship for those employees ends, so there's no gap in compliant employment.
Q4. Does using a payroll aggregator reduce our compliance liability?
No. In the aggregator model, your own entity remains the legal employer in every country, so your company retains full compliance liability regardless of which software or coordination layer is running the payroll process. An aggregator can reduce the operational risk of manual errors and inconsistent processes across countries, but it does not transfer legal responsibility the way an Employer of Record does. If reducing liability itself is the goal, that points toward the EOR model rather than an aggregator.
Q5. What questions should we ask an EOR before signing a contract?
Confirm they are a directly registered legal employer in each specific country you need, rather than a reseller operating through a third-party local partner, since that extra layer can slow down support and blur accountability. Ask for a typical timeline from signed offer to first payslip, get written clarity on the process and cost for converting an employee to your own entity later, and request references from companies with a similar headcount-per-country profile to yours rather than their largest logos.
Q6. Is fully outsourced payroll (BPO) the same as using an EOR?
No. In a fully outsourced payroll arrangement, you still hold the local entity and remain the legal employer — you're only handing off the day-to-day payroll administration to a specialist provider. An EOR, by contrast, is itself the legal employer, and no entity is required from you at all. The BPO model suits companies that have already decided to keep the entity but want to stop running payroll operations internally; the EOR model suits companies that don't want the entity in the first place.
Q7. How does Slasify fit across these four operating models?
Slasify operates primarily as an Employer of Record, hiring on your behalf across 150+ countries through our own entities and local partner network, so you can start compliant employment without incorporating first. For companies that already hold entities and want unified payroll operations instead, our Global Payroll service covers the aggregator and outsourced-processing side of this framework. Either way, the starting point is the same conversation: mapping your headcount and growth plan per country before recommending a model.