The Cyprus IP Box for software, SaaS & AI companies

Your nexus ratio as a software company

Your nexus ratio measures how much of the qualifying profit you can actually shelter, and for most owner-built software companies it lands at or near 100%. The nexus fraction, required by the OECD modified nexus approach, compares your own qualifying research and development spend against total spend on the asset. The more of the development you did yourself, the larger the share of profit that benefits from the IP Box.

In-house development by your own Cyprus team is fully qualifying expenditure, which is why a company that wrote its own code typically reaches a ratio close to 100%. Costs paid to unrelated third-party contractors also count as qualifying expenditure — even where those contractors are located abroad — provided the arrangement is genuinely at arm's length. This is helpful for SaaS businesses that outsource development to independent studios or freelancers rather than to group entities.

Two things reduce the ratio: development outsourced to related parties (companies within your own group) and the acquisition cost of code or IP bought in from outside. Both sit in the denominator but not the qualifying numerator, so heavy reliance on either dilutes the benefit. To soften this, the rules allow a 30% uplift: your qualifying expenditure can be increased by up to 30%, capped at the level of total expenditure, which often restores a near-full ratio for companies with modest acquired or related-party costs.

Practically, this means you should track qualifying and non-qualifying expenditure on a per-asset basis from day one. Keeping contemporaneous records of who did the development, on what terms, and for which software asset is what lets you evidence a high nexus ratio if the position is ever reviewed.

Worked example: an owner-developed SaaS platform

For an owner-developed SaaS platform with €1,000,000 of qualifying IP profit and a 100% nexus ratio, the effective tax cost works out at roughly 3%. The Cyprus IP Box grants a notional deduction of 80% of the qualifying profit, so only the remaining 20% is subject to corporation tax. This worked example shows how the headline benefit translates into a real number for a software business that built its own product in-house.

Start with €1,000,000 of qualifying IP profit (revenue from SaaS subscriptions, per-seat licences and API fees, net of the directly related expenses of earning it). Because the software was developed in-house, the nexus ratio is 100%, so the full €1,000,000 is eligible. Applying the 80% deduction removes €800,000 from the taxable base, leaving €200,000 of taxable profit.

That €200,000 is then taxed at the 15% corporation tax rate applying from 2026, producing tax of €30,000. Expressed against the original €1,000,000 of IP profit, €30,000 is an effective rate of 3%. The figures are illustrative and assume the whole profit qualifies and the nexus ratio is genuinely 100%; the actual outcome depends on how much of your income is IP income and on your specific expenditure profile. This is a worked illustration, not tax advice.

• Qualifying IP profit: €1,000,000
• Nexus ratio: 100% (in-house development)
• IP Box deduction: 80% → €800,000 removed
• Taxable profit: €200,000
• Corporation tax at 15%: €30,000
• Effective rate: €30,000 / €1,000,000 = 3%

Common mistakes SaaS companies make

The most common — and most expensive — mistake is claiming service or consulting income as IP income. Bundling implementation, customisation and support fees into the IP Box inflates the claim and is exactly what tax authorities look for on review; the safe approach is to invoice and account for services separately from software-access revenue so the IP element stands on its own. Over-claiming here can unwind the whole benefit and trigger penalties.

A second recurring error is weak IP-assignment from contractors. If freelancers or development studios built part of your code without a written assignment of the resulting intellectual property to your Cyprus company, you may not legally own the asset you are claiming on. Every development contract should assign all IP to the company in writing, so ownership matches the entity making the claim.

Two further mistakes concern evidence and substance. Failing to keep per-asset R&D tracking makes the nexus ratio impossible to prove, since the OECD nexus calculation is asset-by-asset; you need records that tie specific development spend to specific software. Finally, relying on acquired code without ongoing R&D is fragile — buying in a codebase and then doing little further development gives you a low nexus ratio and a thin substance story, whereas continued in-house development both raises the ratio and strengthens the claim.

• Claiming service, consulting or support income as qualifying IP income
• Weak or missing IP-assignment clauses in contractor agreements
• No per-asset R&D tracking to evidence the nexus ratio
• Relying on acquired code without ongoing in-house R&D