Country-by-Country Reporting: Reconcile Entities and Data Sources
A practical guide to country-by-country reporting, with a worked example, evidence checklist, common mistakes and steps to prepare a defensible working.
AI Summary
Group entities use different currencies, year-ends and definitions of revenue. The useful result is a working that explains the facts, the calculation or classification, and the evidence behind the conclusion. This guide shows how to prepare that working and where a reviewer should investigate before accepting the result.
Scope and applicable period
Indian transfer-pricing documentation for FY 2025–26 / AY 2026–27, with legacy provision references. For Tax Year 2026–27, use the Income-tax Act, 2025 and Income-tax Rules, 2026; OECD guidance does not override Indian law.
Verification date: 11 October 2026. Figures and rates identified as assumptions are teaching examples; apply the stated conditions and the actual facts to a real assignment.
The key principle
Country-by-country reporting is a group-level transparency framework, not a substitute for an entity’s transfer-pricing study. Determine the relevant jurisdiction’s applicable reporting and notification obligations before preparing the data. Identify constituent entities, tax jurisdictions and the group reporting year. Reconcile revenues, profit, tax and other data using the selected consistent sources, explaining differences from local statements.
Worked example
| Item | Value or fact | What it means |
|---|---|---|
| Entity A revenue | ₹100 crore | Check related/unrelated split |
| Entity B revenue | ₹40 crore | Same reporting-year basis |
| Local-to-group adjustment | ₹5 crore | Document direction and nature |
| Combined illustrative revenue | ₹145 crore | Not a reporting-threshold example |
The ₹145 crore total demonstrates reconciliation only; it says nothing about whether the group is legally required to file. Check current Indian section 286 and relevant reporting rules for legacy periods, and the applicable provisions under the new framework for later periods. Do not calculate eligibility from this two-entity example. Apply the relevant CbCR instructions consistently to permanent establishments, tax paid versus accrued and group consolidation differences. Record the reporting entity and data owners so that unresolved jurisdictional items are visible.
A practical sequence
Determine the relevant reporting entity, group year and jurisdictional obligations first. Build the constituent-entity list and assign owners to data fields.
Apply the prescribed definitions and consistent data-source policy, then reconcile currency and period differences. Review tax paid, tax accrued and revenues independently.
Preserve source bridges and unresolved issues with the approved report so that group totals can be reconstructed without assuming they equal consolidated accounting totals.
Important distinction
The 2026 rules introduce corresponding reporting forms under the new Act. Keep the report year and applicable law explicit in the obligation memorandum. This guide does not provide a group-revenue threshold table: confirm the current legal threshold, reporting-entity conditions and notification duties from the applicable framework.
Separate the factual file from the pricing conclusion
Transfer pricing depends on reliable transaction facts and comparability. Contracts, actual conduct, segment accounts and external evidence should tell a consistent story. A margin calculation is only one part of the analysis: the method, tested party, profit indicator, comparable data and adjustments all need reasons. Keep assumptions visible, preserve original data and reconcile the study with reported transactions. OECD materials help analyse issues, but the applicable Indian provisions and rules govern the Indian compliance conclusion. Do not treat a sample percentage, a contractual charge or a favourable comparable as an automatic arm’s-length result.
Evidence checklist
Keep the following records linked to the same entity, period and working version. Identify missing items explicitly; a checked box should mean the document was examined and supports the stated conclusion.
- Group entity and jurisdiction list
- Reporting-year and obligation assessment
- Data-source policy
- Revenue/profit/tax bridges
- Reporting-entity and notification records
Common mistakes and how to avoid them
- Using entity turnover as the group threshold. Compare the conclusion with the group entity and jurisdiction list and resolve any conflicting facts.
- Confusing tax paid with tax accrued. Trace the affected item to the data-source policy before finalising the working.
- Treating CbCR figures as direct arm’s-length results. Use the reporting-entity and notification records to make the final position and remaining exceptions clear.
Before you finalise
Recheck the example’s assumptions against the actual assignment, resolve the identified exceptions and make the final figure or conclusion traceable to its source. Preserve the reviewed version and the reason for material changes. For this task, the reporting-entity and notification records should agree with the conclusion presented to the client, reviewer or authority.
Frequently asked question
Must every local statutory figure equal CbCR data? Not necessarily. The applicable source rules and group basis may differ; explain and consistently document the bridge.
Sources and further reading
- CBDT Notification 22/2026 — Income-tax Rules 2026 and CbCR form
- OECD — India CbCR peer review, 2025
- Income-tax Act, 2025, amended by Finance Act 2026
Related guide: Master file cbcr filing ay 2026 27 due dates applicability.