Skip to main content

Days due and days paid fields explained

Information on the Days due and Days paid fields.

H
Written by Harry Ledger
Updated over 2 months ago

Days Due

The value in this field is accumulated from sickness absence data pulled from the SelectHR system.

Days due is a cumulative value of all historic sickness absence records for the employee across their entire absence history, not just the current holiday year.

It is calculated by establishing the number of SSP qualifying days for each of the employee's sickness absences, and then adding them together to get the total; the total is the value you see in days due.

An easy way to see the days due for an employee is to run an export of data against their absence history record by following these steps.

  1. In the Admin Tool, click Import/Export data.

  2. Click Create an export definition.

  3. Click Select the data to export.

  4. Change the database drop-down to SelectHR.

  5. Log in.

  6. Copy the below SQL:

  7. Select    Person.Snapshot.[Person Number],    Person.Snapshot.[First Name],    Person.Snapshot.Surname,    Max(Absence.[Holiday History].Year) As [Holiday Year],    Absence.AllStatistics.[SSP Days Due],    Absence.History.[Absence Start Date],    Absence.History.[Absence End Date],    Absence.History.[Total Days],    Absence.History.[Absence Type],    Absence.History.[SSP Days Due],    Absence.Person.[SSP Monday],    Absence.Person.[SSP Tuesday],    Absence.Person.[SSP Wednesday],    Absence.Person.[SSP Thursday],    Absence.Person.[SSP Friday],    Absence.Person.[SSP Saturday],    Absence.Person.[SSP Sunday]  From    Person.Snapshot    Inner Join Absence.[Holiday History] On Person.Snapshot.[Person Number] = Absence.[Holiday History].[Person Number]    Inner Join Absence.AllStatistics On Absence.[Holiday History].[Holiday History Number] = Absence.AllStatistics.[Holiday History Number]    Inner Join Absence.History On Person.Snapshot.[Person Number] = Absence.History.[Person Number]    Inner Join Absence.Person On Person.Snapshot.[Person Number] = Absence.Person.[Person Number]  Group By    Person.Snapshot.[Person Number],    Person.Snapshot.[First Name],    Person.Snapshot.Surname,    Absence.AllStatistics.[SSP Days Due],    Absence.History.[Absence Start Date],    Absence.History.[Absence End Date],    Absence.History.[Total Days],    Absence.History.[Absence Type],    Absence.History.[SSP Days Due],    Absence.History.Workflow,    Absence.Person.[SSP Monday],    Absence.Person.[SSP Tuesday],    Absence.Person.[SSP Wednesday],    Absence.Person.[SSP Thursday],    Absence.Person.[SSP Friday],    Absence.Person.[SSP Saturday],    Absence.Person.[SSP Sunday]  Having    Person.Snapshot.Surname = 'REPLACEWITHSURNAME'    And Absence.AllStatistics.[SSP Days Due] > 0    And Absence.History.[Absence Type] = 'Sickness'    And Absence.History.[SSP Days Due] > 0    And Absence.History.Workflow = 1
  8. In the top left of the export, click Options, Paste SQL from clipboard.

  9. At the bottom of the export, in the criteria section, replace the REPLACEWITHSURNAME text with the surname of the impacted employee.

  10. Click Data.

You will now be able to see all absences where SSP days due are greater than 0 (absences where no SSP days were due will not be shown).

If you copy this into Excel, you can add the values up and the total will be what you see in the days due field.


Days Paid

The days paid field is pulled from the SelectPay system, but only where your system is integrated with a SelectPay system. This value will display the number of SSP days which have been paid to this employee within the SelectPay system.

It's important to know that this value can be different from the days due field and that this is not unusual.

In situations where you have historic sicknesses imported on an employee's record that were paid out in another system, the days paid field will be a lower value than days due because they were not paid out for these sicknesses within SelectPay.

There is no way to change the value in this field manually - this field will always get its data via the integration, and so should not be amended in any way.

Did this answer your question?