Every tax advisor in Serbia knows the drill: a multinational group sets up a local entity, registers it for data center services, and expects a simple "cost plus 5%" pricing model.

But what happens when that company actually holds €2 million in server infrastructure and only a handful of employees? Before diving into the numbers, it is essential to understand the basics of Related Party Rules in Serbia: When Do Transfer Pricing Obligations Apply?, as every transaction within a group triggers these complex requirements.

Recently, I worked with a client - a regional data center provider - whose situation perfectly illustrates why a "one-size-fits-all" approach to transfer pricing can be a ticking time bomb for your Serbian tax balance.

The background: High assets, low headcount

‍The client operates a sophisticated data center. In reality, their balance sheet is dominated by Group V assets (IT infrastructure) with a Serbian tax depreciation rate of 30%.

The dilemma was clear:

1. The group wanted a simple, consistent model for their global "limited risk" entities.
2. The Serbian entity was facing a massive mismatch between its massive investment and its operational routine.
3. Global OECD standards had to be met, but local Serbian specificities - especially the "lower of two" depreciation rule - were complicating the math. For a broader look at the current regulatory landscape, check out my Transfer Pricing in Serbia: 2026 Compliance Guide.

The options on the table

‍When dealing with asset-heavy IT entities, a standard markup on operational costs (OPEX) often fails to reflect economic reality. I analyzed several paths:

• The traditional TNMM (Net cost plus): A simple markup on total costs. While easy to implement, it rarely rewards the Serbian entity for the millions of euros "locked" in hardware.
• The capital charge model (ROCE): This model treats the infrastructure as a separate value driver. It asks: "What would an independent investor demand as a return on this specific capital?" It is the "gold standard" for data centers, but it requires a very precise benchmark of the return on capital employed (ROCE).

The "nightmare" scenarios: Real-world risks

If you pick the wrong pricing model, you could end up in a "tax nightmare" where you are economically profitable but carry artificial tax losses - or worse, trigger an audit. Here is how it happens:

Scenario 1: The "profit mirage" (Audit trigger)

The setup: A data center with €2 million in hardware assets operates on a simple "5% markup on salaries" model. With only two employees, the annual taxable profit is set at a symbolic €5,000.

‍The nightmare: During an audit, the inspector points out that no independent investor would deploy €2 million for a 0.25% annual return. The Tax Administration applies a 10% ROCE benchmark, imputing a profit of €200,000.

‍The damage: The company pays 15% tax on the €195,000 difference, plus interest and penalties - money never even invoiced to the parent.

Scenario 2: The "vanishing loss" (The 5-year trap)

The setup: Due to massive initial investments, the Serbian entity generates €500,000 in tax losses. The advisor sets a conservative pricing model that brings in only €20,000 in annual profit.

‍The nightmare: Serbian law limits the carry-forward of tax losses to 5 years. By year 6, the company has only "neutralized" €100,000 of its losses.

‍The damage: €400,000 in tax shields permanently expire. Starting in year 6, the company pays full tax, despite never having recovered its initial investment.

Scenario 3: The "lower of two" cash trap

The setup: The company invoices based on a 30% tax depreciation rate (Group V) to maximize cash flow. However, for accounting, they depreciate over 10 years (10%).

‍The nightmare: According to the Serbian Rulebook (93/2019), for tax purposes, you can only recognize the lower of the two amounts. This creates an artificial tax profit on paper.

‍The damage: The company is forced to pay 15% corporate tax in cash today, even though the equipment is losing value much faster in reality.

What is your real TP profile?

In the end, I found the "sweet spot" - a model that ensured the Serbian entity stayed profitable, satisfied the Serbian Tax Authorities, and kept the group's global auditors happy.

But here is the catch: the right model for a standard service provider is a disaster for a data center.

Are you sure your intercompany markup reflects the assets you actually hold?

Are you maximizing your tax shield, or are you leaving "dead" losses on your balance sheet?

The details matter.

If you are operating an asset-heavy tech business in Serbia, let me determine your actual TP profile and build a pricing model that is consistent, compliant, and optimized for the long haul.