For a profitable software company, the Cyprus IP Box can be one of the most commercially valuable parts of a Cyprus structure.
Qualifying profits generated from proprietary software can be taxed at an effective corporate tax rate of 3%. On €1 million of fully qualifying software profit, that can mean approximately €120,000 less corporate tax than applying the standard 15% Cyprus rate to the full amount.
That is capital the company can retain for:
- product development
- senior hires
- customer acquisition
- acquisitions
- international expansion
- distributions to shareholders
The opportunity is not limited to companies collecting traditional royalties. Qualifying IP income can include royalty income, income embedded in products or services, and other qualifying income. This makes the regime potentially relevant to subscription-based software companies where customers pay to access proprietary technology.
The strongest cases are businesses where the Cyprus company genuinely owns or economically owns the technology, funds or undertakes the relevant development activity, and earns identifiable profit from commercialising the software.
That does not make the regime inaccessible. It makes the tax result defensible.
Royal Pine helps software founders establish whether the opportunity is real, estimate the value of the relief and build the company, development, legal and accounting architecture required to support it.
How the 3% Cyprus IP Box Rate Works
From 1 January 2026, the standard Cyprus corporate income tax rate is 15%. The Cyprus IP Box provides an 80% deduction against qualifying net IP profit, calculated under the nexus approach.
Only the remaining 20% is taxed at the standard rate.
The €800,000 deduction is not an expense the company has to pay.
It is a tax deduction granted by the IP Box rules. It is sometimes called a notional deduction or deemed expense deduction, but the practical meaning is simple:
Cyprus removes 80% of the qualifying profit from the corporate tax calculation. The company pays 15% tax on the 20% that remains.
Without the IP Box, €1 million taxed at 15% would produce €150,000 of corporate tax.
With the full IP Box benefit, the tax would be €30,000.
The potential difference is €120,000 per year.
Could your software profits qualify?
The answer depends on how the technology was created, which company owns it, who pays the developers, where the commercial risk sits and whether the income and costs can be traced properly. Royal Pine reviews those questions before a founder transfers software, moves contracts or rebuilds the operating structure. The objective is to know whether the opportunity is commercially worthwhile before implementation begins.
Which Software Businesses Can Benefit?
Software can fall within the qualifying intellectual-property framework, provided the legal, development and commercial conditions are met. Potential candidates include companies developing:
- SaaS platforms
- enterprise software
- mobile applications
- gaming software
- fintech systems
- cybersecurity products
- artificial-intelligence tools
- developer infrastructure
- data-processing platforms
- workflow automation
- proprietary APIs
- logistics software
- health technology
- industry-specific software
The company does not need to be labelled a technology startup. What matters is the economic reality.
The software should be a proprietary asset that generates identifiable income or creates identifiable value within what customers buy.
A profitable SaaS platform whose customers pay monthly to access its technology may be a strong candidate. A consultancy using a basic internal tool to deliver human services is a different case.
The question is not whether the company uses software. It is how much of the company’s profit is genuinely produced by the proprietary software it owns and develops.
Can SaaS Subscription Revenue Qualify?
Potentially, yes.
A SaaS customer rarely receives an invoice labelled software royalty. The customer pays a monthly or annual subscription for access to a platform. That fee may include several commercial components:
- access to the proprietary software
- hosting
- implementation
- support
- onboarding
- customisation
- training
- consultancy
- data services
- third-party technology
The absence of a separately stated royalty does not automatically exclude the software profit from the regime. The company must still determine how much net profit is attributable to the qualifying software.
That requires more than looking at revenue. The calculation may need to separate:
- software-related income
- implementation fees
- professional services
- third-party software
- customer support
- direct development expenditure
- maintenance expenditure
- sales and marketing costs
- hosting costs
- appropriate overheads
The opportunity is not to relabel all company revenue as IP income. It is to build a credible method for identifying the commercial profit generated by the qualifying software.
A More Realistic SaaS Example
Assume a Cyprus SaaS company produces €1 million of total annual net profit.
After analysing its income and costs, the company determines that €700,000 relates to its qualifying proprietary platform and €300,000 relates to implementation, consultancy and other non-qualifying activity.
| Profit category | Tax calculation | Tax |
|---|---|---|
| Qualifying software profit | €700,000 × 3% | €21,000 |
| Other business profit | €300,000 × 15% | €45,000 |
| Total corporate tax | €66,000 |
The qualifying software profit receives the effective 3% rate. The other profit remains taxable at the standard corporate rate.
The overall effective rate in this example is 6.6%.
That is still a substantial advantage. It is also a more useful way for founders to model the regime than applying 3% tax to turnover and assuming the result is automatic.
The Nexus Rule, Explained Without the Jargon
Identifying software profit is only one part of the calculation. The company must also satisfy the nexus approach.
The tax benefit follows the research and development activity that created the software.
The modified nexus approach connects preferential tax treatment with the R&D expenditure that produced the relevant intellectual property. The greater the qualifying taxpayer’s role in undertaking and funding the development, the stronger the connection between the profit and the tax benefit.
This prevents a group from developing software in one company, transferring legal ownership to another company, and claiming the full IP tax benefit in the second company without the relevant development activity.
The nexus analysis therefore asks:
- Which company employs or contracts the developers?
- Which company pays the development costs?
- Who directs the product roadmap?
- Who decides what is built?
- Who carries the commercial risk if development fails?
- Who owns the resulting rights?
- Which company earns the customer revenue?
- Can the development expenditure be connected to the software asset?
A Cyprus company that only receives licence income while the development, decision-making and risk sit elsewhere may have legal ownership without a strong nexus position.
A Cyprus company that owns the product, funds development, directs the roadmap and earns the commercial income has a more coherent case.
Do All Developers Need to Move to Cyprus?
Not necessarily.
Modern software businesses rarely keep every developer in one office. A Cyprus company may work with:
- Cyprus employees
- international employees
- independent contractors
- specialist agencies
- distributed development teams
The important distinction is not simply where the developer opens their laptop. It is the relationship between the developer and the company claiming the benefit.
R&D expenditure incurred directly by the qualifying taxpayer and qualifying outsourcing to unrelated parties is treated differently from the cost of acquiring IP or outsourcing development to related group companies. Acquisition costs and related-party outsourcing are not included as core qualifying expenditure, although a restricted uplift of up to 30% of qualifying expenditure may apply in the nexus calculation.
For founders, this means the development model matters.
A Cyprus company contracting independent developers can be in a different nexus position from a Cyprus IP-owning company that pays a related subsidiary to employ the entire development team.
Neither arrangement should be judged from the organisation chart alone. The agreements, ownership, control, transfer pricing, expenditure and development records need to be considered together.
The Planning Opportunity
The nexus rule is often presented as a limitation. For a founder planning early enough, it is better understood as an architectural decision.
The opportunity is to align:
- software ownership
- development contracts
- employment arrangements
- product decision-making
- revenue contracts
- expenditure tracking
- financial reporting
A company that waits until the software is mature may need to analyse years of historic development, transfers and related-party arrangements.
A company that builds the right structure earlier can create the records as the product develops.
Good documentation produced in real time is part of the operating system. Reconstructed documentation is an argument.
Can Existing Software Be Transferred to Cyprus?
Potentially.
A founder may already own valuable software personally or through an overseas company. That software may be transferred, licensed or contributed to a Cyprus company, depending on the circumstances.
But moving legal ownership does not automatically move the full tax benefit. The transaction may raise questions including:
- What is the software worth?
- Is the transfer taxable in the current jurisdiction?
- Is it being sold, licensed or contributed?
- Who developed the historic code?
- Which company incurred the historic costs?
- Who will perform future development?
- Are transfer-pricing rules engaged?
- Will the Cyprus company own the future improvements?
- How much future profit will relate to qualifying new development?
The nexus framework restricts the extent to which acquired IP costs and related-party development increase the qualifying nexus expenditure.
For that reason, the strongest strategy is not always to transfer finished software to Cyprus and apply 3%.
It may instead be to establish the future operating and development model in Cyprus, continue building the technology through the right company, and allow the qualifying position to grow with the product.
For software that is still being developed, improved and commercialised, the future architecture can be more important than the historic code transfer.
What Does Not Normally Receive the IP Box Benefit?
The Cyprus IP Box is intended to reward innovation-related intellectual property, not every intangible asset owned by a business.
Founders should not assume the regime applies to:
- trademarks
- company names
- logos
- domain names
- customer lists
- brand reputation
- general commercial goodwill
- marketing concepts
- a Cyprus invoicing company with no relevant development activity
- passively held software developed entirely elsewhere
- all company profit simply because the business sells technology
This does not reduce the commercial value of those assets. It means their value should not automatically be included in the qualifying software-profit calculation.
A marketplace may derive substantial value from its network, customer base and sales operation. A consultancy may derive most of its profit from human expertise. A consumer application may depend heavily on branding and paid acquisition.
The calculation must follow what actually produces the profit.
What Records Should a Software Company Maintain?
A credible IP Box position should not be assembled once a year from a general ledger category labelled development costs.
The company should be able to identify:
- each relevant software asset or product
- the legal and economic owner
- the employees and contractors who developed it
- the work each team performed
- development expenditure by product or asset
- related-party and unrelated-party costs
- ownership and assignment agreements
- product-roadmap decisions
- income attributable to the software
- direct costs associated with that income
- the nexus calculation
- the annual qualifying-profit calculation
The accounting system therefore needs to do more than produce annual financial statements. It needs to preserve the relationship between the developers, the expenditure, the software and the profit.
A Publicly Documented Example: GDEV
Private companies rarely disclose their detailed tax positions. A technology company having offices or employees in Cyprus does not prove it claims IP Box relief. Royal Pine would not describe a company as a beneficiary based only on its Cyprus presence.
One publicly documented example is GDEV Inc., formerly Nexters.
In public SEC filings, GDEV stated that its group began applying the current Cyprus IP regime from July 2021. The filing explains that the regime is based on the nexus approach and requires a direct connection between qualifying income and the qualifying expenditure contributing to that income. It also describes the 80% exclusion of qualifying profit from qualifying intangible assets.
A more recent GDEV filing continues to describe the Cyprus new IP regime as providing an 80% deemed expense deduction against profit derived from qualifying IP.
The significance is not that every software or gaming business can copy GDEV’s structure. It is that a commercially substantial technology business has publicly documented the use of the nexus-based Cyprus regime.
The result depends on the facts, expenditure and operating model of the company claiming it.
Is Your Software Company a Strong Candidate?
The case is likely to be stronger where most of the following statements are true:
- The company owns or economically owns proprietary software.
- The software is central to what customers pay for.
- The company is profitable or approaching meaningful profitability.
- Development is continuing.
- The Cyprus company can undertake, fund or control genuine development activity.
- Development expenditure can be traced to identifiable software products.
- Software income can be separated from consultancy and other services.
- Contractor and employee arrangements support the ownership position.
- Related-party development has been modelled correctly.
- The company is prepared to maintain the required records each year.
- Cyprus will be part of the real operating model, not simply an invoicing location.
The commercial value of the regime increases as qualifying profit grows.
For a pre-revenue company, the IP Box may influence future planning but produce no immediate tax saving because there is no profit to shelter.
For a profitable SaaS or software company producing seven-figure annual profit, the difference can become a significant source of retained growth capital.
When the IP Box May Not Be Worth Pursuing
The Cyprus IP Box may not be the right answer where:
- the company bought completed software and performs little further development
- all development and control remain in another group company
- the Cyprus company would only issue invoices
- most of the company’s value comes from human services, branding or sales
- development costs cannot be reconstructed or tracked
- the nexus position would restrict most of the benefit
- the expected tax saving is too small to justify the administration
- transferring the software would create a disproportionate tax cost elsewhere
The correct answer is not always to force the business into the regime. The correct answer is to model the structure before changing it.
Royal Pine turns away structures where the commercial and evidential foundations are not strong enough. A tax position should reduce risk and create long-term value, not introduce a claim that the founder has to defend alone.
How Royal Pine Builds the Structure
The IP Box should not be treated as a separate tax calculation added after the software company has been formed. It affects several connected parts of the business:
The company architecture
Which company owns the software, earns the revenue, employs or contracts the team and enters into customer agreements?
The legal architecture
Are the intellectual-property assignments, development agreements, employment contracts and contractor terms consistent?
The tax architecture
How are qualifying profit, nexus expenditure, related-party transactions and non-qualifying income treated?
The accounting architecture
Can the financial records trace development costs and income to the relevant software asset?
The operating architecture
Where are decisions made? Who controls the roadmap? Who bears development risk? Is the structure reflected in how the company actually operates?
Royal Pine coordinates these areas as one system.
The founder should not have to collect one answer from the tax adviser, another from the lawyer, another from the accountant and then personally decide how they fit together.
Turn Your Software Into a Defensible Tax Advantage
The Cyprus IP Box is more than a reduced tax rate.
It is a framework for building a software business where the intellectual property, development activity, contracts and financial reporting support the same commercial reality.
For the right founder, the result can be substantial:
- qualifying software profit taxed at an effective 3%
- within an EU jurisdiction
- through genuine operating activity
- with a position capable of being documented and defended
The earlier the architecture is established, the easier it is to track development expenditure, allocate income and avoid restructuring after the software has already created significant value.
Royal Pine assesses the technology, development model, ownership position and wider founder structure before recommending an approach.
When the opportunity is strong, we coordinate the company, tax, accounting, legal, banking and compliance work needed to implement it.
Your software is already creating value. The question is whether the structure around it is preserving enough of that value.
Sources and Further Verification
Frequently Asked
Founder Questions, Answered.
1. Does SaaS subscription income qualify for the Cyprus IP Box?
It can. The Cyprus regime recognises qualifying income that is embedded within other commercial income, not only separately stated royalties. The company must still calculate the net profit attributable to the qualifying software and separate non-qualifying services or activities.
2. Is every software company in Cyprus taxed at 3%?
No. The 3% effective rate applies to qualifying net IP profit that satisfies the nexus requirements. Other company profit remains subject to the standard corporate income tax rate.
3. What does the 80% deduction mean?
Cyprus allows 80% of qualifying net IP profit to be removed from the corporate tax calculation. The remaining 20% is taxed at the 15% corporate rate, producing an effective 3% rate on the qualifying amount.
4. Do all software developers need to work in Cyprus?
Not necessarily. The treatment depends on who incurs the R&D expenditure and whether developers are employees, unrelated contractors or related-party service providers. Related-party outsourcing and acquired IP costs are treated differently under the nexus calculation.
5. Can existing software be transferred to a Cyprus company?
Potentially. However, the transfer value, departure-country tax consequences, ownership history, future development arrangements, transfer pricing and nexus position must be assessed before implementation.
6. When should a founder review the IP Box opportunity?
Ideally before transferring the software, signing new development agreements, moving customer contracts or completing a major funding or liquidity event. The earlier the operating and accounting architecture is established, the easier it is to support the qualifying position.
