We make extensive use of CompanyDetailsRequest. As mentioned here (http://xmlforum.aws.chdev.org/t/changes-to-companydetailsrequest/152), this response now returns Confirmation Statement details in the various RETURNS elements…
However, the Returns → NextDueDate, is still sending the old Annual Return due date and is out by 14 days.
We can account for this internally, however doing so will create issues again if it’s “fixed” and changed to the Confirmation Statement date. However, even if we apply a 14 day fix internally it looks like it could still cause problems.
For 00844529, where a Confirmation statement has been filed the call is returning
<Returns>
<NextDueDate>2016-07-28</NextDueDate>
<Overdue>NO</Overdue>
<LastMadeUpDate>2016-06-30</LastMadeUpDate>
<DocumentAvailable>1</DocumentAvailable>
</Returns>
And it looks like the old DueDate for the previous Annual Return is being retained. Which renders the field fairly meaningless going forward. Unless I’ve got very confused by due dates which is entirely possible.
Any chance of this being updated to reflect the actual Confirmation Statement due date?
ADDITIONAL:
The newly formed company 10261099 returns
<Returns>
<NextDueDate>2017-08-01</NextDueDate>
<Overdue>NO</Overdue>
<LastMadeUpDate></LastMadeUpDate>
<Returns>
Which is what the Annual Return Due Date would have been. On the beta it shows
First statement date 3 July 2017
due by 17 July 2017