What a hypercube is
XBRL Dimensions 1.0 builds a hypercube from four kinds of link in a definition linkbase. A primary item, the concept being reported, points at a hypercube with an all arc. The hypercube points at its dimensions. Each dimension points at its domain, and the domain at the members allowed.
Put together, they say: a fact for this concept must carry these dimensions, with one of these members on each. A fact that carries something else is dimensionally invalid, and the processor reports xbrldie:PrimaryItemDimensionallyInvalidError.
Closed, and on the scenario
Two attributes on the all arc decide how strict the cube is. xbrldt:closed="true" means a fact may carry only the cube’s dimensions and nothing more; an open cube, the default, lets extra dimensions through. xbrldt:contextElement says where the dimension values sit in the context, segment or scenario.
Line4 read every all arc in the EBA 4.2 and 4.3 packages: 47,696 in total, every one closed="true" and contextElement="scenario". That matches the EBA Filing Rules, which forbid the segment (rule 2.14) and allow only explicit and typed members in the scenario (rule 2.15).
Closed cubes are why a supervisory template works. With an open cube, a firm could add a dimension the supervisor never asked for and still pass, and the same cell could mean two things.
An example: one IRRBB cell group
The EBA’s IRRBB template J 10.02 has one of the smallest definition linkbases in the 4.2 package. Its single hypercube covers five concepts about the assumptions behind a bank’s interest rate risk measures.
- Primary items
- 5, from “Change of material assumptions (EVE)” to “Post-shock interest rate floor (NII/EVE)”
- Hypercube
- 1, closed, on the scenario
- Dimensions
- 3: Type of risk, Prudential portfolio, Significant currency for the IRRBB thresholds
- Members allowed
- Type of risk: Interest rate risk only. Portfolio: Banking book only. Currency: any currency in a hierarchy that leaves out x0
Every fact for these five concepts must say interest rate risk, banking book and one currency, and nothing else. A fact with no currency, or with an extra dimension, fails. The currency hierarchy leaves out x0, so a total across currencies is not allowed here.
In the definition linkbase (shortened)ShowHide
ei1002 --all closed scenario--> hyp
hyp --hypercube-dimension--> qLHL
qLHL --dimension-domain (usable=false)--> qTR
qTR --domain-member--> qx2007 (Interest rate risk)
hyp --hypercube-dimension--> qEEF ... qx2001 (Banking book)
hyp --hypercube-dimension--> SCI
SCI --dimension-domain, targetRole--> CU3_4_WITHOUT_X0Line4’s reading of j_10.02-def.xml in the EBA 4.2 frameworks package, with labels from the EBA 4.3 dictionary. Arrows are Line4’s shorthand for the arcs.
How the EBA builds its hypercubes
The EBA reuses one hypercube element, hyp from the Eurofiling model schema, in every cube. Each group of cells gets its own extended link role, so the same element means a different cube in each one. A template’s definition linkbase holds one link role per group of cells that share the same dimensions.
All 250,775 dimension-domain arcs in the 4.2 package are marked usable="false", so the domain heading itself is never a valid value; the allowed members are listed below it. 9,601 of them carry a targetRole that points at a dictionary hierarchy, such as currencies without x0.
- EBA 4.2 package
- 46,935 hypercubes in 1,353 definition linkbases, 330,896 hypercube-dimension arcs
- EBA 4.3 package
- 761 hypercubes in 66 definition linkbases (AMLA and TCB returns)
- Most hypercubes in one template
- C 13.01, CR SEC securitisations: 2,343 in its 4.2 version, 2,451 in 4.0
- Fewest
- 1, in templates such as IRRBB J 10.02 and J 11.02
COREP and FINREP hold more than half the cubes. A template with many differently shaped cells, like securitisations, needs thousands; a short list template needs one.
Hypercubes by framework, EBA 4.2ShowHide
COREP 17,080
FINREP 9,930
Pillar 3 8,208
IRRBB 3,091
IF 2,337
ESG 2,137
Resolution 944
Other 3,208Line4 count, November 2026, of every *-def.xml file under fws in the EBA 4.2 reporting frameworks package, which also carries some earlier framework versions. “Other” is remuneration, payments, asset encumbrance, funding plans, MiCA, financial conglomerates, MREL, SBP and smaller frameworks.
What it means for supervisors
Check every fact against its hypercube, not only its concept. A right number with a missing or extra dimension is a different data point, and a closed cube is the only thing that catches it.
Keep cubes closed. An open cube lets firms add breakdowns the template never asked for, and two firms can then file the same cell in two ways.
Read the targetRole. The hierarchy it points at decides which codes a cell allows, and it changes between releases more often than the cube itself.
Where AI fits, and where people decide
AI can explain a dimensional error in plain words: which concept, which dimension was missing or extra, and which member the cell expected, all read from the published hypercube.
The hypercubes are set by the supervisor, and the checks are deterministic. Software runs them as published; people decide when a template’s breakdowns need to change.
- 1Does your software report a missing or extra dimension as a dimensional error, not let it through?
- 2Are all your hypercubes closed, with dimensions only on the scenario?
- 3Does it follow targetRole to the hierarchy a cell allows, not the whole domain?
- 4Does it treat usable="false" domain headings as invalid values?
- 5Do you publish which templates’ hypercubes changed in each release?
Where Line4 fits
Line4 is SupTech software for financial regulators. It collects returns in XBRL, Excel and CSV by portal, API or MCP, validates them against your taxonomies and rules at the point of submission (see XBRL software for regulators), and puts AI to work reading them, with supervisors making every decision. If you work with a standard we have not yet run in production, we will say so plainly and show you how we would approach it.
Questions
What is a hypercube in XBRL?
A set of dimensions linked to one or more concepts in a definition linkbase. It says which dimensions a fact for those concepts must carry and which members each may take. XBRL Dimensions 1.0 defines it.
What does closed="true" mean in XBRL?
On an all arc it means a fact may carry only the hypercube’s dimensions and no others. An open hypercube, the default, allows extra dimensions. Every EBA hypercube Line4 counted is closed.
What is the difference between all and notAll?
An all arc links a primary item to a hypercube its facts must fit. A notAll arc links it to combinations its facts must not use. The EBA 4.2 and 4.3 packages use only all arcs.
What is a primary item?
The concept a fact reports, such as an amount or a ratio, as seen from the hypercube. Several primary items can share one cube through domain-member arcs between them.
What does contextElement mean?
It says whether the hypercube’s dimension values sit in the segment or the scenario of the context. The EBA uses scenario throughout, and its filing rules forbid the segment.
How many hypercubes does the EBA taxonomy have?
Line4 counted 46,935 in the EBA 4.2 reporting frameworks package, with a median of 7 dimensions each. COREP alone has 17,080; the securitisation template C 13.01 has 2,343.
What error does a fact outside its hypercube give?
xbrldie:PrimaryItemDimensionallyInvalidError under XBRL Dimensions 1.0. It means the fact’s dimensions do not fit any hypercube its concept is linked to.
Are hypercubes used outside Europe?
Yes, under other names. The SEC’s EDGAR XBRL Guide (November 2026) says hypercubes are usually called Tables and dimensions are called Axes in the SEC’s standard taxonomies, and that some tables are closed and allow only certain axes. Its examples are labelled like “Entity Listings [Table]”. Line4 checks dimensional validity the same way whatever the taxonomy calls the parts.
- XBRL International: Dimensions 1.0 (hypercubes, all and notAll arcs, closed, contextElement, error codes)
- EBA: Reporting framework 4.2 (frameworks package read by Line4)
- EBA: Reporting framework 4.3 (frameworks package and dictionary read by Line4)
- EBA: XBRL Filing Rules v5.9 (rules 2.14 and 2.15)
- SEC: EDGAR XBRL Guide (November 2026)
