Short answer
The answer, before the reasoning
IFRS S1 and IFRS S2 are not automatically mandatory for every entity worldwide. Their effective date tells an entity when the Standards can be applied as issued by the ISSB; it does not itself create a legal reporting obligation.
Mandatory status normally arises through a law, securities rule, stock-exchange rule, prudential requirement or formally issued local standard. A reporting team must therefore identify the competent authority, read the binding instrument, test the entity against its scope and phase-in rules, and distinguish direct use of ISSB Standards from locally modified or climate-only requirements.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. Why this question matters
A single sentence such as ‘the ISSB Standards are effective from 2024’ can be technically correct yet operationally misleading. It can cause an entity to begin a full compliance project when no local obligation applies, or to assume that no work is needed because a jurisdiction has not adopted the Standards word for word. The real legal question is not whether the ISSB has issued effective Standards. It is whether a competent authority has introduced requirements that apply to this particular entity, for this reporting period, with this scope, reliefs and reporting claim.
The distinction also matters for voluntary reporters. An entity may choose to apply IFRS S1 and IFRS S2 even when local law does not mandate them, but it must control how it describes that use. An explicit and unreserved ISSB compliance statement is available only when all applicable requirements of the IFRS Sustainability Disclosure Standards have been met. A report that uses selected concepts or metrics should describe that basis accurately rather than imply full compliance.
Quick orientation
- Applies to
- Any entity deciding whether IFRS S1 and IFRS S2 are mandatory, permitted, voluntary or relevant through a parent, lender, exchange or regulator.
- Primary decision
- What binding reporting obligation applies to the entity, from which period, and what reporting claim is supportable?
- Key sources
- The jurisdiction's binding legal or regulatory instrument; regulator guidance; official local standards; IFRS Foundation jurisdictional profiles as a verified orientation source.
- Common confusion
- Treating the ISSB effective date as a worldwide mandate, or treating a consultation, roadmap or market announcement as if it were a binding rule.
In practice
2. Three dates that must not be confused
| Date or status | What it means | What it does not prove — Evidence to retain |
|---|---|---|
| ISSB effective date | The date from which IFRS S1 or IFRS S2 applies when an entity applies the Standards as issued by the ISSB. Both were initially effective for annual periods beginning on or after 1 January 2024. | That every entity in every country is legally required to report. — Current Standard edition and effective-date paragraphs. |
| Jurisdictional commencement date | The first reporting period covered by a law, securities rule, listing rule or local standard. | That every entity in the jurisdiction is in scope; phase-ins and thresholds may apply. — Binding instrument, commencement provision and regulator implementation notice. |
| Entity's first applicable period | The first period in which the entity itself meets scope conditions after considering size, market, sector, public-interest status, group rules and reliefs. | That the same first year applies to all group entities or peers. — Applicability memo with entity facts, scope test and approval. |
3. Five possible jurisdictional outcomes
Figure 1. Jurisdictional applicability decision tree. The ISSB effective date is only the starting context; the binding local instrument determines mandatory status.
In practice
| Outcome | Typical form | What the reporting team should conclude — Claim caution |
|---|---|---|
| Direct adoption | A binding instrument requires IFRS S1 and IFRS S2 as issued, or incorporates them by reference. | Test all entity scope, timing, transition and local procedural requirements, then apply the incorporated edition. — Confirm whether later ISSB amendments apply automatically or require local endorsement. |
| Locally aligned standards | A jurisdiction issues local sustainability disclosure standards based on, aligned with or informed by ISSB Standards. | Apply the local text and identify additions, omissions, modifications and effective dates. — Do not call local compliance ISSB compliance unless the reporting basis supports that statement. |
| Climate-only requirement | A regulator initially mandates climate disclosures, potentially drawing on IFRS S2 or related architecture. | Apply the local climate rule and separately assess whether the entity voluntarily applies IFRS S1 and IFRS S2 in full. — A local climate-first programme is not automatically the IFRS S1 E5 transition relief. |
| Voluntary or permitted use | No mandate applies, but entities may report using ISSB Standards or a regulator encourages voluntary use. | Approve a voluntary reporting basis, scope, resources and claim before drafting. — Partial use must not be described as full compliance. |
| Consultation or roadmap only | A regulator has proposed requirements or announced a future adoption pathway. | Use the proposal for readiness planning, not as proof of a current obligation. — Label proposed dates and requirements as provisional until finalised. |
4. A practical jurisdictional-check method
The following sequence is an LRA implementation method. It is not a substitute for legal advice, but it creates a disciplined evidence trail and prevents the most common scope and claim errors.
Step 1 - Define the entity and the decision
Record the legal entity, consolidated reporting group, securities market, listing category, sector, public-interest status, financial year-end and the reporting period being tested. Clarify whether the question concerns a statutory obligation, stock-exchange compliance, group reporting, a financing covenant, procurement requirement or voluntary market communication. Different questions can produce different answers for the same organisation.
Step 2 - Identify the competent authority
Map the bodies that can impose requirements on the entity: legislature, securities regulator, stock exchange, central bank or prudential regulator, accounting or sustainability standard-setter, and any ministry responsible for corporate reporting. Do not assume that the body issuing a roadmap is the body that creates the binding obligation.
Step 3 - Find the binding instrument
Locate the final law, regulation, rulebook provision, listing rule, formally issued local standard or incorporation notice. Record the official title, instrument number, issue date, commencement date, legal status, official URL and version. A press release, consultation paper or third-party summary is not a substitute for the controlling text.
Step 4 - Determine the relationship to ISSB Standards
Classify whether the jurisdiction requires the ISSB Standards directly, incorporates a specified edition, issues local standards based on the ISSB Standards, mandates only climate-related disclosures, permits voluntary use, or merely draws on selected concepts. This classification determines which text the preparer must follow and which compliance statement may be available.
Step 5 - Test the entity against scope
Apply every relevant scope condition, including listing venue or market segment, market capitalisation, turnover, assets, employee count, public-interest status, sector, financial institution status, incorporation, domicile and group position. Retain the factual evidence used for each threshold. Where the rule applies at consolidated-group level, separately consider whether subsidiaries have local obligations of their own.
Step 6 - Confirm the first applicable period
Read commencement, phase-in, transition and grandfathering provisions. Establish whether the first period depends on entity size, market tier or sector. Distinguish the reporting period from the publication deadline and from any assurance commencement date.
Step 7 - Build a local modification register
Compare the binding local requirements with IFRS S1 and IFRS S2. At minimum, test subject matter, materiality, primary users, reporting entity, location, timing, comparatives, reliefs, GHG measurement, industry-based metrics, financial effects, digital tagging, language, assurance and the wording of the reporting statement. A jurisdiction can preserve broad alignment while modifying one or more of these features.
Step 8 - Check other binding reporting channels
An entity may have overlapping duties under annual-report law, a listing rule, prudential disclosure, emissions legislation or a parent-company instruction. Record each basis separately and design one reporting architecture that meets all applicable requirements without implying that they are identical.
Step 9 - Decide the reporting claim
Choose the statement that accurately reflects the work performed. A full ISSB compliance statement requires compliance with all applicable requirements of the IFRS Sustainability Disclosure Standards. Local compliance should cite the local instrument. Voluntary partial use may be described factually, for example by naming the specific Standards, requirements or metrics used, but should not be dressed up as full compliance.
Step 10 - Approve and version the conclusion
Prepare a short applicability memorandum, obtain legal or compliance review where needed, and secure approval from the accountable executive or governance body. The memo should have an owner, date, version and update triggers. Recheck the conclusion when the entity changes listing status, crosses a threshold, completes an acquisition, enters a new regulated sector, or when the jurisdiction finalises or amends its rules.
5. Evidence hierarchy: what should support the conclusion?
Figure 2. Evidence ladder for a jurisdictional adoption conclusion. The stronger the source, the more weight it can carry in an applicability memo.
In practice
| Source level | Appropriate use | Control question |
|---|---|---|
| 1. Binding instrument | Final conclusion on legal applicability, scope and commencement. | Is this the official current text with legal force for the entity? |
| 2. Regulator implementation material | Interpretation of scope, phase-in, forms, deadlines and enforcement expectations. | Does the guidance clarify rather than replace the binding text? |
| 3. IFRS Foundation jurisdictional profile or snapshot | High-quality orientation on the jurisdiction's adoption approach and alignment features. | Has the profile been updated, and does it link to the controlling local instruments? |
| 4. Consultation or roadmap | Readiness planning and scenario design. | Is the proposal final, and which provisions may still change? |
| 5. Professional or media summary | Discovery and issue spotting only. | Have all material statements been verified against official sources? |
In practice
6. The minimum applicability memorandum
| Field | What to record |
|---|---|
| Entity and reporting group | Legal entity, consolidated group, parent relationship, listings, sectors and year-end. |
| Question tested | Mandatory, permitted, voluntary, parent-required or financing-related application. |
| Competent authority | Regulator, exchange, legislature or local standard-setter with the relevant power. |
| Binding source | Instrument title, number, version, issue date, commencement date and official link. |
| Scope test | Every threshold and eligibility condition, entity facts, evidence and conclusion. |
| First period and deadline | Applicable annual period, publication date, phase-in and transition reliefs. |
| Reporting basis | Direct ISSB, local aligned standards, climate-only, voluntary full application or selected use. |
| Local modifications | Departures or additions affecting materiality, timing, metrics, reliefs, assurance or claim. |
| Reporting statement | Exact proposed wording and the basis supporting it. |
| Approvals and triggers | Reviewer, approver, assessment date, next review and event-driven triggers. |
7. Group and multi-jurisdiction complications
A parent company cannot assume that one group conclusion resolves every local question. The parent may be required to publish consolidated disclosures under one jurisdiction's rules while subsidiaries face local listing, prudential or corporate-reporting duties. Conversely, a subsidiary may be outside local mandatory scope but still need to supply data for the parent's report.
In practice
| Situation | Required analysis | Control |
|---|---|---|
| Parent mandated; subsidiary not locally mandated | Determine group data instructions, consolidation perimeter and whether subsidiary-level publication is unnecessary. | Separate data contribution from local public-reporting obligation. |
| Subsidiary locally mandated | Map local standard, filing location, language, timing, assurance and any differences from the parent basis. | Local legal review and reconciliation to group definitions. |
| Dual-listed entity | Test each exchange and securities regulator, including which rule has the earlier or broader scope. | One obligation matrix with no assumption that the stricter rule automatically satisfies the other. |
| Acquisition or disposal | Assess first-period scope, available reliefs, reporting entity, comparatives and data availability. | Document effective dates and treatment in the applicability memo. |
| Voluntary group ISSB report | Approve whether full ISSB compliance or a narrower selected-use basis is intended. | Pre-clear the reporting statement before data collection and drafting. |
8. Voluntary application: permitted does not mean informal
Voluntary use can create significant value by improving investor communication, preparing for future regulation or meeting financing expectations. It should nevertheless be governed as a formal reporting basis. The entity needs a defined reporting entity, materiality process, disclosure architecture, control framework, publication location and approval process. It also needs to decide whether it intends to meet all applicable ISSB requirements or only reuse selected concepts and information.
In practice
| Voluntary approach | Possible wording pattern | What must be avoided |
|---|---|---|
| Full application | An explicit and unreserved compliance statement, but only after all applicable requirements are met. | Making the statement before requirement-level completeness is demonstrated. |
| Selected use | A factual description of which IFRS S1 or IFRS S2 requirements, metrics or concepts informed the disclosures. | Using ‘compliant’, ‘in accordance’ or similar wording that implies full application. |
| Readiness disclosure | An explanation that the entity is preparing for future ISSB-aligned reporting and identifying current gaps. | Presenting a roadmap or pilot as a completed standards-based report. |
| Local aligned standard | A statement of compliance with the named local standard, plus a careful description of its relationship to ISSB Standards where supported. | Assuming local compliance automatically supports an ISSB compliance statement. |
9. Hypothetical example: a listed group with two reporting regimes
The teaching point is that the group may have three different statements at the same time: a mandatory local parent-company basis, a mandatory climate-only subsidiary basis and a possible voluntary ISSB basis. They share data, but they are not the same legal or reporting conclusion.
In practice
| Question | Assessment | Decision / evidence |
|---|---|---|
| Parent obligation | The parent meets the market and size criteria in Jurisdiction A for the next financial year. | Apply the final local standards; retain the rule, scope calculation and phase-in analysis. |
| Bank subsidiary obligation | The bank meets Jurisdiction B's prudential climate rule, which is not a full IFRS S1/S2 mandate. | Prepare the local prudential disclosure and map data to the parent report without describing it as full ISSB application. |
| Group reporting claim | The parent local standards contain several jurisdictional modifications. | State compliance with the local standards. Make a separate ISSB compliance statement only if a requirement-level assessment supports it. |
| Data architecture | Climate data can be reused, but the two regimes have different deadlines and disclosure formats. | Maintain one controlled data layer with separate local output mappings and sign-offs. |
| Update trigger | The regulator in Jurisdiction B is consulting on broader sustainability disclosures. | Track the consultation as a readiness trigger, not a current mandate. |
In practice
10. Weak versus stronger applicability wording
| Weak wording | Why it fails | Stronger wording - illustrative only |
|---|---|---|
| ‘IFRS S1 and IFRS S2 became mandatory globally in 2024.’ | It confuses the ISSB effective date with jurisdictional legal adoption. | ‘IFRS S1 and IFRS S2 are effective for annual periods beginning on or after 1 January 2024 when applied as issued. Our mandatory reporting basis is determined by [named local instrument], which applies to the Group from [period].’ |
| ‘We are ISSB aligned.’ | ‘Aligned’ is undefined and does not tell users whether all requirements were applied. | ‘The disclosures were prepared under [named local standard]. We also used [specified ISSB requirements or guidance] for [identified purpose]. The report does not make an unreserved ISSB compliance statement.’ |
| ‘The regulator has announced adoption, so the rule applies next year.’ | An announcement or consultation may not be final or legally operative. | ‘The regulator published [final/proposed] instrument on [date]. Our applicability conclusion is based on [final binding provision]; proposed elements are tracked separately in the readiness plan.’ |
In practice
11. Common mistakes
| MISTAKE 1 | Using the ISSB effective date as proof that the Standards are mandatory for the |
|---|---|
| Why it happens | Standard-setting and legal adoption are collapsed into one concept. |
| Why it matters | The project scope, budget, deadlines and public claims may be wrong. |
| Correction | Identify the competent authority and the binding local instrument, then perform an entity-specific scope test. |
| Evidence of correction | Approved applicability memo with official instrument and scope calculations. |
In practice
| MISTAKE 2 | Relying on a consultation, press release or professional summary instead of the |
|---|---|
| Why it happens | Discovery materials are easier to read than legal instruments. |
| Why it matters | Proposed scope, dates or reliefs may be treated as final even though they change before adoption. |
| Correction | Use secondary sources only to locate the official source; classify proposals separately from binding requirements. |
| Evidence of correction | Source register showing legal status, version and official link for each document. |
In practice
| MISTAKE 3 | Assuming a local ISSB-aligned standard is identical to IFRS S1 and IFRS S2. |
|---|---|
| Why it happens | ‘Aligned’ is interpreted as full textual equivalence. |
| Why it matters | Local modifications are missed and an unsupported ISSB compliance claim is made. |
| Correction | Build a modification register covering scope, materiality, timing, reliefs, metrics, assurance and reporting statements. |
| Evidence of correction | Reviewed crosswalk and claim decision signed by legal/compliance and reporting leads. |
In practice
| MISTAKE 4 | Testing only the parent company and ignoring subsidiary or listing-level obligat |
|---|---|
| Why it happens | The group reporting project is mistaken for the full legal perimeter. |
| Why it matters | A subsidiary filing, local language requirement or prudential deadline is missed. |
| Correction | Create an entity-by-entity and jurisdiction-by-jurisdiction obligations matrix. |
| Evidence of correction | Group obligations register linked to legal entities, exchanges and regulators. |
In practice
| MISTAKE 5 | Drafting the compliance statement at the end without deciding the reporting basi |
|---|---|
| Why it happens | The team treats claims as communications wording rather than a conclusion supported by complete requirements. |
| Why it matters | The report overstates the basis of preparation and requires late rework. |
| Correction | Pre-clear the intended claim and requirement map before data requests and drafting begin. |
| Evidence of correction | Approved basis-of-preparation note and requirement-level completion tracker. |
In practice
12. Myth versus reality
| MYTH | IFRS S1 and IFRS S2 were effective from 2024, so every large company must now re |
|---|---|
| REALITY | The Standards' effective date governs application of the ISSB Standards as issued. A legal obligation arises only through the relevant jurisdictional, regulatory, exchange or contractual basis, and the entity must still fall within its scope. |
| Why the confusion arises | ‘Effective’ is often used in accounting and regulation, while market summaries compress a complex adoption process into a single date. |
| Practical consequence | Reporting teams should maintain a versioned applicability memo and should never publish a mandatory-status conclusion based on the ISSB effective date alone. |
In practice
15. Related standards and mapping
| Source | Relationship | Use in this article |
|---|---|---|
| IFRS S1 Appendix E | Direct context | Effective date, early application and first-year transition reliefs when the Standards are applied. |
| IFRS S2 Appendix C | Direct context | Effective date, early application and climate-related transition provisions. |
| IFRS S1 paragraph 72 | Direct | Conditions for an explicit and unreserved compliance statement. |
| IFRS Foundation Jurisdictional Guide | Adoption context | Explains adoption or other use and the features used to describe jurisdictional approaches. |
| IFRS Foundation jurisdictional profiles and snapshots | Implementation evidence | Verified orientation on how individual jurisdictions are using or moving towards ISSB Standards. |
| Local law, rule or standard | Controlling legal source | Determines whether and how the requirements are mandatory for the entity. |
An applicability memo should record the entity, reporting period, applicable jurisdiction, binding instrument, scope, reliefs and intended reporting claim, with the evidence supporting the conclusion. It should also have an owner, date, version, approval and update triggers, and be revisited when the entity or jurisdictional rules change.
Questions
Questions people ask
Did IFRS S1 and IFRS S2 become mandatory worldwide in 2024?
IFRS S1 and IFRS S2 are not automatically mandatory for every entity worldwide. Their effective date tells an entity when the Standards can be applied as issued by the ISSB; it does not itself create a legal reporting obligation. Mandatory status normally arises through a law, securities rule, stock-exchange rule, prudential requirement or formally issued local standard.
Where should I check whether the Standards apply?
Locate the final law, regulation, rulebook provision, listing rule, formally issued local standard or incorporation notice. Record the official title, instrument number, issue date, commencement date, legal status, official URL and version. A press release, consultation paper or third-party summary is not a substitute for the controlling text.
Can a company apply IFRS S1 and IFRS S2 voluntarily?
The distinction also matters for voluntary reporters. An entity may choose to apply IFRS S1 and IFRS S2 even when local law does not mandate them, but it must control how it describes that use.
Does an ISSB-aligned local standard equal IFRS S1 and IFRS S2?
Compare the binding local requirements with IFRS S1 and IFRS S2. At minimum, test subject matter, materiality, primary users, reporting entity, location, timing, comparatives, reliefs, GHG measurement, industry-based metrics, financial effects, digital tagging, language, assurance and the wording of the reporting statement. A jurisdiction can preserve broad alignment while modifying one or more of these features.
Is a regulator consultation evidence of a current mandate?
Locate the final law, regulation, rulebook provision, listing rule, formally issued local standard or incorporation notice. Record the official title, instrument number, issue date, commencement date, legal status, official URL and version. A press release, consultation paper or third-party summary is not a substitute for the controlling text.
What should an applicability memo contain?
An applicability memo should record the entity, reporting period, applicable jurisdiction, binding instrument, scope, reliefs and intended reporting claim, with the evidence supporting the conclusion. It should also have an owner, date, version, approval and update triggers, and be revisited when the entity or jurisdictional rules change.
Sources
Primary sources
Take it with you
The checklists as a working spreadsheet
Every checklist and table on this page, with empty status, owner and evidence columns for your team to fill in and keep.
✓ LRA AI Assistant · Human-in-the-loop
Ask about this guide
It answers from this page, and reaches into the linked disclosure cards when your question is about the standard itself. Your first two answers are free without signing in.
Go deeper · IFRS S1 / S2
IFRS S1 and S2 training
Financial materiality, scenario analysis and the S2 climate disclosures, applied to your own reporting.
Available as Guided Flex, Live Cohort, 1:1 Expert Mentorship or Corporate Programme.
