Run the Generate MyCSP Interface Process (Cutover and Monthly Files)

The Generate MyCSP Interface process generates all cutover and monthly files to include eligible employees’ details, either as of the cutover date, or for the selected reporting period for monthly files.

To run the MyCSP interface process for cutover or monthly files:

1. Use the Client Groups > Payroll > Submit a Flow task. Select your legislative data group and Generate MyCSP Interface.
2. Enter the details as shown:

   Generate MyCSP Interface

   FIELD	DESCRIPTION
   Payroll Statutory Unit	List of PSUs in the legislative data group.
   Effective Date	Defaults to the last day of the previous calendar month, based on system date. Override this to the cutover date for cutover files.
   Paypoint Code	Select the Paypoint Code. The list contains the Paypoint Code for the PSU selected earlier. If you additionally specified a Paypoint Code at legal employer level, that is shown too.
   Submission Type	Cutover or Monthly. Defaults to monthly but can be overridden for cutover submission.
   Final Submission	Defaults to No. Select Yes – final for year if the payroll year has been closed and you expect no further changes that will affect Payment History files.
   Process Configuration Group	List of process configuration groups. The parameters from the default group are used if left blank.

Note: Remove the .txt file extensions from the files created prior to submission to MyCSP.

Final Submission for Year

Select the Final Submission parameter and submit your final files for the scheme year when you expect no further changes that will impact Payment History files. The YRCLOSE field in the Control Totals file is populated to include the closed scheme year.

Do not resubmit a Payment History file for a closed scheme year. This will trigger MyCSP error reference 30035.

Generate the Five-Day Year-End Pension Input Period (PIP) Report

MyCSP requires the reporting of earnings and pension contributions for the period 1 to 5 April, the Pension Input Period (PIP). The PIP file is generated automatically in the application, but the submission of the data to MyCSP is a manual task that is external to the application.

The PIP file generation is a subtask of the main Generate MyCSP Interface flow, Generate MyCSP Interface April Five-Day PIP File. This subtask creates a .csv file, filename PPPPYYYYPIP (where PPPP = Paypoint Code). When the effective date of the flow is April, this .csv is populated with Payment History information for all members of Alpha. (A blank file is created when the effective date is not April.)

The amounts reported in this file are 5/30 of the Payment History April figures. Proration is adjusted for members who were hired or terminated during April. The calculation is the number of days they worked during the PIP period divided by the number of days they worked in the whole of April.

For example:

HIRE DATE	TERMINATION DATE	PRORATION FACTOR
3 April	N/A	3/28
Before 1 April	During April: 3 April 20 April	3/3 = 1 5/20
After 5 April	N/A	N/A. No record is generated for a person who was hired during April, but after 5 April.

The structure of the generated .csv is aligned with the column layout in the manual spreadsheet provided by MyCSP. This enables you to copy and paste the contents of the generated .csv file into the MyCSP manual spreadsheet that you can then send to MyCSP.