Country-By-Country Reporting in UAE: Cbcr Obligations

A country-by-country report is not a tax return, and filing one settles nothing. It fixes no liability, closes no year, and stands as no agreement with the Federal Tax Authority about where a group's profit arose. Groups that treat the submission as an account rendered and accepted have misread what the document is for. The report is an intelligence instrument. It sets out, jurisdiction by jurisdiction, where a multinational group books revenue, where it books profit, what tax it pays and where its economic activity actually sits, and it invites the reader to ask why those four maps do not lie on top of one another.

Two further assumptions fail just as quietly. The first is that information handed to the FTA stays with the FTA. The regime was built to move data across borders: the UAE has arrangements with other jurisdictions under which country-by-country information is exchanged, so a figure entered on a UAE filing is read by tax administrations elsewhere. The second is that a group whose parent files at home has nothing left to do here. Notifying and filing are separate duties running on separate clocks, and the presence of a foreign parent changes who carries the reporting obligation in the UAE rather than removing it.

What the regime does impose is narrow enough to state plainly. One revenue threshold decides whether a group is in scope at all. Two deadlines, both counted from the end of the group's fiscal year, govern the notification and the report. One prescribed electronic format governs how the report is accepted. And two further documents — the master file and the local file — are prepared and kept rather than lodged, which is the part most often mistaken for an absence of obligation.

Related Services: Explore our company formation and UAE compliance and intellectual property advisory services for practical legal support in this area.

The threshold that puts a group in scope

Country-by-country reporting in the UAE follows the approach set out in Action 13 of the OECD's Base Erosion and Profit Shifting project, and it borrows that project's size filter. The obligation attaches to multinational enterprise groups whose consolidated group revenue for the preceding fiscal year exceeded AED 3.15 billion, a figure of roughly USD 860 million and the local expression of the threshold used internationally.

Three features of that test are worth reading slowly. It is a group test, not an entity test: the revenue that matters is the consolidated figure for the whole multinational group, not the turnover of whichever UAE company happens to be looking at the question. It is measured on the preceding fiscal year, so a group crosses the line on the strength of a year already closed, not on the year it is currently living through. And it is a threshold rather than a sliding scale — a group either sits above it and reports in full, or sits below it and does not report at all.

The practical consequence is that scope can be known in advance. A group that finishes a fiscal year a little over the line knows during the following year that it will be reporting, and knows its deadlines before they start running. A group hovering near the threshold, particularly one making acquisitions or disposals, is better served by testing the projected consolidated figure ahead of each year-end than by discovering the answer once the clock has already been running for several months.

Who reports when the ultimate parent sits abroad

Where the ultimate parent entity of the group is resident in the UAE, the position is straightforward: that entity files the country-by-country report with the FTA. The harder and far more common case in this jurisdiction is the group whose ultimate parent sits somewhere else and whose UAE presence is a subsidiary, a regional headquarters or a holding company.

In that case the regime looks for a surrogate parent entity in the UAE — an entity within the group, resident here, identified and designated to discharge the reporting obligation in place of the foreign parent. The point of the mechanism is accountability with an address. A tax authority cannot usefully pursue a parent company beyond its reach, so the rules require that a group with a UAE footprint name someone here who answers for the filing.

Designation is a decision the group makes, and it is worth making deliberately rather than by default. Consider a group headquartered in Europe with three UAE companies: an operating business in a free zone, a small services entity and a dormant holding vehicle. Any of them might be named. The one that should be named is the one with the finance function, the accounting records and the people to answer questions twelve months later — not the one that happens to sit highest on the organisational chart. The obligation, once designated, is real work rather than a formality, and it should sit where the work can actually be done.

Two clocks, both counted from fiscal year-end

The regime imposes two dated duties, and both are measured from the close of the group's fiscal year rather than from any calendar date, any assessment, or any request by the authority.

Duty	Counted from	Falls due
Notification of the reporting obligation	End of the group's fiscal year	Three months later
Filing of the country-by-country report	End of the same fiscal year	Twelve months later

The notification comes first and is the lighter of the two: it tells the FTA that a reporting obligation exists and identifies who will discharge it. The report itself follows, leaving the nine months between the two dates to assemble it. That gap is not generous once the work is understood — the report draws on figures for every jurisdiction in which the group operates, and those figures come from entities on different systems, in different currencies, closing their books at different speeds.

The two duties are independent. Meeting the twelve-month deadline does not cure a notification that was never made, and a notification made on time does not excuse a late report. A group that has read only the headline filing date will already have missed the first obligation nine months before the second one falls due, which is the most avoidable failure in the whole regime. An internal compliance calendar should carry both dates the moment a fiscal year closes above the threshold, and should carry them as two separate entries rather than one.

The portal and the schema it expects

The report is submitted electronically through the FTA's online portal, and it must conform to the XML schema prescribed by the OECD for country-by-country reporting. This is a technical requirement with a substantive purpose: the schema is what allows a report received in the UAE to be processed automatically and exchanged with another jurisdiction without being re-keyed by hand.

The practical effect on a finance team is that presentation is not free. A report that would read perfectly well as a spreadsheet can still fail as a submission if the file is structurally malformed, if fields the schema treats as mandatory are absent, or if values do not carry the codes the schema expects. Groups that leave the mapping exercise to the final weeks tend to discover this at the worst possible moment.

The sensible sequence fixes the data model first and worries about the deadline second. Decide once, across the group, how each jurisdiction's revenue, profit, tax paid, tax accrued, capital, earnings, headcount and tangible assets will be sourced and defined; then map those definitions to the schema fields; then test a complete submission well before it is due. Groups that already report under the other automatic exchange regimes will recognise the pattern, because those regimes turn on the same thing — getting a defined file, in a defined format, through a portal on a defined date.

Master file and local file: held, not filed

The country-by-country report is one of three documents, and the other two behave differently. The master file gives a tax authority the group-level view: the organisational structure, a description of the group's business, its intangibles, its intercompany financial arrangements, and the transfer pricing policies applied across the group. The local file narrows to the UAE, documenting material transactions between related parties here — their nature and terms, the transfer pricing methods applied to them, and the supporting financial information. Both are expected to be prepared consistently with the OECD Transfer Pricing Guidelines, so a group already producing them for another jurisdiction is not starting from nothing.

Neither file is submitted alongside the country-by-country report. They are prepared and maintained contemporaneously, and made available to the authorities on request within the timeframe specified. This is where the assumption at the start of this article does its most expensive work: because nothing is lodged, nothing appears to be owed, and the files get drafted only once a request arrives — at which point the documentation is being written after the fact, by people reconstructing decisions taken years earlier, against a running clock.

Contemporaneous preparation means what it says. The master file and the local file should exist in finished form on the same rhythm as the report itself, and the supporting material behind them should be retained long enough to answer questions raised well after filing; the framework contemplates a retention period of at least ten years for that material. A file written while the transactions are fresh reads as a record. A file written after a request reads as an argument, and tends to be treated as one.

What non-compliance actually costs

Failure to file the report, failure to submit the notification, and filing that is late, incomplete or inaccurate all attract administrative penalties under the UAE's tax procedures framework, imposed by the FTA rather than negotiated with it. Those penalties are the visible cost and usually the smaller one.

The larger exposure is what a defective filing invites. Country-by-country data is read as a screening tool, so a group whose report shows profit concentrated where its people are not can expect transfer pricing enquiries, requests for the master and local files it may not have prepared, and adjustments that flow through into reassessment. Because the same information is exchanged with other jurisdictions, an inconsistency is not contained: a figure filed in the UAE may sit alongside a different figure filed elsewhere by the same group, and the mismatch surfaces in two administrations at once, with double taxation a realistic outcome of the dispute that follows.

None of this is peculiar to country-by-country reporting. It is the logic of every transparency regime now layered over UAE groups, beneficial ownership reporting included: the filing itself is cheap, the information it leaves behind is durable, and the cost of getting it wrong arrives later and from a direction the filer was not watching.

A working order of operations

• Test the group, not the entity. Take the consolidated revenue of the whole multinational group for the preceding fiscal year and measure it against AED 3.15 billion.
• Settle who reports. Where the ultimate parent is abroad, identify and designate a UAE surrogate parent entity that has the records and the people to support the filing.
• Diarise both dates at year-end. Notification at three months, report at twelve, each counted from the close of the fiscal year.
• Build to the schema early. Fix definitions and field mapping, then test a full submission through the portal before the deadline rather than on it.
• Keep the master and local files current. Prepare them as the year runs and retain the supporting material, so that a request is answered from a file rather than from memory.

Disclaimer

This article is for informational purposes only and does not constitute legal advice.

Additional Resources

Explore more of our insights on related topics:

• FATCA compliance UAE US tax reporting
• beneficial ownership reporting UAE UBO compliance
• common reporting standard UAE CRS AEOI
• UAE tax compliance calendar filing deadlines