COREP/FINREP

EBA Filing Rules Explained

Detailed explanation of EBA filing rules for COREP, FINREP, and other prudential reports including naming conventions and technical requirements.

14 min readFebruary 13, 2026Xerify Team
The EBA publishes detailed filing rules that govern how institutions submit XBRL reports. Understanding these rules is essential to avoid rejection. This guide explains the key requirements and how to comply with them.

Key Takeaways

  • File naming convention is strictly enforced
  • Module codes identify report types
  • Reporting level distinguishes solo from consolidated
  • Reference dates must be precisely formatted
  • Version numbers enable resubmission tracking

Filing Rules Overview

EBA filing rules specify: • File naming conventions • XBRL and xBRL-CSV technical requirements • Validation rule implementation • Submission packaging • Error handling procedures Non-compliance leads to automatic rejection at the NCA portal.

File Naming Convention

EBA file names follow this pattern: [LEI]_[ModuleCode]_[ReportingLevel]_[ReferenceDate]_[Version].xbrl Example: 549300ABC123DEF456GH_COREP_CON_2025-03-31_001.xbrl Every component must be exact—wrong separators, case, or formatting causes rejection.

Module Codes

Key module codes: • COREP - Common Reporting • FINREP - Financial Reporting • AE - Asset Encumbrance • LR - Leverage Ratio • LCR - Liquidity Coverage Ratio • NSFR - Net Stable Funding Ratio • SBPRES - Resolution Planning Use the exact code specified for your report type.

Reporting Levels

Reporting level codes: IND (individual/solo), CON (consolidated), SUBCOT (sub-consolidated other). Select the level matching your reporting obligation. Mismatched levels trigger validation errors. Some templates are only applicable at certain levels.

Resubmission Handling

To resubmit corrections: 1. Increment the version number (001 → 002) 2. Keep all other file name components identical 3. The new file replaces the previous version 4. Revalidate before resubmission Document the reason for resubmission for audit trail purposes.

Checklist

  • LEI code is correct and active
  • Module code matches report content
  • Reporting level is appropriate
  • Reference date format is YYYY-MM-DD
  • Version number follows sequence
  • File extension is correct
  • File name validates with naming checker

Put this guide into practice

Validate your files against the latest taxonomy

We use cookies to improve your experience. Essential cookies are always active. Analytics cookies help us understand usage. Privacy Policy