Paying EOR Employees in Belarus: Currency, Banking, and Cross-Border Payment Realities

So you’ve found the developer, the cost adds up, everyone’s keen — and then someone in finance asks the one question that brings it all to a halt: with the sanctions, can we even pay them? Fair question. It deserves a real answer, not an awkward pause.

The short version is yes. You can pay someone in Belarus, reliably, every month, without breaking any rules. The tricky part was never whether you’re allowed to pay a person — it’s how the money gets there: which currency, which banks, which route. That’s what this article is about, and I’ve tried to be straight about the bits most providers would rather skip. One caveat before we start: this is a practical rundown, not legal advice. What’s allowed depends on where your company is based, so run your own situation past someone who does compliance for a living.

How an EOR payment actually flows

It comes down to one question: who pays whom? With an Employer of Record, you’re not the one wiring money into Belarus. You pay the EOR — a vendor, like any other — and the EOR pays your developer. That sounds like a technicality. It’s the reason the whole arrangement works, because it keeps you out of the part that’s complicated.

1. You fund the EOR	2. EOR runs local payroll	3. Employee is paid
In your own currency (USD or EUR), to a bank you already use — same as paying any supplier.	It converts the money, withholds the income tax, and files social contributions in Belarus.	In rubles, on payday, through the EOR’s own non-sanctioned local bank.

So the EOR is your counterparty. You send it money in your own currency, from the same bank you use for everything else, and that’s the end of your involvement in the mechanics. From there it does the rest — it’s the legal employer on the ground, so it runs local payroll, withholds the tax, pays the social contributions, and gets the salary to the developer through its own Belarusian accounts.

Which is why “can I pay someone in Belarus?” isn’t really the question. The question is who your counterparty is and how they move the money. Sort that out and everything after it is just plumbing.

Currency: what you set versus what they are paid in

Every Belarusian salary involves two currencies, and confusing them is one of the easier ways to blow your budget. There’s the currency you promise the salary in, and there’s the currency that actually lands in the developer’s account.

Most foreign employers quote the salary in dollars or euros. It’s what developers working with Western clients expect, and it keeps their pay steady when the local currency wobbles. On the ground, though, the money goes out in Belarusian rubles — Belarusian labor law wants wages paid in local currency — so whatever hard-currency number you agreed gets converted to BYN every payday.

The conversion is where a cost hides that people forget to budget for. Somebody eats the spread between your currency and the ruble, plus the transfer fees, and that somebody is normally you. It’s not much on any single run, but it adds up over a year, so give it a line in the budget. None of this is a reason to quote in rubles instead. Paying in hard currency is one of the quiet things that keeps good developers from leaving, because their take-home doesn’t shrink every time the exchange rate has a bad week.

If you want the actual figure, the National Bank of Belarus publishes the official ruble rate every day, and it’s held in a fairly tight band against the dollar through 2026. Tight isn’t the same as fixed, though, which is the whole argument for quoting in dollars and letting the EOR handle the conversion.

The banking reality (the honest part)

Now the bit everyone’s really asking about. Belarus has been under sanctions from the EU, US and UK since 2022, and this is a topic where a lot of what you’ll hear is either out of date or just wrong — so it’s worth getting the facts straight, in both directions.

Take the EU first. A number of Belarusian banks are sanctioned and have been cut off from SWIFT, the system that carries most international payments. The EU’s own record lists Belagroprombank, Bank Dabrabyt and the Development Bank of Belarus as disconnected back in 2022, with Belinvestbank following soon after, and it bars dealings with the Belarusian central bank on top of that.

Here’s the part that gets lost in the panic: none of that bans paying people in Belarus. It hits named banks and entities. Plenty of Belarusian banks aren’t on any list and are still plugged into the international system, and sending an ordinary salary through one of them is a normal, above-board payment. The question is which bank and which route, not whether you’re allowed to run payroll at all.

And it’s a moving target. The US has actually gone the other way from Brussels: OFAC started rolling back its Belarus measures in late 2025, and a general license in March 2026 cleared transactions involving Belinvestbank and a handful of related entities.

That leaves a real, awkward gap in 2026 — the EU and US no longer line up. Something a US company can legally do might still land an EU company in trouble, and once in a while it works the other way round. Which rulebook applies to you comes down to where your business sits, so the “right” way to pay isn’t the same for everyone.

If you’ve got any EU footprint at all, that gap is worth taking seriously — there’s a readable legal write-up of it worth a look before you lean on the US easing. For payroll the practical upshot is short: use a provider whose banking and screening are set up for your side of the line, and get someone to sign off on your specific case.

Cross-border mechanics and timelines

Even when everything’s routed through clean channels, sending money to this part of the world doesn’t behave like a domestic transfer, and it’s kinder to everyone to say so upfront.

Cross-border payments hop through correspondent banks and get screened for sanctions on the way. With several regional banks shut out of SWIFT, there are fewer intermediaries to route through, and the compliance checks — know-your-customer, anti-money-laundering, the occasional “where’s this money from” — can add a step or two. In real terms that usually means an extra question here and there, or a day or two of delay. A nuisance, and it clears.

The good news is that it settles down. Once the setup’s done and the first payment has gone through, monthly payroll gets boring in the best way. It’s the first run you want to leave room around; after that a decent EOR just does it on time, every time. Give the setup and that first cycle a bit of breathing room, and tell your new hire what to expect so they’re not refreshing their banking app in week one.

Belarus currency-control and payroll rules you do not have to manage

Belarus has its own tangle of currency-control and payroll rules — the sort of thing no foreign employer should be expected to have memorized. You won’t be touching any of it. But it’s worth knowing what your EOR is quietly dealing with for you.

Every payday, the local employer has to convert the money properly, pay the salary in rubles, withhold and hand over the income tax, work out and file the social contributions, and produce payslips and reports that hold up. recruiting.by has a walk-through of the payroll and tax side if you want the detail.

The numbers themselves, straight from the cost side of the series: income tax is a flat 13% in 2026 — the old 9% Hi-Tech Park rate is on pause until 2027 — and employer social contributions come to roughly 28% of gross. There’s a catch in your favor, though. Inside the Hi-Tech Park those contributions are worked out from the national average wage rather than the developer’s real salary, so on higher earners that line comes down a lot.

How the Hi-Tech Park structure helps

Part of why payroll runs smoothly with the right provider comes down to the Hi-Tech Park.

The Hi-Tech Park is Belarus’s special legal and tax regime for IT, and a provider that’s a resident of it operates on a proper, formalized financial footing. That tends to make compliant payroll and banking easier, not harder.

It’s the same setup behind the contribution discount on the cost side. For payments, the benefit is practical rather than clever: an HTP-resident EOR already has the accounts, the processes and the reporting built for exactly this kind of cross-border employment. Nothing’s being invented on the fly for your hire.

How a local EOR de-risks the whole thing

Line it all up and what a local, compliant EOR really does for payments stops looking like admin and starts looking like insurance.

It’s your compliant counterparty. It keeps relationships with banks that aren’t sanctioned, screens every payment against the current lists, wears the FX and the conversion, files everything locally, and pays your developer in rubles on the day it’s due. recruiting.by’s payroll service is built around precisely that — money moving cleanly so the messy middle never becomes your problem.

And there’s a real difference between providers here. A generic global EOR can treat Belarus as a box it’s ticked without ever really solving it; a provider that’s properly established in the market has the rails running already. In a country where the banking really is complicated, that gap is the difference between payroll that works and payroll that stalls.

Questions to ask a provider about payments

Before you sign with anyone for Belarus, pin them down on payments. A provider who’s actually set up for this will answer all of these without missing a beat:

• What currency can we pay you in, and which bank does it go to?
• Which banks and channels do you use to pay staff, and are they clear of current sanctions?
• How do you screen payments and handle KYC and anti-money-laundering on every run?
• How long does the first payment take, and how long does regular monthly payroll take?
• If a payment gets held up or queried, what do you do — and how do you keep the employee in the loop?
• Who pays the FX spread, and how do you set the conversion rate?

Ask these alongside the money questions — fees, contributions, one-off charges — from guide to what hiring in Belarus really costs, and you’ll walk into the decision with the full picture instead of half of it.

Common payment mistakes foreign employers make

The mistakes we watch people make, over and over:

• Paying a developer straight into whatever account they send you, without checking the bank isn’t sanctioned.
• Quoting the salary in rubles and handing the currency risk to the employee — a quiet way to lose them.
• Underestimating how long the first payment takes and leaving a new hire sweating in week one.
• Leaving the FX spread and transfer fees out of the budget.
• Assuming a big global provider has Belarus sorted, and finding out they don’t when a payment sticks.
• Running with the US sanctions relief without checking whether EU rules still apply to you.

Frequently asked questions

Is it actually legal to pay a developer in Belarus?

In most cases, yes. Paying someone’s salary through a bank that isn’t sanctioned is a normal, legitimate transaction — the sanctions go after specific institutions and people, not ordinary payroll. The wrinkle is that your obligations depend on where your company is based, and the EU and US no longer agree, so check your own case with a compliance person or a provider set up for your region.

Can I pay my developer in dollars or euros?

You can agree the salary in dollars or euros, and most foreign employers do. It’s paid out locally in rubles, which is what Belarusian law requires, and the EOR handles the conversion. You send your currency; they receive the ruble equivalent of the figure you agreed.

Will the money actually turn up on time?

Once everything’s set up, yes — monthly payroll through a decent EOR is dependable. Leave a bit of slack around the setup and the very first payment, which can run slower because of the compliance checks. After that it’s routine.

Are Belarusian banks cut off from SWIFT?

Some, not all. A handful — Belagroprombank, Bank Dabrabyt, the Development Bank, Belinvestbank — were disconnected under EU measures, and dealings with the central bank are off-limits. But plenty of Belarusian banks aren’t sanctioned and are still on the international network, and those are what make clean payroll possible.

What if the sanctions change?

They do change — the US eased its measures across 2025 and 2026 while the EU stood pat. A provider that lives in this market keeps an eye on it and reroutes as needed to stay compliant, so your payroll carries on without you having to follow every twist. That’s a big part of why you’d use a specialist instead of doing it yourself.

Am I taking on sanctions risk just by employing someone in Belarus?

Employing a developer and paying them through clean, non-sanctioned channels is low-risk — as long as it’s done properly. The risk shows up when payments aren’t screened, when a sanctioned bank is involved, or when someone ignores the EU–US split. A compliant EOR is there to keep you clear of all three.

So — can you pay someone in Belarus? Yes. Reliably, within the rules, every month, as long as the money travels through the right structure and the right channels. That’s not a puzzle you should be solving live while your finance team waits. It’s the job a local, compliant EOR is built to do. If you’d like the specifics for your own situation — the currency, the timing, how the rails actually work — recruiting.by has already laid the track and can talk you through it.