DOCUMENTATION

Pillar 2 / GloBE

Global minimum tax and data readiness

Pillar Two is not only a tax calculation. It is a data architecture exercise that tests whether the group can reconcile financial reporting, covered taxes, deferred tax positions, elections, and entity classification consistently across jurisdictions.

Overview

The core question is whether the jurisdictional effective tax rate falls below the minimum standard after applying the GloBE mechanics. In practice, however, most implementation friction appears earlier: identifying the perimeter, cleaning entity mapping, understanding local tax attributes, and determining which adjustments materially change the ETR.

For advisory teams, the commercial challenge is translating a dense technical regime into an operating model. Groups need to know where the top-up tax could arise, whether a qualified domestic minimum top-up tax changes the outcome, when safe harbours are available, and which data fields must be owned by tax instead of left entirely to finance.

How Uncle Louis helps

Pillar Two work benefits from one place where entity lists, tax packs, memoranda, and follow-up actions can live together. That reduces the usual handoff friction between tax, finance, and local teams.

Useful outputs for platform users

A readiness memo showing scope, likely hot jurisdictions, and data gaps.
A jurisdictional issues list linking ETR drivers to source records and accounting owners.
A practical implementation roadmap for finance, tax, and local controllers.

When this topic matters

The group meets or is close to the EUR 750 million threshold and wants an early readiness assessment.
Entity data, local tax packs, and deferred tax tracking are spread across multiple finance systems.
Jurisdictions are implementing QDMTT rules and the group needs to understand where top-up tax will land.
Management wants to rely on transitional safe harbours but the underlying CbCR and tax data quality is uneven.

Common risk flags

The group focuses on the 15 percent headline threshold but not on adjustments that move the GloBE ETR materially.
Entity ownership and consolidation mapping are inconsistent between legal, accounting, and tax teams.
Safe harbour reliance is assumed without evidence that CbCR, deferred tax, and tax expense data are reliable enough.
Advisory teams discuss IIR and UTPR but do not map how QDMTT rules change cash tax and compliance sequencing.

How the analysis should be structured

Confirm scope and entity mapping

Validate the group perimeter, excluded entities, joint venture treatment, and jurisdictional grouping before modelling tax outcomes.

Build the jurisdictional ETR view

Reconcile financial accounts, covered taxes, and relevant adjustments at jurisdiction level rather than by entity alone.

Test safe harbours and domestic overlays

Assess transitional safe harbours, QDMTT interaction, and whether local implementation changes the filing or payment result.

Design controls and deliverables

Turn the model into repeatable close processes, governance, and documentation that finance and tax can both operate.

Questions users typically ask

Which jurisdictions are most likely to fall below the GloBE minimum and why?

Can we rely on transitional CbCR safe harbours, or is the data too weak?

How should we explain the interaction between QDMTT, IIR, and UTPR to management?