Country-by-Country Reporting (CbCR) Advisory

It is an annual report that large multinational groups must file, breaking down their revenue, profit, tax paid, employees, and assets by country. Instead of a tax authority seeing only the local UAE entity's numbers, CbCR shows the whole group's global footprint in one document. It exists because, under the OECD's BEPS Action 13 initiative, tax authorities wanted visibility into whether profit is being booked in low-tax jurisdictions that have little real business activity — a pattern known as base erosion and profit shifting.

Only MNE Groups whose total consolidated group revenue in the preceding fiscal year is AED 3.15 billion or more (the UAE's expression of the OECD's EUR 750 million threshold, under Cabinet Resolution No. 44 of 2020), and where the Ultimate Parent Entity (or a designated Surrogate Parent Entity) is UAE tax resident. Most UAE companies — including the vast majority of free zone and mainland SMEs — fall well below AED 3.15 billion and have no CbCR obligation at all.

Usually yes, but a lighter one — the CbCR Notification. Even where the full report is filed centrally by the foreign Ultimate Parent Entity and reaches the UAE through automatic exchange, the UAE Constituent Entity typically still has to file an annual notification confirming which entity is filing the group's CbCR and in which jurisdiction. Only in specific circumstances — such as the absence of an effective exchange agreement between the UAE and the UPE's jurisdiction, or a systemic failure to exchange — would the UAE entity itself be required to file a full local CbCR as a Surrogate Parent Entity.

The Notification is a short annual filing identifying the group's Reporting Entity, its tax residence jurisdiction, and the UAE entity's own classification (Ultimate Parent, Surrogate Parent, or Constituent Entity). The CbCR itself is the substantive report containing the country-by-country financial and headcount data. They are assessed separately, filed within different windows relative to the fiscal year end, and penalised independently — a group can be compliant on one and non-compliant on the other.

For each jurisdiction the group operates in: revenue split between related-party and unrelated-party transactions, profit (or 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 excluding cash and cash equivalents. At the entity level, the report also captures each Constituent Entity's tax identification number, jurisdiction of organisation if different from tax residence, and main business activity from a prescribed list of categories.

The CbCR is prepared in the OECD's prescribed XML schema format and submitted through the Ministry of Finance's designated filing system, following the process set out under Cabinet Resolution No. 44 of 2020 and related Ministerial Decisions. The notification is filed separately through the same channel. Both require the Reporting Entity's details, tax registration information, and — for the CbCR itself — the full country-by-country dataset formatted to the schema's technical specifications.

The UAE applies administrative penalties for late or non-compliant CbCR notifications and filings under its penalty framework for Cabinet Resolution No. 44 of 2020, assessed independently for the notification and the report. Beyond the direct penalty, a late or defective filing can itself become a point of scrutiny once the (eventually filed) CbCR is exchanged with partner tax authorities — timing gaps are visible to anyone reviewing the group's compliance history.

No. CbCR is a disclosure and reporting obligation, not a tax assessment. It does not itself impose tax. However, the data disclosed can prompt a tax authority — in the UAE or in a partner jurisdiction receiving the exchanged report — to open a transfer pricing enquiry if the profit allocation across jurisdictions looks disproportionate to the reported substance (employees, assets) in each location. Any resulting tax adjustment would come through a separate transfer pricing assessment process, not through the CbCR filing itself.

They are complementary, not the same thing. CbCR is a high-level, group-wide picture across all jurisdictions. The Master File (group-wide) and Local File (entity-specific) required under the UAE Corporate Tax Law, Federal Decree-Law No. 47 of 2022, go into much greater detail on the group's value chain, intercompany pricing policies, and the arm's-length analysis for specific related-party transactions. A group above the CbCR threshold will very often also meet the Master File/Local File thresholds, and the three documents need to tell a consistent story.

Typically the UPE files centrally in its own jurisdiction of tax residence — in this case India, under Section 286 of the Income-tax Act, using Form 3CEAC (notification) and Form 3CEAD (report). The UAE Constituent Entity's obligation is then usually limited to its own CbCR Notification, confirming that the Indian parent is the Reporting Entity, provided an effective exchange relationship exists between India and the UAE for CbCR purposes. PNPC coordinates both filings as one engagement from our Chennai/Bangalore/Hyderabad and Dubai offices.

The obligation is assessed annually against the immediately preceding fiscal year's consolidated revenue, so crossing the threshold this year typically triggers the notification and filing obligation from the current fiscal year going forward. We recommend building the CbCR data collection framework in the year before the threshold is expected to be crossed, so the first filing year is not a scramble.

Yes — CbCR and the Qualifying Free Zone Person (QFZP) 0% Corporate Tax regime are entirely separate frameworks. QFZP status relates to the UAE Corporate Tax rate applied to qualifying income of a Free Zone entity. CbCR is assessed at the consolidated group revenue level, regardless of any individual entity's tax rate or QFZP status. A free zone entity that is the UAE-resident UPE (or Surrogate Parent) of a large group above the CbCR threshold has a CbCR obligation independent of its own Corporate Tax position.

We start from the Ultimate Parent Entity's audited (or, where audit is not yet complete, best-available) consolidated financial statements for the immediately preceding fiscal year, applying the group's normal consolidation basis and currency, and compare the resulting figure against the threshold prescribed under Cabinet Resolution No. 44 of 2020. Where the group's fiscal year does not align with the calendar year, or where a material acquisition or disposal occurred mid-year, we document the basis of the calculation carefully, since this is the figure most likely to be questioned first if the classification is later challenged.

A Surrogate Parent Entity is a Constituent Entity that a group designates to file the CbCR on behalf of the whole group in place of the actual Ultimate Parent Entity — typically because the UPE's home jurisdiction does not require CbCR filing, does not have an effective exchange agreement with the UAE, or there has been a systemic failure in that jurisdiction's exchange mechanism. A UAE entity would only become a Surrogate Parent Entity by the group's deliberate designation, not automatically.

There is no independent audit requirement specific to the CbCR filing itself under Cabinet Resolution No. 44 of 2020, but the underlying data must be capable of reconciliation to the group's consolidated financial statements, which are typically audited at the group level as part of normal statutory reporting. We build formal reconciliation working papers as part of every CbCR engagement so the figures are defensible even without a standalone CbCR audit.

The Reporting Entity's finance controller or CFO for data ownership, group tax or transfer pricing lead if one exists, and — because CbCR data is reviewed by boards and, in listed or regulated groups, by audit committees — appropriate senior sign-off before filing. PNPC prepares a summary memorandum specifically for this internal governance step, distinct from the technical filing itself.

Realistically 8 to 10 weeks from the initial threshold assessment to the filed report, assuming reasonably prompt data availability from group entities. Groups with many jurisdictions, non-aligned fiscal year ends, or fragmented ERP systems across subsidiaries should plan for a longer data-gathering phase. The notification itself, once entity classification is confirmed, can typically be filed well ahead of the full report.

The UAE's administrative penalty framework under Cabinet Resolution No. 44 of 2020 addresses both late and non-compliant filings, which includes filings that are inaccurate or incomplete, separately from purely late filings. Beyond the direct penalty, an inaccurate CbCR that is subsequently exchanged with partner jurisdictions can trigger downstream transfer pricing enquiries in those jurisdictions that are considerably more costly to resolve than the original filing would have been to get right.

PNPC can act on the group's behalf for both the notification and the report, subject to the appropriate authorisation being granted for the Ministry of Finance's filing system. In practice, we prepare the data, run the reconciliation, validate the XML file against the current schema, and manage the submission, while the Reporting Entity retains ultimate ownership and sign-off responsibility for the filing, consistent with good governance practice.

CbCR data is not publicly disclosed by the UAE Ministry of Finance. It is exchanged confidentially between tax administrations under the Multilateral Competent Authority Agreement on the Exchange of CbC Reports and equivalent bilateral arrangements, for use in tax risk assessment and transfer pricing analysis by the receiving tax authorities — not for public disclosure.

Yes, in the sense that real substance — employees, tangible assets, and decision-making activity — reported in the CbCR for the UAE jurisdiction supports the profit the group allocates there, which is precisely what a reviewing tax authority looks for when assessing whether reported profit matches reported activity. A UAE entity with strong reported profit but minimal reported headcount and assets is the classic profile that attracts scrutiny; one with substance to match its profit allocation is inherently lower risk.

No longer as an active filing obligation. The UAE's Economic Substance Regulations, originally introduced under Cabinet Resolution No. 57 of 2020 (as amended), required in-scope entities conducting a defined Relevant Activity to file an annual ESR notification and, where applicable, an ESR report. Under Cabinet Decision No. 98 of 2024, the ESR notification and report filing requirement was discontinued for financial years starting on or after 1 January 2023 — so most groups no longer have a live, ongoing ESR filing obligation for those periods. CbCR under Cabinet Resolution No. 44 of 2020 is unaffected by this change and continues to apply on its own terms, based on the group's consolidated revenue threshold.

CbCR is assessed against the group's own consolidated fiscal year, which may or may not align with individual Constituent Entities' local statutory or tax fiscal years, including the UAE entity's Corporate Tax period. We map the group's consolidated fiscal year end, the UAE entity's own tax period, and the resulting notification and filing deadlines separately, since a mismatch here is a common source of missed dates.

The obligation is assessed at the group level, so a newly incorporated UAE Constituent Entity within an already-reporting group typically needs to be added to the existing CbCR data set and entity listing for the current or next filing cycle, rather than triggering an entirely new, separate obligation. We treat new entity onboarding into an existing CbCR-reporting group as a defined step in our new entity setup process for clients already engaged with us on CbCR.

We maintain a standing working file for each CbCR client that carries forward the prior year's data, reconciliation methodology, entity classifications, and Master File/Local File cross-references, so each year's filing builds on a consistent base rather than starting from a blank page. Any change in classification, group structure, or transfer pricing policy is flagged and explained against the prior year's position.

We first assess the group's actual historical obligation — confirming the threshold was genuinely crossed and the classification was correct for the missed year — then work through a regularisation process: filing the outstanding notification and/or report, addressing any administrative penalty exposure under the current framework, and putting a forward calendar in place so it does not recur. Voluntary regularisation, done properly and promptly, is generally viewed more favourably than a filing that only happens after a query from the authorities.

Yes. An acquisition of the UPE typically changes the group's consolidated structure, potentially its Reporting Entity, its consolidated revenue threshold position, and its fiscal year alignment — all of which need to be reassessed. We treat any change of ultimate ownership at the top of the group as an automatic trigger to re-run the full CbCR classification and threshold analysis for the UAE entity.

We agree a fixed fee for the initial threshold assessment and entity classification phase, and a separate fixed or scoped fee for the annual notification and filing cycle once the obligation is confirmed, based on the number of jurisdictions and Constituent Entities involved. Both are confirmed in writing before work begins. Ongoing annual engagements are typically priced as a retainer that also covers the notification, reconciliation, and filing for that fiscal year.

A portal files a form. It does not assess whether your group's threshold classification is correct, does not cross-check the CbCR against your Master File and Local File, does not track the notification and the report as two separate deadlines, and is not present when a foreign tax authority sends a query eighteen months after the exchange. PNPC has advised cross-border groups on international taxation since 1986, with offices across Chennai, Bangalore, Hyderabad and Dubai. We treat CbCR as one part of a group's ongoing international tax position — not an isolated annual form.

Our direct filing capability covers the UAE (through our Dubai office) and India (through our Chennai, Bangalore and Hyderabad offices). For groups with Constituent Entities in other jurisdictions, we coordinate the UAE and India components directly and work alongside the group's local advisors in other countries to ensure the group's overall CbCR position — classification, data, and narrative — is consistent everywhere it is exchanged.

Treating the notification and the report as one obligation with one deadline, when they are legally and administratively separate. The second most common: preparing the CbCR data in isolation from the Master File and Local File, so the three documents tell inconsistent stories about the same group when a tax authority eventually reviews them together.

If growth projections suggest the group will cross the threshold within the next two to three fiscal years, building the data collection framework and reconciliation discipline in advance means the first mandatory filing year is a continuation of an existing process rather than a standing start under deadline pressure. For groups well below the threshold with no near-term growth plans crossing it, a lighter annual threshold-monitoring check is usually sufficient rather than a full advisory engagement.

They do not interact directly — UAE Corporate Tax under Federal Decree-Law No. 47 of 2022 applies a 9% rate on taxable income above AED 375,000 (with 0% below that threshold, and a separate 0% regime for qualifying income of Qualifying Free Zone Persons), and is assessed at the level of each individual UAE taxable person. CbCR is assessed at the consolidated group revenue level and does not depend on any single entity's Corporate Tax liability or rate. A UAE entity can have a modest, even zero, standalone Corporate Tax liability and still sit inside a group with a full CbCR obligation, because the group's total consolidated revenue — not the UAE entity's own tax bill — is what triggers CbCR.

An annual retainer that covers the following year's threshold re-assessment, entity classification review, notification filing, data collection coordination, reconciliation, XML preparation, and MoF submission — plus advisory support if a partner jurisdiction (including India) raises a query following automatic exchange of the group's CbCR data. We also flag, proactively, any changes to Cabinet Resolution No. 44 of 2020, its thresholds, or its administrative penalty framework that could affect the client's obligations.

Both, where the engagement calls for it. CbCR compliance and transfer pricing policy design are related but distinct workstreams — CbCR is a disclosure obligation built from data the group already generates, while transfer pricing policy involves setting or reviewing the actual intercompany pricing methodology (cost-plus, resale price, TNMM, or another OECD-recognised method) that produces those numbers in the first place. We scope each engagement to state clearly whether it covers CbCR compliance alone, or CbCR plus a Master File/Local File and underlying policy review.

The Notification is short — it identifies the Reporting Entity's name and tax jurisdiction, confirms the UAE entity's own classification (UPE, Surrogate Parent, or Constituent Entity relying on another jurisdiction's filing), and states the fiscal year covered. The CbCR report is the substantive filing: full country-by-country financial and headcount data across every jurisdiction the group operates in, plus entity-level detail on tax identification numbers, business activity classification, and permanent establishments. Preparing the notification typically takes a fraction of the time of preparing the full report, which is one reason the two are easy to mentally collapse into a single task even though they are legally separate filings.

For CbCR purposes, the entity's free zone or mainland status in the UAE does not change the group-level threshold test or the Reporting Entity's classification — those are assessed at the consolidated group level, not per UAE entity. What does matter is capturing every UAE Constituent Entity correctly in the group's entity list, including its own tax identification details, so the CbCR's UAE-jurisdiction figures are complete and not understated by omitting a free zone subsidiary that the finance team assumed was out of scope.

Yes — and this is precisely the kind of issue we prefer to catch before submission rather than after a foreign tax authority raises it. If the draft CbCR shows disproportionate profit allocated to the UAE jurisdiction relative to reported employees and tangible assets, we discuss with the client whether the reporting is complete and accurate (sometimes assets or headcount are simply mis-captured) and, separately, whether the underlying transfer pricing policy driving that profit allocation is itself defensible. We do not alter figures to make them look better — we identify whether the reported position is accurate and, if it is, whether it needs a stronger explanatory narrative in the Local File.

It can, if the change affects how consolidated revenue, profit, or capital figures are calculated or presented. We ask new and returning CbCR clients whether there has been any change in the group's external auditor, accounting standard (for example, a shift between local GAAP and IFRS at the consolidation level), or consolidation methodology since the prior filing year, because any of these can shift the reported figures in ways that need to be explained if the CbCR shows a discontinuity from the prior year that is not driven by an actual change in business activity.

Yes. Every Constituent Entity of the group — including dormant entities holding minimal activity or a single asset — must be listed in the CbCR's entity-level detail, with its own tax identification number and business activity classification (the CbCR's prescribed activity list includes a 'dormant' category specifically for this purpose). Omitting a dormant entity from the group's entity list is a completeness error, not a simplification.

The two are set separately. The CbCR report itself is due within twelve months of the end of the group's reporting fiscal year. The notification — identifying which entity is the Reporting Entity and in which jurisdiction — is due by the end of the reporting fiscal year (or within the specific window set under Cabinet Resolution No. 44 of 2020 and its Ministerial Decisions), which in practice usually falls months before the report is due. So the notification is chronologically first even though it is the smaller filing. We confirm the exact current dates for your group's specific fiscal year at engagement start, because these are set by law and can be revised.

It exists independently. CbCR under Cabinet Resolution No. 44 of 2020 predates the UAE Corporate Tax regime (Federal Decree-Law No. 47 of 2022) and continues on its own terms — a group can be within CbCR scope years before it has any Corporate Tax filing history. What Corporate Tax added is the Master File and Local File transfer pricing documentation layer, which now has to tell a story consistent with what the CbCR discloses. So the two regimes are separate obligations that increasingly have to be read together, not one replacing the other.

The split of revenue between related-party and unrelated-party amounts, and the full-time-equivalent employee count per jurisdiction, are consistently the two hardest. Many group ERPs do not tag intercompany revenue in a way that maps cleanly to the CbCR's related/unrelated distinction, and headcount is often held in a separate HR system that counts contractors and part-timers inconsistently across countries. Income tax paid on a cash basis versus accrued is the third — local finance teams frequently report one when the schema asks for both.

It varies entirely by jurisdiction and the type of query, but the more important point is timing of arrival: queries commonly surface twelve to twenty-four months after the CbCR is exchanged, long after the UAE finance team has moved on to the next year's filing. By then the people who prepared the report may have changed, and the reconciliation working papers are the only reliable record of how each figure was derived. That is why we retain the submitted XML, the reconciliation file, and the classification memo as a dedicated per-year archive.

The three things that unblock everything else are the Ultimate Parent Entity's consolidated financial statements for the preceding fiscal year, a current and complete group organisation chart showing every Constituent Entity and its tax residence, and confirmation of the parent jurisdiction's own CbCR position and whether it has an effective exchange relationship with the UAE. With those in hand we can run the threshold test and entity classification quickly; without them the engagement stalls at the first step.

The visible task — uploading a file to the MoF portal — gets done, but the underlying exposures do not get caught: an incorrect threshold or entity classification, a CbCR that does not reconcile to the consolidated accounts, a profit-to-substance mismatch that a partner jurisdiction will flag, or a missed notification. Each of these surfaces later as an administrative penalty or, more expensively, a transfer pricing enquiry in a receiving jurisdiction that costs far more to resolve than correct advisory would have cost upfront.

A reviewing tax authority reads the CbCR as a heat map: it looks for jurisdictions where the group reports significant profit but few employees and little tangible-asset value, because that combination suggests profit may be booked where the real economic activity is not. If the UAE row shows strong profit with thin substance, a partner jurisdiction receiving the exchanged report can open a transfer pricing enquiry challenging the pricing that put the profit there. The CbCR does not itself adjust anything — it is the selection tool that decides whose transfer pricing gets examined.

CbCR advisory is largely a professional-fee engagement — the main external variable is any MoF portal charge and, for India-linked groups, the India-side filing and certification costs on Forms 3CEAC/3CEAD. We separate our professional fee from those third-party items and confirm the latter at execution time rather than publishing a guessed figure, because both the UAE administrative penalty schedule and any portal charges are set by law or authority and can be revised.

If the threshold, notification window, filing format, or penalty framework is amended while we are engaged, we assess the impact on the group's current-year position, update the applicability memo and deadline calendar, and adjust the filing approach before submission. Because our engagement model carries a standing working file forward year to year, a change is applied against a known baseline rather than requiring the whole analysis to be rebuilt.

They have to name the same Reporting Entity and jurisdiction consistently. If the UPE is in India and files there under Section 286 using Forms 3CEAC and 3CEAD, the UAE Constituent Entity's notification must confirm that Indian entity as the Reporting Entity — and the financial data attributed to the UAE and India rows in the single group CbCR must match what each jurisdiction sees. A UAE notification pointing to one Reporting Entity while the India filing names another is a visible inconsistency once both are in the exchange network.

The MoF filing acknowledgement, the submitted XML, the reconciliation working papers tying every CbCR figure to the consolidated accounts, the threshold-and-classification memo for the year, the data templates returned by each Constituent Entity, and a short note on any anomalies or accounting-standard changes explained. It is built so that if a partner-jurisdiction query arrives eighteen months later — after staff turnover — a new finance lead can reconstruct exactly what was filed and why, without re-doing the work.

CbCR advisory itself is a compliance-and-documentation engagement. It escalates when a partner jurisdiction moves from a risk-assessment query to a formal transfer pricing adjustment or dispute — at that point our transfer pricing specialists lead the defence, and where a jurisdiction's procedure requires legal representation or a Mutual Agreement Procedure under a tax treaty, we coordinate with counsel. CbCR advisory then becomes an evidential input to that larger matter rather than the whole engagement.

Yes — this is a large part of our CbCR work. The first step is a diagnostic: confirm whether the threshold was genuinely crossed and the entity classification was correct for the filed year, check whether the notification and report were both filed and on time, and test whether the submitted figures actually reconcile to the consolidated accounts. From there we decide whether to correct, re-file, or voluntarily regularise a missed obligation, and we put a forward calendar in place so the same gap does not recur.

The rate-limiting factor is almost always data collection across the group's Constituent Entities, not the UAE-side technical work. Timeline depends on the number of jurisdictions, whether fiscal year ends are aligned, how many ERP systems the data has to be pulled from, whether the related/unrelated revenue split and FTE headcount are readily available, and whether this is a first filing or a continuation of an existing working file. A first-year multi-jurisdiction engagement is typically 8-10 weeks; a continuation year with a mature template is materially faster.

Before submission we run four checks: the threshold and entity classification against the current Cabinet Resolution; the reconciliation of every CbCR figure back to the consolidated financial statements; the internal consistency of the CbCR against the group's Master File and Local File narrative; and XML schema validation against the current version to catch jurisdiction-code, currency-code, and TIN-format errors. Any anomaly — a profit-to-substance mismatch, a year-over-year discontinuity, an accounting-standard change — is documented with an explanatory note before filing, not left to be queried afterward.