Entity vs EOR vs payroll registration in Europe: a decision matrix
Why this decision is bigger than hiring
When you decide how to employ someone in a new European country, you are making a structural decision about who owns the legal employer relationship, how your payroll model operates in that market, and how much complexity you are taking on or handing off at this stage of your expansion.
Get it right and you move quickly, stay compliant, and keep your options open. Get it wrong and you spend the next 12 months unwinding a model that no longer fits, or carrying costs and admin that were never justified for your headcount.
There are three main routes available to companies hiring in Europe, each with different legal, financial, and operational implications. The right choice in one country is not automatically the right choice in another. This article walks through all three, compares them on the factors that matter most, and gives you a practical framework for deciding which model fits your situation by country and by stage of growth.
The three routes in plain English
Setting up a local entity
A local entity means incorporating a legal presence in the target country, typically a subsidiary or branch. Your company, through that entity, becomes the legal employer. You handle payroll, tax withholding, social security contributions, and employment compliance directly under local law.
An entity also provides you with broader commercial capabilities. You can contract locally, invoice in-country, and build a full operational presence. That makes it the most complete route, but also the most demanding to set up and run.
Using an Employer of Record
An Employer of Record, or EOR, is a third-party organisation that becomes the legal employer in the country on your behalf. Your hire works for you day-to-day, but the employment contract sits with the EOR. The EOR manages payroll, benefits administration, statutory contributions, and local compliance.
You pay a per-employee fee. In return, the legal employer relationship and the associated compliance burden transfer to the EOR. It is worth being clear about one thing here: EOR terms and the degree of local compliance they can offer vary across European countries. An EOR operating in France is navigating a significantly different legal environment to one operating in Poland.
Foreign employer registration
Foreign employer registration means your company remains the legal employer but registers locally with the relevant tax and social security authorities to meet its payroll-related obligations in that country. No full local entity is created.
This route is narrower in scope than entity setup, covering employment and payroll compliance rather than broader commercial activity. It is also not uniformly available across Europe, and where it is available the registration requirements and ongoing obligations differ by country.
One distinction worth making explicit: a payroll provider processes pay on your behalf but does not change who the legal employer is. Foreign employer registration keeps legal employer status with your company and requires you to manage local compliance directly, typically with local advisors.
For more on this route, see our guide to hiring global talent abroad without a local company (including direct employment / foreign employer registration).
What you are really deciding
The choice between these three routes comes down to four trade-offs that play out differently depending on your company's stage, headcount, and target markets.
Control versus speed
An entity gives you direct control over payroll, benefits, and employment terms but takes time to set up, sometimes weeks, sometimes months depending on the country. An EOR gets you to your first hire in days to weeks, but employment terms are mediated through a third party. Foreign employer registration sits in between: you retain direct employer status, but the registration process takes time and requires local expertise.
Fixed cost versus flexibility
Entity setup involves upfront investment and ongoing fixed operating costs regardless of headcount. EOR fees are variable and cost-efficient at low headcount but increasingly expensive as your team grows. Payroll registration typically involves lower upfront costs than entity setup, but the ongoing compliance burden is yours to carry.
Direct liability versus outsourced risk
With an entity or direct registration, your company owns the legal employer relationship and everything that comes with it. Misclassification, a poorly handled dismissal, or a missed statutory payment is your liability to resolve. With an EOR, those obligations transfer to the provider. That is a meaningful risk transfer, particularly in countries with complex labour law, but it comes at a cost and involves dependency on a third party's compliance standards.
Internal bandwidth
This one is underweighted in most comparisons. Running payroll and employment compliance in a foreign country requires internal capacity or reliable external advisors. If your HR, legal, and finance functions are already stretched, EOR removes a significant operational burden. If you have the infrastructure or are building it, the case for direct control strengthens.
The Europe decision matrix
The table below compares all three routes across the factors that typically drive this decision. It is a starting point for structuring your thinking, not a substitute for country-level assessment.
| Factor | Local entity | EOR | Foreign employer registration |
|---|---|---|---|
| Legal employer | Your entity | EOR provider | Your company |
| Setup burden | High | Low | Medium |
| Speed to first hire | Slow (weeks to months) | Fast (days to weeks) | Medium (varies by country) |
| Upfront cost | High | Low to medium | Low to medium |
| Ongoing operating burden | High | Low to medium | Medium (compliance stays with you) |
| Control over payroll and benefits | Full | Limited | Full (with local obligations) |
| Scalability | Strong once established | Efficient at low headcount | Variable |
| Tax and PE sensitivity | Low risk if structured correctly | Generally low risk | Requires careful structuring |
| Best fit | Permanent teams, broader local operations | First hires, speed, market testing | Direct employer model, limited headcount, no entity yet — direct employment without a local entity |
No single route wins across every row. The right answer depends on how many people you are hiring, how quickly you need to move, how long you plan to stay in the market, and what your team can realistically manage.
When an entity makes sense
Entity setup is the right answer when you are making a long-term commitment to a market, not testing it.
The clearest signal is headcount. When you are building a team of five or more people in a single country, the per-employee EOR fees that made sense at one or two hires become harder to justify. At that point, the fixed cost of an entity spread across a growing team often compares favourably.
Beyond cost, there are situations where an entity is simply necessary. If you need to contract with local clients, invoice in-country, or build a commercial presence that goes beyond employment, a foreign employer registration will not cover you and an EOR was never designed for that purpose.
Control is another driver. With an entity, you set the employment terms, manage payroll directly, and make decisions about benefits and compensation without routing them through a third party.
One honest caveat: entity setup timelines vary significantly by country. Some markets are straightforward; others involve multiple registrations and processes that run to several months. If you have already tested a market through an EOR and know the hire is permanent, the question is not whether to set up an entity but when and how to do it without disrupting your existing team.
When EOR makes sense
Using an Employer of Record service provider is the right starting point when speed, simplicity, and low upfront commitment matter more than long-term cost optimisation.
The most common use case is the first hire in a new country. You have identified someone you want to bring on, the market looks promising, but you are not ready to incorporate locally and do not have the internal infrastructure to manage foreign payroll compliance. An EOR lets you move in days to weeks, with the legal employer relationship and compliance obligations handled by a provider who already has local infrastructure in place.
It also makes sense when your internal teams do not have bandwidth for another country's employment obligations. Running compliant payroll in France or Germany is not a light administrative task.
EOR works well for market testing too. Running one or two hires through an EOR before committing to entity setup gives you real operational data without locking in fixed costs. If the market does not develop as expected, winding down is significantly simpler than closing an entity.
The important caveat is that EOR is not a permanent default. Costs accumulate at scale and you are dependent on the EOR's compliance standards and ability to administer benefits in line with local norms. Build a review trigger in from the start, whether that is a headcount threshold, a cost comparison at the 12-month mark, or a planned reassessment tied to your expansion timeline.
When payroll registration can work
Foreign employer registration can be a useful option, though it's often overlooked. It allows your company to be the direct legal employer without needing a local entity. If you want control over employment terms, payroll, and benefits, and if setting up a local entity seems too complex for your current needs, this registration could be a good choice in some countries.
This option works best when the target country allows foreign employer registration, you are willing to manage compliance regarding local payroll rules and tax obligations, and your number of hires is low enough to make compliance manageable.
However, this is not a simplified version of Employer of Record (EOR) services. Compliance responsibility remains with you, and it does not enable local contracting or commercial presence. Companies wanting direct hires, reliable local advisors, and not yet ready for entity setup should consider this option alongside others.
Country-specific feasibility across key European markets
Employer registration requirements, payroll obligations, and the practical availability of each route differ across European countries. The table below gives a working picture across our key markets. It is intended to help you assess feasibility, not replace local legal advice.
| Country | Foreign employer / payroll registration possible? | Main registrations typically involved | EOR note | When entity becomes more attractive | Watch out for |
|---|---|---|---|---|---|
| Netherlands | Generally yes | Belastingdienst (tax), UWV (social insurance) | Competitive EOR market; widely used for first hires | 5+ hires; entity often efficient at scale | Wage tax and social security complexity; 30% ruling implications for expat hires |
| Germany | Possible with careful structuring | Finanzamt (tax), Deutsche Rentenversicherung (social security) | Available; local employment law is detailed | Generally from 5 to 8 hires onward | Works council triggers; co-determination rules at certain headcount thresholds |
| Belgium | Possible but complex | ONSS/RSZ (social security), SPF Finances (payroll tax) | Commonly used as a first-hire route given complexity | Required for local contracting or broader commercial activity | High employer social costs; one of the more complex payroll environments in Europe |
| France | Possible in limited cases | URSSAF (social contributions), impots.gouv.fr (tax) | Widely used given the complexity of French labour law | From first permanent hires where full entity rights are needed | Strong worker protections; dismissal procedures are formal and closely regulated |
| Spain | Generally possible | Seguridad Social / TGSS, Agencia Tributaria (AEAT) | Available; EOR market growing | When building a team beyond 3 to 5 hires | Collective agreements apply by sector and can significantly affect employment terms |
| Italy | Technically possible; rarely straightforward | INPS (social security), INAIL (workplace insurance), Agenzia delle Entrate (tax) | EOR often preferred given administrative complexity | When commercial activity requires a full Italian presence | Complex payroll; strong worker protections; formal dismissal rules |
| Hungary | Possible | NAV (tax and social insurance) | Available; less developed than Western European markets | Lower cost base can make entity setup viable sooner | Cross-border structuring requires careful attention to local rules |
| Poland | Possible | ZUS (social security), Krajowa Administracja Skarbowa (tax) | Commonly used for first hires in a growing tech and services hub | Entity often follows quickly as teams scale | ZUS filing complexity; local payroll expertise required |
| Czechia | Possible | ČSSZ (social security), Finanční správa (tax) | Available; market less saturated than Western Europe | Entity efficient for medium-sized teams | Documentation requirements; local payroll expertise needed |
| Portugal | Possible | AT (tax), Segurança Social | Widely used; growing destination for international teams | Entity straightforward; increasingly common for scaling teams | NHR tax regime changes affect compensation planning for international hires |
| United Kingdom | Yes, post-Brexit own regime | HMRC PAYE and National Insurance registration | Well-established market; clear legal framework | When local commercial presence is needed | Post-Brexit: separate from EU rules; IR35 applies to contractor engagements |
| Sweden | Possible with advisors | Skatteverket (tax and employer registration), social insurance | Available; used by companies testing the Swedish market | When a permanent team warrants a Swedish entity | High employer social contribution costs; detailed reporting obligations |
| Romania | Possible | ANAF (tax), Casa Națională de Pensii Publice (social insurance) | Growing market; increasing interest from international companies | Lower cost base makes entity viable sooner | Local payroll provider quality varies; due diligence on advisors matters |
Common mistakes when choosing a hiring model
Choosing based on headline cost alone
EOR fees look clear and comparable in a spreadsheet. But the full cost picture includes setup, ongoing operating costs, internal time spent managing the relationship, and transition costs if you change model later. Running the numbers at your projected 12 and 24-month headcount, not just your current one, gives you a more accurate basis for the decision.
Assuming payroll registration is a lighter version of EOR
With EOR, the compliance responsibility transfers to the provider. With foreign employer registration, your company remains the legal employer and owns those obligations directly. Going into this route without local advisors or a clear understanding of what local payroll and social security compliance requires is where companies run into difficulty.
Staying on EOR too long without a review trigger
EOR is a sensible starting point in most markets. It becomes a problem when it becomes a permanent default through inertia. Without a defined review point tied to headcount, cost, or time in market, companies often stay on EOR well past the point where entity setup would have made more sense.
Treating Europe as one compliance environment
France, Poland, and the Netherlands require materially different approaches to employment, payroll, and registration. Worker protections, dismissal rules, social contribution rates, and the practical availability of foreign employer registration all differ by country. A model that works cleanly in one market may be significantly more complex, or simply unavailable, in another.
A simple decision checklist
Choose an entity if:
- You are building a team of five or more people in a country
- You need to contract locally or invoice in-country
- You have a long-term commercial commitment to the market
- Your projected EOR costs at 12 to 24 months justify the switch
- You have already tested the market and are ready to commit
Choose EOR if:
- You are placing your first one or two hires in a new country
- Speed to hire matters more than cost optimisation right now
- Your internal team does not have capacity to manage foreign payroll compliance
- You are testing a market before making a longer-term commitment
- Entity setup timelines do not fit your hiring deadline
Choose payroll registration if:
- You want to be the direct legal employer without setting up a full entity
- The target country permits foreign employer registration
- You have access to reliable local payroll and compliance advisors
- Your hire volume is low enough that managing compliance directly is realistic
- You need direct control over employment terms and benefits
Not sure which applies to your situation? We can help identify the right hiring model for your next 12 to 24-month expansion plan. Contact our team.
Making the right call for your markets
The decision between entity, EOR, and foreign employer registration comes down to where you are in your expansion, what your team can manage, and what each market actually requires.
There is no universally correct answer. A company placing its first hire in Amsterdam faces a different decision to one building a 15-person team in Warsaw or testing demand in Milan for the first time. What tends to go wrong is treating this as a one-time decision rather than one that needs revisiting. Markets develop, headcount grows, and costs accumulate. The route that was right at two hires is often not right at ten.
The country-level detail matters too. Getting that assessment right early saves significant rework later.
