COREP validation rule decoder
COREP is the densest of the six: 3,923 entries for 2,468 rules, and 467 of them are errors — more than the other five frameworks combined. It also carries 151 rules that are live in the ITS but absent from the taxonomy, the largest such gap anywhere in the package. Look one up, or filter to the set that can actually reject a return.
Package 4.3 · 2,468 COREP rules across 3,923 entries · 467 errors · 650 inactive · 79 cross-module · runs offline
Look up a rule
Runs in your browser · nothing uploadedSearch a rule code such as e22959_n, a table code such as C_01.00, or any words from the rule text. Filters combine.
Knowing the rule is not passing it. The converter runs the validation rules against your data before submission and reports breaches by severity — with a free tier to start.
Create free account →Where COREP differs from the rest
Own funds, large exposures and leverage generate far more blocking rules than any other framework.
Errors
Of the six frameworks COREP produces the most blocking rules by a wide margin. Own funds, large exposures and leverage all reconcile internally, and each reconciliation is an error rather than a warning.
Inactive
650 COREP entries are switched off. Because the framework is large and long-established, deactivations accumulate faster here than anywhere else.
Not in XBRL
151 COREP rules are not implemented in XBRL, the largest gap in the package. A COREP file can satisfy the taxonomy and still breach the ITS.
Cross-module
Rules spanning more than one module. Template-by-template checking never catches these, which is why they break submissions disproportionately often.
Reviewed 21 August 2026 · source: EBA validation rules package 4.3 of 23 June 2026 · Source: EBA validation rules list, the 4.3 package, as supplied · compiled 20 August 2026 · COREP subset
What this decoder does
It doesResolve and filter
- Finds a rule by code, by table, or by words in its text.
- Filters on severity, active status, XBRL implementation and cross-module scope, in combination.
- Gives a one-click view of the rules that can actually reject a filing: active, implemented, and an error.
- Shows the tables a rule touches, so you can see where to look.
- Runs entirely offline against an embedded copy of the list.
It does notValidate anything
- Check your data. It has no access to your file and never will.
- Reproduce the Expression and Precondition columns. The Description shown here is as published, and for many rules it embeds the formula itself.
- Cover frameworks other than COREP, which have their own pages.
- Cover releases other than 4.3.
- Tell you which templates you are required to file.
Start from what can block you
Of the 2,468 COREP rules in this package, 362 are simultaneously active, implemented in XBRL and severity error. Those are the ones that can reject a filing, and they are the list worth working through before a submission window. The remaining 2,106 are either informational, dormant, or invisible to the taxonomy — useful context, but not what stops a filing.
Nothing you search here leaves your browser
The rule list is embedded in the page and every search runs on your own machine. No query is sent to REGREP, and nothing is logged.
That is deliberate. Which rules you are chasing says a good deal about what is failing.
About validation rules
Does a warning stop my submission?
No. Only severity error can reject a filing. In COREP that distinction matters more than elsewhere: 467 of 3,923 entries are errors, so roughly one in eight breaches will actually stop the return rather than merely be reported.
What does "not implemented in XBRL" mean?
That the rule exists in the published list but is not part of the taxonomy's own validation. It will not fire when your instance document is validated against the taxonomy, even though the rule is live. It is a separate question from whether the rule is active, and the two do not always agree.
Why keep inactive rules in the list at all?
Because the published list is a record as well as a specification — rules are deactivated rather than deleted, so that historical periods and prior releases remain interpretable. For a current filing they are noise, which is why this tool filters them out rather than hiding the distinction.
What makes cross-module rules different?
They span more than one module, so checking a template in isolation never surfaces them. COREP has 79 — fewer than FINREP’s 177, because COREP’s reconciliations tend to sit within own funds rather than across the financial statements.
Why isn't the rule expression shown?
Because the formal expression is the authoritative artefact and belongs in the EBA's own publication, where it carries its context and preconditions. Reproducing it here would invite people to implement from a summary. The description tells you what the rule is about; the EBA list tells you exactly what it tests.
Which release is this?
Package 4.3, from the list supplied for this build. Rules are added, deactivated and re-severitied between releases and between published versions of the same release, so check the current EBA publication before relying on any single entry.
Finding the rule is the easy half.
Create a free account and run the validation rules against your own data before the submission window, not during it.
No card required · free tier on core modules · nothing stored from this tool