Top 7 Mistakes Foreign Companies Make in EOR Contracts in Belarus (And What They Quietly Cost You)

Imagine a client came to us last quarter with a problem. They’d been running EOR through a large global provider for fourteen months — payroll on time, no HR drama, the kind of relationship that doesn’t get a second thought. Then their lead engineer resigned. Two weeks later that engineer was working at a competitor, building on the same architecture he’d just spent a year designing for our client.

The client called the EOR provider asking what to do. The answer, more or less: nothing. The IP assignment in the master contract assigned rights to the provider, not to the client. The underlying employment contract, drafted by a US legal team in English only, wasn’t fully enforceable under the Belarusian Labor Code. Recovering the IP would mean a lawsuit between three parties across two jurisdictions, and the lawyer’s first question — “do you have a Russian-language contract that says the engineer assigned this work to you?” — had a one-word answer.

This isn’t unusual. We see some version of it every month. Most EOR contracts foreign companies sign in Belarus contain at least three of the seven mistakes below. Usually because the contract was drafted by a global provider whose template was built for fifty countries and tuned for none of them. Here’s what to look for.

The 7 mistakes at a glance

#	Mistake	What it typically costs
1	Treating the EOR arrangement as one contract instead of two	Surprise severance, unenforceable termination clauses
2	Letting the EOR draft the employment contract in English only	Contract reinterpreted by labor inspectorate; clauses get struck
3	Misclassifying employees as contractors	Retroactive social contributions (~34%), back taxes, fines
4	Weak or US-style IP assignment language	IP chain-of-title gap; can’t recover work product
5	Assuming termination works the way it does at home	3 months severance + reinstatement risk for protected categories
6	No HTP residency warranty in the master contract	Cost basis changes mid-term with no remedy
7	Post-termination obligations that don’t survive Belarus law	Non-competes struck down; senior leavers walk away clean

Mistake #1 — Treating the EOR arrangement as one contract instead of two

Foreign companies sign one master services agreement with the EOR provider and assume that’s the whole arrangement. It isn’t. There are always two contracts: the MSA between you and the EOR, and the employment contract between the EOR and the employee. The Belarusian Labor Code governs that second one regardless of what your MSA says, and that’s where the surprises live.

The mistake is signing the MSA without ever asking to see the employment contract template. We’ve reviewed MSAs that promise the foreign company “30-day removal of any employee at our discretion,” while the underlying employment contract carries a one-month statutory notice plus three months of severance — costs the EOR will absolutely pass through to you when the moment comes. Different paper, different rules, same invoice.

Ask for both documents in draft before you sign anything. Read the employment contract template line by line. If your provider can’t or won’t share it, that’s the answer to a different question. 

Mistake #2 — Letting the EOR draft the employment contract in English only

The Belarusian Labor Code requires employment contracts to be in Russian or Belarusian. Being bilingual is fine. English-only is not. Some global providers cut corners here by issuing English contracts and arguing they’re “supported by” a Russian translation kept on file somewhere. In a labor dispute, the Russian or Belarusian version is what the inspector reads. If there isn’t one, the contract gets reinterpreted using whatever the inspector or court understands the parties to have meant.

That almost never goes the foreign employer’s way. Belarusian Labor Code is, by design, more protective of the employee than US or UK law, and an ambiguous contract is read in the employee’s favor by default. The Multiplier overview of Belarus employment law lays out the contract requirements clearly — written, signed in two copies, in Russian or Belarusian, with mandatory clauses on job description, working conditions, and compensation.

Fix is straightforward: bilingual contract, identical clauses on both sides, signed by the employee and by your EOR’s authorized representative. We handle this as standard in our payroll and contract setup — but it’s worth checking if your existing provider has done it.

Mistake #3 — Misclassifying employees as contractors

This one’s a favorite of foreign companies trying to keep things light. Start with a contractor agreement, see how it goes, convert later. The thinking is reasonable; the execution gets people in trouble.

Belarusian labor authorities don’t care what label you put on the document. They care about the substance of the relationship. Set hours, your equipment, your instructions, daily reporting into your team — that’s an employee under Belarusian law no matter how many times the contract says “independent contractor.” Penalties are real: retroactive social contributions of around 34% on what you’ve paid the person, back taxes, and administrative fines. 

HTP residency doesn’t shield you from this. HTP gives the resident company a lot of things — tax exemptions, reduced social contribution base, the right to hire foreigners without quota — but it doesn’t override classification rules. If your EOR is suggesting you start with contractors for a role that’s clearly an employee role, push back. The right move is full employment for anyone who looks, walks, and quacks like an employee, with proper IT outstaffing structure if you genuinely need contractor flexibility for project work.

Mistake #4 — Weak or US-style IP assignment language

This is the one that hurts most when it goes wrong, which brings us back to the engineer at the start of this post.

The standard US “work made for hire” assignment doesn’t map cleanly onto Belarusian law. Under Belarusian Civil Code, IP an employee creates in the course of their duties belongs to the employer by default — but only if the employment contract spells it out, the work falls within the documented scope of duties, and the employer pays appropriate consideration for the assignment. Three conditions, all required, and the failure mode is silent: nothing breaks until someone leaves and you go looking for the paper trail.

Global EOR contracts often handle IP through the MSA between you and the EOR, leaving the employment contract silent on assignment. That creates a chain-of-title gap. The EOR holds the rights as the legal employer, then assigns to you under the MSA. If either link is weak — bad employment-contract language, a missing consideration clause, scope of duties that doesn’t actually cover the work — you have an IP problem you can’t see until it costs you.

What you want: explicit IP assignment in the employment contract itself, in Russian or Belarusian, with consideration spelled out and scope of duties broad enough to cover the work the engineer will actually do. Then explicit further assignment in the MSA. We cover this systematically in our HR consulting work because we’ve seen too many companies discover the gap on their way out.

Mistake #5 — Assuming termination works the way it does at home

American clients in particular trip on this. “At-will” or near-at-will termination is the default mental model, and it’s the wrong one for Belarus. The Labor Code doesn’t recognize at-will employment. Termination grounds are listed in Article 42 (and a handful of related provisions) and the list is exhaustive. Outside those grounds you cannot dismiss an employee unilaterally.

This means: severance of three months’ salary for dismissals without cause; one-month employer notice as a baseline; and several protected categories — pregnant employees, employees on maternity or childcare leave, and others — who cannot be dismissed at all in most circumstances. The Lawgratis summary of Belarusian employment law walks through the protected-category rules in plain English.

Where this creates contract problems: the MSA promises you “the ability to remove an employee with 30 days’ notice for any reason.” Read literally, that’s a promise the EOR cannot legally keep. What it really means in practice is that the EOR will pass through to you the full statutory cost of removing the person — severance, notice pay, any wrongful-termination exposure — and “30 days” turns out to mean “30 days plus everything that comes with it.” The fix is realistic termination language in the MSA that matches what’s actually possible under Belarusian law, with clear cost allocation upfront. Talk to our team if your contract reads like the cleanly American one we just described.

Mistake #6 — No HTP residency warranty in the master contract

If your EOR is HTP-resident — and most of the good ones in Belarus are — you’re benefiting indirectly from HTP tax treatment through the cost structure they offer you. Lower social contribution base, exemptions on the EOR’s own corporate tax, the works. Your monthly fee reflects all of that.

Now read your MSA. Does it actually require the EOR to maintain HTP residency for the term of the contract? In our experience, almost never. It happens — providers lose residency for non-compliance, for activity-mix changes, occasionally for administrative reasons that have nothing to do with the client. When it happens, the cost basis under your monthly fee changes overnight, and most contracts are completely silent on what happens next. You either swallow the price increase, fight about it, or walk.

What should be there: an explicit HTP-status warranty clause with a defined remedy if residency is lost — typically a price adjustment, a termination right, or both, depending on what fits your situation. The Spex.by piece on local versus global EOR providers is worth a read on why this matters more than it seems on paper.

Mistake #7 — Post-termination obligations that don’t survive Belarusian law

Most foreign-drafted EOR employment contracts contain US- or UK-style non-compete clauses: 12 to 24 months, broad geographic scope, broad industry definition. Belarusian courts will read those and start striking. Non-competes are restricted in scope and duration under Belarusian law, and broad ones get narrowed or thrown out entirely. NDAs hold up better but only when drafted to local standards.

The result, for a senior engineer who’s seen your roadmap: they leave, your enforceable post-termination claims are narrower than your contract suggests, and the practical recovery options are limited. We’ve watched companies discover this exactly once before they fix their template.

What works in Belarus: NDAs calibrated to what’s actually enforceable; narrow non-competes (where appropriate, with consideration paid for the restriction); and a robust IP-and-confidentiality-survival clause that does the work the broad non-compete can’t. Our PEO setup includes a post-termination-clause review by default, and it’s one of the most common gaps we close on inherited contracts.

How to actually check your contract

If you’ve got an EOR contract on your desk right now — or in force — here’s the six-point check we run on every contract a client brings us.

1. Get both documents. MSA and employment contract template. If you only have one, you only have half the deal.
2. Verify the employment contract is in Russian or Belarusian. Bilingual is fine. English-only is not.
3. Trace the IP chain end to end. Employee → EOR → you. Look for explicit assignment, consideration, and scope-of-duties language at each step.
4. Match termination language to Article 42. If your MSA promises termination flexibility the Labor Code doesn’t allow, you’re going to pay for that flexibility at the wrong time.
5. Look for HTP residency warranties. If the EOR’s tax position underpins your pricing, the contract should say so and have a remedy if it changes.
6. Stress-test the post-termination obligations. Non-competes especially. If the clause was written for a US court, it may not survive a Belarusian one.

FAQ

Can a US-style EOR contract be enforced in Belarus?

Partly. The MSA between you and the EOR provider can be governed by foreign law and held up reasonably well in international arbitration. The employment contract between the EOR and the employee is a different story — it’s governed by Belarusian Labor Code, must be in Russian or Belarusian, and has to follow the mandatory-clause structure set out in the Code. A US-style template translated word-for-word into Russian almost never holds up cleanly. You need a contract drafted to Belarusian standards from the start.

Does HTP residency change how an EOR contract should be drafted?

Yes, in two ways. Your MSA should explicitly require the EOR to maintain HTP residency for the term, with a defined remedy if it’s lost. And the employment contract should be drafted to take advantage of HTP-specific provisions — the reduced social contribution base, the simplified hiring of foreign nationals (no quota for HTP residents), and the scope-of-duties language that supports IP assignment in technical roles. Most boilerplate global-EOR contracts ignore both.

Who actually owns the IP my engineers create through an EOR?

Under Belarusian Civil Code, IP created by an employee in the course of their duties belongs to the employer by default — meaning the EOR, not you. The IP then needs to be assigned onward to you through the MSA. That two-step chain only works if the employment contract has proper assignment language, the work falls within the documented scope of duties, and consideration has been paid for the assignment. If any link is weak, you have a problem. This is the single most common gap we find when we review inherited contracts.

Can I terminate someone through my EOR provider with 30 days’ notice?

Not in the way most foreign employers mean. You can ask the EOR to begin termination, but the Belarusian Labor Code limits unilateral termination to specific grounds in Article 42 and related provisions. Outside those grounds, the practical exit is mutual termination — which usually involves three months’ severance and a settlement agreement. Your MSA might say “30 days,” but the underlying cost is whatever the Labor Code requires, and you’ll pay it.

What language does an EOR employment contract need to be in?

Russian or Belarusian. Bilingual contracts (Russian/English or Belarusian/English) are accepted and usually preferred so the foreign principal can read what’s been signed. English-only is not compliant with Labor Code requirements and creates real enforcement risk in any dispute.

Should I review my existing EOR contract even if nothing has gone wrong yet?

Yes, and the cheapest time to fix any of these gaps is before they matter. The mistakes in this post don’t cause problems on day one — they cause problems on the day someone resigns, the labor inspectorate visits, or the EOR loses HTP residency.

If you want a second pair of eyes

None of this is hypothetical. Every mistake in this post is one we’ve fixed for a client at least once — usually after they came to us because something had already gone sideways with a global provider.If you’ve got an EOR contract on your desk and you’re not sure whether it covers all seven of these, send it over. Twenty minutes on a call, no obligation, and you walk away with a clear list of what’s solid and what needs fixing. Twenty minutes that have, on more than one occasion, saved a client a quarter-million-dollar mistake. Get in touch, and have a look at the rest of the blog while you’re deciding.