Country-by-Country Report (CbCR) Filing

It is an annual report required under the OECD's BEPS Action 13 framework, breaking down a multinational group's revenue, profit before tax, tax paid and accrued, capital, earnings, headcount, and tangible assets on a jurisdiction-by-jurisdiction basis. In the UAE it is governed by Cabinet Resolution No. 44 of 2020 (as amended) and administered by the Ministry of Finance (MoF) — not the Federal Tax Authority, which handles VAT and Corporate Tax. Filing happens on a separate MoF portal from EmaraTax.

The obligation applies where the MNE Group's total consolidated group revenue in the immediately preceding fiscal year meets or exceeds the threshold prescribed under Cabinet Resolution No. 44 of 2020 and related Ministerial Decisions — a figure aligned with the OECD's own recommended CbCR threshold. Because the exact figure is periodically confirmed and can be expressed differently depending on reporting currency, PNPC confirms the applicable threshold against the current Cabinet Resolution and Ministerial guidance at the start of every engagement rather than relying on a remembered figure from a prior year.

The whole group's consolidated revenue — not the UAE entity's standalone turnover. A UAE subsidiary with modest local revenue sitting inside a large global group can still trigger a CbCR obligation for the group, and the UAE entity may still owe an annual Notification even if it is not the entity that files the full Report.

The Notification is a shorter annual filing identifying the Reporting Entity, its tax jurisdiction, and the UAE entity's role in the group — due earlier in the cycle. The Report is the full XML Schema-formatted document containing the jurisdiction-by-jurisdiction financial data, due within twelve months of the fiscal year end. They are assessed and penalised as two separate obligations — completing one does not satisfy the other.

No. Only the Reporting Entity — typically the Ultimate Parent Entity, or a nominated Surrogate Parent Entity — files the full Report. A UAE entity that is merely a Constituent Entity (neither the parent nor the surrogate) still has an annual Notification obligation confirming who is filing on the group's behalf and where, but does not itself submit the full XML Report.

A Surrogate Parent Entity is a group entity nominated to file the CbCR centrally on behalf of the whole group, in place of the Ultimate Parent Entity — often used where the UPE's home jurisdiction lacks an effective CbCR exchange arrangement with all the jurisdictions the group operates in, or where the group prefers to centralise filing in a single, well-understood jurisdiction. A UAE entity can be nominated as Surrogate Parent, in which case it takes on the full Report filing obligation.

For each jurisdiction the group operates in: revenue split between related-party and unrelated-party, profit (loss) before income tax, income tax paid on a cash basis, income tax accrued for the current year, stated capital, accumulated earnings, number of employees, and tangible assets other than cash and cash equivalents. This is Table 1 of the CbCR. Table 2 lists every constituent entity by jurisdiction and its main business activity.

The CbCR must be submitted in the OECD's prescribed CbC XML Schema format — a structured, machine-readable file format, not a spreadsheet or PDF. The MoF portal validates every submission against this schema, and errors — wrong currency codes, malformed jurisdiction codes, an incomplete MessageSpec header, inconsistent entity identifiers — cause an outright rejection on upload rather than a query for clarification.

A rejected upload is not treated as a timely filing — the obligation remains open until a valid submission is accepted by the portal. If the rejection happens close to or after the statutory deadline, the group is at risk of a late-filing penalty even though a submission attempt was made in good time. This is why building in a buffer before the actual deadline, not filing on the deadline itself, is standard PNPC practice.

For a first-time filer with consolidated financial data available at the start, a realistic timeline is six to eight weeks from data collection kickoff to validated XML submission — covering Reporting Entity confirmation, data collection, Table 1 and Table 2 preparation, schema validation, and submission. The Notification, which has its own earlier deadline, is filed separately and earlier in the cycle.

Cabinet Resolution No. 44 of 2020 and the UAE's administrative penalty framework for CbCR non-compliance prescribe penalties for late filing of the Notification, late filing of the Report, and for filing incomplete or incorrect information — assessed as separate, independent breaches. Because the specific penalty amounts are set by Cabinet/Ministerial decision and have been updated since the framework's introduction, PNPC confirms the current schedule with the client rather than quoting a fixed figure that may be out of date.

This happens more often than groups expect, typically where a UAE subsidiary's finance team was unaware that group-consolidated revenue (not local revenue) triggers the obligation. PNPC's first step is a factual determination — confirming the threshold was in fact crossed, in which fiscal year, and the UAE entity's role — followed by a plan to bring the filing current, which may include voluntary disclosure to the MoF depending on how the delay arose.

No. CbCR is one of three tiers in the OECD's transfer pricing documentation standard. The Master File and Local File — required separately under the UAE Corporate Tax Law (Federal Decree-Law No. 47 of 2022) and its related Ministerial Decisions once an entity meets the relevant thresholds — contain the group's value chain narrative and the transaction-level arm's-length analysis. A CbCR filing engagement does not include Master File/Local File preparation; PNPC treats that as a related but separate engagement.

The Reporting Entity is the group entity legally obligated to file the full CbCR — by default, the Ultimate Parent Entity in its jurisdiction of tax residence, unless a Surrogate Parent Entity has been validly nominated. Determining Reporting Entity status requires confirming the group's actual ownership chain, the UPE's tax residence, and whether that jurisdiction has an effective and current CbCR exchange arrangement with the UAE.

Yes, typically a Notification. Even where an Indian UPE files the full CbCR under India's Rule 10DB regime (Form 3CEAD) and India has an effective exchange arrangement with the UAE, the UAE Constituent Entity generally still owes its own annual CbCR Notification to the MoF, confirming that the Indian entity is the Reporting Entity. PNPC's India and Dubai desks coordinate this so the Indian Form 3CEAC/3CEAD filings and the UAE Notification are consistent.

The UAE entity, as UPE, files the full CbCR Report and Notification with the MoF, covering the Indian subsidiaries' data as part of the group-wide Table 1 and Table 2. The Indian subsidiaries, in turn, typically have their own Notification obligation under India's Rule 10DB confirming that the UAE entity is the Reporting Entity — mirroring the UAE's own Notification logic in reverse. PNPC coordinates both sides so the group files consistently in both jurisdictions.

The CbCR filing deadline runs from the group's own consolidated fiscal year end — twelve months from that date for the Report — which may differ from the UAE entity's own Corporate Tax period if the group uses a non-calendar consolidated year. PNPC tracks both calendars separately for clients where they diverge, since conflating the two is a common source of missed deadlines.

From the group's own consolidation package — the same underlying data used to prepare consolidated financial statements — rather than from local trial balances aggregated independently. This ensures the CbCR figures reconcile to the group's audited or management consolidated accounts, which is what a reviewing tax authority will check first if the CbCR is ever queried.

Yes. The OECD CbC XML Schema (and the MoF's implementation of it) includes an Additional Information section for free-text narrative explaining figures that would otherwise appear anomalous — a one-off gain, an unusual headcount movement following an acquisition, or a jurisdiction with disproportionate profit relative to headcount for a documented reason. Using this section proactively is good practice, not an admission of a problem.

No. The CbCR is filed confidentially with the Ministry of Finance and exchanged only between tax administrations under the Multilateral Competent Authority Agreement (MCAA) on the Exchange of CbC Reports — not published, and not disclosed to third parties or competitors. It is a government-to-government exchange for tax risk-assessment purposes.

The MoF exchanges the filed CbCR automatically with the tax administrations of the jurisdictions in which the group has constituent entities, under the MCAA framework, provided an effective exchange relationship exists with each. Those foreign tax authorities use the CbCR primarily as a risk-assessment tool to decide which groups warrant closer transfer pricing scrutiny — it is not itself a transfer pricing audit finding, but it is a well-established trigger for one.

In most cases, yes — a material restatement of the consolidated financial statements underlying an already-filed CbCR should be reflected through an amended filing with the MoF, together with a clear explanation of what changed and why. PNPC manages this through the same portal process used for the original filing, with a documented change log.

The MCAA on the Exchange of CbC Reports is the international framework under which signatory tax administrations, including the UAE's, automatically exchange CbCRs filed in their jurisdiction with the tax administrations of every jurisdiction in which the filing group has a constituent entity. It is the mechanism that turns a single UAE filing into a document visible to multiple foreign tax authorities.

CbCR filing itself remains governed by Cabinet Resolution No. 44 of 2020 and administered by the MoF, separate from UAE Corporate Tax under Federal Decree-Law No. 47 of 2022 administered by the FTA. However, the introduction of Corporate Tax has raised the practical stakes of CbCR accuracy, since a UAE entity's Corporate Tax return, its transfer pricing documentation (where required), and its CbCR figures are now all data points the FTA can cross-reference for the same entity.

Yes. A threshold and Reporting Entity determination is typically a short, focused piece of work — reviewing the group's consolidated revenue figure and ownership chain against the current Cabinet Resolution and Ministerial guidance — that we scope and price separately from the full filing engagement. Many clients start here before committing to the full data-collection and submission process.

Where an effective exchange relationship does not exist between the UAE and a particular constituent jurisdiction, that can affect the Reporting Entity analysis and, in some cases, trigger a 'local filing' requirement in the affected jurisdiction instead of relying purely on exchange from the UAE filing. This is assessed on a jurisdiction-by-jurisdiction basis as part of the Reporting Entity determination.

PNPC scopes and quotes a fixed fee for the CbCR filing engagement — covering threshold confirmation, Notification filing, data collection support, Table 1/Table 2 preparation, XML validation, and submission — agreed in writing before work begins. Pricing depends on the number of jurisdictions in the group, the state of the group's consolidation data, and whether this is a first-time filing or a recurring annual engagement.

Technically, yes, if the team has the OECD CbC XML Schema expertise, MoF portal familiarity, and bandwidth to run threshold testing and Reporting Entity determination correctly. In practice, most groups engage a CA firm because the schema formatting is unforgiving, the Notification-versus-Report distinction is easy to miss internally, and the exchange consequences of an error are not visible until a foreign tax authority raises a query years later.

The MoF portal acknowledgement receipts for both the Notification and the Report, the final validated XML file as submitted, a version history if any amendment was filed, and the correspondence trail with the MoF. This becomes part of the client's permanent Corporate Tax and transfer pricing compliance file, retrievable for any future FTA or MoF enquiry.

Free Zone status does not exempt an entity from CbCR — the obligation is driven by the group's consolidated revenue and the entity's role (UPE, Surrogate, or Constituent), not by whether the UAE entity itself is a Qualifying Free Zone Person for Corporate Tax purposes. A Free Zone entity that is the Ultimate Parent of a large group, or simply a Constituent Entity within one, has the same CbCR obligations as a Mainland entity in the same role.

An acquisition that pushes the group's consolidated revenue over the prescribed threshold triggers the CbCR obligation from that fiscal year onward, based on the new consolidated figure. PNPC recommends re-testing the threshold at every material acquisition or divestment, not just at the routine annual review, since the obligation can arise mid-cycle in ways that are easy to miss if the finance team is focused on integration rather than CbCR compliance.

They are separate regimes with separate legal bases, and it matters that clients not conflate them. CbCR runs under Cabinet Resolution No. 44 of 2020, administered by the MoF. Economic Substance Regulations, by contrast, were discontinued for financial years starting on or after 1 January 2023 under Cabinet Decision No. 98 of 2024 — UAE entities no longer have an ongoing ESR notification or report filing obligation for those later years, though historic ESR filings for earlier financial years remain part of the compliance record. CbCR is unaffected by the ESR discontinuation and continues as an independent, live annual obligation for groups above the revenue threshold.

Yes. The CbC XML Schema requires the reporting currency to be specified and applied consistently across the filing, and PNPC handles the currency and exchange rate convention as part of data preparation — including documenting the basis used where different jurisdictions in the group report in different local currencies before consolidation.

This happens, particularly in groups with complex or recently restructured ownership chains. PNPC's Reporting Entity determination step is designed to catch this before Notification filing, but if it surfaces mid-engagement, we redirect the client's UAE entity to the correct Notification-only filing (confirming the actual Reporting Entity) rather than continuing to prepare a full Report that was never the UAE entity's obligation to file.

This filing engagement is scoped around the mechanics of Notification and Report submission. Assessing whether the group's intercompany pricing would withstand transfer pricing scrutiny — the Master File narrative, Local File benchmarking, arm's-length analysis — is a related but separate advisory engagement PNPC also provides. We flag to every CbCR filing client where their CbCR figures suggest a transfer pricing conversation is worth having, but the two engagements are scoped and priced independently.

Many groups already have a centralised CbCR process run by an international advisor at the group level. PNPC's role in that scenario is typically the UAE-local piece — confirming the UAE entity's specific Notification obligation, ensuring UAE-side portal registration and filing is executed correctly and on the UAE's own deadlines, and coordinating the India-side leg where the group also has Indian entities. For groups without a centralised process, or where the UAE entity is itself the Reporting Entity, PNPC runs the full engagement directly.

Threshold testing against current consolidated revenue and the prescribed Cabinet Resolution threshold. Reporting Entity determination in writing. MoF portal registration for the responsible UAE entity. CbCR Notification preparation and filing. Consolidated data collection support and reconciliation to the group's consolidation package. Table 1 and Table 2 preparation. OECD CbC XML Schema validation. Report submission on the MoF portal. Retention of all acknowledgement receipts and correspondence. Cross-check of CbCR figures against the entity's Corporate Tax return and, where applicable, its transfer pricing documentation. India-side coordination for groups with Indian group entities. Following-year filing calendar setup.