Briefing · 30 October 2026

A new schema, a later date. The OECD's GIR XML Schema 2.0.

On 20 October 2026 the OECD published version 2.0 of the GIR XML Schema. The headline is a new format. The detail that matters is the timing: the new content arrives before the new format, and corrections to old returns will travel in the new one.

Published 30 October 2026Data checked 30 Oct 20264 min read

01What the OECD published

The OECD released version 2.0 of the GIR XML Schema on 20 October 2026, with a revised User Guide. It carries the 2026 revisions to the GloBE Information Return made after the Side-by-Side Package.

Two dates govern the change. Version 1.0, released in January 2025, continues to apply to exchanges of GIR information until 15 June 2028. Version 2.0 applies to all exchanges from 25 June 2028. The OECD’s publication page names neither version for the days in between.

Note the word ‘exchanges’. The schema is built for tax administrations to send GIR data to each other. The OECD says it may also be used for domestic filing. Whether it is, and from when, is for each jurisdiction.

02The March 2027 filing is unaffected

For a calendar-year group in scope since 2024, the 2025 return is due on 31 March 2027. A group first in scope for 2025 files on 30 June 2027. Both dates sit well inside the version 1.0 period. Nothing in the OECD’s dates forces a rebuild for either filing.

The more useful point is the gap between content and format. The OECD’s updated GIR template applies to fiscal years beginning on or after 31 December 2025, as Germany’s BZSt reported in September. For a calendar-year group that is 2026. Under the 15-month rule, the 2026 return is due on 31 March 2028; France’s DGFiP prints that date on its own timeline. That is almost three months before version 2.0 takes over exchanges.

So the first returns built on the revised template fall due while version 1.0 still governs exchanges. The OECD’s publication page does not explain how that overlap will be handled. Expect each authority to answer it for its own filers.

03Corrections are the sleeper

From 25 June 2028, version 2.0 covers all exchanges, including amendments and corrections of GIR information exchanged earlier. A correction to a 2024 or 2025 return that is exchanged after that date travels in the new format, not the one the original was filed in.

The practical consequence is about records, not software. If the only copy of an early return is the XML file that was uploaded, a late correction may mean rebuilding it in a format that did not exist when it was filed. Keeping the underlying data, mapped by element, is cheaper than reconstructing it in 2028.

04Where domestic filing follows the OECD schema

Three jurisdictions in the tracker tie their domestic GIR upload to the OECD schema by name. When their authority moves to version 2.0, filers move with it.

  • United Kingdom. XML conforming to the OECD GIR XML Schema, through compatible software and the Secure Data Exchange Service.
  • New Zealand. XML meeting the OECD GIR XML Schema, through myIR.
  • Singapore. XML per the GIR XML Schema, through the myTax Portal.

Others publish their own specification, so the OECD date reaches filers only through the local one. Italy uses its own published tracciato and XSD. Canada takes the GIR by API only, in XML. Japan accepts the main report in XML or CSV. Germany’s BZSt said in September that the GIR XML schema is being revised.

Two questions are worth putting to your software provider now. Which schema version will it produce for the 31 March 2028 return in each country where you file? And can it produce a version 2.0 correction for a year it first filed in version 1.0?

05Where this comes from

The schema dates come from the OECD’s publication page for the October 2026 schema, read on 30 October 2026 and recorded in the change log. The template’s start date comes from the BZSt newsletter of 17 September 2026. Filing channels come from the tracker rows for each country, each read against the authority’s own page.

Not tax advice. Spotted an error? Tell me; corrections are logged on the method page.