Acquired software and the Cyprus IP Box nexus

Separate the asset test from the expenditure test

Two questions are often confused in an acquisition. The first is whether the intangible asset falls within the qualifying categories and meets the applicable conditions. The second is how the claimant’s expenditure on that asset enters the nexus calculation. A positive answer to the first does not make every euro paid for it qualifying expenditure.

The Cyprus regulations contemplate acquired intangible assets, while expressly excluding acquisition cost from QE and including it in overall expenditure. The distinction is deliberate. Buying an existing codebase cannot simply be relabelled as conducting the development that created it.

Review the purchase agreement and what was actually obtained: software rights, a licence, trademarks, customer relationships, services or several components together. The contract price may require a supported allocation. Marketing IP and other non-qualifying assets do not become eligible merely because they were purchased alongside software.

Model later development against the acquisition history

Suppose a company buys a qualifying software asset for €400,000 and subsequently incurs €100,000 of its own qualifying R&D on that asset. Ignoring other expenditure, QE is €100,000, the uplift is €30,000, and OE is €500,000. Nexus is 26%.

If annual net IP income is €200,000, qualifying profit is €52,000 and the 80% deduction is €41,600. The simplified taxable balance is €158,400, giving €23,760 tax at 15%, or 11.88% of net IP income. The headline 3% does not describe this acquisition-heavy example.

If another €300,000 of qualifying development is later incurred on the same asset, cumulative QE becomes €400,000 and the uplift €120,000. With OE of €800,000, nexus becomes 65%. These illustrations show how expenditure history changes the result; they do not recommend spending money solely to obtain relief.

Keep the price allocation and ownership evidence

An acquisition file should explain the rights transferred, the seller, consideration and valuation basis. Identify whether the arrangement transfers ownership, provides an exclusive licence or grants more limited access. Economic ownership can be relevant under the regulations, but a label in an invoice does not settle the analysis.

Where the seller is related to the buyer, assess the arm’s-length transaction and documentation requirements separately. A valuation issue is not solved by the nexus formula. The amount included in the tax analysis should be supported by the actual transaction and applicable rules.

Retain the development and version history needed to distinguish the acquired technology from later work. A major rewrite may raise questions about the asset being developed. Do not create a new asset identifier solely to leave the acquisition cost behind while continuing to exploit substantially the same rights.

Buying assets is different from buying shares

A share purchase changes the shareholder of the company that holds the software; an asset purchase transfers the software or rights to another taxpayer. The purchaser’s price for shares is not automatically the software acquisition cost in the target company’s nexus schedule.

That distinction does not mean a share deal guarantees preservation of every tax benefit. Review the target’s historic claims, expenditure evidence, ownership, tax risks and any subsequent restructuring. The seller’s claim of a 3% rate should be tested against actual calculations and the facts supporting them.

Before choosing a structure, compare commercial liabilities, ownership transfers, tax treatment in the relevant countries and compliance costs. Nexus is one part of that decision, not a complete acquisition model.

• Identify whether shares, assets or licence rights are being acquired.
• Review the target asset’s eligibility and ownership chain.
• Obtain the expenditure history and existing nexus calculations.
• Allocate consideration across acquired components with support.
• Model subsequent development without erasing historic costs.
• Check transfer pricing and cross-border consequences separately.

Keep amortisation separate from nexus

Tax amortisation may affect the annual profit calculation under its own rules. It does not turn the acquisition payment into QE or make the nexus denominator equal to the asset’s current accounting carrying value. Keep purchase cost, amortisation and development additions in separate reconciled schedules.

A business case should therefore include both the expected operating economics and the supported tax model. The relevant question is how much cash the acquisition can generate after all costs and taxes, not whether the software sector is generally associated with the IP Box.