Crossing the NGER Threshold Mid-Year: What Triggers,...

Most organisations do not walk into an NGER reporting year knowing they will report. They walk into it thinking they might, and somewhere between October and June a facility ticks over 25 ktCO2e or a corporate group ticks over 50 ktCO2e, and suddenly the question is not "should we monitor this" but "what do we owe the Clean Energy Regulator, and when."

We are three and a half months out from the first NGER FY26 submission (due 31 October 2026). If you have crossed a threshold this year, or are on track to, the sequence below is what actually happens next.

What the thresholds are, and where people get them wrong

There are four NGER thresholds, and each triggers a different obligation. They sit inside the National Greenhouse and Energy Reporting Act 2007 and its regulations.

Corporate group thresholds (Section 13 of the Act):

50 ktCO2e emissions (Scope 1 plus Scope 2), or
200 TJ energy produced, or
200 TJ energy consumed

Facility thresholds (Section 12):

25 ktCO2e emissions, or
100 TJ energy produced, or
100 TJ energy consumed

Cross any single one of the corporate thresholds and the controlling corporation must register and report. Cross any single one of the facility thresholds and that individual facility becomes a reportable facility inside the group's return, whether or not the group threshold is triggered.

The mistake we see most often is treating "50 ktCO2e" as a Scope 1 number. It is not. It is Scope 1 plus Scope 2 combined, at the corporate group level, using the operational control consolidation approach as the default. That single misreading is the difference between "we do not report" and "we should have registered last October."

The trigger event: what "crossing" actually means

You do not cross the threshold on the day you emit the 50,001st tonne. You cross it the moment the reasonable estimate for the current financial year (1 July to 30 June) exceeds the threshold. That is a forward-looking test, not a rear-view one.

In practice this means the trigger is a data event, not an emissions event. It happens when someone in the business runs the numbers (or a system runs them automatically) and concludes that the current-year estimate has crossed 50 kt at the group level, or 25 kt at a facility level.

From that moment, Section 13(1) of the Act starts running. You have until 31 August of the year immediately after the reporting year to apply for registration. That is the hard deadline. If you cross the threshold in October 2026, you must register by 31 August 2027. If you cross it in May 2027, same date.

The Clean Energy Regulator does not care whether you crossed by 1% or 50%. Once you have crossed, you are in.

What actually changes the day you register

Registration under Section 12 or Section 13 pulls three obligations forward, all with different clocks.

Reporting obligation. You must submit an NGER report for the full financial year in which you crossed the threshold. Not from the date you crossed. Not from the date you registered. The full year, from 1 July back-dated. This is the part that catches people. You cross the threshold in March 2027, and you owe the CER a full FY27 report (1 July 2026 to 30 June 2027) by 31 October 2027. Nine months of data you probably were not tracking to NGER standard.

Records obligation. Section 22 of the Act requires you to keep records that substantiate everything in the report for five years from the end of the reporting year. That obligation starts retroactively too. If your fuel dockets from August 2026 are sitting in someone's inbox or a shared drive with no version control, they need to be pulled into a records system that can survive an audit five years later.

ASRS Group 2 interaction. If you also cross into ASRS Group 2 (which most corporate groups triggering the 50 kt NGER threshold will), you now have an additional AASB S2 disclosure obligation for the same FY26 period. That disclosure lands with your statutory accounts, not with the CER, and it sits under a completely different assurance regime. Two reports, same underlying data, two different deadlines. See our note on operational, financial, and equity-share consolidation under AASB S2 for the boundary interaction.

What happens if you cross in October

October is the easiest month to cross in. You have most of the reporting year still in front of you.

The realistic action list:

Log the crossing event with a date, a triggering data source, and a signed calculation. This is the first entry in what becomes your NGER audit trail.
Notify the audit committee and finance leadership. NGER registration triggers a director-level accountability under Section 74 of the Act. This is not a sustainability-team decision.
Backfill July, August, September utility bills, fuel dockets, and refrigerant records. Assume you will need every invoice for every controlled facility.
Choose a measurement methodology for each emission source. NGER offers Method 1 (national default), Method 2 (facility-specific with sampling), Method 3 (Australian standard), and Method 4 (direct measurement). The methodology choice is per-source, per-year, and once you pick it you generally cannot switch mid-year without an approved variation.
Set up monthly close discipline for the remaining nine months. You are now on a period-close cadence whether you like it or not.

The October crossing is the one where you can still run the year properly. If you catch it here you can register in Q1 of the following calendar year, get the methodology decisions right, and have your first NGER submission look like a system output rather than a scramble.

What happens if you cross in March

March is where it gets uncomfortable. Nine months of data has already accumulated. Fuel cards have rolled over. Utility bills have been paid and archived. Refrigerant top-ups have happened without a leak log.

The March action list adds one thing the October list did not:

Retroactive data reconstruction. For the nine months of already-past data, you cannot go back and re-measure. You have to reconstruct from source documents. This is where the volume problem hits: a corporate group large enough to cross the 50 kt threshold typically generates thousands of utility bills, fuel dockets, and supplier invoices across all controlled facilities over nine months. The industry benchmark for the data-entry burden alone is around 10,000 fuel receipts per quarter for a mid-sized construction group, which is the scale of extraction Carbonly's AI Document Engine is architected to absorb.

The methodology decision also gets harder in March. Method 2 (facility-specific sampling) requires a sampling plan agreed with the CER before you start sampling. If you did not sample from July, you cannot back-date a Method 2 result for July. You are stuck with Method 1 defaults for the retroactive portion, which usually inflates the number.

If the estimate is close to the threshold, this inflation can push you well past it. The reasonable estimate model has a self-fulfilling quality: catch it early and you can measure accurately, catch it late and the defaults do the measuring for you.

What happens if you cross in May

May crossings are the worst. Two months left in the reporting year, ten months of retroactive reconstruction, and the CER's 31 August registration deadline sitting three months out.

At this point the honest position is: this year's report will lean heavily on Method 1 defaults, the audit trail will be assembled backwards from invoices, and the next year's plan needs to look completely different. You are not going to fix FY26 in May. You are protecting FY27.

Two things matter in a May crossing:

Register on time regardless. The 31 August registration deadline is not a soft deadline. Failure to register carries civil penalties under Section 31 of the Act, currently up to 2,000 penalty units per contravention for a body corporate (A$660,000 at the current A$330 penalty unit value, in force from 7 November 2024). The CER has used enforceable undertakings publicly, most recently in the Beach Energy matter, so treat the deadline as absolute.

Segregate the reconstruction work from FY27 measurement. Do not let the retroactive scramble contaminate the FY27 methodology decisions. FY27 needs a clean measurement plan starting 1 July, running in parallel with the FY26 reconstruction.

The JV and acquisition problem

The consolidation boundary question shows up hard in mid-year crossings. Two patterns cause most of the mid-year triggers we see modelled.

JV emissions flipping into scope. An unincorporated joint venture that was previously reported by the other party can flip into your scope if operational control changes. If you become the operator mid-year, every tonne from that JV site from the date of the operator change counts as yours. If your consolidation approach is operational control (the NGER default), the flip is immediate.

Acquisitions closing mid-year. An acquisition that closes in November brings a facility into the group. That facility's emissions from the date of acquisition through to 30 June count toward the group threshold. If the acquired entity was already an NGER reporter, you inherit their historical reporting; if it was not, you are inheriting a data reconstruction problem.

Both scenarios need to be modelled under all three consolidation methods (operational, financial, equity share) so the audit committee can see which method gives which threshold outcome, and document why the chosen method is the right one. We covered the mechanics of that in operational, financial, and equity share consolidation under AASB S2.

Interaction with AASB S2 Group 2

If your corporate group crossed the NGER threshold and is also large enough to trigger ASRS Group 2 (broadly, two of: over 500 employees, over A$500M revenue, over A$1B assets), your first NGER report and your first AASB S2 disclosure are being built off the same underlying activity data.

They are not the same report. Three practical differences:

Different Global Warming Potentials. NGER uses AR5 GWP values under the current regulations. AASB S2 requires AR6 for the disclosure. The methane and refrigerant lines will not match between the two documents unless you are running per-gas Scope 1 with both AR5 and AR6 available at render time. We wrote the mechanics up in AR5 to AR6 GWPs: calculation impact for NGER and AASB S2.

Different assurance regimes. NGER audits sit under Part 6 of the Act and are performed by CER-registered greenhouse and energy auditors. AASB S2 disclosures sit under ASSA 5010, performed by the statutory financial auditor. Two auditors, two evidence trails, one data set.

Different deadlines. NGER is due 31 October. AASB S2 lands with the statutory accounts, typically two to four months after year-end. The NGER report is the one that goes first, so it sets the numbers the AASB S2 disclosure will be judged against.

The practical implication is that the moment you cross the NGER threshold, you are also lighting up the AASB S2 clock. The 90-day lockdown we described for ASRS Group 2 reporters starts from the date you crossed, not from 1 July.

What to submit and how it lands with the CER

The NGER report itself is a structured XML submission to the CER's EERS portal (Emissions and Energy Reporting System). It contains:

Corporate group registration details and controlling corporation identifier
Reporting entity structure (each facility, its ANZSIC code, its operational control status)
For each facility, per-source emission and energy figures broken down by scope, gas, and fuel type
Methodology reference for each source
Uncertainty percentages where required

Every line in that XML needs to be traceable back to a source document. That is what a five-year records obligation actually looks like: fuel dockets, utility bills, refrigerant logs, JV cost allocations, all linkable back to the aggregated figure on the report. We covered the seven-year retention pattern that most systems now default to (two years longer than NGER's five, to align with AASB S2's expected retention window).

If your data is sitting in spreadsheets, the reconstruction from XML back to source document is where audits stall. If it is sitting in a system with typed audit events, source document links, and factor version pinning, the reconstruction is a click.

The three-and-a-half-month window

We are 15 July 2026. First NGER FY26 submission is due 31 October 2026. If you crossed the threshold in FY26 (any month from 1 July 2025 to 30 June 2026) and have not registered, you should have registered by 31 August 2026. That deadline is six weeks away.

The order of operations for the next 15 weeks:

Week 1 to 2. Confirm the crossing, document the trigger event, notify finance and audit committee.
Week 3 to 6. Register with the CER, elect measurement methodologies per source, complete the consolidation boundary decision under all three methods.
Week 7 to 12. Ingest and reconcile the full year of source documents. This is the volume-heavy phase.
Week 13 to 15. Build the report, run the assurance-ready checks (per-gas breakdown, factor version pin, materiality threshold review), submit the XML.

That timeline is tight but it is not impossible. What kills it is doing the ingestion and reconciliation manually. A mid-sized group crossing the threshold generates too many source documents to enter by hand in three months alongside a day job.

Where Carbonly fits

Carbonly monitors NGER thresholds continuously against the live emissions ledger, so the crossing event is a system notification, not an accountant's spreadsheet discovery in month nine. When a threshold is approached, the platform flags it against the current-year estimate. When it is crossed, the platform logs the trigger, timestamps it, and starts the audit trail.

The AI Document Engine handles the retroactive ingestion across eight file formats (PDF, CSV, Excel, Word, PowerPoint, RTF, images, scanned documents) with a five-tier material matching cascade so the fuel dockets, utility bills, and supplier invoices arrive extracted and mapped to the NGA 2025 factor library. JV consolidation runs under operational, financial, and equity share methods in parallel, so the boundary decision can be modelled before it is locked. Anomaly Detection flags refrigerant top-ups, methane spikes, and fuel outliers that would otherwise slip through a manual reconstruction. The NGER XML export lands the CER submission in the required format.

Bring one of your recent threshold calculations, or a facility-level activity data set you are worried about, to hello@carbonly.ai. We will show you what it looks like inside a system that treats the crossing event as the start of an audit trail rather than a spreadsheet emergency.

Crossing the NGER Threshold Mid-Year: What Triggers, What Changes