ESRS data point inventory workflow

Start with EFRAG IG 3 and the adopted ESRS, not a blank spreadsheet. IG 3 explains that a data point is a separable piece of information required by ESRS disclosure requirements, and that one disclosure requirement can contain multiple data points. Treat each inventory row as a controlled reporting object, not as 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 source material, and whether the row is a minimum disclosure requirement for policies, actions, metrics, or targets.

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 data point inventory is not the same as the ESRS XBRL taxonomy. EFRAG IG 3 explains that the human-readable data point list and the digital taxonomy differ for technical reasons, even though they are based on consistency. Use the inventory to structure disclosures early, then map each final disclosure to the taxonomy element or tagging treatment once the reporting format work starts.

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.