Cyprus iGaming transfer pricing: map related-party dealings

Which transactions should be mapped?

The Cyprus Tax Department’s transfer-pricing legislation directory identifies the relevant statutory framework and documentation provisions. Begin with the actual transactions rather than a preferred margin or tax outcome.

List software royalties, development services, management support, loans, guarantees and cost allocations where relevant. Identify the contracting parties, amounts, purpose and evidence of performance. Keep operating-company player revenue separate from intercompany service income.

What factual analysis is needed?

Explain what each company actually contributes. Legal ownership and invoices are part of the evidence, but the analysis also needs the people making decisions and performing work.

• Who develops, maintains and controls the software?
• Who determines product strategy and budgets?
• Who manages commercial and development risks?
• Which entity contracts with and supports players?
• Who provides funding and on what terms?
• What comparable information is available for the transaction?

How should agreements match the business?

Draft agreements around the services and rights actually provided. Describe deliverables, responsibilities, charging mechanics and records. An agreement written after the fact should not pretend that an undocumented service occurred.

For example, a Cyprus developer may supply engineering work to a licensed operator. The evidence should show the work performed, relevant costs and pricing analysis. A percentage of the operator’s gaming revenue is not automatically appropriate merely because it is easy to calculate.

How do documentation thresholds fit?

Determine the applicable year, transaction categories, related-party tests and current documentation requirements from the Tax Department materials and relevant advice. Do not reuse a historic threshold without checking for changes.

A documentation threshold should not be confused with a general exemption from considering the pricing of a transaction. Keep the substantive pricing analysis and the formal filing or documentation obligations as separate checklist items.

What should the annual review cover?

Reconcile the agreements, invoices, ledger and actual conduct. Investigate material differences from the expected transaction values or functions. Update the analysis when the business changes rather than merely renewing last year’s document.

Coordinate the work with IP ownership, nexus calculations and corporate residence review. Those topics overlap in their facts but have different tests. A favourable conclusion on one does not automatically resolve the others.