Streaming API event not matching REST API

Data Issues
1

The last company-profile event received for company 05744019 on 2024-09-30 12:53:08.309065 UTC / event timepoint 84217747 shows an incorrect next accounts due on date:

  "accounts": {
    "overdue": null,
    "last_accounts": {
      "period_start_on": "2022-01-01",
      "period_end_on": "2022-12-31",
      "made_up_to": "2022-12-31",
      "type": "full"
    },
    "next_due": "2024-09-30",
    "next_accounts": {
      "overdue": null,
      "period_start_on": "2023-01-01",
      "period_end_on": "2023-12-31",
      "due_on": "2024-09-30"
    },
    "next_made_up_to": "2023-12-31",
    "accounting_reference_date": {
      "month": "12",
      "day": "31"
    }

However on the webpage the next accounts are due 2025-09-30: SMARTE CARTE UK LIMITED overview - Find and update company information - GOV.UK

Please can this be looked into?

2

I note this company’s company-profile received a new event on 21st October with the corrected information. Thank you to whoever fixed this.

1 Like
3

Hi,

I have evidence of 1491 companies where the latest made_up_to date from the streaming API does not align with the latest made_up_to date from the REST API. It looks like the streaming API’s accounts.latest_accounts.made_up_to hasn’t actually been updated to the latest made_up_to date available.

Could this please be looked into?

Best,
Luca

4

1491 registration numbers with mismatches attached:
streaming_vs_rest.txt (80.2 KB)

5

Thank you for taking the time to collate this and report it to us. We are investigating the issue.

1 Like
6

We have found an issue with our system. While that is investigated, we have just re-issued those company profiles.
Again thank you for taking the time to report these.

7

Hi Mark,

is there any update on this issue, was it resolved ?

1 Like
8

yes this has been resolved.

9

I’m not sure this has been resolved yet, we’re still experiencing issues with stream events being “stale” and not matching data from the REST API

1 Like
10

We’re also experiencing the issue, doesn’t seem like it is resolved.

11

This issue appears to be quite serious and widespread - we estimate there are almost 30k companies now whose streaming API records on company-profile for period end dates & next accounts due dates do not match those of the REST API.

I appear to be unable to attach any files to the forum but can provide a list.

Please can this be looked into urgently?

1 Like
12

27k registration numbers were reported to CH as having incorrect company-profile dates were re-streamed on 2025-02-11 with corrections.

13

Even if companies are re-issued we’re still seeing non-matching data…

We’re long term users of the REST API and are trying to integrate streaming now for real-time updates. To ensure accuracy of the stream we’ll call the REST endpoint and compare

The majority of comparison differences are on lastAccounts, nextAccounts and confirmationStatement, which I guess would make sense if these fields are most common to change?

Also quite a few show differences on the etag field which I guess isn’t too important if the data matches but our understanding is this is essentially a hash of the data.

14

We were told by CH that a fix (reported above) went in on 9th December, which apparently has fixed events after this date, but any event generated before will remain incorrect in our own records until an updated version is streamed.

We’ve pretty much given up using the Streaming API for now until we have more confidence in it.