Line4 logoLine4

Search line4.ai

XBRL reporting modules: how a filing says which return it is

A reporting module is one return, such as COREP own funds or FINREP, published as its own entry point: a schema file (and for xBRL-CSV a JSON file) that brings in that return’s templates and validation rules and nothing else. A filing names exactly one module by its published web address, and that choice decides which templates and rules apply. Line4 counted 50 modules in the EBA 4.2 frameworks, using 799 distinct templates, 127 of them shared by more than one module. Outside Europe, the US Call Report works the same way under another name: three forms, FFIEC 031, 041 and 051, each with its own entry schema every quarter.

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

Reads the module a filing names first, then runs the rule set built for that module. Nothing is uploaded.

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

What a reporting module is

A supervisory taxonomy is not one report. It is a shared dictionary plus many returns, and each return is published as a module with its own entry point. The EBA’s filing rules put it plainly: entry points “allow users to import the correct modules from the taxonomy, with different modules including different templates and different associated validation rules”.

So a firm never files against “the EBA taxonomy”. It files a FINREP report against the FINREP module, or a leverage ratio report against the COREP leverage module, and the module it names fixes what the supervisor’s software will expect and check.

50reporting modules in the EBA 4.2 frameworks, across 18 frameworks, each with an XSD and a JSON entry pointLine4 count of the EBA 4.2 Reporting Frameworks package, November 2026 →
799distinct templates behind those 50 modules (933 module-template links)Line4 count of the same package
127templates used by more than one module, such as C 00.01 in seven COREP modulesLine4 count of the same package

What a module brings in

Line4 opened every module schema in the EBA 4.2 package. Each one is short and does the same four things.

01The templatesIt imports one schema per template in the return. The G-SII module imports one (G 01.00); FINREP solo data points imports 136.
02The validation rulesAll 50 modules import a validation schema for their return, so the module decides which rules run.
03Filing indicatorsIt imports the filing indicator schemas, so the filing can say which of the module’s templates it contains.
04A version and a start dateIt declares one element that names the module version (for G-SII, 1.3.0) and the first reference date it applies to (31 March 2026).

How a filing names its module

An xBRL-XML filing names its module in one schemaRef element. An xBRL-CSV filing names it in the “extends” list of its report.json. Either way the value is the module’s published web address, not a local file.

The G-SII module, in framework 4.2
XSD entry point
gsii.xsd, in the EBA’s gsii/4.2/mod folder (for xBRL-XML)
JSON entry point
gsii.json, in the same folder (for xBRL-CSV)
Module version
1.3.0, from reference date 31 March 2026
Templates
One: G 01.00
In plain words

The filing points at one web address. That address loads the G-SII module, version 1.3.0, which applies from the 31 March 2026 reference date and brings in one template, G 01.00, with its rules, filing indicators and footnotes.

The schemaRef (illustrative) and gsii.json (as published)Show<link:schemaRef xlink:type="simple" xlink:href="http://www.eba.europa.eu/eu/fr/xbrl/crr/fws/gsii/4.2/mod/gsii.xsd"/> gsii.json, shortened: "eba:documentation": { "FromReferenceDate": "2026-03-31", "ModuleVersion": "1.3.0" }, "extends": [ ".../ext/2020/FilingIndicators.json", ".../ext/2020/FootNotes.json", "../tab/g_01.00/g_01.00.json" ]

The schemaRef line is Line4’s illustration of what a filing carries; the JSON excerpt is from the EBA’s published module file, shortened.

Line4 counted 50 modules in the EBA 4.2 frameworks, using 799 templates. 127 templates sit in more than one module, so the module a filing names decides which rules check them.

The EBA rules for entry points

01One module per report (rules 1.5 and 2.3)An xBRL-XML report must contain only one schemaRef (multipleSchemaRefs). An xBRL-CSV report names its module only through “extends” and must not fill in documentInfo taxonomy (multipleTaxonomyRefs).
02The right module for the date (rule 1.5)The reference must be “appropriate to the module and the reference date”, drawn from the EBA’s published list (inappropriateSchemaRef, inappropriateTaxonomyRef).
03The full published address (rule 2.2)The reference must resolve to the absolute published URL. Software may remap it to a local copy, but the filing carries the web address.
04No extensions by reporters (rule 1.11)Filings to the EBA are “closed form”: every data point is in the taxonomy, and firms must not reference their own extension taxonomies.
05Indicators per template (rule 1.6)A filing gives a filing indicator for templates in the module it names, so the module also defines what “complete” means.

What the EBA actually publishes

Line4 read the entry point list in the EBA 4.2 package (published 31 October 2025) and every module schema it points to, then did the same for the 4.3 package (published 28 June 2026), which adds new returns rather than replacing 4.2.

In one line
EBA 4.2
50 modules, 18 frameworks, 799 distinct templates
EBA 4.3
4 modules (AML risk assessment, third-country branches), 64 templates, none shared
Most modules in one framework
Remuneration, with 9
Templates carried over unchanged
50 template links in 14 modules point to earlier release folders
In plain words

Four modules (FINREP solo data points, FINREP, Pillar 3 common disclosures and COREP own funds) account for 437 of the 933 module-template links. Six modules hold a single template. 43 of the 50 first apply to the 31 March 2026 reference date.

Biggest and smallest modules, and start datesShowFINREP9DP FINREP solo data points 136 FINREP9 FINREP (IFRS 9) 124 CODIS Pillar 3 common disclosures 96 COREP_OF COREP own funds 81 IF_CLASS2 Investment firms class 2 38 COREP_NSFR COREP stable funding 35 ... 6 modules with 1 template each, incl. GSII, IPU, P3DH, MREL_DECISIONS First reference date 31 Mar 2026 43 modules 31 Dec 2025 3 (RESOL1, RESOL2, MREL_DECISIONS) 27 Feb 2026 1 (SBPIMV) 29 May 2026 1 (SBP_RM) 31 Dec 2022 1 (SEPA_IPR) 31 Dec 9999 1 (IF_TM)

Line4 count, November 2026, from META-INF/taxonomyPackage.xml and the mod folder of each framework. A template is counted once however many modules use it.

Modules share templates

Modules are not separate islands. 127 of the 799 templates in EBA 4.2 belong to more than one module. C 00.01, which records the nature of the report, sits in seven COREP modules; S 00.01 sits in all four supervisory benchmarking modules; and FINREP solo data points (136 templates) contains all 124 templates of the main FINREP module, plus 12 of its own.

That is why the module matters more than the template. The same template can be checked by different rules, and counted as complete or not, depending on which module the filing names.

Dates decide which module is right

Each module carries the first reference date it applies to. A filing for 31 December 2025 that names a module starting 31 March 2026 names the wrong one, and EBA rule 1.5 rejects it as inappropriate for the reference date.

Dates also show what is not in use yet. In 4.2 the investment firm threshold monitoring module (IF_TM) carries a start date of 31 December 9999, so no real reference date selects it.

What it means for supervisors

Check the entry point first. It is one line, and if it is wrong, missing or repeated, every later check runs against the wrong templates and rules. A clear message here saves a firm a resubmission cycle.

Check it against the reference date, not just against the list. A valid module address from the wrong release is still the wrong module.

Publish the module list with versions and start dates, as the EBA does in its package manifest and JSON files. Firms and vendors can then pick the right module without asking.

Where AI fits, and where people decide

AI can explain a module in plain words: which templates it holds, which rules it brings and why a filing’s entry point was rejected, all read from the published taxonomy.

The module list and its dates are published by the supervisor, and the entry point checks are deterministic. Software runs them as published; people decide what to do with a filing that names the wrong module.

Put it to workBefore your next taxonomy release
  1. 1Does your software read the entry point first and reject a filing with none, or with more than one?
  2. 2Does it check the module against the reference date, not only against the list of addresses?
  3. 3Does it reject references to firms’ own extension taxonomies?
  4. 4Do you publish every module with its version and first reference date?
  5. 5Do you know which templates sit in more than one module, and which rules apply to each?

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 reporting module in XBRL?

One return, such as COREP own funds or FINREP, published as its own entry point. It brings in that return’s templates and validation rules, and a filing names exactly one module.

What is the difference between an entry point and a module?

In EBA and EIOPA taxonomies they are the same thing seen from two sides: the module is the return, the entry point is the file that loads it. The EBA publishes each module as an XSD entry point for xBRL-XML and a JSON entry point for xBRL-CSV.

How many reporting modules are in the EBA taxonomy?

Line4 counted 50 in the EBA 4.2 Reporting Frameworks package, across 18 frameworks, and 4 more in the 4.3 package (AML risk assessment and third-country branches).

Can an XBRL filing reference more than one entry point?

XBRL allows it, but EBA filing rules 1.5 and 2.3 do not: an xBRL-XML report must have exactly one schemaRef, and an xBRL-CSV report names its module only through “extends”.

What is schemaRef in XBRL?

The element in an xBRL-XML filing that points at the taxonomy schema it was prepared against. In EBA filings it must hold the full published address of one module entry point.

Can firms extend an EBA taxonomy?

No. EBA filing rule 1.11 says filings are “closed form”: every allowed data point is already in the taxonomy, and firms must not reference their own extension taxonomies.

Why does the module version matter?

Each module carries the first reference date it applies to. Naming a module from the wrong release means the filing is checked against the wrong templates and rules, and the EBA rejects it.

Are there reporting modules outside Europe?

Yes, under another name. The US Call Report comes as three forms, each with its own entry schema every quarter: FFIEC 031 for banks with foreign offices, FFIEC 041 for banks with domestic offices only, and FFIEC 051 for banks with domestic offices only and assets under $5 billion. All three draw on one shared set of concepts. By Line4’s count of the September 2026 taxonomy, FFIEC 031 brings in 2,913 concepts on 36 schedules, 041 brings in 2,780 on 32 and 051 brings in 2,329 on 27, and 1,942 concepts are in all three. Line4 matches each Call Report to its form by its schemaRef, as it does with EBA modules, and runs only the edits that apply to that form.

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.