XBRL

XBRL is a structured reporting language that tags business disclosures so computers and people can identify, validate, and compare reported facts.

XBRL, or eXtensible Business Reporting Language, is a structured reporting language that attaches machine-readable tags and context to business disclosures. A tagged fact can identify what was reported, by which entity, for which period, in which unit, and under which reporting taxonomy.

XBRL helps regulators, analysts, and software extract and compare filing data. It does not make the underlying accounting correct, remove the need to read footnotes, or guarantee that two similarly named facts are economically comparable.

Key Takeaways

  • XBRL structures reported facts; it is not an accounting standard or valuation method.
  • A useful fact includes a concept, value, entity, period, unit, and any relevant dimensions.
  • A taxonomy defines available reporting concepts and relationships.
  • Company-specific extensions can represent facts not covered by a standard taxonomy but can reduce comparability if used poorly.
  • Analysts should reconcile tagged data to the human-readable filing and review definitions, context, signs, scales, and footnotes.

What an XBRL Fact Contains

ElementQuestion it answersExample
ConceptWhat is being reported?Revenue
ValueWhat amount or text was disclosed?125,000,000
EntityWhich reporting entity does it belong to?Hypothetical issuer
PeriodAt what date or over what interval?Year ended December 31
UnitWhat measurement is used?U.S. dollars
DimensionsDoes the fact apply to a segment, class, or other axis?North America segment
Decimals or accuracyAt what stated precision is the value reported?Rounded to millions

Without context, the number 125 is ambiguous. It could mean $125, $125 million, 125 shares, a quarterly value, or an annual value. XBRL carries metadata that helps software interpret the fact.

Taxonomies and Extensions

An XBRL taxonomy is a structured dictionary of reporting concepts, definitions, labels, data types, and relationships. A filing maps disclosures to concepts in the applicable taxonomy.

A filer may create an extension when a standard concept does not adequately represent a company-specific disclosure. Extensions can preserve meaning, but an unnecessary custom tag can make comparison harder. Analysts should determine whether an extension is genuinely distinct and how it relates to standard concepts.

Relationships in the filing also matter. Presentation links help organize facts, calculation links express certain arithmetic relationships, and definition links can describe dimensional structures. Passing a technical validation does not prove that the accounting presentation or economic interpretation is correct.

Inline XBRL

Inline XBRL embeds machine-readable tags in an HTML document that people can read in a browser. The SEC’s Inline XBRL viewer lets users inspect tagged facts and associated metadata within an EDGAR filing.

This differs from treating the filing as a picture or plain PDF. The visible text and the structured data are connected in one document, but analysts should still review the complete filing, including narrative disclosures and footnotes that may not be captured by a simple numeric download.

Worked Example: Comparing Revenue

Assume Company A reports revenue of $125 million for the year, while Company B reports $36 million for a quarter. A data download may place both facts in a field labeled revenue, but direct comparison would be misleading unless the user checks:

  • annual versus quarterly periods;
  • consolidated versus segment scope;
  • continuing operations versus another presentation;
  • currency and scale;
  • taxonomy concept and company extension;
  • amended versus original filing status; and
  • relevant accounting policies and footnotes.

If Company A uses a standard revenue concept and Company B uses a custom extension, an analyst should read the extension definition before mapping the values together. Similar labels do not necessarily establish identical accounting meaning.

XBRL vs. Other Formats

FormatMain strengthMain limitation for analysis
Inline XBRLHuman-readable filing with embedded structured factsTags and extensions still require interpretation and quality review
HTMLAccessible narrative and tables in a browserData may require manual extraction if not tagged
PDFPreserves document appearanceOften difficult to extract reliably and may separate values from context
CSV or spreadsheetConvenient tabular analysisMay omit filing relationships, narrative context, and source presentation
JSON APIConvenient system-to-system accessMeaning depends on the source schema and included metadata

XBRL data can be transformed into CSV, JSON, or analytical databases. The output format does not eliminate the need to retain filing identifiers and context.

How to Evaluate XBRL Data

  • Open the source filing and confirm the tagged fact appears in the expected statement or note.
  • Check the filing date, form type, accession number, and amendment status.
  • Review the concept definition, period, entity, unit, decimals, sign, and dimensions.
  • Determine whether the tag is standard or company-specific.
  • Compare values with the visible statement and relevant footnote.
  • Investigate duplicate facts with different contexts rather than selecting one automatically.
  • Separate reported values from ratios or estimates calculated by a data provider.
  • Preserve a link to the original filing when using extracted data.

The SEC’s downloadable financial-statement data is presented as filed. The SEC advises investors to review the full Commission filings before making an investment decision.

Risks and Common Mistakes

  • Treating a tag name as a complete accounting definition.
  • Comparing instant balance-sheet facts with duration income-statement facts.
  • Ignoring units, scales, signs, dimensions, or fiscal-period differences.
  • Assuming all custom extensions are errors or, conversely, treating all extensions as comparable.
  • Using an outdated taxonomy mapping without reviewing changes.
  • Relying on a flattened data set without reading footnotes and narrative disclosures.
  • Assuming technical validation is the same as an audit opinion or regulator approval.
  • Combining original and amended filings without identifying which version is intended.

Official Resources

Filing and tagging requirements vary by form, filer, regulator, and jurisdiction. The applicable taxonomy and filing manual control a specific submission.

FAQs

Is XBRL the same as a financial statement?

No. XBRL structures facts within or alongside a report. The financial statements, accounting policies, footnotes, management discussion, and other filing content provide the broader disclosure context.

What is Inline XBRL?

Inline XBRL embeds machine-readable tags in a human-readable HTML filing, allowing users to read the document and inspect the structured facts in context.

Does XBRL guarantee comparable company data?

No. Taxonomies improve structure, but differences in accounting policies, periods, units, dimensions, estimates, and company-specific extensions can still limit comparability.

Educational Use

This article provides general financial education. It is not accounting, filing, investment, legal, or compliance advice.

Browse Financial Technology