IPBoxCyprus
Cyprus IP Box guides

Game licensing income under the Cyprus IP Box

Separate game code, artwork, brands and publisher payments before calculating IP Box relief. Reconcile royalties, recoupment and development costs.

IPBox Cyprus editorial team · Ebrovia Ltd
Updated:

Game software can fall within the qualifying software category, but a game business may also exploit artwork, music, brands and publishing services. Review the rights and income streams separately. A publisher statement or royalty label does not establish that every receipt is qualifying software profit.

A game is a bundle of assets and rights

A studio’s product may contain engine code, gameplay systems, art, music, narrative, trademarks and licensed characters. These elements can have different owners and legal treatment. Identify the qualifying software rather than assuming the whole entertainment product belongs to one tax category.

The Cyprus regulations include software among qualifying intangible assets and exclude marketing IP. Copyright protection for another type of work does not automatically place that work in the software category. A valuable game brand is therefore not interchangeable with the code that makes the game function.

Keep a rights map covering employee and contractor contributions, external engines and licensed materials. The studio’s ability to distribute a game may rely on licences rather than ownership of every component. The tax analysis should reflect the rights the company actually holds.

Read the publisher agreement alongside the revenue statement

A publisher may pay advances, royalties or a share of receipts after specified deductions and recoupment. It may also acquire rights, fund development or provide services. The contractual and accounting treatment of those flows needs to be established before the IP Box computation.

Do not equate cash received during a period with recognised revenue or net IP income. An advance, recoupment balance and later royalty statement can describe different stages of the commercial arrangement. Reconcile them under the treatment applicable to the contract.

Identify which rights are licensed or transferred and which activities the studio continues to perform. A payment described as a royalty can cover more than software rights, while a development milestone can require separate examination of the underlying transaction.

Review monetisation streams separately

A game can earn through downloads, subscriptions, in-app purchases, advertising, engine licences or merchandise. These streams may involve different assets and commercial functions. Do not apply one blanket conclusion merely because the same title appears in each contract.

StreamQuestion for the file
Game or engine licenceWhich software and other rights are licensed?
In-app purchasesWhat functionality or content is supplied?
AdvertisingHow does software contribute alongside audience and content?
Merchandise or brand licenceIs the income attributable to excluded marketing IP?
Bespoke development for a publisherWho owns the resulting software and what does the fee pay for?

Use a reconciliation rather than a headline sales number

Suppose a publisher report shows €1 million of player receipts, platform deductions and a contractual studio share. The studio should first establish its own recognised income under the arrangement. It should not assume that the entire player-receipts figure belongs in its IP Box model.

Next, identify the income attributable to the qualifying asset and relevant costs. Where the agreement includes separate brand or service elements, assess those components. Only then apply the supported nexus fraction to the appropriate net amount.

This example deliberately avoids inventing a universal publisher split or qualifying percentage. The agreement and operating facts determine the inputs. A transparent bridge is more useful than a promotional tax calculation built on gross game sales.

Track development by the relevant asset

A studio may work on several titles, a reusable engine and shared tools. Track qualifying development expenditure with enough detail to explain those relationships. Shared work should be allocated on a supported basis rather than counted in full for each title.

Separate own development, unrelated-party R&D, related-party outsourcing and acquired IP. Payments for art, audio, marketing or production services should not automatically enter software QE merely because they appear in the game’s budget.

Also review ownership of commissioned work. A paid contractor invoice does not replace the necessary rights analysis, and a third-party engine licence does not mean the studio developed the engine itself.

A studio-specific evidence checklist

Bring the legal, finance and production records together. The file should explain what the studio owns, what it earns and what development expenditure supports the claim.

  • Software asset and title or engine identifiers.
  • Employee, contractor and third-party rights records.
  • Publisher and platform agreements.
  • Revenue and cash-settlement reconciliations.
  • Supported treatment of mixed rights and income.
  • Asset-level development expenditure and shared-cost allocations.
  • Separate assessment of acquisitions and related-party work.

Revisit the position when rights change

A sequel, engine sale, publisher buyout or transfer of a title can change both rights and income. Preserve the earlier history and analyse the new transaction. A conclusion for recurring licence income does not automatically determine the treatment of an outright disposal.

Use a forecast based on the studio’s actual contract and cost mix. The full-nexus corporate rate is an illustration of the mechanism, not a guaranteed rate on a title’s gross sales.

Common questions

Does all game-related copyright qualify?

No automatic conclusion applies. Software is a qualifying category, but artwork, music, branding and other rights require their own classification.

Do publisher royalties automatically receive 3% tax?

No. Establish the rights and relevant net income, then apply nexus and the other conditions. The royalty label alone is insufficient.

Sources and scope

General information, with illustrative examples. Eligibility and tax treatment depend on the facts and applicable law; this article is not an individual tax opinion.