Line4 logoLine4

Search line4.ai

How do regulators version XBRL taxonomies?

A supervisory taxonomy changes in numbered releases, and at the EBA each release carries only the frameworks it changes, with the older tables its modules still use. Tables are versioned one by one, so one reporting module can mix versions: by Line4’s count, the EBA’s FINREP national accounting module in release 4.2.1 uses 139 tables, 130 from 4.2, 6 re-issued in 4.2.1 and 3 still from 4.0. Outside Europe, the SEC releases a new US GAAP taxonomy every year, and the FFIEC publishes a new Call Report taxonomy every quarter.

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

What a taxonomy version is

A supervisory taxonomy is published in numbered releases. The EBA’s recent ones are 4.0, 4.1, 4.2, 4.2.1, 4.3 and 4.4. Since 4.0 the EBA has used “release numbers instead of publication dates in release folders” (EBA, reporting framework 4.0), so the version is part of every web address: a FINREP table from release 4.2 sits under …/fws/finrep/4.2/tab/, and the same table re-issued later gets a new address.

Because the address carries the version, a filing says exactly which version it was prepared against, through its entry point. Two filings of the same template can be checked against different definitions and different rules, and both be right.

01ReleaseA numbered package, such as EBA 4.4. At the EBA it holds the frameworks that changed, not the whole taxonomy.
02ModuleOne return, such as FINREP or COREP own funds, with its own entry point. A module is re-issued when anything in it changes.
03TableOne template. Tables are versioned one by one, so an unchanged table keeps its older address and a new module can still point to it.
04Point releaseA small release, such as 4.2.1, that re-issues one module without touching the rest.
139tables in the EBA 4.2.1 FINREP national accounting module, drawn from three releases (4.0, 4.2 and 4.2.1)Line4 count of the EBA 4.2.1 taxonomy package, November 2026 →
116 of 137Pillar 3 tables re-issued in EBA 4.4 phase 1 with the same data points as in 4.2Line4 count of the EBA 4.2 and 4.4 phase 1 packages →
6reporting frameworks in the EBA 4.4 phase 1 package, against 18 in 4.2Line4 count of the same packages →

What each EBA release carried

Line4 counted the public EBA packages. Release 4.2 is the large one: the EBA re-issued every module except DORA, “due to the finalisation of the data dictionary transition to DPM 2.0 and new glossary” (EBA, reporting framework 4.2). The releases either side carry only what changed. Release 4.4 is split in two “to accommodate for the IFRS18 earlier application” (EBA, reporting framework 4.4): phase 1 from December 2026, phase 2 from September 2027.

So a supervisor cannot simply swap one taxonomy for the next. COREP is not in the 4.4 phase 1 package and stays on its earlier release, while Pillar 3 disclosures and resolution planning move to 4.4. The systems that collect and check the returns need every one of those releases loaded at once.

What each EBA package holds (counted by Line4)
4.1 (July 2025)
4 frameworks, 12 modules: ESG, MiCA, payments and Pillar 3 disclosures
4.2
18 frameworks, 50 modules, from FINREP and COREP to MREL, remuneration and supervisory benchmarking
4.2.1
1 module: FINREP on national accounting (finrep9dp), with 2,369 validation rules
4.3
2 frameworks, 4 modules: AMLA risk assessment and third-country branches; 241 rules
4.4 phase 1
6 frameworks, 13 modules: AMLA, IFRS 18 additions to FINREP, MREL decisions, Pillar 3, resolution planning and third-country branch liquidity; 813 rules
What it tells a supervisor’s system

To read one FINREP filing on 4.2.1, the system needs table definitions from three releases. Drop 4.0 because “we are on 4.2 now” and three FINREP tables can no longer be read.

Where the 4.2.1 FINREP module finds its tablesShowfinrep9dp (release 4.2.1): 139 tables 130 …/fws/finrep/4.2/tab/… 6 …/fws/finrep/4.2.1/tab/… 3 …/fws/finrep/4.0/tab/…

Counted from the module schemas in the EBA 4.1, 4.2, 4.2.1, 4.3 and 4.4 phase 1 taxonomy packages, published on the EBA’s reporting framework pages. Release dates from the same pages.

What a re-issued table really changes

A table with a new version address has not always changed. Line4 compared the data points in each table the EBA re-issued in 4.4 phase 1 with the version before it. Every data point in an EBA table has a stable code, so the comparison is exact.

01Pillar 3: 21 of 137 changed137 disclosure tables were re-issued from 4.2. 21 gained or lost data points (431 added, 279 removed in total); the other 116 have the same data points at a new address.
02Resolution planning: 12 of 38 changedAll 38 RESOL1 and RESOL2 tables were re-issued. 12 changed their data points (76 added, 85 removed). The validation rules went from 168 to 184.
03AMLA: 1 of 32 changedAll 32 risk assessment tables from 4.3 came back in 4.4. Only W 05.01 changed, gaining two cells for the value of remittances in and out. Two new tables joined the module, and a new eligibility module brought nine more.
A new taxonomy version is not a new taxonomy. Much of it is the old one at a new address.

What it means for supervisors

Every release is work twice over: firms change their reporting, and the supervisor changes its collection, its checks and its analysis. The real change sits in the tables whose data points moved, but the work often lands on every table with a new address, because systems key on the address.

Map data points across versions, not table addresses. A table whose data points did not change can carry its history straight across a release; one that did needs a decision on how the old and new figures line up. Keep old releases loaded for as long as firms can resubmit earlier periods.

Where AI fits, and where people decide

Comparing two releases is a deterministic job: list the data points, rules and tables added, removed or kept, and which modules use which release. Software should do it the day a package is published.

AI is useful on top of that list. It can read the change notes and the new rule text, group the changes by what they mean for analysis, and draft the note to firms. Whether a changed data point can be compared with the old one, and where a time series breaks, is a supervisor’s call.

Put it to workQuestions to ask before the next release
  1. 1Which taxonomy releases do your systems have loaded today, and which modules use each?
  2. 2Do you compare releases by data point, or only by table name?
  3. 3How long do you keep an old release for resubmissions of earlier periods?
  4. 4Which time series break at the next release, and who decides how to join them?
  5. 5How soon after a package is published can you test it on real filings?

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 XBRL taxonomy versioning?

The way a supervisory taxonomy changes over time: in numbered releases, each with its own web addresses, so every filing says exactly which version it was prepared against. At the EBA each table is versioned on its own, so one module can use tables from several releases.

Does a new EBA taxonomy release replace the old one?

Not completely. Each package carries only the frameworks that release changes, plus the older tables its modules still use. By Line4’s count, the 4.4 phase 1 package has 6 frameworks and 13 modules, against 18 frameworks and 50 modules in 4.2, so many returns stay on earlier releases.

Why does one module use tables from different versions?

Because tables are versioned one by one. An unchanged table keeps its older address and the new module points to it. The EBA 4.2.1 FINREP national accounting module uses 139 tables: 130 from 4.2, 6 from 4.2.1 and 3 from 4.0.

What changed between EBA 4.2 and 4.4 for Pillar 3?

By Line4’s count, the EBA re-issued 137 Pillar 3 disclosure tables in 4.4 phase 1. 21 gained or lost data points, 431 added and 279 removed in total; 116 kept the same data points at a new version address.

Why was EBA reporting framework 4.2 so large?

The EBA re-issued every module except DORA in 4.2, “due to the finalisation of the data dictionary transition to DPM 2.0 and new glossary”. By Line4’s count the package holds 18 frameworks and 50 modules.

How do supervisors keep time series across taxonomy versions?

By mapping data points rather than table addresses. Where a data point is unchanged, its history carries across the release; where it changed, a supervisor decides how the old and new figures relate, and records that decision.

How often does the EBA release a new taxonomy?

Several times a year. Framework 4.0 applied from March 2025, 4.1 from June 2025, 4.2 from the fourth quarter of 2025, and 4.3 and 4.4 phase 1 from December 2026, with 4.4 phase 2 from September 2027 (EBA reporting framework pages).

How often do taxonomies change outside Europe?

At different speeds. The SEC releases a new US GAAP taxonomy every year, and its EDGAR XBRL Guide says there is a new version even when nothing of substance changed. The FFIEC publishes a Call Report taxonomy for every quarter, back to March 2001, and each quarter’s schema carries the date in its name, such as call-report031-2026-09-30-v301.xsd. Japan’s FSA published its 2026 EDINET taxonomy on 11 November 2025. Line4 keeps each release side by side and checks a file against the version it names.

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.