Example 2: 06722505 , received on 2025-10-30 22:26:29, same as above. This company has not filed anything today. Last submission was weeks ago in October
Example 3: 11213127, received just now. Nothing filed today
This is alarming as each notification triggers a ‘Hey something was filed, but we know that’s not true’ response.
Unfortunately I don’t have the actual timepoints logged against these. Just the time. However, I’ve now added some more logging to monitor it. I’ll provide new time points if/when I can recreate it.
Timepoint 27739759, FUL SERVICES LTD, Company No 10599451. Notification type received Officers. Time 21:20:20.2540 BST
Timepoint 27751883, RICHARDS UK PROPERTIES LTD, Company Number 12224097, Notification type officers. Time 21:28:25 BST
I don’t see any updates to any of these companies on the CH website recently.
Note that these have been received after clearing the timepoint and I was using the default timepoint. The examples I provided earlier without the timepoints were using whatever the latest available timepoint was.
It’s interesting that this evening I have only seen delayed officer notifications. Hopefully its just a fundamental misunderstanding of how timepoints in officer streams work on my part.
Hello. In regard to the above officer examples, as per 'Officers' and ‘Persons with significant control’ resource specification update please be aware we are currently running jobs to bulk load Identity Verification statement dates to the public register ready for the change of legislation on 18th November (hence why they are not the result of a submission from the company’s). I suspect that will explain the activity you are seeing.
The timepoints in all the streams are sequential but publications to the stream are not necessarily the result of an accepted submission e.g. a data maintenance exercise in Companies House could result in the publication of new events.
Hence, in regard to your initial query (filing history events that can not be traced back to an associated, timely submission), the most likely cause is that our internal records were changed for some reason. This would result in a re-publication of the event even if the change was only to meta data that is not included in an event message i.e. a time stamp that is not in the ‘data’ object.