White-label software and the Cyprus IP Box

Identify which side of the white-label arrangement you occupy

The term white-label can describe a developer allowing partners to sell software under their own names, or a distributor buying access to an external platform and placing its own brand on it. These arrangements can look similar to customers while giving the businesses different rights and income.

Map the software owner, platform operator, customer contracting party and any intermediary. Identify who develops the code, who can modify it, who controls exploitation and what each entity is paid for. The logo on the login screen is not a reliable substitute for that map.

The Cyprus IP Box applies through its qualifying-asset, income and nexus rules. It does not provide a separate automatic entitlement for white-label businesses or require every commercially branded product to be treated the same way.

When the company licenses software it developed

If the company owns or economically owns qualifying software and licenses it to partners, the licence income can be analysed under the normal IP Box provisions. Establish the asset, rights, net income and supported expenditure history.

Check what else the partner receives. The agreement may include hosting, support, custom development or brand rights alongside software access. Those components should be reviewed rather than assumed to have identical treatment.

Partner-specific customisations also need tracking. Determine whether the company retains rights, whether the work improves the core asset or creates another asset, and how the relevant costs and income are assigned. A white-label contract can change those facts from one partner to another.

When the company rebrands someone else’s platform

A reseller may have permission to market and provide access to external software without owning the underlying technology. The right to change colours and branding does not automatically establish ownership of a qualifying software asset.

Review whether the company develops a separate original integration or application layer. That contribution may require its own assessment, but it does not transfer ownership of the provider’s whole platform. Identify the rights and income relevant to the company’s actual asset.

Provider charges, resale margins and development expenditure should remain distinct in the records. Do not describe the entire platform fee as the company’s own R&D or treat every customer receipt as income from software the company created.

A contract comparison

Company A develops a scheduling platform and grants partners rights to offer access under their brands. Company B buys access to that platform and resells it with implementation services. Both advertise a white-label solution, but their IP Box assessments begin from different positions.

Company A needs to substantiate its qualifying asset, development history and net licence or embedded income. Company B needs to identify what rights and any original software it has, and distinguish resale or service activity. Neither company should infer its tax result from the other’s marketing claim.

If B later develops a substantial proprietary module, review that module separately. The relevant question is the actual asset and its contribution to income, not whether the business can now describe itself as a developer.

Review the rights and income clauses together

Read the development and commercial agreements as one operating model. The rights clause should match what is delivered and how the parties earn income. Material inconsistencies should be resolved before relying on the tax calculation.

• Who owns or economically owns the underlying software?
• What rights does each partner receive, retain or transfer?
• Who owns customisations and later improvements?
• Are software, brand, hosting and service components distinguishable?
• How are customer income and provider charges recorded?
• Which taxpayer incurred the relevant development expenditure?
• Are any parties related, requiring separate nexus and pricing analysis?

Keep the analysis current as the model evolves

White-label businesses can move from simple resale to original development, or outsource increasing parts of their platform. Update the asset and expenditure records when the operating model changes. Historic acquisition or related-party costs should not disappear because the website now uses a different description.

Use the supported tax model to forecast the actual mix of software and service profit. Full-nexus examples are useful for understanding the mechanism, but a reseller or mixed provider should not present them as a guaranteed rate on its whole business.

Before an investor or buyer review, assemble the provider terms, partner contracts, rights chain and asset-level calculations. A clear explanation of the arrangement is more useful than a claim that the white-label label itself proves eligibility.