It is 4:47 p.m. on the day of an annual filing. The submission portal returns a wall of red text that begins, helpfully, with the words "validation failed". Somewhere inside that wall sits a fourteen-character code, a file path, and a line number. The whole rest of the evening will be decided by how quickly you can read those three things.
Validators look intimidating because they speak a private dialect. They are not actually being cryptic; they are being precise. ESMA, the SEC, HMRC, the UK FRC, the Dutch SBR programme, and the EBA all converge on the same open-source engine in practice. Arelle is the reference processor, and most commercial tools either embed it directly or benchmark against it. When a regulator says "the file did not validate", the operational translation is "Arelle, with this regulator's plugin, emitted a code".
Plugins switch the rule book. `validate/ESEF` loads the ESMA rule pack. `validate/EFM` loads the SEC EDGAR Filer Manual rule pack. `validate/UK` covers HMRC and the UK FRC. `validate/EBA` handles COREP and FINREP. `validate/NL` carries the SBR rules. `inlineXbrlDocumentSet` is the iXBRL plumbing that lets a multi-file document set load as one logical instance. The `--disclosureSystem` flag then pins the version: `esef-2024` is not `esef-2025`, and treating them as interchangeable is how you discover that some rules tightened between editions.
There is one ordering rule that pays for itself every time. Run base XBRL 2.1 validation first, before any regulator overlay. A missing `schemaRef`, a malformed XML document, or an unresolved `contextRef` will produce dozens of cascading downstream messages from the regulator plugin, and almost all of them will vanish the moment the base error is fixed. Triage the cheapest, most generic failures first; the regulator-specific output is then short enough to read without coffee.
Pre-flight pure-XML checks complete the picture. They are cheap, dependency-light, and catch a few classes of issue, like `decimals="INF"` abuse, broken `ix:continuation` chains, and non-ISO currency unit measures, that some validators report only obliquely. The keypoints below extend this triage discipline.
Arelle is the open-source XBRL platform that ESMA, the SEC, HMRC, the UK FRC, and most commercial XBRL tools either embed or benchmark against. When a regulator says 'the file did not validate', operationally that means Arelle (or a derivative) emitted a code.
Plugins select rule packs: validate/ESEF for ESEF, validate/EFM for SEC, validate/UK for HMRC and UK FRC, validate/EBA for COREP/FINREP, validate/NL for SBR. inlineXbrlDocumentSet is the iXBRL plumbing.
The disclosureSystem flag picks the regulator profile: --disclosureSystem esef-2024 selects the ESEF 2024 ruleset, esef-2025 selects 2025, etc.
Always run base XBRL 2.1 validation first. A core failure makes the regulator-specific output noisy and hard to read.
Pre-flight pure-XML checks (decimals='INF' abuse, broken continuation chains, non-ISO currency measures) are cheap to run and catch issues that some validators do not surface clearly.
arelleCmdLine \
--plugins "validate/ESEF|inlineXbrlDocumentSet" \
--disclosureSystem esef-2025 \
--validate \
--file report-package.zip \
--logFormat "[%(messageCode)s] %(message)s - %(file)s %(sourceLine)s"3 questions. Press 1 to 4 to select, Enter to confirm.
Completing this quiz marks the section done in your progress.
Tip: press 1 to 4 to select, Enter to confirm.