Files and Exceptions
There are a few file and exceptions componenets that need to be configured for MyCSP.
Cutover Files
The cutover files are a snapshot of an employee’s data as of the cutover date. All members of a Civil Service Pension scheme, as well as those who have opted out, must be included in the cutover files. If any transactional data is effective on cutover files, they should not be included in the cutover file. You must ensure that the set of MyCSP data recorded on Cloud Payroll as at cutover date matches the last interface sent on your legacy payroll system.
Monthly Interface Files
MyCSP interface is incremental; only changed records are submitted. This helps MyCSP build the employee record throughout the pension year in order to access their pension rights. It is therefore important that all changes are recorded and reported in a timely manner. The types of change that are reported to MyCSP include (but are not limited to):
- New hire or rehire.
- Employee’s basic information such as name, marital status, and address.
- Change to employment information such as assignment category, and change of FTE.
- Absences – most absence types are reportable to MyCSP. How an absence is reported is determined by the legislative grouping code you associate with its absence type.
- Some absences constitute cases of Assumed Pensionable Pay. These are identified automatically based on the absence type and the rate of pay.
- Changes to the employee’s enrolment such as a transition to Alpha, or move to a partnership scheme.
- Members opting in or out of a pension scheme.
- Leavers.
- Salary increases.
- New bonus or allowance, or a change to an existing bonus or allowance.
Interface files are submitted on a calendar month basis only and both the monthly code and interface files default to the last date of the previous calendar month based on the system date.
The Control Totals file is generated as part of the cutover and monthly interface process.
Exceptions
All changes that take place during the month, as well as retrospective changes effective in previous months will be included within the relevant files. However, there are a few exceptions:
- Retrospective changes with an effective date prior to cutover date: those changes will be reported as at cutover date, and not effective date.
- Retrospective changes with an effective date prior to the start of the previous pension year. All changes effective in the current year, current year minus 1, or current year minus 2, will be reported with correct effective date. Older changes will be reported as at the start of previous pension year.
- Retrospective changes relating to the previous period of employment: where an employee has left the company and was rehired at a later date, any changes related to the previous period of employment will not be reported.
It is your responsibility to inform MyCSP where a change of Start Date is required.
Code Files
Assuming the minimum required setup was completed, all grades, bonuses, and allowances for the selected Paypoint Code are included in the cutover and monthly code files, irrespective of whether they are assigned to an employee or not, and irrespective of whether or not there have been changes to a code file since the previous month. It is recommended that you run this file every month.