For years, the fastest way for a foreign tech company to work with engineers in Minsk was simple. Each developer registered as an individual entrepreneur (IP), signed a service agreement with the company abroad, and sent a monthly invoice. No local entity, no payroll, no HR paperwork. For a team of two or three people, it often worked well enough.
The trouble starts when the team grows and the arrangement stays the same. Ten sole proprietors who work only for you, log in to your Jira every morning, take vacations approved by your team lead and receive the same amount every month are not running ten small businesses. In the eyes of a Belarusian tax inspector or labour court, they look a lot like employees without employment contracts.
That gap between paperwork and reality has always carried risk. In 2026 it has become harder to ignore. The list of activities allowed for sole proprietors has been cut, tax authorities are actively reclassifying contractor relationships, and draft amendments to the Labour Code target civil-law contracts that replace employment.
Below, we look at when a contractor model turns into a liability, what is at stake for the client and the team, and how to move Belarusian sole proprietors to an Employer of Record without disrupting the work.
The IP model became popular for practical reasons, not because anyone set out to break the rules.
Speed. Registering as a sole proprietor takes days, and the foreign client only needs to sign a service agreement. There is no need to incorporate a Belarusian company, appoint a director or open a corporate bank account.
Lower visible cost. Under the general regime, a sole proprietor pays 20% income tax and can deduct a flat 20% expense norm instead of documenting costs, plus their own social contributions. For many engineers, this left more money in hand than an employment contract with 13% personal income tax and a 34% employer contribution to the Social Protection Fund (FSZN) on top of the salary.
No employer obligations for the client. Vacation pay, sick leave, terminations and labour inspections are, on paper, the contractor’s problem.
The model only holds while the relationship stays genuinely independent. One client, full-time work inside that client’s processes and a fixed monthly amount describe an employee by substance, whatever the contract says.
Belarusian law has always looked at substance over form. Article 33 of the Tax Code allows the authorities to disregard a structure used mainly to reduce taxes, and Article 25 of the Labour Code treats actual admission to work as the conclusion of an employment contract, even without signed paperwork. What changed recently is how actively these rules are enforced and how many supporting measures now surround them.
No single factor turns a service agreement into an employment relationship. Inspectors and courts look at the whole picture. Still, Belarusian tax practice has settled on a fairly consistent set of indicators, and most of them are easy to spot from the client’s side.
Signs that point to a lack of independence:
Signs of organisational subordination:
If you recognise four or five of these points in your current setup, the relationship would be difficult to defend as a genuine business-to-business contract. If the whole team fits the description, the risk is no longer individual. It is structural.
This logic is not unique to Belarus. Most tax systems test the same things: who controls how the work is done, who bears the business risk and whether the relationship is open-ended. The IRS, for example, groups its test into behavioural and financial control plus the type of relationship. A contract label rarely wins against facts that point the other way.
The consequences of reclassification depend on how the client is structured, but nobody in the chain is fully protected.
A local company that engages sole proprietors instead of employing them is the most exposed party. When the authorities recognise substitution of employment, they can treat the payments as salary and reassess what the company should have paid as an employer:
Where the amounts are large, criminal liability is possible under Article 243-1 of the Criminal Code (evasion of tax agent obligations) and Article 243-3 (evasion of social security contributions). Inspection reports are still being issued for earlier tax periods, so a structure that was quietly abandoned two years ago can still surface.
On the labour side, a former contractor can ask a court to recognise the relationship as employment and claim compensation for unused vacation and for forced absence after an improper termination.
A foreign company without a Belarusian presence is harder for local authorities to reach, so much of the immediate risk falls on the individuals. That does not make the model safe for the client. A team that works exclusively for one foreign company, under its management and on a permanent basis, raises questions that go beyond Belarus:
Contractors carry their own risk too. Reassessment can hit them personally, and they work without paid leave, state sick pay or protection against dismissal. Many senior engineers accepted that trade for higher net income; fewer do once tax practice turns against the model.
Several developments have come together over the past two years, and each of them makes a large IP-based team harder to sustain.
A closed list of activities. Since 1 January 2026, sole proprietors may only carry out activities on the list approved by Council of Ministers Resolution No. 457. IT services under the “Information and communication” section remain on it, so developers can still work as IPs. But the principle has shifted from “everything not prohibited” to “only what is allowed”, and every future revision of the list is now a business risk.
A revenue ceiling with a long tail. A sole proprietor whose annual revenue exceeds BYN 500,000 loses the right to work in that status for three years. That threshold is rarely an issue for one engineer, but it matters for senior contractors who subcontract or bill several clients.
Active enforcement. Tax inspections focusing on substitution of employment through sole proprietors and self-employed people have become routine, and the Supreme Court has published judgments supporting the authorities’ position.
Draft Labour Code amendments. The Ministry of Labour has proposed amendments that would expressly prohibit civil-law contracts that in substance regulate employment. The draft also sets out criteria for identifying an employment relationship, such as work under the client’s management and control or receipt of labour guarantees like paid leave, and introduces an out-of-court procedure for reclassification. The government planned to submit the bill to parliament in April 2026. Whatever its final wording, the policy intent is already shaping how inspectors read contractor arrangements.
Belarus is moving in the same direction as many other countries. ILO Recommendation No. 198, and the ILO guide on the employment relationship built around it, encourages states to presume employment where key indicators such as subordination and dependence are present. Companies that operate in several jurisdictions should expect the same questions everywhere.
An Employer of Record is a Belarusian company that becomes the legal employer of your team. It signs employment contracts under the Labour Code, registers people with the Social Protection Fund and the tax authority, runs payroll, withholds taxes and handles the HR lifecycle. You still choose the people, set their tasks and manage the work.
For a company without a local entity, this is usually the cleanest fix. Working with a direct provider of Employer of Record services in Belarus removes the need to incorporate, appoint a director or maintain local accounting, while the employer obligations sit with a party that handles them every day.
| Legal basis | Civil-law service agreement | Employment contract under the Labour Code |
| Taxes on the person | 20% income tax plus own social contributions, paid by the IP | 13% personal income tax (25% and 30% on the parts of annual income above BYN 350,000 and BYN 600,000) and 1% FSZN, withheld by the employer |
| Employer contributions | None | 34% FSZN plus mandatory Belgosstrakh insurance |
| Leave and sick pay | None by law | At least 24 calendar days of paid leave; sick pay from the Social Protection Fund |
| Reclassification risk | Grows with team size and dependence | Removed for the employment relationship itself |
Moving a team from IP contracts to employment almost always increases the total cost per person, mainly because of employer contributions to the Social Protection Fund. Companies handle this in different ways: some keep net pay unchanged and absorb the difference, some share it with the team, and some restructure compensation with bonuses or benefits. What matters is that the decision is made with a full cost model in front of you, not discovered after the first payroll.
Weigh that against what the company stops carrying: reassessment risk, labour claims, gaps in IP ownership, investor questions and the chance that a key engineer cannot invoice next month after a regulatory change.
A well-run transition takes weeks, not months, and the team should barely notice it day to day.
Many companies treat EOR as a long-term setup. Others use it as a bridge while they decide whether Belarus is a long-term location. When the team grows large enough to justify a structure of your own, employees can be transferred to your own entity with their terms preserved, so the move to EOR today does not lock you into anything.
Yes, IT services are still on the list of permitted IP activities in 2026. The thing to watch is how you actually work with these people. A contractor who has a few other clients and bills you by project won’t raise questions. It gets riskier when someone works full-time only for you, reports to one of your managers and is basically treated like staff. In that case the authorities can reclassify them as an employee.
There’s no magic number. One contractor can be reclassified if the signs are clear enough. In practice, though, the risk jumps when you have several full-time IPs working together as a team. The pattern is easier to spot, and the amounts that could be reassessed get big enough for someone to take an interest.
Not necessarily. You’ll almost certainly pay more overall, but what people take home depends on how you set up their pay. A lot of companies keep net income where it was and treat the extra cost as the price of staying compliant and keeping their team. Your people also get paid leave and sick pay, plus social insurance, none of which they had as contractors.
No. EOR fixes the relationship from the start date of employment. Past periods remain subject to the general limitation rules. Closing old contracts with accurate acts and clean IP assignments helps reduce exposure, and for larger teams it is worth getting a legal review of the historical arrangement.
For a team of ten to twenty people, the full process, from mapping the current setup to the first EOR payroll, is usually a matter of weeks rather than months. Most of that time goes into planning, cost modelling and team communication. The formal onboarding step itself is fast.
Working with Belarusian IPs is fine in itself, and lots of companies do it. It goes wrong when someone is an “independent contractor” on paper but in practice works only for you, gets the same fixed amount every month, has a manager, needs their holidays approved and does it all on your laptop. Whatever the contract says, that person is an employee. With one person it may never come up. With your whole dev team, who’ve been with you for years, it’s a lot harder to argue.
It’s also riskier now than it used to be. The list of what an IP is allowed to do is closed, the authorities are actually checking, and the Labour Code is heading the same way.
Yes, moving people to an Employer of Record costs more. But it’s a cost you can plan for. The other option is a risk you can’t really estimate, while your team goes without the protection they’d have as normal employees.
Our advice is to deal with it before someone else forces the issue, whether that’s an inspection, investors asking questions before a round, or an engineer who leaves on bad terms. If a few of the warning signs above sound familiar, send us a message. We’ll look at how your contractors are set up and work out what switching them to EOR would actually cost you.
