Country-by-country reporting: what it is and how to comply

For multinational groups operating across borders, tax transparency has never been more important. Country-by-country reporting (CbCR) sits at the heart of that transparency push, requiring groups to disclose detailed financial and operational data for every jurisdiction they operate in. Whether a group is navigating this for the first time or refining an existing process, understanding the rules, the data requirements, and the common pitfalls is essential to staying compliant and audit-ready.

CbCR was introduced as part of the OECD’s Base Erosion and Profit Shifting (BEPS) project and has since been adopted by tax authorities across the globe. For growing, multi-entity organisations, it represents one of the more demanding compliance obligations in the transfer pricing landscape. This guide walks through everything finance teams need to know, from who qualifies to how to build a process that holds up under scrutiny.

Who Must File a Country-by-Country Report

CbCR requirements apply to multinational enterprise groups that meet a specific revenue threshold. Under the OECD framework, the obligation falls on groups with consolidated annual revenues of 750 million euros or more in the preceding fiscal year. The ultimate parent entity is typically responsible for filing, though local filing obligations can also apply to subsidiaries in certain jurisdictions.

It is worth noting that many countries have adopted this threshold directly, but some have introduced lower thresholds or additional local requirements. Groups operating in the EU, UK, US, Australia, Canada, and most OECD member countries will almost certainly face CbCR obligations if they clear the revenue bar. Even groups approaching that threshold should monitor their position carefully, as rapid growth can trigger the requirement with little lead time.

Key Data Points Covered in a CbCR

A country-by-country report is a structured snapshot of a group’s global footprint. Rather than summarising consolidated results, it breaks down financial and operational information on a jurisdiction-by-jurisdiction basis, giving tax authorities a clear view of where value is created and where profits are reported.

The core data points required in a standard CbCR include:

Revenue split between related-party and third-party sources
Profit or loss before income tax
Income tax paid and income tax accrued
Stated capital and accumulated earnings
Number of employees on a full-time equivalent basis
Tangible assets other than cash and cash equivalents
A list of constituent entities in each jurisdiction and their main business activities

This combination of financial and operational data allows tax authorities to identify mismatches between where economic activity takes place and where profits are declared. That is precisely why accuracy matters so much. Even minor inconsistencies between the CbCR and other transfer pricing documentation can attract scrutiny.

How Country-by-Country Reporting Fits Into BEPS Action 13

CbCR is one pillar of a three-tier documentation framework established under BEPS Action 13. Understanding where it sits within that broader structure helps clarify its purpose and why tax authorities treat it as a risk-assessment tool rather than a standalone compliance form.

The three tiers are:

Master File — a high-level overview of the group’s global business, including its organisational structure, value chain, and transfer pricing policies
Local File — detailed information on specific intercompany transactions in each jurisdiction, including benchmarking analysis
Country-by-Country Report — the jurisdiction-level financial and operational data described above

Together, these three documents are designed to give tax authorities a consistent, comparable picture of multinational tax reporting across borders. The CbCR is shared between jurisdictions through automatic exchange mechanisms, meaning a filing in one country can inform an audit in another. This interconnectedness is what makes CbCR compliance so consequential for groups with complex structures.

Submission Rules and Deadlines by Jurisdiction

One of the trickier aspects of country-by-country tax compliance is that filing deadlines and submission rules vary significantly between jurisdictions. While the OECD framework provides a common standard, each country implements it through its own domestic legislation.

In most jurisdictions, the CbCR must be filed within 12 months of the end of the reporting fiscal year. For a group with a December year-end, that typically means a filing deadline of 31 December the following year. However, some countries require earlier submissions, and local notification requirements can add another layer of complexity. Many jurisdictions require constituent entities to notify their local tax authority of who the reporting entity is and where the report will be filed, often well before the report itself is due.

Key points to track across jurisdictions include:

Whether local filing is required or whether exchange of information from the parent’s filing is sufficient
The specific notification deadline for constituent entities
Whether the jurisdiction accepts XML schema submissions or requires a different format
Penalty regimes for late or inaccurate filings

With obligations potentially spanning dozens of countries simultaneously, keeping a centralised calendar of deadlines is not optional. It is a basic operational requirement.

Common Compliance Pitfalls and How to Avoid Them

Even well-resourced finance teams run into difficulties with CbCR. The most common issues tend to stem not from a lack of intent but from fragmented data, inconsistent definitions, and insufficient coordination between group entities.

Inconsistent data across entities

When each entity in a group uses different accounting systems, chart-of-accounts structures, or reporting currencies, aggregating reliable CbCR data becomes genuinely difficult. Figures that look correct at the local level can produce misleading totals when combined. Investing in consistent data standards across entities is one of the most effective ways to reduce this risk.

Misalignment between CbCR and other documentation

Tax authorities frequently cross-reference CbCR data against the master file, local files, and statutory accounts. Discrepancies between these documents, even ones that have innocent explanations, can trigger enquiries. Groups should build a review process that checks CbCR figures against related documentation before submission.

Missing or late notifications

Notification requirements are often overlooked, particularly in jurisdictions where the group has a smaller presence. Missing a notification deadline can result in penalties even if the substantive report is filed correctly and on time. A centralised compliance calendar that captures both notification and filing deadlines is essential.

Treating CbCR as a one-off exercise

Some teams approach CbCR as an annual scramble rather than an ongoing process. That approach creates unnecessary pressure and increases the risk of errors. Building CbCR data collection into the regular close cycle means the information is available and validated when it is needed.

Steps to Build a Reliable CbCR Process

A sustainable CbCR process is one that produces accurate, consistent data year after year without requiring heroic efforts from the finance team. Building that process takes deliberate design, but it pays dividends in reduced risk and lower compliance costs over time.

The following steps provide a practical starting point:

Map the group structure — Maintain an up-to-date list of all constituent entities, their jurisdictions, and their principal activities. This should be a living document that reflects acquisitions, disposals, and restructurings in real time.
Standardise data definitions — Agree on consistent definitions for employee headcount, revenue categorisation, and asset values across all entities. Ambiguity at this stage creates problems in aggregation.
Centralise data collection — Rather than chasing entity controllers for figures at year-end, build a structured data collection process that runs in parallel with the group close. This reduces last-minute pressure and improves data quality.
Build in a review layer — Before submission, run the CbCR data through a validation process that checks for internal consistency and flags anomalies for review.
Track deadlines proactively — Maintain a jurisdiction-by-jurisdiction compliance calendar that captures both notification and filing deadlines, with sufficient lead time for review and sign-off.
Leverage purpose-built tools — Spreadsheet-based processes are difficult to audit and prone to version-control errors. Platforms designed for group reporting and CbCR compliance provide structured workflows, validation rules, and audit trails that manual processes cannot match.

For groups already running a consolidated reporting process, integrating CbCR into that workflow is a natural step. Our AARO country-by-country reporting module is built precisely for this purpose, connecting directly to the group consolidation engine so that the data used for financial reporting and the data submitted for CbCR compliance come from the same validated source. That consistency is what keeps discrepancies out of the picture.

As tax authorities continue to invest in data analytics and cross-border information exchange, the quality bar for CbCR submissions will only rise. Groups that build robust, repeatable processes now will be far better positioned to meet that bar and to respond confidently if questions are ever raised. If you want to see how we approach CbCR compliance, explore our dedicated CbCR solution and how it fits into the broader AARO reporting platform.