Step out of corporate reporting and into supervisory reporting. A bank's Common Reporting (COREP) own-funds return runs to several thousand data points across dozens of templates. An insurer's Solvency II Quantitative Reporting Templates run longer still. Neither uses the International Financial Reporting Standards (IFRS) taxonomy; both use the Data Point Model (DPM).
The European Banking Authority (EBA) and the European Insurance and Occupational Pensions Authority (EIOPA) maintain the DPM. It is table-linkbase-driven: each return is a set of tables with row, column, and cell semantics, and the table linkbase plus the dimensional linkbase together describe how to read every cell as a fact in XBRL, the eXtensible Business Reporting Language. Filings are highly dimensional in a way an annual financial report (AFR) rarely is: a single COREP table can carry ten or more axes, and a typical Financial Reporting (FINREP) submission is denser with explicit and typed dimensional members than an entire AFR.
Filing indicators are the gate. Each submission carries facts that declare which templates the submission contains: in EBA filings in xBRL-CSV (the comma-separated-values serialisation of XBRL), one `fi:filed` fact per template, identified by a `fi:template` typed dimension; in xBRL-XML (the Extensible Markup Language serialisation — legacy for EBA, still current for EIOPA Solvency II), `find:filingIndicator` elements from the Eurofiling `find` namespace. The rules demand completeness: every template in the selected module must carry an explicit indicator, positive or negative, and leaving one out entirely violates EBA filing rule 1.6, which is a rejection. The insidious failure is the wrong negative indicator. The file validates cleanly, the template is treated as deliberately not reported, and the under-reporting surfaces with the supervisor on the next cycle, not at intake.
Typed dimensions carry a lot of weight in DPM. Counterparty identifiers (Legal Entity Identifier codes, LEIs), contract IDs, instrument IDs, and similar values are open-ended and cannot be enumerated as a closed list of explicit members. `xbrldi:typedMember` accepts an arbitrary value of a declared XML schema type, and supervisory returns lean on it heavily. For string-typed members like LEIs, equality is textual and case-sensitive. Mixed-case LEIs in the same return become two distinct counterparties unless you normalise the case before tagging.
The file format tells you which world you are in. For EBA returns the migration to xBRL-CSV is complete: submissions with reference dates from 31 March 2026 must be xBRL-CSV, and xBRL-XML is no longer accepted for those. EIOPA runs behind on purpose: Solvency II still files DPM 1.0 xBRL-XML, its taxonomy 2.10.0 (applying from the first quarter of 2027) keeps that classical architecture, and no CSV cutover date is announced. xBRL-CSV is one of the Open Information Model (OIM) serialisations, alongside xBRL-XML and xBRL-JSON; all three serialise the same OIM-level facts in different file formats. CSV cuts file size dramatically for high-volume returns, which is why supervisors care.
The European Banking Authority (EBA) and the European Insurance and Occupational Pensions Authority (EIOPA) publish supervisory taxonomies via the Data Point Model (DPM).
DPM is table-linkbase-driven: each return is a set of tables with row-column-cell semantics, and every cell reads as a fact in XBRL, the eXtensible Business Reporting Language. Filings are highly dimensional.
Filing indicators signal which templates are included in a submission: fi:filed facts with a fi:template typed dimension in xBRL-CSV filings (the comma-separated-values serialisation of XBRL); in xBRL-XML (the Extensible Markup Language serialisation — legacy for EBA, still current for EIOPA), find:filingIndicator elements (Eurofiling 'find' namespace). Every template in the module needs an explicit positive or negative indicator.
EBA returns completed the migration to xBRL-CSV: it is mandatory for reference dates from 31 March 2026, and xBRL-XML is no longer accepted for those. EIOPA Solvency II remains on DPM 1.0 xBRL-XML: taxonomy 2.10.0 (applying from the first quarter of 2027) keeps the classical architecture, and no CSV cutover date is announced. Both formats serialise the same facts under the Open Information Model (OIM).
Bank and insurer filings rely heavily on typed dimensions for counterparty identifiers and contract-level data.
3 questions. Druk op 1 tot 4 om te kiezen, Enter om te bevestigen.
Door deze quiz af te ronden, markeer je deze sectie als voltooid.
Tip: kies met 1 tot en met 4 en bevestig met Enter.