Free Zone Software Licensing to Mainland: Qualifying Income, or 9%?

Is free zone software licensing to a mainland company qualifying income?

Usually not — but the common reasoning is wrong even where the conclusion is right. Licensing software is exploitation of intellectual property, which is an excluded activity for a Qualifying Free Zone Person. Excluded activities are non-qualifying whoever the customer is, so “the customer is on the mainland, therefore 9%” reaches the right destination by the wrong road.

That distinction is not academic. If you believe the customer's location decides it, you will assume that moving the same licence to a free zone customer produces 0% — and it does not. You will also miss the one route that genuinely can deliver 0% on mainland software revenue: the Qualifying Intellectual Property carve-out, calculated under the modified nexus approach, which does not care where the customer is at all.

The framework sits in Federal Decree-Law No. 47 of 2022, with Qualifying Income determined by Cabinet Decision No. 100 of 2023 and the Qualifying and Excluded Activities listed in Ministerial Decision No. 265 of 2023. Those replaced Cabinet Decision No. 55 of 2023 and Ministerial Decision No. 139 of 2023. Much of the free zone commentary online still cites the superseded instruments, or misattributes the activities list entirely — worth checking before you rely on a position paper. Our corporate tax consultants in Dubai re-paper this for tech clients regularly, and the wider framework sits in our UAE corporate tax service.

What actually makes income qualifying for a QFZP?

Cabinet Decision No. 100 of 2023 sets out four routes to qualifying income, and the one most relevant to a software business is the one usually left off the list. Income can qualify through a free zone counterparty, through a listed qualifying activity, through Qualifying Intellectual Property, or as other income where the de minimis requirements are met.

Two of those routes carry an override. Income from transactions with other Free Zone Persons qualifies except where it arises from an excluded activity — which is precisely what catches IP licensing. And income from non-free-zone counterparties qualifies only in respect of listed qualifying activities that are themselves not excluded activities.

Notice what is absent from the qualifying activities list: software development, software licensing, IT services, consulting and SaaS all appear nowhere. The list runs to manufacturing, processing, distribution in or from a Designated Zone, logistics, commodity trading, ship operation, aircraft leasing, holding of securities, regulated fund and wealth management, reinsurance, and headquarter and treasury services to related parties. A technology business is not obviously on it.

Run the analysis in a fixed order rather than starting from the customer. The sequence itself is what stops the wrong rule being applied first:

1. Characterise the transaction — Does the contract grant rights in intellectual property, or supply a hosted service? The two follow different routes.
2. Test against the excluded activities list — Exploitation of IP is excluded, so a licence is non-qualifying whether the customer is in a free zone or on the mainland.
3. Identify Qualifying Intellectual Property — Patents, copyrighted software and functionally equivalent protected rights; trademarks and marketing intangibles are out.
4. Run the modified nexus calculation — Qualifying expenditures plus up-lift over overall expenditures, applied per IP asset, with the expenditure tracking documented.
5. Classify service income separately — For hosted services the ordinary counterparty test applies: 0% to a free zone beneficial recipient, 9% to a mainland customer.
6. Run the de minimis calculation — Non-qualifying revenue below the lower of 5% of total revenue or AED 5 million, documented period by period.

Why is software licensing an excluded activity rather than merely non-qualifying?

Because Ministerial Decision No. 265 of 2023 lists the ownership or exploitation of intellectual property assets as an excluded activity, subject only to the Qualifying Intellectual Property carve-out. The distinction matters: an excluded activity is non-qualifying no matter who the counterparty is, whereas ordinary non-qualifying income can become qualifying simply by dealing with a Free Zone Person.

Granting a licence over software, in exchange for a licence fee or royalty, is exploitation of an IP asset in the ordinary sense. So the exclusion applies at the point the contract grants rights in the code, not at the point the invoice is addressed. That single structural fact is what breaks the “change the customer, change the answer” reasoning that works reasonably well for goods and services.

The immovable property line is the closest analogue, and it is worth reading across: there, a carve-out restores 0% where both the asset and the counterparty tests are met. For IP, the carve-out works differently — it tests the asset and the expenditure behind it, and ignores the counterparty entirely. The free zone warehouse rental guide sets out how the property version works.

What is Qualifying Intellectual Property, and does software count?

Qualifying Intellectual Property covers patents, copyrighted software, and rights functionally equivalent to a patent that are legally protected and subject to registration or approval. Marketing-related intellectual property — trademarks, brand names and similar assets — is expressly excluded. So yes, software can qualify, which is exactly what the standard “software to mainland equals 9%” answer misses.

Qualifying does not mean automatic. Two things have to be true. The asset has to fall within the definition, which turns on legal protection rather than commercial value. And the expenditure behind it has to have been incurred by the free zone person in a way the nexus formula rewards — self-funded research and development, or development outsourced to unrelated parties, rather than IP simply acquired or developed by a related party abroad.

That second limb is where most claims thin out. A free zone entity that licenses in a group product and sub-licenses it to UAE customers has very little qualifying expenditure of its own, so even where the asset is copyrighted software the nexus fraction will be small. A genuine product company with a development team in the zone is a different picture entirely.

How does the modified nexus approach calculate qualifying IP income?

Qualifying income from an IP asset equals qualifying expenditures plus up-lift expenditures, divided by overall expenditures, multiplied by the overall income from that asset. Up-lift is 30% of qualifying expenditures, capped so the numerator can never exceed overall expenditures. The calculation is done per asset, not across the business.

The logic is the OECD's: relief follows the research and development you actually funded. Qualifying expenditures are the R&D costs incurred by the free zone person itself, including work outsourced to unrelated parties. Costs of acquiring the IP, and R&D outsourced to related parties, sit in overall expenditures but not in the numerator — which is what dilutes the fraction for licence-in structures.

Two practical consequences follow. First, expenditure tracking has to be built per IP asset from the start; reconstructing it after the fact is close to impossible and an FTA reviewer will treat an unsupported fraction as zero. Second, moving development to a related party offshore reduces the fraction even where the commercial logic is sound — which makes this a transfer pricing question as much as a corporate tax one. See our UAE transfer pricing service.

Does licensing the software to a free zone customer change the answer?

No — and this is the single most common error in the standard analysis. Income from transactions with other Free Zone Persons is qualifying except where it arises from an excluded activity. Exploitation of intellectual property is an excluded activity. So the same licence, sold to a free zone customer instead of a mainland one, is treated identically.

The “change the customer, change the answer” framing does hold for many transaction types — it is exactly right for services, and it is the deciding factor for commercial property leases. It is simply the wrong lens for IP, because the exclusion attaches to the activity rather than the counterparty. Applying it here produces a false sense of a planning option that does not exist.

Is it a software licence or a SaaS service — and does the difference matter?

It matters a great deal, because the two follow different routes through the rules. A contract granting rights in intellectual property is exploitation of that IP, caught by the exclusion. A hosted subscription where the customer buys access to a service, with no rights in the code, may be characterised as a service — in which case the customer's status becomes decisive again.

If the supply is genuinely a service, the ordinary test applies: qualifying where the counterparty is a Free Zone Person and the beneficial recipient of the service, non-qualifying where the customer is on the mainland, because IT and software services are not on the qualifying activities list. So for a SaaS business, the mainland customer really is the deciding fact — just not for the reason the licence analysis suggests.

Characterisation follows the contract terms and the commercial substance, not the label on the invoice. A “licence agreement” that in substance provides hosted access, or a “subscription” that in substance grants perpetual rights in the code, will be looked at for what it actually does. Review your standard contract templates before you build a tax position on the heading.

What does AED 10 million of non-qualifying software revenue actually cost?

Not AED 900,000 — corporate tax is charged on taxable income, not gross revenue, and a Qualifying Free Zone Person gets no AED 375,000 band. Applying 9% to revenue overstates the liability by whatever your cost base is, which for a software business is usually most of it.

The AED 375,000 point catches people out because it is genuinely different for QFZPs. A standard mainland taxable person pays 0% on the first AED 375,000 of taxable income and 9% above. A QFZP pays 9% on the whole of its non-qualifying taxable income, from the first dirham, because the band sits in a provision that applies to taxable persons other than QFZPs.

Cost attribution is the work here. Where a business has both qualifying and non-qualifying income streams, shared costs have to be allocated on a reasonable and consistent basis, documented, and applied the same way year on year. Model the outcome before year end with the UAE corporate tax calculator, and keep the allocation methodology in the file.

Does AED 10 million of non-qualifying revenue break the de minimis threshold?

Yes — automatically, whatever your total revenue is. The threshold is the lower of 5% of total revenue or AED 5 million, so the AED 5 million limb caps it absolutely. AED 10 million of non-qualifying revenue is double the maximum possible headroom, which means Qualifying Free Zone Person status is lost for that tax period and the four subsequent tax periods.

This is the part the AED 10 million scenario usually misses. Calmly applying 9% to the non-qualifying slice assumes the rest of the income is still sitting at 0% — but once de minimis is breached there is no 0% left. Every dirham of taxable income is taxed at 9%, for five tax periods, and the exposure is an order of magnitude larger than the tax on the software revenue itself.

Two carve-outs soften the calculation without solving this case. Revenue attributable to a domestic or foreign permanent establishment, and revenue from free zone immovable property that fails the commercial property exception, are excluded from both sides of the fraction. Software licence income is neither, so it counts in full.

The practical implication for a free zone technology business is that the qualifying income analysis is a monitoring obligation, not an annual one. If a growing share of revenue is non-qualifying licence income, you will cross AED 5 million long before anyone looks at the return — and by then the tax period is closed and a five-year consequence is locked in.

What other QFZP conditions must a free zone software company meet?

Qualifying income is one condition of five, and all of them must hold throughout the tax period. A software business with a perfectly documented nexus fraction still loses the 0% rate if it has no audited financial statements, no transfer pricing documentation, or inadequate substance in the zone.

One point circulates widely and needs correcting: there are no prescribed headcount or expenditure thresholds in the corporate tax substance test. That numeric framing is a hangover from the Economic Substance Regulations, which were abolished for financial years ending after 31 December 2022. The test asks whether substance is adequate — core income-generating activities undertaken in a free zone, with adequate assets, an adequate number of qualified employees and adequate operating expenditure, judged on the facts.

For an IP-owning entity, substance and nexus point the same way. The activities that generate the income — development, product management, technical decision-making — need to happen in the zone, and the expenditure behind them is exactly what feeds the nexus numerator. A shell entity holding group IP fails both tests at once.

Condition four bites hardest on group IP structures. Intra-group licence fees and development recharges have to be at arm's length and documented, and an adjustment can move income into a period you have already filed — our UAE transfer pricing service covers the benchmarking, and our free zone audit services cover condition five.

So a small free zone software company below AED 3 million of revenue chooses between the two regimes rather than stacking them — the QFZP 0% regime or an Small Business Relief election. And a free zone entity inside a multinational group at or above the Pillar Two threshold falls within the UAE domestic minimum top-up tax (DMTT) for financial years starting on or after 1 January 2025, bringing the effective rate to 15% — the scope test is in our guide to UAE DMTT and Pillar Two.

What documentation supports a qualifying IP or free zone software income claim?

Evidence of the asset, evidence of the expenditure behind it, and evidence of who each customer is. A nexus fraction without expenditure tracking is an assertion, and an FTA reviewer is entitled to treat an unsupported fraction as zero — which moves the whole of the licence income to 9%.

Set the tracking up per IP asset before the development starts, not after the revenue arrives. Retrospective allocation of a development team's time across three products, two of which shipped and one of which did not, is the kind of exercise that consumes weeks and still fails to convince.

A practical tip: add a product or IP-asset dimension to your chart of accounts, and a free zone or mainland flag to your customer master. Together they turn the qualifying income split and the nexus calculation into reports you run monthly rather than reconstruct annually. Our accounting and bookkeeping service configures ledgers this way for free zone technology clients.

What does free zone corporate tax filing cost for a software company?

Corporate tax registration is AED 199, returns run from AED 249 to AED 999 depending on complexity, and deregistration is AED 399. A return carrying a nexus calculation, a cost allocation methodology and a de minimis schedule sits at the upper end — the work is in the analysis, not the form.

Registration is not optional and is not tied to profit. Every UAE juridical person is a taxable person and must register and file, and a company incorporated on or after 1 March 2024 must register within three months of incorporation. Failing to register carries an AED 10,000 penalty whether or not the company has traded.

One VAT note while you are here, because software businesses conflate the two regimes: a licence or subscription supplied to a mainland UAE customer is generally standard-rated at 5% VAT, and free zone status does not change that. Exports of services to overseas customers may be zero-rated where the conditions are met. That is a separate analysis from the corporate tax classification, handled through our VAT return filing service.

For the wider framework see our UAE corporate tax guide for businesses, and compare zones in the UAE free zone comparison tool.