Launch - most working but some not. Others have been successful?

Confirmation Statement (New Annual Return)
1

So the new schemas launched today. Most of our form types have been accepting fine, but not the CS01, PSC04, PSC07 and PSCVS01. In case others have been successfully getting these forms accepted then it means we (I) have got it wrong.
As far as I can tell all of these forms have been passing on the sandpit and even today my submissions are still passing on the sandpit, but my live submissions have not.
So in case anyone else has feedback on that, particularly if anyone has had success with those forms then I will know I got it wrong rather than assuming there is a general system problem. Thanks.

1 Like
2

We are having issue filling has well. Here’s an example of an error message I get for a PSC04:

"Error" : {
    "RaisedBy" : "PSCChangeDetails",
    "Number" : "9999",
    "Type" : "fatal",
    "Text" : "No element 'ConfirmationDate' in class CompaniesHouse::Filing::PSCChangeDetails",
}
2 Likes
3

Again, apologies for the late response, yes this is an issue identifIed yesterday that we are working hard to resolve.

SDN

1 Like
4

Not sure if related, however we are getting a 9999 fatal response:
ConfirmationStatement
9999
fatal
Can’t use an undefined value as an ARRAY reference

This was following an error on FormIdentifier not matching form element - we used the example on the schema live service status which was:
ConfirmationStatement
We changed to
ConfirmationAndVerificationStatement
This progressed to the error : Can’t use an undefined value as an ARRAY reference

any ideas?

5

Thanks. Turned out that the CS01 was my error. Both the sending Class identifier in the gov talk section and the formIdentifier need to be changed to ConfirmationAndVerificationStatement and so I had only changed the formidentifier. It passed sandpit, but not the real world.
Second small issue once that main one was sorted is that lawfulpurpose true is seemingly not optional, but that is obviously a small and obvious fix once you get the missing statement error. Thanks again for the Companies House team that pointed out the error and sorted us out.

6

Perhaps our example will help you? In the actual govtalk section of the submission we still had a ConfirmationStatement identifier still up there and once we changed it to ConfirmationAndVerificationStatement our missing array element message went away.

7

Thanks for that, it worked and we were able to now get submissions accepted

1 Like
8

Thanks Simon.
Is this still an issue?
We are seeing the same error when attempting to file a PSC04 and I am trying to work out if it’s what we are sending or an issue on your end.

9

There are PSC filing issues at our end - i am awaiting an update on progress on a fix.

SDN

1 Like