EY's 2026-27 Worldwide Corporate Tax Guide Covers 150 Jurisdictions. Your Provision Model Covers Fewer Than 20. That Gap Is a Liability.

EY's 2026-27 Worldwide Corporate Tax Guide covers 150 jurisdictions. Your provision model covers fewer than 20 of them. Here's how to close the gap before year-end.

Editorial source review — November 1, 2026. This machine-generated article has been reviewed, but is not certified accurate. Source-backed corrections are incorporated where established. Other legal, survey and product claims may remain unverified; check applicable primary authorities before relying on a deadline or tax position.

Findings in the original version: EY's guide landing page supports coverage of approximately 150 jurisdictions and its stated information cutoff. It is a secondary guide and cannot establish subsequent enactments.

EY published its Worldwide Corporate Tax Guide 2026-27 on October 19. It covers corporate income tax systems in approximately 150 jurisdictions, with data current as of July 1, 2026. Every EY office in 150 countries contributed to it. The result is the most comprehensive annual snapshot of global corporate tax in existence.

I want to make one observation about what that guide represents and what it doesn't. It is a static document. It captures the world as of July 1, 2026. In the 115 days between July 1 and today, at least eight jurisdictions have announced or enacted CIT rate changes, France's Finance Committee has moved Pillar Two threshold amendments through its first legislative stage, and Malaysia's 2027 budget has proposed a rate cut for SMEs. The EY guide does not know about any of that. Your provision model needs to.

150 Jurisdictions Is Not a Research Project — It's Your Risk Register

When a corporate tax director reads EY's Worldwide Corporate Tax Guide, they are not reading it as a survey of interesting jurisdictions around the world. They are reading it as a risk register. Every jurisdiction in that guide is one where:

The practical problem is this: most F500 provision models actively track 15-to-30 jurisdictions. The other 120-plus are either not material or not mapped. "Not material" is a judgment call that gets revisited every time a new entity is formed or a new acquisition closes. "Not mapped" is a liability that compounds every time a jurisdiction in that category enacts a Pillar Two rule, a digital services tax, or an exceptional corporate surtax your provision team doesn't know to watch.

I have seen this failure mode repeatedly. A company acquires a business in a jurisdiction the tax team treats as de minimis — say, under $5 million in revenue. That entity has a deferred tax liability that nobody models in the provision because the entity is below the materiality threshold for individual disclosure. Then the jurisdiction enacts a rate change from 22% to 28%. The remeasurement hits the provision in Q4. The CFO asks why it wasn't flagged. The answer is: we weren't tracking that jurisdiction. That answer is not acceptable in 2026.

The Rate Volatility Trap

The EY guide captures rates as of July 1, 2026, with specific country exceptions where later data was available. That is exactly the right disclosure for a document published in October. But it understates the operational challenge facing provision teams today.

Rate volatility has accelerated since 2022. The reasons are well understood: Pillar Two created a global 15% minimum effective rate floor, which prompted jurisdictions that had been below the floor to raise statutory rates — and jurisdictions that had been above the floor to examine whether their rate premium was competitively sustainable. The result is a rolling cycle of rate adjustments that has not stabilized.

In Q3 2026 alone, the following jurisdictions enacted or proposed CIT changes with provision implications:

None of these developments are in the EY guide's July 1 data. All of them are provision events for companies with entities in those jurisdictions. Your provision model needs to catch them before year-end close, not after.

The Pillar Two Coverage Gap Is a Year-End Problem Right Now

The most operationally significant content in the EY guide — for tax directors managing the next six weeks — is the Pillar Two implementation status by jurisdiction. As of July 1, 2026, more than 50 jurisdictions had enacted IIR, UTPR, or QDMTT legislation implementing the global minimum tax. The number is higher today.

The Pillar Two coverage gap in most provision models has three dimensions:

Entity scope. Does your GloBE computation include all in-scope entities? The 750 million euro consolidated revenue threshold is a group test, but the top-up tax is calculated entity by entity in each low-tax jurisdiction. Companies that assumed their Pillar Two exposure was concentrated in 3-4 jurisdictions are discovering that the "tail" of small entities in 15-20 other jurisdictions creates material top-up tax after the Substance-Based Income Exclusion (SBIE) is applied correctly.

Enacted rate accuracy. The Pillar Two qualified domestic minimum top-up tax (QDMTT) rate varies by jurisdiction. Some jurisdictions have set the QDMTT rate at exactly 15%. Others have set it at their domestic statutory rate adjusted for qualifying income adjustments. If your provision model is loading a 15% rate uniformly across all QDMTT jurisdictions, you are almost certainly wrong in jurisdictions where the effective QDMTT computation diverges from the standard model.

GIR deadline tracking. The GloBE Information Return filing deadline for most jurisdictions is 18 months after fiscal year end — June 30, 2027 for a December 31, 2026 year. Some jurisdictions have moved to 12 months. If your tax compliance calendar has not been updated to reflect each jurisdiction's enacted GIR deadline, you have a compliance risk that is not a provision issue but is a tax director issue.

What a Live Jurisdiction-Level Tax Data Layer Looks Like

A static guide, even EY's excellent one, solves a research problem. It does not solve a provision management problem. The provision management problem requires a live, maintained, machine-readable jurisdiction-level tax data layer — one that your provision calculation engine can query in real time.

Here is what that layer contains:

Clarity Tax maintains 1.25 million semantic tax definitions in our knowledge graph, including jurisdiction-level rates, Pillar Two enactment status, and remeasurement triggers for every jurisdiction where our clients operate. When France's Finance Committee moved the Pillar Two threshold amendment this week, DisclosureIQ flagged it for every client with French entities before the news cycle had finished processing it.

That is the operational posture the EY Worldwide Corporate Tax Guide describes but cannot itself provide. The guide is where you go to understand a jurisdiction. DisclosureIQ is where the jurisdiction comes to you.

What to Do Monday Morning

1. Pull EY's guide and run it against your entity roster. For every jurisdiction in your legal entity structure, verify that you have a current enacted rate loaded in your provision model — not the rate from last year's provision, not a proposed rate, the enacted rate with its effective date. This exercise will surface 5-10 stale rates in most F500 provision models. 2. Map your Pillar Two in-scope entities to enacted QDMTT jurisdictions. For each jurisdiction where you have an in-scope entity and a QDMTT has been enacted, confirm you are running a QDMTT computation — not just a top-up tax overlay at the IIR level. The tax you pay to the local treasury is the QDMTT rate, not the GloBE model rate. 3. Flag France for immediate monitoring. The 2027 Finance Bill's exceptional surtax and Pillar Two threshold changes are still moving through the National Assembly. Enactment triggers an ASC 740 deferred tax remeasurement in the quarter of enactment. If you have French entities with material deferred tax balances, model the remeasurement impact now so you are not doing it under year-end pressure. 4. Update your GIR compliance calendar for FY2026. The GloBE Information Return for fiscal year 2026 is due June 30, 2027 in most jurisdictions — but not all. Check each jurisdiction's enacted GIR deadline, not the OECD default. Some are 12 months, some have deferred to 2028 for early-stage implementations. 5. Identify the jurisdictions in your structure that are not in your current provision model. For each one, assess whether it meets the threshold for inclusion in the provision under ASC 740 or IAS 12. If it does, build the data feed now — not in February during year-end crunch. Every jurisdiction you add to a manual process in February adds risk to an already compressed close cycle.

DisclosureIQ tracks enacted rates, Pillar Two status, and remeasurement triggers across 150-plus jurisdictions in real time — so your provision model reflects the world as it is, not as it was on July 1.

See the Platform →

Sources