Most companies switch their Employer of Record for the same reason: something has quietly gone wrong for months. Support tickets pile up. Payroll reports arrive with corrections. Compliance updates come from the wrong side of the table — the employee, not the provider. By the time HR raises it internally, the case for change is obvious. What is less obvious is how to move employees onto a new provider without breaking what they depend on.
In Belarus, that “anything” carries specific weight. The Labour Code sets out a narrow list of grounds on which employment contracts can be terminated, and each ground carries its own paperwork. Payroll runs on the calendar month with mandatory reporting to the Social Protection Fund (FSZN), Belgosstrakh, and the tax inspection. A gap in any of those filings is visible to the state within days. Miss a step in the wrong order, and the employee is the first to notice — because their salary lands late, their sick leave calculation is wrong, or a certificate they need for a mortgage application is stuck between two providers.
This guide covers what a clean EOR transition looks like in Belarus, in the order it actually needs to happen. It leans on Belarusian labour and tax law rather than a generic international template — that is where most failed transitions come apart.
There is rarely one reason. The trigger is usually a compounding of three or four smaller frustrations that hit at a bad moment — an annual audit, a promotion cycle, a new hire the current provider cannot onboard fast enough.
The most common patterns we see in Belarus:
None of these are grounds for panic. They are grounds for a planned move.
Global EOR guides tend to assume employment can be transferred cleanly between providers with a signature and a system update. In Belarus, several structural rules complicate that assumption.
First, an employee cannot be legally employed by two entities simultaneously in the same role. The prior EOR must terminate the contract properly under Chapter 4 of the Labour Code before the new EOR can sign. That means the sequencing has to be exact — usually a Friday termination and a Monday start, or same-day where both providers cooperate.
Second, statutory registrations do not migrate. When the new EOR takes over as legal employer, the employee has to be re-registered with FSZN and the tax inspection under the new employer’s ID. That is a paperwork exercise, but it happens on a specific timeline and generates a small window during which the employee is technically between employers.
Third, the employment book — either the paper book or its electronic equivalent — carries entries from every employer. A sloppy transition leaves gaps or duplicated entries the employee will have to explain years later when they retire or apply for a benefit.
Fourth, salary in Belarus is normally paid twice a month — an advance and a final settlement — with specific deadlines. Any cutover date that lands mid-cycle creates a proration question that has to be resolved between the outgoing and incoming provider before payroll runs.
None of this is unmanageable. It just cannot be improvised, which is why teams handling their own transition tend to lean on outside HR consulting in Belarus at least for the contract review stage.
A clean switch typically takes four to six weeks from the moment the client signs with the new provider. Faster than that is possible for one or two employees; longer is normal for teams above ten. The phases run roughly like this.
Weeks 1–2: Contract audit and provider selection. Read the current EOR agreement first. Notice periods for termination usually sit between one and three months, and missing the notice window can extend the engagement or trigger financial penalties. Data return clauses, exit fees, and IP assignment provisions matter here too.
Weeks 2–3: Employee communication and consent. Employees in Belarus have specific rights when the legal employer changes. They need to be informed in writing, understand what is changing and what is not, and sign the new contract willingly. This step is where transitions go quiet — and then loud.
Weeks 3–4: Document preparation. New employment contracts drafted under Belarusian law, new job descriptions where required, and the paperwork for FSZN and tax-inspection registration. Benefits — medical insurance, corporate SIM cards, equipment — are re-papered in parallel.
Week 4: Termination by the outgoing EOR. Contracts terminated on a specific date under the correct Labour Code article, final settlements paid, employment books updated. The outgoing provider files its final reports to FSZN and the tax authority for that employee.
Week 5: Onboarding with the new EOR. Contracts signed with the new employer, employee re-registered with the relevant authorities, payroll set up. The first salary payment cycle begins.
Week 6: Monitoring. First payroll runs. Statutory reports filed under the new employer. Any residual documents from the previous provider — historical payslips, tax certificates for prior periods — collected and stored.
The selection criteria worth pressing on:
For companies whose Belarus hires are concentrated in engineering and product teams, our EOR services for IT companies cover the same framework with additional practices for equity, bonus structures, and role classifications that international tech companies typically bring with them.
This is the step most transitions underestimate. In our experience, an employee who is told two days before the switch, in a group email, will treat the change as a warning sign. The same employee, told four weeks in advance in a one-to-one conversation with clear answers to their questions, treats it as an administrative event.
The core message to employees, in order:
One dimension worth thinking about early is senior-level context. If any of the affected employees are executives or heads of function, their contracts often carry unique clauses on bonuses, notice, and non-competes that a standard template will not carry across cleanly. Our note on reference checks and senior hires in Belarus covers some of the local nuance on senior-level employment documentation that becomes relevant here.
The mechanical risks in a Belarus EOR switch cluster in three places.
Salary timing. Belarusian employees expect payment on specific dates. If the switch falls between the advance and the final payment for a given month, the outgoing and incoming provider need to agree who pays which portion, and the client’s cash flow to both needs to reflect that split. It is straightforward if planned; it becomes a problem if discovered on the day. A dedicated payroll service in Belarus usually manages the split cleanly on the incoming side.
Leave balances. Annual leave of 24 calendar days (or more, depending on category) carries a monetary entitlement. On termination by the outgoing EOR, unused leave is either used up or paid out. The new EOR then starts a fresh leave year unless the client and provider agree a specific reconciliation. Most clients prefer paid-out balances to keep the accounting clean.
Sick leave in progress. If an employee is on sick leave on the switch date, the paperwork gets more complicated. The certificate covering that period sits under the old employer’s ID; continuation under the new employer requires specific handling. Where possible, we push switch dates outside known absences.
Beyond the mechanical items, a few risk categories deserve explicit attention.
Currency and banking. Salaries are paid in Belarusian rubles. Where the client funds the new EOR in foreign currency, the incoming provider needs banking capacity and NBRB currency-control paperwork in order before the first payroll cycle. If it does not, the first salary lands late.
HTP residency, if applicable. Where employees sit under an HTP-resident client entity that is being served by an EOR (or is being taken back in-house), the tax profile changes. HTP-resident employers benefit from reduced income tax and social contribution rates on IT employees. Moving between an EOR and a client’s own HTP entity requires specific attention to entitlement dates.
Contract type continuity. Fixed-term contracts (contract system) and open-ended contracts have different rules under the Labour Code. If the outgoing EOR uses one form and the new EOR proposes another, the change needs to be explained to the employee and agreed in writing.
Historical data return. Payslips, tax certificates, and contribution records for periods worked under the previous EOR belong to the employee and — to the extent the client paid for them — to the client. Get them back in a usable format before the outgoing provider’s storage obligation expires.
Four to six weeks is the normal range for a well-planned switch. Very small teams — one to three employees — can move in two to three weeks. Teams above ten benefit from a longer runway, mainly because the communication and consent step takes longer.
They should not. A properly coordinated switch times the termination by the outgoing EOR and the start with the new EOR back to back — usually the last working day of one month and the first of the next, or a Friday-to-Monday cutover. What matters is that the paperwork on both sides reflects a single legal employer on any given day.
Yes. The new EOR is a new legal employer, and Belarusian law requires a written employment contract with each employer. Terms usually mirror the previous contract as closely as possible, with any client-requested improvements folded in.
Unused annual leave is paid out on termination by the outgoing EOR, or, less commonly, transferred by mutual agreement. Bonuses that have accrued but not been paid are settled by the outgoing provider before termination. Any bonus schemes going forward are set up under the new contract.
It happens. The most common form is delay — slow return of records, or a reluctance to time the termination cleanly. The Labour Code protects the employee’s rights regardless, and the new EOR can still onboard on schedule. The client’s leverage is the notice period in the outgoing contract and, in extreme cases, formal correspondence citing the provider’s cooperation obligations.
You can, but the split between the outgoing and incoming provider needs to be agreed in writing in advance, and both providers need to reflect it correctly in their reporting. Most clients prefer to switch at month-end for cleaner accounting.
No. The two EOR providers handle their own registrations and de-registrations with FSZN, Belgosstrakh, and the tax inspection. The client sits above that layer.
An EOR switch in Belarus is not risky by default. It becomes risky when treated as a purely commercial exercise — sign the new contract, cancel the old one, hope the providers coordinate. What determines whether the workforce notices is the sequencing of terminations, registrations, and the first payroll cycle under the new employer, all governed by Belarusian labour and tax law rather than by the platforms involved.
Two decisions matter most, and both are made early. Choose a direct EOR provider with in-house legal and HR — one that can answer labour law questions in English on the same day and apply Belarusian regulatory changes to existing contracts without waiting to be asked. Then run the transition on a documented six-week timeline, with employees informed at week two, not week five. Everything else follows.
If you are considering a move, our team runs these transitions regularly for international clients moving from global platforms and local providers alike. A scoping call covers the current setup, the affected employees, and the target switch date; a written proposal follows within a business day. Full detail on scope, pricing, and coverage is on our Employer of Record service in Belarus page.
“We could qualify for HTP — but should we?” It’s one of the most common structural questions foreign founders ask once their Belarusian entity setup gets serious. HTP residency is usually presented as the obvious answer, but the actual math depends on three variables: team size, profit margin, and operational complexity. For some companies, HTP […]
You decided to set up a subsidiary in Belarus without relocating anyone. The engineering team will hire locally, the parent will fund from abroad, and the day-to-day will be handled by a Minsk-based management company. On paper this is a clean setup. In practice, it works only when the delegation is drafted precisely — because […]
Most foreign IT companies looking at Belarus stop reading after three letters: HTP. It’s understandable. The High-Tech Park has the best marketing, the cleanest English-language materials, and a tax profile that makes the math easy to model. For a lot of software companies, it’s genuinely the right answer. But not for all of them. We […]
