Reference date vs remittance date — the two clocks
Every supervisory return runs on two clocks, and confusing them is the commonest cause of a return that is technically on time and substantively wrong. The reference date is the date the data describes. The remittance date is the date the file is due. They move independently, they can belong to different quarters, and almost every correction question turns on knowing which one you are talking about.
1. The two clocks
| Reference date | Remittance date | |
|---|---|---|
| Answers | “As at when?” | “By when?” |
| Fixed by | The reporting obligation and its frequency | The implementing standards or the collecting authority |
| Governs | Which data goes in the file, and which rules applied then | Whether the file was late |
| Changes with | The calendar | Deadline changes, extensions, national channel rules |
The consequential point is that the framework in force is determined by the reference date, not the submission date. A file submitted today for a reference date last quarter is built against last quarter’s applicable rules — which is exactly what makes late submissions and restatements harder than they look.
2. Reference period: the third concept
Some frameworks add a reference period on top of the reference date, and it is not intuitive. In Regulation (EU) 2016/867, for a given reporting reference date the reference period is defined as the period that starts on the last reporting reference date of the quarter preceding the reporting reference date and ends on that given reporting reference date.
A population built by testing the threshold only at the month end will therefore be short, and the shortfall is invisible in the file itself. This is the kind of error that surfaces months later as a data-quality query rather than as a rejection.
3. Restatements follow the reference date
When a figure turns out to be wrong, the question “which period do we correct?” is answered by the reference date the error affects — not by when it was found. Two habits keep that tractable:
- Record the framework version and rule package against each reference date, not against each submission run. A correction to an old reference date has to be built against what applied then.
- Carry restatements through every affected period. Cross-period validation rules compare a reference date against its predecessor, so correcting one period and not the next produces a fresh failure in a period that was previously clean.
FAQ
Which date determines the rules that apply?
The reference date. A file submitted late, or a correction filed now for an earlier period, is built against the framework and rules applicable to that reference date.
What is a reference period for?
Testing conditions across a span rather than at a point — most importantly thresholds. Under the AnaCredit Regulation the EUR 25 000 threshold is met if it is reached on any reporting reference date within the period.
If we restate one period, do we restate the next?
Usually yes. Cross-period validation compares consecutive reference dates, so a correction applied to one period alone tends to break the following one.
Related: Resubmissions and corrections · Reporting agents · AnaCredit phases
