Transfer Pricing Rules for IT Services in Belarus: A Practical Guide

Transfer pricing is rarely the first thing a founder thinks about when setting up an IT operation in Belarus. The conversation usually starts with HTP residency, headline tax rates, payroll, and headcount. Transfer pricing comes up later — usually in one of two ways. The tax authority requests an economic justification form, or a group restructuring reveals that intra-group invoices haven’t been priced like they would have been between strangers.

By that point the question isn’t whether transfer pricing rules apply. It’s whether the prices the Belarusian entity has been charging (or paying) its parent company, sister company, or shared services hub can be defended against the tax authority’s review — and what evidence exists to do it.

This guide breaks down how the rules actually work for IT services companies operating in Belarus in 2026: what counts as a controlled transaction, which pricing methods are accepted, what documentation has to exist before a request comes in, and where HTP residents sit in the picture. Written for finance leads, founders, and group tax teams making decisions, not for tax lawyers writing footnotes.

The legal basis: Article 30-1 of the Tax Code

Belarus introduced transfer pricing rules in 2012 under Article 30-1 of the Tax Code and substantially overhauled them in 2019 to align more closely with OECD principles. The framework draws on the OECD Transfer Pricing Guidelines as a reference point, but Belarus applies its own codified rules — not the OECD text directly.

The core principle is the standard one. Cross-border transactions between related parties have to be priced as if the parties were independent. Where prices deviate from market levels and that deviation reduces Belarusian corporate income tax, the tax authority can adjust the profit tax base and assess additional tax, plus penalties.

Two specifics matter from the start. First, Belarus has its own definition of related parties, broader than many groups assume. Direct or indirect ownership of more than 20% triggers the test, but so do common management, family ties between owners, and several other relationship patterns. Second, the rules apply transaction by transaction within an annual aggregate, not on a group-wide basis.

What counts as a controlled transaction for an IT company

For the typical international IT structure operating in Belarus — a local entity providing development services to a foreign parent or a regional services hub — the relevant category is foreign trade transactions with related parties. Article 30-1 covers transactions involving goods, works, services, and property rights, which sweeps in the full range of activity an IT company conducts: software development, technical support, R&D services, IP licensing, and intra-group cost recharges.

The monetary threshold for most taxpayers is BYN 400,000 per related counterparty per calendar year (roughly USD 120,000 at recent exchange rates). The threshold rises to BYN 2,000,000 for major taxpayers on the Ministry of Taxes and Duties’ list of large payers and for transactions in strategic goods. Once the aggregate of all transactions with a single related counterparty crosses the threshold in a tax year, every transaction with that counterparty falls under transfer pricing control — not just the marginal amount above the line.

A few patterns are particularly common for IT services and worth flagging:

• A Belarusian development entity invoicing a foreign parent for engineering services on a cost-plus basis.
• An HTP resident licensing software or intellectual property to a non-resident affiliate.
• A regional services hub allocating shared management, marketing, or back-office costs to the Belarusian entity.
• Intra-group financing — loans from the parent to the Belarusian subsidiary, which also engage thin capitalization rules under separate provisions.

In each case, the question the tax authority will ask is straightforward. Would an unrelated party at arm’s length have agreed to the same price under the same conditions?

The five accepted pricing methods

Belarusian transfer pricing legislation enumerates five methods, applied in a defined hierarchy that mirrors the OECD structure:

1. Comparable uncontrolled price method (CUP). Compares the price charged in a controlled transaction with the price in a comparable uncontrolled transaction. The tax authority’s first preference, when reliable third-party benchmarks exist.
2. Resale price method (RPM). Used when the Belarusian entity buys from a related party and resells to independent customers. Less common in pure IT services structures.
3. Cost plus method (CPM). The dominant method for captive development centers — Belarusian entity costs plus an arm’s-length markup. The markup itself is what gets benchmarked.
4. Comparable profits method. Aligned with the OECD’s transactional net margin method (TNMM). Compares net profitability ratios across comparable companies.
5. Profit split method. Applies where both parties contribute uniquely valuable intangibles — relevant for genuine joint R&D, less so for routine offshore development.

Two features of Belarusian practice diverge from how this plays out in OECD jurisdictions. The tax authority frequently uses “secret comparables” — internal data and benchmarks not disclosed to the taxpayer — which makes it harder to anticipate where the arm’s-length range will land. And since 2019, the 20% safe-harbour deviation from the arm’s-length range has been removed. The range is the range, defined by minimum and maximum values, and a price outside it is challengeable.

Documentation: the two forms

Belarusian transfer pricing reporting works in two layers. The economic justification form is the baseline obligation — it applies to most controlled transactions and has to be provided on request from the tax authority. It captures financial information and the conditions of the transaction but does not require disclosure of the pricing method used. Transfer pricing documentation is the more comprehensive form, required for major transactions by major taxpayers (foreign trade transactions exceeding BYN 1,000,000 per counterparty per tax year for taxpayers on the Ministry’s large-payer list).

Both are submitted on request rather than proactively. The tax authority can ask during a field audit or a desk audit, and the deadline to respond is usually between 2 and 10 working days — not the kind of window in which a benchmarking study can be produced from scratch. International tax practice tracked this shift when the framework was rebuilt, and the enforcement weight has only increased since.

Controlled transactions are also flagged at the electronic invoice level. The e-VAT portal requires payers to mark transactions falling under transfer pricing control on the electronic invoice itself. This is a notification mechanism that runs alongside the on-request documentation regime — separate, automatic, and visible to the tax authority in near real-time.

HTP residents are still in scope

A common misconception is that High Tech Park residents — with their 1% unified tax and zero VAT on exports — sit outside transfer pricing rules. They do not. HTP residency provides a preferential tax regime; it does not exempt the resident from Article 30-1.

In practice, HTP residents face transfer pricing scrutiny on two specific fronts. The first is intra-group services pricing — when the HTP resident is invoicing a related party abroad, the price has to be defensible as arm’s length even though the Belarusian profit tax rate is zero. The second is the boundary between qualifying HTP activity and non-qualifying activity. If transfer pricing rules require an adjustment that pushes part of the revenue outside qualifying activity, the standard 20% corporate income tax rate can apply to the adjusted portion, not the 1% HTP rate.

The interaction between HTP status and transfer pricing is one of the more technically demanding areas in practice. A transfer pricing adjustment can affect not just the profit tax base but the integrity of HTP residency itself, which is why most groups treat it as a structuring question at the entry stage rather than a downstream compliance item. The recurring tax mechanics for IT companies in Belarus make this connection more material than the headline 1% rate suggests.

Penalties and what audits actually look like

If the tax authority concludes during an audit that prices were not at arm’s length and Belarusian profit tax was underpaid, the consequences stack:

• The corporate income tax base is adjusted upward, and additional tax is assessed at the standard rate (20% outside HTP; potentially the same if HTP qualifying activity status is challenged).
• A penalty of 40% of the underpaid tax applies on top of the additional assessment.
• Late payment interest accrues from the original due date.
• Periods from 2019 onward are open to review; multiple periods are often requested at once.

The 2019–2022 transition window that suspended late-payment penalties is well behind us. Current audits run at full enforcement weight, and tax authority practice on requesting documentation has been in active enforcement mode since 2019.

The audit pattern most common for IT services companies is a desk review triggered by the electronic invoice flag, followed by a request for the economic justification form, followed (if the tax authority is dissatisfied with the response) by a field audit covering multiple prior years. Most disputes settle at the documentation stage. The ones that escalate generally do so because the taxpayer didn’t have a contemporaneous pricing study, the benchmarking was thin, or the functional analysis didn’t match how the entity actually operated.

Practical compliance — what gets you through an audit

The pattern across IT companies that handle Belarusian transfer pricing well, and the ones that scramble when a request comes in, is consistent enough to summarise:

• Map controlled transactions at the start of the year. Identify every related party, the type of transaction, and the expected annual aggregate. Don’t wait for the year-end close to discover the threshold has been crossed.
• Document the method choice in writing. The economic justification form doesn’t require disclosing the method, but having the method choice and supporting analysis on file is what supports a defence if the position is challenged.
• Run a benchmarking study annually for material transactions. External databases for Belarusian comparables are thin, which is why most groups use regional comparables (CIS, Eastern Europe) supported by reasoned adjustments. The study has to be defensible, not just present.
• Align the functional analysis with the actual operation. If the legal structure says cost-plus services and the substantive activity includes IP development, the functional analysis has to reflect that or it won’t survive review.
• Watch the electronic invoice flagging. Mis-flagging or failure to flag is the most common procedural trigger for a transfer pricing inquiry.
• Track legislative changes. The Tax Code is amended every year, and transfer pricing provisions have been touched in most recent annual cycles.

For groups without an internal Belarusian tax function, this is usually handled by a local advisor who carries the file from year to year — the documentation is cumulative, and the value of consistent positioning across years compounds. Companies running the full HTP residency setup often build the transfer pricing position in at the structuring stage so it doesn’t have to be retrofitted later.

The bottom line

Transfer pricing in Belarus is not the kind of rule that announces itself loudly. It runs quietly in the background — through electronic invoice flags, threshold tests, and audit triggers that don’t surface until the tax authority opens a file. The companies that handle it well treat it as a year-round discipline: map controlled transactions at the start of each year, document method choices contemporaneously, run benchmarking studies before they’re requested, and keep functional analyses aligned with operational reality.

For IT services groups operating in Belarus — whether through a captive development center, an HTP resident, or a regional services hub — transfer pricing is a routine part of the compliance burden, not a special project. Most of the operational time goes into the documentation, the benchmarking, and the cross-checking between legal structure and substance. Done well, it’s invisible. Done badly, it’s the one item on the year-end close that can rewrite a tax position three years after the fact.

The teams that get this right typically run it as part of integrated accounting and tax services rather than as a standalone project, so the transfer pricing position is built into the year-end close rather than bolted on afterwards. That’s the practical answer to most of the questions this guide has covered — and the one that keeps the compliance burden proportionate to the actual exposure.