FINREP validation rule decoder
FINREP is the largest framework and the least blocking: 4,929 entries for 2,492 rules, but only 197 errors. What makes it awkward is elsewhere — 177 cross-module rules, more than twice COREP’s, because financial statements reconcile against prudential figures. Those are the ones template-by-template checking never finds.
Package 4.3 · 2,492 FINREP rules across 4,929 entries · 197 errors · 195 inactive · 177 cross-module · runs offline
Look up a rule
Runs in your browser · nothing uploadedSearch a rule code such as e4429_e, a table code such as F_00.01, 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 →The cross-module problem is a FINREP problem
177 of the framework’s rules compare figures across modules, the highest count in the package.
Errors
FINREP is the largest framework and the least blocking. Financial statements are reported and reconciled rather than tested against hard limits, so almost everything is a warning.
Inactive
195 FINREP entries are inactive — low for a framework of this size, because FINREP rules tend to be amended rather than withdrawn.
Not in XBRL
239 FINREP rules are absent from the taxonomy, mostly the ones comparing accounting figures the taxonomy does not relate to each other.
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 · FINREP 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 FINREP, 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,492 FINREP rules in this package, 194 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,298 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. FINREP is overwhelmingly informational: 197 errors against 4,732 warnings. A firm treating every FINREP breach as blocking is overstating the problem roughly twenty-four fold.
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. FINREP carries 177, the highest count in the package, because accounting figures are reconciled against prudential ones reported elsewhere. This is the single largest source of FINREP rejections.
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