Skip to content

iXBRL, ESEF and SEC XBRL viewer & Excel export

Inspect Inline XBRL 1.1, ESEF ZIP packages, and XBRL 2.1 filings locally: compute scaled numbers, inspect dimensions, and export to Excel.

Drop an Inline XBRL (.xhtml, .html), XBRL (.xml), or ESEF (.zip) file here

Extracts IFRS, UK GAAP, and US-GAAP facts, scaled values, signs, and dimensional contexts locally.

Loads a synthetic IFRS Inline XBRL annual report.

How to use iXBRL viewer

  1. Upload your filing. Drop an Inline XBRL (.xhtml, .html), XBRL 2.1 (.xml), or ESEF ZIP package up to 40 MB into the drop zone, or load the built-in sample report.
  2. Inspect summary counts. Review totals for numeric facts, text disclosures, contexts, and units alongside any contextRef or duplicate-fact alerts.
  3. Filter and search facts. Switch between All, Numeric, and Disclosures tabs and search across concept names, values, units, periods, or dimensions.
  4. Export tabular workbooks. Select Excel workbook (.xlsx) or Filtered facts CSV (.csv) to download your extracted iXBRL tables and facts locally.

Everything you type stays in this browser on your device. Nothing is uploaded, and your saved details are never sent anywhere.

How Inline XBRL 1.1, ESEF ZIP, and XBRL 2.1 filings parse

Financial teams often need to check tagged statutory figures before filing annual accounts or reviewing published reports. This local iXBRL viewer inspects .xhtml, .html, .htm, .xml, and packaged .zip submissions up to 40 MB entirely inside a client-side Web Worker following the Inline XBRL Part 1 Specification 1.1.

File format Detected standard Package priority Parser behavior Special handling
.xhtml Inline XBRL 1.1 Highest inside reports/ Extracts ix:nonFraction and ix:nonNumeric Keeps nested disclosure tags
.html / .htm Inline XBRL 1.1 Fallback after .xhtml Strips HTML styles and scripts Resolves   entities
.xml XBRL 2.1 XML Below Inline HTML files Reads elements with contextRef Deprioritizes _cal, _pre, _lab, _def
.zip ESEF / UKSEF bundle Ranked automatically Unpacks up to 80 MB total Skips __MACOSX/ and reportPackage.xml
Sample button Inline XBRL 1.1 Synthetic IFRS demo Loads harbor-esef-2025-sample.xhtml Includes scale="3" and dimensions

When scanning Inline XBRL documents, balanced tag tracking pairs nested ix:nonNumeric disclosures cleanly instead of truncating early at inner closing tags. Narrative fragments linked through continuedAt attributes are joined across matching ix:continuation IDs using cycle protection, while <ix:exclude> blocks are omitted and <ix:hidden> facts remain marked.

Inside compressed ESEF or UKSEF packages, the scoring engine selects files matching a reports/ folder ending in .xhtml ahead of root HTML files, while deprioritizing linkbases and catalog files.

Audit reviewers moving from statutory annual statements down to underlying statutory general ledgers in France often follow up report inspection with our FEC file checker. Both workflows keep sensitive pre-filing figures off external networks while exposing structural anomalies early.

How are scaled numeric facts, signs, and contexts resolved?

Display text inside annual reports frequently shows rounded thousands or bracketed losses that break generic spreadsheet imports. Our parser strips currency symbols ($, £, €, ¥) and non-breaking spaces, honors xsi:nil="true" nulls, treats zero-dash tokens as 0, and evaluates formatting rules before computing arithmetic totals.

Scaling factors, decimals, negative signs, and ixt formats

Comma-decimal transformations matching commadecimal or numspacecomma strip thousands dots or spaces before turning commas into decimal points, whereas dotdecimal and numspacedot preserve dots. When format is omitted, separator positions determine the decimal mark automatically, matching the structure defined by the XBRL 2.1 Instance Specification.

Bracketed figures like (640) become negative unless sign="+" is explicitly set, and sign="-" inverts positive text values such as finance costs. The resulting number is multiplied by ten raised to scale (for instance scale="3" for thousands) and rounded to six decimal places to prevent binary float tails.

Zero-dash tokens such as zerodash, numdash, fixed-zero, nil, and plain hyphens evaluate cleanly to 0, while HTML non-breaking spaces and XML character entities normalize before display or numeric export.

Resolving entity contexts, period dates, and dimensions

Every fact resolves its contextRef against <xbrli:context> blocks to capture entity schemes, identifiers, instant dates, startDate to endDate durations, or forever periods. Explicit and typed segment or scenario dimensions such as ifrs-full:SegmentsAxis are concatenated into readable axis=member pairs alongside <xbrli:unit> ratios like ISO 4217 EUR or EUR/shares.

Controllers reconciling German subsidiary trial balances extracted from consolidated European reports can also convert DATEV booking CSV files inside the same browser suite. Using a consistent local pipeline avoids copy-paste rounding drift across reporting periods.

Searching tagged facts and exporting to Excel or filtered CSV

Once parsing completes, sidebar summary counters display exact totals for numeric facts, text disclosures, contexts, and units across the active document. Filter buttons toggle between All, Numeric, and Disclosures, while real-time search matches concept QNames, labels, scaled numbers, raw text, periods, units, and dimensions.

Filtering numeric vs text disclosures and 300-row previews

Browser tables display the first 300 matching facts and shorten narrative disclosures to 180 characters onscreen so multi-thousand-tag filings stay responsive. Electronic reporting packages submitted under the ESMA European Single Electronic Format portal often exceed several thousand facts, so downloads always export the complete filtered dataset.

Four-sheet Excel workbooks and RFC 4180 CSV downloads

Selecting Excel workbook (.xlsx) generates true numeric cells rather than formatted strings, whereas Filtered facts CSV (.csv) writes RFC 4180 comma-delimited rows with a UTF-8 BOM across 14 structured columns. All text exports run through sanitizeCsvTable to neutralize leading formula characters (=, +, -, @, |).

  • Numeric Facts sheet: Stores concept QName, prefix, readable label, native numeric Scaled Value, original Raw Text, unit, scale exponent, decimals, period, entity, dimensions, and hidden status.
  • Text Disclosures sheet: Captures long ix:nonNumeric accounting policies and notes up to 10,000 characters per fact alongside context and entity metadata.
  • Contexts and Validation sheets: Lists every parsed context period with dimension strings plus all structural errors and warnings detected during the pass.

CSV downloads write 14 columns covering Concept, Prefix, Label, Kind, Scaled Value, Raw Text, Unit, Scale, Decimals, Period, Entity, Dimensions, Context ID, and Hidden flags.

Finance teams verifying UK statutory filings alongside supplier payment runs can pair these exported spreadsheets with UK Standard 18 BACS payment validation. Both workflows run locally and preserve clean audit trails from trial balance to cash disbursement.

Troubleshooting context errors, size caps, and audit scope

Validation alerts list up to 20 diagnostic findings in the UI and export the full issue list into the Excel Validation sheet. Fixing these structural inconsistencies before submission avoids automated gateway rejections at national business registries.

Handling missing contextRef, unitRef, and duplicate warnings

Four diagnostic codes catch common tagging mistakes: MISSING_CONTEXT when a fact omits or references an unknown context ID, MISSING_UNIT when a numeric tag lacks a unitRef, NUMERIC_FORMAT when text cannot be parsed as a number, and DUPLICATE_INCONSISTENT when identical concept|contextRef|unitRef keys disagree by more than 0.001.

Guidance from the GOV.UK company annual accounts filing overview explains statutory filing paths for UK limited companies preparing tagged accounts. Spotting duplicate fact conflicts and unmapped unit references early helps audit teams trace mismatched rounding in disclosure tables before submission.

ZIP bomb limits, local worker privacy, and review scope

To protect browser tabs from compressed archive exhaustion, uploaded files are limited to 40 MB and extracted ZIP entries stop at 80 MB uncompressed. Processing runs 100% locally in a dedicated Web Worker with zero server transfers, keeping confidential earnings figures private before you verify Australian ABA direct-entry totals before bank submission.

Tip: Click Load sample iXBRL report to open harbor-esef-2025-sample.xhtml first. It demonstrates ifrs-full tags, scale="3", negative sign="-" finance costs, and SegmentsAxis dimensions so you can inspect the Excel export layout locally.

Extracted tables and validation messages are provided for informational purposes only and do not constitute legal, tax, accounting, or financial advice. This browser utility parses instance facts locally without fetching remote XBRL taxonomy linkbases or XSD schemas, so statutory filings still require formal taxonomy validation and review by a qualified accountant, chartered accountant, or tax advisor.

Questions

How does the viewer compute scale factors and sign attributes on iXBRL numbers?

Each nonFraction tag is parsed using its ixt format rule or auto-detected decimal separator, flipped when negative parentheses or sign="-" appear, and multiplied by ten to the power of scale. Results round to six decimal places so Excel cells receive clean numbers.

Which file inside an ESEF ZIP package gets parsed as the primary report?

The extractor expands ZIP entries up to 80 MB while ignoring macOS resource folders. It ranks files inside a reports directory ending in .xhtml first, followed by root XHTML or HTML reports, and deprioritizes linkbase, catalog.xml, and reportPackage.xml metadata files.

Does the parser resolve continuedAt text chains and hidden iXBRL facts?

Yes. Multi-part narrative disclosures split across ix:continuation elements are joined in document order with cycle detection, while ix:exclude tags are stripped. Facts inside ix:hidden blocks are preserved and flagged in a dedicated Hidden column during export.

What sheets and columns are included in Excel and CSV exports?

Excel workbooks generate Numeric Facts, Text Disclosures, Contexts, and Validation worksheets matching your active search and tab filters. CSV exports write UTF-8 BOM rows across 14 columns from Concept through Hidden, with spreadsheet formula-injection protection on text fields.

Why does the viewer flag missing contextRef or duplicate inconsistent facts?

Every fact must reference a defined context ID, and numeric facts require a valid unitRef measure. When two facts share identical concept, context, and unit keys but differ by more than 0.001 scaled units, the diagnostics panel warns you before filing.

What file size limits apply to browser-side iXBRL and ZIP parsing?

Uploaded files are capped at 40 MB, and extracted ESEF or UKSEF ZIP contents are capped at 80 MB uncompressed to prevent browser memory exhaustion. Tables preview the first 300 filtered facts onscreen, while exports write all matching facts up to 10,000 text characters per cell.

Updated