ESG Reporting for CFOs

I started building ESG reporting infrastructure in my finance function before anyone asked me to. Not because I had a personal conviction about sustainability (though I do) but because I could see a regulatory trajectory that was going to land squarely on the CFO’s desk, and I wanted to be ready when it arrived rather than scrambling after.

That was eighteen months ago. Today, the BRSR Core framework is mandatory for the top 1,000 listed companies in India by market capitalisation. The ISSB has published IFRS S1 and S2, and jurisdictions around the world are deciding how quickly to adopt them. The EU’s CSRD is generating sustainability disclosures that are flowing into the financial statements of companies with European operations. And in every finance team I talk to, the same question is surfacing: who owns this?

The answer, increasingly, is the CFO. And that changes what FP&A teams need to build.

Why Sustainability Reporting Is a Finance Problem

For years, ESG reporting lived in the corporate communications or sustainability team. The output was a glossy PDF published annually, disconnected from the financial statements, and subject to limited (if any) external assurance. The data collection was manual. The metrics were self-selected. The audience was primarily ESG rating agencies and socially responsible investors who represented a niche of the shareholder base.

That era is ending. What is replacing it looks much more like financial reporting.

SEBI’s BRSR framework requires quantitative disclosures on energy consumption, water usage, waste generation, employee well-being, and value chain impacts. These are not narrative descriptions. They are structured metrics with defined calculation methodologies, comparable across companies and across periods. BRSR Core goes further and mandates reasonable assurance on specific metrics for the top 150 listed companies, with the assurance perimeter expanding to the top 1,000 on a phased timeline.

When a disclosure requires reasonable assurance, it needs the same rigour as a financial statement line item: defined data sources, documented calculation methodology, internal controls over the data, and an audit trail that an assurance provider can follow from the reported number back to the source. That is a finance problem. It requires the same infrastructure, the same discipline, and the same governance that the finance function already applies to financial data.

The ISSB standards (IFRS S1 and S2) make the connection to financial reporting even more explicit. IFRS S1 requires disclosure of sustainability-related risks and opportunities that could reasonably be expected to affect the entity’s cash flows, access to finance, or cost of capital. IFRS S2 focuses specifically on climate-related risks and requires scenario analysis of the financial impact under different climate pathways. Both standards are designed to be read alongside the financial statements, not in a separate document. The connectivity between sustainability disclosure and financial reporting is a design principle, not an afterthought.

This is why the reporting capability needs to sit within the finance function. The sustainability team brings domain expertise on environmental and social metrics. But the infrastructure for collecting, validating, controlling, and assuring quantitative data at the standard required by BRSR and IFRS S1/S2 is the same infrastructure that finance teams have been building for decades. It would be wasteful to build a parallel system from scratch when the foundation already exists.

The Data Infrastructure Challenge

The hardest part of ESG reporting is not understanding the standards. The standards are well-drafted and reasonably clear about what to disclose. The hardest part is getting reliable data.

Financial data flows through a general ledger that serves as a single source of truth. Every transaction is captured, classified, and reconciled. The infrastructure has been refined over centuries, and while it is not perfect, it provides a controlled, auditable record of the economic activity of the business.

Sustainability data has no equivalent backbone. Energy consumption data might come from utility bills, building management systems, or manual meter readings, each with different levels of accuracy, granularity, and frequency. Scope 1 and Scope 2 greenhouse gas emissions require energy data combined with emission factors that vary by geography and source. Scope 3 emissions (the value chain emissions that often represent 80% or more of a company’s total carbon footprint) require data from suppliers and customers that the reporting entity does not control.

Water and waste data is similarly fragmented. Employee well-being metrics come from HR systems that were not designed for external reporting. Supply chain social metrics require supplier self-assessment, which introduces reliability concerns that anyone who has worked in procurement audit understands immediately.

When I started building the data infrastructure for ESG reporting, I mapped every BRSR metric to three things: the data source, the data owner, and the control point. That mapping exercise took six weeks and produced a picture that was sobering but useful. About 40% of the required data was already captured in existing systems with adequate controls. Another 30% was captured somewhere in the organisation but without the controls, frequency, or granularity needed for assured disclosure. The remaining 30% required new data collection processes.

That 60% gap is the real scope of the implementation, and it is a multi-year project to close it properly. Anyone who tells you that ESG reporting is a compliance exercise that can be handled in a quarter has not looked closely at the data infrastructure it requires.

Building the Capability Before It Becomes Mandatory

I deliberately chose to start building this capability ahead of the regulatory timeline, and I want to explain why, because the argument goes beyond “it is always better to be early.”

The first reason is data quality. The first year of any new reporting regime produces unreliable numbers. I saw this with Ind AS 116 implementation, where the first-year lease calculations required multiple iterations before the data was clean enough to report. I saw it with ASC 606 adoptions in the US, where the initial revenue disaggregation required rework when systems did not capture the dimensions the standard required. The same pattern will play out with ESG data, and the organisations that start early get their unreliable year out of the way before the numbers are subject to mandatory assurance.

The second reason is process integration. ESG data collection that runs as a standalone year-end exercise will always be a scramble. When the process is integrated into the monthly close rhythm (energy data reconciled monthly, emissions calculated quarterly, BRSR metrics tracked on the same cadence as financial KPIs) the year-end disclosure becomes a compilation exercise rather than a data hunt. Building that integration takes time, and it is harder to do under regulatory deadline pressure.

The third reason is organisational learning. The finance team needs to develop fluency with sustainability concepts, emission factor selection, materiality assessment, and the specific assurance expectations of BRSR and ISSB. The sustainability team needs to develop fluency with internal controls, data governance, and the level of documentation that external assurance requires. Both teams need to learn how to work together. That mutual learning is more effective when it happens at a pace that allows mistakes to be learning opportunities rather than compliance failures.

The fourth reason is strategic. The CFO who has ESG reporting capability in place before it becomes mandatory is the one who can use sustainability data to inform business decisions, not just comply with disclosure requirements. When Scope 2 emissions data is reliable and timely, it can feed into the cost model for energy procurement decisions. When water consumption data is tracked at facility level, it can inform capital allocation for efficiency investments. When employee well-being metrics are captured with the same rigour as financial metrics, they can support workforce planning decisions. The compliance value is a prerequisite, but the strategic value is the real return on investment.

What This Means for FP&A Teams

FP&A teams will feel the impact of ESG reporting in three specific ways, and all three require proactive preparation.

First, climate-related financial disclosures will change the forecast. IFRS S2 requires disclosure of the financial effects of climate-related risks and opportunities, including the expected impact on revenue, costs, assets, liabilities, and capital expenditure. This is not a qualitative narrative. It requires quantification, and the natural home for that quantification is the FP&A team’s planning and forecasting process. If you run scenario analysis on your three-year plan, you will need to add a climate scenario (or integrate climate assumptions into your existing scenarios). That means understanding how carbon pricing, physical climate risk, energy transition costs, and changing consumer preferences translate into the financial drivers your model already uses.

Second, sustainability KPIs will enter the variance analysis rhythm. As ESG metrics move from a standalone annual report into the monthly or quarterly reporting cadence, they will need the same variance analysis treatment as financial KPIs. When emissions intensity per unit of revenue increases, someone needs to explain why and what is driving it, just as someone explains why gross margin moved. FP&A teams that already have a strong variance analysis practice (which I covered in Variance Analysis: Making the Monthly Actuals Review Actually Useful) have the analytical framework. They need to extend it to cover sustainability metrics.

Third, the driver-based model needs sustainability drivers. If your revenue forecast is built on volume, price, and mix (which I covered in Price-Volume-Mix Analysis), you may need to add a carbon cost driver. If your cost model is built on headcount and unit economics, you may need to add an energy cost component that reflects the company’s decarbonisation trajectory. The existing model architecture does not need to change fundamentally. It needs to accommodate new input variables that reflect the financial impact of sustainability commitments and regulatory requirements.

None of this is a reason for FP&A teams to panic. It is a reason to start learning now, building the data connections now, and developing the analytical capability before the disclosure deadlines make it urgent.

The Assurance Question

The BRSR Core mandate for reasonable assurance on specified metrics is, in my view, the single most consequential development in Indian ESG reporting. It transforms sustainability disclosure from a communications exercise into a controlled reporting process.

Reasonable assurance is the same standard applied to the financial statement audit. The assurance provider must obtain sufficient appropriate evidence to conclude that the metric is free from material misstatement. That standard drives everything backward through the data chain: source data reliability, calculation methodology documentation, internal controls over data capture and aggregation, and management review of the final disclosure.

For the finance function, this means applying the same control mindset to ESG data that you already apply to financial data. I think about it in four layers.

Data capture controls. Are the source systems capturing the right data, at the right level of granularity, with the right frequency? For energy data, does the building management system capture consumption at the meter level, or only at the site level? The assurance provider will ask.

Calculation controls. Are the emission factors, conversion methodologies, and aggregation rules documented and consistently applied? When you update an emission factor (because the grid emission factor for your state changed), is there a change log? The assurance provider will test this.

Review controls. Does a qualified person review the sustainability data before it enters the disclosure? Is there evidence of that review? This is identical to the management review control that sits on every financial statement line item.

Disclosure controls. Is the final disclosure reviewed against the underlying data, the calculation documentation, and the standard’s requirements before publication? This mirrors the financial statement close review process.

If this sounds familiar, it should. It is the same internal controls framework that finance teams have been operating for years, applied to a new category of data. The concepts are not new. The application is.

A Practical Starting Point

If you are a CFO or finance leader who has not yet started building ESG reporting capability, here is where I would begin.

Start with the BRSR metrics list. Map every metric to its data source, data owner, and current state of readiness. Be honest about where the gaps are. This mapping exercise alone will give you a realistic view of the implementation scope and help you prioritise.

Build a cross-functional working group with the sustainability team, facilities, HR, procurement, and IT. The finance function leads the governance and controls. The domain teams own the source data. Neither can do this alone.

Pick two or three metrics where the data already exists and build the full reporting chain: data capture, calculation, review, disclosure. Get those metrics to assurance-ready quality. That exercise will teach your team more about what “assurance-ready” means in practice than any training programme.

Invest in understanding IFRS S1 and S2, even if your jurisdiction has not yet adopted them. The direction is clear. The pace varies by country, but the convergence toward ISSB standards as the global baseline is unmistakable. Building to the ISSB framework now means you will not need to rebuild when adoption arrives.

And start integrating sustainability data into your regular reporting cadence. Do not wait for the full data infrastructure to be complete. Even imperfect monthly tracking of two or three key metrics builds the organisational muscle for the comprehensive reporting that is coming.

The Leadership Opportunity

ESG reporting is not a compliance burden that finance leaders should delegate to the lowest available resource. It is a leadership opportunity that will define which CFOs are seen as strategic and which are seen as reactive.

The CFO who builds this capability proactively, who connects sustainability data to financial decision-making, who ensures the organisation’s ESG disclosures can withstand assurance scrutiny, and who uses the process to drive genuine business insight, is building a finance function fit for the next decade. The CFO who waits until every regulation is finalised and every deadline is imminent will always be catching up.

I have chosen to be in the first group, and I am learning as I go. The regulatory landscape is evolving quickly. The data challenges are real. The cross-functional coordination is genuinely difficult. But the opportunity to build something meaningful, something that connects financial rigour with the sustainability questions that will define business strategy for the next generation, is exactly the kind of work that makes the finance function essential, not just accurate.

If you are building ESG reporting capability in your finance function, or if you are thinking about where to start, I would genuinely value the conversation. The best approaches I have seen come from practitioners working through the same challenges. Let’s connect.