Moving From EOR to Your Own Entity: A Transition Playbook for Belarusian Teams

Most foreign IT companies hire their first people in Belarus the same way. A product company in London or Dubai finds two or three strong engineers in Minsk, has no appetite for incorporating a company for a handful of hires, and signs them up through an Employer of Record. The provider holds the employment contracts, runs payroll and files the reports. The client directs the work. For a pilot team, that arrangement is hard to beat.

Then the team grows. Three engineers become fifteen, a QA lead and a product manager come on board, and someone in finance starts asking why the company pays a per-head fee every month for people it now treats as a permanent R&D centre. The question is no longer whether to set up a Belarusian entity; it’s how to do it without disrupting delivery or losing people.

This playbook covers that move: the signals that it is time, what changes once you become the employer, how to choose the structure, a realistic timeline, and how to transfer employees from the EOR to your own company. It is written for foreign-owned IT businesses with teams in Belarus, and it assumes you want the switch to be invisible to your clients and as uneventful as possible for your engineers.

Signs your team has outgrown EOR

There is no fixed headcount at which EOR stops making sense. The decision usually rests on a mix of cost, control and how long you plan to stay. These are the signals we see most often:

• The fee line is now very real. EOR fees are charged per employee per month. With five people it’s trivial to absorb. With twenty or thirty the annual fee can easily exceed the cost of running your own company with outsourced accounting and payroll.
• You want Hi-Tech Park benefits for your own business. HTP residency is granted to a specific legal entity for its own business plan. If you want the regime’s tax treatment for your product development, the company that employs the team and runs the projects has to be yours.
• Clients or investors ask about your structure. Enterprise customers, auditors and due diligence teams want to see who owns the work product and where the team is legally employed. An R&D centre that exists only as a line in a vendor contract is harder to explain.
• IP needs a cleaner chain. Under EOR, the code is written by a third party’s employees and the rights are assigned to you by contract. That works, but many groups would prefer that the developers are actually employed within the group so that the ownership starts at the point of creation of the code.
• You need local contracts. Leasing an office, buying equipment or signing with Belarusian partners all require a local counterparty. An EOR provider cannot sign those on your behalf.
• The team is no longer an experiment. If you plan to be in Belarus for years rather than quarters, a permanent structure usually fits better than a flexible one.

If two or three of these apply, model the numbers. The EOR fee you stop paying is set against registration costs, a director, accounting, statutory reporting and, depending on your size and status, a mandatory audit.

What changes when you become the employer

The biggest shift is legal rather than administrative. Under EOR, the provider is the employer in the eyes of the Labour Code, the tax inspection and the Social Protection Fund (FSZN). Once you have your own company, those obligations land on it, and on the person who signs for it.

Area	Under EOR	With your own entity
Employment contracts	Signed by the provider	Signed by your director
Payroll, income tax, FSZN, Belgosstrakh	Calculated and paid by the provider	Your company, in-house or outsourced
Statutory reporting	Filed by the provider	Filed by your company, on deadline
Labour inspections and disputes	Provider is the respondent	Your company is the respondent
Internal regulations and personal data policy	Provider’s documents apply	You adopt your own
Office lease, equipment, local vendors	Not possible in your name	Your company signs directly
Cost structure	Salary, taxes and a per-head fee	Salary, taxes and fixed running costs

Every Belarusian legal entity needs a head: either an individual director or a management company appointed under contract. That person signs employment contracts, approves internal regulations and answers to inspectors. Foreign groups without a trusted manager in Minsk often appoint a local management company for the first year or two.

The cost also changes shape. You stop paying a variable fee per employee and start paying for fixed functions: accounting, payroll, HR records, a legal address and banking. Employment taxes stay broadly the same, with 13% personal income tax withheld from salaries, a 34% employer contribution to FSZN, 1% from the employee and the premium for Belgosstrakh accident insurance. What changes is who calculates, pays and reports them.

Choosing the structure for your Belarusian entity

Most foreign IT groups set up a limited liability company (LLC). It can have a single foreign shareholder, there is no statutory minimum charter capital, and the capital can be paid in within 12 months of registration. Joint-stock companies exist but rarely suit a development centre.

The bigger decision is whether the new company should apply for Hi-Tech Park residency. For most product and outsourcing teams, it should. HTP residents are exempt from corporate profit tax and VAT on qualifying income and pay the Park a quarterly contribution of 1% of revenue instead. FSZN contributions are not charged on the part of a salary above the national average wage, which matters a lot for a team of senior engineers. Residents can also hire foreign specialists without work permits and use instruments such as option agreements and non-compete clauses.

Residency is subject to conditions. The company can only carry out the activities set out in the HTP Regulations and will have to apply with a business project which will be subject to review by the Supervisory Board (typically 4-6 weeks). Any activity outside of the approved scope (e.g. reselling of hardware) would have to be in a separate entity. If in any doubt as to whether your model qualifies, please check the business project requirements for Hi-Tech Park residency prior to registering the company to ensure that your charter and activities are in line from the outset.

Three more questions belong at this stage:

• Who will head the company? A local director you trust, a manager relocated from headquarters or a management company. The choice affects banking, signing authority and day-to-day control.
• Where will the IP sit? If the parent keeps ownership, intercompany agreements and royalty or service flows need to be designed now, not after the first tax review.
• How will the entity earn revenue? A cost-plus service agreement with the parent is the most common model for R&D centres. The mark-up has to be one you can defend to the tax authorities.

The transition playbook: from decision to first payroll

A clean move from EOR to your own entity typically takes 3-5 months. A good deal of that time is spent on preparation rather than on the actual paperwork. The registrations themselves are fairly quick, but you do need lead time for banking, HTP and employee communication. Here is the sequence that works for most teams.

Phase 1. Decide and design (weeks 1–3)

Confirm the business case, choose the legal form and decide on HTP residency. Agree who will head the company, how it will be funded and how it will charge the parent. Then pick a target switch date and work backwards. The first day of a month is the easiest cut-over for payroll and reporting.

Tell your EOR provider early. Check the notice period in your service agreement, and ask how they handle outgoing transfers. A good provider will help plan the move rather than slow it down.

Phase 2. Register the company (weeks 3–6)

Approve the company name, which is then reserved for one month, prepare the charter and confirm the legal address. State registration itself is usually completed within days of filing, after which the company appears on record with the tax inspection and FSZN. Issue the director’s appointment order and start accounting records from the first day.

Phase 3. Open bank accounts and apply for HTP (weeks 5–12)

Open a current account in Belarusian rubles and, if you will invoice in foreign currency, a currency account. Banks run detailed checks on foreign-owned companies, so have ownership charts, beneficial owner details and source-of-funds documents ready. The charter capital and first operating funds go in at this stage.

If you are applying for residency, submit the business project, application and corporate documents to the HTP Secretariat. Under the official admission procedure, review and the Supervisory Board decision should take no longer than one month and ten days from submission. Plan around that window, and avoid scheduling the employee transfer before you know the outcome.

Phase 4. Build the employer infrastructure (weeks 8–14)

Adopt internal labour regulations, a pay and bonus policy, a personal data policy and job descriptions. Check that the company is on record with Belgosstrakh for mandatory accident insurance. Set up payroll software or appoint a payroll provider, arrange a salary card project with your bank and prepare the new employment contracts.

Phase 5. Transfer the team (weeks 12–16)

Agree the transfer date with the EOR provider, collect employee consents, close the EOR contracts and sign new ones. The next section covers this step in detail.

Phase 6. Close out the EOR (weeks 16–20)

Keep the EOR agreement in place for one further payroll cycle to allow the provider time to make their final settlements and file their closing reports. Reconcile the final month and confirm that the FSZN records have the change of employer before you terminate the service contract.

Moving employees from the EOR to your entity

For your engineers, this is the part that matters. Handled well, the switch is a change of name on the payslip. Handled badly, it is the moment people start taking recruiters’ calls.

Legally, the usual route is a transfer to another employer with the employee’s consent, which is a separate ground for ending an employment contract under the Labour Code. The EOR closes the existing contract on that ground, and your company hires the employee from the next day. Nobody resigns, and there is no gap in anyone’s work history.

Settle these points before the transfer date:

• Terms. Match or improve salary, currency linkage, bonuses, benefits, equipment and remote work arrangements. Any downgrade, however small, will be noticed.
• Contract form and term. Decide how long the new contracts will run. People who had multi-year contracts with the EOR will expect at least the same security.
• Probation. Skip the trial period for transferred staff. Putting someone who has worked on your product for years on probation sends the wrong message.
• Leave balances. The EOR normally pays compensation for unused leave in the final settlement. Explain how leave will work in the first months with the new employer, so nobody is caught out when planning a holiday.
• Paper originals. Employment contracts and amendments are still signed on paper, even though many other HR documents can now be exchanged electronically. Plan the signing for anyone working outside Minsk.

Tell the team well in advance (ideally 4-6 weeks prior to the switch) in a live conversation rather than an email. Explain the reasons for the move, what’s going to stay the same and what’s going to change. Then provide each individual with a written summary of their new terms and a named point of contact for any questions they may have. Most engineers take the news well. A local entity is seen as a sign of commitment and many feel that being directly employed is more secure than being employed via a third party.

Finally, decide who will run HR and payroll from day one. Some companies will of course build an in-house team. Others will keep their admin with an external provider via a PEO arrangement whereby the people who already know the files will continue to run them while the legal employment moves to the new company.

Payroll, tax and reporting from day one

The first payroll run under your own entity is where the small set up gaps will be apparent. Salaries must be paid at least twice a month, so agree the advance and final pay dates with your bank before the first month starts. If salaries are linked to USD or EUR, keep the exchange-rate mechanism the EOR used (usually the National Bank of Belarus rate on a fixed date) so employees’ take-home pay doesn’t shift.

If the entity is an HTP resident, apply the regime correctly from the first month. Under the Regulation on the Hi-Tech Park, mandatory social insurance contributions are not charged on the part of an employee’s income above the national average monthly wage. The same Regulation requires residents to audit their annual financial statements and to file an activity report with the HTP administration every year.

Build a reporting calendar before the first month closes. It should cover income tax, FSZN and Belgosstrakh payments every month, quarterly tax returns and the 1% HTP contribution, and the annual financial statements, audit and HTP report. Most foreign groups outsource this work at first. Whatever you choose, ask for a monthly payroll report in the format your headquarters already uses, so the switch is invisible on the group side as well.

Common mistakes to avoid

• Registering before deciding on HTP. The charter and the business project need to match. Fixing a mismatch later costs weeks.
• Leaving banking to the last month. Account opening for a foreign-owned company takes time, and a late start often pushes back the switch date.
• Transferring mid-month. Splitting a month between two employers doubles the payroll and reporting work and confuses people about their pay.
• Changing terms during the move. The transfer is not the moment to rework bonus schemes or trim benefits. Change one thing at a time.
• Ending the EOR agreement too early. The provider still has final settlements and closing reports to file.
• Skipping the intercompany paperwork. Without a service agreement with the parent and a defensible mark-up, the new entity has no documented revenue, and the tax authorities will ask why.

FAQ

How long does the move from EOR to our own entity take?

Typical time frame is 3 to 5 months. State registration takes a few days. The HTP review is limited to one month and ten days after submission. The real time is dictated by banking, the internal docs and preparing the team.

Do employees have to resign from the EOR?

No. The standard route is a transfer to another employer with the employee’s consent. The EOR ends the contract on that ground and your company hires the person from the next day, so there is no break in employment.

Can we move only part of the team?

Yes. Each employee is transferred individually, so some people can stay on EOR while the entity ramps up. Running both models side by side for a few months is common.

Is HTP residency required to run an IT company in Belarus?

No. A company outside the Park pays standard taxes (including the standard 20% corporate profit tax). Most software development and product businesses do qualify for residency and the payroll saving on its own is often sufficient to make the application worthwhile.

Can we hire foreign specialists in the new entity?

Yes. HTP residents can employ foreign nationals without work permits and only need to notify the migration authorities within three working days of signing the contract. Companies outside the Park go through the standard work permit procedure.

Conclusion

EOR is an efficient way to start in Belarus and an expensive way to run a permanent R&D centre at scale. The move to your own entity is not complicated, but it has a natural order: decide on the structure and HTP residency, register and bank the company, build the employer infrastructure, then transfer people with their terms intact. Most problems come from rushing that sequence.

If you are weighing the switch, start with the numbers and a target date, then work backwards. Spex supports foreign IT companies at every stage, from registration and HTP admission to the employee transfer and ongoing payroll. For a timeline and cost estimate built around your team, get in touch with us and we will map out the transition together.