ASRS Group 2 Is Live: What We're Seeing in the First Month

Companies that signed an assurance provider, centralised source documents and briefed the board before 1 July 2026 are operational. The rest are finding missing utility accounts and factor-of-1,000 unit errors in week one. Here is what the first month shows, and what Group 3 should do now.

Carbonly.ai Team July 6, 2026 10 min read
ASRSMandatory ReportingAASB S2Group 2
ASRS Group 2 Is Live: What We're Seeing in the First Month

Five days. That's how long ASRS Group 2 reporting has been live. Financial years starting on or after 1 July 2026 now carry mandatory climate disclosure obligations for mid-market entities - the ones with $200M+ revenue, $500M+ gross assets, or 250+ employees (meet two of three). And every NGER reporter not already in Group 1 got pulled in automatically through the registration pathway, whether they expected it or not.

Some entities are calm, methodical, already running data through systems they set up months ago. Many others are discovering they had less time than they thought.

That gap between companies who prepared and companies who assumed they'd figure it out later is already visible. In the first month of ASRS Group 2 reporting, real patterns are emerging - patterns that will define who gets through this cleanly and who ends up in ASIC's review crosshairs.

The two-speed reality

The split is stark. Some Group 2 companies had their data pipeline, governance framework, and assurance engagement locked in before 1 July. They're not relaxed - nobody is relaxed about first-year mandatory reporting - but they're operational. They know where their data lives. They've already processed Q3 and Q4 FY26 utility bills. Their assurance provider has seen a draft methodology. Their board has been briefed.

Then there are the rest.

These are companies where ASRS was a recurring agenda item at quarterly meetings but never became an active workstream. Someone was "looking into it." A consultant produced a scoping proposal in March that sat in someone's inbox. The CFO assumed the sustainability manager was across it. The sustainability manager assumed the CFO had allocated budget. Nobody confirmed anything with anyone, and now it's July.

Picture a mid-sized manufacturer asking in early July whether it can "get started and backfill the data later." The answer is technically yes, because the reporting period has just started and data is collected going forward. But if its scenario analysis isn't done, its governance disclosures aren't written, it hasn't engaged an assurance provider and it still doesn't have a complete inventory of its Scope 1 sources, it is facing a twelve-month sprint that should have started in February.

We wrote a detailed breakdown of what Group 2 actually requires back in February. If you haven't read it, now would be the time.

The assurance bottleneck is real

This is the one we've been warning about and it's playing out exactly as expected.

Australia's accounting profession has been reporting skills shortages for several years, and sustainability assurance draws on the same limited pool of qualified people.

Now layer mandatory sustainability assurance on top of that existing shortage. Every Group 2 entity needs limited assurance over their governance disclosures, climate risk strategy, and Scope 1 and 2 emissions under ASSA 5010. That's not optional. It's not a "nice to have for your first year." It's a legal requirement from year one.

In our view, assurance capacity is tight. Group 1 demand has already taken up much of the available sustainability assurance capacity. Some firms still have room, but engagement timelines may push well into your reporting period, which means your assurance work might not start until months after data collection begins.

Here's the practical problem. If you can't secure an assurance provider until October or November 2026, they're reviewing your methodology after you've already been collecting data for four or five months. If they flag a problem with your calculation approach - wrong emission factors, incorrect unit conversions, Scope 1 sources you missed - you're reworking months of data. That is a practical risk worth planning for.

Our advice hasn't changed since February: if you don't have an assurance engagement signed, stop reading this and go make phone calls. Today. Not next week.

Data quality problems surfacing early

In these first weeks, the pressure point is data. Specifically, the moment when someone actually tries to assemble twelve months of utility bills and fuel records and realises how bad the situation is.

A few recurring themes.

Missing accounts. Picture a property company with 40 sites that discovers it has utility data for 34 of them. Six sites had electricity accounts registered to the landlord, the tenant, or a previous building manager - and nobody knew which. Getting those accounts identified, contacted, and the historical data retrieved will take weeks. Maybe months.

Inconsistent units. Picture a manufacturer with gas consumption recorded in megajoules on some invoices and gigajoules on others, depending on the retailer, and an internal spreadsheet that doesn't distinguish between the two. A factor-of-1,000 error sitting quietly in a cell.

No source documents. This is the most common one. Companies know roughly how much electricity they used last year because they paid the bills. But the actual PDFs? Downloaded once, maybe forwarded to accounts payable, maybe saved to a shared drive that got reorganised in April. When the assurance provider asks "show me the source document for this 247 MWh figure," the answer can't be "I think it's in an email somewhere."

ASIC has explicitly stated they'll use their directions power from 2026 to compel entities to confirm accuracy, provide supporting documentation, or correct statements that appear incomplete or misleading. If your documentation trail is "we reconstructed the numbers from bank statements because we couldn't find the invoices," that's going to be a difficult conversation.

With Carbonly, every extracted data point links back to the source PDF and the calculation chain is logged, which is what that question needs. We built the AI document processing pipeline specifically for this problem. But honestly, even companies using spreadsheets can avoid the worst outcomes here if they set up a proper document management system now - first week of the reporting period - and enforce it consistently for twelve months.

What Group 1 taught us (and what Group 2 isn't learning)

We published a full analysis of what Group 1 reporters got wrong back in March. The short version: consultant dependency, generic scenario analysis that crumbled under assurance scrutiny, and emission numbers that moved when someone actually checked them.

ASIC's first review of Group 1 sustainability reports is underway. They've already signalled what they found when reviewing voluntary climate disclosures ahead of the mandatory regime: repetitive information, scenario analysis that "lacked detail about the underlying assumptions," and transition plans disconnected from actual targets and strategies. They prompted 15 companies and 4 superannuation trustees to revise or retract sustainability claims during their 2024-25 surveillance. Combined penalties from three greenwashing cases - Mercer ($11.3M), Vanguard ($12.9M), and Active Super ($10.5M) - hit $34.7 million.

Those were greenwashing actions, not ASRS non-compliance. But they signal where ASIC's attention sits. Accuracy matters. Vague claims get punished.

The Group 1 lesson that Group 2 companies should tattoo on their forearms is this: don't buy a report, build a capability. A one-off disclosure that nobody internal understands means more rework in year two, whoever produced it. Entities that invest in repeatable systems, even imperfect ones, can update last year's work instead of starting over.

For Group 2, the practical question is whether there's a faster path than a one-off engagement. There is, but it involves actually understanding your own emissions data - not outsourcing the understanding.

The scope 3 reprieve and why it's a trap

One piece of genuine good news: Scope 3 emissions are deferred for Group 2's first reporting period. You don't have to disclose them until your second year.

Don't mistake that for a free pass.

We're not fully confident in anyone's Scope 3 methodology yet - including our own, if we're honest. The supplier data quality problem is enormous. A mid-market company with 200+ suppliers might get actual emissions data from maybe 10-15 of them. The rest is estimates built on spend-based proxies that can be wildly inaccurate. We're working on it. Everyone's working on it. But nobody should pretend Scope 3 is solved.

Still, starting Scope 3 data collection now - even rough, category-level stuff - is the single best thing you can do to make year two less painful. The companies that defer Scope 3 thinking entirely until their second reporting period will face the same twelve-month sprint that Group 2 laggards are facing right now with Scope 1 and 2.

What Group 3 should be doing right now

Group 3 entities - $50M+ revenue, $25M+ assets, 100+ employees - start reporting for financial years from 1 July 2027. That's exactly twelve months away.

If you're Group 3 and you're reading this thinking "we've got a year," I'd point you at the Group 2 companies currently scrambling and ask you to notice something. Most of them also thought they had a year. In February, July felt distant. Now it's here and they're behind.

Three things Group 3 companies should do before the end of this month.

First, confirm your Group 3 status. The size thresholds are lower than you might expect. $50M revenue, $25M gross assets, 100 employees - meet two of three. Check the consolidated numbers, not just the parent entity. And check whether you're an NGER reporter, because that pulls you into Group 2 instead.

Second, inventory your emissions data sources. Every electricity account, every gas account, every fuel card, every refrigerant top-up log. Don't calculate anything yet. Just find out where the data physically lives and who controls access to it. This takes two to four weeks if someone is actually dedicated to it, and it's the step that catches every late starter off guard.

Third, get a rough budget approved. As an indicative range to confirm with your providers, first-year compliance spend for a mid-market entity is $200,000 to $350,000 all-in - covering assurance, scenario analysis, data systems, and internal or fractional sustainability leadership. That number shocks CFOs who haven't been tracking ASRS closely. Better to have the conversation now, with twelve months of lead time, than in March 2027 when the spend is unavoidable and the timeline is impossible.

Our Group 2 compliance checklist maps directly to Group 3 requirements - the disclosure obligations are identical, just shifted by twelve months.

The modified liability window is closing

One detail that keeps getting lost in the noise. The transitional liability protection - where only ASIC can bring action on Scope 3 emissions, scenario analysis, and transition plan disclosures, limited to injunctions and declarations - runs from 1 January 2025 to 31 December 2027.

For Group 2 entities reporting from 1 July 2026, your first reporting period falls within this window. Your second reporting period - when Scope 3 becomes mandatory - extends beyond it. From 1 January 2028, private litigants can bring civil claims against your climate disclosures. Shareholders. NGOs. Activist investors.

And remember: Scope 1 and 2 emissions have no transitional protection at all. Full liability from day one. Getting those numbers wrong carries full civil liability for the company, and directors who sign the declaration carry personal exposure. That's not a compliance nuisance. That's a legal risk that sits alongside your financial statements.

This is why data quality isn't a "nice to have for year one." It's the difference between defensible disclosures and personal liability for every director who signs the declaration.

What we'd tell any Group 2 entity

We're a carbon accounting software company. We have a commercial interest in companies automating their emissions data collection. I'm not going to pretend otherwise.

But here's the advice that holds regardless of which software, if any, you use.

Get your assurance provider signed this month. Not shortlisted. Signed. Every week you delay, the pool shrinks and the timeline compresses.

Centralise your source documents immediately. Every utility bill, fuel receipt, and refrigerant log from 1 July forward goes into one system - whether that's Carbonly, a competitor, or a well-organised SharePoint folder. The specific tool matters less than the discipline. Twelve months from now, an assurance provider is going to ask you to produce the source document for a specific figure, and you need to be able to find it in under a minute.

Brief your board before August. Directors need to understand what they'll be signing off on. Two hours, minimum. Cover the four AASB S2 pillars, the liability framework, and the assurance timeline. If they haven't been through a proper climate disclosure briefing, they're not ready to sign a declaration.

And start Scope 3 data collection now, even though it's deferred. You'll thank yourself in eighteen months.

ASRS Group 2 is live. The reporting period has started. The companies that treat this week as day one of a structured twelve-month process will be fine. The ones that treat it as a problem for Q3 or Q4 will repeat every mistake Group 1 made - with less sympathy from ASIC and less availability from assurance providers.

Your move.


Related Reading:


With Carbonly.ai, every figure in your ASRS or NGER report keeps an auditable trail back to the utility bill, invoice or operational document it came from. The platform automates the extraction underneath, built for Australian emission factors, regulatory frameworks and reporting timelines. To see that trail on your own documents, email hello@carbonly.ai.

Related articles

AASB S2 figures your assurance provider can trace back to the source

Bring one emission record your team finds hard to evidence. In 30 minutes we show the source document, factor version and change history Carbonly keeps on every record.

Book a 30-minute call Prefer email? hello@carbonly.ai

Per-project pricing, no per-seat fees. We reply within business hours.