If your U.S.-parented group crossed $850 million in consolidated revenue last year, the IRS already knows where every dollar of your profit lives — or it will, the moment you file Form 8975. The country-by-country report (CbCR) does not collect tax. It collects a map. And in 2026, that map is no longer just a transfer-pricing risk document buried in your tax return. It is the gateway to the OECD Pillar Two global minimum tax safe harbor that can save your tax department thousands of hours of GloBE calculations — or expose your low-tax jurisdictions to a 15% top-up tax if you fail the test.
The rules sound mechanical. The consequences are not. Here is what every U.S. multinational, tax director, and controller needs to know about Form 8975 in 2026, and why the report you used to treat as a compliance afterthought now sits at the center of your global tax strategy.
What Form 8975 Actually Is
Form 8975 is the U.S. country-by-country report. It is filed by the ultimate parent entity of a U.S. multinational enterprise (MNE) group as an attachment to the group's annual income tax return — Form 1120 for a C corporation, Form 1065 for a partnership, or the relevant return for the parent's tax classification.
The form itself is short. The substance is in Schedule A, which is filed once per tax jurisdiction in which the group operates. Each Schedule A reports aggregate financial and operational data for all constituent entities resident in that jurisdiction, plus a per-entity listing of those constituent entities and the activities they conduct.
Form 8975 was finalized in 2016 to align U.S. reporting with the OECD's Base Erosion and Profit Shifting (BEPS) Action 13 recommendations. The structure has not changed dramatically since, but the role it plays in cross-border tax enforcement has expanded enormously — and 2026 is the year that expansion becomes operationally critical.
Who Has to File: The $850 Million Threshold
A U.S. person must file Form 8975 if it is the ultimate parent entity of a U.S. MNE group with annual revenue of $850 million or more in the immediately preceding reporting period. The threshold is tested on consolidated group revenue, not standalone parent revenue, and includes all revenue items reported in the consolidated financial statements regardless of whether they appear above or below the line.
A few important nuances:
- The threshold is calibrated to the OECD's €750 million reference point as of January 1, 2015. The IRS chose a fixed dollar amount rather than a moving foreign-currency conversion, which means a euro-zone parent and a U.S. parent of identical economic size can have slightly different filing obligations.
- The MNE group concept is broader than U.S. tax consolidation. It includes any group that prepares consolidated financial statements under U.S. GAAP or IFRS and has at least one constituent entity resident in a tax jurisdiction other than the United States, or has a permanent establishment in another jurisdiction.
- Stateless entities count. Disregarded entities, certain partnerships, and entities with no jurisdiction of tax residence are reported under the country code "X5" on a separate Schedule A.
- Surrogate filing is available. If the ultimate parent sits in a non-U.S. jurisdiction that has not entered into a competent authority arrangement with another jurisdiction where a constituent entity resides, a U.S. constituent entity can be required to file as a surrogate parent to keep the local jurisdiction satisfied.
The threshold is tested annually on the prior period's revenue. Crossing the line for the first time triggers immediate filing for the current year. Dropping below does not automatically end your filing obligation — many groups continue voluntary filing to maintain audit-trail consistency.
What Goes on Schedule A
Each Schedule A captures aggregate financial data for one tax jurisdiction. The form is short but every line is loaded:
Line 1 — Revenues from unrelated parties. External revenues earned in or attributable to the jurisdiction.
Line 2 — Revenues from related parties. Inter-company revenues earned in or attributable to the jurisdiction. The split between Lines 1 and 2 is the single most-scrutinized data point in the entire form because it signals to tax authorities where transfer-pricing audit attention should land.
Line 3 — Total revenues. The sum of Lines 1 and 2.
Line 4 — Profit or loss before income tax. Aggregate pre-tax book income for the constituent entities in the jurisdiction, excluding extraordinary income and prior-period adjustments to the extent the group's financial statements present them separately.
Line 5 — Income tax paid (on a cash basis). Cash taxes paid during the reporting period to the listed jurisdiction and to any other jurisdiction on income earned in the listed jurisdiction (for example, foreign withholding taxes).
Line 6 — Income tax accrued — current year. The accrued current income tax expense recorded on taxable profits or losses, excluding deferred taxes and reserves for uncertain tax positions.
Line 7 — Stated capital plus accumulated earnings. Aggregate equity capital plus retained earnings of the constituent entities, measured at the end of the reporting period.
Line 8 — Number of employees. Full-time equivalent headcount of the jurisdiction's constituent entities. The group can elect to measure year-end headcount, average headcount, or any other reasonable basis — provided the method is applied consistently across all jurisdictions and from year to year.
Line 9 — Tangible assets other than cash and cash equivalents. Net book value at year-end of property, plant, and equipment located in the jurisdiction. Intangibles, financial assets, and cash are excluded by design — the OECD wants a measure of real economic substance, not balance-sheet items that can be moved with a wire transfer.
Part II — Constituent entity listing. For each entity resident in the jurisdiction, the group reports the legal name, tax identification number, jurisdiction of organization (if different from tax residence), and the main business activity by checking applicable boxes (R&D, holding intellectual property, purchasing/procurement, manufacturing/production, sales/marketing/distribution, administrative/management/support, internal group finance, regulated financial services, insurance, holding shares, dormant, or other).
The activity codes are where the tax-authority targeting algorithm starts. A holding company with intellectual property and no employees, sitting in a low-tax jurisdiction, lights up like a Christmas tree.
How the Data Gets Shared
The IRS does not sit on Form 8975 data. It automatically exchanges it with foreign tax authorities under bilateral competent authority arrangements (CAAs) negotiated under double tax treaties and tax information exchange agreements. The exchange is conducted using the OECD's standardized CbC XML schema and typically occurs within 15 months of the close of the reporting fiscal year (12 months for the first year of a new CAA).
By the time you file Form 8975 with your U.S. return, the German, French, Japanese, and Indian tax authorities are already in the queue to receive jurisdiction-specific extracts. They will run analytics. They will look for jurisdictions where you report large profits but few employees and few tangible assets. They will compare your CbC data with the transfer-pricing documentation you submit locally. Discrepancies generate audit notices.
This is why the form's "boring" data fields are not boring. Every line is a potential question.
Filing Mechanics and Deadlines
Form 8975 and Schedules A attach to the ultimate parent's federal income tax return and are due on the return's original or extended due date. For a calendar-year C corporation, that is April 15 with an automatic extension to October 15. For a calendar-year partnership filing 1065, the original deadline is March 15 with extension to September 15.
Practical points:
- File electronically. The IRS strongly encourages e-filing because the data has to be converted to the OECD CbC XML schema for automatic exchange. Paper filings slow the pipeline and increase the risk of data transcription errors that surface as audit questions in foreign jurisdictions.
- One Form 8975 per group per year. Even if the U.S. parent files multiple separate U.S. returns (rare but possible for certain partnerships), only one CbC report is filed per MNE group.
- Voluntary filing for surrogate compliance. If your group's ultimate parent is in a jurisdiction whose CbC rules took effect later than the IRS rules, the U.S. constituent entity can voluntarily file Form 8975 to satisfy foreign local filing requirements. Many groups did this for fiscal year 2016 and 2017 when other jurisdictions were still ramping up.
- Amended reports. If you discover material errors after filing, amend the entire Form 8975, not just the affected Schedule A. The OECD XML schema does not support partial amendments.
Penalties and Audit Exposure
The U.S. Treasury did not write penalty provisions specifically for Form 8975. Instead, general information-reporting penalties under Internal Revenue Code Sections 6038 and 6038A can apply because Form 8975 is treated as an information return. These can include:
- A base penalty for failure to file timely or filing materially incomplete information.
- Continuation penalties if the failure persists after IRS notice.
- Loss of foreign tax credits or deductions in extreme cases of willful non-compliance.
But the bigger exposure is rarely the U.S. penalty. It is the foreign audit risk that flows from the data the IRS shares automatically. A jurisdiction that receives your Schedule A and concludes that profits are being booked in a low-tax affiliate without corresponding employees, assets, or activities can open a transfer-pricing audit, propose adjustments, and pursue mutual agreement procedure cases that drag on for years.
Treat Form 8975 as audit-defense documentation, not a filing chore. Reconcile every Schedule A to your transfer-pricing master file, your local files, and your statutory financial statements before you submit.
The 2026 Pillar Two Connection: Why CbC Just Became Existential
Through 2025, CbC data was important. In 2026, it became foundational.
The OECD's Pillar Two global minimum tax — the GloBE rules that impose a 15% effective tax rate on large multinationals on a jurisdiction-by-jurisdiction basis — uses the CbC report as the input layer for its Transitional Country-by-Country Reporting Safe Harbor. A group that meets specified tests in a jurisdiction using its qualified CbC data can skip the full GloBE calculation for that jurisdiction and avoid the top-up tax for that fiscal year.
There are three alternative tests for the Transitional CbCR Safe Harbor:
- De Minimis Test. The jurisdiction has CbC revenue less than €10 million and CbC profit before tax less than €1 million.
- Simplified ETR Test. The jurisdiction's simplified effective tax rate — calculated as income tax expense divided by profit before income tax from the CbC report, with limited adjustments — equals or exceeds the transitional rate: 15% for fiscal years beginning in 2023–2024, 16% for 2025, and 17% for 2026.
- Routine Profits Test. The jurisdiction's profit before income tax is less than or equal to the substance-based income exclusion amount (a percentage of payroll and tangible assets).
The OECD originally scheduled the Transitional CbCR Safe Harbor to phase out after 2026. In January 2026, the OECD published its Side-by-Side Package, which extended the safe harbor by one year and retained the 17% rate for 2026 fiscal years. The extension gives U.S. MNEs additional runway to either switch to the Simplified ETR Safe Harbor or build the full GloBE calculation engine.
For tax directors, the takeaway is simple: if your CbC data is wrong, your Pillar Two safe harbor election can fail. A miscoded entity, a mis-jurisdiction-allocated revenue stream, or an inconsistent employee-count methodology can push a jurisdiction from "safe harbor — done" to "full GloBE calculation required" with a stroke. Many groups are running parallel CbC and Pillar Two preparation processes for 2026 fiscal years specifically to manage this risk.
Qualified Financial Statements: The Gating Concept
The safe harbor only works if your CbC report is built from qualified financial statements. The OECD defines qualified financial statements as:
- The accounts used to prepare the consolidated financial statements of the ultimate parent entity, or
- The separate financial statements of each constituent entity, provided they are prepared under an acceptable accounting standard (such as U.S. GAAP, IFRS, or another OECD-recognized standard) and the entity's data is reliable.
Critically, a CbC report built from management accounts or non-statutory ledgers is not qualified. If your group's CbC inputs come from a transfer-pricing data mart rather than from your statutory closing process, your Pillar Two safe harbor position can be challenged.
Many tax departments are restructuring their CbC data collection in 2026 specifically to source from audited or audit-ready statutory accounts at the entity level. The work is unglamorous — chart-of-account mapping, jurisdiction tagging, intercompany eliminations — but the payoff is a defensible Pillar Two position.
Common Filing Mistakes That Trigger Foreign Audits
After ten years of CbC reporting, certain patterns now reliably draw foreign tax-authority attention:
1. Stateless income. Large revenue or profit reported in the X5 (stateless) jurisdiction without supporting business rationale. Often this is a disregarded entity or hybrid that needs to be assigned to a real jurisdiction.
2. Employee-to-profit mismatch. Hundreds of millions of dollars of profit in a jurisdiction with five employees. Even if the structure is legal, the local revenue authority will open a substance audit.
3. Activity miscoding. Checking "sales/marketing/distribution" for an entity that is really booking IP licensing revenue. Foreign tax authorities run pattern matches and inconsistencies get flagged.
4. Tax-paid versus tax-accrued divergence. A jurisdiction with high accrued tax expense but consistently low cash tax paid often indicates uncertain positions, transfer-pricing reserves, or refund claims. Worth disclosing proactively in the transfer-pricing local file.
5. Year-over-year volatility in headcount or tangible assets without restructuring documentation. Particularly when paired with profit shifts. This is the single most common trigger for "request for information" letters in EU jurisdictions.
6. Inconsistent employee counting methodology. The OECD instructions require a consistent method across jurisdictions and across years. Switching from year-end headcount to average FTE midstream without disclosure invites questions.
Each of these errors is mechanical, not fraudulent. But the foreign audit cost — outside counsel, controversy reserves, mutual agreement procedure delays — can dwarf the time it would have taken to get the data right at filing.
Building a Defensible CbC Process for 2026
Tax departments that get CbC reporting right in 2026 generally do five things:
- Source from statutory accounts, not management reporting. This is a hard rule for Pillar Two safe harbor eligibility.
- Document the data-collection methodology. Write down how revenues are split between related and unrelated parties, how employees are counted, how the activity codes are applied, and how stateless income is identified.
- Reconcile to the consolidated financial statements. The sum of all Schedule A revenues plus eliminations should tie to the consolidated revenue figure. Discrepancies need explanations on file.
- Cross-check against the transfer-pricing master file and local files. A controlled transaction described one way in the local file and another way through the CbC activity codes is a guaranteed question.
- Stage a Pillar Two safe harbor test before filing. Run the three transitional CbCR safe harbor tests for every jurisdiction. If a jurisdiction fails the safe harbor, you have time to investigate whether the failure is real, a data error, or a structural issue that requires deeper Pillar Two analysis.
Accurate bookkeeping is the foundation here. The CbC report sits on top of your statutory ledgers; if those ledgers are unreliable or inconsistent across jurisdictions, no amount of post-close adjustment will produce a defensible report. Tax departments that fight this fire after the close pay for it twice — once in compliance hours and again in foreign audit exposure.
What's Coming After 2026
Three forces are reshaping CbC reporting beyond 2026:
- Public CbC reporting in Europe. EU Directive 2021/2101 requires public disclosure of certain CbC data for groups with EU activities, applicable for fiscal years starting on or after June 22, 2024. U.S. groups with EU operations are now publishing jurisdiction-level profit and tax data on their corporate websites or in annual reports. Whatever you put on Form 8975 will increasingly be readable by investors, journalists, and competitors.
- Pillar Two GIR filings. Beginning with fiscal years 2024 and 2025, MNE groups in scope of Pillar Two will file Global Information Returns (GIRs) in addition to CbC reports. The GIR is far more detailed and not eligible for the same automatic exchange protections. Tax controversy resources will increasingly focus on GIR data, with CbC serving as a corroborating layer.
- AI-driven audit selection. Tax authorities in the OECD, the EU, India, and the U.S. are deploying machine learning models trained on CbC data to predict transfer-pricing audit yield. Outlier detection — a Schedule A that looks anomalous against your peer group — increasingly drives audit selection decisions, not random sampling.
The era when CbC reporting was a compliance afterthought is over.
Keep Your Global Financial Records Audit-Ready
CbC reporting is only as defensible as the underlying ledgers it sits on. When statutory accounts are messy, intercompany flows are opaque, or audit trails go missing, even the best-staffed tax department cannot build a clean Form 8975. Beancount.io provides plain-text, version-controlled accounting that gives multinational tax and finance teams full transparency over their ledgers — no proprietary file formats, no vendor lock-in, and a complete audit trail of every entry. For groups managing global compliance obligations, that level of clarity is the difference between a defensible CbC filing and a year of audit defense. Get started for free and see why finance teams are switching to plain-text accounting.