Climate disclosure rules compared: CSRD, IFRS S2, CSDS, SEC

Climate disclosure rules are not converging on a single template, and 2026 is the year that became obvious. Europe is simplifying and narrowing its regime, the ISSB baseline is being adopted country by country, Canada has published standards but not yet mandated them, and the US federal rule is being unwound while a state law moves ahead. If you report across borders, you are managing several regimes at different speeds. This guide maps where each one stands and what it asks of your underlying data.

One thing is constant across all of them: they all ultimately require emissions numbers built from real consumption. The regulatory text differs; the need for clean, auditable utility data does not.

IFRS S1 and S2: the global baseline

The International Sustainability Standards Board (ISSB) published IFRS S1 (general sustainability requirements) and IFRS S2 (climate) in June 2023, with S2 effective for reporting periods beginning on or after 1 January 2024. IFRS S2 fully incorporates the TCFD recommendations and requires disclosure of Scope 1, Scope 2 and, subject to relief provisions, Scope 3 emissions.

IFRS S2 is not law by itself. It becomes binding only when a jurisdiction adopts it. The IFRS Foundation now publishes jurisdictional profiles tracking that adoption, and by 2026 more than twenty jurisdictions had adopted or committed to the ISSB standards on a voluntary or mandatory basis. Think of S2 as the common grammar that national rules are increasingly written in.

CSRD and the ESRS: broad, then narrowed

The EU Corporate Sustainability Reporting Directive (CSRD) is the most detailed regime, delivered through the European Sustainability Reporting Standards (ESRS) and built on a double-materiality principle: companies report both how climate affects them and how they affect the climate. It requires assured, granular disclosure including full Scope 1, 2 and 3 emissions.

In 2025 and 2026 the EU pulled that scope back sharply. A stop-the-clock directive published in April 2025 postponed reporting by two years for large companies not already reporting. The follow-on Omnibus simplification, whose final text the co-legislators agreed in December 2025 and the Council signed off in February 2026, raised the reporting threshold to companies with more than 1,000 employees and over 450 million euros in turnover, removing a large share of previously in-scope firms.

Canada's CSDS: published, voluntary for now

The Canadian Sustainability Standards Board (CSSB) released CSDS 1 and CSDS 2 in December 2024, closely modelled on IFRS S1 and S2 with Canadian modifications, effective for annual periods beginning on or after 1 January 2025. Crucially, they are voluntary unless made mandatory by a securities regulator or legislation. The Canadian Securities Administrators had earlier paused work on a climate-disclosure rule, so Canadian issuers currently face a national standard they can adopt but are not yet compelled to follow.

SEC and California: the US split

The US federal picture reversed. The SEC adopted a climate-disclosure rule in March 2024, then stopped defending it in court in 2025, and in May 2026 formally proposed to rescind it in its entirety. For now, there is no operative federal climate-disclosure mandate for registrants.

California moved the opposite direction. SB 253 requires companies with over 1 billion dollars in revenue doing business in the state to report Scope 1, 2 and 3 emissions under the GHG Protocol, with the first Scope 1 and 2 reports due August 10, 2026. SB 261 requires biennial climate-risk reporting aligned with TCFD for companies above 500 million dollars in revenue, though litigation has affected its timing. For many US-active companies, California, not Washington, is now the binding federal-scale requirement.

The frameworks side by side

What this means for your data pipeline

Given the divergence, the safe strategy is to build to the strictest common denominator and stop tracking each rule separately at the data layer. That means capturing Scope 1, 2 and 3 activity data with enough granularity and audit trail to satisfy assured EU reporting, then mapping the same source to whichever regimes actually bind you.

• Capture consumption by site and period, not just annual totals
• Keep an audit trail from each reported number back to the source bill or meter file
• Support both Scope 2 methods, since frameworks and target-setters expect market-based and location-based
• Structure the data once so you can re-map it as rules change, which they will

This is exactly the gap MartinAI closes. It reads bills, meter data and Green Button files, validates them, and produces structured consumption with the lineage assurance and disclosure require. When the frameworks shift again, and they will, your data does not have to be rebuilt.