Can One Dataset Support UK SRS S1, IFRS S1, ESRS and GRI?

ANSWER · EXPLAIN · APPLY · EVIDENCE · CONNECT · PUBLISH

London Reporting Academy · Working publication package · 2 August 2026

The four reporting systems overlap because they address many of the same real-world matters: climate, water, biodiversity, workforce, value chains, governance, policies, actions, targets and metrics. The overlap creates a strong case for shared source data. It does not remove the differences in users, materiality, reporting boundaries, calculation rules, presentation and statements of compliance.

A useful architecture separates three things that are often mixed in a spreadsheet: the fact, the judgement and the disclosure. The fact might be 1,250 cubic metres of metered water withdrawal at a site. The judgement determines whether and how that fact is relevant under each framework. The disclosure combines the fact with scope, methodology, context, financial or impact analysis, comparatives, targets and limitations.

A group should maintain stable identifiers for legal entities, subsidiaries, associates, joint ventures, facilities, countries, business lines, products, suppliers and other value-chain relationships. Each record should carry effective dates so acquisitions, disposals, closures and supplier changes can be reconstructed for the reporting period.

This master data can serve all four systems, but the reporting perimeter derived from it can differ. UK SRS S1 and IFRS S1 start with the same reporting entity as the related financial statements and then consider value-chain scope for each risk or opportunity. ESRS applies its legal reporting perimeter and value-chain requirements. GRI focuses on impacts across activities and business relationships and applies GRI reporting requirements. The shared register should therefore be richer than any single report boundary.

Use one issue universe with distinct fields rather than separate topic lists. A record can capture the activity or relationship, dependency, actual or potential impact, affected stakeholder or resource, risk driver, sustainability-related risk or opportunity, time horizon, locations, financial pathways, evidence and management response.

Framework-specific materiality conclusions then sit beside the common description: UK SRS investor materiality, IFRS investor materiality, ESRS impact materiality, ESRS financial materiality and GRI impact significance. This avoids losing significant impacts during an investor-risk screening and avoids assuming that every significant impact is material to primary users.

The shared layer can hold raw activity data, payroll records, incident data, meter readings, procurement data, emissions factors, survey results, complaints, policies, board minutes, calculation files and external datasets. Each data object should include the unit, period, currency where relevant, source system, extraction date, owner, method, estimation status, quality flag, evidence link, preparer, reviewer and retention rule.

A metric should not be represented only by a label and a number. The data dictionary needs a technical definition, numerator, denominator, population, organisational and value-chain boundary, treatment of acquisitions and disposals, frequency, restatement policy, assumptions and limitations. These fields make framework reconciliation possible.

The core object is the most granular reliable fact that the organisation can govern. Examples include an electricity invoice line, a payroll employee-month, a safety incident, a supplier assessment, a grievance case, a training completion, a water meter reading or a board approval. It should retain the original source reference and should not be overwritten when a framework changes.

A calculation object transforms source data into a metric. It records formula, factors, conversion tables, aggregation rules, estimates, exclusions, method owner and version. Multiple calculations can legitimately use the same source object. For example, a safety incident dataset can produce RIDDOR counts, total recordable incidents, severity rates and a supplier-worker indicator, each with a different definition.

The evidence object connects the fact and calculation to source files, approvals, reconciliations, review findings and remediation. It distinguishes public evidence from restricted records, which matters for grievances, personnel data, commercially sensitive information and legal privilege.

The output object records the framework, edition, disclosure requirement, materiality conclusion, report location, narrative context, published value, disaggregation, comparative, cross-reference, compliance statement and approval. It is this layer - not the source dataset - that changes when standards or reporting routes change.

Visual: controlled architecture for four frameworks

Source systems feed a common data and evidence model. A controlled adjustment log records the framework-specific decisions before publication under UK SRS, IFRS, ESRS or GRI.

The adjustment log is the key interoperability control. It explains why a common source object produces the same, adjusted or excluded output in each framework. The log should be auditable and should not rely on undocumented spreadsheet edits.

• Confirm the reporting entity is the same as the related financial statements.

• Identify risks and opportunities that could affect prospects and apply primary-user materiality.

• Apply UK sources-of-guidance provisions, including the optional nature of specific SASB reference.

• Select industry-associated and entity-specific metrics and disclose their sources and methods.

• Connect information across governance, strategy, risk management, metrics, targets and financial statements.

• Test UK reliefs, timing and compliance statement separately.

• Apply the IFRS investor-materiality lens and IFRS reporting-entity requirements.

• Document mandatory consideration of SASB topics and metrics.

• Check IFRS transition reliefs and date of initial application.

• Complete the IFRS S1/S2 disclosure index and explicit statement test.

• Confirm legal scope, reporting perimeter and the ESRS edition applicable to the reporting period.

• Apply double materiality: impact materiality and financial materiality, including required value-chain analysis.

• Map common data to ESRS disclosure requirements and datapoints without assuming equivalence from a crosswalk.

• Apply ESRS-specific definitions, phase-ins, presentation and sustainability-statement requirements.

• Retain the EU legal and assurance trail separately from voluntary UK or GRI reporting.

• Determine material topics from the organisation's most significant impacts across activities and business relationships.

• Use applicable Sector Standards and relevant Topic Standards.

• Provide impact and management context, not only a metric value.

• Maintain the GRI Content Index, omissions and statement of use independently.

Official interoperability guidance and indexes are valuable discovery and reconciliation tools. They can show where definitions, architecture or disclosures are closely aligned and can identify additional requirements. They should not be loaded into a system as a permanent equivalence table without version and review controls.

The ESRS-ISSB interoperability guidance explains a high degree of alignment while making clear that entities still need to apply the standards themselves. The GRI-ESRS interoperability index similarly supports navigation but notes differences in scope, granularity and definitions. The IFRS Foundation-GRI joint statement emphasises common disclosures serving distinct purposes. These documents support a mapping relation, not an automatic data substitution rule.

1. Store the source mapping document, publication date and direction of mapping.

2. Classify the relationship as direct, supporting, partial, presentation-only or no match.

3. Record residual differences in definition, scope, materiality, unit, disaggregation and narrative context.

4. Assign a reviewer and review date; do not let the mapping update independently of the underlying standards.

5. When one framework changes, automatically place affected mappings, calculations and articles into a review queue.

The shared dataset includes meter readings, purchased-water invoices, source type, facility, catchment, reporting period, estimation flag, evidence file and reviewer. The issue register links community impacts, ecosystem dependency, operational risk, permit risk and financial planning.

For UK SRS S1, the output focuses on material risks and opportunities affecting prospects, concentration in the value chain, strategy, financial effects and risk-specific metrics. For IFRS S1, the output may be substantially the same, but the source-of-guidance file also demonstrates mandatory SASB consideration. For ESRS, the organisation applies the applicable double-materiality and datapoint requirements for the relevant edition. For GRI, it reports significant impacts, management approach and relevant Topic Standard information.

The headline total may be identical across outputs only if the boundaries, sources and definitions match. The narrative and disaggregation are unlikely to be identical because each framework answers a different reporting question.

UK SRS S1 General Requirements for Disclosure of Sustainability-related Financial Information. February 2026, especially paragraphs 17-24, 46-64, 72-75 and B2-B11 Official source

IFRS S1 General Requirements for Disclosure of Sustainability-related Financial Information. June 2023 Official source

ESRS-ISSB Standards Interoperability Guidance. May 2024; use as guidance, not equivalence Official source

GRI-ESRS Interoperability Index. November 2024; mapping aid with residual differences Official source

IFRS Foundation and GRI joint statement. Common disclosures serving distinct purposes, May 2026 Official source

European Commission - revised ESRS adoption. 3 July 2026; scrutiny and application status Official source

GRI 1 and GRI 3. Impact reporting and material-topic requirements Official source