The issue with the expiry dates of policies that incept from 1st March 2019 onwards has now been resolved and the fix has been made live. Any records created before today will need to be reviewed and the expiry date manually corrected.
Thank you for your patience whilst we resolved the issue, and please accept our apologies for the inconvenience caused.
We have identified an issue affecting the expiry dates of policies with a one year term with inception dates of 1st March 2019 onwards – with 2020 being a leap year the expiry date of these policies is one day short of what it should be. We are working on a fix to resolve this issue as a matter of urgency but, in the meantime, the expiry dates of any affected policies should be manually amended.
This does NOT affect Renewals or MTAs.
The issue arises when the inception for a new quote is changed and the period originally does not cover the leap day and is then changed to include it.
SchemeServe currently recalculates the expiry date by taking the new inception and advances by the exact term of the policy.
This logic is to stop non standard length policies getting their term reset when the inception changed.
It is causing this issue because in this case the term should actually change from 365 to 366 days.
We are testing the patch now, updates to follow...