For most of the last decade, climate disclosure sat in a separate filing cabinet from the financial statements. The sustainability team kept it; the auditors looked at it lightly; and the board read it as commentary rather than a regulated disclosure. Four shifts have closed that distance at once. The regulator now treats climate disclosure as a financial reporting obligation. The auditor now applies the discipline of financial reporting controls to the underlying data. The capital markets now price the credibility of that data into the cost of debt. And the cost of running the current model is rising faster than the assurance bar it has to clear. Each pressure has a different source, but each one pushes the file to the same desk. The CFO now owns climate disclosure in both substance and name.
This piece sets out the framework that ties those four pressures together. It is the hub article for the SCIAR CFO Insight Series. The earlier pillars in the series treat each pressure on its own terms. AASB S2 and its assurance pathway sit with the regulators. Spreadsheet-based data and weak controls sit with the auditors. Sustainability-linked loans and green bonds sit with the treasurer. The consultant cost curve sits with the finance function. The argument here is that all four problems have the same underlying solution, and that the CFO who frames them as four separate projects will spend twice as much money taking twice as long to land in the same place as the CFO who treats them as one.
The framework rests on four pillars: regulation, infrastructure, capital markets, and cost. Each pillar is a separate workstream in most resource companies today. Each one is reporting to a different line of management. Each one is producing a different status report. The framework’s first move is to name the four pillars together, so the connections between them become visible.
The regulatory pillar is the statutory obligation. The Treasury Laws Amendment (Financial Market Infrastructure and Other Measures) Act 2024 brought a climate disclosure regime into Chapter 2M of the Corporations Act 2001. AASB S2 is the standard that directors must comply with. ASIC Regulatory Guide 280 sets the supervisory expectations for materiality, a reasonable basis, and disclosure quality. The assurance regime, governed by ASAE 3000 in its current form and by ASSA 5000 as it phases in, sets the evidence bar. The regulatory pillar is the one most resource sector CFOs have already engaged with. Pillar 1 of this series treats it in full.
The infrastructure pillar is the data system on which the disclosure is built. For most resource companies, that system is still a network of spreadsheets stitched together by an external consultant at year’s end. The five Excel control failures auditors flag in climate workbooks, covered in Pillar 4 of this series, are not edge cases. They are the modal pattern. Audit-ready infrastructure replaces the workbook with a pipeline that runs from the primary instrument (the fuel invoice, the haulage record, the meter reading) through a documented calculation engine to the disclosure footnote. Pillar 4 sets out what that pipeline looks like in Practise. Pillar 5 sets out the controls library that wraps around it.
The capital markets pillar concerns the pricing of disclosures by lenders, bond investors, and rating agencies. Sustainability-linked loan margins are now priced against assured climate KPIs. Green bond second-party opinions now examine the data assurance environment, not just the use-of-proceeds framework. The ICMA Green Bond Principles and the Sustainability-Linked Loan Principles define the disclosure baseline. The pricing differential between issuers with assured continuous data and issuers with annualised consultant estimates is now measurable. Pillars 7 and 8 of this series treat each instrument on its own terms.
The cost pillar is the total cost of running the disclosure cycle. For Group 1 entities running on the current consultant-led model, the spend trajectory does not flatten. Each cycle demands more Scope 3 categories, greater granularity, more assurance hours, and a higher bar for controls. A consultant-led model that clears limited assurance comfortably will not clear reasonable assurance at any reasonable cost. The total cost-of-ownership comparison between in-house infrastructure and continued reliance on consultants, addressed in Pillar 9 of this series, is the cost case supporting the infrastructure pillar’s capital request.
The four pillars look like four separate workstreams. They are not. Each one drives toward the same underlying requirement: a single source of climate data that is captured continuously, calculated through a documented engine, and verified by an independent certification body. That data system is what the AASB S2 directors’ sign-off requires to meet the reasonable basis test. It is what the auditor needs to test operating effectiveness over the reporting period. It is what the lender and bond investor need in order to price assured KPIs. And it is what the finance function needs in order to break the consultant spend cycle.
Once the four pillars are seen as four pressures on the same data system, the investment case simplifies. The CFO is no longer comparing four small projects competing for a slice of the discretionary budget. The CFO is making one capital decision against four returns. The board paper looks different. The conversation with the audit partner looks different. The conversation with the treasurer looks different. The cost line in the long-range plan looks different.
The financial reporting calendar is the most powerful integration lever the CFO has. The climate file is used to run on the NGER calendar, with an annual submission to the Clean Energy Regulator on 31 October. The data was prepared after the financial year close, often by external consultants, and the output landed in the sustainability report rather than in the disclosure pack that the CFO signs off. Under AASB S2, that separation no longer holds. The sustainability report is lodged at the same time as the financial report. The data must be in the consolidation pack on the financial close calendar, not on the NGER calendar.
The practical consequence is that climate data needs to land at the same close milestones as financial data. The month-end close becomes the natural cadence. Site-level fuel consumption, haulage and rail records, electricity meter reads, and procurement and offtake data should all be captured on a monthly cycle and reconciled to the source. Quarterly closes should produce a draft Scope 1, 2 and 3 estimate that the audit team can walk through. The year-end close produces the disclosure pack with no surprises and no consultant rebuild. The shift in cadence is significant, but it is the same cadence shift that finance functions ran a generation ago to bring management reporting onto a monthly close. The discipline is not new. Applying it to climate data is.
For Group 1 entities with a 30 June financial year end, the first AASB S2 reporting period closes on 30 June 2026. The first sustainability report must be lodged with the financial report. That timetable is now non-negotiable. The CFO who is still running the climate file on the NGER calendar in November 2026 has already missed the integration point.
The board paper that supports the directors’ declaration under the new sustainability reporting regime is the document on which the framework lives or dies. A weak board paper signals to the audit partner, the regulator, and the D&O underwriter that the four pillars are still being run as four separate workstreams. A strong board paper signals the opposite. Four content areas need to be covered in every cycle.
Regulatory status. Where the entity sits on the AASB S2 timeline. Which transition reliefs are being relied on and which are expiring? Any developments in ASIC guidance, AASB interpretive pronouncements, or peer enforcement that change the disclosure expectation. The materiality determination for the reporting period and the rationale for any change from the prior period.
Infrastructure and controls. The state of the data pipeline from the primary instrument to the disclosure footnote. The controls library and its testing record over the reporting period. Any control deficiencies identified during the cycle and the remediation status. The directors should be able to read this section and form a view on whether the controls operated effectively across the period, which is the bar reasonable assurance will eventually require.
Capital markets posture. The status of any sustainability-linked loans, green bonds, or transition bonds on issue. The KPI verification position relative to lender and bondholder requirements. Any pricing implications of the assurance position? The treasurer’s view of refinancing windows is shaped by the data assurance environment, which supports or constrains.
Cost trajectory. The current cycle spend is split by category (consultant, internal headcount, technology, assurance). The forward projection of that spend on the existing model. The alternative TCO under the in-house infrastructure model. The investment case for closing the gap and the timeline over which the savings land.
The board paper should not read as a sustainability paper. It should read as a financial reporting board paper. Structure, evidence weight, materiality framing, and the level of judgment disclosure should be drawn from the audit and risk committee’s existing playbook on the financial statements. The directors who sign the declaration are reading the paper through the lens of their statutory liability under the Corporations Act. Vague narrative reassurance is not what that lens is looking for.
The framework is only useful if it translates into a sequenced plan. A 12-month plan for a Group 1 CFO who is still running the current consultant-led model has four quarters and four deliverables.
Run a controls baseline against the current state. Document the five Excel control failures in the present workbook against the auditor’s lens. Document the methodology decisions held in the consultant’s working papers rather than in the company’s controls library. Run a cost baseline of the current cycle, with line items for consultant fees, internal time, assurance fees, and rebuild work. Output: a controls and cost baseline paper for the audit and risk committee.
Design the target-state data pipeline from the primary instrument to the disclosure footnote. Identify the source systems that already capture the inputs needed for the Scope 1, 2, and 3 calculations. Specify the calculation engine, the controls library, and the certification pathway. Confirm the assurance provider’s expectations against the target state. Output: an architecture paper that the audit partner has reviewed and the assurance provider has acknowledged.
Build the data pipeline. Migrate methodology from the consultant’s working papers to the company’s controls library. Begin month-end close integration. Run a parallel cycle in which the new pipeline produces the same numbers as the existing workbook, and reconcile them. Output: a working pipeline with a documented control set and an audit trail across at least one quarter of data.
Run the year-end close on the new pipeline. Produce the disclosure pack from the pipeline rather than from the consultant rebuild. Have the assurance provider test the operating effectiveness of controls across the reporting period. Lodge the sustainability report with the financial report on the statutory timetable. Output: a clean assurance opinion produced on infrastructure that will scale to reasonable assurance in the following cycle.
Four quarters are a tight calendar, but it is the calendar that the statutory timetable allows. The CFO who waits a year saves no time and incurs another cycle of consultant spend with no infrastructure to show for it.
The framework only holds together if the operating model behind it is clear. Most resource companies enter the AASB S2 cycle with climate disclosure ownership distributed across three executives. Group Sustainability owns the historical relationship with the data, the methodology, and the assurance provider. The Chief Risk Officer owns the risk register, the materiality assessment, and the capital markets risk disclosure. The CFO owns the disclosure outputs, the assurance contract, the director sign-off package, and the statutory lodgement. None of those three executives owns all of it. The result is that the problem is everyone’s responsibility and no one’s authority.
The framework requires a clearer assignment. The CFO owns the disclosure as a financial reporting obligation. The CFO sets the control expectations, contracts with the assurance provider, signs off on the disclosure pack, and presents the board paper. The CRO owns the materiality assessment, the climate-related risk disclosure, and the scenario analysis methodology. The CRO is the second line of defence on the controls library. Group Sustainability owns the operational data relationships at the site level, the methodology research and updates, and the engagement with rating agencies and sustainability finance providers on data quality. Group Sustainability is the first line of defence at the source data layer.
The model is not a reassignment of all climate work to finance. It is a clarification of accountability so the four pillars can run as one programme rather than three. The board sees a single owner. The audit partner has a single point of accountability for the controls environment. The treasurer has a single source for the assured KPIs lenders and bondholders are pricing. The auditor’s findings flow to the CFO, not to three different executives running three different remediation plans.
The honest test of any framework is whether it changes how the CFO spends time. The current pattern, for most Group 1 CFOs, is that climate disclosure consumes a concentrated burst of attention in the weeks before year-end, recedes for the rest of the year, and then returns when the auditor or a capital markets transaction forces it back onto the agenda. The framework changes that pattern in two ways.
First, attention spreads across the year. With a monthly close cadence on climate data, the CFO sees the same data flow on the same calendar as the financial close. Issues surface earlier. Methodology changes get raised before the year-end window closes. The audit partner is briefed on changes during the cycle rather than at the end. The board paper writes itself across the year rather than being assembled in three weeks at the end of June.
Second, the framework reframes the capital request. The CFO is no longer asking for a budget for a sustainability project. The CFO is asking for a budget for a financial reporting control project that also covers the climate file. The conversation with the CEO and the board changes accordingly. The capital is committed against the same standard as any other financial reporting control investment. The cost case carries the same weight as any other financial reporting compliance case.
Climate disclosure has moved inside the financial reporting perimeter in Australia. The four pillars (regulation, infrastructure, capital markets, and cost) push from four directions toward the same underlying requirement. A CFO who treats the four as one programme spends less, lands sooner, and presents the board with a single, coherent picture of where the entity sits on the disclosure maturity curve. A CFO who treats them as four separate projects spends more, lands later, and presents a fragmented picture that the audit partner, the treasurer, and the regulator each see through differently.
The framework is the integration point. Pillars 1 through 9 of the SCIAR CFO Insight Series treat each pressure on its own terms. This piece is the hub. The CFO who reads each pillar in turn and ties them back to the framework set out here will have the mental model needed to run the file on financial reporting discipline rather than on sustainability-era habit.
Nick Ogle has over 30 years of experience in Enterprise IT, spanning engineering, sales, and marketing roles across Australia, the USA, and APJ for various IT vendors.
Nick is passionate about Entrepreneurship and Software innovation that drives positive change. Currently, he is the Sales & Marketing Manager at SCIAR Systems, a Newcastle-based SaaS startup, where he helps commercialise its groundbreaking Bulk Commodity Logistics & Emissions Certification solutions.