DAC7 platform reporting validator
Check annual platform seller exports with explicit national reporting and schema scope.
EU countries; national scope varies · Germany, France, Poland, Romania, Croatia, PortugalOpen validatorFind 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.
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.
Valid structure · rule-only · Missing context · Broken continuation · Own teaching XSD error · Expected codes and locations
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
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.