EOR или дочерняя компания: открывать юридическое лицо или работать через Employer of Record?

You’ve found a strong candidate in a country where you have no legal presence. Or you’re testing a new market and want to hire two or three people locally before committing to anything long-term. Either way, the same question comes up: do you establish a subsidiary, or do you work through an Employer of Record?

Both paths are legitimate. Both have real trade-offs. What’s less useful is treating this as a purely administrative decision — because the structure you choose will shape how fast you can move, how much legal risk you carry, and how expensive it is to change course later.

This article breaks down how the two models actually work, where each one fits, and what to watch out for on either side.

What’s the difference?

A subsidiary is a legal entity you own and register in the target country. It gives you full employer status, the ability to contract locally, and complete control over HR and benefits. It also comes with registration fees, local accounting obligations, ongoing compliance costs, and — if things don’t work out — a complicated wind-down process.

An Employer of Record is a third-party organization that legally employs your workers on your behalf. The EOR handles payroll, contracts, taxes, and local compliance. You retain control over the team’s work — the EOR handles the paperwork and legal exposure. There’s no entity to register and no permanent infrastructure to maintain.

Here’s how the two compare across the factors that matter most:

	EOR	Subsidiary
Setup time	Days to weeks	3–6+ months
Upfront cost	Low (monthly fee)	High (legal, registration, admin)
Compliance liability	Carried by the EOR	Carried by your company
Best for	1–10 employees, market testing	10+ employees, long-term commitment
Control over benefits	Limited to EOR offerings	Full flexibility
Exit flexibility	High — cancel the contract	Low — entity dissolution is complex
Revenue/contracting locally	May require entity depending on jurisdiction	Fully supports local contracting

When an EOR is the right call

Speed is the most obvious reason to use an EOR. Registering a legal entity — even in a relatively straightforward jurisdiction — typically takes three to six months. Opening bank accounts, appointing local directors, registering with tax authorities: the steps add up. An EOR can have your first hire onboarded in weeks.

But speed isn’t the only factor. These are the scenarios where EOR consistently makes more sense:

• You’re entering a new market for the first time and aren’t yet certain it warrants long-term investment.
• Your local headcount is small — typically under ten people. At that scale, the overhead of running a subsidiary almost always exceeds the cost of an EOR.
• You need to hire quickly, and losing a candidate to a slow legal setup process isn’t an option.
• You want to build an offshore development team or outstaffing arrangement without the full administrative weight of entity ownership.
• Your business model doesn’t require local contracting or revenue generation in that country — at least not yet.

When a subsidiary makes more sense

There are situations where an EOR is not the right long-term answer, and it’s worth being clear about them.

If you’re planning to hire more than ten people in a country, the math usually shifts. The per-employee monthly fee of an EOR begins to outweigh the fixed costs of running your own entity. At that scale, a subsidiary also gives you more control: over benefits design, over employment terms, over how your brand is perceived as an employer.

• You plan to generate revenue or sign local contracts in that country — some jurisdictions require an entity for this.
• Long-term workforce planning is already in place, with stable headcount projections.
• Your employer brand in-market matters, and you want direct employment relationships.
• You have the internal resources (legal, finance, HR) to manage local compliance on an ongoing basis.

The hidden costs of each path

Neither option is free of friction. The comparison looks cleaner on paper than it does in practice.

With a subsidiary, the headline costs — registration fees, legal counsel, notarization — are visible from the start. What tends to catch companies off guard is the ongoing cost: local accountants, annual filings, director fees if required, and the time your internal team spends on coordination. If the market doesn’t work out, closing a legal entity is often more expensive and slower than opening one.

With an EOR, the costs are more predictable — a monthly fee per employee — but there are trade-offs in flexibility. You’re working within the benefit structures the EOR offers, which may not match exactly what you’d design yourself. In some jurisdictions, there can also be questions about the permanence of the arrangement if it runs for several years without an entity being established.

Neither of these is a reason to avoid one model or the other. They’re just worth factoring into the decision before you’re already committed.

A practical decision framework

If you’re unsure which structure fits your situation, these questions tend to clarify things quickly:

If…	Then…
< 10 hires planned?	Start with EOR
Need local revenue/contracts?	Entity likely required
Still validating the market?	EOR — preserve flexibility
Speed is critical?	EOR wins on time-to-hire
No internal compliance capacity?	EOR absorbs the burden

The most common pattern for fast-growing tech companies is to start with an EOR, prove the market, grow the team past the threshold where a subsidiary becomes cost-effective, and then transition. The two aren’t mutually exclusive — they’re often sequential.

Country-level data on registration costs and timelines from the World Bank’s Doing Business archive can also help frame how much the subsidiary commitment actually involves in a given jurisdiction — figures vary more than most people expect.

How Eor.by fits into both stages

Eor.by works with IT companies and international businesses at both points in that journey. The core service is EOR — legal employment, payroll, compliance, and HR administration for teams based in Belarus and the wider region. But the in-house legal team also supports companies thinking further ahead: entity structure questions, HTP park registration, and the transition from EOR to owned entity when the time is right.

For companies building offshore development teams or outstaffing arrangements, the combination of EOR infrastructure and IT-specific expertise makes the setup straightforward from day one. Payroll automation handles salary processing across multiple currencies without your finance team needing to learn a new jurisdiction’s tax rules.

The Belarus IT market in particular benefits from the HTP special regime, which provides significant tax advantages for registered tech companies. An EOR that already operates within that regime can pass those benefits through to your team without you needing to register independently.

FAQ

Can I switch from an EOR to a subsidiary later?

Yes, and it’s a fairly common progression. The EOR handles employment while you’re establishing your entity, and once the subsidiary is registered and operational, employment transfers across. Timing the transition carefully — particularly around local notice periods and employment continuity — is important, which is where an EOR with in-house legal support makes the process easier.

Is using an EOR legal in all countries?

EOR is legal in the vast majority of jurisdictions, though the specific rules vary. Some countries have restrictions on how long an EOR arrangement can run, or require certain employment conditions regardless of the model used. A few countries also have regulated industries where EOR may not apply. Always verify the specifics for the country you’re hiring in.

How many employees can I have through an EOR before it makes sense to open a subsidiary?

The commonly cited threshold is around ten employees, though it depends on the country and the EOR’s pricing structure. In some jurisdictions with high entity setup and maintenance costs, the EOR remains cost-effective even beyond that. In others, where registration is relatively inexpensive, the crossover point comes sooner. The right answer is a cost comparison specific to your situation, not a general rule.

Does an EOR affect how my employees experience working for me?

In practice, very little. Your employees report to you, work on your projects, and are managed by your team. The EOR’s role is largely invisible to them — payslips may come from the EOR entity, and the employment contract will name the EOR as the legal employer, but day-to-day working life is determined by you. The main area where it does show up is benefits, which are tied to the EOR’s standard offerings rather than anything you design independently.

What happens if local laws change after I’ve set up an EOR arrangement?

That’s one of the core advantages of the EOR model. Keeping up with changes to employment law, tax rates, and statutory benefits is the EOR’s responsibility, not yours. A good EOR monitors regulatory changes in the jurisdictions it covers and updates employment contracts and payroll accordingly. You get notified of anything that affects your team; you don’t have to track it yourself.

The bottom line

Setting up a subsidiary is a long-term bet. It makes sense when you’re committed to a market, your headcount justifies the overhead, and you want the full control that comes with owning a local entity. An EOR is how you make a smart, low-risk move first — hiring quickly, staying compliant, and keeping your options open while the picture becomes clearer.

For most companies entering a new market, the EOR is not a compromise. It’s the right structure for where they actually are. The subsidiary conversation tends to take care of itself once the market has proved out.