Skip to main content

Missed clocking appearing for employee despite having clocked in and out

Why missed clocking notifications may appear even when an employee has clocked in and out, and how the system corrects these cases.

Written by James Pardy

You can understand why missed clockings show up for employees due to the timing of the overnight calculation job, an uneven number of clock times, or a mismatch between how clock-in and clock-out records were entered. This guide explains these scenarios and how to resolve 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.


Missed clocking caused by a mismatch between clocking entry types

A missed clocking can occur when the clock-in and clock-out records for the same day were entered differently — for example, one was added automatically by the system and then edited on the timesheet screen, while the other was entered manually. Because the two records were created in different ways, the system treats them as separate and unlinked entries, which results in a missed clocking pay code.

To resolve this, you have two options.

Option 1: Delete and re-enter the mismatched clockings

This resolves the issue for the affected days immediately.

  1. Delete all the clock-in entries for the affected days.

  2. Manually re-enter the clock-in times. Entering them the same way as the clock-out records ensures they match.

  3. Recalculate attendance on the timesheet.

Option 2: Turn off the Work Pattern clocking match requirement

This changes the configuration so the system no longer requires clock-in and clock-out records to be the same type. Use this option if the issue occurs regularly due to how clockings are entered in your organisation.

  1. Go to CoreTime > System Params > Work Patterns.

  2. Open the affected employee's work pattern.

  3. Locate the Work Pattern toggle (or the equivalent clocking match setting).

  4. Turn the setting off.

  5. Select Save.

  6. Recalculate attendance on the timesheet.

📌 Note: Option 2 applies to future timesheets. For any days that have already been affected, use Option 1 to correct the existing missed clocking entries. 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

Did this answer your question?