Late filing — what to do when a return will miss
Every reporting function will eventually face the same decision 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.
1. The two options, honestly compared
| File late, complete | File on time, incomplete | |
|---|---|---|
| What you breach | The remittance deadline | Nothing yet — but you have submitted something you know to be wrong |
| Visibility | Immediate and unambiguous | Deferred, and discovered by the authority or by you |
| Follow-on work | None, once filed | A resubmission, and potentially across several periods |
| Best where | The delay is short and the error would be material | The gap is immaterial, disclosed, and the correction is scheduled |
2. 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.
3. 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 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.
4. 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 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.
The dry run that tests the process rather than the file is what surfaces the first two, and it surfaces them in a week when nothing is due.
5. A worked case
Facts: a source system fails two days before a remittance date. The extract can be produced manually but one dimension — a counterparty classification — cannot be derived for a subset of records.
What the decision looks like: the affected subset is quantified first, because materiality determines everything else. If it is small and the gap can be described, file on time with the limitation disclosed and a stated correction date. If it is large enough to distort the return, file late with a proactive notification explaining why.
What the practitioner does either way: notifies the authority before the deadline; records the decision, its basis and its owner; and — because the incident revealed a dependency nobody had documented — adds the source system to the reporting dependency map with a contingency. The last step is the one that stops the same incident happening twice.
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 is the most common hidden cause?
An unmonitored acknowledgement. Without matching it, a rejected file is recorded as filed and the deadline passes unnoticed.
Related: Resubmissions and corrections · Answering a data-quality query · Reporting governance
