Client-owned custom software and the Cyprus IP Box

Start with the client contract, not the developer’s job title

A development company may produce sophisticated software but transfer the relevant rights to the client. Another company may retain a platform and license access while configuring it for customers. Both employ developers, yet their income and ownership facts differ.

Read the statement of work and rights provisions together. Identify what is delivered, what transfers, what the company retains and whether the client receives an assignment or a licence. Check whether the contract distinguishes reusable background technology from client-specific work.

The Cyprus regulations can recognise economic ownership, but that does not mean any company involved in coding automatically owns the asset for IP Box purposes. Establish the actual rights and economic arrangement before treating service revenue as income from qualifying IP.

Three common arrangements

The following comparison is a way to organise the review, not a declaration of eligibility for every contract with the same label.

Document retained platform rights clearly

A company may use its own framework or modules to deliver client projects. If it intends to retain and exploit those components, the contract should identify the relevant background technology and the client’s permitted use. Avoid assuming a broad assignment leaves the company free to reuse everything.

Maintain a technical map linking the retained modules to their development history and commercial use. A general assertion that the company has “know-how” is not necessarily an identification of qualifying software.

Where a customer funds improvements, review the rights in those improvements and the charging arrangement. The fact that work benefits a reusable platform does not remove the need to examine the actual contract and expenditure incurred by the claimant.

Do not relabel a development fee as a royalty without support

Tax treatment follows the substance and applicable rules, not a convenient invoice label. Changing “development services” to “software licence” does not establish that the company retains and exploits a qualifying asset.

At the same time, avoid a universal claim that every bespoke-project receipt must have identical treatment. A transaction can involve services, licences or disposal of rights. The regulations distinguish relevant income categories, and the particular arrangement needs analysis.

If the contract contains several components, establish a defensible allocation and consistent cost treatment. Do not assume the statutory 80% deduction supplies the allocation percentage. First determine the relevant net income, then apply the supported nexus calculation where appropriate.

Keep customer work and the company’s asset schedule aligned

Track development effort by the relevant project and asset. A team may work on client-owned deliverables and the company’s retained platform during the same period. The expenditure should not all be assigned to the retained asset merely because that asset can support an IP Box claim.

Reconcile payroll and contractor allocations to actual work records. Identify related-party development and acquisition costs separately. Rights analysis and expenditure classification should explain the same operating model.

Where the company sells an asset it previously exploited, review the distinction between a disposal and continuing licence income, including whether the gain is capital or trading in nature. Do not assume every transfer of source code has the same tax result.

Questions to resolve before making a claim

Review material contracts individually or by a genuinely consistent contract model. A standard template can still be modified by client terms, statements of work or later amendments.

• What software or rights are being supplied?
• Who owns or economically owns each component?
• What reusable background technology is retained?
• Who owns improvements and future versions?
• What does each part of the fee compensate?
• How are relevant income and costs recorded?
• Which expenditure relates to the claimant’s qualifying asset?
• Have transfers or disposal gains been analysed separately?

Align tax planning with the business model

Retaining a platform can be commercially attractive, but customer requirements, pricing and liability also matter. Do not rewrite rights solely to obtain a tax label that the operating arrangement cannot support.

A clear contract and asset map lets the company assess its actual opportunities. It can distinguish profitable service work from qualifying software exploitation without pretending that one description fits every project.