XBRL and Machine-Readable ESG Reporting: What Your Team Needs to Know

November 25, 2025  |  Technical Deep-Dive

← Back to Blog

XBRL machine-readable ESG reporting

The era of sustainability reporting as a narrative exercise is ending. Both the SEC Climate Disclosure rule and the EU's CSRD require machine-readable tagging of key sustainability data using XBRL (eXtensible Business Reporting Language) or inline XBRL (iXBRL). For compliance teams that have spent years producing PDF sustainability reports, this represents a fundamental change in the output format - and a new set of technical requirements that most ESG teams are not equipped to handle alone.

This article explains what machine-readable tagging means in practice, what the specific requirements are under each regulation, and what your team needs to do to prepare.

What Machine-Readable Tagging Actually Means

XBRL is a structured data language that attaches standardized labels to financial and, increasingly, sustainability data. When a company files an annual report with XBRL tagging, each tagged data point - a revenue figure, an emissions total, a headcount - is marked up with a machine-readable identifier from a standardized taxonomy. This allows regulators, investors, and data platforms to extract and compare specific data points across companies and filing periods without human reading and manual entry.

Inline XBRL (iXBRL) is a variant where XBRL tags are embedded in a human-readable HTML document, rather than in a separate machine-readable file. The document looks like a normal web page when viewed by a human but contains structured data tags that allow automated extraction. ESMA adopted iXBRL for European reporting in 2020 for financial data, and CSRD's XBRL taxonomy extends this to sustainability disclosures.

The practical implication: when you disclose your Scope 1 GHG emissions in your CSRD sustainability statement, that figure will not exist only as text in a PDF. It will be tagged as a specific XBRL element - say, "esrs:GrossScope1GHGEmissions" - with attributes specifying the unit (metric tons CO2e), the period (fiscal year 2025), and the organizational boundary. Regulators can then aggregate and compare that data point across all CSRD-reporting companies without manual data collection.

SEC Climate Disclosure: XBRL Tagging Requirements

Under the SEC's final climate disclosure rule, companies that file using EDGAR's electronic filing system (which covers all US public companies) must tag their climate-related disclosures using XBRL. The tagging requirement applies to:

  • The numerical climate disclosures in the annual report, including Scope 1 and Scope 2 emissions figures by gas type and in CO2e aggregate
  • Financial statement footnote disclosures related to severe weather events and climate-related costs
  • Quantitative transition risk disclosures where included

The SEC has developed a dedicated Climate Disclosure Taxonomy - a structured vocabulary of XBRL elements specifically for the climate disclosure rule requirements. Companies are required to use elements from this taxonomy for required disclosures, and may use custom extensions for company-specific disclosures that do not correspond to existing taxonomy elements.

The XBRL tagging requirement phases in over time. Large accelerated filers are subject to tagging requirements for their 2026 annual reports. Accelerated filers follow one year later. Smaller reporting companies have additional phase-in time.

For companies that already produce XBRL-tagged financial statements (which has been required for US filers since 2009), the addition of climate disclosure tagging is an extension of an existing process, not a new one. But the team responsible for ESG disclosure - typically sustainability or compliance - now needs to coordinate directly with the SEC reporting team responsible for XBRL tagging, which historically have not interacted.

CSRD: The European Sustainability Reporting Taxonomy

The EU's European Sustainability Reporting Standards (ESRS) are being implemented with mandatory iXBRL tagging via the European Sustainability Reporting Taxonomy (ESRT). EFRAG (the European Financial Reporting Advisory Group) has developed the taxonomy to provide machine-readable identifiers for each data point required across the 12 ESRS topical standards.

The CSRD iXBRL implementation differs from SEC XBRL in one important respect: CSRD uses the inline format, where the XBRL tags are embedded in the human-readable sustainability statement rather than filed as a separate machine-readable document. This means your sustainability statement must be authored in a way that supports simultaneous human readability and machine-readable tagging - a formatting requirement that most current ESG reporting workflows are not built to accommodate.

The ESRT includes tags for thousands of data points across the ESRS standards, ranging from GHG emissions figures to governance process descriptions to biodiversity metrics. The taxonomy includes both mandatory disclosure elements (which must be tagged) and voluntary elements (which may be tagged when companies include additional disclosures beyond minimum requirements).

Why This Creates a New Workflow Requirement

Producing an iXBRL-tagged CSRD sustainability statement is not a task that can be completed by adding a tagging step at the end of your normal report production process. It requires a structured workflow where:

  1. Data is assigned to specific ESRS disclosure requirements during the collection phase, not retrospectively after the report is drafted
  2. Numerical data is stored with its unit, period, and organizational boundary attributes - which are required XBRL attributes for every tagged element
  3. The disclosure text is authored with tagging in mind - placing tagged figures in locations within the text where they can be wrapped in iXBRL tags without disrupting readability
  4. A taxonomy mapping is maintained that connects each collected data point to its corresponding ESRS XBRL element identifier

ESG reporting teams that continue to produce PDF reports and convert them to machine-readable format at the end will face significant rework costs and risk of tagging errors. The efficient path is to produce iXBRL from the source data system, which requires a platform that understands both the ESG data requirements and the XBRL output format.

Taxonomy Customization and Extension

Not every disclosure will correspond to a pre-defined taxonomy element. Both the SEC Climate Taxonomy and the European ESRT allow custom extensions for company-specific disclosures. Using extensions requires discipline: over-extension - creating custom elements for disclosures that are already covered by the standard taxonomy - fragments the comparability value of the tagging and may be flagged in SEC staff review.

The standard for extension decisions is: if a standard taxonomy element exists that accurately represents the disclosed concept, use the standard element. Only create a custom extension when no standard element exists. This requires familiarity with the taxonomy structure, which most sustainability teams do not currently have - another reason why XBRL tagging for ESG disclosures requires collaboration with finance and legal teams that have more experience with EDGAR filing requirements.

Preparing Your Team for Machine-Readable Reporting

The practical preparation steps for compliance teams approaching their first XBRL-tagged ESG filing:

  • Engage your financial reporting team now. They own the existing XBRL filing infrastructure. ESG disclosures need to be integrated into their workflow, not bolted on separately.
  • Map your ESG metrics to taxonomy elements before the filing cycle. Produce a spreadsheet that lists every material ESG disclosure, its value, and its corresponding taxonomy element. This mapping is what you will hand to the XBRL preparer.
  • Understand the unit and period attributes. XBRL requires every numerical element to have a declared unit (metric tons, USD, percentage) and period (point in time or duration). Inconsistent units across filings - mixing metric tons and short tons, for example - is a validation error that will delay filing.
  • Plan for validation testing. EFRAG and the SEC both provide XBRL validation tools. Run your tagged document through validation before submission. Validation errors are common in first-cycle filings and take time to resolve.

Nossa Data's platform includes XBRL export capabilities aligned to both the SEC Climate Taxonomy and the ESRS taxonomy, enabling your team to produce machine-readable disclosures directly from the structured data layer. Request a demo to see the XBRL workflow in action.


← Back to all articles