What is XBRL?

  • Company data & APIs
  • Financial document processing
  • 3 min read

The short answer

XBRL is a standard for structured business reporting that associates reported facts with machine-readable concepts and context.

XBRL: why it matters

Automated company-data workflows need clear meanings and traceable transformations. An operation that runs successfully can still produce a result that is unsuitable for the intended business question.

How to assess it in practice

For xbrl, retain the specific source, scope and effective date, and distinguish verified facts from assumptions before using the result in a decision. Start by defining the question the team needs to answer. Identify the relevant record or evidence, check its scope and date, and retain the reasoning behind the result. If evidence conflicts, keep that conflict visible for review.

Worked example

Illustrative workflow: a team reviewing a business adds a separate check for xbrl. The reviewer’s task is to for xbrl, retain the specific source, scope and effective date, and distinguish verified facts from assumptions before using the result in a decision. The outcome is recorded together with the supporting evidence; an unresolved question stays open rather than being converted into a positive result.

Illustrative scenario

Two facts share a similar label but have different contexts. Inspect the taxonomy concept and dimensions before combining them in one financial series.

Distinctions that matter

XBRL belongs to the financial document processing topic family. Read Optical Character Recognition (OCR) alongside it to understand the adjacent question. Each page has its own intended scope; shared context does not make the concepts equivalent.

Evidence and review output

Review these

  • Original document and page context
  • Value, concept, period and unit
  • Validation and review outcomes

The review should produce

A traceable financial fact with its source context and extraction or mapping uncertainty retained.

Across this family

Extract a financial fact together with its entity, period, currency, unit and reporting scope. Character recognition, table assignment and concept mapping are separate quality problems. Use reconciliation and field-level review to catch plausible-looking values placed in the wrong context.

A note from practice

An XBRL fact combines a concept with context such as entity, period and unit. Machine-readable reporting reduces some extraction work but does not remove the need to interpret extensions and reporting scope.

Limits and common mistakes

The practical boundary is important: For xbrl, retain the specific source, scope and effective date, and distinguish verified facts from assumptions before using the result in a decision. Do not substitute a related label for this check or assume that missing information is a negative finding. Source-specific and jurisdiction-specific rules require their own review.

Frequently asked questions

Which evidence should I review?

For this topic, focus on original document and page context, value, concept, period and unit, validation and review outcomes. The relevant source and dates should be retained with the finding.

How is XBRL different from Financial Data Normalisation?

Financial data normalisation aligns reported values to a consistent analytical model while preserving source context. The distinction matters because the evidence needed for that concept may not resolve the question addressed on this page.

What should the result of the review contain?

A traceable financial fact with its source context and extraction or mapping uncertainty retained. Preserve material conflicts instead of replacing them with an unexplained success flag.

Continue learning

See the registry record behind every answer.

Primary, government-sourced data on 600M+ companies in 200+ countries, with full source attribution.