ISSB Reporting Explained: What S1 and S2 Mean for Your Finance Function
ISSB reporting has moved from the conceptual to the operational. With the International Sustainability Standards Board's first two standards, IFRS S1 and IFRS S2, now embedded in the regulatory pipelines of jurisdictions from Australia to Japan, and with S&P Global tracking a widening map of adoption commitments through 2026, the question for most large organisations is no longer whether the standards apply but how quickly the finance function must be ready. This article sets out the ISSB standards explained in practical terms, and argues that the defining challenge of the next reporting cycle is not disclosure itself but the distance between what companies can disclose and what they can credibly assure.
IFRS S1 establishes the general requirements for disclosing sustainability-related financial information. It asks an entity to identify and report the sustainability risks and opportunities that could reasonably be expected to affect its cash flows, access to finance, or cost of capital over the short, medium, and long term. IFRS S2 sits alongside it as the climate-specific standard, incorporating the four pillars familiar from the TCFD framework: governance, strategy, risk management, and metrics and targets. The essential shift the two standards introduce is one of connectivity. Sustainability information is no longer a separate narrative appended to the annual report. It is expected to sit within the same reporting boundary, on the same timeline, and to the same standard of rigour as the financial statements themselves.
That connectivity is precisely why ISSB reporting lands squarely on the finance function rather than on a sustainability team operating in isolation. Under S1 and S2, sustainability disclosures must be prepared for the same reporting period as the related financial statements and, in most adopting jurisdictions, released at the same time. Finance teams that have spent years building controls, materiality judgements, and audit trails around financial data are now being asked to extend that discipline to emissions inventories, climate scenario analysis, and forward-looking transition plans. The data maturity gap here is considerable. Where revenue recognition rests on decades of established practice, a Scope 3 emissions figure may depend on supplier estimates, industry averages, and modelling assumptions that would not yet survive an auditor's scrutiny.
Scope 3 is where much of the practical difficulty concentrates. S2 requires disclosure of Scope 1, Scope 2, and material Scope 3 greenhouse gas emissions, and it is the value chain emissions in Scope 3 that expose the weakest data foundations. This is not a theoretical concern. Industrial groups such as Elsewedy have described the intertwined challenge of gathering Scope 3 data while simultaneously preparing for carbon border mechanisms, and the same underlying data is increasingly demanded by more than one regime at once. The UK's recognition of sixteen overseas carbon pricing schemes for CBAM relief illustrates the point: the emissions and carbon cost information a company assembles for border adjustment purposes overlaps materially with what S2 expects. Organisations that treat these as separate exercises will duplicate effort and multiply the risk of inconsistency between disclosures that regulators and assurers can now compare side by side.
The gap between disclosure and assurance is the issue senior teams most consistently underestimate. Producing a number is one task. Producing a number that an external assurance provider will sign off against a recognised standard is another entirely. Many jurisdictions are phasing in assurance requirements, beginning with limited assurance and moving toward reasonable assurance over subsequent years. Limited assurance is a lower bar, but even it requires documented methodologies, traceable source data, and evidence of internal review that many first-year reporters simply do not yet have. The uncomfortable reality is that a disclosure which satisfies the letter of S1 or S2 in year one may not withstand the assurance expectations of year three. Finance functions should be building for the assurance standard they will face at the end of the transition, not the disclosure standard they face at its start.
There is a governance dimension that deserves particular attention. S1 and S2 both require disclosure of how sustainability-related risks are governed, including the role of the board and management. This mirrors a broader pattern that CorpStage observes across governance regimes, including in the AI domain, where recent commentary has noted that organisations frequently struggle to follow their own governance frameworks once they are written. A stated policy is not the same as a functioning control. The ISSB standards will expose the same weakness if governance disclosures describe oversight structures that do not operate in practice. Boards should expect that assurers and, in time, regulators will test whether the governance described in the report is the governance that actually exists.
Practical readiness therefore rests on a few priorities. First, establish a single reporting boundary and a shared data architecture so that financial and sustainability information reconcile rather than diverge. Second, map where sustainability data serves multiple regimes, from ISSB to CBAM to national disclosure rules, and manage it once at source. Third, apply financial-grade controls to the metrics most likely to attract assurance scrutiny, starting with the greenhouse gas inventory. Fourth, treat the transition period as a build phase for assurance readiness rather than a grace period for approximation. Organisations that sequence their work this way convert a compliance obligation into a source of decision-useful information for capital allocation and risk management.
CorpStage works with finance and sustainability leaders to close the distance between disclosure and assurance under the ISSB standards. That work spans materiality assessment, data lineage and controls design, Scope 3 methodology, and governance alignment across overlapping regimes such as ISSB and CBAM. As adoption broadens through 2026, the advantage will belong to organisations that treat S1 and S2 not as a reporting exercise to be survived but as a discipline to be embedded. The firms that prepare for the assurance standard now, rather than the disclosure standard alone, will be the ones whose numbers hold when scrutiny arrives.