Qualifying Free Zone Person: The De Minimis Problem

The Invoice Nobody Classified

A Dubai free zone trading company raises an invoice in March. The customer is a mainland distributor, the goods leave a warehouse outside a Designated Zone, and the invoice goes out like every other invoice that month. Nobody pauses over it, because nothing about it looks unusual.

The following February, the auditors ask for the split between qualifying and non-qualifying revenue. The finance manager opens the sales ledger and starts reading invoice descriptions, trying to reconstruct a classification that was never recorded. The number that emerges sits slightly above 5% of total revenue.

At that point the company has not failed a test it could still pass. It failed it eleven months ago, and the consequence is not a one-year adjustment — it ceases to be a Qualifying Free Zone Person from the beginning of that tax period and for the following four tax periods. Five years at 9% instead of 0%, decided by a handful of transactions nobody classified at the time.

This article is about the part tax advice does not cover: how you capture that classification when the invoice is raised, and how you watch the ratio while you can still do something about it.

What the Rules Actually Say

A short, accurate summary, drawn from the Ministry of Finance’s own published decisions.

The de minimis requirement. Under Article 3 of Ministerial Decision No. 229 of 2025, a Qualifying Free Zone Person’s non-qualifying revenue in a tax period must not exceed 5% of total revenue, or AED 5,000,000, whichever is lower.

Read that last clause carefully. For a company with revenue below AED 100 million, the binding constraint is the 5%, not the AED 5 million — the absolute figure only becomes the limit for very large free zone businesses.

The consequence of failing. Under Article 5(2), a Free Zone Person that fails the de minimis requirement — or any other condition — ceases to be a Qualifying Free Zone Person from the beginning of the relevant tax period and for the following four tax periods.

The activities were restated in 2025. Ministerial Decision No. 229 of 2025 was issued on 28 August 2025, repeals Ministerial Decision No. 265 of 2023, and takes effect from 1 June 2023 — retroactively. Qualifying Activities under Article 2(1) include manufacturing and processing of goods, trading qualifying commodities, holding shares and securities for investment, owning and operating ships, reinsurance, fund management, wealth and investment management, headquarter and treasury services to related parties, aircraft financing and leasing, distribution of goods in or from a Designated Zone, logistics services, and ancillary activities. Excluded Activities under Article 2(2) include transactions with natural persons (with exceptions), banking, insurance, finance and leasing (each with carve-outs), and owning or exploiting immovable property other than certain commercial property transacted with a free zone person.

What goes into the calculation. Cabinet Decision No. 100 of 2023, Article 4(2) defines non-qualifying revenue as revenue from Excluded Activities, revenue from non-qualifying activities where the other party is a Non-Free Zone Person, and revenue from transactions with a Free Zone Person that is not the beneficial recipient. Article 4(3) excludes certain revenue from both sides, including revenue attributable to a permanent establishment and most immovable property transactions.

Techvaria is a Zoho implementation partner, not a tax adviser. Whether a specific transaction qualifies is a determination for your tax adviser and auditor. What follows is about recording and monitoring that determination, not making it.

Why the Penalty Is the Whole Story

Most compliance obligations are forgiving in shape: you file late, you pay, you move on. This one is not.

• It is retrospective by the time you see it. The test applies to a completed tax period. Measure it at audit and the breach has already happened — there is no correction window, because the thing to correct was a decision about which business to accept eleven months ago.
• It compounds. Not one year at 9% — five.
• It can turn on a small amount of revenue. At the 5% constraint, a company with AED 40 million of revenue can carry AED 2 million of non-qualifying revenue. One unusual contract, one mainland customer served outside a Designated Zone, one property transaction can move a company from comfortable to breached — and it is rarely the transaction anyone was watching.
• It is invisible to normal reporting. Revenue by customer, by product, by month — none of those answer the question the rule asks. Unless something in your system distinguishes qualifying from non-qualifying revenue, the number does not exist until somebody builds it by hand.

What Counts as Non-Qualifying Revenue

Three categories, and the second and third are where businesses get caught.

1. Revenue from Excluded Activities. The clearest case — transactions with natural persons outside the specified exceptions, banking and insurance, certain finance and leasing, and most immovable property exploitation.
2. Revenue from non-qualifying activities where the counterparty is a Non-Free Zone Person. The common one. The same activity can be qualifying or not depending on who you sold to, which makes counterparty status part of your revenue data rather than part of your CRM notes.
3. Transactions with a Free Zone Person who is not the beneficial recipient. The longest tail. Selling to a free zone entity that is passing goods or services through to someone else does not get you the treatment its status suggests, and establishing beneficial recipient status requires evidence gathered at the time — not during an audit two years later.

The practical consequence. Each revenue transaction needs to carry the activity type, the counterparty’s free zone or mainland status, whether they are the beneficial recipient, and whether a Designated Zone is involved. None of that is on a standard sales invoice, which is why so few companies can produce the figure on demand.

The Measurement Problem

• Classification has to be made once, at the right moment — when the transaction is created, by someone who knows the facts. A year later, the person reconstructing it from an invoice description is guessing, and documenting a guess as a tax position.
• The ratio is only useful while it can still change. Knowing in February that you were at 5.3% last year is a tax computation. Knowing in August that you are at 4.1% and trending upward is a business decision — you can decline a contract, restructure a delivery, route a transaction differently.
• Revenue mix moves without anyone deciding it should. A strong quarter in one line, a single large mainland contract, a change in how goods are routed. The ratio shifts as a by-product of commercial activity, which means nobody owns it unless somebody is made to.
• The evidence has to exist, not just the number. If the FTA or your auditor asks why a transaction was treated as qualifying, “because it was” is not an answer. A classification recorded at the time, with the counterparty status and the basis alongside it, is.

Building Revenue Classification Into Zoho Books

The problem is that the data the calculation needs does not exist anywhere in structured form. The capability is Zoho Books holding it as part of the transaction. The outcome is a ratio available continuously rather than reconstructed annually.

• Classify at the point of invoicing, as a mandatory field — qualifying, non-qualifying, or excluded from the calculation. A field that can be left blank will be left blank, and a blank classification is the same as none.
• Hold counterparty status on the customer record: free zone or mainland, which free zone, whether a Designated Zone is relevant, and whether the entity is the beneficial recipient where established. Capturing this once and inheriting it onto transactions removes most per-invoice judgement — and surfaces the exceptions, which are the ones needing attention.
• Use item-level classification where qualifying status follows the activity rather than the customer, so the invoice inherits it.
• Separate the excluded revenue. Cabinet Decision No. 100 of 2023 removes certain revenue from both sides of the calculation; treating that as a third classification keeps the computation defensible.
• Attach the basis, not just the label. A short structured note — activity, counterparty status, beneficial recipient evidence — turns a classification into something that survives questioning.
• For multi-entity groups, keep this at entity level. Each free zone entity has its own de minimis position.

Monitoring the Ratio in Zoho Analytics

Classification gives you the data. Monitoring converts it into protection.

• The running ratio — non-qualifying revenue as a percentage of total, year to date, per entity, refreshed as transactions post. This belongs on the finance dashboard monthly, not in a year-end computation.
• Headroom in dirhams, not percentages. “We are at 3.8%” is abstract. “We can take another AED 1.4 million of non-qualifying revenue this period” is a figure a commercial director can use when deciding whether to accept a contract.
• Threshold alerting set at 3.5% or 4% — well below the limit, so there is room to act. An alert at 4.9% tells you about a decision you can no longer make.
• Forward projection. Blending booked revenue with contracted and pipeline revenue projects the year-end ratio rather than reporting the position to date. That projection is what makes the number a planning input.
• The classification exception report — overridden classifications, missing customer status, empty basis notes. This is the data quality control that stops a confident ratio being built on incomplete input.

Catching It Before the Invoice Exists

The best place to catch a de minimis problem is before the sale is agreed.

• Capture counterparty status at quotation. If free zone or mainland status and beneficial recipient information are recorded in Zoho CRM when the opportunity is created, the classification is settled by the time an invoice is raised — and settled by the salesperson who actually spoke to the customer.
• Flag at-risk opportunities in the pipeline. A commercial team that can see the headroom will sequence deals sensibly across periods. One that cannot will unknowingly spend it on a low-margin contract.
• Make it a question, not an assumption. Asking a prospect about entity status and the end recipient is a normal commercial conversation in the UAE. Not asking is how a transaction with a free zone intermediary ends up misclassified.

Where a bespoke evidence register is genuinely justified — a complex group, heavy beneficial-recipient documentation, a structured approval chain on overrides — Zoho Creator can hold that alongside Zoho Books. For most companies, custom fields and disciplined process will do.

What Zoho Cannot Do for You

This section determines whether your project succeeds, so it matters more than the three above it.

• There is no QFZP module. Zoho does not ship a free zone tax feature that calculates your de minimis position automatically. You are building a revenue classification data model plus reporting, configured for a specific UAE requirement.
• The software cannot classify your revenue. It can hold a classification, require one, make it auditable, and calculate the ratio. Whether a transaction is qualifying is a tax determination made by your adviser and tested by your auditor. Automating the capture of a determination is not the same as making it.
• It does not file anything. Your return goes through the FTA’s own channels.
• De minimis is one condition among several. QFZP status also requires adequate substance, audited financial statements and arm’s length treatment of related party transactions. Monitoring the ratio tells you nothing about those.
• The rules change. Ministerial Decision No. 229 of 2025 replaced the 2023 decision and applied retroactively. Your classification logic reflects a regulatory position at a point in time and needs reviewing when that position moves.
• Garbage in, confident garbage out. If classifications are entered carelessly to clear a mandatory field, you will have a precise ratio built on nothing. The exception report exists for this reason, and someone has to read it.

Dubai and UAE Considerations

Designated Zones are not all free zones. Distribution of goods in or from a Designated Zone is a Qualifying Activity; the same distribution from a free zone that is not a Designated Zone is a different question. If your position depends on this, your warehouse and delivery routing is part of your tax position and needs to be visible in your system.

Dual-licensed structures. Many Dubai groups run a free zone entity alongside a mainland one. Each has its own position, inter-entity transactions need classifying, and the entities should be properly separated in Zoho Books rather than combined with a department field.

VAT classification is not tax classification. Different questions, different rules. Reusing a VAT field for de minimis classification is a shortcut that produces wrong answers.

E-invoicing is arriving alongside this. As UAE e-invoicing requirements progress, invoice data becomes more structured and more externally visible. A business that already classifies revenue cleanly is better placed for both; one that does not is solving two data problems at once.

Implementation: A Realistic Sequence

1. Get the tax determination first. Your adviser maps your revenue streams against the current Qualifying and Excluded Activities and documents the logic. This is the specification; nothing is configured before it exists.
2. Measure where you are today. Classify the current period manually to establish the baseline — usually the moment the project justifies itself.
3. Design the data model: classification field, customer status fields, beneficial recipient flag, Designated Zone indicator, basis note.
4. Configure Zoho Books — custom fields, defaults inherited from customer and item, validation so classification cannot be skipped.
5. Remediate the customer master. Tedious, and it removes most of the ongoing judgement.
6. Build the running ratio and headroom figure in Zoho Analytics, per entity.
7. Set the alert deliberately low and name an owner.
8. Push classification upstream into CRM so it is captured at quotation.
9. Build the exception report and schedule someone to read it monthly.
10. Review annually with your adviser, and immediately on any change to the decisions.

Best Practices

1. Get the tax determination documented before any configuration. You are encoding a position, not inventing one.
2. Make the classification field mandatory.
3. Hold counterparty status on the customer record so transactions inherit it.
4. Record the basis, not just the label.
5. Track per entity. A group ratio protects nobody.
6. Express headroom in dirhams so commercial teams can use it.
7. Set the alert at 3.5% or 4%, where there is still time to act.
8. Project forward, including pipeline.
9. Capture classification at quotation, by the person who knows the customer.
10. Read the exception report monthly.
11. Keep VAT and corporate tax classification separate.
12. Re-check the logic when the decisions change — as they did in 2025, retroactively.

Common Mistakes

• Measuring once a year at audit. By then the breach is permanent.
• Assuming the AED 5 million figure is your limit. Below AED 100 million of revenue, the 5% is what binds you.
• Classifying from invoice descriptions after the fact. That is a reconstruction, not a record.
• Treating counterparty status as a note rather than data. It is part of the calculation.
• Ignoring the beneficial recipient question. Selling to a free zone pass-through is not the same as selling to a free zone customer.
• Running one ratio across a group. Each entity has its own status.
• Reusing the VAT classification. Different rules, different answers.
• Setting the alert at 4.9%. By then there is nothing left to decide.
• Leaving the ratio unowned. It moves with commercial activity that nobody connects to tax status.
• Configuring before the tax determination exists. You automate a guess.

An Illustrative Scenario: A DMCC Trading Company

A composite illustration built from patterns common in the UAE market. It is not an account of a specific named client.

Consider a DMCC-registered trading company distributing industrial components, with a Designated Zone warehouse, a mix of free zone and mainland customers, and a small mainland service entity alongside it.

Before

Revenue was invoiced from Zoho Books with no classification attached, and customer records held billing address and payment terms but nothing about entity status. The de minimis position was produced once a year by the finance manager, who exported the sales ledger and classified it line by line over several days. The prior period had come out at roughly 4.2% — comfortable enough that nobody treated it as a risk, and arrived at late enough that nobody could have acted if it had not been.

What Was Implemented

The tax adviser mapped the revenue streams against the current decisions and documented which activity and counterparty combinations produced qualifying revenue, including the Designated Zone distinction and the beneficial recipient question. That document became the specification.

Zoho Books was then configured with classification as a mandatory invoice field defaulting from customer and item, and the customer master was remediated so every active customer carried entity status and a beneficial recipient flag where established. Zoho Analytics produced a running ratio per entity, headroom in dirhams, a forward projection including pipeline, and a monthly exception report. The alert was set at 3.5%. Classification capture was pushed into Zoho CRM so entity status was asked at quotation.

After Two Quarters

The outcome that mattered was a conversation in month seven, when the projection showed the ratio heading toward the threshold on contracted work. The commercial director could see the headroom in dirhams and sequenced a large mainland delivery into the following period — a decision available only because the number existed in month seven rather than month nineteen.

The classification exercise also surfaced a recurring arrangement with a free zone customer where goods were plainly moving on to a mainland end user, treated as qualifying for two periods on an assumption nobody had tested. It went to the tax adviser, which is where it belonged.

Industry Use Cases

• Trading and distribution. The largest free zone population in Dubai and the most exposed, because qualifying status depends on counterparty, goods routing and Designated Zone involvement — all of which change transaction by transaction. See trading and distribution solutions.
• Logistics and freight. Logistics services are a Qualifying Activity, but the boundaries around ancillary services and mainland counterparties need careful classification. See logistics solutions.
• Manufacturing and processing. Both are Qualifying Activities, so the risk usually sits in adjacent revenue — service contracts, spares to mainland customers, equipment hire. See manufacturing solutions.
• Holding, headquarter and treasury structures. Holding securities for investment and headquarter and treasury services to related parties are Qualifying Activities, with arm’s length requirements applying alongside. See IT services ERP for group entities running shared services.