For a foreign company that has just become a resident of the Belarusian High-Tech Park, the first year-end close can feel like it should be the easy part. The regime removes profit tax on core activity, exempts a wide range of turnover from VAT, and generally rewards residents with one of the lightest tax burdens in the region. It is tempting to assume that light tax means a light close.
It does not. The year-end close for an HTP resident is not a single filing on a single date — it is a season that runs from the final weeks of the reporting year until the start of the following summer, with two distinct finish lines rather than one. This matters most for the businesses that make up the bulk of the Park: foreign-owned R&D centres, product companies, and fintech and crypto operators running cross-border. The teams that struggle are almost always the ones that planned for the first finish line and forgot the second. This article walks through the realistic timeline, deadline by deadline, and then covers the points where closes reliably come apart.
Belarus runs on the calendar year. The financial year ends 31 December, and everything downstream of that date is measured from it.
The close is not a single event. It is a sequence that runs from early January to the start of July, with three phases stacked on top of each other:
The statutory close — bringing the books to a clean year-end position under Belarusian Accounting Standards (BAS), reconciling every account, and preparing the annual financial statements.
The tax close — finalising the annual returns, confirming the qualifying-revenue treatment holds for the whole year, and settling any balance owed.
The audit — the mandatory independent audit of the annual financial statements, which every HTP resident must complete regardless of size.
The mistake is to treat these as three things that happen one after another with comfortable gaps between them. In practice they overlap, depend on each other, and a delay in the first phase compresses the time available for the third — the phase with the least give in it.
The statutory close is the foundation. Everything downstream is built on the annual financial statements, so if the books aren’t right, nothing after them will be either.
For a typical thirty-person HTP resident with nothing unusual in the year, the statutory close takes one to three weeks of concentrated work — provided the monthly books were kept properly. When they weren’t, and there are unreconciled months, a backlog of primary documents, or a bank feed that stopped matching the ledger in September, the close stretches, sometimes dramatically.
The core tasks here are the unglamorous ones: reconciling all bank accounts to the ledger, closing out payables and receivables, confirming the treatment of foreign-currency balances at year-end rates, verifying fixed-asset registers and depreciation, clearing suspense accounts, recognising accrued expenses in the right period, and agreeing intercompany balances with the parent.
The annual accounting policy statement is due in this window too. Under current rules it must reach the tax authorities by 31 March, and any amendments approved during the year must be filed within thirty days of approval — a smaller obligation that is easy to forget until it’s late.
Where it goes wrong: phase one usually falls apart in January, the moment someone realises the monthly books weren’t as tidy as everyone assumed. A month that supposedly “closed” during the year often closed in name only. A payment got booked with no paperwork behind it. Currency differences never got posted. A reconciliation quietly got skipped because there was a deadline that day. You don’t notice any of it until the annual close drags every account back to a position you can actually defend — and by then you’re fixing it in the worst possible week to be fixing anything. That’s the whole reason bookkeeping recovery shows up on so many year-end to-do lists. It’s not unusual at all.
Running alongside the statutory close is the tax close. For an HTP resident, this is less about the profit-tax return that dominates a standard-regime company’s year and more about confirming the preferential treatment applied all year actually holds.
The headline HTP levy is 1% of gross revenue, far simpler than the standard profit-tax regime that a non-resident company would face — the difference between the two, and what the standard rules actually demand, is set out cleanly in the PwC tax summary for Belarus. But “simpler” is not “automatic.” The annual close is where the qualifying-revenue question gets settled for the whole year: which revenue streams fell inside the resident’s registered activities and qualified for the regime, and which — if any — fell outside and have to be treated differently. A resident that added a new revenue line mid-year without checking it against its registered activities can find, at year-end, that a slice of income doesn’t sit cleanly inside the 1% treatment.
The annual returns come together in this phase and are due, with the annual financial statements, by 31 March. For any local employees holding parent-company equity — RSUs or options that pay out foreign-source income — personal annual returns are relevant here too, and easy to overlook because they sit at the intersection of the individual and the company.
The classic phase-one stumble is a January one: you open the books expecting them to be clean and find out they aren’t. “Closed” months have a way of being closed loosely. Maybe a payment went in without supporting documents, maybe some currency differences were never posted, maybe a reconciliation slipped through when everyone was up against a deadline. Whatever it was, it stays invisible right up until the annual close forces every single account to stand on its own — and now you’re sorting it out with almost no time to spare. Which is exactly why fixing up the books at year-end is such an ordinary request, not some rare emergency.
This is the phase that catches foreign owners off guard, because in many home jurisdictions a company of this size would never be audited. The HTP regime removes that discretion: the mandatory audit of the annual financial statements applies to every HTP resident, regardless of headcount or revenue.
The deadlines are firm and worth committing to memory. The audit must be completed no later than 30 June of the year following the reporting year, and the auditor’s opinion submitted to the HTP Administration no later than 1 July. Separately, confirmation that the audit took place is filed with the Ministry of Finance through its online questionnaire. The formal requirements and the current state of the regime are set out on park.by, the Park’s official portal.
An audit is not a same-week exercise. The auditor needs the finalised statements, the underlying ledgers, contracts, bank confirmations, payroll records, and answers to whatever the review turns up. A clean audit of a straightforward resident still runs several weeks from engagement to signed opinion, and if the auditor finds something — a treatment they disagree with, a documentation gap, a currency-control issue — the timeline extends while it’s resolved.
The mechanics of the audit deadline, and how to organise the process without losing weeks to back-and-forth, are covered in more detail in this breakdown of the mandatory audit for HTP residents.
Where it goes wrong: the audit gets treated as the last item in a sequence rather than a phase with its own runway. A resident that only starts thinking about the auditor once the statutory close is finished finds that booking one in May means competing for capacity with every other HTP resident doing the same thing. Good auditors fill their spring calendars early, and leaving the engagement that late is how a June deadline becomes a scramble — or a miss, which carries administrative consequences and complicates the resident’s standing with the Administration.
For an HTP resident earning in USD or EUR and paying salaries and suppliers in Belarusian rubles, currency control runs through the entire year and surfaces at year-end in the reconciliation. Cross-border services contracts above defined thresholds have to be registered with the servicing bank before payments clear, supporting documentation lodged within set windows, and statements matched on both sides. HTP residents get a simplified version of this regime compared with standard-regime companies — but simplified is not absent, and the close is where any gaps become visible. An invoice that went out before its contract was registered, a receipt that arrived without matching documentation, a foreign-currency balance that was never revalued: these turn up when the books are forced to a defensible position. The current rulebook sits with the National Bank of the Republic of Belarus.
Almost every foreign-owned HTP resident has a second close running in parallel — the parent’s. The local entity closes to Belarusian Accounting Standards; the group consolidates under IFRS. The bridge between the two is where a surprising amount of year-end friction lives, and the problem is rarely the numbers themselves. It’s ownership. The local statutory accounts close on the Belarusian timeline, the group needs IFRS-adjusted figures on the parent’s audit schedule, and the reconciliation between them lives in a working file that too often nobody owns. When the IFRS adjustments aren’t done until the parent’s auditors ask for them, the two sets of numbers drift, and reconciling them after the fact is slower than building the bridge as you go.
Groups that run this cleanly assign the BAS-to-IFRS reconciliation explicitly — usually to the same firm handling the statutory accounting — and plan it from the first month of the year rather than the last. The broader rhythm of running a Belarusian entity from abroad, including how the reporting calendar synchronises with a parent’s audit cycle, is laid out in this guide to managing a foreign subsidiary remotely.
Pulling the phases together, here is the rhythm a well-run HTP resident follows:
January — Statutory close begins: bank reconciliations, year-end currency revaluation, closing payables and receivables, clearing suspense accounts. First contact with the auditor to book capacity.
February — Statutory close finalised, annual statements drafted. Tax close underway: qualifying-revenue review, annual returns prepared. IFRS adjustments started for the parent.
By 31 March — Annual financial statements filed, annual returns submitted, accounting policy statement lodged, personal returns handled for employees with foreign-source income.
April to May — Audit fieldwork: the auditor works through the statements and raises questions, the team responds, and the IFRS reconciliation is handed to the parent.
By 30 June — Mandatory audit completed.
By 1 July — Auditor’s opinion submitted to the HTP Administration; confirmation filed with the Ministry of Finance.
The dates are fixed. What varies is the slack between the phases — entirely a function of how clean the monthly books were and how early the audit was booked.
Across dozens of year-end closes, the failures cluster into the same short list: loose monthly books that become a January reconstruction exercise; the qualifying-revenue surprise, where a mid-year model change was never checked against registered activities; the late audit booking, where auditor capacity is gone by the time the statutory work finishes; the BAS-to-IFRS gap, with no named owner for the reconciliation to the parent’s accounts; and the currency-control clean-up, where transactions that ran ahead of their documentation all surface at once.
None of this comes down to accounting, when you look closely. It comes down to two things: someone being clearly on the hook for each task, and the work not getting deferred until December. Sort those out — a calendar with an owner next to every deadline, and a monthly rhythm you actually stick to — and these problems mostly stop happening.
That is also why so many foreign-owned residents run the annual close through a single provider that already holds the statutory accounting, the tax treatment, and the audit coordination under one roof. When the same team that kept the books all year runs the close and manages the auditor, the handoffs that cause most year-end trouble simply don’t exist — which is exactly what specialist accounting support for HTP residents is built around.
It is, and it’s one of the first things that trips up foreign founders. There’s no revenue floor or headcount cut-off that lets a smaller resident skip it — the requirement is attached to the status itself, not to how big you are. A company of the same size in another country might never need an audit, so the assumption that a lean team won’t either is fair enough. In the Park, though, residency is what puts the audit on your calendar, and it applies from your very first reporting year.
The statutory close for a typical thirty-person resident with clean monthly books runs one to three weeks. The audit adds several weeks on top, and pulling the numbers into IFRS for a parent adds more still. The full sequence from year-end to a signed audit opinion spans the first half of the year — which is why the deadlines run to 30 June and 1 July rather than closing in the first quarter.
The levy is simple, but the close isn’t the same thing as the tax rate. The annual close is where the qualifying-revenue question is settled for the whole year, where the mandatory audit happens, and where the BAS-to-IFRS bridge for the parent gets built. The low headline rate doesn’t remove any of that.
It carries administrative consequences and complicates the resident’s interaction with the HTP Administration and supervisory authorities. Because good auditors fill their spring calendars early, the practical risk isn’t a decision to skip the audit — it’s leaving the engagement so late that capacity is gone and the deadline slips by default.
Yes. The accounting close, statutory filings, Park reporting, and audit coordination can all be run remotely, which is how most foreign-owned residents operate. What matters is that the work is organised around the HTP calendar and kept audit-ready throughout the year, not where the team happens to sit.
The year-end close is where an HTP resident’s whole year of financial discipline is tested at once. The timeline itself is not complicated — statutory close through early March, annual filings by 31 March, mandatory audit by 30 June, auditor’s opinion by 1 July. What makes it hard is that each phase depends on the one before it, the deadlines have no give, and the audit — the phase with the least flexibility — sits at the end.
Simplicity isn’t what makes a close go smoothly. Discipline is. Keep your monthly books tidy and defensible. Check every pivot in your business model against your registered activities while it’s fresh, not at year-end. Book the auditor before everyone else does. Skip any of that, and the problem doesn’t disappear — it just waits until spring to show up.
If you’re approaching your first year-end as an HTP resident, or inheriting a set of books that drifted during the year, the right move is to map every deadline to a named owner now — and close the gap between monthly discipline and the annual close before January forces the issue. If you’d rather work through that calendar with a team that runs these closes every year, contact us and we’ll take it from your current position.
Hackathons have long become an integral part of the Information Technology ecosystem worldwide, and Belarus is no exception. They are especially relevant for participants of the High-Tech Park, where innovation, startups, and the development of new products are at the core of activity. A hackathon is not merely a competition for programmers; it is a […]
Most EOR invoices get paid on trust. One lands at the start of the month, the total is close to last month’s, and someone in finance signs it off before lunch. That holds up right until it doesn’t — until a leaver turns out to have been paid for two months after they left, or […]
Most foreign technology groups arrive in Belarus with a familiar structure: a parent company in the US, the EU, the UK, or the UAE owns a Belarusian entity that writes code, runs an R&D function, or maintains a product for the group. Money moves between them constantly — the local company invoices the parent for […]
