Skip to content
EBA · EU-wide

Supervisory reporting — the anatomy of a return

Fintech Passport
August 20, 2026 · 9-min read
Supervisory reporting — the anatomy of a return

A supervisory return is not a document — it is the output of a specification, and the specification changes on a published cycle. Understanding that is the difference between a reporting function that plans and one that reacts. Every return, from a bank’s own-funds file to a payment institution’s safeguarding table or a fraud return, has the same anatomy — and each part has real dates and rules attached.

1. The six parts of every return

PartWhat it fixesExample
The obligationWho reports, what, how oftenArticle 96(6) PSD2: statistical data on fraud to the competent authority
The framework releaseData point model, taxonomy, templatesEBA reporting framework 4.x; a national authority’s own tables
The reference dateThe date the data describes31 March, 30 June, 30 September, 31 December
The remittance dateThe date the file is due12 May for the 31 March quarter under Regulation (EU) 2021/451
The channelHow and where the file is deliveredA national portal, file transfer or API
The validation rulesThe tests the file must passFramework rules plus the collecting authority’s own checks

Only the first is law in the ordinary sense. The other five are technical artefacts published on a schedule — and they are where most of a reporting team’s year actually goes. The detail on the two clocks is in reference date vs remittance date; the channel landscape is mapped in reporting channels compared.

2. Three families, often confused

A payment or e-money institution in the EU typically owes returns from three families, and each has a different purpose, collector and tolerance for approximation.

PrudentialStatisticalConduct, fraud and AML data
QuestionIs this firm safe?What is happening in the economy?Are customers and the system protected?
CollectorThe supervisorThe central bank, directly or via the supervisorSupervisor, central bank or financial intelligence unit
Typical contentBalance sheet, own funds, safeguarded funds, P&LPayment volumes and values, balance-sheet items by sector and residenceFraud by type and liability bearer, complaints, AML risk data
Typical frequencyMonthly to annualMonthly to half-yearlyHalf-yearly or annual

The bridge between the first two is in prudential vs statistical reporting compared. The practical conclusion: one intermediate data model carrying every qualifier any return needs, rendered several times, rather than parallel pipelines that drift apart.

3. What a framework release actually contains

A release is a package, not a document. For the European Banking Authority’s frameworks it comprises the data point model — a structured representation identifying the business concepts, their relations and the validation rules — the XBRL taxonomy expressing that model in a technical format, the validation rules, and annotated templates that consolidate the regulatory text with the templates and instructions for that version.

Releases are numbered sequentially: 4.0 applied from December 2024 reference dates, and 4.2 finalised the transition of the data dictionary to DPM 2.0. Applicability is set per module, and validation rules can change between releases, so “we are on version X” does not answer “what applies to this submission” — the reference date does. The upgrade discipline is in managing a taxonomy release upgrade.

Most payment and e-money institutions never file the EBA’s CRR taxonomies. Their prudential returns use national templates — in Luxembourg, the CSSF’s Z tables (payment institutions) and W tables (e-money institutions) under Circulars CSSF 11/511 and 11/522 — with the same anatomy.

4. Reference dates, remittance dates and corrections

The clearest codified example is Commission Implementing Regulation (EU) 2021/451, the ITS on supervisory reporting for institutions under the CRR, which applies from 28 June 2021 and repealed Implementing Regulation (EU) No 680/2014. It is written for credit institutions and in-scope investment firms, but its mechanics are the template most national regimes echo:

  • Reference dates (Article 2): month-end for monthly reporting; 31 March, 30 June, 30 September and 31 December for quarterly; 30 June and 31 December for semi-annual; 31 December for annual.
  • Remittance dates (Article 3(1)): by close of business on the 15th calendar day after the reference date for monthly; 12 May, 11 August, 11 November and 11 February for quarterly; 11 August and 11 February for semi-annual; 11 February for annual.
  • Weekends and holidays (Article 3(2)): a deadline falling on a Saturday, Sunday or public holiday in the competent authority’s Member State moves to the next working day.
  • Unaudited figures (Article 3(4)): may be submitted; where audited figures later differ, the revised figures go in without undue delay. Other corrections follow the same standard under Article 3(5).
  • Format (Article 21): monetary values to at least thousands of units, institutions identified by LEI, each file accompanied by reference date, currency, accounting standard and scope of consolidation.

In any regime, the framework in force is set by the reference date, and a correction is a new submission of the affected return, not a patch. The mechanics of correcting are in what is a resubmission, and what to do when a deadline is missed is in late filing and reporting incidents.

5. The fraud return: a supervisory return every PSP owes

The one return almost every payment and e-money institution shares is the PSD2 fraud return. The EBA Guidelines on fraud reporting under Article 96(6) PSD2 (EBA/GL/2018/05, amended by EBA/GL/2020/01 with effect from 1 July 2020) set the content:

  • Report both unauthorised payment transactions and transactions resulting from manipulation of the payer, by volume and value, and only transactions that were actually executed.
  • Report every six months (Guideline 3.1). Small payment institutions exempted under Article 32 PSD2 and e-money institutions waived under Article 9 of Directive 2009/110/EC report annually, with the data still split into two six-month periods (Guideline 3.2).
  • The deadline is set by the national competent authority (Guideline 3.3); the authority then has six months from the day after the end of the reporting period to send aggregated data to the ECB and the EBA.
  • Losses per liability bearer are reported in the period they are booked, not the period of the fraud, and exclude insurance refunds.
  • Authorities report adjustments to past periods in the next window, up to 13 months after execution — mirroring the payer’s notification right under Article 71 PSD2.

Collection routes differ: in Luxembourg, for example, fraud statistics under Circular CSSF 19/712 go to the Banque centrale du Luxembourg rather than to the CSSF. The full field-by-field build is in the PSD2 fraud return, how it is built.

6. Three worked scenarios

Scenario A — the channel changes under a quarter already closed. Facts: a Luxembourg e-money institution files its monthly balance sheet and safeguarding tables (W 1.1, W 1.2) and quarterly capital adequacy and P&L (W 1.4, W 2.1) as Excel files under Circular CSSF 23/833. Its Q1 2027 return falls due in April 2027. Rule: the CSSF announced in September 2026 that an integrated eDesk module will replace the Excel process and Circulars 11/511 and 11/522; 1 January to 31 March 2027 is a test-only window, and from 1 April 2027 eDesk is the sole official channel for any report whose deadline falls on or after that date — even where the period ended earlier. What the practitioner does: treats the March 2027 monthly and the Q1 2027 quarterly as eDesk filings, runs a full dry submission in the test window, and chooses early between manual entry and the automated S3 route with a JSON file. Outcome: the first live eDesk filing repeats a rehearsed one. Detail: CSSF eDesk, S3 and API.

Scenario B — fraud reclassified after the return went in. Facts: a payment institution filed its H1 fraud return. In October its fraud team reclassifies a cluster of transfers from unauthorised to manipulation of the payer, and books final losses on several cases. Rule: the categories are distinct breakdowns; adjustments to past periods flow through the next reporting window within 13 months of execution; losses are reported when booked. What the practitioner does: corrects the H1 transaction categories through the authority’s resubmission route, places the newly booked losses in H2 rather than restating H1, and logs both decisions. Outcome: H2 is consistent with a corrected H1, and losses do not oscillate between periods.

Scenario C — a deadline on a weekend, then an audit adjustment. Facts: a group credit institution’s annual return for 31 December is due on 11 February, which falls on a Saturday; it files unaudited figures on the Monday. In March the auditors adjust provisions. Rule: Article 3(2) of Regulation 2021/451 moves the deadline to the next working day; Article 3(4) requires the revised, audited figures without undue delay. What the practitioner does: diarises the shifted date, flags the file as unaudited, and on the audit opinion resubmits every affected template, re-checking cross-period rules. Outcome: on time, then promptly corrected.

7. Running the reporting year

  • One calendar, keyed to deadlines. List every return with its reference date, remittance date, channel and owner. Country calendars are a starting point: Spain, Luxembourg, France.
  • Version log per reference date. Record the template or taxonomy version, rule package and source extract used for each period, so any correction can be rebuilt against what applied then.
  • Pre-validate. Run the rules locally; channel rejections cost days.
  • Branches count. Host authorities may collect data from branches — see host state vs home state reporting.

8. FAQ

Is supervisory reporting the same as statistical reporting?

No. Supervisory (prudential) returns test whether a firm is safe; statistical returns feed central-bank aggregates. They have different legal bases and collectors and define common-sounding concepts differently. Most payment firms owe both, plus fraud and AML data returns.

Do payment and e-money institutions file COREP and FINREP?

Not under Regulation (EU) 2021/451, which covers institutions under the CRR. Payment and e-money institutions report on national templates set by their home supervisor, though some national regimes borrow the same structure and some groups file both.

Which date decides the rules that apply to a return?

The reference date. A late file or a correction for an earlier period is built against the template version and rules applicable to that reference date, not the day it is sent.

How often must a PSP report fraud data?

Every six months under the EBA guidelines. Exempted small payment institutions and waived e-money institutions report once a year, split into two half-year periods. The submission deadline is set by the national authority.

Do we correct an error found after filing, or wait for the next period?

Correct the affected period through a resubmission without undue delay, then check whether the following period also needs restating because cross-period validation compares consecutive reference dates.

9. What to do, today

  1. Build or refresh a single register of every return you owe: obligation, family, reference date, remittance date, channel, template version, owner.
  2. Confirm the current fraud-return deadline with your national authority and whether you fall under the annual regime for exempted institutions.
  3. Check for announced channel changes — such as the CSSF’s eDesk switch on 1 April 2027 — and book a test submission inside any test window.
  4. Start a version log keyed to reference dates, not to submission runs.
  5. Write down your correction procedure: who decides, how a resubmission is made, and how the next period is checked.

Related: The data point model · XBRL taxonomies · Validation rules · The EU regulatory reporting guide

Related reads.