Cyprus IP Box for software companies: eligibility, records and the real cost of support

Understand what the headline percentage describes

Cyprus’s IP incentive allows an 80% deduction on qualifying profit calculated under the nexus approach. The standard corporate tax rate increased to 15% from January 2026. Where the full deduction applies, the arithmetic is 15% × 20% = 3% on that qualifying profit.

This is not a flat 3% rate for every technology company or every euro of revenue. Eligibility, profit calculation and the development connection matter. Other income and obligations need their own treatment.

Start with the asset, not the company label

Sumly’s guidance identifies developed copyrighted software and patents as potential qualifying assets, while excluding brands and trademarks. Calling your business a SaaS company does not answer who owns the asset, how it was developed or which income relates to it.

Prepare a product inventory. For each item, describe what it does, who created it, who owns it and how customers pay to use it. If a product combines acquired code, founder work and contractor development, explain that history rather than presenting it as one undifferentiated asset.

Build the record before year-end

A practical bookkeeping design connects income and development expenditure to the relevant asset. Decide how invoices, payroll and contractor costs will be tagged. Record who performed the work and any relationship between the parties so your adviser can assess the nexus calculation.

The exact tax categorisation needs professional review, but you can make that review easier by retaining the underlying contracts, invoices and development descriptions. A spreadsheet assembled from memory at year-end is a weak starting point for a complex claim.

• An inventory of software and other proposed qualifying assets.
• Ownership and assignment agreements, where relevant.
• Income streams connected to each product.
• Development costs and the parties performing the work.
• A consistent way to link accounting entries to supporting records.

Be careful with software developed before the move

If the product already exists in another company or was built personally, incorporation in Cyprus does not automatically move ownership. Identify the current owner and obtain advice before assigning or licensing the asset. Valuation and cross-border consequences can be separate from routine formation.

Also distinguish selling access to your own product from providing consulting services or reselling someone else’s software. A company can have several activities with different treatment. Ask the adviser to map them before you base a relocation budget on the full advertised benefit.

What “IP Box application support” costs

Sumly lists IP Box tracking at €50/month in addition to a platform plan, excluding VAT. Application assistance is discussed separately on a call. Its guidance explains that the deduction is claimed through the corporate tax return rather than a separate standalone IP Box application form.

Ask the team to distinguish the eligibility assessment, initial records setup, ongoing tracking and return preparation. Find out who reviews the calculation and who submits the return under the plan you select.

Example: a product built by both staff and contractors

Imagine that your employees develop the core application while an independent contractor builds a separate reporting module. Another company controlled by the founder supplies additional development. Keep those three workstreams distinguishable in the records. They may all contribute useful code, but the relationship with each developer can matter to the nexus analysis. A single development expense account without supporting detail makes that assessment unnecessarily difficult.

Ask the technical lead to identify which asset each workstream supports and the accountant to connect the related costs. Have the adviser review the classifications rather than assuming the independent and related suppliers receive identical treatment. This simple example illustrates why project records, contracts and accounting entries need to fit together. It also shows why a monthly tracking fee should be evaluated against a real process for capturing the information, not just the presence of a software feature.

Identify the asset before calculating a benefit

Begin with an inventory of what the company actually develops or owns. A software business may contain several different assets: a core application, a separate analytics engine, a trademark, documentation and customer-specific work. Do not assume that everything sold by a technology company has the same treatment. The review needs to identify the potentially qualifying intangible and connect it to the development activity and income being considered.

For each candidate asset, write a short technical and commercial description. Explain what it does, who developed it, when development began, how it is used and how the company earns money from it. Add links to internal records such as repositories, project plans and relevant contracts. These records support an assessment; a repository alone does not establish legal ownership or tax eligibility. The description should be understandable to an adviser who has not worked on the product.

Separate assets from services surrounding them. A company might license its own software while also charging for implementation, training or bespoke consulting. Those activities can appear on the same invoice, but the income analysis still needs to consider their substance. Ask how the different elements should be identified and allocated. A broad software subscription label is not a reason to assume that every euro received qualifies for the same deduction.

Check the chain of ownership in the code and development work

Confirm who owns the relevant rights today. Code may have been written by a founder before incorporation, by employees, by independent contractors or by another group company. Review the agreements that connect that work to the entity seeking relief. Paying an invoice for development does not always answer every question about ownership and permitted use. Resolve uncertainty in the contractual chain before treating the asset as something the Cyprus company can exploit on the assumed terms.

If an existing product is being moved from another country or entity, treat the transfer as a separate project. It may require valuation, contractual documentation and tax advice in more than one jurisdiction. A standard company formation engagement does not automatically transfer intellectual property. Nor should the move be recorded as a nominal transaction simply because the founder controls both sides. Explain the actual history so the advisers can assess the appropriate treatment.

Keep versions of the relevant agreements and a timeline of ownership changes. Where open-source components or third-party licences are involved, identify their role in the product and the rights the company holds. The tax review and the commercial licensing review are connected but not identical. A clear asset file helps both, and it can also become useful during customer due diligence, investment or a future sale of the business.

Make the nexus analysis traceable to development expenditure

The nexus approach connects the benefit to qualifying development expenditure rather than granting a flat reduction to all technology revenue. Start by classifying costs according to the work performed, the asset concerned and the relationship with the developer. In-house development, unrelated outsourced research and development, related-party work and acquired intellectual property can have different effects in the calculation. Have the classification and any permitted uplift reviewed instead of treating every invoice with development in its description as equivalent.

Create project codes that your technical and accounting teams can both understand. For example, one code might refer to the core billing engine while another covers a separate mobile application. Staff time, contractor invoices and relevant supporting documents can then be connected to the correct project. Avoid creating a level of detail that nobody can maintain. The system should be sufficiently specific to support the analysis and sufficiently practical that the team updates it while the work is happening.

Reconcile the project records with the general ledger. If the development schedule says a project incurred €80,000 while the accounts show a different amount, identify the reason rather than leaving two competing figures. Timing, capitalisation, allocation and excluded costs may explain differences, but they should be documented. The purpose of tracking is not to generate an impressive dashboard; it is to make the calculation reproducible from underlying records when the return is prepared or questions arise.

Compare a full-benefit example with a reduced nexus example

Assume, for illustration only, €100,000 of relevant net IP profit, a fully qualifying asset and a nexus fraction of one hundred percent after the required calculation. An eighty percent deduction would be €80,000, leaving €20,000 subject to the assumed fifteen percent corporate income tax rate. The resulting tax is €3,000, equivalent to three percent of the illustrated profit. The example excludes other adjustments and does not establish that a particular company or product meets the conditions.

Now assume the same €100,000 of relevant net IP profit but a nexus fraction of fifty percent. The qualifying portion for this simplified illustration is €50,000. Applying the eighty percent deduction to that portion gives a €40,000 deduction, leaving €60,000 taxable at fifteen percent. The resulting tax is €9,000, or nine percent of the original profit. This shows why quoting a three percent result without the nexus assumptions can materially overstate the benefit.

Finally, consider non-qualifying activities alongside the product. If the company also earns profit from consulting, that profit needs its own treatment; it does not automatically inherit the illustrated IP result. Ask the adviser to show the calculation by relevant asset or activity and then reconcile it to the company’s overall tax computation. The useful number for cash planning is the supported company-wide liability, not the lowest theoretical rate shown on one part of the business.

Handle mixed software and service revenue consistently

A common commercial model combines recurring software access with onboarding and support. Another charges customers for bespoke development while retaining a reusable internal framework. These models require more analysis than simply checking whether the business describes itself as SaaS. Prepare the customer agreements and explain what the customer receives, what rights are granted and which parts of the price relate to different deliverables. The legal wording and actual delivery should tell a consistent story.

Discuss an allocation method before the year-end rush. If shared staff, infrastructure or other costs support several activities, explain how the business records them and ask what method is appropriate for the tax calculation. Do not allocate all costs to ordinary services while assigning all income to qualifying IP merely to improve the result. The method should be supportable, consistently applied and connected to the underlying commercial facts.

Review changes in the product catalogue. A new consulting offer, an acquired application or a major licensing arrangement can alter the income mix. Tell the person maintaining the IP records when those changes occur so the accounting setup can adapt. It is easier to add a sensible revenue code when a new product launches than to separate a year of combined invoices later, especially when several staff members remember the work differently.

Design a monthly record process the team will actually follow

Assign one person to keep the development overview current and another, if appropriate, to reconcile financial records. At month end, review new projects, completed work, contractor invoices and any changes in asset ownership or income streams. Record unresolved classification questions for the adviser. This routine does not need to become a large internal bureaucracy. Its value is that the evidence is captured while developers and founders can still explain what happened.

Keep the supporting material proportionate but coherent. Project descriptions explain the purpose of the work; time or task records help connect people to activity; contracts explain the relationship with developers; invoices and payment records connect the work to expenditure. No single document answers every question. Together they create a more useful trail than a folder containing only invoices labelled software services. Preserve the records in a form that remains accessible if a contractor leaves or an internal tool changes.

Schedule a periodic review of the assumptions behind the calculation. Check whether related-party relationships changed, an asset was acquired, a project was abandoned or a product started generating a different type of income. Those events may affect the analysis. The monthly process should make exceptions visible instead of automatically categorising everything under the same rule. This is where ongoing tracking can be useful, provided the initial eligibility and accounting approach have been properly established.

Agree what initial assessment and ongoing support include

The phrase IP Box application can make the process sound like buying a separate licence that permanently approves a tax rate. Ask the provider to explain the actual work: initial review, asset and expenditure analysis, supporting records, the tax computation and the relevant return treatment. If a ruling or other specialist advice is proposed for a particular uncertainty, scope that separately. Do not assume that routine tracking includes every legal or tax question connected with an existing international software business.

Sumly publishes an IP tracking add-on at €50 per month on top of the applicable plan. Confirm the current terms, the initial work required and who prepares or reviews the final calculation. For budgeting, twelve months at that figure is €600 before VAT, but it is not an all-in price for transferring intellectual property, obtaining valuations or resolving ownership problems. Those are distinct tasks that may need different professionals and separate fees.

Before a call with Relocated.cy, prepare the product description, ownership history, development locations, related-party relationships and a rough breakdown of income and development costs. State whether the product already exists or is being built in the new company. Sumly can use that information to scope its support and identify the analysis needed. A well-supported deduction begins with a real asset and reliable records, then a calculation; it should not begin with a promised tax rate and work backward.

What to bring to the first discussion

Bring a short product description, ownership history, approximate development spending and a breakdown of how the business earns money. A useful first outcome is knowing whether the opportunity merits a detailed assessment and what evidence is missing.

Relocated.cy can coordinate that discussion with company setup and ongoing Sumly support. Establish the commercial and tax scope before treating an indicative rate as part of your business forecast.