Belarus has been sanctioned by Washington, Brussels, and London for almost five years. The framework expanded sharply after February 2022, eased in places under the Trump administration through 2025 and early 2026, and remains divergent across the three jurisdictions. None of that has stopped international companies from hiring engineering and operations talent in Minsk — but the cost of getting it wrong has risen, and the path that works in 2026 looks different from the one that worked in 2022.
For US, UK, and EU companies, an Employer of Record is the cleanest route into the Belarusian labour market right now. The structure removes the lead time of incorporation, transfers employer-side compliance to a licensed local provider, and — when done properly — keeps the client at arm’s length from the sanctioned parts of the Belarusian economy. The catch sits in “when done properly.” EOR is a contractual layer, not a sanctions firewall. Compliance still rests with the foreign client, and the client still has to know what it is looking at.
This guide covers what the US, EU, and UK regimes actually prohibit; how those prohibitions intersect with employment; and the screening, banking, and contracting steps that keep an EOR engagement on the right side of the line.
The starting point is to dispel a common misconception. Belarus is not a comprehensively sanctioned country in any of the three Western regimes. It is not Cuba, Iran, North Korea, or Syria. US, UK, and EU sanctions on Belarus are targeted — they restrict dealings with named individuals and entities, certain economic sectors, and specific types of transactions. They do not prohibit ordinary commercial relationships with non-sanctioned Belarusian counterparties.
But the three regimes draw the line in different places, and the gap has widened over the past twelve months.
OFAC administers Belarus sanctions under Executive Orders 13405 and 14038. The headline restrictions are an asset freeze against parties on the Specially Designated Nationals (SDN) List, a ban on new investment by US persons in Belarus, and prohibitions on transactions involving certain sectors.
Three rounds of easing through 2025 and early 2026 rolled back parts of the framework in exchange for prisoner releases. Belavia, the national airline, was removed from the SDN List in November 2025. Belaruskali, the Belarusian Potash Company, and Agrorozkvit were delisted in March 2026. On 26 March 2026, OFAC also rescinded Directive 1 under EO 14038 — which had banned dealings in Belarusian sovereign debt — and issued General Licence 14 authorising transactions with Belinvestbank and certain affiliates.
What did not change: the new investment prohibition in EO 14038, the SDN designations of hundreds of other Belarusian individuals and entities, and the prohibition on transactions in sectors identified in the executive order.
The EU regime is materially broader and has continued to expand. Restrictive measures under Regulation 765/2006 cover dual-use exports, financial services, transport, energy, technology, and a growing list of services. The 20th sanctions package, adopted on 23 April 2026, added new import and export prohibitions, banned transactions with Belarusian crypto-asset service providers, and brought the Belarus framework closer to the Russia regime in several respects.
Of direct relevance to EOR engagements: nine Belarusian banks are subject to full transaction bans under EU law — Belagroprombank, Bank Dabrabyt, the Development Bank, Belinvestbank, BelVEB, Belgazprombank, Alfa-Bank (Belarus), Sber Bank (Belarus), and VTB Bank (Belarus). The EU asset freeze covers 310 individuals and 46 entities as of mid-2026, with the regime extended through 28 February 2027. The 50% ownership rule extends those prohibitions to majority-owned subsidiaries.
The UK runs its own autonomous Belarus regime under the Republic of Belarus (Sanctions) (EU Exit) Regulations 2019. OFSI handles financial sanctions, the Office of Trade Sanctions Implementation (OTSI) handles trade sanctions, and the FCDO maintains the designations list. The substantive prohibitions track the EU framework closely, but the lists do not align perfectly — entities sanctioned under one regime may not be sanctioned under the others.
New Sanctions End-Use Controls came into force on 13 May 2026, targeting circumvention through third countries. For UK companies hiring in Belarus, the practical implication is that any technology or service provided to a Belarusian employee falls within the scope of UK export and trade controls, even where the employee is engaged through a third-party EOR.
The legal logic of EOR matters when you assess sanctions exposure. Under the arrangement, a licensed Belarusian provider holds the employment contract with the worker, runs payroll, withholds taxes, and meets statutory reporting obligations. The foreign client signs a services agreement with the provider — not with the employee directly.
For sanctions purposes, that narrows the client’s regulatory exposure to a defined set of counterparties. First, the EOR provider itself. Next, the Belarusian bank that processes payroll. Finally, the employee as an individual. Each needs to pass screening against the relevant SDN, EU consolidated, and UK sanctions lists before the engagement starts and on an ongoing basis.
That is a much smaller surface than direct incorporation, which would add the local entity, its directors, its bank, its suppliers, its landlord, and its statutory advisors to the screening perimeter. It is also smaller than direct contractor hiring, which often triggers questions about permanent establishment and tax residency on top of the sanctions analysis.
The following checklist reflects what compliance teams at international IT, fintech, and fund-backed companies actually run before greenlighting a Belarusian hire through EOR. None of it is exotic. All of it is non-negotiable.
Screen the EOR provider. Run the legal entity name and its beneficial owners against OFAC’s SDN List, the EU consolidated financial sanctions list, and the UK Sanctions List. Check the 50% rule: if any sanctioned party holds a majority stake, the provider is itself a sanctioned counterparty. Repeat the check at the start of every engagement and re-screen quarterly against current designations.
Screen the individual employee. Belarusian citizens are not sanctioned by virtue of nationality. Past employment at a sanctioned state-owned enterprise warrants a closer look, particularly for roles involving sensitive technology or finance. Compliance-aware HR consulting in Belarus generally builds this check into the candidate intake process rather than treating it as a one-off legal review.
Choose the payroll bank carefully. Of the nine Belarusian banks under EU transaction ban, several remain commercially active and are widely used for domestic payroll. Hiring an employee whose salary settles to an account at one of those banks creates direct exposure for an EU-based payer. A capable EOR provider routes salary to a non-sanctioned commercial bank — Priorbank, MTBank, BSB Bank, and several others operate normally for EOR payroll and maintain functioning USD and EUR correspondent relationships.
Plan the payment route. USD payments to Belarus pass through US correspondent banks and are subject to OFAC screening, even where neither the sending nor the receiving institution is a US bank. EUR payments face EU screening. The EOR provider invoices the client in whatever currency the client prefers — typically USD or EUR — and converts to Belarusian rubles for net salary disbursement. The conversion step is where most banking problems surface, and where the choice of EOR provider matters most.
Confirm the sector. EOR works for engineering, product, design, finance, operations, and most corporate functions. It does not work for roles supporting Belarusian defence, dual-use technology production, energy or petrochemical export, or any activity that touches a sanctioned state-owned enterprise. The sector check should be documented at the briefing stage and revisited if the role scope changes.
Address technology and IP transfer. If the employee will receive source code, proprietary tooling, or restricted technical information, the transfer is subject to US export controls (EAR), EU dual-use regulations, and UK strategic export controls. EOR does not waive those obligations — it changes who the legal employer is, not what the technology is. Licensability sits with the client.
Document the anti-circumvention position. Belarus has been used as a routing point for Russia-related circumvention since 2022. EU and UK regulators expect EU- and UK-headquartered companies operating in Belarus to demonstrate that their engagement is not, directly or indirectly, providing economic benefit to Russian end-users or sanctioned Russian counterparties. A brief written analysis at the start of the engagement — covering who the employee actually works for, what they produce, and where it goes — closes the most common gap.
The single most consequential operational decision in a Belarusian EOR engagement is the bank. A well-run provider holds salary accounts at multiple Belarusian banks, allowing it to route around any institution that goes onto a sanctions list mid-engagement.
For US clients, USD payroll is generally workable through non-sanctioned Belarusian banks with US correspondent relationships. The provider invoices in USD, the funds settle in a USD account in Minsk, conversion happens through the National Bank of Belarus exchange mechanism, and net salary goes out in rubles to the employee’s domestic account.
For EU and UK clients, EUR or GBP routing is more common, and the same operational pattern applies — though the screening burden on the receiving side has tightened materially since the EU’s 18th package converted SWIFT restrictions into full transaction bans for the nine listed banks. For finance and HR leads weighing how the underlying account infrastructure works in practice, opening a bank account in Belarus for a non-resident walks through the documentation and correspondent landscape in more detail.
Some hires don’t fit the EOR model regardless of how clean the compliance picture looks. The most common scenarios:
The employee will be working on technology that is itself controlled — encryption above certain key lengths, dual-use software, or items on the EU Dual-Use Regulation 2021/821 Annex I list. Export licensing applies regardless of the employment structure, and the EOR contract does not address it.
The role sits inside a sanctioned sector by function rather than by employer. Engaging a “consultant” who advises a sanctioned Belarusian state-owned enterprise on financial restructuring puts the client into prohibited territory even where the EOR contract is clean on paper.
The hire is for a senior management or board role at a Belarusian entity that holds material Russian business — the dual-regime exposure (Belarus plus Russia) needs to be assessed as one piece, not separately.
In any of those cases, the route forward is not “find a different EOR.” It is to step back, take written advice on the specific prohibition, and decide whether the role can be redesigned, licensed, or relocated.
The short answer is yes, conditional on three checks. First, every counterparty in the chain — the EOR firm, the Belarusian bank where salary lands, and the candidate themselves — has to come back clean against the OFAC SDN List. Second, the job itself can’t fall inside a sector carved out by EO 13405 or EO 14038. That mainly means defence, state-owned petrochemicals, and anything that pulls a designated entity into scope. Third, there is the new investment prohibition in EO 14038, which on its face looks like a problem. It isn’t in practice. OFAC’s published interpretation treats ordinary salary payments to an individual via a third-party Belarusian employer as outside the scope of “new investment,” so a properly structured EOR arrangement does not require a specific licence.
Functionally similar in scope, but the lists do not perfectly align. UK companies need to screen against the UK Sanctions List specifically — not rely on the EU consolidated list as a proxy. The Sanctions End-Use Controls in force since 13 May 2026 add a layer on technology transfers and services routed through third countries.
For non-sanctioned banks with US correspondent relationships, yes. Most operational issues come not from the sanctions framework itself but from individual correspondent banks tightening their internal risk policies. A capable EOR provider will hold accounts at multiple Belarusian institutions and can re-route if a particular bank rejects the payment.
Most designations are accompanied by a wind-down general licence — typically 30 to 90 days — to allow for orderly transition. The provider should monitor designations daily and move payroll to a non-sanctioned bank before the wind-down expires. This is part of what the EOR fee buys.
In standard cases, no. Licences become relevant if the role touches a restricted sector, involves a sanctioned counterparty, or requires the transfer of controlled technology. The compliance review at the start of the engagement is what determines whether a licence is needed.
Belarus sanctions compliance for hiring is not the same problem as Belarus sanctions compliance for trade in goods. The screening surface is smaller, the prohibitions are less restrictive, and the operational risks are more manageable — provided the structure is designed around the current framework rather than the one that existed before the 2025–2026 changes. For most US, UK, and EU companies, the right answer in 2026 is still a properly structured EOR engagement with a direct local provider; the right preparation is twenty minutes of screening, a written sector assessment, and a deliberate choice of payroll bank.
We sign Belarusian employment contracts, run payroll, and absorb the local compliance load for clients hiring out of New York, London, Berlin, and the Gulf. If you are scoping a Belarusian hire and want a view on whether the structure works for your specific compliance profile, our EOR services in Belarus page sets out how the engagement runs end to end.
Dear Clients! We are pleased to announce the completion of a project to recruit 3 (three) developers for a US project in the VRLabs area. To date, the project has attracted over $ 100 million in investments. Due to the existence of a confidentiality agreement, we cannot write the name of the brand under which […]
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 […]
