Source Systems for Pillar Two: Why Trial Balance Alone Is Not Enough

The trial balance is a useful starting point for Pillar Two, but it does not contain the full set of data, tax logic, adjustments, and jurisdictional reporting structure needed for GloBE-ready outputs.

A common starting point in Pillar Two implementation is the trial balance.

That is understandable.

The trial balance is structured, familiar, and already used as a base for financial reporting and tax processes. It often feels like the natural place to start when teams begin thinking about GloBE calculations.

In practice, however, it is not enough.

The trial balance provides a starting point, but it does not contain the full set of data required to support Pillar Two. More importantly, it does not explain how that data needs to be adjusted, reconciled, or governed across jurisdictions.

That is why relying on the trial balance alone tends to create false confidence early in the process. The real gaps only become visible later, when the organisation tries to move from a high-level model to a repeatable reporting process.

What the Trial Balance Actually Provides

The trial balance is a summary of financial accounts at a point in time.

It is useful because it provides:

• revenue and expense balances
• pre-tax accounting income
• certain tax-related balances at a high level
• a structured base for entity-level financial analysis

That makes it a useful anchor for initial scoping.

It can help answer early questions such as:

• what the basic income profile looks like
• where major balances sit
• how entity-level financial data is organised
• whether the chart of accounts structure is broadly usable

But that is only part of what Pillar Two requires.

Why the Trial Balance Falls Short

The problem is not that the trial balance is irrelevant.

The problem is that Pillar Two sits above and beyond it.

It lacks the granularity Pillar Two often needs

The trial balance works at account level.

Pillar Two often requires more detailed breakdowns, including:

• separation of income or expense categories that receive different treatment under GloBE
• identification of specific adjustment categories
• more precise visibility over tax-related balances
• supporting detail that sits behind account totals

In many cases, the required distinction is not visible from the account balance alone.

A single line in the trial balance may contain items that need to be treated differently for Pillar Two purposes. Once that happens, the trial balance stops being a complete input and becomes only a starting point.

It does not contain the full tax layer

This is one of the biggest misunderstandings in early implementation.

Pillar Two does not work off current tax expense alone. It requires a broader and more refined tax view, including:

• adjusted current tax
• deferred tax components
• remeasurements or movements that need separate treatment
• other tax adjustments needed to arrive at covered taxes

Much of this does not sit cleanly in the trial balance.

In practice, the trial balance usually shows the accounting outcome of tax entries, but not the full logic needed to determine covered taxes under Pillar Two. That logic often sits in tax provisioning systems, tax reporting schedules, or separate supporting workpapers.

It has no visibility over the adjustment layer

This is where many projects run into trouble.

The trial balance reflects accounting outputs before Pillar Two-specific adjustments are applied. It does not show:

• how accounting income is adjusted to GloBE income
• how covered taxes are modified
• where judgement-based treatment is applied
• how manual overlays are introduced
• whether the same methodology is being applied across jurisdictions

Those steps are essential.

And because they usually sit outside the trial balance, a process built too heavily around TB extraction will eventually need a second layer of logic built on top of it.

That second layer is often where complexity really begins.

It is not naturally aligned to jurisdictional reporting

Trial balances are usually maintained at legal entity level.

Pillar Two operates primarily at jurisdiction level.

That sounds like a simple aggregation problem, but it often is not.

In practice, moving from entity-level trial balance data to jurisdiction-level GloBE outputs may require:

• aggregation across multiple entities
• alignment across different local account structures
• reconciliation between local books and group reporting
• consistent treatment of entities within the same jurisdiction
• treatment of items that do not align neatly between legal entity and reporting views

The trial balance does not solve that automatically.

It gives you raw entity-level balances. It does not give you a finished jurisdictional reporting model.

Why Pillar Two Needs a Multi-Source Data Model

The deeper issue is that Pillar Two does not sit in one reporting layer.

It cuts across several.

A workable Pillar Two process usually depends on information drawn from:

• financial accounting records
• consolidation systems
• tax provision or tax reporting processes
• local statutory reporting
• manual adjustment and support files

Each of these serves a different purpose.

The trial balance helps with book-level financial data. The consolidation system helps with group reporting logic and eliminations. Tax systems help with current and deferred tax analysis. Local statutory accounts may explain local accounting treatments or reporting differences. Manual workpapers often hold the adjustment logic that has not yet been embedded in a system.

That is why a single-source mindset creates problems.

Pillar Two is not just a data extraction exercise. It is a data construction exercise across multiple reporting layers.

What Additional Sources Are Usually Required

Consolidation systems

These are often needed to support:

• group-level financial alignment
• eliminations and consolidation adjustments
• the starting point for jurisdictional aggregation
• consistency with consolidated reporting

They are especially important where local trial balances alone do not reflect the reporting view used by the group.

Tax reporting or provisioning systems

These are critical for:

• current and deferred tax analysis
• tax provision detail
• supporting schedules behind tax balances
• identifying tax adjustments that do not appear clearly in the trial balance

Without this layer, covered tax analysis is usually incomplete.

Local statutory accounts and local reporting files

These are often needed where:

• local accounting treatment differs from group treatment
• statutory disclosures provide supporting detail not visible elsewhere
• jurisdiction-specific positions need to be understood more clearly
• the group needs to reconcile differences between local and consolidated views

This is especially relevant in multinational groups with uneven local system maturity.

Manual workpapers and support files

In many organisations, important parts of the Pillar Two logic still sit outside formal systems.

That may include:

• local calculation files
• adjustment schedules
• deferred tax support
• mapping files
• review and reconciliation workpapers

These are often unavoidable, especially in early-stage implementation.

But they also create risk:

• inconsistent local practice
• weak traceability
• dependency on individual knowledge
• limited scalability

What This Means for Data Readiness

Understanding source systems is not only about identifying where data exists.

It is about understanding how the reporting model is actually built.

The key questions are:

• which system is the source of record for each major input
• which sources provide supporting detail only
• where transformations occur
• where data is aggregated
• where manual intervention is required
• where reconciliations are needed
• whether the result can be repeated under reporting timelines

Without this, it is not possible to design a reliable Pillar Two data model.

A group may believe it has the necessary data because the trial balance exists. In practice, the real question is whether the group can connect that trial balance to the other layers required to produce GloBE-ready outputs under control.

Implications for Implementation

The limitations of the trial balance affect how Pillar Two projects should be structured.

Data mapping becomes multi-source

The mapping exercise is not simply:

trial balance account to calculation line

It usually becomes:

trial balance plus tax data plus consolidation logic plus local support plus manual adjustments to GloBE input

That is a very different exercise.

Reconciliation becomes a core activity

Once multiple sources are involved, reconciliation becomes central.

Groups need to understand and explain differences between:

• book and tax data
• local and group reporting
• system outputs and manual adjustments
• entity-level and jurisdiction-level views

This is not side work. It is part of the core implementation effort.

Control requirements increase quickly

The moment the process depends on several systems and manual files, control design becomes much more important.

Groups need enough structure to ensure:

• consistent treatment across jurisdictions
• traceability of adjustments
• repeatability across periods
• auditability of outputs

That is why a Pillar Two reporting model built on multiple data layers needs stronger governance than a simple extraction model.

Link to the Next Layer

Once the source system landscape is understood, the next challenge becomes clearer.

Even with the right data sources, the process still depends on how accounting data is transformed into GloBE-ready inputs.

That is where the adjustment layer becomes critical.

The next question is no longer only: which systems hold the data?

It becomes: what needs to happen to the data before it can be used?

That is where manual adjustments, local workarounds, and control design start to matter most.

Conclusion

The trial balance is a useful starting point for Pillar Two.

But it is only that: a starting point.

It does not contain the full set of tax information, it does not explain the adjustment layer, and it does not by itself produce a jurisdictional reporting model. Pillar Two depends on a broader multi-source structure that brings together financial data, tax logic, consolidation views, local reporting detail, and controlled adjustments.

For multinational groups, the implication is practical: Pillar Two data readiness cannot be built on trial balance extraction alone. It requires a multi-source approach with clear mapping, reconciliation, and control across the reporting chain.