Filing Pillar Two in Australia
Australia is one of the more demanding jurisdictions to file Pillar Two in. Not because the computation is different – it follows the GloBE rules like everywhere else – but because the filing is split across four obligations, lodged through two different channels, behind an access layer that runs on the ATO’s timetable rather than yours.
We are now filing in Australia. This is what the process involves, in the order it has to be done.
First, the terminology, because it causes real errors
Australia does not use the terms QDMTT or ORN.
The domestic top-up tax is the DMT, reported in the Australian DMT Return. The notification confirming that the GloBE Information Return was lodged offshore is the foreign lodgment notification, and it lives inside Section 3 of a combined return. Groups that map a UK or EU compliance tracker onto Australia and search it for “QDMTT” or “ORN” find nothing, and conclude there is nothing to do.
Four obligations, three forms, two channels
Australia has four Pillar Two lodgment obligations. Since March 2026, three of them are combined into a single form – the Combined Global and Domestic Minimum Tax Return (CGDMTR). The GIR is not part of it and lodges separately.
Obligation | What it covers | Where it lodges | First-year deadline |
GloBE Information Return (GIR) | The group-level GloBE computation, in OECD XML | Separate lodgment: file transfer or API | 18 months after year end |
Foreign lodgment notification | Confirms where the GIR was lodged offshore | Section 3 of the CGDMTR | 18 months after year end |
AIUTR | Australian IIR / UTPR top-up tax | CGDMTR | 18 months, plus 30-day deferral for FY2024 |
DMTR | Australian domestic minimum tax | CGDMTR | 18 months, plus 30-day deferral for FY2024 |
Subsequent years run to 15 months after the end of the fiscal year. For calendar-year groups first in scope for FY2024, the first lodgments fell due on 30 June 2026.
Get the Four-Obligation Breakdown as a Reference Sheet
The table above, plus which channel each obligation actually lodges through, as a PDF you can check against before you’re mid-filing and guessing.
The access layer is where first-cycle groups lost time
Nothing can be lodged until the group has a Global and Domestic Minimum Tax (GDMT) account and role with the ATO. This is an administrative prerequisite with a queue attached, and it has no relationship to whether the numbers are ready.
- The client initiates the GDMT account and role request through Online services for business, or by phone.
- Where a tax agent will lodge, the client must complete that account and role creation first, then nominate the agent. The agent then has 28 days from nomination to add the client.
- Access to the CGDMTR runs through myID at standard or strong identity strength.
The ATO advised during the first cycle that account and role requests were being processed and that agents did not need to follow up. Read that as what it is: a queue with a lead time you do not control.
The practical consequence is simple. Start this the day Australia comes into scope, not when the computation is signed off. A group with a complete, validated GIR and no working credential cannot lodge.
The GIR is a structured transmission, not a form
The GIR XML file lodges through Online services for business or Online services for agents using file transfer, or through API-enabled software built to the ATO’s published specifications.
The requirements that catch teams out are in the identifiers:
- Message type – gir.0001.lodge.request
- MessageRefID – AU + reporting year + AU + sending entity IN + unique reference, e.g. AU2024AU123456789_1
- DocRefID – AU + reporting year + sending entity IN + unique reference, e.g. AU2024123456789_Summary1
Each part of the return needs its own DocRefID – FilingInfo, GeneralSection, Summary, JurisdictionSection and UTPRAttribution are separate. The file must also carry a Bulk Business Document Message wrapper, with an identifier (ABN, TFN or ARN), document type, document ID and name, and the software organisation, product and version.
Two rules matter more than the rest.
A MessageRefID can be used once only. Corrections and deletions require new identifiers – you cannot resubmit under the same reference.
And some fields cannot be corrected in place at all. Changes to certain elements require a deletion to be processed first, then a fresh lodgment. That is a very different remediation path from editing a form, and it needs to be understood before an error is discovered rather than after.
The CGDMTR: Section 3 is where the dependencies sit
Section 3 of the CGDMTR carries the foreign lodgment notification. It requires:
- The UPE’s name exactly as reported in the GIR, its jurisdiction, at least one identifier (TFN, ABN or TIN), and a postal address – where the UPE is not the lodging entity.
- Where the GIR has been or will be lodged: Australia, the UPE in a foreign jurisdiction, or a designated filing entity in a foreign jurisdiction.
- Designated filing entity details, where one applies.
- A three-letter currency code for the Australian top-up taxes, the exchange rate used to convert to AUD, and the conversion methodology.
Two practitioner notes on this section.
If the GIR lodgment date is not known, the ATO directs filers to the TIMESTAMP element in the message header of the GIR XML, which records when the file was prepared and sent. What goes in the field is the date of lodgment in the foreign jurisdiction – not the date exchange with the ATO is expected.
And if the UPE or designated filing entity lodges the GIR overseas after the Australian due date, Australian group entities are not treated as having lodged at the time of that foreign lodgment. The Australian obligation remains unsatisfied until the ATO receives the return on exchange, or it is lodged directly with the ATO. A late central filing becomes an Australian exposure, and the Australian entities carry it.
The designated local entity, and the 20-entity ceiling
A designated local entity (DLE) can lodge on behalf of the Australian entities in a group. The conditions are specific:
- It must be a group entity that is GloBE located in Australia.
- It must be nominated by every other group entity that is GloBE located in Australia.
- There is no nomination form to lodge. The DLE is identified in the relevant sections of the GIR and the CGDMTR.
Then there is the operational ceiling almost nobody scopes for. A DLE lodging for more than 20 group entities cannot use the online portal. It must use the API channel, which supports up to 300 entities.
For a group with 25 Australian entities, that is a software dependency discovered at the point of lodgment unless it was identified at the start of the project.
On payment: the DLE can pay for itself and for the entities it lodges for, but the correct payment reference number must be used for each entity. A PRN issues where an entity’s top-up tax liability is greater than zero.
The deferral covers less than it appears to
In-scope groups received an automatic 30-day lodgment deferral for the first FY2024 filings, with no application required.
It applies to the AIUTR and the DMTR only.
Neither the GIR nor the foreign lodgment notification can formally be deferred. An automatic 30-day suspension of lodgment enforcement applies to the foreign lodgment notification for fiscal years starting in 2024. For the GIR, the ATO may consider a suspension during the transition period, but it has to be requested separately.
A suspension of enforcement is forbearance, not a new due date. The obligation remains outstanding throughout, and none of it moves the payment date.
Exemptions do not travel across returns
Legislative Instrument LI 2025/28 relieves certain entities of the obligation to lodge a DMTR and/or an AIUTR – among them certain subsidiary members of tax consolidated or MEC groups, and entities not GloBE located in Australia. The AIUTR exemption requires both an IIR-related and a UTPR-related condition to be satisfied.
Exemption from one return is not exemption from all. The GIR and the foreign lodgment notification sit outside the instrument. An Australian group entity retains a GIR lodgment obligation even where the Australian top-up tax amount is nil.
Penalties, and what the transitional posture actually is
Failure to lodge attracts a base penalty of one penalty unit for every 28 days or part thereof that the document is overdue, to a maximum of five penalty units. For significant global entities, the base penalty amount is multiplied by 500 – a maximum of 2,500 penalty units per document.
False or misleading statement penalties run at 25%, 50% or 75% depending on behaviour, and for the minimum tax these can be doubled.
PCG 2025/4 sets out the ATO’s transitional approach to lodgment obligations, including remission where taxpayers can demonstrate they acted in good faith and took reasonable measures to understand and comply. The ATO has also indicated it expects the relevant entity or nominated DLE to make contact before the due date where a delay is expected.
That is an administrative posture, not a statutory concession, and it rewards groups that engage early over groups that explain late.
Ready reckoner
The sequence that worked in the first cycle, and the reason each step sits where it does.
When | Action | Why it bites |
As soon as Australia is in scope | Request the GDMT account and role. Nominate the tax agent after that request completes. | Queue with a lead time you do not control. The agent has 28 days to accept. |
Same time | Confirm the DLE and obtain nominations from every Australian group entity. | No form exists; the DLE is named in the GIR and CGDMTR, so it must be settled before either is built. |
Same time | Count the Australian entities the DLE will lodge for. | Above 20, the portal is unavailable and the API channel is mandatory. |
60 days out | Confirm where the GIR will be centrally lodged, and the entity that will lodge it. | Section 3 needs the UPE or DFE name exactly as reported in the GIR. |
60 days out | Test LI 2025/28 exemptions entity by entity. | Exemption from the DMTR or AIUTR does not touch the GIR or the notification. |
30 days out | Build and validate the GIR XML, including the BBDM wrapper and every DocRefID. | Identifiers are single-use. Some fields require deletion and relodgment, not correction. |
30 days out | Assemble Section 3 data, including currency code, exchange rate and conversion methodology. | Commonly missed because it is a tax data point held by treasury. |
At lodgment | Lodge the GIR, then the CGDMTR. Capture the receipt for each. | Amendments can only be made by the original lodging entity, and some CGDMTR data cannot be amended at all. |
After lodgment | Store evidence of acceptance against each entity, and diarise the next cycle at 15 months. | A filing that cannot be evidenced six months later cannot be defended. |
Get the Australia Pillar Two Ready Reckoner
The full first-cycle sequence above, as a PDF – every step, every deadline pressure point, and why each one bites where it does.
Where a filing partner earns its fee
The computation is usually the adviser’s work, and it should be. What sits after it is a different discipline, and the first cycle showed where the time actually goes.
- Schema construction and validation against the current specification, not the one published when the project started.
- Identifier governance – single-use references, per-part DocRefIDs, and a remediation path for fields that cannot be corrected in place.
- Channel selection, which is decided by entity count and is a software question, not a tax one.
- Credential and access management, which runs on the authority’s clock.
- Evidence of acceptance, captured per entity and stored where an auditor will find it.
None of that appears in a computation workbook. All of it determines whether the filing happens.
Cycle two is shorter – the first-year 18-month window drops to 15 months – and the transitional posture regulators showed this year will not repeat indefinitely. The groups that came through the first cycle cleanly were not the ones with the simplest numbers. They were the ones who treated lodgment as a systems problem and started it early.
Is Your Australian Entity Count Already a Software Problem?
If your DLE is lodging for more than 20 Australian entities, the portal is already off the table. Book a free 15-minute call to check your channel, credential, and identifier setup before it becomes a lodgment-day surprise.
Sources
- ATO – Lodging, paying and other obligations for Pillar Two
- ATO – GloBE Information Return (GIR) XML file requirements
- ATO – CGDMTR instructions, Section 3: Local and foreign lodgment notification
- ATO – Pillar Two account and role creation
- ATO – Pillar Two lodgments now available in Australia
- ATO – PCG 2025/4, Global and domestic minimum tax lodgment obligations: transitional approach
About the author
Saurabh Satija is Global Head of BEPS & Pillar Two and VP Sales, UK & Ireland at DataTracks, the HMRC-recognised regulatory reporting provider. He built DataTracks’ Pillar Two practice from zero and led its first live GloBE cycle: close to 500 filings, including more than 150 GIRs, for 160+ clients across 10+ jurisdictions. Based in London.
LinkedIn: linkedin.com/in/saurabhsatija
DataTracks is one of six HMRC-recognised Pillar Two software providers listed on GOV.UK, and filed across ten-plus jurisdictions in the first live GloBE cycle.