CbCR Reporting UAE 2026: Country-by-Country Reporting and What MNE Groups Actually Have to File

What is CbCR reporting in the UAE? CbCR — country-by-country reporting — is the annual jurisdiction-by-jurisdiction breakdown of revenue, profit, tax paid, headcount and assets that multinational groups above AED 3.15 billion in consolidated revenue file under Cabinet Resolution No. 44 of 2020. In the UAE only a UAE-tax-resident ultimate parent entity notifies and files.

Country by country reporting UAE carries the steepest fixed-amount penalty in the country’s international tax framework. A missed report or notification triggers AED 1,000,000, plus AED 10,000 per day of continued failure.

The legal foundation is Cabinet Resolution No. 44 of 2020, which replaced Cabinet Resolution No. 32 of 2019. It is the current governing instrument implementing OECD BEPS Action 13 in the UAE — see BEPS explained for UAE businesses for where Action 13 sits in the wider framework.

The framework applies to MNE groups with consolidated group revenue of AED 3.15 billion or more. Here’s the part that catches people out, though: under Article 2 of Cabinet Resolution No. 44 of 2020 the UAE places both the notification and the report on a UAE-tax-resident ultimate parent entity. A UAE subsidiary or branch of a group headquartered abroad has no UAE notification or report of its own — the obligation follows the parent in its home jurisdiction.

Enforcement has sharpened. The Ministry of Finance, which administers CbCR as the UAE’s Competent Authority, has moved from registration drives into substantive review of late and incomplete filings.

This guide walks through the threshold mechanics, the CbC notification and report deadlines, the OECD three-table format, surrogate parent filing, and how CbCR feeds DMTT and transfer pricing. A worked example, the common mistakes, and a compliance checklist follow. If you are unsure whether any UAE filing applies to your structure, start with CbC notification vs report in the UAE. If your group is in scope and you want the notification and XML filing handled end to end, our CbC reporting support in the UAE covers scope confirmation, MoF portal submission and cross-document reconciliation.

What CbCR actually is in the UAE

CbCR reporting is a transparency framework — not a tax. Each in-scope MNE group files one CbC Report annually, typically prepared by the Ultimate Parent Entity (UPE) in its home jurisdiction.

That report is then automatically exchanged with tax authorities in treaty partner countries via bilateral Competent Authority agreements.

The report gives every relevant tax authority a consolidated picture of where the MNE group earns revenue, pays tax, employs people, and holds tangible assets, jurisdiction by jurisdiction.

On top of that sits the UAE-specific layer. Where the group’s ultimate parent is UAE-resident, that parent must separately file an annual notification with the UAE Ministry of Finance confirming it is the Reporting Entity, and then file the CbC Report itself. Where the ultimate parent sits abroad, the UAE resolution imposes no matching notification on the group’s UAE constituent entities — the report and any notification are handled in the parent’s jurisdiction.

Why the data matters past the checklist

The data filed in a CbC Report flows into several downstream tax workflows. The Transitional CBCR Safe Harbour uses qualified CbC Report data to work out whether UAE Domestic Minimum Top-up Tax can be deemed zero for a jurisdiction, so errors in the report can knock the whole group out of the safe harbour. Tax authorities worldwide, the FTA among them, run the same data as their first risk-assessment filter when picking MNE groups for transfer pricing audit. And the aggregate UAE figures in the report should reconcile to the group’s UAE corporate tax return filings, because a material discrepancy between the two is exactly what flags immediate audit risk.

CbCR vs Master File vs Local File

CbCR sits within the broader OECD BEPS Action 13 three-tier documentation framework. The three documents have different scope but work together:

Document	Scope	Filing obligation
CbC Report	High-level jurisdictional financial and operational data — entire MNE group	Filed by the group’s ultimate parent; in the UAE, only a UAE-resident ultimate parent notifies and files
Master File	Global organisation, value chain, intangibles, financing	Local File obligation triggers this; kept on record, produced on request
Local File	Specific controlled transactions of the UAE entity	UAE entity maintains; submitted on FTA request

Our UAE transfer pricing guide covers Master File and Local File mechanics in detail.

Who actually has to file?

Who’s in scope

An MNE group is in scope for country by country reporting UAE if its consolidated group revenue equals or exceeds AED 3.15 billion in the fiscal year immediately preceding the reporting year. The threshold aligns with the OECD’s EUR 750 million equivalent and mirrors the UAE Pillar Two DMTT scope threshold.

Under Cabinet Resolution No. 44 of 2020 the annual notification and the CbC Report both fall on the group’s UAE-resident ultimate parent entity — the entity at the top of the group that prepares the consolidated financial statements, where its tax residence is in the UAE. That entity both notifies and files the report.

A UAE operating subsidiary, holding company, or branch whose ultimate parent is resident abroad has no UAE notification or report of its own. The group’s obligation is discharged in the parent’s jurisdiction, so the practical first question is simply: where does the ultimate parent sit?

Who’s out

The following are fully outside UAE CbCR filing obligations:

• MNE groups with consolidated group revenue below AED 3.15 billion
• UAE-only groups with no foreign constituent entities
• Natural persons, non-juridical entities, and similar structures
• UAE constituent entities whose ultimate parent is resident abroad — the notification and report sit with the parent, not the UAE entity

There is no minimum number of foreign jurisdictions required. An MNE group with operations in just two countries — the UAE and one other — qualifies as a multinational group and is in scope if it meets the revenue threshold.

Entity type	CbC notification required	CbC Report filing
UAE-resident UPE of in-scope MNE	Yes — by fiscal year-end	Yes — within 12 months
UAE constituent entity (subsidiary/branch) of a foreign-UPE MNE	Generally no	No — filed by the parent abroad
MNE group below AED 3.15B threshold	No	No
UAE-only group (no foreign entities)	No	No

CbCR filing deadlines for a UAE holding company under a foreign parent

Country-by-country reporting for a UAE holding company owned by a foreign parent usually raises the same question: what is the actual CbCR filing deadline, and does the UAE company owe anything when the report is prepared abroad? The short answer under Cabinet Resolution No. 44 of 2020 is that a UAE holding company sitting beneath a foreign ultimate parent generally owes nothing in the UAE — neither the notification nor the report. The resolution places both obligations on a UAE-resident ultimate parent entity, so when the ultimate parent is abroad and files at home, the group’s CbCR duties are discharged in that jurisdiction.

The two deadlines that matter apply when the UAE company is itself the group’s ultimate parent: the notification is due at fiscal year-end, and the full CbC Report within 12 months of year-end. A UAE holding company beneath a foreign parent normally files neither — the whole CbCR obligation follows the parent abroad. The practical task for a foreign-owned UAE holding company is therefore to confirm the parent’s residence and that the parent is filing, rather than to calendar a UAE deadline that generally does not apply.

Holding companies still warrant care, because their line in the group’s CbC report often shows sizeable profit against a small headcount — exactly the substance pattern counterparty authorities tend to question, wherever the report is filed. If you are weighing whether any UAE filing applies to your structure, CbC notification vs report in the UAE sets out the split, and our CbC reporting support covers scope confirmation, notification preparation and cross-document reconciliation.

The compliance cycle, end to end

Step 1: Confirm scope — apply the threshold test

Use the MNE group’s consolidated annual revenue from the fiscal year immediately preceding the reporting year. A group with AED 3.3 billion in 2024 revenue is in scope for the 2025 reporting year.

Reassess annually — groups near the borderline can drift in and out of scope as revenue fluctuates.

Step 2: Identify the group’s ultimate parent and its residence

The UAE notification and report attach to a UAE-resident ultimate parent entity. Map the group’s ownership to confirm whether the ultimate parent is UAE-resident. If it sits abroad, the group’s UAE constituent entities generally have no separate UAE notification to file, and the obligation is met in the parent’s jurisdiction.

Step 3: Confirm the Reporting Entity

Where the ultimate parent is UAE-resident, it is the Reporting Entity for UAE purposes and both notifies and files. Where it is resident abroad, the report is filed there; a surrogate arrangement is an OECD concept rather than a UAE statutory designation, so any such structure should be confirmed with the Ministry of Finance.

Step 4: Set up UAE MoF portal access

A UAE-resident ultimate parent files the notification electronically through the UAE Ministry of Finance portal, which requires an authorised signatory. First-time filers should allow two weeks for access setup — do not leave this to the final days before the deadline.

Step 5: Submit the CbCR notification

File by the last day of the MNE group’s financial reporting year. For calendar-year groups this is 31 December. The notification confirms the Reporting Entity identity, the filing jurisdiction, and the UAE entity’s role within the group structure.

Step 6: Prepare the CbC Report (if required)

A UAE-resident ultimate parent must file the full CbC Report within 12 months of fiscal year-end. The report requires detailed financial and operational data for every jurisdiction in the MNE group.

Begin data collection immediately after fiscal year-end. Six months minimum lead time is realistic given the data volume.

Step 7: Generate and validate the OECD XML schema file

The CbC Report must be submitted in the OECD-specified XML schema format. Use specialised CbCR software or a group tax department system to generate the file. Validate against the schema before submission to prevent portal rejection.

Step 8: File through the MoF portal and retain confirmation

Submit the XML file through the Ministry of Finance portal. Capture and store the submission confirmation receipt.

Keep all supporting documentation — CbC Report, notification records, preparation workpapers — for a minimum of five years from submission date, as required by Cabinet Resolution No. 44 of 2020.

Keeping records for seven years is a common advisory practice recommendation, not a legal requirement under CbCR law. It can simplify multi-obligation audits where different UAE tax retention clocks apply.

Thresholds and deadlines at a glance

Obligation	Threshold / condition	Deadline
Annual CbCR notification (UAE-resident ultimate parent)	AED 3.15B+ consolidated group revenue	Last day of financial reporting year
CbC Report — UAE-resident UPE	AED 3.15B+ and UAE is the parent’s residence	Within 12 months of fiscal year-end
UAE constituent of a foreign-parented group	Ultimate parent resident abroad	No UAE notification or report — filed by the parent abroad
Documentation retention	UAE-resident Reporting Entity	Minimum 5 years from submission (statutory); 7 years is a common advisory recommendation, not a legal requirement

For calendar-year 2026 reporting:

Milestone	Date
CbCR notification deadline (2026 reporting year)	31 December 2026
CbC Report filing deadline (2026 reporting year)	31 December 2027
Threshold test basis year	2025 consolidated group revenue

What missing a deadline actually costs

Cabinet Resolution No. 44 of 2020 prescribes the following penalty schedule. These are the steepest fixed-amount penalties in the UAE tax framework.

Violation	Penalty
Failure to file CbC Report on time	AED 1,000,000 + AED 10,000/day (daily portion capped at AED 250,000)
Failure to file CbCR notification on time	AED 1,000,000 + AED 10,000/day (daily portion capped at AED 250,000)
Failure to retain required documentation	AED 100,000
Filing inaccurate or incomplete information	AED 50,000 to AED 500,000

[[chart:cbcr-penalties]]

The notification penalty and the report penalty each carry an AED 1,000,000 fixed component. However, Article 8(3) of Cabinet Resolution No. 44 of 2020 caps the total penalties — the daily accruals aside — at AED 1,000,000 per entity for any reporting fiscal year.

This means a UAE-resident ultimate parent that misses both its notification and its CbC Report in the same fiscal year still tops out at AED 1,000,000 on the fixed side, not AED 2,000,000. The daily accrual component (AED 10,000/day, capped at AED 250,000 per violation) runs separately on top of that aggregate cap and is not subject to it.

The three-table format

The CbC Report follows the OECD’s standardised three-table structure:

Table	Content
Table 1	Aggregate jurisdictional data: revenue from related and unrelated parties, profit/loss before tax, income tax paid, income tax accrued, stated capital, accumulated earnings, number of employees, tangible assets — per jurisdiction
Table 2	List of all constituent entities: name, jurisdiction of tax residence, jurisdiction of incorporation (if different), and main business activity
Table 3	Supplementary information: data source explanations, exchange rate methodology, any additional context needed to interpret Tables 1 and 2

The full report must be submitted in the OECD XML schema format. Manual XML generation at scale is impractical — groups of any size use specialised CbCR software.

Example: a UAE-headquartered tech group

Scenario: A UAE-headquartered technology services group with the following profile:

• Consolidated group revenue in 2025: AED 4.2 billion (above the AED 3.15 billion threshold)
• Fiscal year: calendar year (1 January to 31 December)
• Constituent entities: UAE parent + subsidiaries in Saudi Arabia, India, United Kingdom, and Singapore
• UAE entity is the Ultimate Parent Entity

CbCR timeline for the 2026 reporting year:

Step	Deadline	Action
Threshold test	January 2026	Confirm 2025 consolidated group revenue AED 4.2B — in scope
Portal access setup	February 2026	Register authorised signatories for UAE parent on MoF portal
Data collection begins	January 2026	Extract jurisdictional P&L, tax paid, headcount, assets for all 5 jurisdictions
CbCR notification	31 December 2026	UAE parent notifies: role = UPE, Reporting Entity = UAE parent
CbC Report filing	31 December 2027	XML file covering all 5 jurisdictions submitted to MoF portal

[[chart:cbcr-timeline-2026]]

Table 1 data extract (illustrative figures, AED millions):

Jurisdiction	Revenue — related	Revenue — unrelated	Profit before tax	Tax paid	Employees
UAE	185	1,240	280	25.2	340
Saudi Arabia	95	610	115	19.6	180
India	240	380	65	6.5	520
United Kingdom	60	420	88	22.0	95
Singapore	180	790	140	11.9	210

The UAE figures reconcile to the UAE corporate tax return: AED 280M profit before tax → first AED 375,000 at 0% = nil; remaining AED 279.625M at 9% = AED 25.17M corporate tax — consistent with the AED 25.2M tax paid shown in Table 1. This reconciliation step is mandatory before submission.

If the group also qualifies for the Pillar Two Transitional CBCR Safe Harbour for the UAE jurisdiction — low profit margin test, substance-based income exclusion — the CbC Report data supports the safe harbour claim directly.

Any material error in Table 1 UAE figures risks disqualifying the safe harbour and triggering full UAE corporate tax GloBE calculations.

Surrogate parent filing — an OECD concept, handled with care in the UAE

A Surrogate Parent Entity (SPE) is an OECD mechanism: a constituent entity a group nominates to file the CbC Report in place of the ultimate parent, most often where the ultimate parent’s jurisdiction cannot exchange the report with the countries that need it.

It comes up for UAE-anchored groups whose historical ultimate parent sits in a jurisdiction with limited exchange coverage. The important caveat is that Cabinet Resolution No. 44 of 2020 frames the UAE obligation around a UAE-resident ultimate parent entity; it does not set out a formal UAE “surrogate” designation or a secondary local-filing route. So while centralising a group’s reporting in the UAE can simplify compliance, any surrogate arrangement should be confirmed with the Ministry of Finance before the group relies on it, rather than assumed from the OECD framework.

For UAE-anchored groups, the cleanest position is usually to establish whether a UAE entity is, or can properly become, the group’s ultimate parent for reporting purposes, which aligns filing with the UAE’s corporate tax filing calendar.

Where CbCR data lands next: DMTT and TP audits

CbCR data feeds the UAE’s international tax compliance web. Inaccuracy in the CbC Report cascades into two high-value downstream areas:

Pillar Two DMTT — Transitional CBCR Safe Harbour

The UAE DMTT Pillar Two regime allows qualifying MNE groups to use the Transitional CBCR Safe Harbour to deem top-up tax zero for a jurisdiction during the transitional period. But this only applies if the CbC Report data is accurate and “qualified” within the OECD definition.

Groups that prepare inaccurate or late CbC Reports lose access to this safe harbour entirely. This forces full GloBE effective tax rate calculations that are much more complex and may result in substantial top-up tax charges.

Transfer pricing audit risk selection

The FTA uses CbCR data alongside Local File submissions and TP Disclosure Forms to risk-rank UAE constituent entities for transfer pricing audit. The specific red flags include:

• Low effective tax rates relative to group average (flags profit shifting concerns)
• High intra-group revenue with low pre-tax profit in the UAE jurisdiction
• Material headcount-to-profit imbalances across jurisdictions
• Inconsistencies between CbCR figures and Local File transaction amounts

Cross-document reconciliation — CbCR against Master File, Local File, TP Disclosure Form, and UAE corporate tax returns — before submission prevents the inconsistencies that trigger audit selection.

Where we see UAE groups slip up

The first slip is the mirror image of a common myth: many assume a UAE subsidiary of a foreign group must lodge its own UAE notification. Under Cabinet Resolution No. 44 of 2020 it generally need not — the notification and report sit with a UAE-resident ultimate parent. The real exposure runs the other way: a UAE-headquartered group that treats the notification as an afterthought, because it is a standalone obligation with its own AED 1,000,000 penalty even when the report is filed on time.

The second is losing track of borderline threshold drift. A group operating near the AED 3.15 billion revenue line moves in and out of scope as year-on-year revenue shifts; one that was out in 2024 can be back in for 2025. So the threshold needs reassessing every year rather than settling it once and forgetting it.

The third is inconsistent data across the documentation tiers. CbCR data flows automatically into the FTA’s risk-assessment systems alongside Local File and TP Disclosure Form submissions, discrepancies get picked up algorithmically, and reconciling the documents against each other before filing is really the main thing standing between the group and audit selection.

The fourth is misreading how a UAE-anchored group centralises its reporting. Where a foreign ultimate parent’s jurisdiction has thin exchange coverage, groups sometimes assume they can simply nominate a UAE “surrogate” filer. Because Cabinet Resolution No. 44 of 2020 builds the UAE obligation around a UAE-resident ultimate parent rather than a statutory surrogate route, the cleaner fix is usually to confirm which entity is the group’s ultimate parent for reporting, and to agree any surrogate arrangement with the Ministry of Finance in advance.

The fifth is starting the report data collection too late. The 12-month window sounds generous until you begin: assembling Table 1 and Table 2 data across dozens of legal entities, multiple ERP systems, and varied local GAAP frameworks takes three to six months at a minimum, and that’s assuming nothing goes sideways. Beginning straight after fiscal year-end is the habit that keeps last-minute errors out.

One genuine edge case is the timeline. Cabinet Resolution No. 44 of 2020 was issued in June 2020, repealing the earlier 2019 resolution, but the reporting obligation itself takes effect for fiscal years from 1 January 2019. A UAE-headquartered group that came into scope early on should check it has filed notifications for all open periods — the obligation runs from the 2019 commencement date, not the 2020 issuance date.

Groups that run CbCR properly, with accurate data, on-time notifications and clean reconciliation, avoid the AED 1,000,000 penalty and keep their Pillar Two Transitional Safe Harbour eligibility intact, and they tend to sit lower down the FTA’s transfer pricing audit list as well. Set against the penalty and the safe harbour value at stake, the compliance spend is modest.

Reporting errors the FTA spots first

The CbCR process throws up a small number of recurring errors that the FTA and exchange-treaty partners spot quickly. Each is preventable with disciplined data governance.

Revenue classification is the first. Table 1 splits revenue between “related parties” and “unrelated parties,” and many groups misclassify treasury income, royalties from related entities, or intra-group service charges. What that produces is double counting, where the same revenue shows up once in the related column of the receiving jurisdiction and again in the unrelated column of the same one. Reconciling against the consolidated trial balance and eliminating intercompany transactions cleanly heads it off.

Tax paid and tax accrued get confused just as often. Tax paid is the cash figure; tax accrued is the current-year liability per the books, and the two diverge in any given year because of timing differences in payment cycles. Report one where the other belongs and you distort the jurisdictional effective tax rate that the safe harbour test leans on, so both columns need populating, each from its correct underlying ledger source.

Employee headcount drifts methodologically. The report wants headcount on a consistent basis across all jurisdictions, but some groups count full-time equivalents in the UAE and then switch to a person-by-person basis elsewhere. The OECD’s standard is full-time equivalents at year-end, or the average over the year; document whichever you use in Table 3 and apply it uniformly across every jurisdiction.

Tangible assets are another trap, because Table 1 requires them to exclude cash and cash equivalents, intangibles, and receivables. Leave the cash in and you inflate the asset base for cash-rich jurisdictions, which tend to be the holding companies, and that distorts the substance-based comparison that drives Pillar Two safe harbour eligibility.

The last one is completeness of the entity list. Table 2 has to include every consolidated entity, dormant ones, holding shells, and entities that earned nothing in the period alike. Drop a single legal entity and you’ve created a common audit finding and a frequent trigger for further review.

Lining up CbCR data with the DMTT Safe Harbour

The Transitional CBCR Safe Harbour under the UAE Pillar Two regime allows a jurisdiction’s top-up tax to be deemed zero where three tests are met using qualified CbC Report data:

• A de minimis test (revenue and profit below thresholds)
• A simplified ETR test (above 15% for 2024 returns, rising for later periods)
• A routine profits test (profit below a substance-based exclusion)

For the UAE jurisdiction in particular, the safe harbour tests are typically straightforward to satisfy provided the underlying CbC Report data is accurate. The relevant inputs come directly from Table 1: profit before income tax, income tax accrued, revenue, employees, and tangible assets.

The reconciliation discipline is to ensure these figures match the GloBE Information Return when the group eventually moves to full GloBE calculations after the transitional period.

Groups that prepare CbC Report and GloBE Information Return data in isolated workflows discover material differences during the transition. Build a single integrated data set sourced from the same ERP and consolidation system, with shared reconciliation logic feeding both reports.

The UAE Domestic Minimum Top-up Tax guide covers the substantive Pillar Two calculation. The CbCR workflow should feed it cleanly.

Who actually reads your CbC report — and what they do with it

A CbC report is not a filing that disappears into an archive. Under the exchange framework, every jurisdiction where the group operates can receive it automatically, and tax authorities run it through risk-assessment engines. Three downstream uses matter for UAE groups.

Treaty and withholding positions get cross-checked. When a group claims reduced withholding rates on royalties or interest flowing into the UAE, the source country’s authority can read the CbC report to see whether the UAE entity that “owns” the income actually shows employees, assets and profit there. A table 1 line showing thin substance next to fat related-party revenue is a classic challenge trigger — the mechanics of those claims are covered in our withholding tax UAE guide.

Financing structures light up. Jurisdictional splits of related-party interest income and expense make debt-loading visible at a glance. A UAE entity carrying heavy intercompany interest against modest EBITDA should expect the deduction to be tested under the UAE interest limitation rules — and to see the same ratio questioned by counterparty jurisdictions reading the same report.

Domestic audit selection feeds on it. The FTA’s risk engine consumes what the group files. Inconsistencies between the CbC report, the corporate tax return and the transfer pricing disclosure form are precisely the machine-detectable mismatches that drive selection — how that process runs from notice to assessment is set out in our FTA tax audit UAE guide.

The practical discipline this implies: before submission, read your own report the way a foreign auditor would. Any line where profit sits without people, or revenue sits without activity, needs a documented explanation ready before anyone asks.

Choosing a Dubai accounting firm for international CbCR compliance

Groups looking for a Dubai accounting firm or one of the UAE transfer pricing firms to support international CbCR compliance usually need help with coordination rather than the raw numbers, which the group tax function already holds. An accounting firm in Dubai can support an internationally structured group on the UAE side of the obligation: confirming whether consolidated revenue crosses the AED 3.15 billion threshold, establishing whether the group’s ultimate parent is UAE-resident (and so whether any UAE notification or report is owed at all), and checking that the UAE figures in Table 1 reconcile to the local corporate tax return before anything is submitted.

The value sits in reconciliation and calendar discipline. CbCR data is read alongside the corporate tax return and the transfer pricing disclosure form, and mismatches between them are what draw a review — so aligning the three before filing is the practical safeguard. A UAE adviser can also flag whether a UAE entity is the group’s ultimate parent for reporting purposes, and keep any notification and report deadlines on a shared calendar with advance reminders.

This is preparation and advisory support, not representation before the authorities. For how CbCR interacts with the wider compliance load, see our transfer pricing guide and corporate tax services.

If you’re in scope, here’s what to do this quarter

Most UAE SMEs are entirely outside CbCR scope. The AED 3.15 billion threshold ensures the obligation applies only to large multinational groups.

If your UAE business is part of a global group and you are unsure whether consolidated group revenue crosses the threshold, that determination should be made now, not at year-end.

If you are in scope, the practical actions are:

1. Confirm threshold status using the preceding year’s consolidated revenue figures
2. Establish where the ultimate parent is resident — this determines whether any UAE notification or report is owed, and by which entity
3. Calendar both deadlines where a UAE entity is the reporting parent — notification by fiscal year-end, CbC Report within 12 months — with 60-day and 30-day advance reminders
4. Establish MoF portal access for the UAE Reporting Entity’s authorised signatory well before the notification deadline
5. Coordinate with group head office on which entity is the Reporting Entity before the notification is due
6. Align CbCR data with UAE corporate tax returns and transfer pricing documentation before submission

For in-scope groups, the notification is the first and most commonly missed obligation. The report is typically a group tax function deliverable. Ensuring UAE entities fulfil the notification requirement is the immediate practical priority.

For questions about scope, notification preparation, or how CbCR aligns with your UAE corporate tax services and transfer pricing documentation, the FTA website and Ministry of Finance portal publish the current technical guidance.

For UAE accounting, VAT and corporate tax support, see Velmont Crest.

---

References:

1. UAE Ministry of Finance — Cabinet Resolution No. 44 of 2020 — governing instrument for UAE CbCR, MoF portal and submission procedures
2. UAE Federal Tax Authority — CbCR coordination with corporate tax filings and broader UAE tax compliance
3. UAE Government Business Portal — official guidance on UAE business obligations