Auto-enrolment issues
This journal has been raised to indicate there are some additional pieces of work that are requested for March 1st and to find out the implications if they cannot be met. 3 Auto-enrolment pieces of work have been raised. Two have been raised within the project and one within Unidesk JIRAs https://www.jira.is.ed.ac.uk/jira/browse/HRS072-7 and https://www.jira.is.ed.ac.uk/jira/browse/HRS072-6
as well as UNIDESK I130123-0079.
The timescale indicated is 1st March. More information is requested to find out if parts can go in after March 1st and be backdated or not. Also Phase 2 Tax Year End is progressing during this time for Tax Year End.
In addition HRS071 HR HESA is also progressing and it initially looks like a resource conflict will have to be raised to enable this work to progress.
18/02/13 Greg is working on the Auto-enrolement patches in DEV going through for 1st March today. JIRA HRS072-8 has now been included also and will also be implemented into DEV today.
A risk has been raised - RISK 14 regarding the security patches + including IS Apps Password + JRE patches. Issue is whether JRE patches will be able to be accommodated within the 2 days downtime
19/02/12 Update on API Until we run the auto enrolment process on LIVE, Payroll will not have the data to give you. It cannot be replicated in TEST as all new starts will not be picked up. The format will be the same as the file Pamela gave Alyson and Pamela would like it to be dated from 1st March. Payroll will not be running the first set of reports until after 1st March. Payroll have to run a payroll first to generate earnings, run the auto enrolment process and then rollback the payroll until later in the month.
The payroll timetables are available when we estimate the reports will be run but there will not be as many records after the first month.
Pamela would probably like the API run before 18th March on LIVE if possible so that we can check the records - as there will be so many in March. The first month is auto enrolling all current employees that are not in a pension scheme. We will be doing quite a few trail runs. Thereafter it will only be new starts so will be easier to manage. We may not need the API going forward if they are all defaulting to NEST on joining the University, but we will definitely need it for the first run. That will depend on the eRecruitment work being ion place which I am not involved with.
The DEV file will not work in TEST as we have not generated a pensions auto enrolment process in TEST yet. I will be able to provide a file for TEST very quickly after we run it. We just want to get it right in DEV first. (HTBN staff are not defaulted to NEST)
For info, we are waiting for a payroll to run so that we can find out if the patches have worked in DEV and we will let you know as soon as possible either way.
Alyson replied - I think we will still need the API as they are not all defaulting to NEST on joining the university. It depends on grade and salary I think and htbns will not be touched by the eRecruitment bit because they have zero salary recorded