Databases, data and software under the Cyprus IP Box

Separate three layers of a data business

A data-driven service may combine a collection of information, a structure for organising it and software for searching, analysing or presenting results. Those layers can have different owners and different legal protection. A single product name does not make them one kind of IP.

EU database law distinguishes copyright in an original selection or arrangement from the separate protection associated with substantial investment in obtaining, verifying or presenting contents. Rights in the underlying materials remain a separate matter. The software used to make or operate a database is also distinct.

The Cyprus IP Box regulations identify qualifying categories, including software, and exclude marketing IP. The existence of some form of intellectual-property protection is therefore not a complete eligibility test. Establish the category relied upon rather than calling every protected digital asset copyrighted software.

An asset map for a data product

This practical map helps organise the review. It does not declare any item automatically eligible or ineligible under every possible set of facts.

Data access and software functionality may earn different income

A customer may primarily pay for access to a dataset, for analytical functionality or for a combined service. The invoice description “platform subscription” does not settle that distinction. Review the product’s actual value proposition and the contractual rights supplied.

If qualifying software contributes to a wider product or service, embedded-income analysis may be relevant under the regulations. That is a reason to examine attribution, not permission to place all data revenue in the IP Box calculation. A supported allocation may be necessary.

Consider a service licensing a third-party dataset through an original analysis application. The company should identify rights in the dataset, rights in its software, relevant costs and how income is attributable to the offering. The fact that software is needed to access data does not itself prove that all profit comes from qualifying software.

Keep data costs separate from development assumptions

Buying data, cleaning records and developing a software capability can involve different activities. Do not automatically treat every data-related invoice or analyst salary as qualifying R&D expenditure. Identify the work and its direct relationship with the relevant qualifying asset.

A data licence may be an operating input to the product without being acquisition of the company’s own software asset. Conversely, a transaction might include both software rights and data rights. Review what was purchased and allocate amounts where the facts require it.

Maintain the distinction between expenditure affecting annual net income and expenditure entering the nexus fraction. A cost’s commercial importance does not determine its nexus category. Support classifications with the actual contracts, work records and asset map.

A documentation checklist for founders and finance teams

Start the file before drafting a tax-rate claim. The most useful outcome is a clear explanation of which asset the company relies on, what rights it has and how that asset earns income.

• Identify data, database structure and software separately.
• Record ownership, licences and relevant restrictions.
• Explain the qualifying IP category relied upon.
• Describe the development activities and costs for that asset.
• Reconcile customer income and shared costs.
• Document any embedded-income allocation.
• Resolve uncertain rights or tax classifications explicitly.

Avoid two opposite shortcuts

The first shortcut is to assume that every database qualifies because it has copyright or another protected right. The second is to assume that a company using a database cannot have qualifying software. Both miss the need to identify the actual asset.

A defensible assessment can recognise original software within a data business while treating other rights and income separately. Where a business relies on a category other than software, examine that category’s specific conditions, including any applicable certification and thresholds, rather than borrowing the software conclusion.