Skip to the answer

Disclosure GuidesPillar guides, articles, FAQ and expert notes

Level 2 · Decision guide·UAE FDL 11 / 2024 · Disclosure guides

UAE Climate Law and IFRS S2: Can One GHG and Climate Risk System Support Both?

How to share entity, facility, emissions, evidence, scenario and financial-effect data while preserving different legal triggers, boundaries, verification and reporting claims

Who this is for A 11-minute read for reporting teams working through One climate dataset, several reporting outputs, and for reviewers testing whether the evidence behind it holds.

Published passport

Current as at 10 August 2026
RK Reviewed by Dr Ross KurinkoLinkedIn Strategic ESG Advisor · IFRS S1 & S2 / GRI / ESRS expert GRI Certified Global Trainer · PhD, University of Cambridge · ESG-AI expert 15+ years on FTSE 100 & Fortune Global 500 disclosures Canary Wharf, London LRA educational guidance · Not issued or endorsed by MOCCAE

Edition written against

Federal Decree-Law No. (11) of 2024 and IFRS S2 are different instruments. UAE climate-law duties depend …

Published

10 Aug 2026

Knowledge Hub guide

Last reviewed

10 Aug 2026

Short answer

The answer, before the reasoning

Yes, one controlled system can support both, but only if it stores source facts separately from output rules. Reuse legal-entity, facility, energy, fuel, refrigerant, factor, evidence, risk, scenario, action and governance records.

Then apply two release views: the UAE view follows the determined Source, competent-authority method, form, verification and record requirements; the IFRS S2 view follows the financial reporting entity, material climate risks and opportunities, Scope 1-3 disclosures, scenario analysis, resilience and financial effects. A shared dataset reduces duplication; it does not make the two regimes equivalent. The strongest architecture is “one source of controlled facts, multiple approved outputs”, not one blended report or one unqualified compliance statement.

Educational practitioner guidance. Not legal advice. Verify current official requirements and entity-specific regulator correspondence before acting.

Quick orientation

Quick orientation

Applies to
UAE entities and groups that face or prepare for climate-law MRV and also apply, plan to apply or report to a parent under IFRS S1 and IFRS S2.
Primary decision
Which data and controls are genuinely reusable, which boundaries require a bridge, and which output-specific requirements need separate calculations or narrative.
Key sources
Federal Decree-Law No. (11) of 2024; applicable UAE implementing instructions; IFRS S1 and IFRS S2; GHG Protocol; official ISSB educational material.
Common confusion
Using the same GHG total as evidence that the entity complies with both instruments, or assuming authority verification covers IFRS S2 climate-risk and financial-effect disclosures.

Shared system does not mean shared compliance conclusion

The two regimes answer different questions. UAE climate law establishes a national legal framework for measurement, reporting, verification, reduction and adaptation. Article 6 duties are linked to Sources determined by MOCCAE and the competent authority. IFRS S2 asks for material information about climate-related risks and opportunities that could reasonably be expected to affect an entity’s prospects, for primary users of general purpose financial reports.

These purposes overlap around emissions, targets, actions, risks and governance. They diverge around trigger, reporting entity, materiality, Scope 3, scenario analysis, financial effects, filing route and claims. The system must preserve both the common evidence and the residual differences.

Figure 1. One controlled evidence base can feed two different outputs. The UAE and IFRS S2 views remain separately governed.

In practice

Side-by-side architecture

Dimension UAE climate-law output IFRS S2 output — System control
Trigger Source status, Article 6 determination, local instruction or separate registry trigger. Application of IFRS Sustainability Disclosure Standards under jurisdictional, group or voluntary basis. — Store the applicable instrument and trigger for each output.
Primary user Government, competent authority, verifier or enforcement body. Existing and potential investors, lenders and other creditors. — Tag data-user and release purpose.
Reporting perimeter Named legal entity, facility, Source or locally prescribed perimeter. Same reporting entity as the related financial statements. — Maintain legal-entity, facility and financial-reporting hierarchy with bridge rules.
Materiality Legal requirements and authority-defined scope; do not replace with IFRS materiality. Material information about climate risks and opportunities affecting prospects. — Separate legal applicability from financial materiality decisions.
GHG scope Article 6 and implementing method; Resolution 67 separately uses Scope 1 plus Scope 2 threshold/reporting. Scope 1, Scope 2 and Scope 3 information under IFRS S2 requirements. — Store all source records and output-specific inclusion status.
Scenarios / resilience May arise through adaptation, authority, sector or reduction requirements; not fully specified as an Article 6 scenario-analysis disclosure in the Decree-Law. Required climate resilience assessment using scenario analysis, with a proportionate approach. — Shared risk and scenario library; separate disclosure tests.
Financial effects Not a general Article 6 disclosure category stated in the Decree-Law. Current and anticipated effects on financial position, performance and cash flows, subject to IFRS S2 requirements and reliefs. — Link risks/actions to finance records without forcing them into the legal inventory.
Verification / assurance Authority or programme verification requirements; Resolution 67 requires authorised/accredited verification. IFRS S2 itself is a disclosure standard; assurance depends on jurisdiction or engagement. — Record criteria, subject matter, scope, provider and conclusion separately.

Rule

CLAIM CONTROL

<p>A shared system does not support a shared compliance statement. Approve the UAE legal claim and the IFRS Sustainability Disclosure Standards compliance statement separately, using output-specific checklists, representations and sign-off.</p>

The master data model

Figure 2. A master climate data model stores controlled identities, measurements, evidence, risk/strategy fields and review status before producing output-specific views.

In practice

Data domain Minimum master fields Why it is reusable
Identity Legal entity ID, financial reporting entity, facility, asset, operator, lease, jurisdiction, authority status. Supports entity, facility and consolidated views without losing legal facts.
Emission source Source ID, equipment/activity, gas, Scope candidate, owner/control, unit and data owner. Allows different scope or perimeter filters while preserving the source record.
Measurement Activity data, factor, GWP, equation, period, estimate flag, uncertainty and method version. Supports recalculation, authority forms and IFRS method disclosures.
Evidence Evidence ID, document/system, source location, owner, period, review, confidentiality and retention. Creates a shared audit trail while controlling restricted records.
Risk / opportunity Driver, physical/transition type, exposure, time horizon, likelihood, magnitude and affected business model. Feeds IFRS S2 and internal risk work; may also support UAE adaptation or reduction engagement.
Scenario Scenario source, assumptions, warming/policy pathway, horizon, variables, assets and limitations. Supports proportionate resilience work and repeatable updates.
Action / target Action, target, baseline, scope, owner, resources, expected effect, dependency and status. Supports legal reduction information and IFRS S2 strategy/metrics disclosures.
Financial effect Line item, mechanism, time horizon, current/anticipated status, method and uncertainty. Bridges climate analysis to finance without altering the emissions inventory.
Control and release Preparer, reviewer, approval, finding, correction, output, version, release status and claim. Prevents one draft number from being used uncritically in every channel.

Reporting entity and boundary bridge

IFRS S1 requires sustainability-related financial disclosures for the same reporting entity as the related financial statements. A UAE MRV instruction may identify a facility, local legal person or Source. The master system should therefore not have a single “company” field. It should have a hierarchy and effective dates, so acquisitions, disposals, new branches, management contracts and facility transfers can be reflected consistently.

In practice

Bridge question Record required Review output
Is every UAE Source inside the IFRS reporting entity? Entity relationship and consolidation status. Included, excluded or separately disclosed with rationale.
Does the authority require facility data below group level? Facility-to-entity mapping and aggregation rule. Reproducible facility report and group reconciliation.
Are joint ventures or associates treated differently? Ownership, control, financial accounting treatment and inventory approach. Boundary adjustment and IFRS S2 explanation where material.
Has the group changed during the period? Acquisition/disposal date, baseline and recalculation decision. Comparative and boundary change record.
Are leased or managed assets controlled? Contract rights, actual operations and accepted consolidation method. Scope assignment and residual value-chain treatment.

One GHG inventory - but not always one published total

A common calculation engine can store activity data and calculate emissions once. The release totals can still differ legitimately. The UAE authority may require a designated facility and specified factor; IFRS S2 may require the whole financial reporting entity and Scope 3. A group should reconcile the views rather than forcing them to match.

In practice

Possible difference Example Required control
Perimeter UAE filing covers one plant; IFRS S2 covers the consolidated group. Facility-to-group reconciliation and explanation.
Scope coverage UAE instruction covers Scope 1/2; IFRS S2 includes Scope 3. Scope status and output filter for every source/category.
Method / factor Authority specifies a local factor; group model uses another factor set. Retain both method versions and quantify the bridge.
Reporting period Authority calendar differs from financial year. Period mapping, cut-off controls and no silent mixing.
Estimate maturity Legal filing uses verified primary data; IFRS Scope 3 uses estimates. Data-quality flag and separate assurance/verification scope.

Scope 3 and the UAE legal perimeter

IFRS S2 requires an entity to consider its entire value chain and all 15 Scope 3 categories, and disclose categories included in its Scope 3 measure. It also provides a measurement framework that recognises estimates and prioritises higher-quality data. The UAE Decree-Law does not itself list those 15 categories. Therefore the master system can store Scope 3 data, but the UAE legal output should include it only where the applicable authority or instrument requires it.

Rule

METHOD BRIDGE

<p>Where a jurisdictional authority requires a different GHG measurement method, IFRS S2 contains relief and disclosure requirements around the alternative method. The exact effect depends on the applicable IFRS S2 edition, the part of the entity covered and any early application of the 2025 amendments. Recheck the current text before relying on the relief.</p>

Scenarios, resilience and financial effects

An emissions inventory cannot by itself support IFRS S2. The system also needs climate-risk and opportunity records, scenario assumptions, time horizons, resilience conclusions, strategy responses and financial linkages. A proportionate first-year scenario analysis may be qualitative or partly quantitative where that is commensurate with the entity’s circumstances, but it must still be traceable to reasonable and supportable information.

In practice

Record Minimum evidence Control question
Risk and opportunity Driver, affected asset/business, time horizon, magnitude, owner and evidence. Is the item connected to prospects, not merely an environmental topic?
Scenario choice Source, pathway, assumptions, geography, variables and rationale. Does the selection cover relevant physical and transition uncertainty?
Resilience conclusion Exposure, adaptive capacity, action, dependency, threshold and limitation. Can management explain what could fail and when?
Financial effect Mechanism, line item, current/anticipated effect, method and uncertainty. Is the link to financial position, performance or cash flows supportable?
Governance Committee/board oversight, decisions, challenge and approval. Does evidence show actual oversight rather than policy wording only?

In practice

Verification and assurance are not interchangeable

Activity Typical subject matter What it does not automatically cover
UAE MRV verification Defined emissions statement, facility or authority report under specified criteria. IFRS S2 materiality, risk identification, scenarios, financial effects or the compliance statement.
Internal control review Data lineage, reconciliations, approvals, estimates and release controls. An independent external opinion.
IFRS sustainability assurance Specified sustainability disclosures under jurisdictional/engagement criteria. A legal determination that the UAE Article 6 obligation has been met unless in scope.
Financial statement audit Financial statements and audit procedures. Full assurance over climate disclosures unless explicitly included.

Implementation workflow

1. Lock the UAE legal instruments, Article 6 status, authority, facility requirements and any Resolution 67 track.

2. Lock the IFRS S2 application basis, reporting entity, reporting period, materiality process and compliance-claim plan.

3. Create common identity, source, method, evidence, risk, scenario, action and financial-effect records.

4. Add output rules rather than duplicating source records: inclusion, transformation, disclosure, verification and approval.

5. Reconcile the UAE and IFRS GHG totals by entity, facility, Scope, period, factor and estimate status.

6. Run separate completeness reviews: legal requirement checklist for UAE; IFRS S2 material disclosure checklist for investor reporting.

7. Obtain separate sign-offs and representations for each output and retain a crosswalk/change log.

Hypothetical example: a diversified UAE group

The group stores fuel, electricity, refrigerants and factors in one source model. It produces a verified facility view for the authority and a consolidated group view for IFRS S2. The difference is reconciled by perimeter, Scope, factor and period. A separate risk module links transition policy and physical heat exposure to assets, actions and financial effects. The group does not state that the facility verification assures the entire IFRS S2 disclosure.

Hypothetical scenario

ILLUSTRATIVE SCENARIO

<p>A fictional UAE group has an industrial subsidiary designated under a local MRV programme and a consolidated IFRS S2 reporting entity containing industrial, logistics and service subsidiaries. The plant report covers facility Scope 1 and 2; the IFRS S2 disclosure covers the group and material Scope 3 categories, climate scenarios and financial effects.</p>

Illustrative only. It shows how the decision is made, not wording that can be copied or relied on.

In practice

Weak versus stronger architecture

Weak architecture Why it fails Stronger architecture
One “official” GHG total for every purpose. Different perimeters, Scopes and methods are hidden. One source dataset with reconciled output views.
IFRS materiality determines legal filing scope. Financial materiality cannot replace legal applicability. Run legal and IFRS decisions separately, then connect evidence.
Verified emissions equals assured IFRS S2. Risk, scenario and financial disclosures may be outside the verification scope. Record criteria and subject matter for each engagement.
Scenario results stored only in slides. Assumptions and data cannot be reproduced or updated. Maintain scenario records, versions, variables and governance evidence.
Crosswalk maintained as labels only. No transformation or residual gap is controlled. Record field-level relationship, adjustment, owner and review.

Common mistakes

Using the financial reporting group as the Article 6 Source without authority evidence.

Excluding facility detail because IFRS S2 is consolidated.

Assuming the UAE method automatically satisfies IFRS S2 GHG measurement disclosures.

Leaving Scope 3 outside the master model until the reporting deadline.

Running scenario analysis independently from asset, risk and finance data.

Calling a verifier’s factual findings an assurance opinion over the whole sustainability disclosure.

Publishing an unqualified “complies with both” claim without separate checklists and sign-offs.

Myth

“If we calculate GHG emissions once under a recognised method, the UAE climate law and IFRS S2 are both covered.”

Reality

The calculation can be reused, but the legal trigger, reporting entity, materiality, Scope 3, scenarios, financial effects, verification, filing and compliance statement still require separate decisions. Reuse the data; do not merge the requirements.

Readiness

Dual-output checklist

  • UAE legal and IFRS S2 application bases are separately documented.
  • Legal entity, facility and financial reporting hierarchies are linked.
  • Every emission source has output-specific inclusion and method status.
  • Scope 3 category screening is complete for IFRS S2 and separately assessed for UAE requirements.
  • Scenario, resilience and financial-effect records are controlled.
  • UAE verification and IFRS assurance scopes are not conflated.
  • GHG totals reconcile by perimeter, Scope, period, factor and estimate.
  • Each output has its own checklist, representation, approval and release version.
  • Framework amendments and authority instructions trigger crosswalk review.

Self-check

  1. Can the team explain every difference between the UAE and IFRS S2 GHG totals?
  2. Does the system know which entity is the legal Source and which is the financial reporting entity?
  3. Can a reviewer trace scenario assumptions to resilience and financial-effect conclusions?
  4. Do the verification and assurance statements name their exact criteria and subject matter?

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.

Download .xlsx

✓ 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.

Try
2 free answers Automated · the LRA team is one click away

Go deeper · UAE FDL 11 / 2024

UAE Climate Law training

Obligations under Federal Decree-Law 11 of 2024, from inventory to the reduction plan.

Available as Guided Flex, Live Cohort, 1:1 Expert Mentorship or Corporate Programme.

See course formats
/en/knowledge-hub/disclosure-guides/uae/uae-one-dataset-many-outputs/uae-climate-law-and-ifrs-s2-can-one-ghg-and-climate-risk-system-suppor/