Pillar 3 validation rule decoder
All 545 Pillar 3 entries in the 4.4 list are inactive. None can fire, none is an error, and only one is absent from the taxonomy. The list is published as a record rather than as a live constraint — which is worth knowing before anyone spends a morning chasing one.
Package 4.3 · 369 Pillar 3 rules across 545 entries · 0 errors · 545 inactive · 0 cross-module · runs offline
Look up a rule
Runs in your browser · nothing uploadedSearch a rule code such as v12737_m, a table code such as K_41.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 →Active, implemented, and severe are different questions
Most confusion about validation rules comes from collapsing three independent flags into one idea of “the rule applies”.
Errors
Only an error can reject a submission. The remaining 545 are warnings: they are reported, they may attract supervisory questions, and they do not stop the filing going in.
Inactive
Deactivated rules stay in the published list. Chasing one is wasted work, and a tool that does not separate them will send you after rules that cannot fire.
Not in XBRL
A rule can be live in the ITS and absent from the taxonomy. That is the gap behind a file that passes your own checks and fails at the door, or the reverse.
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 · Pillar 3 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.
- Shows plainly that no rule in this framework carries error severity, so none can reject a filing on its own.
- 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 Pillar 3, 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
Pillar 3 is the unusual case in this set: all 369 rules across 545 entries are marked inactive in the published list, and none carries severity error. Nothing here can fire during taxonomy validation and nothing here can reject a filing. Read this list as the specification of what Pillar 3 disclosure validation is intended to check, not as a pre-submission checklist — and re-check it against the current EBA publication each release, because deactivated rules are the ones most likely to come back.
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 rules with severity error can reject a filing. Warnings are reported and may prompt supervisory follow-up, but the return is accepted. Of the 545 Pillar 3 rules here, 0 are errors and 3,456 are warnings — so treating every rule as blocking overstates the problem by roughly eight to one.
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 no amount of checking a single template will surface them. A firm that validates template by template and submits module by module can pass every local check and still breach a rule that compares figures across modules. There are 0 of them in Pillar 3.
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