Developer salaries and Cyprus IP Box qualifying expenditure

A technical role does not make every hour R&D

The regulations expressly include wages and salaries within qualifying expenditure, while requiring a direct connection with the qualifying intangible asset. This is why payroll is often central to the nexus calculation of a software business. It is also why importing the entire engineering payroll without analysis can overstate the numerator.

A developer may work on a new product capability, investigate a technical problem, answer customer tickets and prepare a sales demonstration within the same week. These activities do not become identical for tax purposes because one person performed them. Describe the underlying work, identify the asset and then assess the associated expenditure.

Job descriptions help establish responsibilities, but they rarely explain how a particular period was spent. Use project records, work logs, release documentation and management evidence together. A percentage repeated unchanged every month should be capable of surviving a factual check against the work actually performed.

An illustrative mixed-duty payroll allocation

Assume an employee’s salary cost for a period is €8,000. Supported work records attribute half to development of Product A, one quarter to Product B and one quarter to operational support. If the development activities satisfy the qualifying criteria, the candidate salary allocation is €4,000 to A and €2,000 to B. The remaining €2,000 needs its own treatment rather than automatically entering QE.

The example does not establish a statutory percentage or an official timesheet method. Its purpose is to show how the same payroll line can be divided using evidence. Employer contributions, bonuses, benefits and other payroll-related amounts require their own classification; do not add every payroll ledger account to QE without reviewing what it represents.

Reconcile the allocated total to payroll and avoid duplicate charges. If another group entity employs the developer and invoices the Cyprus business, the cost is not simply the Cyprus company’s own salary expenditure. The outsourcing and related-party rules need to be applied to the actual arrangement.

Connect payroll, work and the asset

A practical evidence chain runs from the payroll entry to the person, from the person to the documented work and from that work to the qualifying asset. Each link serves a different purpose. A payslip establishes compensation; it does not establish the nature of development. A code commit shows a change; it does not establish the full cost.

Create stable project and asset identifiers that finance and engineering both understand. Keep a short explanation of material allocations, including shared-platform work. Where several products benefit, use a supported allocation instead of counting the same effort in every product’s nexus numerator.

Review the distinction between development and routine operation periodically. A team’s duties can change after launch, and a founder may move from coding to management or sales. Last year’s allocation should not be carried forward solely because it produced a favourable result.

• Payroll period and employee reference.
• Description of the development task and its connection with the asset.
• Supporting project, release or work records.
• Allocation method for mixed duties and shared work.
• Reconciliation of allocated amounts to the underlying payroll.
• Evidence of the employer and any intercompany recharge.

Founder time and unpaid work need particular care

A founder’s valuable effort is not the same thing as expenditure incurred by the claiming taxpayer. Do not insert a market-value salary for unpaid historic work merely to create a stronger nexus fraction. Establish the actual expenditure and legal arrangement before deciding what enters the schedule.

Pre-incorporation development raises additional ownership and expenditure questions. A later transfer of code to a company does not automatically turn the founder’s historic effort into that company’s own R&D expenditure. Review the transfer, any consideration, supporting records and subsequent development separately.

Where records are missing, identify the gap and recover genuine source evidence where available. A retrospective narrative may explain events, but it should not be presented as a contemporaneous timesheet. The goal is a traceable, supportable calculation, not a perfectly filled spreadsheet.