Skip to content
EBA · EU-wide

Validation rule — why your submission was rejected

Fintech Passport
August 20, 2026 · 9-min read
Validation rule — why your submission was rejected

Validation rules are the part of a reporting framework that actually decides whether your file exists. They are published with the framework, they are part of the data point model rather than an add-on, and — critically for planning — they change more often than the framework itself. The European Banking Authority issues updated or small validation rule packages on a quarterly basis, which means a submission that passed last quarter can fail this one with no change to your data. This piece explains what a validation rule tests, how severity works, how to read the EBA’s rule files and deactivation lists, and what to do when a return bounces — with three worked cases.

1. What they test

A validation rule is a machine-checkable condition on reported data. Most are equations or inequalities between data points; some check that a value is present, has the right sign or sits within a list of allowed values. They fall into five practical families:

KindWhat it checksTypical cause of failure
StructuralThe file is a valid instance of the taxonomy in forceA superseded taxonomy edition, or a module whose applicability has moved
Intra-templateInternal arithmetic — totals equal the sum of their partsRounding applied inconsistently, or a component mapped into the wrong dimension
Cross-templateThe same data point reported in two places agreesTwo source queries built independently for what is one data point
Cross-periodConsistency against a prior reference dateA restatement that was applied to one period and not carried through
PlausibilityValues fall within expected rangesA genuine business change — which needs explaining, not fixing

The cross-template family is the one that exposes mapping weaknesses. A figure is identified by its data point, not its cell position, so if the same data point appears in two templates it must carry the same value. The data point model is what tells you which cells are in fact one figure.

2. Severity: error and warning

Every EBA rule carries a severity. With the 2.9 reporting framework the EBA replaced its older categories with two classes, error and warning. The Bundesbank’s published guidance describes “error” as the successor of what used to be called a blocking failure: if an error rule breaks at initial validation, the report is rejected and a corrected file is needed. A warning breach does not necessarily lead to rejection, but it is not free either — the institution is expected to explain it.

The underlying XBRL International specification on assertion severity uses the same logic: an error demands full compliance and results in rejection, a warning is cautionary.

Two points practitioners miss:

  • Severity is not permanent. The EBA’s own instructions for the new rule files state that a rule’s severity, and its active or inactive status, are recorded per module version, with a “sent on” date fixing from when an activation, deactivation or severity change applies. A warning today can become an error next quarter.
  • The national authority decides the handling. How explanations are collected — a feedback file, a portal field, an email — is set by each authority’s own procedure. The Bundesbank, for example, has described a process in which warnings trigger a feedback status and a file in which the institution enters explanations, and explanations are not accepted for error breaches.

3. Anatomy of a rule

Each rule has a code, an expression, the module versions it applies to, a reference-period window, a severity and a status. Rule codes in the EBA’s lists take forms such as v0492_m; national authorities that add their own checks use their own prefixes, so the prefix of a failing rule tells you immediately whose rule you broke.

Since release 4.0, rule expressions are written in DPM-XL. Much of what used to sit in spreadsheet columns now sits inside the expression itself. The EBA’s instructions describe two building blocks. A selection operator in braces names the table, rows or columns being read, the default value used when a cell is empty, and whether arithmetic is done on intervals or points. A with operator states shared context once instead of repeating it in every operand. A simple intra-template rule therefore reads as one column of a table equal to the sum of two others, each defaulting to zero when empty and compared with interval arithmetic — that is, with a rounding tolerance rather than to the cent.

The rule files changed format with DPM 2.0. The old Excel file had a tab per release going back to 2.0. The new format gives, in one document, the full history of each rule: code, module version, expression, description, from and to dates, start and end release, severity, active or inactive status, and the sent-on date. During the transition both formats were published, the new one covering only the module versions of the current releases.

4. The quarterly cycle and deactivated rules

The EBA changes rules through two routes. An updated validation rules package is published about two months before a framework release’s first reference date. A small validation rules package follows every quarter. Since release 4.0 each quarterly exercise ships a micro taxonomy package and DPM update scripts, so that rule changes stay aligned between the taxonomy and the database. The most recent quarterly update at the time of writing was published on 14 September 2026.

Each quarterly list flags rules that have been deactivated — because they were wrong or caused IT problems — and rules that have been reactivated. The EBA reminds competent authorities that data should not be formally validated against deactivated rules. Three habits follow:

  • Re-run last quarter’s accepted file against this quarter’s rules before building the new one. It is the cheapest possible early warning, and it separates “our data changed” from “the rules changed”.
  • Track deactivated and reactivated rules. A control built around a rule that has been withdrawn silently stopped working; a reactivated rule can start failing files that passed for a year.
  • Keep the failure log. The pattern of failures over time is the best available map of where your data model and the framework disagree.

5. National rules on top

The framework rules are a floor. National competent authorities routinely operate additional checks in their own collection systems, and those are the ones that generate the last-minute rejections, because they are not in the package a reporting tool ships with. A submission process that validates only against the framework rules will discover the national layer at the remittance deadline.

The practical answer is to validate twice: once against the framework rules, early, and once against the authority’s own channel as far ahead of the deadline as the channel allows — which for most collection systems means submitting a test file rather than waiting. Read the authority’s feedback file field by field: it normally gives the rule code, the cells involved and the values found, which is enough to locate the source query.

6. Worked case: a reactivated rule

Facts: a reporting firm’s quarterly prudential return has been accepted for four quarters. This quarter the authority rejects it on a cross-template rule. Nothing changed in the source data or the reporting tool.

Rule: the quarterly EBA list reactivated the rule, which had been deactivated for an IT issue. Its severity is error, so the breach is blocking.

What the practitioner does: checks the rule code against the latest list and the history file, confirms the reactivation and its sent-on date, then traces both data points. One template takes a figure after a manual adjustment; the other takes it from the raw ledger. The adjustment is moved upstream so both templates read the same value.

Outcome: the corrected file is accepted, and the rule is added to the team’s tracked list, so its next status change is seen before the deadline rather than after.

7. Worked case: a warning that is real

Facts: a payment institution’s safeguarded balance jumps after a large merchant is onboarded. The return validates with one warning on a cross-period plausibility rule.

Rule: warnings do not necessarily stop the file, but the authority expects an explanation through its own channel.

What the practitioner does: resists the suggestion to “smooth” the figure. Confirms the number against the safeguarding reconciliation, then writes a two-line explanation naming the business event and the date, and files it through the authority’s procedure.

Outcome: the return stands as filed. When the supervisor later asks about the growth, the explanation is already on record and matches the reconciliation.

8. Worked case: the national check nobody tested

Facts: a firm’s tool validates its return cleanly against the EBA taxonomy. On deadline day the national portal rejects it on a rule code with the authority’s own prefix.

Rule: the authority runs additional checks in its collection system; these are not in the EBA package.

What the practitioner does: pulls the authority’s published list of national checks, finds the rule — a requirement to report a field the EBA rules leave optional — fills it, and resubmits. Then books a test submission slot for the following quarter, two weeks before the deadline.

Outcome: the return is accepted late in the day; from the next quarter the national layer is tested before the deadline, not on it.

FAQ

Why did a file that passed last quarter fail this quarter?

Most often because the validation rule package changed. Updated or small packages are published quarterly, independently of the framework version, and rules can be deactivated, reactivated or change severity.

Should every validation alert be resolved before submitting?

Error breaches must be. Warnings may reflect a real business change, and the right response is a documented explanation rather than an adjustment.

What does a deactivated rule mean for us?

The EBA has withdrawn it, usually because it was incorrect or caused IT problems, and authorities should not formally validate data against it. Your own controls should stop relying on it too.

What is DPM-XL?

The language in which EBA validation rules are written since release 4.0. A rule’s expression now carries the table selection, the default for empty cells and the arithmetic approach.

Are the published rules the complete set?

No. National competent authorities commonly apply their own additional checks in their collection channels, which is why an early test submission is worth more than a late internal validation.

Where do we find a rule’s history?

In the EBA’s rule file in the new format, which records for each module version the expression, applicability dates, severity, status and the date from which a change applies.

9. What to do, today

  1. Head of regulatory reporting: download the latest quarterly EBA list and compare deactivated and reactivated rules against your own controls.
  2. Reporting team: re-run last quarter’s accepted file against the current rules and log every new failure with its rule code and severity.
  3. Data team: trace every cross-template data point to a single source query.
  4. Compliance: keep a register of warning explanations filed, so the next supervisory question is answered from the record.
  5. Everyone: book a test submission with your authority’s channel well before the next deadline.

Related: Data point model · Resubmissions and corrections · XBRL taxonomies · What is supervisory reporting · Surviving a framework release

Related reads.