Documents for a Cyprus IP Box tax ruling request

Define the question before collecting documents

A large folder is not necessarily a clear application. Start with the issue on which clarification is sought: the qualifying asset, income attribution, expenditure classification or another specific aspect of the arrangement. State the relevant facts and distinguish existing operations from proposals.

Explain the taxpayer and parties involved. A group diagram can help, but it should connect to the actual ownership, development and payment relationships. Avoid diagrams that show legal entities without explaining what each one does.

The Cyprus Tax Department’s ruling framework emphasises complete facts and information. Confirm the current submission process and required administrative material when filing; a generic website checklist cannot replace case-specific requirements or follow-up questions.

Organise the file by the proposition it supports

Use an index that tells the reviewer why each document is included. Suggested sections are set out below.

Explain the software in language a tax reviewer can follow

Describe the functionality, users and commercial role of the software without relying only on marketing language or technical jargon. Identify the relevant asset and its boundaries, including material third-party components and rights.

A full source-code dump is not a substitute for that explanation. Use targeted technical evidence and references where appropriate, keeping confidential material proportionate to the issue. The file should show what was developed and how it is exploited.

Where several products share a platform, explain the tracking and allocation approach. A company-wide total with no asset connection leaves the reviewer unable to follow the nexus calculation.

Make the calculations reproducible

Show the expenditure inputs, uplift cap, nexus fraction, net IP income and 80% deduction as separate steps. Reconcile each input to its supporting schedule and the relevant accounts. Label examples and projections clearly.

Do not hide unresolved classifications in a single total. If a payment could be an acquisition, related-party development or another category, establish the facts and explain the proposed treatment. The application should expose the issue on which clarification is needed.

Check that the narrative and numbers describe the same arrangement. A statement that all development is internal conflicts with an expenditure schedule dominated by a group-company invoice unless the difference is explained.

Common preparation problems to remove

The most useful review asks whether another person can reconstruct the position from the file. Remove contradictions, duplicate versions and unsupported promotional claims before submission.

Dates matter. Distinguish signed agreements from drafts and completed transactions from planned steps. Do not present a proposed operating model as an established historical fact.

• Unclear asset descriptions or ownership gaps.
• Nexus totals without underlying expenditure history.
• Turnover used where net IP income is required.
• Unexplained income or shared-cost allocations.
• Contracts inconsistent with the stated operating model.
• Projections presented as actual results.
• Missing current administrative or fee material.

Keep the application as part of the ongoing evidence file

Retain the submitted version, supporting documents, correspondence and response together. They establish what facts and questions were put forward. Later changes can then be compared with the actual file rather than remembered informally.

A ruling does not replace annual bookkeeping or the need to support the tax computation. Continue maintaining asset-level income and expenditure records, and review material changes in rights, development and revenue.

Do not promise a guaranteed outcome or completion date merely because the checklist is complete. The authority can require clarification, and the relevance of any response depends on the facts and scope addressed.