COREP/FINREP

FINREP Validation Best Practices

Expert guidance on validating Financial Reporting (FINREP) submissions to avoid common errors and ensure NCA acceptance.

16 min readFebruary 14, 2026Xerify Team
FINREP (Financial Reporting) is the EBA's framework for harmonized financial reporting by credit institutions. This guide focuses on validation best practices to help you produce error-free FINREP submissions.

Key Takeaways

  • FINREP validation has both technical and business rule layers
  • Cross-template consistency checks are critical
  • Reconciliation with COREP is required
  • Early validation prevents deadline pressure
  • Documentation supports audit queries

FINREP Overview

FINREP provides standardized financial statement reporting: • Balance sheet (F 01.01 - F 01.03) • Income statement (F 02.00) • Comprehensive income (F 03.00) • Breakdown of assets and liabilities • Non-performing exposures (F 18.00) • Forborne exposures (F 19.00) Both IFRS and national GAAP variants exist with different template applicability.

Validation Layers

FINREP validation includes: 1. Technical validation (XBRL syntax, schema conformance) 2. Intra-template validation (within-table consistency) 3. Inter-template validation (cross-table checks) 4. Business rules (EBA-defined logic checks) 5. Data quality rules (outlier detection, trend analysis) All layers must pass for successful submission.

Common Validation Errors

Watch for these frequent issues: • F 01.01/F 01.02 balance mismatch • Income statement vs comprehensive income inconsistency • NPE ratios outside expected ranges • Missing breakdown details • Sign convention errors (credits vs debits) Pre-validate each template before combining the full submission.

Cross-Report Checks

FINREP must reconcile with COREP: • Own funds (C 01.00) vs equity (F 01.03) • Total assets reconciliation • RWA supporting data Discrepancies trigger regulator queries. Document any intentional differences with clear explanations.

Quality Assurance Process

Implement a robust QA process: 1. Source data validation before extraction 2. Template-level checks during generation 3. Full submission validation 4. Trend comparison vs prior periods 5. Peer comparison where data available Maintain validation logs for audit evidence.

Checklist

  • Source data reconciled to GL
  • Template-level validation passed
  • Cross-template checks completed
  • COREP reconciliation verified
  • Prior period comparison reviewed
  • Outliers investigated and documented
  • Full submission validation clean
  • Validation log archived

Related Resources

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