How to Set Up an Offshore Development Center (ODC) in Minsk: Legal, Tax, and Operational Roadmap

A pattern we’ve watched repeatedly over the past two years.

A foreign-owned ODC isn’t built the moment a company decides, “We should hire some engineers in Belarus.” It’s built much later — usually 18 to 36 months after the first Belarusian engineer signed on through an EOR, once the team has scaled past fifteen or twenty people, and once the operational control gap and the structural cost stack have begun to argue for a permanent presence on the ground.

The conversation usually starts with the COO or the head of finance, not with the head of engineering. The engineering side is typically happy with what they have. It’s the operational and financial side that begins to feel the friction — EOR margin compounding monthly, decisions that need a Belarus-based counterparty to sign things, IP chains that everyone hopes are clean but nobody has properly stress-tested. And the right answer, in our experience, isn’t always to convert.

This article walks through the framework. When an ODC is the right answer. When it isn’t, even when the team has reached the size where the conversation usually starts. And when the answer is yes, how the setup actually plays out in 2026 — including the parts that blow up timelines if you don’t see them coming.

ODC vs. EOR — the question before the question

Too many foreign clients ask “How do I set up an ODC in Belarus?” when the question they should be asking, honestly, is “Do I actually need one yet?” The setup work is structural. It costs time, attention, and political capital inside the foreign parent. If the team size and operational complexity don’t yet justify it, the right answer is to stay on the EOR model for another year and revisit. The question of when to convert deserves more space than it usually gets.

EOR remains the right answer when

• Team size is under 15–20 engineers and not trending sharply higher.
• The Belarus team is supporting a non-Belarus headquarters, and the engineers don’t need a direct contractual relationship with the foreign parent.
• Banking simplicity matters more than tax optimization at the current scale.
• The foreign parent doesn’t want the compliance, HR, and reporting overhead that a Belarusian entity carries — even an HTP-resident one.

ODC becomes the right answer when

• Team size has stabilised above 20 and is trending toward 40 or more.
• The Belarus operation needs commercial decision rights — signing local supplier contracts, leasing office space, building its own employer brand presence.
• EOR margin (typically 8–15% of total monthly payroll for an established relationship) starts to materially exceed the cost of running a local entity.
• Operational sovereignty — equipment ownership, office leases, local vendor relationships — becomes important to the business.
• The structural HTP advantages would be larger as a direct resident than as a client of an HTP-resident EOR.

This is the section the linear how-to articles tend to skip. We’re foregrounding it because the conversion decision is more consequential than the conversion mechanics. The mechanics are well-understood. The decision is what foreign founders sometimes get wrong, by deciding too early or by deciding too late.

The HTP framework — why almost every serious ODC ends up there

Most foreign-owned ODCs in Belarus are residents of the High-Tech Park. The alternative — a standard Belarusian limited liability company without HTP residency — is structurally uncompetitive for IT operations of any meaningful scale.

The High-Tech Park is the special legal and tax regime created for IT companies in Belarus. As of 2026 it hosts over a thousand resident companies, providing the operational framework that most foreign clients ultimately work through whether directly (as an ODC) or indirectly (as an EOR’s client).

The substantive HTP benefits, in summary:

• 9% personal income tax on engineer wages (versus the standard 13%).
• Social fund contributions calculated on the average national salary, not the engineer’s actual full salary — this is the structural saving that compounds fast at scale.
• 0% VAT on most IT services exports.
• 9% corporate profit tax (versus the standard 20%).
• Reduced rates on dividends and royalties for residents.
• English-language commercial contracts permitted.
• Elements of English commercial law accommodated in commercial agreements.
• Simplified residency procedures for foreign IT specialists.

Qualification turns on whether the company’s principal activity falls inside the HTP-permitted activity list (software development and a number of related categories all qualify). The Ministry of Economy HTP overview has the current details. In practice, foreign-owned IT companies that meet the activity criteria almost always qualify. The application process is procedural rather than discretionary, but it isn’t instant — typically 30 to 60 days from filing, sometimes longer if the business plan triggers additional review questions.

The legal entity setup, step by step

The actual mechanics walked through honestly. Not a checklist — a narrative of how the work sequences and where the time goes.

Entity type

Most foreign-owned ODCs in Belarus are limited liability companies. 100% foreign ownership is permitted. Minimum charter capital requirements are trivially low. Joint-stock company structures exist but are rarely used for ODC purposes; the LLC is the standard answer.

Registration

Through the territorial unified registration body for the district where the entity will sit. Core registration is typically 5 to 10 business days from filing — if the document set is complete. The document set includes founding documents, founder identification (apostilled and translated where the founder is foreign), proof of legal address, and the charter. Getting the document set complete is the part that takes time; the registration itself is fast once you’re ready to file.

HTP residency application

Separate process, usually run in parallel with entity registration or immediately afterward. Application includes the business plan (specific format), activity classification, founding documents, and supporting attachments. Approval typically 30 to 60 days. The administration occasionally comes back with clarification questions — building in a two-week contingency for this is wise.

Banking account opening

This is the step where timelines stretch most often. Foreign-owned entities face KYC processes that vary materially by bank. Some Belarusian banks have established workflows for foreign-owned IT entities and onboard them efficiently in four to six weeks. Others apply heightened compliance scrutiny that runs eight weeks or longer. The practical lesson: pick the bank early, start the conversation in week one, not week six, and treat the banking relationship as the gating dependency it usually is.

Tax registration and currency control

Tax registration is standard and runs in parallel with the entity setup. Currency control compliance deserves a specific mention. Belarus operates a currency control regime that affects how foreign-owned entities move money in and out. Manageable, but it needs to be set up correctly from the start — your first inbound payment from the foreign parent will be reviewed under currency control rules, and a smooth pass on that review is largely about having registered the relevant agreements correctly at the outset.

Personnel hire and onboarding

Either fresh hires into the new entity or — more commonly for clients with established EOR-based teams — conversion of existing engineers from the EOR into the new entity. The conversion path is the typical scenario for the audience this article is written for, and it is covered in its own section below.

Honest framing on overall timeline: a clean setup typically runs 3 to 4 months end-to-end. A rushed setup runs 2 months and accumulates problems that surface in year one. The right pace is the unrushed pace.

The EOR-to-ODC conversion — the path most readers are on

This is the specific scenario that applies to most foreign clients who ask the ODC question — they already have engineers in Belarus through an EOR and are converting to a directly-owned entity. The mechanics are well-trodden but easy to get wrong.

The sequence that works

Set up the ODC entity and obtain HTP residency before terminating EOR contracts. This sounds obvious; it isn’t always done. The window between the EOR contract ending and the new entity’s first payroll is the window where engineers feel uncertain about their employment status, where small problems become big ones, and where attrition risk is highest. Don’t open that window if you can avoid it. Run the new entity in parallel for a transition period.

Negotiate transition terms with the existing EOR early in the process. Most EORs cooperate with conversions — they understand that a client moving to ODC is a sign they did their job well. Some try to extract additional margin during the transition (longer notice periods, transition fees, charges for assistance with paperwork). Plan for both. Read the existing EOR contract specifically for the termination and transition clauses before you start, not after.

Re-hire each engineer into the new entity with continuity of service preserved where possible. Belarusian labour law has specific rules around continuity of service, vacation accrual, and severance — getting this right matters for engineer morale and for legal hygiene. Most local labour counsel will guide this in detail.

Transfer equipment ownership if the EOR was the legal owner. Negotiate this as part of the transition; some EORs sell at book value, others request a small premium.

Re-paper the IP assignment chain. This is the moment to fix anything that wasn’t clean originally. The new chain runs engineer → ODC entity → foreign parent (or, if the ODC is the foreign parent’s directly-owned subsidiary, engineer → ODC, with the parent owning the ODC and therefore indirectly the IP). Either way, get the assignment language fresh and clean. Don’t carry forward language from the previous EOR contracts without reviewing it.

Communicate the change to engineers carefully. The anxiety engineers feel during an employer change is real and well-founded — even when nothing actually changes for them in terms of compensation or working conditions. Clear, early communication and individual conversations prevent the avoidable attrition we’ve seen at clients who handled this less attentively.

Common conversion mistakes

• Setting up the new entity but starting payroll before HTP residency is granted — which forces the entity to operate under non-HTP cost structures for the first quarter and erodes the conversion economics.
• Terminating EOR contracts before the new entity’s banking account is operational.
• Forgetting to re-paper the IP assignment chain. The old chain (engineer → EOR → foreign parent) breaks when the EOR exits. A new chain has to be in place before the transition completes.
• Not communicating early to engineers. By the time HR explains the change, anxiety has spread informally and some engineers are already in recruiter conversations.

Operational setup — what the entity actually runs

Beyond the legal setup is the operational stack the entity needs to function. Quick walk-through of the components and how foreign clients typically resolve each.

Office or remote

Belarusian IT in 2026 is largely remote-first. The default for engineering work is hybrid or fully remote, and an entity can run that way without strict physical office requirements. That said, a small Minsk office signals seriousness, creates a center of gravity for the team, and provides a credible address for visiting clients and partners. Most ODCs settle into a small office (200 to 500 square meters) in central Minsk districts — Niamiha, Centralny, the area around Pobediteley Avenue — housing 30 to 50 hot-desks for a team of 60 to 80 engineers. Office lease costs are meaningful but not punishing — $15 to $30 per square meter monthly is typical.

HR and payroll

Either built in-house with a hired HR manager (and a chief accountant, which is required by law) or outsourced to a local payroll provider. The hybrid is most common — local payroll provider handles compliance and processing, in-house senior HR business partner handles people management. Pure outsourcing works at a smaller scale; once the team is past 40 engineers, an internal HR presence becomes valuable.

Compliance and accounting

Labor code compliance, tax filings, and HTP reporting. A chief accountant is mandatory for the entity by Belarusian law — the role can be filled in-house or, more commonly at a smaller scale, outsourced to a local accounting firm with the in-house team handling oversight.

Equipment procurement and lifecycle

Most ODCs handle this in-house once they hit 30+ engineers. Below that, working with a local IT supplier on a managed basis is simpler. Equipment ownership becomes part of the entity’s balance sheet, with tax and operational implications, but is generally cleaner than the EOR-owned equipment alternative.

Ongoing recruitment

Some ODCs build internal recruiting teams once they reach 50+ engineers. Most continue to retain a relationship with a local recruitment agency for ongoing search work, particularly for senior and specialised roles. Internal recruiters in Belarusian IT cost $2,500 to $4,500 monthly gross at the senior level — affordable, but the case for in-house recruitment is about ongoing volume rather than cost. External IT recruitment typically runs at the standard percentage of annual gross at hire, with terms that favour predictable volume.

Tax and financial mechanics — what the savings actually look like

The numbers behind the conversion decision. Comparing an HTP-resident ODC running the same team that previously ran through an EOR.

The headline tax differences for an HTP-resident entity versus a non-HTP entity (the EOR is HTP-resident for most foreign clients, so the relevant comparison is HTP-ODC versus HTP-EOR):

• Personal income tax: 9% (HTP resident) — same in both ODC and EOR cases when the EOR is HTP-resident.
• Social fund: calculated on the average national salary base — same in both cases.
• VAT on IT exports: 0% for both.
• Corporate profit tax: 9% — applies to both, calculated on the entity’s profits.
• EOR margin: 8–15% of total monthly payroll for an established relationship. This is the line that disappears when you move from EOR to ODC.

The structural saving in the ODC model is the EOR margin. Everything else is broadly comparable when both sides are HTP-resident.

Worked example

A 25-engineer team at $5,000 average gross monthly. Total gross payroll roughly $125,000 monthly.

EOR-routed total cost (gross payroll, employer-side contributions, benefits, EOR margin): approximately $175,000 to $190,000 monthly. The exact figure depends on the benefits richness and EOR margin tier.

HTP-resident ODC running the same team (same gross, same employer-side contributions, same benefits, no EOR margin, plus the entity’s own running costs — office, accounting, HR, equipment): approximately $145,000 to $160,000 monthly.

Monthly difference: roughly $20,000 to $30,000. Annually: $240,000 to $360,000.

Setup costs that offset this in year one: roughly $30,000 to $50,000 in entity setup, banking onboarding, HTP residency application, legal fees, office lease deposits, equipment purchases, and the time cost of the founder’s attention. Crossover from net cost to net saving typically occurs 12 to 18 months from setup, sometimes faster for larger teams.

Below 15 engineers, the math doesn’t work — EOR is cheaper end-to-end. Above 40 engineers, ODC is significantly cheaper. Between 20 and 40 engineers is the zone where the decision turns on factors beyond pure cost — operational control, employer brand, the strategic importance of the Belarus operation to the foreign parent.

Where the timeline blows up — the honest section

Where setup projects go wrong: observations across multiple conversions in 2024–2026.

Banking is the single biggest delay vector

Foreign-owned entities can face KYC processes that take four to eight weeks at the slow end. Some banks have efficient foreign-IT-client workflows; others do not. The practical lesson is to start the banking conversation in the first week of the setup, identify two or three candidate banks, and run the relationship-building in parallel with the entity registration. Treating banking as an afterthought is the single most reliable way to push the timeline from four months to seven.

Founder document apostille and legalization

Foreign founders consistently underestimate how long it takes to gather their home-jurisdiction documents. Notarised and apostilled copies of foundation documents, passport copies, proof of address, sometimes corporate good-standing certificates — all need to be obtained in the home jurisdiction, then apostilled, then translated into Russian (sworn translation by a recognized translator), and only then submitted in Belarus. Build in four weeks for this. It takes six.

HTP residency review questions

The HTP administration occasionally comes back with clarification questions on the business plan, particularly around activity classification or projected revenue. These questions aren’t a sign of trouble — they’re routine for non-standard cases. Build in two weeks of contingency for an exchange of clarifications.

Currency control on the first inbound payment

The entity’s first cross-border inbound payment from the foreign parent — typically the initial capitalisation or the first invoice — sometimes gets held by the bank for compliance review. Anticipated, not surprising, but it’s a process step that runs a few days to two weeks. Plan for it; don’t be caught with payroll due and incoming capital still under review.

Existing EOR cooperation

Some EORs cooperate fully and helpfully with conversions; others extract additional margin during the transition window. Read the existing EOR contract, specifically the termination, notice period, and transition cooperation clauses, before you start the conversion. Plan accordingly.

Engineer communication

The gap between “we’re moving you to a new entity” and “actually, nothing meaningful changes for you” is the gap where avoidable attrition happens. Brief engineers early, individually where possible. Pay particular attention to the senior contributors whose departures during a conversion would pose the greatest delivery risk. Some of them will be the most anxious about the change, precisely because they have the most to lose if things go wrong.

The bottom line

Setting up an ODC in Belarus is a project, not a decision made once and executed. Done well, it converts a 20-to-40-person Belarusian team from an EOR cost stack to a structurally cheaper, more controlled setup, with savings that compound year over year and a permanent base for future scaling. Done poorly, it produces a four-month project that becomes a seven-month project, an engineer cohort that loses confidence in the transition, and an IP chain that has to be cleaned up months after the fact.

The single most useful preparation is the question we opened with: Do you actually need an ODC right now, or are you 12 months early? If the answer is “early,” stay on the EOR model and revisit. If the answer is “now,” plan for the four-month case, build in contingency for six, and start the banking conversation before you start the entity registration.

At Recruitment.by we work with foreign clients on both sides of this decision — the EOR-based teams growing toward the conversion question, and the established ODCs running ongoing hiring. On the structural side of HTP residency, our HTP residency support and joining HTP services cover the application process and operational onboarding. For the broader organizational and compensation design that goes with scaling an ODC, our HR consulting handles the strategic side. Ongoing IT recruitment into the new entity, and supporting payroll and PEO services during transition, run alongside. For a conversation about your specific case — whether you’re at or beyond the threshold, or just wanting to model the trajectory — contact us.