You can understand why missed clockings show up for employees due to the timing of the overnight calculation job or an uneven number of clock times. This guide explains these scenarios and how the system handles them.
Why missed clocking appears after an employee clocks out
The overnight calculation job runs between 1am and 2am each day. At this time:
The employee may only have clocked in but not yet clocked out.
This causes the system to generate a missed clocking because it sees only one clock time.
The calculation job runs again the following night. By then, it will detect the employee’s clock out (for example, at 4:00 am) and calculate the hours worked correctly.
Missed clocking caused by uneven number of clock times
Another reason for missed clockings is if there is an uneven number of clock times (for example, one clock in and no matching clock out).
The system requires an even number of clock times to match clock ins with clock outs.
If there is an uneven number, a missed clocking will be generated.
In this case, the latest clocking entry should be reviewed and possibly removed to resolve the issue.
📌Note: Missed clockings caused by overnight processing will automatically correct after the next calculation run. Manual correction is only needed if there is an unmatched clock time.