Related-party R&D under the Cyprus IP Box

Identify the actual development arrangement

A group can organise software development through employees of the IP owner, a development subsidiary or independent contractors. Those arrangements may produce similar technical work but different nexus results. Start with who incurs the expenditure and who provides the services.

The Cyprus regulations expressly distinguish outsourcing to unrelated persons from amounts paid or payable directly or indirectly to related persons for R&D. They also address cost-sharing arrangements. A contract name such as “reimbursement” or “cost contribution” does not remove the need to examine the relationship and actual work.

Map the contractual and payment chain where several entities are involved. Do not assume that placing an intermediary between the IP owner and a related developer changes the substantive classification. Record the parties, relationship, services, charging basis and asset concerned before completing the nexus schedule.

A group-development example

Assume the claimant has €300,000 qualifying expenditure and €200,000 related-party R&D on one asset, with no acquisition cost. Overall expenditure is €500,000. The uplift is the smaller of €90,000, being 30% of QE, and the €200,000 related-party amount. Nexus is therefore €390,000 divided by €500,000, or 78%.

On €400,000 annual net IP income, qualifying profit is €312,000. The 80% deduction is €249,600, leaving €150,400 taxable in this simplified example. At 15%, tax is €22,560, equivalent to 5.64% of net IP income before other adjustments.

The related-party cost has not made the asset automatically ineligible, but the full-nexus 3% illustration no longer describes this case. Nor does the uplift cover all €200,000: its separate 30%-of-QE ceiling matters.

Transfer pricing and nexus are different tests

Transfer pricing examines whether controlled transactions are consistent with the arm’s-length principle and how functions, assets and risks support the pricing and profit allocation. Nexus determines what proportion of qualifying IP profit receives the deduction through the expenditure formula.

An intercompany development charge can be appropriately priced and still remain excluded from QE because it is related-party outsourcing. Conversely, a favourable nexus fraction does not establish that the IP owner is entitled to all group profit or that an intercompany royalty is correctly priced.

Maintain both analyses where relevant. The development agreement and operational evidence should explain who controls development, bears risks and exploits the rights. The expenditure schedule should separately explain how costs were classified under the IP Box rules. Do not use one document’s conclusion as a substitute for the other.

What the supporting file should show

A useful file connects the contractual model to operations. If a subsidiary is described as providing routine development services, the work records, decision-making and risk control should be consistent with that description. A signed agreement alone cannot establish how the business actually functioned.

Keep changes visible. A developer moving from the subsidiary’s payroll to the IP owner’s payroll can change the arrangement prospectively, but it does not rewrite the earlier outsourcing history. Historic costs and subsequent own-development expenditure need to remain distinguishable.

Reconcile intercompany charges to the accounts and to the asset schedules. Explain any shared services or non-development components rather than inserting the entire invoice into one category. Where the classification is uncertain, resolve the underlying facts before choosing the more favourable column.

• Group relationship and relevant ownership or control facts.
• Contracts and descriptions of actual development services.
• The asset or assets benefiting from the work.
• Invoices, supporting cost records and allocation methods.
• Evidence of development decisions and risk control.
• Separate nexus and transfer-pricing conclusions.

Do not restructure around the fraction alone

A change in the development model can affect employment, operational control, transfer pricing and tax in several countries. Compare those consequences with any expected IP Box benefit. Moving an invoice without changing the real arrangement may create more uncertainty rather than a stronger position.

Use a sensitivity model to quantify the actual effect of proposed future expenditure, retaining the historic denominator. Then assess whether the proposed arrangement makes commercial sense and can be operated as documented. The tax calculation should follow a credible business structure.