NGER October 2026 Deadline: A Month-by-Month...

You have six months. On 31 October 2026, your NGER report for the 2025-26 financial year is due in the Clean Energy Regulator's Emissions and Energy Reporting System. No extensions. No grace period. The CER publishes the names of late reporters on its website, and repeated failures trigger infringement notices carrying penalties of $222 per penalty unit.

Most companies don't start thinking about this until August. Some wait until September. That's how you end up with a sustainability analyst working weekends in October, chasing missing electricity bills from a utility retailer who takes three weeks to respond.

We've seen this cycle repeat for years. Before building Carbonly, our team spent nearly two decades working inside enterprise data systems at mining and energy companies. Every October was the same panic. The companies that submitted clean, accurate NGER reports weren't smarter. They just started earlier.

Here's a month-by-month timeline from April through October that keeps you ahead of the deadline. For each month, we've mapped what typically goes wrong, because knowing the failure modes is half the battle.

But this year there's an added dimension. If you're an NGER reporter, you're automatically an ASRS Group 2 entity from 1 July 2026. That means this financial year is also your first AASB S2 data collection year. The NGER preparation you do now feeds directly into your mandatory climate-related financial disclosures. Two frameworks. One data collection effort. Get it right once.

April and May: Data audit and gap identification

This is where you find out what you actually have and what's missing. Don't skip it.

Pull together a complete inventory of every emissions data source across your NGER-registered facilities. Electricity bills. Gas invoices. Fuel card statements. Diesel delivery dockets. Fleet fuel records. Refrigerant top-up logs. Waste transfer receipts. Water bills if you have wastewater treatment obligations.

For each source, answer three questions. Do we have continuous coverage for July 2025 through to the current month? Is the data in a format we can actually process (not buried in someone's inbox)? And does the source document contain what we need for NGER calculations, specifically consumption quantities, billing periods, and meter or account identifiers?

What goes wrong in April-May:

The biggest problem is subcontractor data that never arrives. If you have subcontractors operating equipment on your sites, their fuel consumption is likely within your operational control boundary under sections 11 to 11B of the NGER Act. But getting that data requires contractual leverage you should have established at project award, not six months before the reporting deadline. Start chasing it now. Send formal data requests with specific format requirements. If a subcontractor ran 15 excavators on your site for nine months and can't tell you how much diesel they burned, that's a gap you need months to close.

The other common failure is discovering that your facility register doesn't match reality. Companies acquire sites, divest others, change operational arrangements with JV partners. If you've had any corporate changes since your last NGER report, check whether your facility registrations with the CER are still accurate. Facility registration errors don't just affect this year's report. They compound across reporting periods and are exactly the kind of problem that triggers an enforceable undertaking, as happened to more than one NGER reporter in 2025.

This is also the month to confirm which version of the NGA Factors workbook applies to your 2025-26 report. DCCEEW published the 2025 edition with material changes: updated state-based electricity grid emission factors, new market-based methods for biomethane and hydrogen consumption, revised flared gas emission factors for oil and gas operations, and updated N2O factors for wastewater. If your spreadsheet or software is still using 2024 factors, every calculation downstream will be wrong.

June: Close the financial year data

The 2025-26 financial year ends on 30 June. Your goal for June is simple: make sure every utility bill, fuel card statement, and supplier invoice for the full twelve months is collected before you move to calculations.

This sounds obvious. It isn't. Electricity retailers typically issue bills on cycles that don't align with the financial year. A quarterly bill issued in early July might cover consumption from mid-April to mid-June. A bill issued in late July covers May to July, crossing the financial year boundary. You need to know your billing cycles for every meter at every facility so you can identify which bills will arrive after 30 June but contain FY2025-26 consumption data.

What goes wrong in June:

Missing utility bills. This is the single most common data gap we hear about from NGER reporters. A bill from one electricity retailer for one facility in one quarter goes missing. Maybe the bill went to an old email address. Maybe the account was transferred during a property management change. Maybe it simply wasn't forwarded. You don't notice it's missing until you're reconciling in August, and then the retailer takes three weeks to reissue it.

The fix is a reconciliation check in June. For every meter or account number in your facility register, confirm you have bills covering July 2025 through the latest available period. Flag anything missing now. Three weeks of retailer turnaround time in June is inconvenient. Three weeks in October is fatal.

For AASB S2, June is also when you should be documenting your measurement approach. AASB S2 paragraph 29(a) requires you to disclose absolute gross Scope 1 and Scope 2 greenhouse gas emissions. NGER reporters get some relief here: you can use the NGER Measurement Determination methodology for facilities within your NGER reporting boundary. But for any operations outside that boundary, you'll need the GHG Protocol. And Scope 3, which NGER doesn't cover at all, requires its own data collection entirely. Start scoping that now if you haven't already.

July: Process, calculate, and apply NGA 2025 factors

The financial year has closed. Data collection should be substantially complete. Now you turn documents into numbers.

This is the month where the NGER Measurement Determination (2008, as amended) actually matters. For fuel combustion (the most common Scope 1 source), the core formula is straightforward: multiply the quantity of fuel consumed by the energy content factor from Part 2 of Schedule 1, then multiply by the per-gas emission factors from Part 3. For example, diesel has an energy content factor of 38.6 GJ/kL. Natural gas is 39.3 x 10^-3 GJ/m3. You need to calculate energy content separately, then emissions of CO2, CH4, and N2O individually before aggregating.

That per-gas breakdown is where the ANAO found most problems. Their performance audit of the NGER scheme revealed that 72% of the 545 reports examined contained errors, with 17% containing significant errors. Energy content calculations were among the most common failure points. The maths isn't hard. But doing it correctly across dozens of fuel types, hundreds of invoices, and multiple facilities with different measurement units is where mistakes creep in.

What goes wrong in July:

Energy content calculation errors. This is the single most common NGER reporting error according to practitioners, auditors, and the CER's own compliance data. The typical mistake: confusing units. A gas invoice shows consumption in cubic metres. The energy content factor is in GJ per cubic metre. But someone reads the bill as megajoules instead of cubic metres, or applies the factor for natural gas when the fuel is actually LPG, or forgets to convert kilolitres to litres before applying a per-litre factor.

The NGA Factors version problem also surfaces here. The 2025-26 legislative amendments changed emission factors for flared gas, introduced new requirements for reporting tonnes of flared gas when using methods 2, 2A, or 3, and mandated consistent market-based method application across all facilities within a controlling corporation. If you downloaded the NGA Factors workbook six months ago, check whether there's been a mid-year update. One wrong factor applied consistently across all your facilities produces a systematic error that auditors will find.

For AASB S2, July is when Group 2 reporting obligations formally begin. Your first AASB S2 annual reporting period starts on or after 1 July 2026. That means every piece of emissions data you're processing for NGER right now is simultaneously your foundational AASB S2 dataset. The quality bar just doubled. NGER errors that the CER might catch become AASB S2 errors that your external auditor will definitely catch, because AASB S2 disclosures are subject to assurance under ASSA 5010.

August: Quality assurance and anomaly detection

You've processed the data. Now break it.

August is for stress-testing your numbers before anyone else sees them. Run every check you can think of, and a few you haven't.

Start with year-on-year comparisons. Pull your 2024-25 NGER submission (you kept a copy, right?) and compare facility by facility, source by source. Any variance greater than 15% needs an explanation. Did that facility expand? Did you change fuel suppliers? Did consumption genuinely drop because of an efficiency project? Or did someone enter 1,200 kL of diesel instead of 120 kL?

Check for duplicates. When the same invoice gets processed twice, and it happens more often than anyone admits, the emissions double. This is especially common when multiple people handle data entry across different facilities, or when a bill reissue arrives and gets treated as a new document rather than a replacement.

What goes wrong in August:

The anomaly you don't investigate. Every dataset has outliers. The temptation is to assume they're real and move on. But an electricity consumption figure that's four times last year's value at the same facility usually means a data entry error, a unit conversion mistake, or a billing anomaly from the retailer (estimated reads can be wildly inaccurate). Investigating takes time. Not investigating means submitting a number you can't defend if the CER asks.

We're honest about this: anomaly detection is still partly manual work, even with software. Automated checks catch the obvious stuff, like duplicates and missing periods. But interpreting whether a 40% increase in natural gas consumption at a manufacturing facility is a genuine operational change or a broken meter requires someone who understands the operations. Don't outsource this step to someone who's never visited the site.

This is also the month to reconcile your energy production and consumption figures. The CER's EERS system was updated to automatically report consumption of solar, wind, water, or geothermal energy. If you input production of electricity from these sources, you must not separately input consumption. Double-counting renewable energy production as both generated and consumed is a compliance error the system won't catch for you.

September: Internal review, approval, and period locking

Your numbers are calculated, checked, and reconciled. September is about getting sign-off and locking things down.

This step gets rushed every year, and that's a mistake. Internal review isn't bureaucratic overhead. It's the last line of defence before your data goes to the regulator. The person who prepared the report shouldn't be the person who approves it. Get a second set of eyes, ideally someone with enough technical understanding to spot a suspicious number but enough distance from the data to ask uncomfortable questions.

Walk through the Section 19 report structure. Confirm that every facility mapped to the controlling corporation is accounted for. Verify that total corporate group emissions are the correct aggregation of facility-level figures. Check that the energy production and consumption totals are internally consistent. These metadata fields don't get the same attention as the headline emissions number, but they're what auditors and the CER check first, because they reveal whether the reporter actually understands their own reporting boundary.

What goes wrong in September:

Late-breaking data changes. Someone finds a missing fuel receipt. An invoice gets corrected by a supplier. A facility manager sends updated meter reads. Every change at this stage has to flow through recalculation. If you don't have version control on your data (and most spreadsheet-based processes don't), a September correction can quietly overwrite an August figure that was already verified. Period locking, where you formally close a month's data and prevent further edits without an explicit unlock, prevents this. It's a discipline most carbon accounting teams don't have.

The other September risk is approval delays. The person who needs to sign off on your NGER report is probably a CFO or COO. They're busy. They don't want to read a 40-page emissions report cold. Brief them early. Share a one-page summary in the first week of September. Flag anything unusual. If your emissions went up 20% because of a new facility or a change in operational control, they need to understand why before they'll sign.

For AASB S2, September is when you should be aligning your NGER data with your broader climate disclosure. AASB S2 requires governance disclosures (who's responsible for climate risk oversight), strategy disclosures (how climate risks affect your business model), and risk management disclosures (how you identify and manage climate risks). The emissions numbers from your NGER report feed into the Metrics and Targets pillar, but they're only one piece of a much larger disclosure. If your board hasn't been briefed on AASB S2 obligations, September is late but not too late.

October: Submit through EERS and don't look back

The deadline is 31 October 2026 at 11:59 pm AEDT. Do not leave it to the 31st.

The Clean Energy Regulator's Emissions and Energy Reporting System is accessed through their Online Services portal. If you haven't logged in since last year, do it in the first week of October. The CER migrated EERS to a new platform in 2025, and your login credentials or access permissions may have changed. Discovering this at 10 pm on 31 October is not where you want to be.

Complete a dry run submission in early October. Enter your data. Review the system-generated summaries. Check that the EERS validation rules don't flag anything unexpected. The system applies its own consistency checks, and sometimes those checks reveal issues you missed in your own QA, like a facility that's registered under an old corporate structure or an energy content figure that exceeds the system's plausibility range.

What goes wrong in October:

Portal access problems. Someone left the company. Authorisation delegations expired. The CER changed the authentication system. These are not technical problems. They're administrative ones. But they can cost you days you don't have.

The 2025-26 legislative amendments also introduced new Schedule 4 requirements: you now need to include accreditation codes and surrender ID numbers for renewable energy certificates if you're using the market-based method for Scope 2 electricity emissions. If you've been preparing your data without these reference numbers, you'll need to gather them before submission.

Submit at least three business days before the deadline. If the system rejects your submission or flags a validation error, you need time to fix it. The CER publishes late reporters. That's not where your company wants to appear, especially now that NGER reporters are also ASRS-reporting entities visible to investors, lenders, and insurers scrutinising your climate credentials.

The NGER-to-ASRS pipeline: why this year is different

Here's the part that changes the stakes for every NGER reporter.

Under the Treasury Laws Amendment (Financial Market Infrastructure and Other Measures) Act 2024, NGER reporters are automatically classified as ASRS Group 2 entities. Group 2 reporting obligations begin for annual reporting periods starting on or after 1 July 2026. So the 2025-26 data you're preparing for your October NGER submission? It's also the baseline dataset for your first AASB S2 climate-related financial disclosure.

The good news is that AASB S2 explicitly allows NGER reporters to use their NGER Measurement Determination methodology for Scope 1 and Scope 2 emissions at NGER-registered facilities. You don't need to redo your emissions calculations under the GHG Protocol for those facilities.

The complications are twofold. First, NGER uses AR5 global warming potentials while AASB S2 technically requires AR6 (which the ISSB standards reference). For most companies, the numerical difference is small, but it's a methodology difference your auditor may raise. Second, NGER doesn't cover Scope 3. AASB S2 requires Scope 3 disclosure (with a first-year exemption for Group 2 entities, but you still need to be building the data collection infrastructure).

If you're treating your October 2026 NGER report as just an NGER report, you're doing half the job. Build your data collection, quality assurance, and audit trail with both frameworks in mind. The effort is almost identical. The cost of doing it twice is not.

Carbonly helps NGER reporters automate document processing, apply the correct NGA 2025 factors, run anomaly detection, and maintain a full audit trail that satisfies both the CER and AASB S2 assurance requirements. Per-project pricing, no locked-in contracts. Reach out at hello@carbonly.ai to see how it works with your data.

Related reading: