Assignment Category Changes

For further information on the assignment categories used in MyCSP reporting, see: Service History File Setup.

Note: In accordance with MyCSP rules, an assignment category that changes during a break in service is reported only when the employee returns from the break.

Leavers and Transfers to Other Civil Service Organizations

The Service History record triggered as a result of an employee termination or the ending of an assignment uses the employee’s current Service History record, reporting the termination date (or assignment end date) as the record end date together with their leaving reason. The start date and start code from the current Service History record is reported in the leaver’s record.

For example, Sarah is in the Alpha scheme and on maternity leave. Her statutory maternity pay has ended and she went on to unpaid maternity leave as of 11 April. Sarah decides not to return to work and her employment is terminated on 10 July. Her termination Service History record includes:

Leaver’s Termination Service History Example

REPORT TAG	REPORTED VALUE	DESCRIPTION
STARTDTE	11/04/19	The start date of Sarah’s current Service History record before her termination. (The date on which her maternity pay dropped to zero pay.)
STARTCDE	MN	The start code of Sarah’s current Service History record before her termination. (The code for unpaid maternity leave.)
SVRSN	5	Sarah was terminated with action End Assignment and action reason Worker Request. This action reason was mapped to MyCSP end reason 5 – Resignation.
ENDDTE	10/07/19	Termination date

For more information on mapping termination, end assignment, and end employment terms actions and reasons to MyCSP leaving reason codes, see Termination Action and Reason Mapping to Service History End Reasons

Absences

An absence only triggers a service record if the absence type is associated with a valid legislative grouping code. If the absence is child-related or sick leave (such as maternity or shared parental leave), the rate of pay is an additional factor that determines if a service record is required and under which codes the absence is reported. See How Child-Related and Sickness Absences Impact the Service History File for further examples.

If consecutive reportable absences share the same Service History start code, for example, an employee goes from maternity leave (statutory maternity pay, start code MS) to shared parental leave (also statutory maternity pay, also start code MS), then one Service History record is generated to cover the entire period when they were paid statutory maternity pay. If the consecutive absences were associated with different Service History start codes, for example, the employee went from unpaid leave (start code VN) to maternity leave at full pay (start code MF), then a Service History is generated for each absence with the respective start codes.

An absence record must be approved in order to be reported correctly in the Service History file. If an absence record has changes that are pending approval, that absence will not be reported, and in certain cases, could even cause a deletion file to be generated. The absence will be reported when it’s approved, even if it’s in the following month’s interface.

Return from Break

Return from break absences (Start Code: RB) are triggered when an end date is entered on a reportable absence and another reportable absence doesn’t start the day after the previous absence ended.

According to MyCSP rules, a service history change that occurs the calendar day after the end of the absence supersedes the return from break. For example, if an employee returning from unpaid maternity leave transfers to a Partnership scheme the day after their leave ends, a Transfer to Partnership record is required, not a Return from Break record.

Suspension without Pay

An assignment status that changes to Suspended - No Payroll triggers a service record (Start Code: XN).

Opt Outs

Manage your MyCSP pension opt outs using pensions automatic enrolment. See the Oracle Fusion HRMS (UK): Pensions Automatic Enrolment and Functional Considerations (Doc ID 2006584.1 ) for information.

Here’s a summary of different opt out scenarios and their impact on the Service History file:

Opt Out Business Scenarios

BUSINESS SCENARIO	PENSIONS AUTOMATIC ENROLMENT CARD	WHAT NEXT	MYCSP PROCESS RESULTS
Employee is automatically enrolled and opts out within one month of joining scheme. Employer permitted to refund pension contributions taken (if any).	Reason for Leaving Qualifying Scheme – Contractual opt-out Opt-Out Refund Due – Yes Qualifying Scheme Leaving Date – Same as Qualifying Scheme Joining Date	PAE process records opt out date as at Qualifying Scheme Joining Date. Benefits and Pensions card component is end dated as at Qualifying Scheme Joining Date	Employee reported as opt out as at Qualifying Scheme Joining Date
Employee is automatically enrolled and opts out after one month but before 3 months of joining scheme. Employer requests permission from MyCSP to refund any contributions taken. Employer ceases contributions but does not report employee as opt out until decision received from MyCSP. Then see below:	Reason for Leaving Qualifying Scheme - Contractual opt-out Opt-Out Refund Due – Pending Decision Qualifying Scheme Leaving Date – Actual date of leaving	Benefits and Pensions card component is end dated as at Qualifying Scheme Leaving Date to stop any further pension calculations.	See below.
Decision is received from MyCSP: Refund is due.	Opt-Out Refund Due – in correction mode, change this from Pending Decision to Yes. Qualifying Scheme Leaving Date – in correction mode, change this to the same as the Qualifying Scheme Joining Date.	In correction mode, remove end date of card component on Benefits and Pensions card and end date this as at Qualifying Scheme Joining Date.	Employee reported as opt out as at Qualifying Scheme Joining Date
Decision is received from MyCSP: No refund is due.	Opt-Out Refund Due – change this from Pending Decision to No.	Benefits and Pensions card component already dated as at Qualifying Scheme Leaving Date; no further action required.	Employee reported as opt out as at Qualifying Scheme Leaving Date

Note: Opting in and out of a qualified Civil Service pension scheme uses the “contractual opt-in” and “contractual opt-out” reasons; the non-specific “opt-out” and “opt-in” reasons are not used in MyCSP.

Scheme members who opt out after the permitted opt-out period has ended are considered to have left the scheme (not opted out) and the Reason for Leaving Qualifying Scheme should be “Left Scheme” .

Note: When a person opts out of a Partnership scheme, the Service History file reports the details of the scheme they were eligible to join (and may or may not have enrolled in) prior to enrolling in Partnership. You record that in the scheme Eligible to Join field on the PAE card. See Interaction with Pension Automatic Enrolment (PAE) Processes for more information.

Pensions Automatic Enrolment Left Scheme Report

An opt out within a month is reported in the Pensions Automatic Enrolment Left Scheme report as having left as at Qualifying Scheme Joining Date. An opt out after 1 month is considered, from a PAE perspective, as leaving the scheme (without refund) and is therefore reported as at Qualifying Scheme Leaving Date.

If it is later confirmed that the member was entitled to a refund and therefore, from a MyCSP perspective, opted out as at Qualifying Scheme Joining Date, the fact that they are listed as having left the scheme as at Qualifying Scheme Leaving Date conforms with PAE regulations; the MyCSP refund process is outside of the legislative requirements of pensions automatic enrolment.