Occasionally, SelectPay will list a TUPE date against an employee.
Typically this is for new starters but can happen for existing employees.
Scenarios
For new employees, the continuous service date is set earlier than the employee's start date on the appointment.
For existing employees, a new appointment is created and the Starter flag is ticked in error. This should only be ticked for an employee's first appointment or for a re-joining appointment if they have previously left.
The employee's payroll number has recently changed.
Checking the Continuous Service Date
In the Employee zone, click Details.
On the Work tab, note the continuous service date (CSD).
Click Career History.
Click All Appointments, note the start date of the first appointment.
If the CSD predates the first appointment, then this would explain the TUPE date being populated.
The TUPE date is populated in SelectPay when the CSD predates the first appointment; this confirms the employee must have been transferred from another organisation.
Checking the Starting flag on the Employee's Appointment
Open the Employee Zone.
Click Career History.
Search for and click on the employee.
If you now see the Current Appointment screen you can check Starting tick box, however you may need to click on All Appointments.
Checking for a recent Payroll number change
This may also be due to an amendment of the employees payroll number. Follow the steps below to identify if this has been amended.
From within the Admin tool select Import/export data from the Maintenance section.
Select Create an export definition.
Click Select the data to export.
Select your SelectPersist database from the Database dropdown.
Click onto the SQL tab.
Copy the code below then click on the green Options arrow and click Paste SQL from Clipboard:
Select audit.[Object Schema], audit.[Object Name], audit.[Key Number], audit.[Audit Date], audit.Action, [audit fields].[Field Name], [audit fields].[Is Text], [audit fields].[Was Text], [audit fields].[Is Date], [audit fields].[Was Date], [audit fields].[Is Number], [audit fields].[Was Number], [audit fields].[Is Decimal], [audit fields].[Was Decimal], [audit fields].[Is Boolean], [audit fields].[Was Boolean], security.users.[User Name], [audit fields].[Sent to Payroll], audit.[XML Response], security.users.[Person Number] From audit Inner Join [audit fields] On audit.[Audit Number] = [audit fields].[audit number] Inner Join security.users On audit.[User Number] = security.users.[user number] Where (audit.[Object Schema] = 'employee' And audit.[Object Name] = 'appointment history' And [audit fields].[Field Name] = 'payroll number' And [audit fields].[Is Text] = '1234') Or (audit.[Object Schema] = 'employee' And audit.[Object Name] = 'appointment history' And [audit fields].[Field Name] = 'payroll number' And [audit fields].[Was Text] = '1234')
Amend the Is and Was text numbers so they reflect the Payroll Number in question.
If this returns any results, then this may also have caused the TUPE date to be transferred to Pay.