ESRS data point inventory workflow

Start with the ESRS version that legally applies to the reporting period, then use the matching EFRAG IG 3 as implementation support rather than starting from a blank spreadsheet. IG 3 explains that a datapoint is a separable piece of information required by an ESRS disclosure requirement and that one disclosure requirement can contain multiple datapoints. Treat each row as a controlled reporting object, not a loose topic label.

For each row, record the ESRS standard, disclosure requirement, paragraph or application requirement reference, data type, conditional wording, voluntary status, phase-in status if shown in the applicable source, and whether the row belongs to a minimum disclosure requirement for policies, actions, metrics, or targets. Also record the source version so a later ESRS amendment does not silently change the inventory.

Do not mark a data point as out of scope just because a reporting team lacks data. The Commission Q&A states that ESRS 2 is mandatory for companies under CSRD scope, while other standards and individual disclosure requirements and data points are subject to materiality assessment. EFRAG IG 1 also explains that ESRS 2 cross-cutting disclosures are reported irrespective of the materiality assessment outcome.

For data points subject to materiality, the row should point to the material impact, risk, or opportunity, the threshold or qualitative criterion used, and the evidence supporting the conclusion. If a data point derived from SFDR, the Benchmarks Regulation, or the Capital Requirements Regulation is assessed as not material, record the explicit not-material treatment and where the table entry will appear in the sustainability statement.

The inventory should show who can prove each disclosed fact. For quantitative data, name the source system, extraction logic, period, consolidation check, and reconciliation owner. For narrative data, name the policy, governance record, stakeholder input, management approval, or board material that supports the text.

EFRAG IG 1 notes that documentation can help governance bodies prepare ESRS 2 IRO-1 disclosures and help assurance providers perform their work. Translate that into controls: every high-risk row needs an evidence package, reviewer sign-off, change log, and clear treatment for estimates, restatements, and late evidence.

The datapoint inventory is not the ESRS XBRL taxonomy. EFRAG IG 3 explains that the human-readable list and digital taxonomy differ for technical reasons. Use the inventory to structure disclosures, then map final disclosures to taxonomy concepts as readiness work. ESMA states that undertakings are not required to mark up sustainability reporting until the relevant rules are adopted by delegated regulation.

For tagging readiness, add columns for taxonomy element, tag status, extension need, anchoring rationale, text-block scope, table handling, dimensions, units, period type, and duplicate-value checks. ESMA's ESEF consultation material describes marking up as using XBRL elements to label information in a human-readable annual report so that it is machine-readable.

Do not freeze the inventory once and reuse it unchanged. Reconcile it whenever the applicable ESRS text, EFRAG implementation material, reporting perimeter, materiality conclusion, value-chain estimate, policy, action, target, metric, or assurance finding changes. Record the trigger, affected rows, prior conclusion, revised conclusion, reviewer, approval date, and effect on the draft sustainability statement.

At reporting-period close, the inventory should account for every applicable disclosure requirement and every row carried forward from the preparer register. Each row needs a final state such as disclosed, not material with rationale, not applicable because a stated condition was not met, phased in under the applicable rule, voluntary and included, or unresolved and escalated. Data unavailability is a control issue, not a substitute for the materiality or applicability decision.