Negative result when clocks are delayed

When clock data is delayed or incomplete at the time clock results are processed by a scheduler, you can see unexpected negative values (for example, ‑0.01) in Time & Attendance outputs.

This typically occurs because the scheduler processed an earlier, partial set of clocks, and later‑arriving swipes were never re‑processed.

Symptoms

• Negative totals such as ‑0.01 appearing in timesheets or clock results.

• Entries missing expected clock swipes for affected days.

• Discrepancy between imported clocks and processed results for the same period.

Why this happens

• Delayed clock imports: Some swipes arrive after the scheduler has already run clock processing for that period.

• Scheduler offset behavior: Schedulers are often configured with an offset (for example, “process the previous day”). If late swipes land after that window, they are not included the next time the scheduler runs.

• Partial processing: The initial run processes incomplete clock data, producing small negatives like ‑0.01. Later, the missing swipes import successfully, but they are not re‑processed unless you trigger it manually.

Resolution

Follow these steps for each affected day once the missing swipes have arrived:

1. Reset Clock Data for affected days (Time & Attendance > Reset Clock Data):

2. Process Clock Data (Time & Attendance > Process Clock Data)

Tips to prevent recurrence

• Ensure your scheduler offset matches the timing of your clock import feeds so late swipes are still within the processing window.

• If clock imports can be delayed, schedule processing after import completion or run manual re‑processing for impacted dates.

• Periodically audit clock import logs to detect delays and confirm all expected swipes have arrived before scheduled processing.

• For multi‑day delays, consider processing a date range rather than a single day to catch late arrivals.