An IP asset register for a Cyprus IP Box claim

Give every calculation a stable asset identity

A tax computation can contain accurate arithmetic while referring to an unclear asset. Product names change, repositories are reorganised and several subscription plans may use one codebase. A stable identifier helps keep the rights, costs and income connected across those changes.

The register is an index to evidence, not proof of eligibility on its own. Each entry should explain what the asset is and where the supporting documents are held. A row labelled “software” with a value is rarely enough to make the claim understandable.

Start with the technology and rights map. Distinguish original software, acquired components, brands and other assets. Record the category relied upon for IP Box purposes and any unresolved question rather than marking every intangible as qualifying by default.

Suggested fields and what each one explains

Adapt these fields to the business. They are suggested controls, not a statutory list of mandatory column names.

How one entry connects the supporting files

For SW-001, the register points to the employee and contractor rights file, a development history, an income reconciliation and the nexus schedule. Each of those files uses the same identifier. The register does not repeat every invoice or code commit.

If the company later launches a second brand using the same software, record the commercial change without automatically creating a new asset. If a genuinely separate asset is developed, document that conclusion and its relationship to the original platform.

The distinction matters because renaming a product should not erase its acquisition history or duplicate development expenditure. A stable register makes those mistakes easier to detect.

Record asset boundaries and shared work

Explain material boundary decisions: one codebase may support several products, or one product may rely on separate software assets. The appropriate tracking follows the facts and applicable rules, not whichever grouping gives the lowest tax.

Where shared R&D cannot be directly assigned, link the allocation method and supporting evidence. The sum of allocations should reconcile to actual expenditure. The register can identify the affected assets, while the detailed calculation remains in its own schedule.

Do the same for bundled income. A register entry should point to the revenue allocation analysis rather than imply that every receipt bearing a product name belongs to one qualifying asset.

Use changes as review triggers

Update the register when rights are transferred, software is acquired, a major rewrite occurs or a product is retired. Preserve earlier versions and explain changes in classification. Do not overwrite history so that a later reviewer cannot reconstruct the previous claim.

Assign responsibility for keeping the record current and for resolving questions. Finance may maintain the index, while engineering and legal advisers supply relevant facts. The important point is that someone checks whether the entry still describes the business.

Keep access proportionate to the information. The register can link to controlled records without exposing source code, personal details or confidential contracts to everyone who uses the financial schedule.

• Review asset additions, disposals and material changes.
• Check that rights files and income accounts remain linked.
• Reconcile expenditure schedule references.
• Record unresolved eligibility or allocation questions.
• Keep dated versions and an explanation of corrections.

What the register cannot establish by itself

A completed template does not guarantee eligibility, a tax ruling or a particular nexus fraction. It organises the evidence needed to assess those matters. The underlying rights, activities, income and costs must still support the claim.

Use the register as the starting point for an annual review and for investor or buyer due diligence. Its value is that it lets another person find and understand the relevant evidence without relying solely on the founder’s memory.