When Does Your Corporate Group Tip Into NGER Reporting? The Threshold Maths Most CFOs Get Wrong

The NGER thresholds look simple on paper. Add up the group's emissions, check the number, register or don't. The mistakes happen earlier than that, in the aggregation rules. Operational control, joint venture interests, what counts as a 'facility' under the Act. Get these wrong and you either over-report or miss the trigger year entirely.

Denis Patel June 13, 2026 11 min read
NGER ComplianceCorporate GroupOperational ControlReporting Thresholds
When Does Your Corporate Group Tip Into NGER Reporting? The Threshold Maths Most CFOs Get Wrong

A CFO at a mid-market property group called us last quarter with a deceptively simple question. They had eleven assets under management, three joint ventures, and one wholly-owned development arm. Were they over the NGER threshold or not?

The honest answer was: we didn't know yet, and neither did they. Not because the rules are hidden. They sit in plain view in the National Greenhouse and Energy Reporting Act 2007 and the NGER Regulations 2008. The problem is that the threshold maths sits on top of three other tests that most finance teams haven't worked through properly. Operational control. Facility boundaries. Joint venture treatment.

Get those wrong and the threshold calculation is wrong before you start.

The Two Threshold Levels (Still The Easy Part)

Section 13 of the NGER Act sets the trigger numbers. They haven't shifted in years.

A corporate group must register if, in a financial year, the group's total Scope 1 and Scope 2 emissions reach 50,000 tonnes CO2-e, or the group produces or consumes 200 TJ of energy. Either trigger pulls you in. It's an "or" test, not an "and".

A single facility within the group must be reported if it hits 25,000 tonnes CO2-e, or 100 TJ of energy produced, or 100 TJ of energy consumed. Again, any one of those.

The Safeguard Mechanism sits one tier above this, at the 100,000 tCO2-e facility threshold. If you're reading this article, you're probably not there yet. But it's worth knowing the staircase: 25 kt facility for NGER reporting, 50 kt group for registration, 100 kt facility for Safeguard Mechanism obligations.

So far, so straightforward. The maths breaks down at the question of whose emissions go into the bucket.

Operational Control Is The Default — And It's Not What You Think

The NGER Act uses operational control as the default boundary test. This sounds like it should align with how your finance team thinks about consolidation. It doesn't.

Under section 11 of the Act, your corporate group reports emissions from facilities where the group has operational control. The Clean Energy Regulator's operational control guidance defines this as the authority to introduce and implement operating policies, health and safety policies, and environmental policies. Note what's missing from that test: financial ownership.

A few consequences fall out of this that catch finance teams off guard.

You can have a 30% equity stake in a facility and still be the controlling corporation for NGER purposes if you supply the operations team and call the policy decisions. You can also own 70% of a facility and not be the controlling corporation, if your JV partner runs operations under a service agreement. The accounting consolidation lens doesn't help here. Two different tests, two different answers.

This is the cleanest divergence from the GHG Protocol approach most CFOs are familiar with. GHG Protocol gives you a choice between equity share, financial control, and operational control. NGER doesn't. Operational control is the default, and switching to financial control requires a formal application and Clean Energy Regulator approval under section 11AA. Almost nobody does this in practice. If your sustainability team or consultant is reporting on a financial control basis without that approval on file, that's a problem worth surfacing before the next reporting deadline.

The parallel here is worth flagging. AASB S2 climate disclosures follow the financial reporting boundary, which is typically a control basis aligned with AASB 10. So you can end up with two different consolidation perimeters for the same corporate group. NGER on operational control. AASB S2 on financial control. Different scopes. Different methodologies. The AR5 versus AR6 GWP gap compounds this. You will be reconciling the two for years.

What "Facility" Actually Means

The word "facility" does a lot of work in the NGER Act and most companies use it casually. The legal definition under section 9 is specific.

A facility is an activity, or series of activities, that involves the production of greenhouse gas emissions, the production of energy, or the consumption of energy. They must be attributable to a single industry sector. And they must form a single undertaking or enterprise.

What this means in practice:

Two adjacent buildings used for different industry activities are two facilities. A shopping centre and an office tower next door, even under the same ownership, can be separate facilities if they sit in different ANZSIC industry codes. Conversely, a series of related sites with the same industrial purpose, even spread across a state, can sometimes be one facility for NGER purposes. A network of grid substations operated by a single utility, for instance.

The "single undertaking" test trips people up. Mining companies sometimes treat each pit as a facility. Sometimes they treat the whole operation, including processing, as one. The Clean Energy Regulator's Facilities Under the NGER Scheme guideline document is the reference here, and it's worth reading rather than guessing.

For property managers and head contractors, the facility question matters because it changes which sites need to roll up under the 25 kt trigger. We've written previously about how head contractors on multi-site projects need to think about boundary aggregation before they can answer the threshold question.

Joint Ventures and the Equity Interest Problem

Joint ventures are where the threshold maths gets properly messy. The NGER Act handles JVs through the operational control test, but the policy intent is that emissions get reported once, by the controlling corporation, against the corporate group that controls operations.

So if your group has a 50/50 JV with another reporter, and your partner has operational control, the emissions sit in their books for NGER. Your group reports zero from that facility for Scope 1 and 2 NGER purposes. Even though you own half of it.

That sounds clean. The complication is that AASB S2, the ISSB-derived disclosure regime that mandatory climate reporting flows through, expects you to disclose emissions consistent with your financial reporting boundary. Which often means equity share or proportionate consolidation. So the same JV that produces zero NGER emissions for your group might produce a 50% equity share of those emissions in your AASB S2 disclosure.

We've spent a fair bit of product engineering time on this. The JV consolidation module in Carbonly supports operational, financial, and equity share methods running in parallel against the same underlying source data, with period locking so the boundary you used at the reporting date can't drift later. Most carbon accounting tools we've seen handle one of these methods and force you to pick. That doesn't work when your obligations span two regimes with different boundary rules.

The honest admission here: JV emissions allocation is the area where we still see the most data quality issues across our customer base. Not because the maths is hard. Because the operational control determination depends on contracts, side letters, and operating committee terms of reference that nobody documents in a way that a carbon accounting system can read. Someone, usually the company secretary, has to make the call and keep it under review.

When You Tip Over: The Registration Mechanic

Say you've done the maths properly. The group has tipped past the 50 kt CO2-e threshold or the 200 TJ energy threshold for the first time. What now?

Section 12 of the NGER Act requires you to apply for registration as a controlling corporation by 31 August of the year following the trigger year. Miss this and you've already breached. The application is made to the Clean Energy Regulator through the EERS portal.

Then the report itself. Under section 19, your annual NGER report is due by 31 October of the year following the reporting year. No extensions. The October deadline has been hardcoded into the Act for years and the Clean Energy Regulator does not move it for individual reporters.

For Group 1 reporters, AASB S2 disclosure ran first against FY2025. For Group 2, it runs against financial years starting from 1 July 2026, which catches most NGER reporters automatically. So the October NGER deadline now sits inside a wider climate reporting calendar that includes financial-year-aligned AASB S2 disclosure, often with limited assurance attached.

Five years of records have to be kept under section 22 of the Act. The accuracy expectation is on the directors. Section 75 carries strict liability provisions for false or misleading reports, with criminal penalties up to 2 years for dishonest conduct. The penalty unit value for civil contraventions sits at $330 from 7 November 2024, with the next indexation due 1 July 2026. A serious breach can reach into the hundreds of thousands of dollars.

Three Aggregation Mistakes We See Repeatedly

A few patterns turn up enough that they're worth flagging directly.

Mistake one: forgetting subsidiaries acquired late in the year. If you bought a business on 1 March and they had 8 months of emissions in your consolidated group financial year, those 8 months count toward your group threshold. The Clean Energy Regulator's view is that the group test runs against the full corporate group as it stood across the reporting period, with emissions attributable to the period of control.

Mistake two: treating Scope 2 electricity as smaller than it is. Some groups exclude tenant-paid electricity in leased premises on the basis that they don't pay the bill. Under operational control, if your group runs the facility, you report the Scope 2 emissions associated with that facility's electricity consumption. Who pays the bill is a separate question from who has operational control. This catches property managers in particular.

Mistake three: applying a national average grid factor. The state-based grid emission factors in the NGA Factors workbook differ substantially. Victoria runs at 0.78 kg CO2-e/kWh. Tasmania at 0.20. If your group operates 60% of its sites in Victoria and you use the national average of 0.62, you're under-counting by roughly 25% on your largest emissions tranche. That can be enough to drop you under the 50 kt threshold on paper when you're actually over it. The full state-by-state NGA factors need to apply at the site level.

How We Approach the Threshold Question

A few things we've built into Carbonly that bear on this specifically.

The emissions tracking sits on an NGER-native data model, with categories aligned to the NGER Determination 2008 energy and emissions categories from day one. Not a generic GHG Protocol model with NGER mapping bolted on later. That matters when you're trying to back-test whether the group has tipped over a threshold across a financial year.

Source tracking and a complete audit trail mean every emissions data point traces back to the source document, the calculation method, and the emission factor version used. When the Clean Energy Regulator queries a line in your report two years later, you can find it.

Period locking means once a reporting period closes, the boundary you applied at that point in time is preserved. JV reorganisations, operational control changes, even acquisitions don't retroactively rewrite history. That matters for both NGER and AASB S2 audit trails.

Seven-year retention is built in, exceeding the five-year NGER requirement under section 22 with a buffer for AASB S2 and Corporations Act expectations.

None of this replaces the legal interpretation work. Operational control determinations, facility boundary definitions, and JV reporting allocations are judgement calls that need to be made by people who understand your contracts. What the system does is hold those decisions in a structured form, so the threshold maths runs cleanly against them and you don't have to rebuild the analysis from spreadsheets every year.

What To Do This Quarter

If you're a finance lead at a growing group and you think you might be approaching the threshold, the practical sequence is:

Pull the last full financial year of emissions data at the site level. Apply state-based grid factors from the current NGA Factors workbook. Document operational control determinations for each facility, including JVs, in writing. Then run the corporate group total. If you're above 40 kt CO2-e or 160 TJ, you should be planning for registration in the next reporting cycle, not the one after.

The threshold maths is the last step. The aggregation rules are the first. Most groups that get this wrong got it wrong before they touched the calculator.


Related reading:

Take the Next Step

Ready to automate your carbon reporting? Carbonly.ai is working with a select group of Australian organisations.

Join the Waitlist