What Is iXBRL? Definition, Format and Why It’s Required

iXBRL is a hybrid reporting format that combines a human-readable financial report with machine-readable data, using tags embedded inside an ordinary XHTML document. It exists so that regulators, investors and software can extract structured data from a report without losing the version people read. This article explains what iXBRL means, how it differs from plain XBRL, how the tagging process works in practice, and which regulations require it, from the EU’s ESEF and CSRD rules to the US SEC’s Inline XBRL mandate and the UK’s HMRC filing requirement. 

What does iXBRL stand for?

iXBRL stands for Inline eXtensible Business Reporting Language. It is a format that embeds structured, machine-readable financial data directly inside a human-readable document. In practical terms, an iXBRL file looks like a normal annual report when opened in a web browser, with tables, headings and narrative text laid out as expected, but it also carries hidden tags behind each figure that a computer can read and process automatically. 

This dual purpose is the entire point of the format. Before iXBRL, companies typically had to produce two separate versions of a report, one for human readers and one in structured XBRL for regulators and data systems. XBRL International, the organisation responsible for the standard, describes iXBRL as an open standard that allows a single document to serve both purposes at once. That single-document approach is why regulators across Europe settled on it as the basis for digital financial reporting. 

iXBRL vs XBRL

XBRL, or eXtensible Business Reporting Language, is a machine-readable data standard used to tag individual facts in a financial report, such as revenue, profit or total assets, so that software can read and process them automatically. On its own, an XBRL instance document is not designed to be read by a person. It exists purely as structured data, and CFOUR’s guide on what XBRL is and its role in EU reporting covers the standard itself in more detail. 

iXBRL solves the readability problem. It takes the same underlying XBRL tags and embeds them inside an XHTML document, the same markup language used to build web pages. The result is a report that a person can open and read normally in a browser, while the tags remain fully accessible to software for extraction and analysis. XBRL International’s guidance sets this out clearly, describing iXBRL as one of several interoperable XBRL report formats, distinct from plain xBRL-XML precisely because it merges structured data with human-readable presentation. 

This distinction also determines what a company is asked to file, rather than just how the format works in theory. CFOUR’s separate guide on the practical difference between filing structured data directly and filing it embedded in a readable report sets out how this plays out specifically across ESEF, UKSEF and SBR filings. For most companies operating under EU reporting mandates today, iXBRL rather than plain XBRL is the format required, because regulators want both machine processing and human readability from the same submission. 

How iXBRL tagging works

Producing an iXBRL report follows a broadly consistent sequence, regardless of which regulation applies. Understanding this sequence is useful before evaluating any software, because it clarifies what a tagging tool needs to do. 

Converting a report to XHTML

The starting point is usually a finished annual report, most often prepared in Word, InDesign or a similar publishing tool and exported to PDF. That report is converted into XHTML format, preserving the visual layout, tables and formatting that readers expect. This conversion step on its own does not involve any tagging. It simply produces a browser-readable version of the document that can subsequently carry embedded tags.

Tagging data points against a taxonomy 

Once the report exists in XHTML, individual data points, such as line items in the financial statements or specific disclosures in the notes, are tagged using concepts drawn from a taxonomy. A taxonomy is a structured dictionary of financial or sustainability concepts relevant to the applicable regulation, for example the ESEF taxonomy based on IFRS. Where no existing taxonomy concept matches a company’s specific line item, an extension can be created, though extension concepts are expected to be anchored to the base taxonomy wherever possible. This is the stage most people mean when they refer to iXBRL tagging. 

Validating and submitting the package 

After tagging, the report is validated against the rules of the relevant taxonomy and regulation. Validation checks that tags have been applied correctly and that the resulting XBRL data is internally consistent. Many workflows also include a review stage, where an auditor or a second preparer checks the tagging before submission. Once validated, the report is packaged into the format required by the regulator, typically alongside the taxonomy files, and submitted through the relevant filing channel. 

Which regulations require iXBRL? 

iXBRL is not a single-regulation requirement, and its use now extends well beyond Europe. It has become the common technical format underpinning several distinct national and regional reporting mandates, each with its own scope and rules. 

ESEF for EU listed companies 

The European Single Electronic Format, introduced by ESMA under the amended Transparency Directive, requires companies with securities listed on EU-regulated markets to prepare their annual financial reports in XHTML. Where those reports include IFRS consolidated financial statements, the disclosures must additionally be tagged using the ESEF taxonomy in iXBRL, so that the structured data sits inside the same human-readable document. ESMA’s own guidance describes this explicitly as embedding XBRL tags in the XHTML document using inline XBRL technology, which allows the benefits of structured, tagged data to be combined with a report format people can still read directly. For a fuller walkthrough of scope and requirements, CFOUR’s guide on who needs to comply with ESEF and what the regulatory framework requires covers this in more depth. 

CSRD and the expansion to sustainability reporting 

Inline XBRL is also expanding within the EU beyond financial statements. Under the Corporate Sustainability Reporting Directive, sustainability statements will eventually need to be tagged using the ESRS taxonomy EFRAG has developed, in the same iXBRL format used for ESEF. As of the current date, however, no fixed deadline has been set for mandatory tagging of CSRD sustainability statements. Digital tagging becomes mandatory only once the European Commission adopts XBRL technical standards through a Delegated Act amending the ESEF Regulation, a step that depends on ESMA completing its regulatory technical standards consultation, and mandatory tagging is not expected for financial year 2026.  

SBR for Dutch companies 

Standard Business Reporting, the Dutch framework for filing with the Chamber of Commerce, has extended its use of iXBRL considerably in recent years. Under Staatsblad 2024, 428, electronic filing via SBR now applies to financial years beginning on or after 1 January 2025, closing the last gap in a phased rollout that already covered micro, small and medium-sized entities. For large entities, this means the first mandatory electronic filings land in 2026, covering the 2025 financial year. Companies filing under IFRS, alongside those with more complex or entity-specific reporting layouts, generally use the iXBRL format rather than plain XBRL for this filing. 

One detail worth noting for anyone assessing scope precisely is that tagging of the notes to the financial statements, the management report and other narrative information, sometimes referred to as block tagging, remains temporarily exempted. It is expected to become mandatory only once ESMA has introduced a revised block-tagging approach for ESEF, and as ESMA has not yet done so, no fixed date currently applies to this part of the requirement. Companies and firms delivering SBR tagging services to clients can find a comparison of the tools available for this specific mandate in CFOUR’s review of the leading iXBRL tools built for Dutch SBR reporting. 

Beyond the EU, the United States and United Kingdom 

Inline XBRL is not exclusively a European requirement. In the United States, the Securities and Exchange Commission mandates Inline XBRL for public companies filing Forms 10-K and 10-Q, a requirement phased in between 2019 and 2021 depending on filer size, as confirmed by the SEC’s own compliance guidance. In the United Kingdom, HMRC has required companies to file Corporation Tax computations and accounts in iXBRL format since April 2011, and Companies House is separately moving toward mandatory software-based filing that also relies on iXBRL as it phases out its paper and web filing routes. For companies operating across multiple jurisdictions, this means iXBRL is often not a single compliance project but a recurring format requirement across different regulators.

Conclusion

iXBRL combines machine-readable financial data with a document people can still read normally, which is why regulators across Europe, the United States and the United Kingdom have converged on it as the basis for digital reporting. Within the EU, its use continues to expand from ESEF into CSRD’s sustainability disclosures, even where exact tagging deadlines, such as Dutch block tagging and CSRD’s own timeline, are still being finalised. For any company newly encountering the term, the practical task is usually narrower than the regulation itself, converting a report to XHTML, tagging it against the correct taxonomy and validating it before submission. 

See how CFOUR Comply supports ESEF and SBR iXBRL reporting on a single platform. 

Preparing your tagging process now means your team is ready well before your next ESEF or SBR filing deadline. 

Request Demo