FINREP for Spanish PIs and EMIs — the reduced taxonomy

FINREP is not bank-only. Spanish-licensed Payment Institutions and Electronic Money Institutions file a reduced FINREP set against the EBA-coordinated taxonomy, submitted to Banco de España. The reduced version captures fewer tables than the CRR-bank FINREP but follows the same XBRL conventions and is checked against the same validation framework. Most first submissions fail the same way — incomplete mapping of off-balance-sheet items, mis-classified safeguarding accounts, missing counterparty sectors. This piece walks through what the reduced FINREP covers, where the mapping work concentrates and how it sits alongside the rest of the Spanish reporting catalogue.

1. What FINREP is

FINREP — Financial Reporting — is the EBA’s harmonised reporting framework for supervisory financial information. The original implementation in Commission Implementing Regulation (EU) 680/2014, refreshed multiple times since, sets out the templates and the XBRL taxonomy. National supervisors collect the data and forward it to the EBA’s central data store.

For CRR-bank credit institutions, FINREP runs to many tables. For non-bank PSPs in Spain, Banco de España requires a reduced subset that captures the balance-sheet, income-statement and selected counterparty data needed for supervisory oversight without the full prudential apparatus.

2. Who files reduced FINREP in Spain

• Electronic Money Institutions authorised under Law 21/2011
• Payment Institutions authorised under Royal Decree-Law 19/2018
• Branches in Spain of foreign-licensed EMIs and PIs, for their Spanish-attributable activity

The obligation flows from Banco de España Circular and the cross-referenced EBA Guidelines. Smaller PIs and AIS-only providers may face proportionate reductions; check the current BdE circulars for the specific carve-outs.

3. The reduced FINREP tables

The core blocks of the reduced FINREP for PIs and EMIs:

• Balance sheet — assets, liabilities, equity, with the line-item granularity the supervisor needs to assess capital adequacy and safeguarding
• Income statement — interest income / expense (limited for non-lenders), fee and commission income / expense, operating expenses, results from financial operations, impairment
• Customer-funds breakdown — e-money outstanding (EMIs) and customer-payment balances (PIs), split by the safeguarding model
• Off-balance-sheet items — guarantees, commitments, contingent liabilities
• Related-party transactions — group, shareholders, directors
• Counterparty breakdowns — by sector, country and residual maturity for relevant items

4. Cadence and channel

• Frequency: typically quarterly for headline tables, semi-annual or annual for some supplementary breakdowns; check the current Banco de España calendar
• Submission deadline: generally T+30 to T+45 calendar days from the reference date, varying by table
• Format: XBRL against the EBA reduced FINREP taxonomy
• Channel: via EDITRAN for institutional filers; some non-XBRL supplementary returns travel through complementary BdE portals

5. Where the mapping work concentrates

Three areas swallow most of the engineering time on a first submission:

• Safeguarding accounts. Customer funds segregated under Article 7 EMD2 or Article 10 PSD2 sit on the EMI / PI balance sheet but are not unencumbered own funds. The FINREP classification needs to match the supervisor’s view, with the safeguarding-vehicle counterparty correctly identified.
• Counterparty sectoring. Every counterparty in the breakdowns has an ECB sector code. Customer-master systems built around tax / KYC IDs often lack a clean sector mapping. Building it once is reusable for AnaCredit, statistical returns and CIRBE.
• Off-balance-sheet items. Guarantees and commitments that look small in commercial volume can be reportable. The discipline of mapping every product to a FINREP line is non-trivial; under-reporting is a common finding.

6. FINREP and COREP — different things

Spanish PIs and EMIs file FINREP-style financial information. They do not file CRR-bank COREP. Their own-funds reporting follows the PSD2 / EMD2 calculation methods. For Spanish investment firms, COREP under IFR / IFD applies — see our COREP IFR piece for that track.

7. Reconciliation with other returns

FINREP totals at year-end must reconcile to the audited financial statements. Mid-year submissions are checked against statistical returns and against the CIRBE aggregates where the institution holds credit exposures. Persistent reconciliation breaks are a supervisory matter — Banco de España’s data-quality team flags pattern errors and asks for an explanation.

8. Getting started — practical sequence

• Pull the reduced FINREP taxonomy from the EBA’s current published set; align local data to the line items, not the other way round
• Build the counterparty-sector mapping once and reuse it across FINREP, statistical returns, CIRBE and AnaCredit (where applicable)
• Map safeguarding accounts with explicit counterparty identification and segregation evidence
• Run a dry submission against the BdE test environment before the first live filing
• Set up reconciliation processes — FINREP vs. financial statements, FINREP vs. CIRBE — from the start, not after the first finding

9. FAQ

10. What to do, today

• If you are scoping a new Spanish licence, build the FINREP data layer alongside the application — not after grant.
• Map safeguarding accounts to FINREP line items explicitly; vague placeholder accounts fail validation.
• Reuse the counterparty-sector mapping across every reporting framework — CIRBE, AnaCredit, statistical returns, FINREP.
• Plan one BdE pre-production dry submission per reporting cycle; first-time live submissions rarely pass clean.
• Treat reconciliation between FINREP, financial statements and CIRBE as a continuous control, not an annual exercise.

Related: SURFI France · Banca d’Italia Segnalazioni · DNB statistical reporting · What is CIRBE? · AnaCredit for payment firms · EMI licence in Spain