Skip to content
EBA · EU-wide

Late filing — what to do when a return will miss

Fintech Passport
August 21, 2026 · 9-min read
Late filing — what to do when a return will miss

Late filing is a decision every reporting function eventually faces under time pressure: file late and correct, or file on time and wrong. It is a genuine judgement with supervisory consequences either way, and the worst version is making it at 6pm on the deadline with no agreed route and nobody willing to own it. The decision should be pre-made as a framework, before the situation that needs it. Below: how the deadline works, the options, who decides, when to tell the authority, three worked incidents and the fixes.

1. What “late” actually means

Before deciding anything, be precise about the deadline you are about to miss. For credit institutions reporting under the CRR, the EBA’s implementing technical standards on supervisory reporting — adopted as Commission Implementing Regulation (EU) 2021/451 — fix the calendar in Article 3, and the original text is unusually concrete:

  • Close of business on the remittance date is the cut-off, not midnight.
  • Quarterly returns are due on 12 May, 11 August, 11 November and 11 February; semi-annual on 11 August and 11 February; annual on 11 February; monthly on the 15th calendar day after the reference date.
  • Where the remittance day is a Saturday, a Sunday or a public holiday in the Member State of the receiving authority, data are due on the following working day.
  • Unaudited figures may be submitted; where audited figures later differ, the revised figures go in without undue delay — and so do any other corrections to submitted reports.

Check the version in force for your reference date, because the reporting ITS are amended regularly. Payment and e-money institutions, and branches filing national returns, usually work to deadlines set by the national competent authority’s own circulars and portals rather than this calendar — the logic below is the same, but confirm the exact cut-off in the instrument that governs your return.

2. The two options, honestly compared

File late, completeFile on time, incompleteFile on time, limitation disclosed
What you breachThe remittance deadlineNothing yet — but you have submitted something you know to be wrongNothing, provided the correction follows as stated
VisibilityImmediate and unambiguousDeferred, and discovered by the authority or by youImmediate, on your terms
Follow-on workNone, once filedA resubmission, potentially across several periodsOne planned resubmission
Best whereThe delay is short and the error would be materialAlmost never defensibleThe gap is quantified, explainable and bounded

3. Who decides

The decision needs a named individual with authority to take it, plus a deputy — because reporting deadlines do not respect leave. Assigning it to a committee guarantees the decision is made by default, which in practice means whatever the operational team does in the last hour.

Three things should be recorded at the time, not reconstructed later: what was known, what was decided, and by whom. That record is what converts an incident into a managed event, and it is the first thing a supervisor asks for if the incident recurs. A one-page incident log per return is enough:

  • the return, the reference date and the remittance date;
  • the cause, the affected templates or fields and the quantified impact;
  • the option chosen, the reason, the decision owner and the timestamp;
  • what the authority was told, when, through which channel;
  • the correction date and the root-cause action, with an owner.

Link the log to your reporting governance and sign-off framework so that the person who decides is the same person who signs the return.

4. Tell the authority before the deadline, not after

The single most effective action, and the one most often skipped out of embarrassment, is a short proactive notification before the deadline passes: what has happened, what you will file and when, and what you are doing about it.

It costs nothing and changes the character of the event entirely. An authority that learns of a delay in advance is managing a known issue with a cooperative firm. The same authority discovering a missing return is managing an unexplained failure — and the second framing attaches to the firm rather than to the incident.

Where the reporting channel has a contact route for this, use it. Where it does not, the supervisory relationship contact is the right recipient, and a two-paragraph email is sufficient. Keep it factual: the return and reference date, the cause in one sentence, the quantified impact, the date you will file or correct, and the name of the person accountable. Never promise a date the delivery team has not confirmed.

5. Worked case: a source system fails two days out

Facts: a bank’s quarterly COREP return for the September reference date is due on 11 November. Two days before, a source system fails. The extract can be produced manually, but one dimension — a counterparty classification — cannot be derived for a subset of exposures.

What the rule says: the remittance date is fixed at close of business; there is no extension mechanism in the ITS. Corrections to submitted data go in without undue delay.

What the practitioner does: quantifies the affected subset first, because materiality determines everything else. If it is small and the gap can be described, the return goes in on time with the limitation disclosed to the supervisor and a stated correction date. If it is large enough to distort capital ratios, the decision owner opts to file late and notifies the supervisor before the cut-off, explaining why. Either way, the decision, its basis and its owner are logged, and — because the incident revealed a dependency nobody had documented — the source system is added to the reporting dependency map with a contingency.

Outcome: one controlled resubmission instead of a silent misstatement, and a dependency that will not cause the same incident twice.

6. Worked case: the rejected file nobody saw

Facts: a payment institution uploads its periodic national return on the deadline day. The portal accepts the upload, but the authority’s validation later rejects the file. The rejection notice goes to a shared mailbox nobody monitors, and the team discovers it a week later when preparing the next period.

What comes back: from the authority’s side, no valid return was received by the deadline — the upload is not a filing. The firm is now late without having decided to be.

What the practitioner does: fixes the validation errors and resubmits immediately; notifies the authority the same day, stating when the original upload happened, why it was rejected and when the valid file went in; and treats the missed acknowledgement as the real finding. The control fix is to make “filed” mean “acknowledgement received and matched”, with a named owner checking it before the deadline closes.

Outcome: a late filing on the record, but one the firm found, explained and closed itself.

7. Worked case: audited figures move after submission

Facts: a bank submits its annual return on 11 February using unaudited figures. In March the external audit adjusts a provision, changing reported own funds.

What the rule says: unaudited figures are permitted; where audited figures deviate, the revised figures must be submitted without undue delay.

What the practitioner does: nothing about the February filing was late, so this is not a late-filing incident — it is a correction. The function resubmits the affected templates promptly once the audit opinion is issued, checks whether any later period carries the same figure forward, and records the resubmission against the original incident log. See resubmissions and corrections for how to scope one.

Outcome: compliant on the deadline and on the correction duty.

8. What makes late filing likely

Three structural features predict it, and all three are fixable outside an incident:

  • No margin. A return always filed on the last possible day has no resilience. If the extract depends on a month-end close that lands two days before the deadline, a one-day close delay is a reporting incident.
  • Single points of failure. One person who can approve, one person who can submit, one certificate nobody monitors. Each of these turns an ordinary absence or expiry into an incident.
  • Unmonitored acknowledgements. A submission is complete when the acknowledgement is received and matched. Without that control, a rejected file is recorded as filed and the deadline is missed without anyone knowing.

A practical calendar sets an internal deadline some working days ahead of each remittance date, a test upload where the portal allows validation before formal submission, and a post-deadline check that every acknowledgement is in. The dry run that tests the process rather than the file is what surfaces the first two features, and it surfaces them in a week when nothing is due.

FAQ

Is it better to file late or file wrong?

Usually neither. File on time with the limitation disclosed and quantified, and a stated correction date. Where the gap would distort the return, file late with a proactive notification.

Should we tell the authority in advance?

Yes. A delay notified before the deadline is a managed issue; the same delay discovered by the authority is an unexplained failure, and that framing attaches to the firm.

What if the remittance date falls on a weekend?

Under the EU supervisory reporting ITS, data are due on the following working day where the date is a Saturday, Sunday or public holiday in the receiving authority’s Member State. National returns follow their own rules, so check the governing instrument.

Does an upload count as a filing?

Not until the authority’s validation accepts it. Treat a return as filed only once the acknowledgement has been received and matched to the submission.

How fast must we correct an error found after filing?

Under the EU reporting ITS, corrections and revised audited figures go in without undue delay. In practice, set and communicate a specific date rather than relying on the phrase.

Can we ask for an extension?

The EU reporting ITS contain no extension mechanism. Never assume a national authority has granted one unless it confirms in writing.

What is the most common hidden cause?

An unmonitored acknowledgement. Without matching it, a rejected file is recorded as filed and the deadline passes unnoticed.

What to do, today

  • Head of regulatory reporting: name the decision owner and deputy for every return, and write the late-versus-limited decision rule down before you need it.
  • Reporting team: set an internal deadline ahead of each remittance date and make “acknowledgement matched” the definition of filed.
  • Compliance / supervisory liaison: confirm the channel and contact for a pre-deadline notification for each authority you report to, and keep a two-paragraph template ready.
  • COO: map the source systems and certificates each return depends on, and assign a contingency to every single point of failure.

Related: Resubmissions and corrections · Answering a data-quality query · Reporting governance · Testing a new return

Related reads.