
Country by Country Reporting Is a Data Problem First
The tax technical questions in a CbCR filing are usually settled early. What consumes the months is assembling figures that live in different systems, on different bases, in different entities.
- CbCR asks for figures by tax jurisdiction. Your systems hold figures by legal entity and by management structure, and neither maps cleanly.
- The reported numbers will not tie to statutory accounts or to consolidated reporting, and that is expected rather than an error.
- What matters is that the differences are explainable. A reconciliation from a known source to the reported figure is the whole defence.
- Six data elements carry most of the effort, and headcount and tangible assets are consistently the worst two.
- Build a source map once, with an owner per element per jurisdiction, and the annual exercise stops being a rediscovery.
A country by country report asks for revenue, profit, tax paid, tax accrued, capital, earnings, employees, and tangible assets, broken down by tax jurisdiction.
None of those are difficult concepts. The difficulty is that your systems record by legal entity, your management reporting records by business unit, your payroll records by employing entity, and your fixed asset register records by location, and no two of those agree about where anything sits.
So the technical tax discussion finishes in a week and the data assembly takes a quarter, which is the reverse of what most people expect the first time they run it.
Why the assembly is the hard part
The tax positions in a CbCR are usually well understood. The group knows where its entities are, what they do, and roughly what they earn.
The report asks for that information organised by tax jurisdiction, which is a dimension most finance systems do not carry as a native attribute. Legal entity is close and not identical, particularly where an entity has a permanent establishment elsewhere or operates across borders.
Every element then needs its own mapping. Employees map from payroll, tangible assets from the fixed asset register, revenue from the ledger with a related party split, and each mapping is built by a different team with a different definition of the same word.
| Element | Usual source | Where it goes wrong |
|---|---|---|
| Revenue, related and unrelated | General ledger with a counterparty flag | The related party split is often not maintained at transaction level, so it has to be derived after the fact |
| Profit before tax | Statutory or consolidation reporting | Which basis, and consistently applied across all jurisdictions rather than whichever was available per entity |
| Tax paid on a cash basis | Treasury and tax payment records | Payments made by one entity on behalf of another, and payments spanning periods |
| Tax accrued | Tax provision workings | Current versus deferred, and the treatment of prior year adjustments |
| Stated capital and accumulated earnings | Statutory accounts | Definitions vary between jurisdictions, so a consistent group definition has to be chosen and documented |
| Employees and tangible assets | Payroll and the fixed asset register | The two worst elements. Headcount basis and asset location both require decisions nobody has previously had to make explicit |
The last row consumes disproportionate time every year unless the basis is documented once and reused.
Headcount and assets are the two that hurt
Employees looks trivial until you have to pick a basis. Headcount at year end, average over the year, or full time equivalent. Employed by the entity, or working in the jurisdiction. Contractors included or not. Every one of those choices changes the number.
Tangible assets is the same problem in a different register. Assets are recorded where they were purchased, where they are booked, or where they physically sit, and those three diverge for anything mobile.
Neither has a single correct answer that applies everywhere. What matters is choosing a basis, documenting it, and applying it consistently across jurisdictions and across years, because a basis that changes silently between filings is the pattern most likely to attract a question.


Build the reconciliation, expect the differences
CbCR figures will not agree with your consolidated accounts. The reporting perimeter differs, eliminations work differently, and the bases are not the same.
That is anticipated by everyone reading the report. What is not anticipated is a set of figures with no traceable path back to a source, which is the position a group ends up in when the assembly is done manually under deadline and the workings are not retained.
The reconciliation does not need to be elegant. It needs to start from an identified source figure, show each adjustment with a reason, and arrive at the reported number.
Build the entity to jurisdiction map first
Including permanent establishments and any entity operating across borders. This map is the spine of the whole exercise and it changes as the group changes.
Write a definition for each element, once
Headcount basis, asset location basis, related party flag derivation, profit basis. One page, agreed, and reused every year.
Name an owner per element per jurisdiction
Not per element globally. The person who can answer a question about payroll in one country is rarely the person who can answer it in another.
Assemble from source with the workings retained
The intermediate files are the reconciliation. Discarding them is what makes next year's exercise a rediscovery.
Reconcile each element to a known source figure
Consolidated revenue, group headcount, group net book value. Differences are expected and should be listed with reasons.
Compare year on year before filing
A jurisdiction whose figures moved sharply without a business reason is usually a mapping change rather than a real movement.
The tax questions finish in a week. The data assembly takes a quarter.
ChatFinAssembling the elements from source, with the workings kept
ChatFin is an AI platform for the financial close, built for enterprise finance teams and connected directly to the ERP you already run, including Oracle NetSuite, SAP Business One, JD Edwards, Acumatica, Microsoft Dynamics 365, and Sage Intacct.
For country by country reporting, a ChatFin agent assembles the ledger based elements directly from the ERP against your entity to jurisdiction map, derives the related party revenue split from counterparty data rather than from a manual flag, and retains the intermediate workings as the reconciliation.
It compares each element year on year by jurisdiction and flags movements that look like mapping changes rather than business changes, before the filing rather than after. ChatFin agents read live ERP data rather than a static export, and every action they take is prepared as a draft that a named person reviews and approves before anything posts. The approval record is retained, which is what turns an automated step into evidence rather than a gap in the trail.
Talk to us about this workflow
Frequently Asked Questions
Why is country by country reporting a data problem?
Because the report asks for figures by tax jurisdiction, and finance systems record by legal entity, business unit, employing entity, or physical location. None of those correspond exactly to tax jurisdiction, so every data element needs its own mapping, built by a different team with a different working definition.
Should CbCR figures tie to the statutory accounts?
No, and they generally will not. The reporting perimeter, the eliminations, and the bases differ. What is expected is that the differences are explainable through a documented reconciliation from an identified source figure to the reported number, with each adjustment carrying a reason.
Which data elements are hardest to assemble?
Employees and tangible assets, consistently. Headcount requires choices about basis, timing, and whether contractors count. Tangible assets requires a decision about whether location means where an asset was purchased, where it is booked, or where it physically sits. Neither has a universally correct answer.
What matters most about the chosen basis?
Consistency. Several bases can be defensible, but a basis that changes between filings without explanation is the pattern most likely to attract questions. Document the choice once, apply it across all jurisdictions, and reuse it year on year.
How do you make next year easier?
Retain the workings. The intermediate files produced during assembly are the reconciliation, and discarding them turns the following year into a rediscovery exercise rather than a refresh. A documented entity to jurisdiction map with a named owner per element per jurisdiction does the rest.
References and further reading
- OECD tax transparency and country by country reporting for the international framework behind country by country reporting.
- Thomson Reuters ONESOURCE for tax reporting and CbCR preparation software.
- insightsoftware, maker of Longview whose Longview products cover tax and statutory reporting.
- IFRS Foundation for the reporting requirements underlying the source figures.
The workings are the reconciliation.
Most of the annual pain in a CbCR filing is rediscovery, because last year's intermediate files were not kept and the basis decisions were never written down.
ChatFin can assemble the ledger based elements from your ERP against the jurisdiction map and retain the workings as the reconciliation.
Book a DemoSee this running against your own ledger.
We will look at the accounts, the entries, and the evidence trail behind them in your ERP, and show what an agent prepares before a person approves it.
Image credits. Photography via Pexels, free to use under the Pexels License (commercial use, no attribution required). Photographers are credited beneath each image as a courtesy. Product visuals and all diagrams © ChatFin; diagrams may be reproduced with attribution and a link to this page.
Disclaimer. This article is general information on accounting and close operations, not accounting, audit, tax, or legal advice. Confirm the treatment of any specific transaction with your own advisors and auditors. Third party product names are the property of their owners and are referenced descriptively only.