What Your CFO Actually Needs From Carbon Reporting

A Deloitte survey of Australian CFOs found that 73% now view climate risk as material to financial performance. Two years ago, that figure was 35%. The jump didn't come from a sudden burst of environmental concern. It came from AASB S2 landing squarely in the CFO's lap.

Climate disclosures are now part of the annual report. Same Corporations Act provisions as the financials. Same director sign-off. Same audit scrutiny. The sustainability team still does the work, but the CFO owns the number the moment it sits next to revenue and EBITDA in the annual report. And most CFOs we talk to have the same complaint: they can't get a straight answer to four simple questions without triggering a multi-day data exercise.

Those four questions are: What's our carbon number? Are we compliant? What does it cost us? Are we on track?

If your sustainability manager can answer all four in under ten minutes with numbers that reconcile to both NGER and AASB S2, you're ahead of most companies in Australia. If the answer to any of them starts with "I'll need to check the spreadsheet and get back to you," you've got a problem that gets worse every quarter.

Question one: What's our carbon number?

This sounds simple. It isn't. The CFO wants total emissions by scope, with a trend line showing whether the number is going up or down. They don't want to learn what Scope 1 and Scope 2 mean. They want a figure that's defensible, current, and broken down the same way the rest of their financial reporting is structured: by business unit, by project, by period.

The problem is that carbon data doesn't flow like financial data. Revenue hits the general ledger in near real-time because every transaction runs through accounting software. Emissions data, by contrast, sits in PDF utility bills, fuel card statements, waste manifests, and supplier invoices scattered across inboxes and SharePoint folders. Someone has to collect all of it, extract the consumption figures, match them to the right emission factors from the NGA Factors workbook, and calculate the CO2-e total.

A mid-size company with 20 to 50 sites typically needs 400 or more hours per year just for that data assembly. By the time the sustainability manager compiles the board pack, the data reflects a period that ended six to eight weeks ago. The CFO is making decisions based on stale numbers.

What they actually want is a monthly summary. Total Scope 1, Scope 2, and (where available) Scope 3 in tonnes CO2-e. A comparison to the same period last year. A breakdown by business unit or project that matches the financial reporting structure. And an indicator showing whether the trend is up, down, or flat.

That's not a complicated ask. It's just impossible to deliver manually when the source data arrives as 200 PDFs per quarter in 15 different formats.

Question two: Are we compliant?

For the CFO, compliance isn't abstract. It's a risk register item with dollar consequences.

There are two separate compliance tracks running simultaneously for most entities now. NGER requires annual reporting to the Clean Energy Regulator by 31 October, covering Scope 1 and Scope 2 emissions for facilities exceeding 25 kt CO2-e (or corporate groups exceeding 50 kt CO2-e or 200 TJ). The penalty unit value under the Crimes Act 1914 sits at $330 as of late 2024, and civil penalties for NGER contraventions can run to hundreds of penalty units per offence. Non-trivial money.

AASB S2 adds a second layer. Climate disclosures are now part of the annual report filed under the Corporations Act. Group 2 entities start reporting for financial years from 1 July 2026. Group 3 follows from 1 July 2027. And here's the part CFOs care about most: the same auditor who signs off on your financials now provides assurance over your climate disclosures under ASSA 5010.

In Year 1, that means limited assurance over governance disclosures, strategy (AASB S2 paragraphs 9(a), 10(a) and 10(b)), and Scope 1 and 2 emissions (paragraph 29). By Year 4 (financial years from 1 July 2030), it steps up to reasonable assurance over everything. We've written a detailed breakdown of the eight evidence tests auditors will run under ASSA 5010.

What the CFO needs here isn't a tutorial on assurance levels. They need a traffic light. Is our NGER submission on track for the October deadline? Is our AASB S2 disclosure ready for the annual report? Are there any gaps the auditor is likely to flag? Red, amber, green. Backed by an audit trail they can point the assurance team to without routing every question through the sustainability manager.

We're honest about this: the audit trail is the part most companies are furthest behind on. We've spent 18 years building enterprise data systems at BHP, Rio Tinto, and Senex Energy, and the single consistent pattern is that auditors don't care about your narrative. They care about your evidence chain. Every emission figure needs to trace back to a source document, an emission factor, and a calculation methodology. If that chain is a spreadsheet with manual lookups, the auditor will find the break.

Question three: What does this cost us?

This is where carbon reporting becomes a finance conversation, not a sustainability one.

The real cost of ASRS compliance for a mid-size entity runs between $750,000 and $1.6 million per year according to Treasury's Policy Impact Analysis. That includes internal labour, consulting fees, assurance costs, system costs, and legal review. But the CFO doesn't want a lump sum. They want to know where the money goes and whether it's well spent.

The cost breaks down roughly like this. Data collection and processing eats 40 to 50% of the total. External consulting (gap assessments, scenario analysis, transition plan narrative) takes another 20 to 30%. Assurance fees for ASSA 5010 limited assurance range from $50,000 to $150,000 depending on complexity. Legal review of the disclosures adds $20,000 to $60,000. And systems and tooling typically account for 5 to 15% of the budget.

Then there's a cost that sits outside the compliance budget entirely: ACCU exposure under the Safeguard Mechanism. If your facilities exceed their declining baselines, you're buying Australian Carbon Credit Units to cover the gap. ACCU spot prices have been sitting around $30 to $36, but the government's fixed-price cap for excess emissions starts at $75 (indexed at CPI plus 2% per year). For a facility 25,000 tonnes over baseline, that's roughly $912,000 in surrender obligations at current rates. And the baselines drop 4.9% every year.

The CFO wants this information project by project. Not because they're interested in carbon accounting, but because they need to allocate the cost to each project's P&L. A construction company running 30 active sites needs to know the carbon compliance cost per project, the same way they know the insurance cost per project. It's an input to tender pricing, to margin calculations, to capital allocation decisions.

This is also why per-project pricing for carbon accounting software makes sense to finance teams. It's a cost that maps directly to the P&L line it supports, not a central overhead that gets buried in shared services.

Question four: Are we on track?

Targets without tracking are just press releases. And AASB S2 paragraph 33 requires entities to disclose their progress against climate-related targets, including whether they're using offsets, what metrics they're tracking, and whether their targets have been validated by a third party like SBTi.

The CFO's version of this question is blunter: are we going to hit our target, or are we going to have to explain why we didn't?

Most companies set a target (say, 43% reduction by 2030, aligning with the national target) and then don't track progress until the annual report is due. By then, it's too late to course-correct. If your emissions intensity crept up 6% in the first half of the year because a new project site ran on diesel generators instead of grid power, you want to know that in July, not in February when the annual report is being drafted.

The financial translation matters here too. Every tonne of CO2-e your company emits above its reduction trajectory has a cost. That cost might be ACCUs under the Safeguard Mechanism. It might be the reputational cost of missing a publicly stated target. It might be the capital cost of a transition plan that requires accelerated investment in later years because early years were wasted. The CFO needs to see all of that as a financial projection, not just an emissions chart.

We're still working out the best way to present Scope 3 trajectory data. Scope 1 and 2 are relatively straightforward because the data comes from sources you control: your utility bills, your fleet fuel, your process emissions. Scope 3 depends on supplier data quality, and that varies enormously. We won't pretend the Scope 3 trajectory forecast is as reliable as Scope 1 and 2. It isn't, not for anyone, regardless of what their marketing says.

Why the numbers don't tie (and why the CFO hates that)

Here's a problem that doesn't get enough attention. In many organisations, NGER reporting and AASB S2 disclosures are prepared by different people, using different data sources, with different organisational boundaries, and sometimes different emission factors.

NGER uses the NGER Measurement Determination, which specifies particular methods (Method 1 through Method 4) for different emission sources. AASB S2 paragraph 29(a)(ii) requires measurement in accordance with the GHG Protocol Corporate Standard, except where it conflicts with AASB S2 itself. In practice, the numbers should be close. But "close" isn't good enough when both figures appear in filings that carry legal consequences.

The reconciliation problem gets worse when a consultant prepares the NGER submission and the sustainability team prepares the AASB S2 disclosure independently. Different source data. Different spreadsheets. Different rounding. The CFO ends up with two numbers that should match and don't, and no clear explanation for the difference.

The fix isn't complicated in principle. Both reports should pull from the same underlying dataset, with the same source documents, the same emission factors, and the same organisational boundary. The differences (NGER's facility-level focus versus AASB S2's entity-level consolidation, for instance) should be documented and reconcilable. But that's hard to do when your data sits in spreadsheets that the consultant emailed back in October and the sustainability manager updated in January.

Carbonly.ai was built to solve exactly this. One dataset. One audit trail. NGER and AASB S2 reports generated from the same source-traced data, so the numbers tie automatically. When the auditor asks why your AASB S2 Scope 2 figure differs from your NGER Scope 2 figure by 342 tonnes, you can show them exactly which facilities are included in one boundary but not the other, and trace every kilowatt-hour back to a specific bill.

What the monthly CFO report should look like

We've talked to enough finance teams to have a view on this. The CFO doesn't want a dashboard login. They don't want to learn a new platform. They want a PDF in their inbox on the first Monday of each month.

Page one: Emissions summary. Total Scope 1 and 2 in tonnes CO2-e, comparison to the same month last year and the year-to-date trajectory. Broken down by business unit or project, matching the financial reporting structure.

Page two: Compliance status. NGER submission timeline (data collected, gaps remaining, submission deadline countdown). AASB S2 readiness status. Any audit trail gaps flagged. Upcoming assurance milestones.

Page three: Cost impact. Compliance spend year-to-date (internal labour, consulting, assurance, systems). ACCU exposure if applicable: current position versus baseline, projected surrender cost at current ACCU prices. Per-project carbon cost allocation.

Page four: Target progress. Actual emissions versus reduction target trajectory. Variance analysis. Flagged projects or business units driving the variance. Estimated financial impact of being ahead or behind target.

Four pages. Four questions answered. Monthly. Consistent. Auditable.

That's the reporting rhythm AASB S2 implicitly demands. Paragraph 6 requires disclosure of how often the governance body considers climate-related matters. If your answer is "once a year when we prepare the annual report," your auditor will have questions.

The shift from sustainability project to finance function

BDO's 2025 Sustainability CFO Outlook Survey found that 47% of CFOs expect their involvement in ESG strategy and execution to increase in the next 12 months. That's not surprising given the regulatory trajectory. What's surprising is that 53% apparently think it won't.

Carbon reporting is becoming a finance function. Not because sustainability teams aren't capable, but because the regulatory framework has placed it inside the annual report, subject to the same assurance standards as financial data. The CFO doesn't need to become a carbon accounting expert. But they do need the same quality of information they get from every other part of the business: timely, accurate, auditable, and expressed in dollars.

If you're a sustainability manager reading this, the implication isn't that your role shrinks. It's that your role shifts from data assembly to analysis and strategy. The mechanical work of collecting bills, extracting numbers, matching emission factors, and building spreadsheets is the part that should be automated. The judgment calls, like which reduction initiatives deliver the best ROI, how to structure the transition plan narrative, and where the Scope 3 data gaps actually matter, those require human expertise.

If you're a CFO reading this, start with one question: can your team produce those four answers (total emissions, compliance status, cost exposure, target progress) with numbers that reconcile between NGER and AASB S2, backed by an audit trail your assurance provider will accept under ASSA 5010?

If yes, you're in better shape than most.

If the answer involves the words "spreadsheet," "I'll need to check," or "we'll have it by next week," reach out at hello@carbonly.ai. Carbonly.ai offers per-project pricing so the cost sits where it belongs: in each project's P&L, not as an invisible overhead in shared services.