Humanfrog Lab

Offices in the Balkans: what must our IT cover in each country, and how should we organise support?

Opening a site in Zagreb, Belgrade or Sarajevo is quick. Getting its IT right takes longer: users need accounts and devices on day one, the network has to connect securely to HQ, and every country has its own rules on e-invoicing, fiscalisation, cybersecurity and personal data. Four of the six countries are outside the EU, which matters for data access as well.

This page is for companies headquartered in Austria, Germany, Italy, elsewhere in the EU or the US, and for Slovenian and Croatian groups expanding south. The tool builds a checklist for each country you select, recommends a support model and lists what a new site needs before it opens. The guide below explains how to split work between HQ and the region.

What must our IT cover in each Balkan country?

Updated 7 min read

What must our IT cover in each Balkan country?

Select your countries, describe what HQ already runs and where your data live. The result is a printable checklist per country, a support model with reasons, a rollout list for a new site and the risks to address. Country information as of November 2026.

Select the countries where you have or are opening sites, then describe what HQ already provides. The result shows a checklist for each country, a recommended support model, a rollout checklist for a new site and the main risks. It takes about three minutes.

Countries with sites

Other countries in the region on request; the checklist covers these six.

Sites and users per country

Approximate numbers are fine. Count every office, warehouse or shop as a site.

What does HQ provide centrally?

Select everything the group already runs for all companies.

Where do data and servers live?

Several answers are possible.

What needs to be done on site?

Work that needs a person physically present.

Expected support hours
Language for HQ, reporting and escalation

Users at the sites are supported in the local language either way.

Is the group in a regulated sector (NIS2, DORA, health, energy)?

Or a supplier to such companies that has to meet their security requirements.

Select at least one country to see the result.

IT for subsidiaries in the Balkans: checklist (Humanfrog Lab)

Recommended support model

Why this model

Who does what:

Country checklist

Status as of November 2026, verified on official sources where possible. Rules change, so confirm details with the authority or a local adviser.

Rollout checklist for a new site

Use it for every new office, warehouse or shop. Items that do not apply to your answers are left out.

Humanfrog manages the IT environment of Alfa SP, with companies in Slovenia, Croatia and Serbia. We also look after IT for a company with sites in every country of the region: Fortinet equipment at each site, connected via SD-WAN to a central point that we maintain.

The result is a planning aid, not legal or tax advice. Country information is as of November 2026; confirm current rules with the authorities, your tax adviser or a local lawyer.

Send yourself the result and talk to an expert ↓

The calculation runs in your browser. Your answers are only sent if you submit the contact form below.

Central or local: who does what

Companies with sites across the Balkans usually end up with one of three set-ups: HQ IT runs everything and buys on-site help when needed, each subsidiary hires its own local IT company, or one regional partner covers all countries. Whichever you choose, the split of responsibilities matters more than the org chart. A simple rule works well: HQ owns standards, licences and data; the region delivers the service consistently on site.

AreaUsually central (HQ)Usually local or regional
Identity and emailEntra ID, Microsoft 365 tenant, licences, MFA policyAccount requests, onboarding, first-level help in the local language
DevicesStandard models, Intune policies, security toolsDelivery, set-up, replacement, warranty cases
NetworkFirewall standard, VPN or SD-WAN design, central pointLines, cabling, Wi-Fi, firewall installation, on-site fault finding
ApplicationsERP, CRM, file shares, data locationLocal integrations (e-invoicing, fiscal devices), printers and scanners
SecurityBaseline, monitoring, incident processApplying the baseline, local incident contacts, awareness training

Use the tool on this page to see which model fits your countries, users and on-site needs.

Identity, devices and the network between sites

Give every new site the same foundation as HQ from day one. Users get accounts in the central directory with MFA; laptops are enrolled in device management before they are handed over, with the local keyboard layout and language. That way a new office in Belgrade or Skopje is just another group of devices and users, not a separate IT island.

For connectivity, standardise the firewall at each site and connect it to HQ or a central point over site-to-site VPN or SD-WAN, with a backup line from a second provider or a mobile network. Keep a documented IP plan from the start; overlapping address ranges are one of the most common reasons why connecting a new site takes weeks instead of days.

From our practice: one company we support has sites in every country of the region. Each site has Fortinet equipment connected via SD-WAN to a central point that Humanfrog maintains, and we look after IT for the whole company, including the secure connections between sites. The same firewall standard everywhere means the security rules, monitoring and troubleshooting are the same in every country.

Security baseline and the NIS2 supply-chain view

Define one security baseline for the whole group: endpoint protection, patching, email protection, backups, logging to central monitoring and an incident process with contacts per country. Write it down once and apply it at every site, whoever does the work locally.

NIS2 applies through national laws in EU member states: ZInfV-1 in Slovenia and the Cybersecurity Act in Croatia, alongside the laws in your home country. Serbia and North Macedonia have adopted their own NIS2-aligned laws, Montenegro has an information security law, and in Bosnia and Herzegovina you should check the current status. If your group is in scope, NIS2 also requires you to manage the security of your IT suppliers. Every local IT company is a supplier you have to assess, contract and audit. Fewer suppliers mean fewer assessments. See our NIS2 guide to check whether you are in scope.

Data location and transfers out of the EU

Slovenia and Croatia are in the EU, so personal data move freely between them and your EU headquarters. Serbia, Bosnia and Herzegovina, Montenegro and North Macedonia are outside the EU, and as of November 2026 none of them is on the European Commission's list of adequacy decisions. In practice this means that when staff or an IT supplier in those countries access personal data held in the EU, for example your Microsoft 365 tenant or ERP, it counts as a transfer under the GDPR. The usual safeguard is standard contractual clauses, together with a transfer impact assessment. Each of the four countries also has its own data protection law and authority, which regulate transfers out of the country.

Keep data in an EU cloud region or at HQ where possible, avoid unmanaged local servers, and document who has admin access from where.

Local invoicing and fiscalisation that touch IT

Invoicing rules are often where a "simple" new site turns into an IT project, because the ERP, certificates and fiscal devices must fit each country.

CountryWhat IT has to support (as of November 2026)
SloveniaFiscal verification of cash invoices (cards included) with FURS; B2B e-invoices only from 1 January 2028
CroatiaFiscalisation 2.0 since 1 January 2026: eRačun between VAT taxpayers through an information intermediary
SerbiaB2B invoices through the state SEF system since 2023; e-fiscalisation of retail since May 2022
MontenegroOnline fiscalisation of invoices since 2021; B2B e-invoicing in preparation
North MacedoniaFiscal cash registers; national e-invoicing (e-Faktura) being introduced
Bosnia and HerzegovinaRules per entity; new fiscalisation law in the Federation of BiH (2026)

For each country, agree who owns the regime (finance, the ERP partner or IT), test the connector end to end, track certificate expiry dates and open the right firewall endpoints. More detail: Slovenia e-invoicing 2028 and Croatia fiscalization 2.0.

Language, support hours and documentation

Users should get help in Slovenian, Croatian, Serbian, Bosnian, Montenegrin or Macedonian; HQ needs reports and escalations in its own language. Agree both in the SLA, along with support hours. All six countries are in the same time zone as Vienna, Munich and Milan, which makes business-hours support simple; 24/7 needs a team in shifts, not one local technician.

Documentation is the part most often skipped. For every site you need a network diagram, an asset list, licences, contacts and passwords in a vault the company owns, plus runbooks for local technicians. Without it, every handover between suppliers becomes a small crisis.

Choosing a regional partner and typical mistakes

  • Local presence: ask who will actually be on site in each country, and how quickly.
  • One standard: the same tools, baseline and reporting in every country.
  • Microsoft 365, Azure and network skills as well as user support.
  • Security and contracts: NIS2 and DORA clauses, access control, incident reporting and audit rights.
  • Exit terms: documentation and admin access stay with you.

Typical mistakes

  • Opening the site first and sorting out IT afterwards, with personal email accounts in the meantime.
  • A local server "just for now" that nobody patches or backs up.
  • Ignoring data transfers when non-EU staff get access to EU systems.
  • Leaving e-invoicing and fiscal devices to the accountant until invoicing stops.

Example scenario

A hypothetical example, not a client. An Austrian manufacturer opens sales offices in Zagreb, Belgrade and Sarajevo with about 40 users. HQ already runs Microsoft 365, Intune and SAP. The best fit is one regional partner: HQ keeps identity and applications, the partner handles on-site set-up, the group's standard firewall with VPN to Vienna, local-language support and German-language reporting. Separate attention goes to the SEF connector in Serbia, eRačun in Croatia, standard contractual clauses for the Serbian and Bosnian staff, and the entity-level rules in Bosnia and Herzegovina.

References

Humanfrog manages the IT environment of Alfa SP, a logistics company with operations in Slovenia, Croatia and Serbia. For five years we have supported its 40 active users at six locations in three countries: we migrated email and documents to Microsoft 365, set up access management, automated backups and centralised monitoring, and moved the servers to the cloud (also described in Forbes Slovenija, in Slovenian).

We also look after IT for a company with sites in every country of the region, with Fortinet equipment at each site connected via SD-WAN to a central point we maintain.

For information only, as of November 2026. Country rules change; confirm them with the authorities linked in the tool or with a local adviser. This text is not legal or tax advice.

To compare the cost of running IT in-house or with a partner, see managed IT services cost. If you would like us to review your set-up in the region, talk to us.

Frequently asked questions

Do we need a separate IT partner in each Balkan country?
Not necessarily. One regional partner with its own engineers and local technicians can cover several countries under one contract and one SLA. What matters is that it can be on site quickly, supports users in their language and knows the local rules on invoicing and data.
Which countries in the region are in the EU, and why does it matter for IT?
Slovenia and Croatia are EU member states. Serbia, Bosnia and Herzegovina, Montenegro and North Macedonia are not, and as of November 2026 none of them has an EU adequacy decision. When staff or IT suppliers there access personal data held in the EU, for example in Microsoft 365, GDPR transfer rules apply, usually through standard contractual clauses.
Does NIS2 apply to our subsidiaries outside the EU?
NIS2 applies through national laws in EU member states, such as ZInfV-1 in Slovenia and the Cybersecurity Act in Croatia. Serbia and North Macedonia have adopted their own NIS2-aligned laws and Montenegro has an information security law. If your group is in scope in the EU, its supply-chain and risk duties also reach systems and suppliers in the rest of the region.
What do e-invoicing and fiscalisation mean for IT?
They are integration projects: the ERP or invoicing software must connect to the national system or a provider, use valid certificates and, for retail, certified fiscal devices or software. Croatia introduced Fiscalisation 2.0 on 1 January 2026, Serbia has used the SEF system for B2B invoices since 2023, and Slovenia makes B2B e-invoices mandatory from 1 January 2028.
Can our HQ IT team run the subsidiaries remotely?
Much of it, yes: identity, Microsoft 365, device management and security can be run centrally. Hardware, network work, onboarding, printers and POS still need people on site. Agree runbooks, response times and documentation duties with whoever provides those local hands.
What should a contract with a regional IT partner include?
Response times per country and priority, support languages and hours, security obligations (relevant under NIS2 and DORA), reporting to HQ, ownership of documentation and passwords, and clear exit terms. Ask how the partner covers each country: own staff, subcontractors or both.

Stay up to date

Regulations, licence prices and technology change fast. When we update the guides and tools in the Lab or publish a new article, we let you know by e-mail. Occasional, and never spam.

Subscribe to the newsletter