For calendar-year MNE groups, 30 June 2026 was the headline date — 18 months after the first GloBE fiscal year end of 31 December 2024. It didn't hold for everyone. On 8 July 2026, filing windows for GIR submissions were extended to 1 September 2026 in response to problems that had been building for months. That extended deadline has now passed, which makes this a good moment to look honestly at what the first cycle actually involved.
What went wrong
Two issues dominated, and neither was really about the tax computation itself:
- Portal availability. A meaningful number of jurisdictions had not finished building the systems needed to receive GIR submissions by the time groups were ready to file. A group could have a complete, correct return and still have nowhere compliant to send it.
- Exchange mechanism gaps. Where a group intended to rely on the central filing exception — filing once, in the UPE's jurisdiction, for the whole group — the Multilateral Competent Authority Agreement (MCAA) network needed to actually route that information onward wasn't uniformly in place.
Both problems sit squarely with tax administrations, not filers — but the exposure, in the form of potential late-filing penalties, sat with groups.
What OECD's May 2026 guidance actually did
On 18 May 2026 the OECD stepped in with guidance intended to defuse exactly this. The key points:
- Participating jurisdictions agreed to publish, by 31 May 2026, a list of countries whose portals were confirmed operational — giving filers a concrete answer to "can I actually submit here yet?"
- Countries committed to using their own domestic legal mechanisms to waive penalties or suspend filing deadlines for groups caught out by portal delays.
- Relief was tied to groups that had properly used the MCAA central filing exception — this was not a blanket amnesty, it protected filers who had done the right thing procedurally and were blocked by infrastructure, not filers who simply hadn't prepared.
The practical effect was the two-month extension to 1 September 2026 that many groups ultimately relied on. But "relief available" and "relief automatically applied" were not the same thing in every jurisdiction — some tax authorities required an active request or a specific procedural step to access the waiver, rather than applying it by default.
The technical complexity nobody budgets for
Even where portals worked, the first cycle exposed how much validation burden sits inside the GIR XML schema itself. Namespace declarations, cross-reference integrity between Parts A through E, and jurisdiction-specific extensions to the base OECD schema all produced rejected submissions that had nothing to do with the underlying GloBE numbers being wrong. Groups that treated XML generation as a final export step — rather than something to validate continuously through the computation — lost the most time in the final weeks.
What to fix before the next cycle
| Problem this cycle | Fix for next cycle |
|---|---|
| Found out late that a jurisdiction's portal wasn't ready | Check jurisdiction readiness at the start of the filing window, not the week before the deadline |
| XML rejected on schema validation, discovered near deadline | Validate against the OECD schema continuously as the computation is built, not as a one-off export step |
| Assumed central filing exception meant no local obligations | Confirm each jurisdiction's own notification and QDMTT self-assessment deadlines separately — these are not covered by GIR central filing |
| Penalty relief assumed automatic | Check whether your filing jurisdiction requires an active request to apply portal-delay relief |
What's coming next
The OECD has signalled further work to streamline reporting obligations by the middle of the year, and the EU's DAC9 exchange framework brings its own automatic-exchange deadline of 31 December 2026 for information already filed centrally. Neither of those removes the underlying lesson from this cycle: the GloBE computation is usually the easy part. The filing infrastructure around it — schema validation, jurisdiction readiness, and exchange mechanics — is where most of the last-minute risk actually lives.
Pillar2OS validates your GIR XML against the current OECD schema continuously as your computation runs, not as a final export step, so schema errors surface weeks before a deadline instead of days before one. Try it free.