Hiring Across the EU From an Estonian OÜ: Contractors, Employees and the Misclassification Risk
You run an Estonian OÜ, and you have people in three different countries, all invoicing you monthly like contractors. It works, until you notice that one of them only works for you, uses the laptop you sent, and follows a schedule you set — and that nagging feeling shows up. That feeling is worth listening to, because the label on the contract does not decide the question; what the person actually does, day to day, does.
The short answer
Social security follows the worker’s country of activity, not your company’s country — this is the core rule of EU Regulation 883/2004, and it applies regardless of what the invoice says.
A genuine employee in another EU member state is generally handled under that country’s employment and payroll rules, not Estonia’s — Estonian TSD and the Employment Register only cover people you employ INTO Estonia.
Tax and labour authorities look at substance, not paperwork: control, integration into your business, exclusivity, who supplies the tools, and who bears the financial risk all point toward employee or contractor.
An A1 certificate confirms which country’s social security legislation applies to a worker temporarily active in another EU/EEA country or Switzerland — it does not decide employment status.
A remote employee abroad can, in some circumstances, create a permanent establishment for your Estonian company in their country, tied to where management and decisions actually happen, not to the registry entry.
Your realistic options are local employment, an employer of record, or a genuine independent-business relationship — each has a real cost or a real constraint, and there is no free fourth option.
Why does paying everyone as a contractor feel like it might not be right?
Because in substance, it often isn’t a contractor relationship at all. A contract that says “independent contractor” changes nothing about how a tax authority or labour inspectorate classifies the relationship. They look through the paperwork to the facts: who sets the hours, who can say no to other clients, who owns the laptop, who eats the loss if the work goes wrong. If those facts point to an employment relationship, the country where that person lives and works can treat it as one — with back taxes, back social contributions, and penalties landing on your company.
This is not an Estonia-specific quirk. Every EU member state runs some version of a substance-over-form test for exactly this reason: paying people as contractors is cheaper for the payer and, sometimes, for the worker too, so there is a permanent incentive to mislabel real employment. Tax authorities know this and they are not shy about reclassifying.
What actually decides employee versus contractor status?
No single factor decides it — authorities weigh a cluster of facts about how the work actually happens. The names used most often are control, integration, exclusivity, who provides the tools, and who carries the risk. A relationship that scores “employee” on most of these is very likely to be treated as one, whatever the invoice header says.
Factor | Points toward employee | Points toward genuine contractor |
|---|---|---|
Control | You set hours, method, and daily tasks | They decide how and when the work gets done |
Integration | They’re on your org chart, use your email, attend your standups | They operate as an outside supplier delivering a defined result |
Exclusivity | You are effectively their only client, long-term | They serve multiple clients or are free to |
Tools and equipment | You supply the laptop, software licenses, workspace | They use their own equipment and bear that cost |
Financial risk | They get paid regardless of outcome, like a salary | They can lose money on a bad engagement, invoice for deliverables |
Substitution | The work must be done by that specific person | They could send someone else to do the work |
Permanence | Ongoing, indefinite relationship, renewed automatically | Defined project or fixed term, genuinely ends |
If you read down that table and most boxes land in the left column for someone you’re paying against an invoice, you have a misclassification risk, not a contractor. It doesn’t matter that they asked to invoice you, or that it’s more convenient for both sides — the label doesn’t override the substance.
Where does social security actually apply — Estonia, or the worker’s own country?
It’s almost always the worker’s own country, not the country where your company is registered. EU Regulation 883/2004 coordinates social security across the EU/EEA and Switzerland on a single core principle: a person is covered by only one country’s system at a time, and the default is lex loci laboris — the legislation of the country where the work is actually carried out, regardless of where the employer sits or where the worker lives.
There are two situations founders trip over. First, a person who lives and works entirely in one EU country for a company based in Estonia is, in almost every case, subject to that country’s social security — not Estonia’s — from day one. Second, a person genuinely working across two or more member states follows a more specific rule under Article 13 of the Regulation: broadly, the state of residence applies if a substantial part of the activity happens there, and otherwise the state of the employer’s registered office applies. That second rule has real edge cases, so if you have a genuinely multi-country worker, get a specific ruling for that pair of countries rather than assuming.
Where they live and work | Who they’re paid by | What generally applies |
|---|---|---|
Estonia, full-time | Your Estonian OÜ | Estonian payroll, TSD, Employment Register — standard employee route |
A single other EU country, full-time, employee in substance | Your Estonian OÜ | That country’s employment law and social security, not Estonia’s |
Two or more EU countries, genuinely split work | Your Estonian OÜ | Article 13 of Reg. 883/2004 decides — residence state or employer’s state, check the specific pair |
Outside the EU/EEA/Switzerland (e.g. UK, UAE, Canada) | Your Estonian OÜ | No EU coordination rule applies — check that country’s domestic rules and any bilateral treaty |
A single other EU country, genuinely independent business | Invoicing your OÜ as B2B | Their own country’s self-employment/business rules — not payroll at all |
The company’s country of registration decides almost nothing about where a worker’s social security is owed. The worker’s country of activity decides almost everything.
What does an A1 certificate actually do?
An A1 certificate confirms which single EU/EEA/Swiss country’s social security legislation covers a worker, typically for a business trip or a temporary posting to another member state — it prevents double contributions and gives the worker (and the authorities in the host country) written proof of where contributions are being paid. It is issued by the competent authority in the country whose legislation applies, on request.
An A1 certificate is a social security document, not an employment-status document. It doesn’t make someone an employee, and it doesn’t make someone a contractor — it just settles, for social security purposes, which country’s system is on the hook. You may still need one even for short trips: an employee genuinely based in Estonia who travels to client meetings in Germany or France can need an A1 to cover that travel. For more detail on the underlying coordination rules, the European Commission’s social security coordination pages are the primary EU-level source, and EMTA is the Estonian tax authority to check for the Estonian side of any specific case.
How is hiring someone INTO Estonia different from engaging someone who lives and works elsewhere?
Hiring into Estonia means the full Estonian payroll machinery applies; engaging someone abroad usually means it doesn’t. If you employ someone who genuinely lives and works in Estonia, you register them in the Employment Register (TÖR) before their first working day, run monthly payroll declarations (TSD), and pay social tax at 33% on top of gross salary, subject to the minimum monthly social tax base. That’s the same regime any Estonian employer runs, and it’s the one Enty’s payroll service is built around.
If the same person instead lives and works in, say, Poland or Portugal, none of that Estonian machinery applies to them — because the work isn’t happening in Estonia. What applies instead is Polish or Portuguese employment and social security law, and your Estonian OÜ becomes a foreign employer with local obligations there, which is a very different administrative problem than running Estonian payroll. Confusing the two — assuming that because the company is Estonian, Estonian payroll rules cover everyone on the payroll — is the root of most of the mess described in this article.
Employed in Estonia, living in Estonia: standard Estonian payroll — TÖR, TSD, 33% social tax, 22% income tax, all managed the normal way.
Employed in substance elsewhere in the EU, even if paid by the Estonian company: that country’s payroll and social security rules generally apply, not Estonia’s.
Genuinely self-employed elsewhere, invoicing as B2B: neither country’s payroll rules apply — it’s a commercial relationship, reported as such.
Why is a misclassified foreign ‘contractor’ the expensive version of this mistake?
Because the bill, when it lands, includes years of back contributions, penalties, and interest — not just the correction going forward. If a country’s authority decides that someone you’ve been paying as a contractor for two years was, in substance, an employee, they don’t just ask you to fix it from next month. They can assess employer social security contributions retroactively, sometimes for several years, plus late-payment penalties, plus the withheld income tax the worker should have had deducted at source.
It’s also not a risk you control from Estonia. The authority that reclassifies the relationship is the worker’s own country’s tax office or labour inspectorate — the one with jurisdiction over where the work actually happens. Estonia registering the company, or Enty running clean Estonian bookkeeping, does nothing to shield a genuine employment relationship dressed up as a foreign invoice. The exposure sits with your company as the employer of record in substance, wherever that substance points.
Back social security contributions for the misclassified period, calculated on the payments made.
Back income tax withholding the company should have applied, plus interest.
Administrative penalties for failing to register the worker and file the required declarations.
In some countries, the worker gaining retroactive employee rights — paid leave, notice, severance — that a contractor never had.
Can a remote employee abroad create a permanent establishment for your Estonian company?
Sometimes, yes — but not automatically just because someone works from home in another country. A permanent establishment (PE) is a tax concept: a fixed place through which a company’s business is wholly or partly carried on in a country other than where it’s registered. The OECD updated its Model Tax Convention commentary in 2025 to give clearer guidance specifically on home-office PE risk, introducing a rough threshold: if an employee habitually works from a home office in a foreign country for at least half their working time over a rolling 12-month period, that home office is more likely to be treated as a place of business — and if the activities carried out there are a core part of the business, that can create a PE.
Be honest with yourself about the caveats here. This OECD update is recent, it’s guidance on interpreting existing tax treaties rather than new binding law, and not every country has adopted it, so a specific country pair can still apply older, stricter, or different reasoning. The related and older risk is place of effective management — if the person running the company day-to-day is sitting in another country making the real decisions, some countries will argue the company itself is tax resident there, which is a bigger problem than a PE. Both risks are about substance and control, the same themes as the employee/contractor test above — they’re not separate universes.
In practice, one employee working remotely and reporting to you doesn’t usually tip into PE territory on its own. What raises the risk is that person negotiating and concluding contracts on the company’s behalf, managing other staff, or otherwise acting as if they run a branch of the business from that country. If that’s the shape of the role, get a local opinion for that specific country rather than guessing.
What are your realistic options once you know someone is really an employee?
You have three genuine paths, and none of them is free: local employment, an employer of record, or restructuring the relationship into a real B2B one. Which one fits depends on how long-term the role is, how many countries you’re dealing with, and how much administrative load you’re willing to carry directly.
Register as a local employer in that country. You run local payroll, pay local social security and income tax withholding, and follow local labour law on contracts, leave, and termination. This is the most durable option for a long-term, senior, or exclusive role, but it means learning (or paying someone to learn) a second country’s payroll rules on top of Estonia’s.
Use an employer of record (EOR). An EOR is already a registered local employer in the worker’s country; it employs the person on paper and invoices your OÜ for salary, contributions, and a service fee. It costs real money — typically a monthly per-employee fee on top of the salary and statutory costs — but it removes the local registration burden and the misclassification risk in one move. Be honest with the person hiring: it costs more than a contractor invoice, and that’s the price of doing it correctly.
Restructure into a genuine independent-business relationship. If the work can actually be organized as a defined deliverable, with the person free to work for other clients, using their own tools, and bearing real commercial risk, a proper B2B contract is legitimate and normal — this is not a workaround, it’s simply accurate if the substance supports it. The test is the same table from earlier in this article: if most factors genuinely point to “contractor,” a contractor relationship is fine.
What doesn’t work as a long-term fix is doing nothing and hoping the invoice format is enough. A genuine contractor relationship is genuinely fine — plenty of founders build teams this way correctly, with real freelancers who have other clients and control their own work. The problem is only ever the gap between the label and the substance, and that gap is exactly what a tax authority is trained to find.
How does this connect back to running the Estonian side cleanly?
Getting the Estonian side right doesn’t insulate the rest of the structure, but it does mean one fewer place for something to go wrong. People you hire directly into Estonia — living and working there — go through the standard TÖR registration, monthly TSD filing, and social tax obligations, and that part is genuinely straightforward to run correctly with the right bookkeeping support. The harder judgment calls are always about the people who aren’t in Estonia, which is exactly why this article exists.
If you’re incorporating fresh and building a team across several countries from the start, it’s worth mapping out, country by country, who will actually be an employee in substance before you sign a single contract — not after a tax authority asks. That one exercise, done early, is far cheaper than any of the fixes above.
Frequently asked questions
Does it matter what the contract calls the person — employee or contractor?
No, not on its own. Tax and labour authorities classify the relationship by its substance — control, integration, exclusivity, tools, and financial risk — not by the label on the contract or invoice. A contract calling someone a contractor doesn’t protect you if the actual working relationship looks like employment.
If I pay someone through my Estonian OÜ, does Estonian social tax apply to them?
Only if the work is actually being carried out in Estonia. Social security generally follows the country where the person lives and works, not the country where the paying company is registered — this is the core rule of EU Regulation 883/2004 for people active within the EU/EEA and Switzerland.
What is an A1 certificate and do I need one?
An A1 certificate confirms which single country’s social security legislation covers a worker who is temporarily active in another EU/EEA/Swiss country, avoiding double contributions. You may need one even for an Estonia-based employee travelling for short work trips elsewhere in the EU — check with the relevant social insurance authority for the specific trip.
What happens if a country decides my ‘contractor’ is actually an employee?
That country’s authority can assess back social security contributions, back income tax withholding, and penalties, sometimes covering several past years, plus interest. The worker may also gain retroactive employment rights such as paid leave or notice, depending on that country’s law.
Can my Estonian company just hire someone in another EU country directly?
Not through Estonian payroll — if that person genuinely lives and works there as an employee, that country’s employment and social security rules apply, which usually means registering as a local employer, using an employer of record, or restructuring into a genuine B2B relationship.
Does having one remote employee abroad automatically create a permanent establishment?
No. A single remote employee doing ordinary work doesn’t automatically create a permanent establishment. The risk rises when that person negotiates contracts, manages the business, or works from a home office for a large share of their time — the OECD’s 2025 guidance uses a rough 50%-of-working-time reference point, but adoption varies by country, so check the specific pair of countries involved.
Is an employer of record worth the cost for just one person?
It depends on how long-term and senior the role is. An EOR costs a monthly fee on top of salary and local statutory costs, which is real money — but for one important, ongoing, employee-in-substance role, it’s usually cheaper than the retroactive bill from a misclassification finding, and far less work than registering as a local employer yourself.
Is a genuine freelance contractor relationship actually risky, or is this only about disguised employees?
A genuine contractor relationship is genuinely fine and common — the risk only exists in the gap between the label and the substance. If the person has other clients, controls their own hours and methods, uses their own tools, and bears real commercial risk, a proper B2B contract reflects reality and doesn’t need to change.
Does this apply the same way for someone outside the EU, like in the UK, the UAE, or Canada?
No — EU Regulation 883/2004 only coordinates social security within the EU/EEA and Switzerland. For a worker outside that zone, you’re looking at that country’s domestic employment and tax rules plus any bilateral social security or tax treaty Estonia has with it, and those vary a lot by country, so check the specific one rather than assuming EU logic applies.
