Just adding this to the forum as it has been raised already directly with CH who have confirmed that there is an issue.
We are seeing a number of CS01 filings rejected because CH thinks the name in the CS01 does not match the name of any director in the CH records:
**The name you have provided for xxxxxxx does not match any active director that Companies House holds on record. Please make any necessary amendments. If the name held by Companies House is incorrect, you must correct the directors details before resubmitting the CS01**
We have checked all of these filings and in many cases the name is exactly the same or very similar. We therefore do not think the CS01 should be rejected.
We have raised this with CH via email and they have acknowledged that there is an issue which is also affecting web filing, but they do not have a timeline for a fix. Please can we have an update @xml? We have an increasing number of companies that are getting close to or past their confirmation statement due dates and are unable to file on time because of this issue.
For the benefit of the forum, this is the latest update we have had from CH about these ongoing issues:
"This is a known issue whereby when going to accept a CS01s the rules firing on our system; even when the code is correct, doesn’t give us an option to override it, so we reject it.
We have also been advised that with any CS01 UVID issues, do NOT copy and paste the number into the relevant box but to hand type with the removal of any hyphens etc. They also need to be in upper-case.
You can also try deleting files and cookies, trying again on a different browser, or using incognito mode.
We are aware of these issues, they have been reported to our IT team, and we are working to fix them but these suggestions may work as a workaround for now."
From a software filer’s perspective, the codes are always in CAPS, we strip all hyphens and spaces and deleting files/ cookies will make no difference. So we do not know what to do.
Thank you @snicholas. Any pointers as to who we should contact? We have an increasing number of CS01s being rejected with no way of knowing what the actual issue is or when it might be fixed!!
Likely cause is that you are putting first and middle name in the first name field in the XML
You need to use all three XML fields appropriately - as the XML fields are directly mapped to internal CH processing systems - and that results in the name mismatch.
if you have technical issues at your end, try splitting the first/middle name to the correct XML fields - then the advice is to remove the middle names from the filing.
Thanks @snicholas - we think this may be the issue and are resubmitting some filings to check. Am I right in saying that this validation is new? We have never had any other filings (e.g. change of director details) validated because the first name contains first and middle names? Indeed, we have filed a large number of director appointments where the first name contains multiple names, but now appears that CH has split those names out into first and middle, and is validating against that. Is that correct?
We are also facing the same issue, it is being sent as we receive it example below, in the data request we are receiving array of forenames so in the confirmation statement we are sending that as space separated forenames, it use to work with the confirmation statement but failing for confirmation statement with verification
The name you have provided for RAJEEV PRABHAKARAN OLICKEL does not match any active director that Companies House holds on record. Please make any necessary amendments. If the name held by Companies House is incorrect, you must correct the directors details before resubmitting the CS01.
Many of our customers are facing the issue so we need a solution to this issue as soon as possible.
I’ve no idea why, but they’ve decided to enforce OtherForenames for officer identifications.
From what I can see, this appears to be whatever is included in the second value of Forename.
Yes @Imran - it is quite frustrating to access/ use data from CH that is provided in one format (Forename & Surname) as it has done for ever, but then now be required to send that same data back in a new format (with 3 fields if there is more than 1 name in Forename). We are also not sure what happens if someone has 2 names as their forename (e.g. John Paul - where Paul is not a middle name, but part of the forename).
Would we be required to split that into Forename and OtherForename?
And what happens if that person has completed IDV using “John Paul” as their forename, but then their IDV confirmation statement submission requires their name as Forename: John OtherForename: Paul - and that does not match their forename in the CH IDV record?..
We tried to submit PSCVerificationStatement today it is also failing with error
Missing Title
I have checked the xml and title is not mandatory for psc return type and it is not even sent back in data request then how are we going to fill in the title if we dont even have it. Below is the structure returned by company data request
I’m also running into issues with PSCVerificationStatement.
CH data doesn’t provide a title for a PSC, and according to the schema this field isn’t required.
Despite that, we’re consistently getting a fatal error when it’s missing. Even when sent with an empty space.
Not sure what the correct way is to bypass or handle this… any guidance would be much appreciated.
@snicholas Any update on the issue with title, since some of verifications started on 1st of this month and we were not able to file till now and deadline is 14th of this month.
PSC filings where the PSC has a title (e.g. Mr, Miss…) are getting through, but where they do not have a title (which should be acceptable as it is not a mandatory field) they are being rejected.
Any update would be great, please, as we have a number of PSCs who are getting close to the end of their 14 day window… Thanks!
