← Back to blog

GIR XML Schema v2.0: what changed from v1.0 and what your system needs before June 2028

The OECD published GIR XML Schema v2.0 in October 2026. It introduces six structural changes from v1.0, makes schema versioning mandatory, and sets a hard cutover date of 25 June 2028 for all GIR exchanges. Here is a field-by-field breakdown and a migration checklist for groups and their software providers.

Why the XML schema matters

The GloBE Information Return is not just a filing document. Under DAC9 in the EU, and equivalent automatic exchange frameworks in the UK, Australia, Japan and other adopting jurisdictions, the GIR is exchanged between competent authorities as a structured XML file. The schema governs what fields are present, what values are permitted, and how the file is validated before exchange. A GIR that does not conform to the schema accepted by the receiving jurisdiction will fail validation and not be treated as filed.

The original GIR XML schema (v1.0) was published alongside the first GIR template in June 2024. It was designed for the rules as they stood at that point, before the subsequent waves of OECD guidance added the Side-by-Side Safe Harbour, the explicitly conditional taxes framework, the QDMTT year-end safe harbour, and the September 2026 peer review framework. Version 2.0, published by the OECD in October 2026, catches up with all of those additions.

The hard cutover: 25 June 2028

Both v1.0 and v2.0 are valid during the coexistence period. Version 1.0 continues to be accepted for new exchanges of GIRs prepared under the original template, and for all periods reported before 25 June 2028. After that date, all new exchanges and all exchanges of previously-filed returns (including amendments and information-exchange responses) must use v2.0 format.

The June 2028 date was set to give groups, software providers, and national exchange systems approximately 18 months to migrate after v2.0 was published. Groups filing FY2025 returns in 2027 can file under v1.0 if they choose, but those same returns will need to be re-exchanged under v2.0 if any amendment or information request triggers an exchange after June 2028.

What changed: v1.0 to v2.0

The structural changes fall into six categories.

1. GIRSchemaVersion attribute is now mandatory

In v1.0, the GIRSchemaVersion attribute on the root element was optional. Many groups filed v1.0 returns without populating it. In v2.0, the attribute is mandatory and must be set to 2.0. Groups that filed earlier periods under v1.0 without this attribute must add it when amending or re-exchanging those returns. This is the smallest change mechanically but affects the largest number of previously-filed documents.

2. SideBySideDisclosure section

The Side-by-Side Safe Harbour, introduced in September 2026 Administrative Guidance, requires disclosure in the GIR for each constituent entity that applies it. Version 1.0 had no structured field for this. Groups reporting under v1.0 either added a free-text annex or omitted the disclosure entirely, relying on the transitional flexibility noted in the June 2026 guidance.

Version 2.0 introduces a mandatory SideBySideDisclosure block within the entity section. For each constituent entity using the safe harbour, the block records: the qualified blended CFC regime applied (currently GILTI or QUALIFIED_SUCCESSOR), the allocation approach, and confirmation that the adjusted effective rate test has been met. This makes the disclosure machine-readable for exchange purposes and consistent with what receiving jurisdictions will expect under their domestic Pillar Two rules.

3. ExplicitlyConditionalTax flag in CoveredTaxes

Following the September 2026 guidance on explicitly conditional taxes, v2.0 adds a boolean ExplicitlyConditionalTax flag to each tax entry in the CoveredTaxes block. Where a tax was treated as an explicitly conditional levy and included in covered taxes because the conditions were satisfied for the period, the flag is set to true. This sits alongside the existing tax type and amount fields. Under v1.0, groups either added a free-text note or left the distinction unmarked. The v2.0 flag standardises the treatment across all exchanges.

4. QDMTTYearEnd section

The QDMTT safe harbour for differing year-ends (where a jurisdiction's local accounting period differs from the MNE's reference fiscal year) has its own data requirements that v1.0 could not cleanly accommodate. Version 2.0 adds a QDMTTYearEnd section to the QDMTT block, capturing both the local-period and reference-year figures separately. The section is optional and applies only where a year-end mismatch exists and the safe harbour has been applied. See our separate article on the revised GIR template for 2025+ periods for the template-level treatment of this same requirement.

5. PeerReviewStatus enumeration per jurisdiction

The September 2026 peer review framework introduced a formal status classification for each jurisdiction's domestic Pillar Two law. Version 2.0 adds a PeerReviewStatus element to each jurisdiction section, populated from an enumeration: QUALIFIED, PROVISIONALLY_QUALIFIED, NOT_ASSESSED, or REVIEW_IN_PROGRESS. The status is recorded as of the filing date and is relevant for QDMTT and STTR entries, where the qualified status of the domestic law affects how the safe harbour is treated by other jurisdictions.

6. TemplateVersion element

The final addition is a required TemplateVersion element at the return level, with two permitted values: ORIGINAL (for GIRs prepared under the template published in 2024) and REVISED (for returns prepared under the revised template mandatory for periods from 31 December 2025). This distinguishes the two generations of GIR at the XML level, ensuring that exchange systems and receiving jurisdictions can apply the correct validation rules and interpret the data fields consistently. Without it, a receiving jurisdiction cannot tell whether a SideBySideDisclosure block is present because the group used the revised template, or because it was added as an extension to the original template.

What the June 2026 guidance workarounds required, and how v2.0 replaces them

The June 2026 Administrative Guidance was published before v2.0 existed. For the transition period, it permitted groups to handle Side-by-Side Safe Harbour disclosure and explicitly conditional tax classifications via free-text annexes or optional extensions to v1.0. Some groups applied these; others did not, in reliance on the fact that exchange frameworks were not yet requiring them.

Under v2.0, those workarounds are replaced by structured fields. Groups that filed under the free-text approach will need to migrate those disclosures into the SideBySideDisclosure block and ExplicitlyConditionalTax flag when they next amend or re-exchange those returns. This is not a retroactive obligation before June 2028, but it is work that should be scoped and planned now.

Migration checklist: what your system needs before June 2028

  1. Confirm your GIR software provider has a v2.0 roadmap with a published target date. The June 2028 cutover gives 18 months from the October 2026 publication. Providers that have not committed to a date should be pressed. Groups that build their own GIR XML generation need to scope the schema upgrade work now.
  2. Identify any v1.0 GIRs already filed that may need re-exchanging. An amended return filed after 25 June 2028 for any period must be in v2.0 format. If your FY2024 GIR is likely to be amended (for example, following a tax authority enquiry or a correction to safe harbour elections), budget for the v2.0 migration as part of that work.
  3. Map your v1.0 free-text annexes to the v2.0 structured fields. If you used the June 2026 workaround for Side-by-Side disclosures or explicitly conditional tax flags, document which entities and periods are affected. The migration to v2.0 fields requires the same underlying data; this is a structural change, not a new data-collection exercise.
  4. Test that GIRSchemaVersion is populated in your v2.0 output. The mandatory attribute is the most easily-missed change, because it was optional in v1.0. Many teams will have silently omitted it. Add it to your output template and your validation checklist.
  5. Check that TemplateVersion correctly reflects the GIR template used. For FY2024 returns prepared under the original template, the value is ORIGINAL. For FY2025 and later returns prepared under the revised template, it is REVISED. If your data model does not currently track which template version was used for each period, add that field before the first revised-template return is prepared.
  6. Wait for the v2.0 XML schema file before finalising your implementation. The OECD publishes the formal XSD alongside the narrative description. Build your mapping logic against the XSD, not against the narrative, as there may be minor differences between what the guidance describes and what the schema enforces.

Pillar2OS generates GIR XML natively, tracking schema version against each filed return and flagging any v1.0 returns that will require migration when the June 2028 cutover approaches. The SideBySideDisclosure, ExplicitlyConditionalTax and PeerReviewStatus fields are populated automatically from the computation and election layers. See the Compliance Centre.

Sources