What determines whether your entity has a UAE Corporate Tax obligation

The most common assumption we encounter is that an entity's licence type settles its tax position. It does not. A licence records what an entity is permitted to do; the tax question is about what it actually does, who it does it with, and where the value is created.

Two entities holding identical licences in the same zone can reach different conclusions, because one sells to customers outside the UAE through its own staff and the other invoices a related party for work performed elsewhere. Nothing on the licence distinguishes them.

First, what is the entity's activity in substance — not the activity described on the licence, but what the people employed by it spend their time doing.

Second, who does it transact with. Transactions with related parties are treated differently from transactions with independent customers, and the presence of the former changes what documentation you need regardless of the tax outcome.

Third, where value is created. This is the question groups most often answer by reference to where the invoice is raised, which is rarely the same thing.

Groups are exposed more often than standalone entities, for a structural reason: the position of any one entity depends on facts held by another. The UAE entity's treatment may turn on functions performed by a parent, or on an agreement signed elsewhere that nobody in the UAE has read.

The practical consequence is that a group cannot establish its UAE position entity by entity. It has to be mapped once, across the group, and then maintained as the group changes.

The useful output is not a conclusion but a documented position: what the entity does, who it transacts with, where value is created, what treatment follows, and the reasoning that connects them. Written now, while the facts are current.

A position paper prepared contemporaneously is a materially stronger document than the same analysis reconstructed two years later, and the difference shows under review.