Decision
Should IP Be Owned by a Holding Company?
Should IP Be Owned by a Holding Company?: short answer
Last reviewed
Yes, and for most software groups it is the preferred structure. A Cyprus IP holding company owns the code and licenses it to an operating company for a royalty. The nexus fraction is maintained by having the IP company itself fund the development, through its own staff or unrelated contractors.
| Recommended structure | Cyprus IP holding company owning the IP, separate operating company under licence |
|---|---|
| How the operating company pays | A royalty, ordinarily percentage-based or a fixed fee, deductible to the payer |
| How nexus is maintained | The IP company funds development through its own staff or unrelated contractors |
| Qualifying expenditure | Own staff and genuinely unrelated R&D partners, wherever located |
| Requires careful structuring | Development funded by a related party, which enters overall expenditure |
| Additional benefits | Asset protection, licensing to multiple operating entities, a cleaner acquisition perimeter |
The two-entity model separates the most valuable asset from trading risk and supports the IP Box at the same time, provided the development is funded from the entity that owns the asset.
The two-entity model
For most software and AI groups, the effective Cyprus structure is two companies rather than one.
A Cyprus IP holding company owns the software, the algorithms, the models and the codebase. A separate operating company handles customer contracts, billing, support and day-to-day operations. The IP company grants the operating company a licence, and the operating company pays a royalty back for it, ordinarily percentage-based or as a fixed fee.
That royalty is deductible to the operating company and is income of the IP company, where the IP Box deduction applies to it. The structure also does what founders want it to do commercially: the most valuable asset sits outside the entity carrying trading risk, it can be licensed to more than one operating company as the group expands into new markets, and an acquirer can value it distinctly.
The question is therefore not whether to separate the IP. It is how to separate it while keeping the nexus fraction intact.
How nexus is maintained
The nexus fraction measures qualifying expenditure the claimant itself incurred against overall expenditure on the asset. Since the IP company is the claimant, the development has to be funded from there.
In practice that means the IP company:
- Employs its own technical staff, or engages the development team directly under contract.
- Contracts unrelated R&D partners in its own name where development is outsourced.
- Pays those costs from its own accounts, so the expenditure record sits with the entity claiming.
- Takes the technical decisions, with Cyprus-based directors participating in strategic direction.
- Documents the roadmap, the sign-offs and the commit history against its own governance.
Geography is not the constraint. A development team distributed across several countries produces qualifying expenditure provided the contractual relationship runs to the IP company and the parties are unrelated. What matters is the relationship and who bore the cost, not where the developers sit.
The arrangement that needs care
The version that requires attention is the one where the operating company employs the engineers and pays for the development, while the IP company owns the resulting code.
That development is related-party expenditure from the IP company's perspective. It enters overall expenditure without entering the qualifying numerator, which compresses the nexus fraction and reduces the proportion of income the deduction applies to.
This is a structuring question rather than a barrier. The usual remedies are straightforward:
- Move the development contracts and payroll into the IP company, so future spending qualifies.
- Engage unrelated R&D partners directly from the IP company rather than through the operating entity.
- Where some related-party development is unavoidable, apply the uplift, which adds up to 30 percent of qualifying expenditure to the numerator, capped at the non-qualifying amount.
- Track the fraction cumulatively, because it improves as qualifying spending accumulates over the life of the asset.
What the structure needs alongside it
Two supporting elements make the model hold together.
Transfer pricing. The royalty between the operating company and the IP company is a related-party transaction and needs to be set on arm's length terms and documented. Getting the rate supported at the outset is considerably easier than justifying it later.
Substance in the IP company. The entity claiming the deduction is asserting that it owns, directs and exploits a valuable intangible from Cyprus. That calls for Cyprus-based directors participating in strategic decisions, registered premises and active banking, and technical or managerial capacity in Cyprus or contracted R&D partners working to it.
Both are ordinary features of a properly implemented structure, and both are far cheaper to establish during setup than to retrofit.
Common questions
Can a holding company own IP and claim the Cyprus IP Box?
Yes. A Cyprus IP holding company owning the software and licensing it to an operating company is the standard structure for software groups. The deduction is available to it provided it is Cyprus tax resident and the nexus fraction reflects development it funded itself.
Who should employ the developers?
The company that owns the IP, either directly as employees or by contracting unrelated R&D partners in its own name. That is what makes the spending qualifying expenditure for the entity claiming the deduction.
What if the operating company already employs the engineers?
The development is then related-party expenditure and the fraction is diluted, which is a structuring issue rather than a dead end. Moving the contracts and payroll into the IP company improves the position from that point, and because the fraction is cumulative it recovers as qualifying spending accumulates.
Does the royalty between the two companies need documentation?
Yes. It is a related-party transaction requiring arm's length pricing and transfer pricing support. Setting and documenting the rate when the licence is put in place is the straightforward moment to do it.
Can the IP company license to more than one operating company?
Yes, and that is one of the reasons the structure is used. A single IP company can license to operating entities in several markets, which keeps ownership consolidated while local operations sit where the customers are.
Technical definition
A two-entity structure in which a Cyprus IP holding company owns the software, algorithms and related intangibles, and a separate operating company handles customer contracts, support and daily operations under a licence, paying a royalty to the IP company. The IP company claims the IP Box deduction on that royalty and embedded income.
Practical implications
The nexus fraction rewards research the claimant itself funded, so the IP company should contract the development directly, whether through its own technical staff in Cyprus or through unrelated R&D partners. Where the operating company funds the development instead, that spending is related-party expenditure and careful structuring is needed to maintain the deduction.
Common misconceptions
Two errors recur. The first is assuming that any holding company can hold IP and claim the deduction regardless of who paid for the development. The second is the opposite: concluding that because nexus follows funding, IP should never sit in a separate entity. Both miss the point, which is that ownership and funding should sit in the same company.