XBRL 2.1 · iXBRL 1.1 · LOCAL LITE

XBRL/iXBRL preflight with Arelle

Find broken inline references before your annual report reaches the publishing queue. Local structure checks and a separate import of your own offline Arelle evidence, for reporting, audit and software teams.

Runs on this device. No report upload. Demo: structure only; XSD and Arelle not executed.

EN · DE

Check a report locally

One check free. Existing Pro / Team batch limits: 25 / 100 files, 50 MB total. Each document gets its own result. ZIP packages use the separate optional input below.

Optional local Arelle report

Import JSON produced by our offline adapter with separately installed Arelle 2.47.4. It binds exact document bytes, profile, artifact hashes and selected validation options. Raw Arelle logs are not accepted without that envelope. A batch compares this report with each document, so a report for another file is rejected.

The adapter requests contexts, units, dimensions, all duplicate facts and round-to-nearest calculations. Formula execution is an explicit option for licensed applicable rules. Imported evidence is supplied by you; it is not a server attestation. Multi-document inline sets and third-party plugins are outside this first scope.

Offline adapter and exact CLI scope →
Optional authorised local XSD

No official XBRL/XHTML schema is bundled. Supply original files only when concrete rights cover processing and import mapping. Core XBRL schemas require their Software Notice; the document license alone does not suffice. For iXBRL, a generic XSD pass cannot establish embedded-fact semantics.

Include source URL, publisher, version, validity, acquisition date, concrete rights and notices for every file. SHA256 is computed from original bytes. No external fetch. XSD 1.1 and incomplete dependencies remain unexecuted.

Own teaching XSD · not official XBRL
Optional authorised package reference preflight

ZIP limit: 10 MB compressed and expanded, 100 files, 1 MB per file. Relative paths only. No extraction to disk, executable content, DTD/entities or network fetch. This checks local schemaRef/linkbaseRef and taxonomy entry points with explicit catalog rewriteURI mappings; it is not complete taxonomy-package conformance.

Without sufficient rights, leave the package out and use the independent structure check. No IFRS/ESEF taxonomy is downloaded automatically.

Your report stays in this browser tab.

A clear result at each layer

Independent preflight checks local references, unique XML IDs, inline targets and continuation chains. Context meaning, units, dimensions, duplicate facts, decimals/calculations and applicable formulas belong to Arelle. They remain not executed until matching local evidence is imported. No new XBRL engine is implemented here.

XML, supplied XSD, independent structure, plausibility, package references and imported Arelle evidence are separate. Unknown profiles never receive full green approval. Full ESEF, national GAAP profiles, legal rights and filing acceptance are not checked.

Fictional examples with known outcomes

Valid structure · rule-only · Missing context · Broken continuation · Own teaching XSD error · Expected codes and locations

Taxonomy rights stay separate

ESMA’s ESEF 2025 page reserves IFRS rights and prohibits commercial reuse. The EEA nonassertion is not a general SaaS license. No IFRS/ESEF taxonomy, protected rule library or national taxonomy is bundled or processed on an assumption of freedom. BYO, runtime and server-only placement do not remove restrictions.

Arelle 2.47.4 CLI · Arelle licenses · XBRL rights boundary · ESMA ESEF 2025 rights · Own-work notices

Context and unit repair guide · Continuation and package repair guide

Investigate a broken reference before importing evidence

When a fact points to a missing context, compare its contextRef with the actual context identifiers in the document. A similar visible label is not a replacement for an exact reference. For numeric facts, inspect the unit reference as a separate relationship. Repair the exporter or report template that produced the dangling reference.

Run the offline adapter again after editing the report. Evidence for yesterday’s XHTML must not be applied to today’s bytes. Keep the options and authorised taxonomy artifacts with that result. Import rejection can therefore mean the evidence does not match the selected document; it does not by itself establish a new accounting error.

Arelle pinned CLI documentation