“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 saves six-figure sums annually. For others, the compliance overhead exceeds the tax benefit.
The decision is structural and hard to reverse cheaply — switching between structures involves real time and cost — so it pays to run the numbers carefully before committing. This post walks through the tax math, the compliance overhead, and three worked examples at different team sizes, so you can see where the breakeven actually falls.
Before the comparison, a quick sketch of what each structure actually is.
Standard LLC \. The default Belarusian legal entity for foreign-owned tech businesses. Fully foreign ownership is permitted; many LLCs are 100% owned by US, UK, EU, UAE, or CIS parent companies. The standard corporate tax framework applies: 20% on profit, 20% VAT on most domestic sales, ~34% employer FSZN on full salary base, ~1% employee FSZN. Setup is fast — 1 to 2 weeks. Ongoing compliance is moderate: standard accounting, monthly payroll filings, quarterly VAT returns, the usual regulatory submissions to FSZN and the tax authority.
HTP resident. A Belarusian legal entity that has additionally been approved as a resident of the High-Tech Park regime. The underlying entity is still an LLC (or another approved Belarusian form); HTP residency layers a tax and regulatory framework on top. Setup adds 3 to 6 months and a substantial business project application. Ongoing compliance is heavier: HTP-specific reporting, mandatory annual independent audit, 1% revenue payment to the HTP administration, and a continuing obligation to operate within the approved activity catalog. Tax benefits are material: 0% profit tax on qualifying activity, 0% VAT on qualifying activity, FSZN base capped at the national average salary. Working with a provider experienced in HTP applications is the typical approach, because the business project document and the supervisory board review both benefit from specialist knowledge.
What comes next: a side-by-side on the tax math, the compliance overhead, and worked examples at three different team sizes — so the breakeven becomes concrete rather than abstract.
The substantive comparison. Each line, both structures.
Corporate profit tax. LLC: 20% on net profit. HTP: 0% on qualifying activity. This is the single largest delta. For a company generating 500,000 BYN annual profit, the LLC pays 100,000 BYN more per year — material at any scale, and the line item that drives most of the structural argument for HTP.
VAT. LLC: 20% on most domestic B2B sales, with standard input VAT recovery. HTP: 0% on qualifying activity. For software companies selling primarily to foreign customers, the practical delta is smaller than the headline numbers suggest — foreign B2B sales are typically zero-rated for VAT purposes regardless of structure. For domestic sales or non-qualifying revenue streams, the delta is real.
FSZN. LLC: 34% employer + 1% employee on full salary base. HTP: 34% employer + 1% employee, but the base is capped at the national average salary. As of 2025, that cap is approximately 2,000 BYN/month. For a senior developer earning 5,000 BYN/month gross under the HTP framework, the LLC pays 1,700 BYN/month in employer FSZN; the HTP resident pays 680 BYN/month. The annual delta per senior developer is roughly 12,240 BYN. For a 10-person team, this scales to ~122,000 BYN/year — a recurring benefit that compounds with headcount and salary level.
Personal income tax. LLC: 13% flat. HTP: 13% flat. The previously reduced 9% rate for HTP-resident employees has been suspended through 2027, so there’s no delta on this line. Worth flagging because the difference is often misremembered by founders who read older HTP material.
Belgosstrakh. LLC: 0.6% on full salary base. HTP: 0.6%, same treatment. No delta.
HTP administrative contribution. LLC: none. HTP: 1% of revenue, paid quarterly to the HTP administration. This is the explicit offset against the tax savings — small for low-revenue companies, more significant for high-revenue ones. For a company with 5M BYN annual revenue, this is 50,000 BYN/year.
Putting the deltas together for a 10-person team generating 5M BYN revenue and 1.5M BYN profit: the LLC profit tax is 300,000 BYN; the LLC FSZN excess is ~122,000 BYN; total LLC tax disadvantage runs to ~422,000 BYN. HTP gains those 422,000 in savings minus 50,000 in administrative contribution — a net benefit of ~372,000 BYN per year. The mechanics of how each of these lines actually gets calculated and reported are walked through in a separate piece on IT-sector taxes; the key point for this comparison is the net delta and how it scales.
Tax savings come with operational obligations attached. The CFO and COO view of the comparison:
Standard LLC. Annual financial statements per Belarusian accounting standards, monthly payroll and tax filings, quarterly VAT returns, standard regulatory submissions to FSZN and the tax authority. Most foreign-owned LLCs handle this through a Minsk-based accounting firm at a typical cost of $500–1,500 per month, depending on team size and transaction volume. Predictable, well-understood, no exotic requirements.
HTP resident. Everything the LLC has, plus several HTP-specific obligations:
The average monthly incremental cost over the LLC baseline is between $300 and $800, depending on how complicated the activity is. The annual audit adds $3,000 to $8,000, depending on the scope and auditor. Administratively speaking, HTP residency is more difficult but predictable; the majority of seasoned providers regularly handle the additional compliance. Because the needs are specific enough to require it, specialized accounting for HTP-resident companies is recognized as a service category in Belarus.
The qualitative difference matters as much as the quantitative one. An LLC can pivot its activities relatively freely within general Belarusian law. An HTP resident cannot — a material business model change might require de-residency or a supplementary application, both of which carry time and cost. For companies operating in a stable activity, this binding is fine. For early-stage companies still finding product-market fit, the catalog constraint can become a real operational issue.
It’s difficult to act on abstract math. The comparison for three realistic example companies is shown here.
Example 1: Small team, modest revenue
Three developers at 4,000 BYN/month average. Annual revenue 800,000 BYN; profit margin 20% (160,000 BYN profit).
Verdict: marginal. The math works, but only just. Many small operators stay as LLC for simplicity — the management bandwidth needed for HTP compliance can exceed what a 3-person team can spare in the early stages.
Example 2: Mid-size team, established revenue
Ten developers at 5,000 BYN/month average. Annual revenue 5M BYN; profit margin 30% (1.5M BYN profit).
Verdict: obvious. HTP residency pays for itself many times over. The payroll mechanics that drive most of the FSZN delta — including the timing and base-cap rules — are covered in detail in the payroll services framework for either structure, but the practical impact is that under HTP, every senior hire costs the employer materially less.
Example 3: Large team, scaling revenue
Thirty developers at 6,000 BYN/month average. Annual revenue 18M BYN; profit margin 35% (6.3M BYN profit).
Verdict: HTP residency is structurally essential at this scale. Operating as a standard LLC would be a serious tax error — the foregone savings exceed the annual compensation of several senior engineers.
The pattern is clear: breakeven sits between Example 1 and Example 2 — somewhere around 5 employees and 1M BYN revenue, depending on profit margin. Below that, the structural overhead can outweigh the tax benefit. Above that, HTP increasingly dominates. The broader Belarus tax environment in regional context gives useful framing — the standard LLC framework isn’t punishing by international standards, which is partly why the breakeven exists at all rather than HTP being obviously correct in every case.
The honest section. A few cases where the straightforward math doesn’t apply, and the structural choice deserves more careful thought.
For most foreign-owned IT companies past the Example 2 scale, HTP residency is the right answer. Below that, run the math honestly — the structural overhead is real, and the savings need to justify it on their own terms, not in the abstract.
Yes. Many foreign-owned LLCs start standard and convert to HTP residency once team size and profitability justify the structural overhead. The conversion process is essentially the same as a new HTP application: business project preparation, supervisory board review, approval. The underlying entity continues uninterrupted; only the regime overlay changes.
Roughly 5 employees and 1M BYN annual revenue, but the actual number depends heavily on profit margin. A 3-person team with 40% profit margin can hit HTP breakeven; a 7-person team operating at break-even profitability may not. The honest answer is to run the calculation with your actual numbers — comparative IT taxation across the region shows how Belarus’s structural math compares to neighboring jurisdictions, which can frame the decision when an HTP vs LLC question is really a Belarus vs neighbor question.
Not materially. Both structures allow dividend distribution to foreign shareholders under standard Belarusian rules. There are some procedural differences in how dividends are handled at the HTP-resident level, but the fundamental ability to repatriate profits is comparable for both. The choice is rarely driven by dividend mechanics.
Within one entity, no — an HTP resident must operate within its approved catalog scope, as defined by the HTP framework. Across separate entities, yes: it’s common for groups to maintain an HTP resident for qualifying technology activity and a separate LLC for ancillary services. The overhead of running two entities needs justification, but for businesses with meaningful non-qualifying activity, it can be cleaner than trying to squeeze everything into one HTP scope.
Yes, materially. LLC incorporation in Belarus typically completes in 1–2 weeks. HTP residency on top of an LLC adds 3–6 months for the business project preparation and supervisory board review. For founders working to an investor or customer deadline that requires HTP status, the timeline needs to be planned from day one — starting the HTP application late puts the entire structure under deadline pressure.
Each model fits a different stage. EOR works without a Belarusian entity; PEO assumes you already have one. Direct operation through your own HTP entity is the most cost-efficient at scale but carries the most setup and compliance overhead. The detailed comparison of PEO and EOR models covers when each makes sense; in the context of this comparison, EOR makes sense pre-HTP, and PEO makes sense once your HTP entity is operational and you want to outsource the workforce administration layer.
No, because there’s no profit tax on qualifying activity to deduct against. The 1% is paid on gross revenue regardless of profitability — the implicit price of the broader tax framework. For loss-making periods, this can feel painful: the administrative contribution is owed even when the company is unprofitable. That’s part of why pre-revenue startups should run the math carefully before committing.
Employment relationships continue uninterrupted. The underlying legal entity doesn’t change — only the regime overlay. Employees see no contractual change; the practical effect for them is that the FSZN cap rule begins to apply to their contributions (with their written consent), which doesn’t change their take-home pay but reduces the employer’s contribution cost on their salary.
Send your team headcount, average salary, projected revenue, and rough profit margin. You’ll get back a side-by-side LLC vs. HTP comparison for your specific case — including the breakeven analysis and the structural recommendation. No commitment; the calculation is most useful before you commit either way.
The Belarus Hi-Tech Park is a special legal regime that provides favorable conditions for the development of IT companies and export-oriented technological projects. However, there are still many stereotypes surrounding the HTP: it is often referred to as an “ecosystem,” administrative mechanisms are misunderstood, and benefits are sometimes attributed to it that do not actually […]
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 — […]
Most international groups that own a Belarusian subsidiary aren’t physically in Minsk. The headquarters sits in London, New York, Dubai, Singapore, or Berlin. The CFO checks in over Slack, the board reviews quarterly numbers in a dashboard, and the only people on the ground are the engineering team, an accountant, and whichever statutory officers the […]
