Company Data Request v3.1

Sorry as previously mentioned you can not submit CompanyDataRequest, hence the examples provided

To be clear. You want us to efile confirmations of what you have at CH and you’re not providing any facility for us to use companydatarequest before the live date to get the data that needs confirming?

If this is the case, are you allowing us to re-submit declarations from our databases (either in error or by policy but in either case blind) which may already be present on yours and you will detect duplication on your side without submission failure on our side?

Hi Charlotte,

  1. In this post you provide some examples of the companyDataRequest. As we can’t test it, just to be extra sure, would you mind providing examples with Corporate PSCs?

  2. We are also wondering how the PSC person level statements would show up in the companyDataRequest XML. Do you have any examples?

  3. According to the BaseTypes, ServiceAddressType has only “SameAsRegisteredOffice” as “true” or nothing, but in this example you have <SameAsRegisteredOffice>Y</SameAsRegisteredOffice>. Should the ‘Y’ be ‘true’ instead (and no SameAsRegisteredOffice element is ‘false’)?

  4. In this example you have the nature of control OWNERSHIPOFSHARES_25TO50PERCENT_AS_PERSON but the PSC Basetypes do not specify this nature of control. I assume that in the example, OWNERSHIPOFSHARES_25TO50PERCENT_AS_PERSON should be OWNERSHIPOFSHARES_25TO50PERCENT. Is the assumption correct?

  5. In this example you have a director with multiple Forename elements. But in this incorporation XML the <OtherForenames> element is used instead. Which one is correct?

Thanks

Thanks for query we will get you some examples through shortly

1 & 2) - Here is an example with a person level statement, legal person and corporate person

  1. This is as per live now, it is inconsistent

  2. This is a mistake, sorry, which we are putting a fix in for shortly and I shall correct the examples.

  3. This is an inconsistency rather than a mistake sorry.

The live company data request is returning N for the sameas elements, Also the statement of capital does not match the Schema it is the old version containing the unpaidamountpershare.

Also should I be receiving this error message for made up dates prior to today?

Request date must be today’s date or before 30/06/2016

We are looking into the issue with capital and will get back to you ASAP. Do you have an example of a company returning ‘N’ for sameAs as I cant see that problem sorry. Can I ask what date you were using please for the other issue please. thanks

1 Like

The date I used was 01.07.2016, company number 10259776 returns

>  <PSCs>
>             <PSC>
>                <PSCNotification>
>                   <Individual>
>                      <Forename>@@@@@@@@</Forename>
>                      <Surname>@@@@@@@@@</Surname>
>                      <ServiceAddress>
>                         <SameAsRegisteredOffice>N</SameAsRegisteredOffice>
>                         <Address>

Data request

<GovTalkMessage>
  <EnvelopeVersion>1</EnvelopeVersion>
  <Header>
    <MessageDetails>
      <Class>CompanyDataRequest</Class>
      <Qualifier>request</Qualifier>
      <TransactionID>41422</TransactionID>
    </MessageDetails>
    <SenderDetails>
      <IDAuthentication>
        <SenderID>xxxxxxxxxxxxxxxxx</SenderID>
        <Authentication>
          <Method>clear</Method>
          <Value>xxxxxxxxxxxxxxxx</Value>
        </Authentication>
      </IDAuthentication>
      <EmailAddress>software@xxxxxxxx.co.uk</EmailAddress>
    </SenderDetails>
  </Header>
  <GovTalkDetails>
    <Keys />
  </GovTalkDetails>
  <Body>
    <CompanyDataRequest xmlns="http://xmlgw.companieshouse.gov.uk" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlgw.companieshouse.gov.uk http://xmlgw.companieshouse.gov.uk/v2-1/schema/CompanyData-v3-1.xsd">
      <CompanyNumber>10259776</CompanyNumber>
      <CompanyAuthenticationCode>XXXXXX</CompanyAuthenticationCode>
      <MadeUpDate>2016-07-04</MadeUpDate>
    </CompanyDataRequest>
  </Body>
</GovTalkMessage>

thanks - can i just check what date do you use when you get this error:
Request date must be today’s date or before 30/06/2016

The first of July 2016

Is there any update on this issue?

Apologies. The capital fix went in last night so you should now TotalAmountUnpaid. Forename issue you mentioned where the schemas are different between when we return middle names as multiple forenames or otherForenames, is because the schemas are inconsistent sorry. So what you get returned for middle names will depend on the schema you are using. The date issue, is because the date has to be either todays date or a date before SBEE if you are trying to file an AR01. Sorry for delay hope that helps.

Two points

  1. The SameAsRegisteredOffice issue remains on PSCs ie

    N

This means that the XML does not conform to the Schema

  1. Also we are not using the Datacheck for an Annual return but for a CS01, the CS01 may not be dated today. Is the intention to make this work for any date apart from the current date?

We are looking at the SameAsRO and SameAsServiceAddres element returning N or Y, which is incorrect it should be true or false as you mentioned so this will go live early next week. Thanks

Please can I seek clarification on the Forename \ Otherforname issues. When using the CompanyData-v3-1.xsd schema for made up dates greater than 01/07/2016. Should we expect

a) Multiple forenames elements
b) One forename and one otherForenames element

The schema seems to suggest that is should be b, but currently a is being returned.

@mark_fermandel

The simple answer is no, the CompanyDataRequest will only return data for the company as at today’s date.

Thanks,

Mark

It is incorrect but this is the same for PSCs and Officers, which I dont believe we have changed so we wouldnt want to change it and break the companyDataRequest for others. Although I appreciate its not clear but wary of causing more problems.

Can you please confirm that when the sameasserviceaddress and sameasRO is changed to true or false that the same will be done for SecureAddressInd and SuperSecureIndividual as these are also being returned with N or Y?

Thanks

HI. We are hoping to change the SameAs flags in tonights release to update to use true/false and we will investigate the secure flags, as I would have the SecureAddressInd that it would always have returned Y or N. We will investigate and get back to you.

Just a quick point there are no false value for the sameas elements in the schema. The value should be true or the element omitted to meet the schema.