Cyprus IP Box nexus: expenditure and evidence for software

What does the nexus approach do?

The Ministry of Finance describes an 80% deduction linked to qualifying intangible-asset profit calculated under the nexus approach. The calculation is asset- and evidence-dependent; it is not a blanket deduction from all gaming revenue.

First separate qualifying IP income from other income and determine the relevant net amount. A player-facing operator’s gross receipts should not simply be relabelled as software royalties. Embedded income and allocation questions require a supported analysis.

Which expenditure categories matter?

The government-hosted IP guide distinguishes qualifying R&D expenditure from acquisition costs and related-party outsourcing in the overall expenditure calculation. It also describes a limited uplift. That guide contains historical tax-rate figures, so it should be used for the described mechanics, not as a current rate source.

Classify costs consistently by asset and activity. Preserve the distinction between development performed by the taxpayer, unrelated-party work, related-party work and acquisition expenditure. A single ledger account labelled “software costs” may not provide enough detail.

What does a simplified calculation illustrate?

Assume, solely for illustration, that the properly determined nexus fraction is 60% and the relevant net IP income is 100,000 units. Qualifying profit would be 60,000 units, and an 80% deduction on that amount would be 48,000 units. The example does not establish eligibility or the final tax liability.

This demonstrates why a reduced nexus fraction changes the result. The actual calculation requires correct cost classification, permitted uplift treatment, income allocation and applicable tax rules. Do not advertise the maximum effective benefit as guaranteed for every software business.

What evidence should a development team preserve?

Build records during development rather than reconstructing them only when preparing a tax return.

• An identifiable asset and version or project structure.
• Developer roles, work records and relevant agreements.
• Invoices and cost allocations linked to the development activity.
• Related-party status of outsourced work.
• Ownership and rights supporting exploitation of the software.
• The income calculation and assumptions used for allocation.

What changes require reassessment?

Acquiring software, outsourcing more work to a group company or changing the revenue model can alter the analysis. Review those changes before assuming that an earlier calculation remains valid.

Keep the nexus work coordinated with transfer pricing and IP ownership. A contract assigning rights does not by itself establish qualifying expenditure, and a qualifying cost does not by itself establish the amount of qualifying income. Each part needs its own evidence.