DMTT Registration: Your Real Deadline Is the Data Behind It

Two weeks ago, a tax manager at a Dubai-headquartered group picked up the phone and said something we have heard five times since about DMTT registration in the UAE: "Our advisor told us to register for the top-up tax by 30 November. We'll fill in the form next month." Next month. As if the form were the job.

It is not. The form — the EmaraTax registration application for the UAE's 15% Domestic Minimum Top-up Tax — is genuinely straightforward. The work underneath it is not. Between now and 30 November 2026, any multinational group in scope needs to know its GloBE income computation, its constituent-entity mapping, and its covered-taxes reconciliation well enough to stand behind them. That is not paperwork. That is your entire 2025 financial picture, rebuilt through a 15% effective-tax-rate model.

Practitioners are already saying this out loud. Tax advisory teams describing the registration process call it "comparatively mechanical" — and in the same breath warn that it cannot be responsibly completed until the GloBE income computation, the constituent-entity mapping and the covered-taxes reconciliation are substantially done. On LinkedIn, tax professionals are reframing 30 November outright: not a filing deadline, a data-readiness deadline. The deadline says November. The homework says your whole 2025.

This is the debate that matters for DMTT registration in the UAE right now — and it is the one most groups have not had yet.

What the 30 November DMTT registration deadline actually requires

First, the mechanics, because precision matters here. The UAE's Qualified Domestic Minimum Top-up Tax implements the OECD Pillar Two GloBE framework: large multinational groups must face an effective tax rate of at least 15% in every jurisdiction where they operate, and where the local rate falls below that, a top-up tax is collected locally.

The registration rules were set by FTA Decision No. 12 of 2026. An entity subject to the top-up tax registers on EmaraTax — entity by entity, or through a single Designated Filing Entity (DDFE) appointed to manage the group's domestic minimum tax compliance. The standard deadline is seven months from the end of the first in-scope fiscal year. The transitional rule is the one biting now: for groups whose first in-scope fiscal year ends before 30 April 2026, the deadline is a fixed date — 30 November 2026. For the common case, a calendar-year group whose first in-scope year ended 31 December 2025, that is 52 days from today.

On 7 October 2026, the FTA published its Top-up Tax Guide on Scope and Registration — announced through WAM, the state news agency — the first official rulebook walking through who falls in scope, how each entity type is treated, and how registration works. It is the instruction manual for the machine the Decision built in summer. As we covered in our detailed breakdown of the registration mechanics, the guide also spells out the FTA's power to register the entity itself if you don't, and a flat AED 10,000 penalty for late registration.

So yes: the form is mechanical. You log in, you identify the entities, you name your DDFE, you submit. Compared with, say, preparing a full corporate tax registration with all its elections, this part is a form.

But here is the thing nobody puts on the form: the registration asks you to state your position on scope. It asks you to declare, entity by entity, what you are. And you cannot declare that responsibly without the data.

DMTT registration: why the filing date is the easy part

Think about what a group has to know before it registers.

To decide you are even in scope, you run the revenue test: consolidated group revenue of at least €750 million in at least two of the four fiscal years immediately preceding the tested year. One spike year doesn't pull you in; two do. That sounds simple until you try it — group finance directors know that "consolidated revenue" across a multinational with JVs, flow-through entities, and entities that changed hands is a reconciliation exercise, not a lookup.

Then the mapping. The guide walks through the treatment of constituent entities, permanent establishments, joint ventures, flow-through entities and hybrid entities. Every one of them has to be identified, classified, and placed. The groups that get hurt here are not the giant banks with dedicated Pillar Two teams — they are the mid-sized multinationals with a legacy holding company in another jurisdiction, a dormant subsidiary nobody has looked at in three years, a single overseas branch opened for one contract. One entity you forgot to map is one entity you registered wrong.

Then the computation itself. GloBE income is not accounting profit. Covered taxes are not the tax line on your P&L. Reconciling the two, entity by entity, to arrive at an effective tax rate you can defend — that is specialist work, and it has to be substantially done before the registration, because the registration is the moment you commit to your position on scope. As the advisory analysis puts it: you cannot responsibly register without the computation, the mapping, and the reconciliation substantially performed.

This is the gap the 30 November framing hides. The date looks like a filing date. It behaves like a readiness date. The groups treating it as paperwork will discover — somewhere around mid-November — that the paperwork demands answers they haven't computed.

The three data jobs that decide everything

1. The GloBE income computation

GloBE income starts from your financial accounting net income or loss — and then adjusts. Standard adjustments strip out things like intra-group dividends, equity gains and losses, revaluation gains, and stock-based compensation effects. Each adjustment is a judgement call with the guide's examples to follow. If your group's 2025 close produced clean, audited, entity-level numbers, you have a head start. If your 2025 close was "roughly right" — provisions parked where they were convenient, intercompany charges settled in January — the computation will find every shortcut you took.

2. The constituent-entity map

Every entity, every PE, every JV, every flow-through and hybrid — classified, ownership confirmed, definition recorded. This is the map the guide's registration section assumes you already have. We have seen groups discover during this exercise that a "dormant" foreign subsidiary was still filing local returns, or that a JV they treated as an investment is a constituent entity under the rules. Each surprise is a scope change, and each scope change is a registration change.

3. The covered-taxes reconciliation

Covered taxes are the taxes that count toward your 15% effective rate — and the definition is narrower than most finance teams expect. Timing differences matter: deferred tax accounting has its own rules under the framework. Getting this reconciliation wrong doesn't just change your ETR estimate; it changes whether you owe top-up tax at all, and in which jurisdiction. This is the number your board will ask about. It has to be defensible.

The cost of treating it as a form

What happens if you register on 28 November with the mapping half-done? The mechanics are unforgiving.

First, the appointment. The DDFE has to be the right entity, appointed with valid authority, in time. Grant Thornton's advisory tracking the framework notes the penalty exposure: AED 10,000 per entity where the appointment or filing fails. A wrong DDFE appointment doesn't contain the damage — it multiplies it across every entity in the group.

Second, the position. Registration commits you to a scoping position. If your constituent-entity map was wrong — the forgotten JV, the misclassified flow-through — your registration is wrong, and correcting it later means amendments, explanations, and penalty exposure you could have avoided by doing the map first.

Third, the calendar behind the calendar. The first top-up tax return and the payment fall due 30 June 2027 — and there is a narrow, often-misread relief around late returns for early fiscal years that does not extend to late registration or late payment. A rushed registration doesn't buy you time; it spends your credibility early.

We are not saying the FTA expects a dry-run filing with your registration. The authority's language is about registration, not about rehearsing computations. But the practitioners are right about the logic: the data the registration rests on has to exist before the registration is filed, or the filing is a declaration you can't support. And in a year when the FTA's enforcement visits ran past 103,000 in six months, "we'll fix the data later" is a position no group should want to defend.

Why groups keep underestimating the data work

Part of it is who owns the conversation. In most groups, the top-up tax landed on the tax team's desk as a compliance task — register, appoint, file. The data work underneath belongs to group finance, FP&A, and the consolidation team, and the two sides haven't always met in the middle. The tax team knows the 30 November date. The finance team hasn't been told their 2025 close is about to be rebuilt through a GloBE lens.

Part of it is the threshold myth. "We're not a €750 million group" is a sentence we hear a lot — from groups that haven't actually run the 2-of-4 test on consolidated, group-wide revenue. The test looks back four years. Two of those years might have been the strongest in the group's history. The test doesn't care about this year's revenue. It cares about the four years you've already reported.

And part of it is the carve-out confusion. Groups conducting their activities exclusively within the UAE are outside the regime regardless of revenue — but "exclusively" is doing a lot of work in that sentence. One overseas PE ends the argument. The exclusivity question is a mapping question, which means it's a data question too.

Your 52-day data-readiness plan

If your group is anywhere near the threshold, this is the order of operations — data first, form second:

1. This week: run the 2-of-4 test properly. Pull consolidated revenue for the last four fiscal years, group-wide, including entities you wish you'd forgotten. €750 million in at least two of them? You're potentially in scope. Calendar the re-test if you're out — next year's close could be the second year.
2. Answer the "exclusively UAE" question honestly. List every entity, PE, JV and flow-through, everywhere. One thing outside the UAE and the carve-out doesn't apply.
3. Build the constituent-entity map. Every entity classified, ownership confirmed, definitions recorded. Expect surprises — that's the point of doing it in October rather than discovering them under audit.
4. Start the GloBE income computation and covered-taxes reconciliation. You don't need the final return — that's 30 June 2027 — but you need the numbers substantially there, because they prove your scope position. Use the same entity-level financial data discipline you'd apply to a free-zone qualifying income analysis.
5. Model the effective tax rate. The 15% ETR is the point of the whole regime. Know where you stand, jurisdiction by jurisdiction, before you register — not after.
6. Decide the DDFE route. Centralise through a Designated Filing Entity with valid, timely appointment — most groups should — because the penalty runs per entity.
7. File the EmaraTax applications with a buffer. Early November, not 28 November. The deadline is the submission date. Build in the weeks, not the days.

The same discipline runs through the rest of your compliance stack. Supplier verification for your VAT claims runs on documented data, not assumptions. The registration mechanics we detailed in our TTGREG1 breakdown are only as good as the map behind them. Every compliance milestone in this market now punishes the same habit: treating the form as the work.

30 November is a filing date. The deadline is the data.

There is a version of November where a group's board gets a calm update: the map is done, the 2-of-4 test is run, the GloBE computation is substantially complete, the DDFE is appointed, the EmaraTax applications went in with three weeks to spare. And there is a version where a tax manager discovers on 25 November that the "mechanical" form is asking questions nobody in the group has computed answers to.

Both versions start from the same date. The difference is whether you treat 30 November as the deadline — or as the day the deadline catches up with you.

Not sure where your group stands on data-readiness? Talk to Escrow Consulting Group. We run DMTT scope reviews, build constituent-entity maps, and get the GloBE data position right before the registration goes in — so 30 November is a filed application, not a surprise. Visit escrowconsultinggroup.com for a free consultation.