Your Belarusian entity signs with a PEO. The provider takes over payroll calculation, files the returns, runs the bank transfers, and produces clean monthly reports. It feels like the tax exposure went with the workload.
It didn’t.
In Belarus, what’s marketed as “co-employment” or “shared employer responsibilities” is administrative outsourcing. The legal employer is still your entity. Every miscalculation, every late filing, every misapplied HTP base ends up on your balance sheet — recoverable from the PEO only by contract, not by the regulator’s order.
This post walks through the four tax lines a PEO runs on your behalf in Belarus, what changes when your entity is an HTP resident, and where the operational risk actually sits.
Belarus has no statutory co-employment framework. The PEO contract you signed — whatever its marketing name — is one of two things in legal terms: a services agreement with your Belarusian entity as the sole employer, or an EOR arrangement where the provider itself is the employer of record. There’s no middle category.
If you have your own Belarusian legal entity and the PEO is calculating your payroll, you’re in the first scenario. The PEO is your contracted service provider, not your co-employer. Salary obligations sit with your entity. Tax withholding sits with your entity. FSZN registration is in your entity’s name. Filings are submitted under your tax ID.
What the PEO actually owns is the operational execution: calculations, scheduling, banking, documentation, ongoing compliance monitoring, the day-to-day relationship with the tax authority. None of which is small — these are exactly the things a foreign parent doesn’t want to staff in Minsk — and a good Belarus PEO arrangement covers all of it. But none of it transfers legal liability.
This is the conceptual anchor for everything below. When the next sections talk about tax math, the math runs through your entity. The PEO calculates it correctly or incorrectly, but the rate cards, the rules, and the eventual reconciliation with the regulator are yours.
Belarusian payroll has four moving parts the PEO calculates each month. Three are mandatory across all employers; one varies based on HTP residency. We’ll look at each separately.
Standard rate: 13%, withheld from gross salary.
The PEO calculates the withholding line by line, but the funds flow through your entity’s accounts and the filing goes in your entity’s name. Standard deductions (dependent children, education expenses where eligible) are applied by the PEO based on documentation the employee provides — typically signed declarations and supporting certificates that the PEO holds on file.
One misconception worth correcting: HTP residency does not change the PIT rate. The reduced 9% rate that previously applied to HTP-resident employees was suspended; through 2027, HTP employees pay PIT at the same 13% flat rate as any other employee. Some foreign parents assume HTP gives a discount here. It doesn’t.
What HTP does change is the next line.
Standard rate: ~34% paid by the employer, plus 1% withheld from the employee.
This is the largest payroll tax line in Belarus and the one where HTP residency rewrites the math. For a non-HTP entity, FSZN is calculated on the employee’s full gross salary. For an HTP resident, the base is capped at the national average monthly salary published by Belstat — roughly 2,000 BYN in 2025. The cap rule comes directly from the HTP regime and is one of the headline incentives of the program.
Worked example, one developer with a 5,000 BYN monthly gross:
That’s a 1,020 BYN saving per month, or about 12,240 BYN per year. Per developer. For a team of ten developers in the 5,000 BYN salary band, the annual difference exceeds 120,000 BYN — material money even at modest team sizes, and the reason most foreign-owned IT entities in Belarus pursue HTP status.
Two operational details matter here. First, the employee has to consent in writing to the HTP base being used for their FSZN calculation; this consent is collected at onboarding and kept in the employee file. Second, the average salary figure updates monthly, and the PEO has to apply the correct period’s figure to each month’s payroll. Both are routine for a competent provider and easy to miss for a sloppy one.
Rate: around 0.6% of payroll, paid by the employer.
This covers occupational injury insurance and applies to all employers regardless of HTP status. No exceptions, no caps, no reduced rate. The PEO calculates and remits it alongside the other payroll lines. It’s a small line but generates penalties if missed, so worth confirming it appears in your monthly reporting.
A handful of additional lines round out the payroll tax picture. Targeted contributions apply in specific cases (typically not standard commercial IT). For HTP residents, there’s a 1% revenue-based contribution to the HTP administration — technically not a payroll tax (it’s a charge on revenue, not salary), but PEOs commonly handle the filing alongside payroll reporting because both go through the same monthly cycle. Confirm with your provider that this line is being tracked; a missed HTP administrative payment can put residency status at risk, and HTP status is exactly the thing your entire FSZN math depends on.
Concrete failure modes worth knowing:
In every case above, the regulator’s claim is against your Belarusian entity. The PEO’s exposure is contractual — what your services agreement says about errors, what indemnification looks like, and what cap (if any) sits on provider liability. Recovery is real but it’s a separate process from the tax authority’s collection action. The cleaner way to manage this is to choose a payroll provider in Belarus whose error rate is structurally low: in-house legal review, HTP-specialist staff, and audit-ready documentation as a default.
This is the operational hinge that makes PEO selection more than a procurement decision. The price difference between a strong provider and a weak one is small. The penalty exposure from a weak provider can be significant.
Because most foreign-owned IT entities in Belarus running through a PEO are HTP residents, the full HTP picture is worth the extra paragraph. Accounting and compliance for HTP companies covers the entity-level mechanics in depth, but the four payroll-adjacent lines are worth pulling out here.
HTP status affects four lines visible in payroll and accounting:
PIT stays at 13%. Belgosstrakh stays at 0.6%. The first two lines (profit and VAT) sit upstream of payroll and are filed by the accounting function, but they’re the reason the entity exists in HTP form. The FSZN saving is what flows directly through the PEO’s monthly calculations.
HTP status carries constraints worth flagging because they affect who you can put on the entity’s payroll. HTP-resident companies can only conduct activities listed in the program’s catalog. Hiring a developer for HTP-qualifying work is straightforward. Hiring a marketing manager whose role doesn’t map cleanly to the catalog needs to be structured carefully — sometimes through a parallel non-HTP entity — to avoid putting residency at risk. This is upstream of payroll mechanics but downstream of HTP entitlement, and a good PEO will flag the question before the hire goes through.
The structural choice between PEO and EOR comes down to one variable: do you have a Belarusian entity, and is keeping it worth what it costs to maintain.
No entity yet. Go with an Employer of Record. The provider is the legal employer; tax liability sits with them; you get speed and simplicity but pay a higher per-employee fee and don’t get HTP benefits directly (unless the EOR is itself an HTP resident, in which case the savings pass through indirectly).
Have an HTP-resident entity, building a team. PEO. The tax savings from HTP run through your entity, the PEO handles the operational load, and you keep direct visibility into compliance. Higher internal load than EOR, lower per-employee cost, full HTP benefits.
Have an entity, considering closing it. Cost-benefit between maintaining the entity for HTP benefits and switching to EOR. The break-even depends on team size, salary band, and what other operations the entity supports. For teams above roughly five developers earning at HTP rates, keeping the entity and using a PEO usually wins on pure tax math; below that, EOR can win on simplicity.
In all three scenarios, the choice is not about outsourcing liability. PEO retains your liability and gives you the HTP tax structure. EOR moves liability to the provider and gives you operational simplicity. The structural difference between PEO and EOR comes down to those two trade-offs — picking on tax outcome and audit posture, not on which arrangement sounds more “outsourced,” leads to the right answer.
No. Under a PEO, your Belarusian entity remains the legal employer and the taxpayer. The PEO calculates, files, and pays on your behalf, but regulatory claims for underpayment, late filing, or miscalculation sit with your entity. Recovery from the PEO, if warranted, is contractual.
No. Payroll tax filings in Belarus are submitted under the employer’s tax ID — meaning your entity’s. The PEO prepares the filings and handles the submission mechanics, but the filing itself is your entity’s.
The base for employer FSZN contributions is capped at the national average monthly salary (around 2,000 BYN in 2025) instead of the employee’s actual salary. For a developer earning 5,000 BYN, this cuts the employer’s monthly FSZN contribution from ~1,700 BYN to ~680 BYN. The rate stays at 34%; what changes is the base.
The tax authority will collect underpaid amounts from your entity, with penalty interest. Whether you recover from the PEO depends on the indemnification clauses in your services agreement. Strong contracts cap PEO liability at a defined multiple of monthly fees, which may or may not cover the full exposure.
Yes. Penalties are a fixed amount per missed filing plus daily interest on unpaid taxes. The entity is the legal payer. Internal recovery from the PEO follows the same contractual route as other errors.
A competent one can, but it’s worth asking specifically. Belarus has its own rules on when one-time payments enter the FSZN base, and the rules differ from typical European approaches. The mechanics of IT payroll taxation in Belarus are documented separately; mis-coded year-end bonuses are a common quiet error that surfaces only at audit.
Most foreign-owned HTP entities still keep accounting separate from payroll, either in-house or through the same provider in a different service line. Payroll is one slice of the entity’s accounting picture; profit tax, VAT, HTP reporting, and statutory accounts all sit outside the PEO’s normal scope. A single provider can cover both, but they’re different contracts.
Per-employee PEO fees are typically 30–50% lower than EOR fees for the same role. The trade-off is that PEO assumes you’ve already absorbed the cost of maintaining a Belarusian entity, which runs €30,000–60,000 per year before salaries. Against the backdrop of Belarus’s overall tax environment, PEO wins on per-employee economics; EOR wins on total cost when the team is small or the entity isn’t justified by other operations.
The highest-leverage thing a foreign parent running an HTP entity through a PEO can do this quarter is have someone independent reconcile one month of payroll filings against actual contracts. Mistakes in FSZN base, missing consent documentation, miscoded bonuses — these are silent issues that compound until an audit surfaces them.
We do this on a fixed fee. Send a sample payslip and one month’s reporting register, and you’ll get a written assessment back within a few days: what’s correct, what needs documentation, and where the exposure sits.
Angel investments are a key financing mechanism for early-stage startups and innovative projects. They provide not only capital but also experience, contacts, and strategic guidance. Unlike venture capital funds, angel investors usually act individually, risking their own money for promising ideas and teams that can impact the market. In Belarusian and international startup ecosystems, angel […]
Personal data protection in the European Union: basic provisions Information on the Internet needs to be protected, especially personal data. So, when registering on sites on the Internet, we enter our personal data, which are stored in automated systems. Collection, storage, use of personal data should be regulated by law. It should be noted that […]
The conversation usually starts the same way. A senior engineer asks for a one-on-one, closes the door, and says they’ve been talking to another company. Sometimes there’s a written offer attached. Sometimes there isn’t. Either way, the next forty-eight hours will decide whether you keep one of the people your team can’t easily replace — […]
