Almost everyone researching Belarus’s Hi-Tech Park (HTP) focuses on getting in: the profit-tax exemption, the 9% personal income tax, the visa and work-permit advantages. Far fewer think about how a company can lose that status — and that is the risk that actually bites.
HTP residency is not a permanent title you earn once; it is a conditional status you keep only by complying with the rules. The HTP Supervisory Board can exclude a resident for failing to deliver its business project, earning revenue from activities outside the permitted list, missing reports or the quarterly administration fee, breaching the agreement on the conditions of activity (the resident agreement) or the Park’s rules (including anti-money-laundering obligations), or providing false information. Losing the status also means more than losing the benefits from that day on. The real sting is retrospective: exclusion for a breach triggers a clawback, with the tax authorities recovering the tax you saved through the benefits during the breach period, plus penalties and late-payment interest. This article covers the grounds for exclusion, the consequences, and how to keep the status you have.
Start with the premise that changes how you see everything else. Once granted, HTP residency has no end date — but it lasts only as long as you comply. It continues until the resident chooses to leave or the Supervisory Board decides to exclude it, and keeping it means keeping the business project up to date and on track, filing reports and paying the administration fee. In other words, you hold the status on conditions; you do not own it outright. That is easy to forget once you are in and the benefits are flowing, which is exactly how residents drift into the problems that cost them the status. Treat residency as an ongoing obligation rather than a one-off achievement, and everything else in this article — the grounds and the consequences — comes down to avoiding mistakes that are entirely avoidable.
A company can lose the status in a limited number of ways. Some are neutral: the resident’s own application (voluntary exit) and the liquidation or reorganisation of the company. The ones that matter are exclusions by the Supervisory Board for breach. These include: failure to perform, or improper performance of, the resident agreement or the HTP Regulation; failure to deliver the business project, where the Board decides that continued residency is no longer justified; earning revenue from non-core activities outside the permitted list and the business project; missing the quarterly 1% administration fee or the annual reporting; anti-money-laundering and related violations; and providing false information to the HTP administration. What these have in common is that each one breaches a condition the status depends on — and, apart from voluntary exit and liquidation, it is the Supervisory Board that decides on exclusion.
The two ways a status ends are worth separating, because they are not equally painful. A voluntary exit — leaving on your own application — is clean: you stop being a resident from that point, you are not penalised for the compliant period behind you, and there is no clawback. Exclusion for breach is the opposite: it brings retrospective tax recovery for the breach period. That difference has a practical consequence that often surprises people. If a company can no longer meet the HTP conditions — say its activities have moved outside the permitted list, or it cannot deliver the business project — a planned voluntary exit is almost always better than carrying on until the Board excludes it. The voluntary route avoids the clawback that a forced exclusion for the same underlying problem would bring. Put simply, if the HTP no longer fits, leaving on your own terms beats being pushed out. Recognising this early, and choosing a clean exit over a slow-burning breach, can be the difference between a simple change of tax regime and a retrospective tax bill.
The first consequence is simple and immediate: once the status is lost, all HTP tax benefits and preferences end. The profit-tax exemption, the 9% personal income tax and the VAT reliefs all go, and the company moves to the general tax regime from the date the status is lost. The other advantages of residency go with them: visa-free entry and the simplified work-permit rules that made hiring foreign specialists easy, as well as currency-control relief and other perks. The company itself continues to exist — exclusion from the Park is not liquidation. You are not wound up; you simply become an ordinary Belarusian company again, taxed and regulated like any other. For a business built around the HTP regime, that alone is a major change. But it is not what does the most damage.
The consequence that turns a compliance slip into a serious financial problem is retrospective. Where the right to the benefits is lost, the resident must pay the taxes, fees and other mandatory payments it did not pay because of the benefits, for the period to which the loss applies, together with penalties and late-payment interest under the Tax Code. In plain terms: if you were in breach for a year, the tax you saved over that year can come back as a bill, with penalties and interest added. So the cost of exclusion is not only the regime you lose going forward; it is the tax you thought you had saved being reclaimed for the breach period. That is why a seemingly minor but prolonged breach — a steady stream of non-core revenue, a business project left to lapse — can end up costing far more than the benefits were worth over the same period. The clawback is the reason compliance is not optional housekeeping but basic financial self-protection.
The clawback is not a vague penalty; it follows a clear logic, and understanding it shows why it hurts. When the right to the benefits is lost, you are treated, for the relevant period, as if you had never had them, so the taxes the benefits exempted or reduced are recalculated at the standard rates and become payable. In practice, that means the profit tax you did not pay (at the standard rate), the difference in personal income tax (the standard rate instead of the HTP’s 9%), any VAT covered by the reliefs, and so on. This applies to the period for which the right is lost, which is tied to when the breach arose rather than simply to the date of exclusion. On top of that come penalties for non-payment and late-payment interest, which accrue over that whole period. The result is that a breach lasting, say, a year does not cost you one year’s benefits — it costs you the full standard tax for that year plus penalties and interest, which can far exceed the benefit you enjoyed. The longer the breach goes unaddressed, the bigger the bill: time is the multiplier. This is also why the date on which the breach is found to have arisen matters so much, and why a resident facing exclusion should look beyond the fact of the breach itself. Establishing when the non-compliance actually began, and whether it was a one-off or ongoing, can materially change the amount recovered. A breach that genuinely started last quarter produces a very different bill from one the authorities treat as running for two years. So the clawback is not a fixed figure handed down with the exclusion; its size depends on the period, and the period can be disputed on the facts — another reason to involve an adviser early rather than accept the first figure put forward.
Exclusion is not arbitrary; it follows a procedure, and knowing it helps a resident respond. A breach usually comes to light through the resident’s own reporting, the annual audit or monitoring by the HTP administration — a declaration that does not reconcile, non-core revenue in the accounts, a missed payment. The matter goes to the Supervisory Board, which decides whether to exclude the resident and, if it does, specifies the ground, the specific violation and the year in which it occurred (that year determines the clawback period). The resident is then removed from the register, the benefits end, and the tax recovery follows. Two points matter for a resident in this position. First, there is usually room to engage before and during the process — to explain, to correct, to show that the breach was isolated rather than systematic — and how convincingly you do so can affect the outcome. Second, a Board decision is not final: it can be challenged in court, which is why you should take advice as soon as exclusion becomes a real possibility, not after the decision has been made.
In practice, most exclusions are self-inflicted and preventable, and they tend to stem from a handful of avoidable triggers. Drifting into non-core revenue — income from activities outside the permitted list and the business project — is a common one, often without the resident realising that the income is non-core and therefore a breach. Letting the business project lapse, or falling short of its targets, is another. Missing the quarterly 1% payment or an annual report is a third: mundane, but enough. AML/CFT failures and gaps in ownership records complete the list. The fix is unglamorous but reliable: keep the business project up to date and on track, file and pay on time, stay strictly within the permitted activities, and keep your AML and ownership records in order. None of this is difficult; it is simply the part of residency that does not feel urgent until it suddenly is. That is why building it into how the company runs, rather than reacting once a problem surfaces, is what protects the status.
Most exclusions can be prevented, so the sensible approach is to treat compliance as a routine rather than a series of one-off tasks. Start with the business project. Make sure the company actually meets the targets set out in it, and update the project whenever the business changes direction, so that the document still describes what the company really does. Before signing a new contract or launching a new service, check that the activity appears on the permitted list and is covered by the project. Pay the quarterly 1% fee to the HTP administration on time, and file the annual reports and complete the audit by the deadlines. AML/CFT procedures and ownership records also need to be kept up to date. Once a year, set aside time to review all of these points together. A short internal review of this kind usually reveals small discrepancies long before they turn into a breach.
None of this takes much effort once it is part of normal practice. Problems tend to start when compliance is pushed to the bottom of the list and only gets attention after something has been flagged. A resident that keeps to this routine and speaks to an adviser whenever it is unsure about a new activity is very unlikely to lose its status.
It is also worth deciding who is in charge of all this. In some companies it is the finance director or the compliance officer; in others, an external adviser handles it on a retainer basis. What matters is that one person is accountable. In our experience, residents rarely lose their status because they set out to break the rules. Far more often, a report was not assigned to anyone, a new source of revenue was never reviewed, or a payment was overlooked during a busy quarter. Naming a responsible person and keeping a simple calendar of payment, reporting and audit deadlines removes most of that risk, and it costs very little compared with what HTP residency is worth.
What to do next depends on your situation. If you are a resident at risk — a breach has been flagged, a report missed, non-core revenue identified — act early and fix the problem: the difference between a corrected lapse and exclusion with a clawback often comes down to how quickly and convincingly you respond. If your residency is in good standing, build compliance into your processes and review it regularly so the status takes care of itself. Either way, this is specialist IT and corporate law territory, where early advice costs far less than a retrospective tax bill. For more on how the status is obtained and kept, see our HTP residency services; if you are worried about losing it, or want to make sure you won’t, get in touch.
Here is how it goes wrong. A software company — an HTP resident enjoying 0% profit tax and the 9% personal income tax — takes on a profitable line of work slightly outside its permitted activities, such as consulting or reselling third-party products, and books the revenue without flagging it as non-core. For a year or more, nobody stops it; the money is good. Then the annual audit, or a review by the HTP administration, picks up the non-core revenue. The matter goes to the Supervisory Board, which excludes the company, citing the non-core activity and the year. Now the consequences arrive all at once: the benefits end, the company moves to the general regime, and the clawback recovers the tax it would have paid for that period without the benefits, plus penalties and interest. The extra profit from the non-core work is often a fraction of the resulting bill. The company never set out to break the rules; it simply did not check whether the new revenue fell within its permitted activities. That is exactly the trap, and exactly why the check belongs before you take on the work, not after. Had the company caught it early — treated the work as falling outside the Park, moved it to a separate entity that is not an HTP resident, or sought advice before booking the revenue — it could have kept its status and done the work cleanly elsewhere. The lesson is not “don’t grow” but “grow deliberately”: check each new revenue stream against the permitted activities and keep non-core work outside the resident company.
A few common beliefs cost residents their status. That residency is permanent once granted — it isn’t; it is conditional, and the Board can exclude you. That losing it only affects the future — it doesn’t; the clawback reaches back over the breach period. That a little non-core revenue is harmless — it isn’t; non-core income is a breach regardless of size. That a missed report or a late 1% payment is trivial — both are genuine grounds for exclusion. That exclusion means liquidation — it doesn’t; the company survives, just without the regime. And that once a problem is found, it is already too late — often it isn’t; engaging and correcting early can change the outcome. Most of these stem from treating HTP residency as a prize won rather than a status to maintain. See it the other way — as a conditional regime you keep by complying, with a retrospective cost if you don’t — and the mistakes become obvious and avoidable.
Neutral routes, and the breaches that cost you the status (and risk a clawback).
| Your own application | Voluntary exit from the Park |
| Liquidation or reorganisation | The company ceases to exist in its current form |
| Failure to deliver the business project | The Supervisory Board decides that continued residency is not justified |
| Non-core activities | Revenue from activities outside the permitted list or the business project |
| Missing reports or the 1% fee | Failure to meet reporting obligations or pay the quarterly administration fee |
| Breach of the resident agreement or HTP rules | Failure to perform, or improper performance of, the resident agreement, including AML violations |
| False information | Providing misleading information to the HTP administration |
*A general guide only: the grounds and consequences are set by HTP legislation and may change — check the current position for your company.
Yes. HTP residency is a conditional status, not a permanent one. It continues as long as you comply, but the Supervisory Board can exclude a resident for breach; a resident can also leave voluntarily or lose the status through liquidation or reorganisation. So it is something to maintain, not a one-off win — and losing it has real consequences, including a possible clawback of past tax savings.
The neutral grounds are voluntary exit and liquidation or reorganisation. The breach-based grounds are: failure to perform, or improper performance of, the resident agreement or the Park’s rules; failure to deliver the business project; earning revenue from non-core activities; missing the quarterly 1% fee or the annual reporting; AML violations; and providing false information. Breach-based exclusions are decided by the Supervisory Board.
The HTP Supervisory Board — the same body that decides on registration also decides on exclusion for breach. Voluntary exit (on the resident’s own application) and loss of status through liquidation or reorganisation do not depend on a Board decision, but every breach-based exclusion does, and the decision specifies the ground and the year of the violation.
They end when the status is lost. The profit-tax exemption, the 9% personal income tax and the VAT reliefs no longer apply, and the company moves to the general tax regime, losing the other advantages as well (visa-free entry, simplified work-permit rules, currency-control relief). The company itself continues to exist — exclusion is not liquidation — but the regime that made it attractive is gone from that point.
Yes, where the status is lost for breach. The resident must pay the taxes, fees and other mandatory payments it did not pay because of the benefits, for the period to which the loss applies, plus penalties and late-payment interest. A prolonged breach can therefore turn the tax you thought you had saved into a retrospective bill — the most serious consequence of exclusion.
Revenue from activities outside the permitted HTP list and your declared business project. HTP residents may only earn income from activities the Park allows and that are covered by their business project; anything else is non-core income and a breach of the regime — and a common, often inadvertent, reason residents lose the status. Staying strictly within the permitted activities is essential.
Through avoidable, usually prolonged compliance failures: drifting into non-core revenue, letting the business project lapse or underperform, missing the quarterly 1% payment or annual reports, and AML or ownership-record failures. Most exclusions are self-inflicted and preventable — which is good news, because keeping the status is largely a matter of avoiding these pitfalls.
Keep the business project up to date and on track; file reports and pay on time (including the quarterly 1% fee); stay strictly within the permitted activities; and keep your AML and ownership records in order at all times. Build compliance into the way the business operates and review it regularly. If a problem is flagged, act quickly to resolve it — a prompt, credible response is often what prevents exclusion.
For the breach period, you are treated as if you never had the benefits, so the exempted or reduced taxes are recalculated at standard rates and become payable (profit tax at the standard rate, personal income tax at the standard rate instead of 9%, any VAT covered by the reliefs). This applies to the period for which the right is lost (tied to when the breach arose), plus penalties and late-payment interest. The longer the breach, the bigger the bill.
A breach comes to light (through reporting, the audit or monitoring by the HTP administration); the Supervisory Board decides whether to exclude and, if so, specifies the ground, the violation and the year; the resident is removed from the register, the benefits end, and tax recovery follows. There is usually room to engage and correct the problem, and a Board decision can be challenged in court — so take advice as soon as exclusion becomes a real possibility, not afterwards.
Usually, yes, if you can no longer comply. A voluntary exit is clean — no clawback — whereas exclusion for breach triggers retrospective tax recovery. So if your activities have moved outside the permitted list or you cannot deliver the business project, a planned voluntary exit is better than carrying on until the Board excludes you for the same problem. Leaving on your own terms avoids the clawback a forced exit would bring.
Potentially, yes. Non-core revenue (income from activities outside the permitted list and the business project) is a breach regardless of size, and a common reason residents are excluded. The risk grows the longer it continues, because the clawback covers the breach period. If you have taken on work you are unsure about, have it reviewed promptly and, if necessary, change course — acting early costs far less than a retrospective bill.
HTP residency is a conditional status that lasts only as long as you comply, and the Supervisory Board can exclude a resident for failing to deliver the business project, non-core activities, missed reports or fees, breaches of the rules, or false information. Losing it means losing the regime and — where the loss follows a breach — a clawback of the tax saved over the breach period, plus penalties and interest. So treat the unglamorous compliance work as the core of residency: keep the project current, file and pay on time, stay within the permitted activities, and fix problems early. Know how you can lose the status, and you will keep it.
If you are an HTP resident and want to be sure you will not lose your status — or you are facing exclusion and need to protect your position — tell us about your situation, and we will advise on compliance and the risks. Get in touch, and read our guide to obtaining HTP resident status.
After the company’s owners decide to liquidate, the process is controlled by the state and regulated by the relevant legislation. In our article, attorneys talk about the main features of the liquidation of companies in Belarus, the rules and requirements that must be followed during this procedure. In the case of liquidation of the company, […]
Receiving an inheritance is traditionally perceived as the acquisition of property or money, but in practice it can result not only in benefits but also in significant responsibilities. Along with the inheritance, the heir receives not only the assets, but also the debts of the deceased, as well as certain obligations to maintain the property. […]
On 28 September 2026, Belarus’s High-Tech Park registered the country’s first two “crypto-banks” — a legal status that barely exists elsewhere. The headline invites two misreadings: that a crypto-bank is a crypto exchange dressed up as a bank, or a bank that has started holding crypto. In law it is neither. It is a purpose-built […]
