A user's working pattern is extremely important; because the users work pattern data is:
Exclusively referenced to determine the divisor for leave balance deduction calculations (e.g. fractions of Weeks [e.g. for Annual Holidays] and/or fractions of Days [e.g. for Sick Leave]).
If the data is not present or not up-to-date; then the deduction of leave balance related to a timesheet shift entry, may be calculated incorrectly.
You need to set a users work pattern and keep these records up-to-date. We broadly recommend a periodic review for all user's working patterns in your account - to ensure accuracy of the records.
You can review work patterns for all your users/employees by running the Employee Details Report, and display the "Advanced Work Hours" column, this will present the hours set for the user; in the report output.

Example: A user works an 8.00 hour day, Monday - Friday; but in the past worked an 8.00 hour day Monday - Thursday (Fridays off). Their work pattern was not updated when they started working Monday - Friday and Tempus had this outdated configuration set. A public holiday falls on a Friday and the users timesheet is populated (correctly) with "Public Holiday Not Worked" timesheet entry for the 8.00 hour day on that Friday - which they would have otherwise worked.
In the above scenario, despite the timesheet stating that there is 8.00 hours to be processed for the given (public holiday) Friday; because the users work pattern is set where they do not ordinarily work on the Friday - Tempus will nullify the earnings at the pay run level based on the outdated configuration.
This has the potential to cause an underpayment. The above example intends to underline the importance of keeping a users work pattern data accurate.
If you need to update A user's working pattern, or are having difficulty in understanding what is currently set, please reach out to our support team who will aim to assist you on this matter.