Choosing your business activities: how UAE registers actually work

Each licensing authority maintains its own register and numbers it its own way. The code is an address inside that register, and it is not a national identifier that every authority answers to. There is one real qualification to that, and it is worth knowing rather than glossing: several UAE registers publish against the shared national activity numbering — the seven-digit codes — and where two of those lists carry the same seven digits, they usually are the same activity. Dubai mainland, IFZA and RAKEZ's non-free-zone list all number that way, which is why Accounting & Bookkeeping is 6920003 in all three and Aviation Consultancy is 5229012 in all three. Across our capture, 1,314 distinct seven-digit codes appear in two or more registers for that reason.

The free zones running proprietary schemes number independently, and there a matching code means nothing at all. DMCC writes 7412-01, Ajman Free Zone writes AM-04134, RAKEZ's free-zone list writes 70100-06 or RAKEZ /2017/20, Meydan and Shams and SPC Free Zone write dotted four-digit codes. Nothing in those schemes is coordinated with anything in the others, and a coincidence of digits between two of them is a coincidence. This is an important consideration when deciding between compare free-zone and mainland routes company formation.

The clearest demonstration is an activity that exists under one name in several registers at once. Virtual Assets Advisory Services appears in three of the registers we capture, and it carries a different code in each: 6599-89 at DMCC, 6920010 at IFZA, 6619.82 at Meydan. Those are not three renderings of one number; they sit in three different numeric families. Any reasoning of the form 'my other activities start with 69, so this one will group with them' holds only inside the register you are actually applying to.

Telecommunications Equipment Trading shows both halves at once across five registers: 5152-11 and 515211 and 4741.98, which are three unrelated schemes, and 4741021 in two registers, which is one shared national code appearing where you would expect it to. Insurance Consultancies appears under five distinct codes across six registers on the same pattern. The name travels. The code travels only between the lists that share the national numbering, and never on your say-so. Understanding how a trade licence works is essential for navigating these complexities.

Some registers do expose a recognisable statistical classification alongside their own code. Only Ajman Free Zone labels the classification as ISIC in its published list, which is why a row's permission scope there reads in the form 'Licence type: Commercial; ISIC 4662005' — the licence family, then the classification. The number it prints is not a separate lineage: Ajman's Accounting & Bookkeeping carries ISIC 6920003, which is the same national code Dubai mainland and IFZA publish as their primary code for that row. No other register we capture carries an ISIC value at all, and Ajman's own field is not populated on every row — 1,562 of its 1,689. Do not assume the classification is there until you have seen it.

Permission scope is the part people skip, and it is the part that decides whether an invoice is covered. It is the combination of two things the register states: the licence family the row belongs to, and the classification of the row itself. For comprehensive guidance, consider consulting Velarozone's advisers for expert advice.

The family answers what kind of licence this is — trading, service, industrial, professional and so on in the authority's own vocabulary. The classification answers which specific work inside that family you may perform. Neither on its own is the permission. A licence in a Services family does not permit all services; it permits the listed rows.

Two practical rules follow, and both are unglamorous. First, an activity that describes what you sell is worth more than one that describes what you are — 'Accounting & Bookkeeping' is a scope, 'business consultancy' as a self-description is not. Second, the wording on your licence is the register's wording, not yours: if you would not recognise your own work in the row's text, a bank compliance officer reading your licence will not recognise it either.

Where a register publishes long descriptive rows — and some do, running to several lines listing exactly which goods or services are covered — read the whole row. The qualifying clause at the end is doing real work.

The licensing authority is often not the only body whose permission an activity needs. Many rows carry a note naming another regulator, and our capture records that note verbatim where the register publishes it.

The rows below are real examples, quoted as the register writes them. Notice how much information is packed into the parenthetical: several registers state not only who must approve, but when — before the licence is issued, or after it.

Where a register states the timing, it is telling you something about sequence rather than about difficulty. A pre-licence approval sits on the critical path: the licence does not exist until the other regulator has said yes, so the whole formation waits on a body that has its own queue and its own criteria. A post-licence approval does not block issuance — it blocks lawful operation. The licence arrives, the company exists, and the activity still cannot be performed until the second permission lands.

The post-licence case is the one that catches people, because everything looks finished. A licence in hand reads as completion, and the undertaking you signed about approvals still outstanding is easy to forget you signed. Where a licensing regime deliberately separates issuance from the permits needed to conduct an activity — as Dubai's Executive Council Resolution No. (5) of 2024 does — that gap is a designed feature of the process, not an oversight.

Registers that record timing record both kinds in quantity. In our August 2026 capture, IFZA's rows carry 168 approval notes marked before issuance against 75 marked after; SPC Free Zone's carry 135 marked pre-licence against 304 marked post-licence; Shams's carry 75 pre against 198 post. The point is not the ratio at any one authority — it is that both cases are ordinary, and that the timing is a thing you can find out before you apply.

This is the most important sentence on the page. In our capture, the proportion of rows carrying a published external-approval note ranges from most of the register to none of it: Dubai mainland's list carries a note against 1,797 of 2,277 rows; Meydan's against 891 of 2,230; DMCC's against 344 of 973; IFZA's against 244 of 824; Shams's against 280 of 1,001; SPC Free Zone's against 441 of 1,982. Two registers we capture — Ajman Free Zone's and RAKEZ's — publish no approval note against any row in the source we read.

Those are differences in what each list publishes. They are not differences in how regulated each place is, and reading them the second way is how an application gets refused. A blank field means our source is silent, and silence is not clearance.

The registers prove this against themselves. Insurance Consultancies appears in six of the registers we capture. Five of them name the Central Bank against the row, in five different renderings. The sixth records nothing at all — the same activity, the same country, the same regulator, and a blank field. Telecommunications Equipment Trading behaves identically: four registers name the telecommunications regulator, one records nothing.

So treat the approval column as a positive signal only. Where a register names a regulator, believe it. Where it does not, the question is still open, and it is answered by asking the licensing authority which approvals your specific row attracts — in writing, before you pay.

There is no canonical national activity name that every authority uses. There is a common vocabulary, drawn loosely from international classification and from decades of shared practice, and then there is each register's own rendering of it.

Management Consultancies appears under that exact name in four of the registers we capture, carrying three distinct codes between them — AM-04134 at Ajman Free Zone, 7414-05 at DMCC, and 7020003 at both Dubai mainland and IFZA, which share the national numbering. A near-identical Management consultancy activities appears in three more, coded 7020.00, 7020 and 7020. Seven registers, one idea, five codes and two spellings — and the second of those counts is case-folded: Meydan publishes 'Management Consultancy Activities' title-cased where Shams and SPC Free Zone publish it lowercase, so a search that respects capitalisation finds three renderings, not two.

The regulator names vary too, in the same field that is supposed to tell you who must approve. The telecommunications regulator appears in our capture as 'Telecommunications and Digital Government Regulatory Authority', as 'TDRA', as 'TDGRA' and as 'Telecommunications And Digital Government Regulatory Authority (TDRA)' — four renderings of one body, because each register wrote its own list.

Three habits follow from this. Search a register by concept and by several spellings rather than by the phrase your last adviser used. Never carry a code across from another authority's list. And when a row is proposed to you, ask for the exact name and code that will print on the licence, because that string — not the summary in the email — is what a bank, a customer and a regulator will read.

Amendment fees are not a penalty. They exist because changing a licence is a fresh transaction: the register entry is altered, a new licence is issued, and depending on what changed the constitutional documents may need re-notarising and re-translating. Every authority we track charges something for it, and the charge is the authority's, on its own schedule.

Rejections have their own arithmetic. An application naming a row whose external approval was never obtained does not fail cheaply — it fails after the preparation, sometimes after the attestation done abroad, and the second attempt repeats whichever steps have expired. Nothing in that sequence is refunded because the work was performed.

This page publishes no figures for either, deliberately. Both are authority-specific and activity-specific, and a number here would be a guess dressed as a fact. What is worth knowing is the structure: the cost of getting the activity wrong is always larger than the cost of confirming it, because confirming it is a question and fixing it is a transaction.

The corollary is a scheduling one. Pin the activity down before the trade name, before the workspace and before any payment, because every one of those follows from it. An activity settled late is an activity settled after other people's clocks have started.

The instinct is to fit everything onto one licence, and it is usually right — one renewal, one file, one set of dates. It stops being right at three specific points, and all three are visible before you apply.

The first is a hard structural stop. Where a register groups by licence type, an activity from a different type is not an addition at all; the authority issues a separate licence. DMCC's published schedule states this plainly: activities from a different licence type — Service, Trading or Industrial — require a new licence. No allowance covers that, because it is not a counting question.

The second is the standalone row. Some activities cannot share a licence with anything, whatever family they sit in. DMCC's schedule gives single-family office, real estate and DGCX as its examples. If one of your intended rows is standalone, the shape of the answer is already two entities or one narrower business, and no amount of negotiating changes it.

The third is arithmetic rather than structure. Where a register prices by code group — a group included, a fee to open the next one — a single distant activity can cost more as an addition than it contributes as revenue. That is the moment to ask whether the distant activity belongs in a different entity with its own file, its own risk profile and its own renewal date.

There is a fourth reason that is nothing to do with registers, and it is worth stating because clients raise it constantly. A licence is a public document. Everything on it is read together by banks, customers and counterparties, and a licence that lists a coherent business reads differently from one listing an unrelated spread. That is a presentation consideration, not a legal one, and it should never override the structural tests above — but it is a real reason a second entity sometimes earns its cost.

Work in this order. Each step narrows the next one, and doing them out of order is what produces an amendment.