XBRL, iXBRL, ESEF, EDGAR: A Practical Guide to Structured Filing Formats

For most of financial and sustainability reporting history, a filing was a document, a PDF or a printed report that a human read from top to bottom. That model is disappearing. Regulators around the world now require, or are moving toward requiring, structured, machine-readable filings that can be parsed, compared, and analysed automatically, at scale, across every company that files.

For teams that have not built this capability before, the alphabet soup of formats, XBRL, iXBRL, ESEF, EDGAR, HMRC, FERC, can be genuinely confusing. This guide breaks down what each one actually requires and why the underlying discipline, structured data with a traceable audit trail, matters more than the format itself.

XBRL: the underlying language of structured filing

XBRL (eXtensible Business Reporting Language) is the foundational standard behind most structured regulatory filing today. Instead of a number simply appearing in a document, each figure is tagged against a taxonomy element, a defined, standardised label that says exactly what the number represents. A tagged revenue figure is unambiguous to any system reading the filing, in a way that the same number sitting in a PDF table is not.

The taxonomy is the critical piece. Getting figures tagged correctly against the right taxonomy elements, consistently across periods and consistently with how peers report the same line items, is the actual work of XBRL compliance. It is also where manual tagging processes tend to introduce the most errors.

iXBRL: human-readable and machine-readable at once

Inline XBRL (iXBRL) solves a practical problem with plain XBRL: a pure XBRL file is not something a person can easily read. iXBRL embeds the same structured tagging directly inside a human-readable HTML document, so the same file that a regulator's system parses automatically is also the document a person can open and read normally. This is now the standard requirement for UK HMRC corporate tax filings and is widely used elsewhere.

ESEF: Europe's structured format for annual financial reports

The European Single Electronic Format (ESEF) requires listed companies in the EU to prepare annual financial reports in a structured, XHTML-based format with iXBRL tagging for the primary financial statements. It follows the same core logic as iXBRL generally, structured tags embedded in a readable document, applied specifically to the requirements of EU-listed issuers and the ESEF taxonomy.

EDGAR: the US SEC's structured filing system

The SEC's EDGAR system has required XBRL-tagged financial data from public companies for over a decade, and its scope continues to expand alongside disclosure requirements. For companies filing with the SEC, whether financial statements or sustainability-adjacent disclosures, getting the taxonomy mapping right the first time avoids the back-and-forth correction cycles that slow down a filing.

FERC and sector-specific structured reporting

Beyond general corporate and financial reporting, sector-specific regulators increasingly require their own structured formats. The US Federal Energy Regulatory Commission (FERC), for instance, requires specific structured filings from regulated energy entities. The pattern repeats across jurisdictions and sectors: the specific taxonomy and submission mechanism differ, but the underlying requirement, structured, tagged, machine-readable data with a clear audit trail, is consistent.

Why validation before submission matters more than the tagging itself

Correctly tagging data against a taxonomy is necessary but not sufficient. Most rejected or flagged filings fail not because the tagging was technically wrong, but because the underlying data had gaps, inconsistencies, or figures that did not reconcile against each other or against the prior period. Running completeness and consistency checks before submission, not after a regulator's system flags them, is what actually determines whether a filing goes through cleanly.

• Completeness checks: every required taxonomy element has a value, with no silent gaps
• Consistency checks: figures reconcile across statements and against the prior reporting period
• Traceability: every tagged figure can be traced back to its source data and the approval that signed off on it
• Format validation: the file itself conforms to the taxonomy and submission mechanism the regulator expects

The format is the regulator's requirement. The audit trail behind the format is what actually protects you when a figure gets questioned.

Building this capability without starting from zero

Most organisations do not need to become taxonomy experts to file confidently. Soilo's RegTech Reporting platform supports structured filing preparation across XBRL, iXBRL, EDGAR, ESEF, HMRC, and FERC-style workflows, with completeness and consistency validation built into the process before submission, not discovered after. The same underlying data structure that supports ESG and Carbon MRV reporting carries through into filing-ready, taxonomy-tagged output, so figures do not need to be re-entered or re-mapped for each regulatory format.

For teams facing a structured filing requirement for the first time, whether it is an upcoming ESEF deadline, an EDGAR submission, or a new sector-specific mandate, the practical starting point is the same: get the underlying data structured and validated once, then let the appropriate taxonomy mapping and format handle the regulator-specific requirements from there.