Line4 logoLine4

Search line4.ai

XBRL concepts: what a supervisory taxonomy lets firms report

A concept is a thing a firm can report a value for in XBRL, declared in a taxonomy schema with a name, a data type and a period type, and for amounts optionally a debit or credit balance. In supervisory taxonomies concepts are called metrics, and a concept alone is not a cell: the dimensions add the rest. Line4 counted 6,314 concepts in the EBA 4.3 and EIOPA 2.10.0 dictionaries. Every one is dated to a single instant, even the flows, and not one carries a debit or credit balance. Outside Europe, US Call Report concepts are named after their Federal Reserve MDRM code, such as RCON2170 for total assets.

Open a sample filing and check it, free in your browser →

Checks each fact against the data type of its concept, then runs the published rules. Nothing is uploaded.

Guide · 7 min read · Updated 21 November 2026 · By Jess Luper

What a concept is

XBRL 2.1 defines a concept as “a definition of a kind of fact that can be reported”. There are two kinds. An item holds one value, such as an amount, a date or a code. A tuple groups items into a compound fact, such as a director’s name, age and pay. Every concept in the EBA 4.3 and EIOPA 2.10.0 dictionaries is an item; the EBA uses tuples only to wrap filing indicators, never for data.

Each concept is declared once, in a schema (.xsd) file, and every fact in a filing points at one. The declaration fixes what kind of value the fact can hold and how it relates to time. Labels, layouts and rules are attached later, in linkbases.

6,314concepts declared in the EBA 4.3 dictionary (2,494) and the EIOPA Solvency II 2.10.0 dictionary (3,820)Line4 count of every metric in the two public dictionaries, November 2026 →
100%of them have period type instant, including the 84 EBA concepts labelled as flowsLine4 count of the same dictionaries
0carry a debit or credit balance attributeLine4 count of the same dictionaries

What a concept declares

01NameA code that is unique in its namespace, such as eba_met:mi53. Facts use it as their element name.
02Data typeMonetary, percentage, integer, decimal, date, boolean, string or enumeration. A fact that does not fit its type fails before any business rule runs.
03Period typeInstant (a value at a point in time) or duration (a value over a period). XBRL 2.1 says it “MUST be used” on every item.
04BalanceOptional, and allowed only on monetary items: debit or credit. It tells software which way an amount usually runs.
05NillableWhether a fact may be sent with no value (xsi:nil). EBA marks 1,274 of its concepts nillable, yet its filing rule 2.19 forbids nil facts, so the schema allows what the rules do not.
06For enumerations, the listAn enumeration concept names the domain and hierarchy its codes come from, so a currency concept only takes currency codes.

A concept is not a cell

In company reporting one concept often means one line of the accounts. In a supervisory taxonomy built on a data point model, a cell is a concept plus dimension values. The concept says what kind of number it is; the dimensions say what it is about.

EIOPA shows both ends of the scale in one dictionary. Its moderately dimensional concepts (2,993) carry part of the meaning in the concept itself: mi68 is labelled “Monetary | Discounted | Reported but not settled claims | Ceded”. Its highly dimensional concepts (827) carry almost none: mi1 is labelled just “Monetary”, and every other detail is a dimension.

So counting concepts tells you little about the size of a framework. The EBA 4.3 dictionary has 2,494 concepts but its tables hold far more cells, because one concept such as mi53 “Carrying amount” is reused across many templates with different dimensions.

Line4 counted 6,314 concepts in the EBA 4.3 and EIOPA 2.10.0 dictionaries. Every one is an instant, even the flows, and none carries a debit or credit.

What EBA and EIOPA actually declare

Line4 read every concept in the EBA 4.3 dictionary package (all its met.xsd files, versions 3.4 to 4.3) and every metric in EIOPA’s published 2.10.0 DPM dictionary.

In one line
Commonest type
Monetary at EBA, enumeration at EIOPA
Period type
Instant, all 6,314
Balance
None in either
Tuples or abstract concepts
None in either
EIOPA Solvency II 2.10.0 dictionary: 3,820 metrics

Enumeration 1,650 43% Monetary 1,458 38% String 332 9% Percentage 143 4% Integer 90 2% Boolean 70 2% Date 42 1% Decimal 35 1% 1,227 have an end date; 2,593 are still current

EBA 4.3 dictionary: 2,494 conceptsShowMonetary 783 31% Enumeration 757 30% Percentage 258 10% String 336 13% (184 non-empty string) Integer 118 5% Boolean 114 5% (2 true-only) Date 78 3% Decimal 50 2%

Line4 count, November 2026. EBA concepts counted once each across the dictionary’s versioned schemas; EIOPA metrics from the Metrics sheet of its DPM dictionary workbook.

Every concept is an instant, even the flows

XBRL lets a concept be a duration, which is how company taxonomies report income and cash flows. EBA and EIOPA do not use it. All 6,314 concepts are instants, and EBA filing rule 2.13 requires every period in a report to be the same reference date instant.

The flows are still there. The EBA marks 84 concepts with codes starting md and labels such as md10 “Actuarial gains and losses (flow)”, next to mi codes for stocks such as mi53 “Carrying amount”. The period they cover is set by the template and its dimensions, not by the XBRL period.

The EBA explains why in its filing rules: reporting varying “event” dates as XBRL periods would cause “complexity, confusion, and practical difficulties”, so it ties the XBRL period to the report’s reference date and puts other dates in dimensions.

No debits or credits

In company reporting the balance attribute lets software check that assets are debits and liabilities credits. None of the 2,241 monetary concepts in the two dictionaries carries one.

Where a sign matters, it is set by the reporting instructions for the cell and checked by formula rules, the same way sums are, not by the concept.

Enumerations: codes, not free text

An enumeration concept takes a value from a list in the taxonomy, such as a currency, a country or a yes/no answer. In the EBA dictionary these use the extensible enumerations type and name the domain and hierarchy their codes come from: CUA, “Currency in which the transaction / contract is denominated”, only accepts codes from the currency domain.

They are now the biggest single group at EIOPA (1,650) and almost a third of the EBA dictionary (757). A wrong code fails the type check, so firms get a precise error instead of a free-text answer a supervisor has to clean up.

Reading concept codes

Most EBA and EIOPA codes start with two letters: the data type (m monetary, p percentage, e enumeration, s string, i integer, b boolean, d date, r decimal) and then i or d. At EIOPA the second letter is always i. At EBA, d marks flows such as md10.

Treat the code as a hint, not a rule. 917 EBA concepts use codes starting with q, and EBA declares 258 percentage concepts but only 140 codes start with p. Software should read the declared data type, not guess from the name.

What it means for supervisors

Check data types first. A fact that does not match its concept’s type is rejected before any of the published rules can run, so this is the cheapest error to catch and explain.

Do not expect period or balance checks from XBRL alone. In EBA and EIOPA taxonomies dates live in dimensions and signs live in formula rules.

Use the enumeration lists. They tell you every code a firm may send, which makes clean reference data for your own analysis.

Where AI fits, and where people decide

AI can explain a concept in plain words: what mi53 means, which templates use it and which codes an enumeration allows, all read from the taxonomy.

The concepts themselves are published by the EBA or EIOPA, and the type checks are deterministic. Software runs them as published; people decide what to do with a filing that fails.

Put it to workBefore your next taxonomy release
  1. 1Does your software reject facts that do not match their concept’s data type, with a clear message?
  2. 2Does it read data types from the schema rather than guessing from concept codes?
  3. 3Do your sign checks come from formula rules, given no concept has a balance?
  4. 4Can you list the codes each enumeration concept allows?
  5. 5Do you know which concepts were added or given an end date in the new 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 concept in XBRL?

A thing a firm can report a value for, declared in a taxonomy schema with a name, a data type and a period type, and for amounts optionally a debit or credit balance. Every fact in a filing points at one concept.

What is the difference between a concept and a metric?

None in practice. EBA and EIOPA call the concepts in their data point model dictionaries metrics. A metric plus dimension values makes a data point, which is a cell in a template.

How many concepts are in the EBA and EIOPA taxonomies?

Line4 counted 2,494 in the EBA 4.3 dictionary and 3,820 metrics in the EIOPA Solvency II 2.10.0 dictionary, of which 2,593 are still current.

Why are all EBA and EIOPA concepts instants?

Because every period in an EBA or EIOPA report is the reference date instant (EBA filing rule 2.13). Flows such as gains and losses are still reported; the period they cover comes from the template and its dimensions.

Do EBA and EIOPA concepts have a debit or credit balance?

No. Line4 found no balance attribute on any of the 2,241 monetary concepts in the two dictionaries. Where a sign matters, the reporting instructions set it and formula rules check it.

What is an enumeration concept?

A concept whose value must be a code from a list in the taxonomy, such as a currency or country. It is the biggest group at EIOPA (1,650 metrics) and almost a third of the EBA dictionary (757).

What do EBA concept codes like mi53 and md10 mean?

The first letter is the data type (m for monetary) and the second shows instant or flow: mi53 is “Carrying amount”, md10 is “Actuarial gains and losses (flow)”. Not every code follows the pattern, so software should read the declared type.

What do concepts look like outside Europe, for example on the US Call Report?

Each concept is named after its Federal Reserve MDRM code: a four-letter prefix and a four-character item number, such as RCON2170 for total assets. The same item can sit under several prefixes for different scopes of the bank: 2170 appears four times in FFIEC 031, including RCFD2170 and RCON2170. By Line4’s count of the September 2026 FFIEC 031 taxonomy, its 2,913 concepts carry 2,133 different item numbers, and 2,766 of them (95%) are monetary. Like EBA metrics, they are either instant or duration: balance sheet items such as RCON2170 are instant, income items such as RIAD4340 (net income) are duration. Line4 reads both naming styles, so one platform collects returns built on either.

Share this guideShare on LinkedIn
Was this useful?

For supervisors

New guides and Insights, by email

One short email when we publish something worth your time, from Jess Luper. No spam, unsubscribe any time.