A single spreadsheet now decides whether your tax department spends 2026 quietly closing books or scrambling to defend transfer pricing positions in five jurisdictions at once. That spreadsheet is the one your team submits behind Form 8975 — the IRS country-by-country report — and the data it carries travels much further than most controllers realize.
If your U.S. multinational enterprise (MNE) group had $850 million or more in consolidated revenue in the preceding year, you owe the IRS a Form 8975 with one Schedule A for every tax jurisdiction in which any constituent entity is resident. From the IRS the data flows, under bilateral competent authority arrangements, to every tax administration where you operate. Those administrations use it to flag transfer pricing risk, screen for permanent establishment exposure, and — starting with this filing cycle — feed the OECD's Pillar Two global minimum tax safe harbors.
This guide walks through who must file, what the report actually contains, how the $850 million threshold is tested, what's changed for the 2026 cycle, and the most common mistakes that turn an annual compliance task into an audit notice.
What Country-by-Country Reporting Actually Is
Country-by-country reporting (CbCR) was born out of the OECD's Base Erosion and Profit Shifting (BEPS) project, specifically Action 13. The premise was simple: large multinationals were reporting enormous profits in low-tax jurisdictions where they had only a handful of employees and no tangible assets, and tax administrations had no efficient way to see the pattern across borders.
The fix was a standardized one-page-per-country summary, filed once at the parent-entity level and exchanged automatically among the tax authorities of the countries where the group does business. The United States adopted this framework through final regulations under Treas. Reg. §1.6038-4 and operationalized it through Form 8975 and Schedule A (Form 8975).
Form 8975 itself is short — it identifies the U.S. ultimate parent entity, the reporting period, and the number of Schedules A attached. The substance lives in Schedule A: one schedule per tax jurisdiction, summarizing revenue, profit, taxes paid, capital, accumulated earnings, headcount, and tangible assets aggregated across every group entity resident there.
Who Must File: The Four-Part Threshold Test
Not every U.S. multinational owes Form 8975. The filing requirement is narrowly defined, and getting the threshold analysis wrong in either direction is a costly mistake.
A U.S. person must file if all of the following are true:
- It is the ultimate parent entity of a U.S. MNE group. The ultimate parent is generally the entity that is required to consolidate the group's financial statements under U.S. GAAP — or that would be required to consolidate if it were publicly traded — and that is not itself consolidated by another entity.
- The group is a multinational, meaning at least two constituent entities are resident in different tax jurisdictions, or one entity is resident in one jurisdiction and is subject to tax in another based on a permanent establishment.
- The group's annual revenue in the preceding reporting period was $850 million or more, measured on a consolidated basis using U.S. GAAP.
- The reporting period is the fiscal year used for the parent's consolidated financial statements, not necessarily the U.S. tax year.
Three details routinely trip up filers. First, the threshold is tested against the preceding year's revenue, so a group that crosses $850 million in 2025 first files for the 2026 reporting period. Second, "revenue" for this purpose includes ordinary income, extraordinary income, and gains from investment activities — broader than what most groups think of when they say "revenue." Third, joint ventures accounted for under the equity method are generally not constituent entities, but joint ventures that are line-item consolidated are.
The $850 million figure was chosen as the U.S. equivalent of the OECD's €750 million reference threshold set in 2015. It has not been indexed for inflation and remains unchanged for the 2026 cycle.
The Surrogate Parent Filing Pathway
Some U.S. groups file Form 8975 even though they are not the ultimate parent — typically because the ultimate parent is in a jurisdiction that does not require CbCR or does not have an exchange agreement with the United States. In those cases, the U.S. entity acts as a "surrogate parent entity" under Treas. Reg. §1.6038-4(j).
Surrogate parent filing is voluntary in form, but in practice it becomes mandatory because the alternative is local filing in every jurisdiction where the group has a presence. Most large groups would rather file one Form 8975 in the United States than file dozens of local CbCRs around the world.
Schedule A Walkthrough: What You Actually Report
Schedule A has three parts, and each must be completed for every jurisdiction with at least one resident constituent entity.
Part I: Tax Jurisdiction Information
Part I is an aggregate financial profile of the group's operations in the jurisdiction. The required line items are:
- Revenues from unrelated parties (line 1a) — third-party revenue earned by constituent entities in that jurisdiction.
- Revenues from related parties (line 1b) — intercompany revenue from other constituent entities, regardless of where those other entities reside.
- Total revenues (line 1c) — the sum.
- Profit (loss) before income tax — book income before tax for the jurisdiction, aggregated across all resident constituent entities.
- Income tax paid (on cash basis) — taxes actually paid during the reporting period, including withholding taxes paid by the constituent entities.
- Income tax accrued — current year — the current tax expense booked, excluding deferred taxes and provisions for uncertain tax positions.
- Stated capital and accumulated earnings as of year-end.
- Number of employees — full-time equivalent count.
- Tangible assets other than cash and cash equivalents — net book value, excluding intangibles, receivables, and cash.
Two consistent themes cause headaches. First, intercompany revenue is reported gross, not netted. Second, withholding taxes are included in cash taxes paid even when the legal taxpayer is somewhere else — the jurisdiction of source matters.
Part II: Constituent Entity Information
Part II is essentially a directory. For each constituent entity resident in the jurisdiction, you list the legal name, the jurisdiction of organization (if different from residence), the U.S. or foreign tax identification number, and a checkbox indicating the entity's main business activities from a fixed list (R&D, manufacturing, sales, holding, internal group financing, etc.).
The activity codes are heavily scrutinized by tax administrations. A holding company that also performs significant procurement should not be coded only as "holding"; an activity coding mismatch with the substance later asserted in a transfer pricing defense is one of the easier ways to lose an audit.
Part III: Additional Information
Part III is free-text. It is where you explain anything that would otherwise look anomalous: stub-period entities, restructurings, currency translation methodology, dividends excluded from revenue, and similar context. Skilled filers use Part III defensively — providing context here often heads off questions that would otherwise come back as information document requests.
Filing Mechanics and Deadlines
Form 8975 is attached to the U.S. ultimate parent entity's income tax return for the tax year in which the reporting period ends. That means the deadline is the income tax return deadline, including extensions — typically October 15 for calendar-year corporations on extension, March 15 for partnerships on extension.
Three practical points:
- Electronic filing is required for corporations filing Forms 1120, 1120-F, and 1120-S that are required to e-file their return. For groups with significant numbers of constituent entities, attempting to compile the Schedule A data manually is no longer realistic.
- The reporting period is the consolidated financial reporting period, even if the U.S. parent has a different tax year. A non-calendar consolidated reporting period requires filing with the return that covers it.
- A short-period reporting period is generally not annualized for threshold purposes, but groups facing this should consult the specific rules.
How the Data Travels: Competent Authority Exchange
Filing with the IRS is only the first step. Under the OECD's Multilateral Competent Authority Agreement on the Exchange of Country-by-Country Reports — and a network of U.S. bilateral Competent Authority Arrangements (CAAs) with about 50 partner jurisdictions — the IRS transmits each Schedule A to every partner jurisdiction where a constituent entity is resident.
This exchange has two practical consequences:
- Your CbCR is read by every tax administration you operate in, not just by the IRS. A statement made in Part III to soften a U.S.-facing concern may be read by a foreign auditor with very different assumptions.
- Jurisdictions without an exchange relationship may require local filing, which is where the surrogate parent pathway becomes useful. Groups should map their footprint against the IRS's CbC jurisdiction status table annually to catch newly added or suspended exchange relationships.
What Has Changed for the 2026 Cycle
Three developments are reshaping how CbCR data is used in 2026, even though the form itself has not been substantively redesigned.
Pillar Two Transitional Safe Harbor
The OECD's Pillar Two global minimum tax — a 15% effective tax rate floor for groups with €750 million or more in consolidated revenue — relies on CbCR data for its transitional safe harbor. For fiscal years beginning between January 1, 2024 and December 31, 2026, a jurisdiction can be deemed compliant with Pillar Two if it passes one of three CbCR-based tests:
- De minimis test — total revenues under €10 million and profit (loss) before tax under €1 million in the jurisdiction.
- Simplified ETR test — a simplified effective tax rate at or above 15% in 2024, 16% in 2025, and 17% in 2026.
- Routine profits test — profit before tax less than or equal to the substance-based income exclusion.
The simplified ETR is calculated using CbCR profit and CbCR income tax accrued, with adjustments. This means errors in your Form 8975 now have a direct dollar consequence: a flawed Schedule A can push a jurisdiction out of safe harbor status and into the full Pillar Two calculation, which is dramatically more complex and more expensive to administer.
Heightened Audit Use
Tax administrations have moved well past the "we'll look at this someday" phase. CbCR data is now an active input into risk-screening algorithms, including jurisdictional ETR anomaly detection, employee-to-profit ratio screening, and intangible profit concentration alerts. Several jurisdictions, including the UK and Australia, openly publish their CbCR risk-assessment frameworks.
Public CbCR in the EU and Australia
Although Form 8975 itself remains confidential between tax administrations, EU Directive 2021/2101 and recently enacted Australian rules require public disclosure of certain CbCR-like data for fiscal years starting in 2024 and 2025 respectively. U.S. groups with EU operations should expect their European subsidiaries to be filing publicly available reports that draw on the same underlying numbers. Inconsistencies between public reports and the confidential Form 8975 will be visible.
The Five Most Common Mistakes
Looking across IRS audit notices, OECD peer reviews, and Big Four CbCR remediation engagements, the same handful of errors keep appearing.
Misclassifying revenue type. Treating dividends from subsidiaries as ordinary revenue, or excluding extraordinary gains, is one of the most common errors. The instructions are specific: include all revenue captured in the consolidated financial statements other than dividends from constituent entities.
Inconsistent jurisdiction of tax residence. A constituent entity must be reported in exactly one jurisdiction in Part I (with limited exceptions for stateless entities and dual residents subject to a tiebreaker). Reporting the same entity in two Schedule A's, or omitting a permanent establishment, will be obvious to any auditor with access to the data.
Treating cash taxes and accrued taxes interchangeably. Cash taxes paid (line 5) and current year tax accrued (line 6) measure different things. Many groups load the same number into both columns, which produces an effective tax rate that does not match either book or cash reality and immediately flags the entity for review.
Using inconsistent data sources year over year. Some groups source Part I from statutory accounts in year one, then switch to management accounts in year two when an ERP changes. The instructions allow either approach, but switching mid-stream without documentation in Part III produces year-over-year movements that look like profit shifting even when nothing has changed.
Ignoring the Part III narrative. A blank Part III is a missed opportunity. Auditors notice anomalies in the data first and look for context second; if Part III provides that context, the inquiry often stops there.
How CbCR Connects to Day-to-Day Bookkeeping
CbCR feels like a corporate-tax-department problem, but the data inputs come from the general ledger. Three habits make the annual compilation dramatically easier:
- Tag every legal entity with its tax residence jurisdiction in the chart of accounts, and treat that tag as a controlled attribute that flows through consolidation.
- Track intercompany revenue separately from third-party revenue at the entity level, not just at the segment or BU level. CbCR requires the entity-level split.
- Reconcile cash taxes paid in the local ledger to the entity's tax return each quarter, so the year-end Schedule A number is auditable rather than reconstructed.
Groups whose underlying accounting is in opaque proprietary systems often discover that pulling the underlying data each year takes weeks. Groups with transparent, scriptable ledgers — where every transaction's legal entity and tax jurisdiction are queryable attributes — compile Form 8975 in days.
Keep Your Multinational Books CbCR-Ready From Day One
Whether you are crossing the $850 million threshold for the first time or refining a process you've run for five years, the underlying challenge is the same: getting clean, jurisdiction-tagged financial data out of your accounting system without a six-week reconciliation project. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — every transaction is queryable, every entity attribute travels with the journal, and there's no black box between your operations and your CbCR file. Get started for free and see why finance teams managing complex multi-entity structures are switching to plain-text accounting.