Payroll user guides
Payroll desktop
Release v2.52
COVID-19 changes to SSP
Class 1A NI contributions
CEO Pay reporting
Termination awards
New rules for low-emission cars
Hours and Days in Payroll
Employment Allowance changes
Parental Bereavement Pay
History generation for Pensions and Pay groups
IR35 Working rules
Holiday pay calculation changes
Changes to Pension re-enrolment
Printer names on RDP
Plain Paper P45s
Release v2.56
2.56 Release Report
Payroll version 2.56 Upgrade Instructions
Health and Social Care Levy message on the payslip
Support for the Alabaster ruling
Automatic recalculation of SMP,SPP etc
New NI Letters for freeports and veterans
HMRC gateway password saving
Release v2.58
Release v.2.61
Rolled up holiday pay for irregular hours and part-year workers
Statutory Paternity Pay (SPP) legislative update
Company Sick Pay (CSP)
Diary Changes for CSP
Working Patterns
Year End Guides
OVERVIEW - Payroll desktop version 2.58
DOC A - Payroll 2.58 Upgrade Instructions
DOC B - Payroll 2.58 Upgrade notes
DOC C - Copy Year-End Instructions v2.58
DOC D - Payroll v2.58 RTI Year-End Procedure
Functionality
Adding a New Pay Element
Pay Rises
Modifying Custom Reports
Company and Employee Audit Trail
Maintaining Users and User Profiles
Automatic Pension Re-enrolment
Maintaining Elements and Relationships
Change NI Table Letter
Loans and Save Schemes
Adding additional fields to payslips
Maintaining Display Views
Viewing RTI Submissions
Standard (STD) and Live Pay Period fields
Average Holiday Pay
Changing Pay Groups
Elements of Pay
Errors and Troubleshooting
Payroll web
Manage Employees
Creating an Employee
Editing an Employee’s details
Viewing an employee’s payslips
Making an Employee a Leaver
Printing Employee P45s
Emailing Employee P45s
Change Employee NI Letter
Running Payroll
Starting a Payroll Cycle
Edit Pay Elements
Benefits
Cost Breakdown
Run Checks
Emailing Payslips (as part of running a payroll)
BACS/RTI
View Summary and close payroll
Restart Payroll cycle
Adding and Removing Employees from Payroll
Statutory Payments
Statutory Payments
Statutory Maternity Pay (SMP)
Statutory Sick Pay
Import Sickness
Company Sick Pay (CSP) web functionality
Statutory Paternity Pay (SPP)
Import of Sick Pay information
HMRC Messages
Month End
Permissions
General System Use
Reporting
Emailing in the web application
Importing Data
Backing up Data in Payroll
Product Hub
Release notes
Release 5.8
Release 5.7
04/07/2024 Payroll web 5.6 - desktop 2.61.4 release
16/04/2024 - Payroll - desktop v2.61.3.1 hotfix
OneAdvanced Payroll desktop version 2.61.3
Payroll - Year End - desktop v2.61.1 web v5.4 Release Report
Payroll: desktop version 2.58.2
Payroll desktop version 2.58
Payroll: web version 5.3
Payroll: desktop version 2.56.2
Payroll: desktop version 2.56.3
Payroll: web version 5.2
Year End Activities
Year-End Overview
Upgrading your system
Backing up your data
Running the installation program
Converting data directories that are not under the WINPAY directory
End of year overview (formerly RTI year-end procedure)
Last submission of the year
Print RTI amendments
Linked Companies
Year-end procedure
Update all payrolls and run check report
Copy year-end data instructions
EPS and final payments to HMRC
Print P60s
Starting the new tax year
Company year-end
Employee year-end
How to correct for a previous year
Clearing historical data (optional)
Scenarios
- All Categories
- Payroll user guides
- Payroll desktop
- Elements of Pay
- Payroll Relationships
Payroll Relationships
Updated by Karishma
Introduction
There are especially reserved employee record fields used by Payroll for carrying out specific, built-in functions. These are described as system fields. Other fields, such as the ones you can define yourself, are not regarded in any special way by Payroll. This means that you can set up your own fields. However, a problem exists. For example, if the user defines a numeric field called BONUS, this will not automatically add any bonus values to gross pay when the employee is paid. It simply creates a place for a numeric value to be stored. In order for it to be treated as an element of pay you need to set up a 'payroll relationship'.
Payroll relationships define how the employee record fields are to be treated during the payroll cycle (e.g. for a BONUS field you will need to set up an 'addition' relationship so that any bonus values are added to gross pay). There are several different types of payroll relationships that you can define. These are as follows:
Addition: any field to be included in gross pay. You can define whether the amount is taxable or subject to National Insurance. It is possible to define whether the amount is to be included in the total pay for the employee's pension calculation.
Deduction: these are subtracted from gross pay after the calculation of tax and National Insurance. A deduction that is to be made before tax and National Insurance are calculated, should be defined as an 'addition' but given a negative value. You can label deductions as pension payments, which means they are subject to tax relief.
Deduction from gross: items subtracted from gross pay such as a salary sacrifice pension.
Expenses: these are added to net pay. They are not counted for tax and National Insurance purposes.
Benefit in kind: this is a value used in calculating tax and National Insurance but which is not actually added to the employee's pay. This field is treated as if it were both an addition and a deduction.
Loan: this allows an amount of money (the outstanding balance) to be paid by means of regular payments. A loan field can be decreased or increased as required. You can also specify whether or not the balance is allowed to go negative. Loans are really a way of maintaining a balance (e.g. holiday pay remaining) and have no effect on pay unless linked with another relationship, such as an addition.
Rate of pay: this type of field allows you to multiply two fields together and put the result into a third employee record field. This gives the facility for a number of rate of pay type calculations (e.g. hours worked multiplied by rate of pay).
To-date: these allow totals of fields to be calculated over several pay periods. They can be set to zero at the end of the tax year or as required at the end of any user defined period. An example of a period-to-date field would be a savings scheme.
Warning levels: these allow a monetary 'limit' to be placed on the calculated value of a field. The system does not actually limit the value, but warns you when this limit is exceeded.
Many of the basic relationships required in Payroll will have been set up previously. However, there are facilities to extend and customise these relationships to match your own requirements.