SaaS and consulting income: separating a Cyprus IP Box claim
Allocate mixed software, implementation, training and consulting income without assuming every SaaS invoice qualifies for the 80% deduction.
IPBox Cyprus editorial team · Ebrovia Ltd
Updated:
A SaaS company should not automatically treat consulting, implementation and training receipts as qualifying IP income. Examine what each contract supplies and how qualifying software contributes to the income. Any allocation must be supported by the facts, with related costs and non-IP profit treated consistently.
One customer relationship can contain several activities
A software customer may pay for platform access, setup, custom configuration, training and strategic advice. The supplier may sell those items separately or under one annual agreement. A single invoice or subscription label does not make them economically identical.
The Cyprus IP regulations recognise embedded income from products and services directly related to qualifying IP. That requires a careful attribution exercise where appropriate; it is not a rule that all services delivered by a software company qualify.
Start with the contract and actual delivery. Identify what the customer buys, which asset contributes to the offering and what work the company performs. The sales description should be checked against operational facts rather than used as the sole evidence.
Separate prices help, but are not conclusive
Distinct contract prices for subscriptions and consulting can make the analysis easier to trace. However, the allocation should still reflect the actual arrangement. Artificially moving most of a consulting fee into a small software-access charge does not establish a defensible IP income result.
Where a bundle has one price, document the method used to attribute income. Relevant evidence may include the nature of the components, commercial pricing and the functions performed. The appropriate method depends on the facts and any applicable pricing rules.
Do not adopt an industry-wide ratio such as “80% of SaaS turnover qualifies”. The statutory 80% deduction is applied later to nexus-adjusted qualifying profit. It does not answer the earlier question of how a mixed customer fee should be allocated.
A transparent mixed-business illustration
Assume a supported analysis identifies €600,000 revenue attributable to qualifying software and €200,000 from consulting. Relevant costs are €250,000 for software income and €150,000 for consulting. The resulting net amounts are €350,000 and €50,000 respectively.
At a supported 80% nexus fraction, qualifying software profit is €280,000 and the IP Box deduction is €224,000. The remaining software profit is €126,000. Adding €50,000 consulting profit gives €176,000 taxable profit in this simplified model and €26,400 tax at 15%.
These figures are illustrative, not suggested allocation percentages. The example excludes other tax adjustments and shows why applying 3% to all receipts would be misleading. Both the supported income split and the nexus fraction affect the outcome.
Allocate costs alongside income
A revenue allocation without a consistent cost allocation can overstate eligible net profit. Staff, infrastructure and support may serve both software access and consulting. Explain the basis for splitting shared costs and ensure the totals reconcile.
Keep development expenditure separate from the annual cost-of-income calculation. A consultant’s work may be ordinary customer service, qualifying development or a mixture. The treatment depends on the work and its connection with the asset, not simply the person’s technical expertise.
Customer-funded custom work can also raise ownership questions. If the customer owns the resulting code, the supplier must not assume it is earning income from software it retains and exploits. Review the rights alongside the revenue classification.
What the finance file should contain
The file should make the business model understandable without relying on a promotional description of the product. Link the contract components to revenue accounts, cost allocations and the relevant software asset.
Review material changes such as new implementation packages, managed services or bespoke development. An allocation suited to a standardised product can become outdated when the service component grows.
- Customer contracts and descriptions of each component.
- Evidence of how the services are actually delivered.
- Supported revenue allocation for bundled prices.
- Consistent direct and shared-cost treatment.
- Ownership analysis for custom software.
- Reconciliation to recognised revenue and total profit.
- Separate nexus schedule for qualifying development.
Use the analysis for pricing and forecasting
A clear split helps management understand which activities generate profit, not just how tax is calculated. Consulting can remain commercially valuable even where its profit does not receive the same relief as qualifying software.
Forecast the business using its expected income mix rather than assuming every future euro will have the full-nexus rate. This produces a more useful cash model and reduces the risk of overstating tax savings when the company expands its service offering.
Common questions
Does implementation income always fall outside IP Box?
Do not apply a universal answer without examining the facts. Determine the activity, the qualifying software contribution and any supported attribution under the applicable rules.
Can I label consulting as a software subscription?
A label does not change what is actually supplied. Contracts, delivery and a defensible income allocation must support the treatment.
Sources and scope
- Cyprus IP regulations, KDP 336/2016
Regulation 4 defines expenditure, the capped uplift and net income; regulation 5 requires records by intangible asset.
- Cyprus Income Tax Law 118(I)/2002, consolidated
Article 9(1)(κ) provides the 80% deduction. The corporate-rate examples use the 15% rate applicable from 2026.
General information, with illustrative examples. Eligibility and tax treatment depend on the facts and applicable law; this article is not an individual tax opinion.