Line4 logoLine4

Search line4.ai

XBRL enumerations: answers picked from a list

An enumeration is a concept whose answer is a code picked from a list, such as Yes, No or Not applicable, a country or a currency. Under Extensible Enumerations 1.0 the concept names a domain and a hierarchy, and the allowed answers are the usable members of that hierarchy. The fact holds the member’s name, such as eba_CU:EUR. Line4 counted 448 enumerations among the 2,185 metrics in the EBA 4.3 dictionary, about 1 in 5. Outside Europe, the SEC lists Extensible Enumerations 1.0 and 2.0 among the specifications every EDGAR filing may use.

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

Runs the published validation rules on a real filing. Nothing is uploaded.

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

What an enumeration is

Many questions in a return have a fixed set of answers: Has the bank changed a material assumption? In which currency is the contract? Which approach does the firm use? An enumeration concept holds one of those answers as a code from the taxonomy, not as free text, so every firm writes the same answer the same way.

XBRL International’s Extensible Enumerations 1.0, a Recommendation since 29 October 2014, defines the type enum:enumerationItemType. Each concept of that type must carry two attributes: enum:domain, the head of the code list, and enum:linkrole, the hierarchy that picks the allowed members.

01enum:domainThe domain the codes come from, such as Currency (CU) or Geographical area (GA). It MUST be specified.
02enum:linkroleThe extended link role whose domain-member arcs list the allowed codes. It MUST be specified, and lets one domain serve many shorter lists.
03enum:headUsableOptional. If true, the domain head itself is also an allowed answer. No EBA 4.3 enumeration uses it.
448enumeration metrics among 2,185 in the EBA 4.3 dictionary, drawing on 78 domainsLine4 count of the EBA 4.3 dictionary, November 2026 →
4allowed answers in the median EBA enumeration; 110 have exactly two, 37 have 100 or more, the largest 359 countriesLine4 count of the hierarchies the same 448 metrics point to →
10,474enumeration facts among 179,347 in 75 public EIOPA and Bank of England sample filingsLine4 count of the XML samples served by Line4 Check, November 2026 →

How the allowed list is set

The specification is exact: the allowed values are “the set of usable domain members obtained by following domain-member relationships starting from the domain head in the extended link role identified by the @enum:linkrole attribute.” A member marked usable="false" in that hierarchy is a heading, not an answer.

A fact with any other value fails: “Facts reported against concepts with a type of enum:enumerationItemType with a non-nil value MUST have a value that is in the domain of enumeration values for the concept. enumie:InvalidFactValue MUST be raised if this condition is not satisfied.”

This is how the EBA keeps one currency domain but many currency questions. Line4 found 13 enumerations on the CU domain; the 12 with a list point at hierarchies of 166 to 186 currencies.

An example: one IRRBB yes-or-no question

The EBA’s IRRBB template J 10.02 asks whether the bank changed a material assumption in its economic value of equity measure. The metric is ei1002, an enumeration on the Code Lists domain (ZZ) with hierarchy ZZ830.

ei1002, EBA 4.3 dictionary
Label
Change of material assumptions (EVE)
Type
enum:enumerationItemType, domain eba_exp:ZZ, linkrole ZZ830
Allowed answers
3: eba_ZZ:x773 Yes, eba_ZZ:x774 No, eba_ZZ:x775 Not applicable
Declared
Twice in the 4.3 dictionary, once with the 3.4 hierarchy and once with the current one
In plain words

The bank answered Yes. The value is a name, not the word “Yes”, so software reads it the same way in every language. The prefix eba_ZZ must be declared in the file, or the value means nothing.

In the filing (shortened)Show<eba_met:ei1002 contextRef="c1">eba_ZZ:x773</eba_met:ei1002>

Line4’s reading of met.xsd, met/3.4/met.xsd and dom/zz hier-def.xml in the EBA 4.3 dictionary, with member labels from dom/zz/mem-lab-en.xml. The fact line is Line4’s illustration in the shape the specification requires.

Line4 counted 448 enumerations in the EBA 4.3 dictionary, about 1 in 5 metrics. Each one turns a question into a code every firm writes the same way.

What the EBA and the samples hold

Enumerations are the second most common kind of EBA metric, after amounts (783) and ahead of percentages (258). Nearly half of them, 212 of 448, sit on four domains: Code Lists, Boolean total, Codes and Geographical area.

They are also the only metrics the EBA declares more than once. The 4.3 dictionary holds 2,494 metric declarations for 2,185 names; the 309 extra are all enumerations, redeclared when their allowed list changes. Every other type is declared once.

In one line
EBA 4.3 dictionary
448 enumerations of 2,185 metrics, 757 declarations, 78 domains
Shortest lists
110 with two answers, such as LEI code type or National code type
Longest lists
37 with 100 or more, mostly countries and currencies; the largest 359
75 sample filings
10,474 enumeration facts of 179,347: EIOPA 9,683, Bank of England 791
In plain words

Most enumerations are short yes-no or pick-one questions. A few are long country or currency lists, and those are where firms most often send a code the cell does not allow.

EBA enumerations by domain, 4.3ShowCode Lists (ZZ) 138 Boolean total (BT) 27 Codes (qCO) 25 Geographical area (GA) 22 Main category (MC) 15 Approach (AP) 13 Currency (CU) 13 Other 71 domains 195

Line4 count, November 2026, of every met.xsd in the EBA 4.3 dictionary and the hierarchies their enum:linkrole points to, starting from the enum:domain head as the specification says. Two metrics point at no usable list and are left out of the list sizes, which cover 446. Sample counts are facts named ei followed by digits in the XML samples served by Line4 Check; Bank of England banking samples use EBA members such as eba_CU:EUR.

Extensible Enumerations 2.0

Version 2.0, a Recommendation since 12 February 2020, adds a set type, enum2:enumerationSetItemType, for questions with several answers. It also changes how the value is written: an expanded name URI, the namespace and the member name joined by #, instead of a prefix that depends on the file.

Its error codes are more specific: enum2ie:InvalidEnumerationValue for a bad single answer, and InvalidEnumerationSetValue, RepeatedEnumerationSetValue and InvalidEnumerationSetOrder for sets, whose values must be unique and in order. The EBA 4.3 dictionary still uses version 1.0.

What it means for supervisors

Check every enumeration against its own hierarchy, not the whole domain. A real currency code can still be wrong for a cell that allows only some currencies.

Keep a fallback member for the real world. The EBA Filing Rules describe eba_CU:x46, “Other Currency (open axis tables)”, for currencies missing from its list or not yet in ISO 4217.

Publish changed lists with each release. Because the EBA redeclares an enumeration when its list changes, the same question can have two declarations, and firms need to know which one their module uses.

Where AI fits, and where people decide

AI can turn a failed code into plain words: which question, which answer was sent, and the answers the cell allows, all read from the published hierarchy.

The lists are set by the supervisor, and the check is deterministic. Software tests the value against the list as published; people decide when a list needs a new answer.

Put it to workBefore your next taxonomy release
  1. 1Does your software test each enumeration fact against its own linkrole, not the whole domain?
  2. 2Does it reject headings marked usable="false" as answers?
  3. 3Does it check the value’s prefix is declared in the file?
  4. 4Do you publish which enumeration lists changed in each release?
  5. 5Is there a fallback member for real-world codes your list does not have yet?

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 an enumeration in XBRL?

A concept whose value is a code picked from a list in the taxonomy, such as Yes, No or a currency. Extensible Enumerations 1.0 defines the type enum:enumerationItemType.

How does XBRL decide which enumeration values are allowed?

The concept names a domain (enum:domain) and a hierarchy (enum:linkrole). The allowed values are the usable members found by following that hierarchy’s domain-member arcs from the domain head.

What does an enumeration fact look like?

In xBRL-XML the value is a QName, a prefix and a member name, such as eba_CU:EUR. In Extensible Enumerations 2.0 it is an expanded name URI: the namespace and member name joined by #.

What error does a wrong enumeration value give?

enumie:InvalidFactValue under Extensible Enumerations 1.0. Version 2.0 uses enum2ie:InvalidEnumerationValue, with separate codes for set values that are invalid, repeated or out of order.

How many enumerations does the EBA taxonomy have?

Line4 counted 448 enumeration metrics among 2,185 in the EBA 4.3 dictionary, on 78 domains. The median allows 4 answers; the largest, a country list, allows 359.

Why does the EBA declare some enumerations twice?

When an enumeration’s allowed list changes, the EBA declares it again with the new hierarchy. Line4 found 757 declarations for the 448 enumerations, and no other metric type declared more than once.

What is the difference between Extensible Enumerations 1.0 and 2.0?

Version 2.0, from February 2020, adds a set type for several answers at once and writes values as expanded name URIs instead of prefixed names. The EBA 4.3 dictionary uses version 1.0.

Are enumerations used outside Europe?

Yes. The SEC’s EDGAR XBRL Guide (November 2026) lists both Extensible Enumerations 1.0 and 2.0 among the specifications every EDGAR filing may use, with the prefixes enum and enum2. It also makes some uses an error, such as an enum2:domain attribute on an element. Line4 checks enumeration values against the taxonomy’s allowed list for each regulator.

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.