Why does a Time Tracker balance change without transactions?

Updated by Daniel Sjögren

If a Time Tracker changes suddenly, it’s usually due to schedule items existing in previous time periods that have not yet been transferred to payroll.

A Time Tracker will count the last updated period and 60 days backward in time, counting from today's date. This means that if you have any items within the past 60 days from the current day (or the day currently displayed in the time card) that have not been transferred to payroll, your Time Tracker will display the incorrect amount of hours.

To resolve this, please make sure to do a definitive transfer to payroll in order to update. Afterward, your Time Trackers should display the correct amount of hours. 

To be clear, a definitive transfer to payroll, also sometimes referred to as a hard lock of the Schedule and is not the same thing as locking your schedule from the Schedule view. Simply locking your schedule will only prevent changes from being made to shifts and punches, but will still affect the Time Tracker balance.
Why 60 days?

The 60-day interval is designed to ensure optimal system performance and calculation accuracy. Our calculation engine (LABM) supports both Time Trackers and Payroll. When payroll (TTP) isn’t run frequently, LABM must process larger datasets for on-demand calculations, increasing system load and potentially impacting performance. Therefore, we have a limit in the backend that can only refer to information up to 60 days in the past.

Running payroll at least once every 60 days creates a "snapshot" of calculation outcomes in our database. This snapshot allows LABM to reference pre-calculated data and focus only on recent updates.

Example

Vacation days count all days from the actual day and back in the time if the salary period is hard locked (otherwise up to 60 days) and even take into account up to 30 days forward.

How Did We Do?