IPBoxCyprus
Cyprus IP Box guides

Software resellers and Cyprus IP Box eligibility

Distinguish third-party software resale from exploiting your own qualifying software, including original integrations and value-added services.

IPBox Cyprus editorial team · Ebrovia Ltd
Updated:

Reselling third-party software does not automatically create qualifying IP income for the reseller. Identify any qualifying asset the company owns or economically owns, the rights it exploits and its relevant development expenditure. A reseller margin and profit from original software require separate analysis.

A software business is not necessarily an IP owner

A company can earn substantial revenue selling licences, arranging subscriptions or providing implementation for another supplier’s software. Those activities can be commercially valuable without establishing that the reseller holds the underlying qualifying software asset.

Review the supplier agreement. Determine whether the company has distribution rights, a licence to use the software, rights to modify it or a broader economic ownership position. Do not infer the answer from the word partner or from access to source code.

The Cyprus IP regulations recognise economic ownership in the qualifying-asset definition. That makes the actual rights important; it does not mean every permission to sell access is economic ownership of the software. A specific assessment is needed where the claim relies on that concept.

Separate resale, services and original development

A value-added reseller may do more than pass through licences. It may build an original integration, develop a separate application or provide consulting and support. Identify those contributions individually rather than assigning one tax treatment to all activity.

An integration is not automatically a qualifying asset merely because code was written. Establish the software, rights, development and income relationship. Equally, the presence of resale activity should not prevent a genuine original software asset from being assessed on its own facts.

Customer contracts should explain what is supplied. If the company sells third-party access and its own module as a bundle, any attribution of income and costs needs support. The 80% statutory deduction is not a substitute for this allocation.

An original add-on changes the questions, not the answer automatically

Suppose a company resells a third-party accounting platform and develops its own inventory module. The platform provider continues to own the core software. The reseller’s module has a separate rights chain and development history.

The company should distinguish receipts and costs associated with the core platform, its module and implementation services. It then assesses whether the module is qualifying software and what net income is attributable to it. The entire customer relationship does not become eligible merely because one proprietary component has been added.

If the module was purchased rather than developed, the acquisition and nexus treatment also matter. If a related group company developed it, related-party outsourcing requires separate classification. The commercial description “our solution” does not answer either question.

Licence purchases are not automatically R&D

Payments to the platform supplier may buy resale rights, customer subscriptions, access or other services. Classify the transaction actually purchased. Do not place all supplier charges into QE because they concern software.

Development costs for the company’s own asset need evidence of the work, claimant and connection with that asset. Support and implementation time can be mixed with development, so a supported allocation may be necessary.

Keep the annual profit calculation separate from nexus. A supplier charge may be relevant to the margin earned from resale without being qualifying development expenditure. Conversely, historic development costs may remain relevant to an owned module’s nexus fraction.

Evidence that distinguishes the business components

A useful file makes clear which rights the company has and how each activity earns income. This is particularly important where marketing describes a combined offering under one product name.

  • Supplier and distribution agreements.
  • Rights in any original module or integration.
  • Employee and contractor ownership records.
  • Customer contracts showing the supplied components.
  • Revenue and supplier-cost reconciliation.
  • Supported allocation of mixed services and software income.
  • Asset-level development and acquisition expenditure history.

Forecast a mixed tax outcome where the facts require it

Do not present the full-nexus 3% illustration as the expected tax rate on all resale turnover. Model the supported profit components and apply the relevant rules to each, including any other tax adjustments.

A partial IP Box opportunity may still be meaningful for a company with genuine original software. The useful question is how much qualifying profit the actual asset supports, not whether the business can adopt a technology label.

Review the assessment when the company’s role changes. Moving from resale to development, acquiring a module or changing supplier rights can alter the analysis. Keep prior expenditure and rights history rather than starting the record again with the new marketing description.

Common questions

Does a licence to resell software establish IP Box eligibility?

Not by itself. Assess the rights and whether the company owns or economically owns a qualifying asset, together with income and expenditure conditions.

Can a reseller’s own integration qualify separately?

Potentially, if it is a qualifying asset with supported rights, development expenditure and attributable income. The conclusion does not automatically extend to all third-party software resale.

Sources and scope

General information, with illustrative examples. Eligibility and tax treatment depend on the facts and applicable law; this article is not an individual tax opinion.