R&D Tax Incentive in Serbia: Between Innovation, Tax Efficiency, and Proper Project Structuring

Although it is often primarily associated with the IT sector in practice, experience shows that its potential goes far beyond traditional technology companies and can be relevant across various industries, from logistics and manufacturing to pharmaceuticals and the development of internal business systems. 

The incentive was introduced through amendments to the Corporate Income Tax Law (hereinafter: Law) at the end of 2018 and has been applicable starting from tax periods beginning in 2019. Its main advantage lies in the ability to recognize costs directly related to research and development activities at double their amount in the tax balance sheet, significantly reducing the corporate income tax base. 

However, although the concept appears relatively straightforward, practice shows that, in addition to innovation as a statutory requirement, the key factors for successfully claiming the incentive are the proper structuring of the project and its adequate documentation from the perspective of tax regulations and the practice of the Ministry of Finance, particularly in the context of a potential tax audit. 

What Qualifies as R&D and Why Practice Often Matters More than the Project Label 

In accordance with Article 22g of the Corporate Income Tax Law, taxpayers are entitled to recognize expenses directly related to R&D activities at double their amount in the tax balance, provided that such activities are carried out within the territory of the Republic of Serbia. 

The Law defines research as original or planned investigation undertaken to acquire new scientific or technical knowledge and understanding, while development is defined as the application of research results or other scientific findings for the development of new or significantly improved products, processes, systems, or services before their commercial production or use. 

In practice, the interpretation of this definition is one of the most important issues. It is not sufficient for a project to be “modern,” digital, or technologically advanced. What is essential is the presence of technical uncertainty, the resolution of specific development or process challenges, and a clearly defined development process through which the company arrives at a new or improved solution. 

For this reason, qualifying projects in practice often include the development of software platforms, process optimization algorithms, laboratory development projects, improvements to production systems, or the development of specific internal tools and functionalities—provided that such activities genuinely involve the creation of new or enhanced functionalities and the resolution of concrete technical issues. 

Importantly, eligibility for the incentive does not depend on whether the project ultimately results in a successful final product. The Ministry of Finance has repeatedly taken the position that costs may still be recognized even if the project does not lead to a market-ready product, as long as the activities themselves qualify as R&D. In practice, this is particularly relevant for projects that go through multiple iterations of development, testing, and adjustment before reaching a final solution. 

For this reason, an increasing number of companies are opting to perform a preliminary analysis at an early stage of project development to assess whether their activities have the potential to qualify as R&D. In practice, it often turns out that companies already carry out qualifying activities but fail to recognize them as a basis for utilizing the incentive. 

Conditions for Applying the Incentive and Typical Qualifying Costs 

For a project to be considered carried out in Serbia, at least 90% of all employees engaged in R&D activities must perform their work within the territory of the Republic of Serbia. Additionally, the taxpayer must possess documented project descriptions with clearly defined objectives, planned phases, and project activities. 

The relevant Rulebook further specifies the types of costs considered directly related to R&D activities. In practice, these most commonly include employee salaries, costs of materials and equipment directly used in R&D, software and licensing costs, costs of external professional services and know-how (excluding services obtained from related parties), intellectual property protection costs, as well as certain financing and production service expenses directly linked to the project. 

A proper understanding of the treatment of equipment and external services is particularly important. For example, equipment qualifies as an R&D cost only to the extent that it is used for development, testing, and validation within the project, whereas equipment used in regular business operations after the development phase is generally not considered a qualifying cost. 

Similarly, companies often face questions regarding the engagement of external contractors, consulting teams, and software partners. In many projects we have encountered, the way the project is documented has proven to be decisive in potential tax audits. 

Documentation as the Core of the Tax Position 

One of the most important practical aspects of the R&D incentive is documentation—this is also where most issues arise during tax audits. 

For each project, it is necessary to prepare documentation often structured as a comprehensive R&D study, which, in addition to a formal project description, demonstrates the entire development logic: the problem being solved, the reasons for technical uncertainty, the organization of activities, the participants involved, and the costs directly associated with development activities. 

Along with the tax return, taxpayers submit documentation including the project description, planned phases and activities, time tracking of employees, and detailed cost breakdowns. Companies must also retain supporting documentation evidencing project implementation and incurred costs, including budgets, procurement plans, third-party agreements, invoices, internal records, technical documentation, and other relevant documents. 

Our experience shows that effective R&D documentation should not be overloaded with technical jargon, but must clearly demonstrate the development process and the direct link between activities and costs. In practice, the main issue is often not a lack of innovation, but the way the project is documented and presented. 

For this reason, documentation is no longer merely a compliance requirement—it represents a key element of a broader tax strategy. Well-prepared documentation supports not only tax reporting, but also the long-term sustainability of a company’s tax position and significantly reduces risk in the event of a tax audit. 

The Most Sensitive Issue in Practice: Own-Account vs Contract R&D 

One of the questions that regularly arises in practice is the distinction between R&D carried out for a company’s own account and contract R&D performed for another party. 

According to the current positions of the Ministry of Finance, the right to apply the incentive exists when the taxpayer performs R&D for its own benefit and retains the results and benefits of the project. Conversely, when a company performs development activities as a service for other legal entities, including related parties, the incentive, as a rule, is not available. 

This issue is particularly relevant for IT companies, outsourcing models, and shared service centers. In such structures, it is essential to properly assess who is the actual owner of the project, who bears the development risk, who owns the results, and whether the company acts as the principal developer or merely as a service provider. 

At the same time, practice shows that certain structures may still be sustainable if they are properly designed and documented, although this typically requires additional analysis and clear evidence that the R&D is performed for the company’s own account. For example, the Ministry of Finance has taken the position in one of its opinions that software developed and owned by a company, and subsequently licensed for use, may qualify as R&D activity, even in cases where such software is used in specific industries (such as extractive industries), where exploration-related costs are otherwise explicitly excluded from the incentive. 

For this reason, the analysis should not be limited to the name of the project or the company’s industry, but should instead focus on the actual substance of the activities, the project structure, and the way the overall model is set up. 

Request for an Opinion from the Ministry of Finance as an Element of Tax Certainty 

Although submitting a request for an official opinion from the Ministry of Finance is not a legal requirement, in practice it is often considered one of the most important steps in the process of implementing the R&D incentive. 

In projects involving complex structures, related parties, a combination of different incentives, or significant amounts of costs, a properly prepared request can be highly important—both before entering the documentation phase and later in the event of a tax audit. 

Our experience shows that the way in which a project is presented to the Ministry of Finance often has a decisive impact on how the nature of the activities and the related tax treatment are understood. For this reason, the preparation of such requests has increasingly moved beyond a purely formal exercise and has become part of a broader strategy for establishing a sustainable tax position. 

As part of our work, we have been involved both in the preparation of R&D studies and full project documentation, as well as in drafting requests for opinions to the Ministry of Finance. 

Interaction with Other Tax Incentives and Practical Issues in Combining Incentives 

One of the topics that is increasingly encountered in practice is the possibility of combining the R&D incentive with other tax benefits. 

Based on our current understanding of the regulations and established practice, there are no obstacles to using the R&D incentive in parallel with certain other corporate income tax incentives, including incentives for investments in fixed assets, provided that the conditions for each incentive are met. 

On the other hand, when it comes to personal income tax and social security contributions, the rules are more restrictive. The incentive for salaries of employees engaged in R&D cannot be used simultaneously with other employment-related incentives for the same individuals, except for the corresponding contribution incentive. 

For this reason, in larger development teams and more complex structures, it is often necessary to analyze in advance which model produces the most favorable overall tax outcome and how to properly allocate employees and activities across different incentive regimes. 

R&D Incentive as Part of a Long-Term Tax and Business Strategy 

Although the R&D incentive is often viewed as a standalone tax measure, practice shows that it is increasingly becoming part of a broader tax efficiency and business development strategy. 

Companies that continuously invest in the development of products, processes, digital solutions, and technological improvements are increasingly using this incentive not only as a source of immediate tax benefit, but also as a tool for optimizing development costs and improving the sustainability of innovation investments in the long term. 

At the same time, experience shows that the greatest value lies not merely in formally applying the incentive, but in properly structuring the project from the outset—from the design of activities and contractual arrangements, through record-keeping and documentation, to communication with the Ministry of Finance and the establishment of a sustainable tax position. This is where the difference becomes most apparent between projects that successfully utilize the incentive and those where it remains an untapped opportunity. 

For this reason, preliminary project analysis is increasingly proving to be a valuable tool for assessing the potential to apply the R&D incentive, identifying key tax risks, and helping companies structure their development activities in a way that is sustainable both from a business and a tax perspective.