ASRS Group 2: What to Lock Down in the First 90 Days

The clock started on 1 July 2026. If you are an ASRS Group 2 reporter (more than 500 employees, or revenue above A$500M, or assets above A$1B), you are now inside your first AASB S2 reporting year, and the decisions you make in the next 90 days will decide how painful August 2027 gets.

We say this from watching Group 1 go first. The Group 1 cohort did not fail because they lacked resources. They failed because they let the first quarter drift. Consolidation boundaries were still being argued in Q3. Baselines were being restated in Q4. Auditors turned up in the last quarter of the year to a data set that had been changing under them for nine months.

Group 2 does not have to repeat that. The first 90 days are not about producing anything for the disclosure. They are about locking the foundations so the rest of the year can execute without churn.

Why the first 90 days matter more than the last 90

AASB S2 is a financial disclosure standard. It sits inside the same audit and governance regime as your statutory accounts. That means every change you make late in the year has a ripple effect: restatements, re-controls, re-runs of the trial balance for emissions, fresh auditor testing. You cannot patch it in September like you might patch a voluntary sustainability report.

The pattern from Group 1 is stark. Companies that locked their consolidation boundary, baseline year, factor set, and reporting perimeter by the end of Q1 spent Q4 finishing narrative disclosure. Companies that did not, spent Q4 rebuilding the ledger.

There are eight things that need to be nailed down. In order.

1. Lock the consolidation boundary before you touch a single kWh

The consolidation boundary is the perimeter of what you are reporting on. AASB S2 requires it to be the same as your financial reporting perimeter, but the practical decisions inside that are where reporters get tripped up.

Three decisions have to be made and documented in the first fortnight:

Consolidation approach. Operational control, financial control, or equity share. AASB S2 defaults to the same approach as the parent's financial statements, which for most Australian corporates means financial control. But for joint ventures, PPPs, and minority investments, this decides who is on the hook for what.

Joint venture treatment. If you sit inside an unincorporated JV, decide up front whether emissions from the JV site flow into your ledger under operational control (100% if you operate it), financial control (per the accounting treatment), or equity share (your percentage). JV consolidation under all three methods should be sitting inside a single system so the alternatives can be modelled without shifting the ledger.

Newly acquired entities. If you closed an acquisition in FY26, the base date for including that entity in your emissions accounts is not automatic. AASB S2 lets you choose, but you have to choose once and document why.

Get these three onto a signed one-pager, dated, and filed with the audit committee papers. That page becomes the reference every auditor question comes back to for the next 12 months.

2. Snapshot the baseline before the ledger moves

The baseline is the single most audited number in your disclosure. Every downstream metric (intensity, percentage reduction, trajectory against targets) is calculated off it. If the baseline moves after Q1, everything moves with it.

Take the baseline year (typically FY22 or FY23 depending on how you set it) and lock it as an immutable snapshot. Not a spreadsheet tab. A time-stamped, version-controlled record that shows the exact inputs, factors, and calculations used, with the person who signed it off.

The baseline snapshot is a specific capability inside a proper carbon accounting system, and it exists for exactly this reason: so that when the auditor asks in month 11 "what was your FY23 Scope 1 gross?" you can produce the same number that was signed off in month 1. If your baseline lives in a shared Excel file, it will not survive the year.

We have written more on this in why spreadsheets stop working for compliance-grade carbon accounting and on the mechanics of restating a baseline after an error is caught. Both are worth reading before you sign off the snapshot.

3. Pin the emission factor version to NGA 2025

This one is quiet but expensive if you miss it. The DCCEEW National Greenhouse Accounts Factors are updated annually. The 2025 edition landed with revised state grid factors (NSW and ACT 0.64, Victoria 0.78, Tasmania 0.20 kg CO2-e/kWh, and the rest of the country in between).

You need to pin the factor version at the start of the year and not touch it. If DCCEEW releases NGA 2026 in mid-year (which they typically do), you keep reporting FY27 on NGA 2025 until year-end. Then you switch. Applying two different factor versions across a single reporting year invalidates comparability, and auditors will pick it up.

The factor set also has to carry three attributes on every emission record:

The factor value itself (numeric).
The source (NGA 2025, EPD Australasia, supplier-specific).
The GWP set applied (AR5 for NGER, AR6 for AASB S2 where you choose to render at AR6).

We have gone deep on the AR5 versus AR6 wrinkle in AR5/AR6 GWPs and their calculation impact. If you have methane in your Scope 1 (fugitives, coal seam, wastewater, waste, livestock), read that piece before you sign anything off. The GWP delta on methane between AR5 (25) and AR6 (29.8, or 27 depending on which AR6 value your assurance provider accepts) meaningfully moves your headline number.

Factor versioning is not optional detail. Read emission factor versioning and the audit trail for the mechanics of how to make this stand up under assurance.

4. Complete the Scope 3 materiality assessment early, not late

AASB S2 requires disclosure of material Scope 3 categories. It does not require all 15. The materiality assessment is where you decide which categories are in and which are out, and it has to be defensible under ASSA 5010 assurance.

The Group 1 error we watched most often was leaving the Scope 3 materiality call until Q3 because the data was not ready. That is backwards. You do the materiality assessment first, using proxy data if you have to, then you go and get the primary data for the categories you have declared material.

The practical shortlist for most Group 2 reporters comes down to:

Category 1 (Purchased goods and services) is material for almost everyone.
Category 3 (Fuel and energy related activities) is material if your Scope 1 and 2 is above about 25 ktCO2e.
Category 4 (Upstream transport) is material for anyone shipping physical goods.
Category 5 (Waste generated) is material for manufacturers and property.
Category 6 (Business travel) is material once headcount goes above 500.
Category 11 (Use of sold products) is material for anyone selling equipment, vehicles, buildings, or software running on hardware.

Everything else you assess and then usually disqualify. But the assessment has to be written down, signed by someone senior, and dated. Read the materiality threshold for emissions errors for how ASSA 5010 assurance treats this call.

5. Decide the system of record in the first month

This is the fork in the road. Either your emissions ledger lives inside a proper system, or it lives in a network of Excel files that gets rebuilt every year by whoever is on the desk that quarter.

The decision has to be made in month one because everything downstream depends on it. You cannot run a materiality assessment against data you cannot query. You cannot pin factor versions against a spreadsheet that has no version control. You cannot answer the auditor's traceability question if your source documents are in someone's Outlook folder.

What "system of record" means in practice:

One place where every emission record lives, from meter reading to reported number.
Every record traces back to a source document (invoice, meter export, fuel docket).
Every record carries the factor, source, and GWP set used.
Every change is logged with who, when, and why.
The whole thing survives the person who set it up leaving.

Whether that system is Carbonly or something else is your call. What is not optional is having one. We wrote a longer treatment of this in what your CFO needs from carbon reporting.

6. Engage the assurance provider now, not in Q4

Group 2 reporters need limited assurance on Scope 1 and 2 in year one under the ASSA 5010 phasing. Your Big 4 audit firm can do it, and most likely will. The engagement letter, the scoping conversation, and the audit plan need to be in place by the end of Q1.

Why now? Because the assurance provider will do a "readiness review" in Q2 or Q3, and what they flag then is what you have to fix before year-end. If you have already locked your consolidation boundary, baseline, factor set, and materiality, the readiness review takes a week. If you have not, it becomes a rebuild.

The ASSA 5010 audit preparation checks piece walks through the eight tests the assurance provider will run. Read it before your first scoping call so you know what they are going to ask. If your audit committee chair wants a wider frame, the audit committee chair AASB S2 playbook covers the governance side.

7. Set the board briefing cadence and stick to it

AASB S2 paragraph 6 requires disclosure of the governance body's oversight of climate-related risks and opportunities. If your board sees climate data twice a year, that will read badly in the disclosure. If they see it quarterly with a proper decision paper, it reads well.

The cadence we would recommend for a Group 2 first-year reporter:

Month 1: Board sign-off of consolidation boundary, baseline snapshot, and materiality assessment.
Month 4: First quarterly ledger check. Anomalies flagged. Trajectory against targets shown.
Month 7: Half-year review. Assurance provider readiness feedback tabled. Any restatement risks.
Month 10: Pre-close review. Disclosure draft tabled.
Month 13 (post year-end): Sign-off before disclosure.

Every board pack needs to show the number, the change since last quarter, the reason for the change, and the assurance status. That is a lot to produce quarterly if your ledger is a spreadsheet. It is one dashboard export if it is a system.

8. Write the operational calendar and put it on the wall

The last thing to lock in Q1 is the calendar for the rest of the year. Not a Gantt chart in someone's OneDrive. A one-page calendar that lists every deliverable, owner, and date.

The must-haves:

Monthly data close (by day 15 of the following month).
Quarterly anomaly review (last week of the quarter).
NGER submission (by 31 October 2026 for FY26, if in scope).
Half-year assurance readiness review (typically January or February).
Full-year assurance fieldwork (typically May and June).
Board sign-off of disclosure (per your cadence).
Public disclosure (with the annual report, typically August or September).

For NGER-registered entities, the 31 October deadline is non-negotiable and comes fast. The first-time NGER reporter practical guide walks through what needs to be in place to hit it cleanly.

Where this leaves you in early October

If you have followed the eight steps, by early October you will be 90 days in with:

A signed consolidation boundary and JV treatment note.
A locked baseline snapshot, version-controlled.
A pinned factor version (NGA 2025) with GWP set declared.
A signed Scope 3 materiality assessment.
A system of record holding the emissions ledger with traceable source documents.
An engaged assurance provider with a signed scoping letter.
A board cadence with the first briefing done.
A written calendar for the rest of the year.

None of that is disclosure content. It is the foundation the disclosure is built on. If you have it in place by October, the year executes. If you do not, you spend the next nine months on the back foot.

What we would do differently for Group 2

We watched Group 1 for a full cycle. If we were running the first 90 days for a Group 2 reporter today, the three things we would emphasise more than we did last year are:

Data traceability from day one. Every single emission record has to trace back to a source document with one click. Not a shared drive, not an inbox, one click. This is what auditors ask for first, and it is what breaks last.

Anomaly detection running in the background. You cannot wait until quarter-end to find that a meter reading has been double-counted or a supplier invoice was booked at the wrong unit. Anomaly detection sitting on the ledger, flagging outliers as they land, is the difference between a clean year and a clean-up quarter.

Assurance provider inside the tent from month one. Not because you want them influencing the numbers, but because you want to know what they will test before they test it. Their readiness review is where the surprises land. Better to know in Q2 than in Q4.

None of this is glamorous. It is process work. But process work in Q1 is what lets you spend Q4 on narrative disclosure instead of data forensics.

If you want to see what a locked-down system of record actually looks like against your own year, bring a recent NGER submission or a batch of supplier invoices to hello@carbonly.ai and we will show you how the same data lands inside Carbonly with the baseline snapshot, factor version pinning, JV consolidation, and anomaly detection already in place.