prev | next
Current Status: January 2026
Original Specification: XBRL 2.1 (December 2003)
Latest Updates: Multiple specifications updated through 2025
XBRL (eXtensible Business Reporting Language) is the international standard for digital reporting of financial, performance, risk and compliance information. It enables the definition, preparation and exchange of business reporting information across organizational boundaries in a manner that can be validated at every point in the process.
- Metadata and Data Separation: XBRL separates the structure and meaning (taxonomy) from the actual data (instance)
- Machine-Readable: Designed for automated processing and validation
- Multi-Dimensional: Supports complex, multi-dimensional business data
- Extensible: Taxonomies can be extended to meet specific reporting requirements ("a false promise")
- Validation: Multiple layers of validation ensure data quality
- Format Agnostic: Data can be represented in XML, JSON, CSV, or inline HTML
XBRL is one of the most complex definition languages ever developed. XBRL 2.1 is the current standard. While XBRL 2.2 was proposed and could have resolved some issues, it received no support, making XBRL 2.1 the de facto standard. XBRL uses the concept of Taxonomies to define the metadata of an XBRL instance document.
It's estimated that XBRL is two orders of magnitude (or more) more complex than XML. If you understand XML in detail, you can comprehence the level of complexity involved.
An XBRL instance document is a collection of facts that together make up a business report. Each fact represents an individual piece of information (e.g., "Profit at Acme Inc. in 2023 was $10M").
A fact is an individual data point consisting of:
- Value: The actual data (numeric or text)
- Concept: What the fact represents (defined in taxonomy)
- Context: Who, when, and other dimensions
- Unit: For numeric facts (e.g., USD, shares)
- Decimals/Precision: Accuracy specification for numeric facts
Taxonomies are the "dictionaries" that define:
- Concepts: The business terms and their data types
- Relationships: How concepts relate to each other
- Presentation: How information should be displayed
- Calculation: How values should add up
- Definitions: Additional semantic information
Contexts provide the dimensional information about facts:
- Entity: The reporting organization
- Period: Time period (instant or duration)
- Scenario/Segment: Additional dimensions (deprecated in OIM)
Additional dimensions beyond the basic context provide multi-dimensional reporting:
- Explicit Dimensions: Pre-defined members in the taxonomy
- Typed Dimensions: Values defined by data type
The XBRL standard consists of multiple interrelated specifications:
- XBRL 2.1 - Core specification (2003, continuously maintained)
- XBRL Dimensions 1.0 - Multi-dimensional data support (2006)
- Inline XBRL (iXBRL) - Embedding XBRL in HTML
- xBRL-XML - Traditional XML format
- xBRL-JSON - JSON representation (via OIM)
- xBRL-CSV - CSV representation (via OIM)
- Table Linkbase - Tabular data templates
- Generic Links - Flexible relationship definitions
- Generic Preferred Label - Label customization
- Formula - Complex validation and calculation rules
- Calculations - Simple arithmetic relationships
- Assertions - Business rule validation
- Extensible Enumerations - Standardized code lists
- Versioning - Tracking taxonomy changes
- Taxonomy Packages - Distribution format for taxonomies
- Report Packages - Distribution format for reports
- Registries - Shared resources (units, functions, transformations)
- Global Ledger - Transaction-level reporting
- Infrastructure - Supporting utilities
- Open Information Model (OIM) - Syntax-independent core model
- Digital Signatures - Security and authentication
- Streaming Extensions - Large data volume handling
XBRL is used worldwide for:
- Listed company financial statements (SEC, ESMA, etc.)
- Tax reporting
- Annual reports and disclosures
- Banking supervision (Basel, COREP, FINREP)
- Insurance (Solvency II)
- Securities regulation
- Statistical reporting
- Central bank data collection
- Government financial management
- Management reporting
- Supply chain reporting
- ESG (Environmental, Social, Governance) reporting
- Reduced manual data entry
- Automated validation
- Standardized reporting process
- Multi-format output from single source
¶ For Regulators and Data Consumers
- Automated data collection
- Immediate validation
- Easier data aggregation and analysis
- Improved data quality
- Machine-readable disclosures
¶ For Analysts and Investors
- Direct data access
- Automated comparison across entities
- Time-series analysis
- Integration with analytical tools
Must implement all syntactic restrictions in the specification.
Must implement both syntactic and semantic restrictions, including linkbase processing.
There is a limited amount of XBRL processors available worlwide. GLOMIDCO XBRL Processor is one of the most advanced processors on the market and optimed for Straight Through Processing (STP).
Many XBRL creation implementations are based on some form of DPM, typically involving filling a database or spreadsheet with capabilities to generate one specific XBRL instance document. While this approach is commonly used, it represents a poor solution from an XBRL perspective. Validation is often impossible or very limited, resulting in XBRL instances that fail validation checks.
XBRL builds on several W3C and other standards:
- XML Schema: For taxonomy structure
- XLink: For relationship definitions
- XPath: For navigation and calculations
- XML: Base syntax for xBRL-XML
- JSON: Base syntax for xBRL-JSON
- CSV: Base syntax for xBRL-CSV
- HTML/XHTML: Base for Inline XBRL
The standard is maintained by XBRL International (XII), a global not-for-profit consortium operating in the public interest. The organization:
- Develops and maintains specifications
- Provides conformance testing
- Supports implementation worldwide
- Facilitates international cooperation
As of January 2026:
- XBRL 2.1 remains the stable core specification
- Open Information Model provides modern, simplified framework
- Multiple format options (XML, JSON, CSV, Inline) for different use cases
- Widespread adoption by regulators worldwide
- Continuous evolution with new specifications in development
- Strong focus on usability and developer experience
For detailed information about specific specifications, see: