Czech R&D tax deductions explained

For a technology company in Prague the R&D deduction is one of the few tax features that can change the economics of a project. It is also one a finance director approaches with caution, because the tax authorities treat it as an area where the paperwork has to match the claim. The logic of the deduction matters more than the rate.

This explainer describes the mechanism in general terms. It is not tax advice. The rates and conditions have been amended repeatedly, so prepare any claim with a tax adviser who knows the current law.

The basic idea

The Income Tax Act (Act no. 586/1992 Coll.) allows a taxpayer to deduct from its tax base a specified part of the costs spent on research and development, on top of deducting the costs themselves as normal expenses. Qualifying spending therefore reduces taxable profit by more than the amount spent. How much more depends on the percentage set in the Act, which has changed more than once; check the Financial Administration for the current figure.

The deduction is mainly a feature of corporate income tax, discussed in Czech corporate income tax explained, though individuals who carry on a business can in principle use it. It reduces the tax base. It does not produce a refund where there is no profit, but the Act allows unused amounts to be carried forward for a limited period (check the current rules).

What counts as R&D

The Act refers to research and development projects as defined in the Act on the Support of Research, Experimental Development and Innovation (no. 130/2002 Coll.), which follows EU state-aid concepts and the OECD Frascati approach. In broad terms:

• Basic research is experimental or theoretical work to gain new knowledge, without a direct practical application.
• Industrial research is planned research to gain new knowledge for developing products, processes or services.
• Experimental development is using existing knowledge to create new or improved products, processes or services, including prototypes and pilots.

Routine work does not qualify. Quality control, minor adjustments to existing products, market research and ordinary software maintenance are not R&D just because engineers do them. The test is whether the project tries to resolve a scientific or technological uncertainty.

Which costs may count

The Act specifies the eligible categories. They generally include the staff costs of people working on the project, materials and consumables, certain services bought from research organisations and depreciation of equipment used for the project, depending on the exact wording. General overheads are treated more narrowly. Whether a particular cost qualifies depends on the Act and the tax authority's interpretation, so review a list drawn up for one project against the current text.

Subsidies matter. Costs covered by a grant or other public support may be excluded from the deduction or reduced, to avoid a double benefit. Companies receiving money from the Technology Agency or EU programmes (see Czech start-up ecosystem and EU funds for Czech businesses) should check how the two interact.

Documentation

The central requirement is to be able to demonstrate the project. The taxpayer must keep project documentation setting out the objectives, the work done, the expected results, the time frame, the responsible persons and the costs. The Act expects a project to be described before and during the work, not reconstructed afterwards. Staff timesheets, invoices for external services and technical records such as reports and test results form the evidence.

The deduction is claimed in the corporate income tax return, with any attachment or notification the form instructions require (check the current forms). The tax office can examine the claim, and when it does it will look at the project file and the allocation of costs. For how the filing works, see Czech corporate income tax explained.

Seeking certainty

A taxpayer who wants certainty can seek an assessment before claiming. The rules allow the provider of public R&D support, or the competent authority, to assess whether a project meets the definition of R&D, and the tax office takes that assessment into account (check the Financial Administration for the current procedure). It does not remove every risk, since costs and documentation still matter, but it narrows the argument about the nature of the project.

Common pitfalls

Treating all software development as R&D. Claiming the costs of staff who spent little time on the project. Failing to keep time records. Claiming costs already funded by a grant. Starting the paperwork after the year has ended. A clear internal rule, such as a project code for every R&D task, makes each of these easier to avoid.

Group structures raise further questions. If a Czech company does work for a foreign parent, who bears the risk and who owns the results affects whether the costs are the Czech entity's own. That belongs with a transfer-pricing and tax adviser, as does the interplay with dividends and distributions.

What to do first

If you think a project may qualify, write a one-page description of the uncertainty it addresses and how you will test it, before you start. Open a separate cost code. Then ask a tax adviser to read the current Income Tax Act with you. The paper you produce for them is the start of the file the tax office would later ask for.

This is a general explainer, not legal or tax advice.