Quantifying Transition Risk Under AASB S2: From Narrative to Numbers

The first round of AASB S2 disclosures from Group 1 entities is now public, and the gap between the strong reports and the weak ones is not in governance or strategy. It is in paragraph 30(b).

Most Group 1 entities took the transition relief under AASB 2024-3 in year one. That relief expires for annual reporting periods beginning on or after 1 January 2026, which for most calendar-year entities means the 30 June 2026 financial year end is the first time the full quantitative disclosure of "current and anticipated financial effects" becomes mandatory.

If you are a CFO or climate risk lead at a Group 1 entity, or you are preparing for Group 2 reporting (FY starting 1 July 2026), the question is no longer whether you describe transition risk in your sustainability report. It is whether you can put a dollar figure on it that holds up under ASSA 5010 assurance.

We have spent the last 18 months watching how this actually plays out across construction, mining, property and financial services clients. The honest answer is that quantification is harder than the standard makes it sound, and most of the work happens outside the climate team.

What paragraph 30(b) actually requires

AASB S2 paragraph 29 sets out the broad strategy disclosures. Paragraph 30 is where the standard gets specific about financial effects, requiring entities to disclose "the current and anticipated effects of climate-related risks and opportunities on the entity's financial position, financial performance and cash flows."

Paragraph 30(b) is the bite. It requires quantitative information unless the entity determines that quantitative information would not be useful, in which case qualitative information is permitted with an explanation. ASIC has been clear in Regulatory Guide 280 that the "not useful" exception is narrow. It is not a backdoor for entities that simply have not done the work.

The transition relief in AASB 2024-3 lets entities provide qualitative information instead of quantitative for the first annual reporting period only. After that, the burden shifts.

What auditors are looking for in year two:

• Anchored amounts (a dollar figure, a tonnage, a percentage of revenue or capex)
• A documented methodology
• A connection to the entity's financial statements line items
• Sensitivity to at least two scenarios under paragraph 22
• An honest distinction between "current" effects (already in the numbers) and "anticipated" effects (modelled forward)

The "current" effects piece is where most year-one reports were weakest. A current effect is something already hitting the P&L or balance sheet. Safeguard Mechanism ACCU purchases for a 2024-25 exceedance are a current effect. A 4% increase in insurance premiums for cyclone-exposed assets is a current effect. Most entities did not separate these from speculative forward effects, and the auditors are now asking for it.

The Safeguard Mechanism is the easiest number to anchor

If you operate a facility covered by the Safeguard Mechanism, you have a quantifiable transition cost sitting in front of you right now.

The Safeguard baseline decline rate is 4.9% per year through 2029-30. Your baseline tonnage shrinks by 4.9% annually. If your facility emissions stay flat, the gap between baseline and actual widens each year, and that gap has to be closed with ACCU surrenders or SMC trades.

The arithmetic for a hypothetical mid-tier covered facility:

• Current baseline: 250,000 tCO2-e
• Actual emissions FY25-26: 240,000 tCO2-e (10,000 t buffer)
• Projected baseline FY29-30: ~206,400 tCO2-e (after four years of 4.9% decline)
• If actual emissions stay at 240,000 t, the FY29-30 gap is ~33,600 t

At ACCU spot prices around $35-40 per tonne (Clean Energy Regulator quarterly data), that is $1.17M to $1.34M per year of direct compliance cost by FY29-30. At forecast prices of $50-75 per tonne (some analyst views), the same gap is $1.68M to $2.52M.

That is a paragraph 30(b) number. It connects to the financial statements (cost of goods sold, or below the line as a separate compliance cost), it has a documented methodology (Safeguard baseline decline times projected production), and it can be sensitivity-tested by varying the ACCU price assumption.

We have written more about the Safeguard Mechanism 2026 changes and how to track compliance against declining baselines, but for AASB S2 purposes, the key point is that this is the most defensible quantified transition risk you can disclose. It is grounded in current regulation, not a 2050 net zero scenario.

Carbon price exposure where you are not the Safeguard counterparty

The harder quantification problem is when carbon costs are flowing through your business indirectly. Three common channels:

Energy contract pass-through. Large industrial energy contracts increasingly include a carbon cost component, either explicit (a Safeguard Mechanism pass-through clause in a gas supply contract) or implicit (the embedded carbon cost in electricity from a generator with its own compliance obligations). If you have a multi-year energy supply contract, your procurement team has the clauses. Read them. Quantify the exposure.

Supplier price increases. Cement, steel, aluminium, freight. If your suppliers are Safeguard covered or are facing CBAM in export markets, their cost base is shifting. Year one disclosures handled this badly because most entities just wrote "we expect supplier costs to increase" without a number. Year two needs an estimate, even a rough one, with a stated assumption.

Customer carbon cost pass-through. This one cuts the other way. If your customers are Safeguard covered and you are a major supplier of carbon-intensive inputs, they will push back on prices or seek substitutes. The quantification is "what fraction of revenue is at risk if customers reformulate procurement to a lower-carbon alternative."

For each of these, the technique is the same: identify the exposed contract or revenue stream, multiply by a carbon price assumption, sensitivity-test the assumption across at least two scenarios. The number does not need to be precise. It needs to be defensible.

Asset stranding for fossil fuel and carbon-intensive assets

If you hold long-life assets whose value depends on a market that may not exist in 2040 or 2050, AASB S2 paragraph 30(b) wants you to think about impairment.

This is where the climate disclosure and the financial statements collide. AASB 136 (Impairment of Assets) already requires impairment testing when there are indicators. AASB S2 is now asking entities to be explicit about how climate transition scenarios feed into the cash flow projections used in those impairment tests.

The disclosure questions:

• What is the carrying value of assets exposed to demand collapse under a 1.5°C scenario?
• What discount rate adjustments has the entity made to reflect transition risk?
• Are there assets where useful life has been shortened in the books because of transition assumptions?

ASIC has flagged this area for scrutiny. If your sustainability report describes a 1.5°C scenario in which thermal coal demand falls by 75% by 2040, but your financial statements still depreciate coal-related assets over 30 years at unchanged discount rates, the auditor will ask why.

The honest answer for many entities is that the impairment models have not been updated yet. The disclosure should say so, not pretend they have.

Scenario sensitivity is where the numbers come from

Paragraph 22 of AASB S2 requires climate-related scenario analysis. Paragraph 30(b) wants the financial effects to flow from those scenarios. The link between them is the actual workflow most entities are still building.

A workable approach we have seen across multiple clients:

Pick three scenarios. The standard does not mandate three, but three works for sensitivity. Most CFOs anchor on:

• 1.5°C aligned (orderly transition, high carbon price, fast demand shift)
• 2°C / "delayed transition" (policy shock around 2030, disorderly response)
• 3°C / current policies (physical risk dominates, transition risk muted)

The NGFS scenarios are the most common reference, partly because the IFRS S2 illustrative guidance points to them.

Translate scenarios into operating assumptions. This is the step most entities skip. A "1.5°C scenario" is not an input to your P&L. A carbon price of $90/tCO2-e by 2030, a 30% reduction in thermal coal demand, and a 15% increase in cement prices is an input. The translation work happens in spreadsheets owned by finance, not by the sustainability team.

Run the assumptions through revenue, COGS, capex and impairment. This is where scenario analysis becomes a financial modelling exercise rather than a narrative exercise. Most year-one disclosures stopped before this step.

Disclose ranges, not point estimates. Paragraph 30(b) accepts ranges. A disclosure that says "anticipated effects on EBITDA range from -$8M to -$24M per year by 2030 across the three scenarios tested" is more useful than a single point estimate that implies false precision.

We covered the scenario mechanics in more depth in our climate scenario analysis guide and carbon reduction planning under scenarios. The CFO-side of this is laid out in our first AASB S2 disclosure playbook.

What "current" effects actually look like

The "current" half of paragraph 30 is underrated. Auditors are asking what climate-related amounts are already in the financial statements, and most entities have not done the inventory.

A non-exhaustive list of items we have seen entities pull together:

• ACCU surrenders for Safeguard compliance (current period cost)
• Climate-related insurance premium increases (often 8-15% for cyclone or bushfire exposed assets)
• Capex on emissions reduction projects already approved (electrification, fleet transition, methane capture)
• Costs of NGER reporting, AASB S2 reporting and external assurance
• Asset write-downs already taken where climate was a contributing factor
• Litigation provisions (where applicable)

These are real numbers from real ledger lines. They form the "current effects" disclosure. The "anticipated effects" disclosure then sits alongside as the forward-looking piece.

Climate Active certification used to feature in this list, but the Federal Government's position retirement of the Climate Active brand in early 2025 means voluntary certification credits are no longer a defensible standalone disclosure for AASB S2 purposes. If your prior disclosures relied on Climate Active, this is a year-two cleanup item.

How TCFD got absorbed

For CFOs who built reporting capability under TCFD between 2018 and 2023, the good news is that the structural work carries over. AASB S2 is built on the four-pillar TCFD architecture (Governance, Strategy, Risk Management, Metrics and Targets). The IFRS Foundation took over TCFD monitoring when the TCFD disbanded in October 2023, and IFRS S2 (the parent of AASB S2) absorbed all 11 TCFD recommendations.

What AASB S2 adds beyond TCFD:

• Mandatory rather than voluntary
• More prescriptive on scenario analysis (paragraphs 22-24)
• Tighter financial connectivity (paragraph 30)
• Industry-specific metrics via the SASB-derived guidance
• Mandatory Scope 1, 2 and material Scope 3 disclosure with AR6 GWPs

The AR6 GWP point catches NGER reporters every time. NGER still uses AR5 GWPs under the NGER Determination. AASB S2 requires AR6. Methane is 27.9 under AR6 versus 28 under AR5 (small difference for CH4), but the bigger gap is on some HFCs and N2O. Your NGER submission and your AASB S2 disclosure will not match if you do not handle this. We wrote up the mechanics in our AR5/AR6 dual-framework explainer.

How this looks in practice with a consultant in the loop

If you are running this through a consultant (most mid-tier entities are), the workflow looks something like this:

1. Your sustainability team or consultant runs the scenario analysis and produces qualitative narrative
2. Finance is handed the scenarios and asked to translate them into P&L impacts
3. Finance pushes back because the assumptions are not concrete enough
4. Multiple iterations to get scenario inputs to a level where they can drive financial modelling
5. Risk committee reviews the financial effects ranges
6. Audit and risk committee sign off on the disclosure language
7. ASSA 5010 limited assurance over the methodology and the numbers

The bottleneck is almost always step 3 and 4. Consultants are good at running scenarios. Finance is good at modelling P&L. The handoff between them is where the work compounds.

A pattern that is becoming standard: maintain the scenario library and the financial impact ranges in a system that can be re-run year over year, rather than rebuilding the analysis each reporting cycle. That is partly what we built our scenario builder, targets and MACC modules for.

A practical workflow: build scenarios in the scenario builder, translate them into reduction pathways with the action library, layer carbon prices in via the MACC view to see which interventions cross the threshold under each scenario, and lock the period at sign-off so the assured numbers do not move. The JV consolidation module (operational, financial or equity-share) matters for entities with joint ventures, since paragraph 30(b) financial effects need to align with the boundary used in the financial statements.

What it does not solve: the actual financial modelling still happens in your finance team's models. We feed the inputs and hold the audit trail. We do not replace the FP&A function.

What to do before 30 June 2026

If you are a calendar-year Group 1 entity applying transition relief in year one, your year two reporting period starts 1 January 2026. By 30 June 2026, you want:

1. A documented list of "current effects" already in the financial statements with ledger references
2. Three scenarios with quantified operating assumptions (carbon price, demand changes, input cost changes)
3. P&L and balance sheet impact ranges across the three scenarios, with sensitivity to the key assumptions
4. A clear separation between current and anticipated effects in the draft disclosure
5. Risk and audit committee review of the methodology (not just the numbers)
6. Engagement with your ASSA 5010 assurance provider on what evidence they will want to see

The audit committee chair playbook sets out what the committee needs to ask. The climate risk register guide covers the upstream work that feeds the financial effects disclosure.

The entities that get this right will not be the ones with the best scenarios. They will be the ones whose finance team owns the numbers.

If you want to see how a working scenario-to-numbers pipeline holds together with an audit trail attached, reach out. We will walk you through what year two disclosure looks like from inside the system, with your own data.