This Knowledge Base article will show you how to add Statutory Sick Pay (SSP) in the Accord Payroll system. It provides guidance on where to locate the SSP settings and how to ensure the correct configuration is applied for accurate payroll processing.
Entry of SSP
- Click on Employee Code button, select desired employee
- Click on Transactions tab
- Click on the SSP button
- Enter the PIW (Period of Incapacity for Work) start date and end date
- Click Calculate button
- If prompted enter average weekly (AW) earnings and ensure Override AWE auto calculation box is ticked
| Note: You may be prompted to enter average weekly earnings if the employee does not have period records for the previous 8 weeks on weekly payrolls or previous 2 months on monthly payroll. Normally it only happens for recent starters or when you just started using CIPHR Payroll. |
- Click on the Update button to continue. The SSP period will be shown in the employee table of SSP periods
The next time you click on the SSP button for this employee the screen above will be shown. To enter a new period of incapacity for work (PIW) for this employee click on the New PIW button.
The payment of SSP will be paid to the employee and the recovery due (if applicable) will be automatically taken off the liability of Tax and NIC due from the Company for that particular tax month, which will be shown on the P32 Yearly Totals report automatically. The amount of SSP will be printed on P35 Continuation Sheet report.
| Note: The way of entering SSP payments described above uses CIPHR Payroll functionality to calculation SSP automatically. If you prefer to calculate SSP manually you can enter SSP payment wage type 210000 or 051000 on the Transactions page of the employee form as you would enter any other one off payment. The 051000 wage type should be used if you need to automatically reduce basic pay by the amount of SSP paid. Regardless of the way you have chosen to enter SSP, the SSP recording and reporting will be similar and is done automatically. |
Footer
Comments
0 comments
Article is closed for comments.