Nil return — reporting that nothing happened
“We had nothing to report” and “we reported that we had nothing” are different statements, and several regimes only accept the second. A nil return — also called a negative declaration — is an affirmative statement, for a given period, that no reportable events occurred. Where a regime requires one, not filing is a breach even though there was genuinely nothing to say.
1. Why regimes require them
Silence is ambiguous. From the authority’s side, a missing file could mean no activity, a technical failure, a firm that has forgotten, or a firm that has decided not to report. A nil return removes the ambiguity and makes the population complete, which is what lets an authority monitor coverage at all.
| Situation | What the authority can conclude |
|---|---|
| No file received | Nothing — the cause is unknown, and follow-up is required |
| Nil return received | The firm was in scope, checked, and had nothing reportable |
| Populated return received | The firm was in scope and had reportable activity |
2. Where they show up
Nil or negative reporting appears across several families of obligation. Periodic AML declarations frequently require a negative declaration where no reportable operations occurred in the period, and firms with narrow product sets file them routinely for months at a time. Some prudential and statistical collections apply the same logic through a reduced or empty submission for entities whose in-scope activity is nil. Others take the opposite approach and treat non-submission as correct where there is nothing to report.
Because the answer is regime-specific, the only reliable method is to record it per obligation rather than to generalise. A reporting calendar that lists only the populated returns will miss the nil ones precisely because they never generate work.
3. Making it honest
The risk with nil returns is not that they are hard — it is that they become automatic. Three cheap controls keep them meaningful:
- Evidence the check, not the file. Retain the query or extract showing the population was empty, with its run date. The file proves you filed; the extract proves you looked.
- Alert on the transition. The dangerous period is the one where activity starts and the process still files nil out of habit. A rule that flags any period where the population moves from zero to non-zero is worth more than the return itself.
- Review the scope test annually. A nil return that has been correct for two years may be correct only because the scope test was written for the old product set.
FAQ
Do we have to file if we have nothing to report?
It depends on the obligation. Some regimes require an affirmative negative declaration; others treat non-submission as correct. Record the answer per obligation rather than assuming one rule across your calendar.
What should we retain for a nil period?
Evidence that the check was run and returned nothing — the query, extract or report with its run date — alongside the submitted file or its acknowledgement.
What is the main failure mode?
Filing nil out of habit in the first period where activity actually occurs. A control that flags the zero-to-non-zero transition catches it.
Related: Spain’s monthly operations declaration · Resubmissions and corrections · What is supervisory reporting
