Symptoms worth suspecting
Consistent late arrivals, impossible timestamps, and a month that went wrong with no system change.
Home / ZKTeco clock troubleshooting
DEVICE TIME
ZKTeco clock drift and wrong punch times.
The device is the source of truth for time in your attendance data, and almost nobody checks it. A drifted clock produces data that is internally consistent, plausible and quietly wrong — the worst kind of bug to own. Troubleshoot in the order below.
What Flowwkkr includes
Explore the product area in more detail and see how it fits into the wider Flowwkkr HR workspace.
Fastest diagnostic first
Compare device time to a known-good clock, then compare again ten minutes later to detect drift.
Time zone and DST
A device left set to daylight saving shifts every punch by an hour for part of the year. Pakistan does not observe it.
Why drift goes unnoticed
The error is consistent, so the report looks coherent. It usually surfaces at payroll, not attendance.
Do not re-key the month reflexively
Fix the clock, measure the actual scope of the error, then correct through an auditable adjustment.
Stop it recurring
Enable NTP sync, add device time to a monthly checklist, and re-check after any outage.
What ZKTeco Clock Troubleshooting actually does
The biometric device is the source of truth for time in your attendance data, and almost nothing checks it. A device whose clock has drifted produces attendance that is internally consistent, plausible and quietly wrong, which is the worst kind of bug to own. This is a practical troubleshooting page, in the order the problems actually appear.
ZKTeco Clock Troubleshooting is the process of identifying and correcting time errors on a ZKTeco or other biometric terminal, where incorrect device clocks corrupt every late-arrival, overtime and payroll calculation that depends on them.
Symptoms that point to a clock problem
- Late arrivals appearing even though staff arrive on time
- Overtime calculated as consistently higher, or lower, than expected
- Punches timestamped at an impossible time, such as 03:00 for a 09:00 shift
- Attendance that was correct last month and is wrong this month, with no system change
- Devices disagreeing with each other by different amounts
Diagnostic order, fastest first
Work down this list. Most cases are resolved in the first two steps, and none of them require restarting anything.
| Step | Check | If it is wrong |
|---|---|---|
| 1 | Device time vs a known-good clock on the same network | Set the device time manually to fix today |
| 2 | Device time zone and daylight-saving setting | Correct the zone before anything else |
| 3 | Is NTP time sync enabled and the server reachable? | Enable NTP sync, or schedule a manual check |
| 4 | Has the device lost power or battery for a long period? | Expect a reset, and re-verify after the next outage |
| 5 | Does the agent PC time agree with the device? | Align them; a mismatch makes diagnosis harder |
| 6 | Firmware version on the device | Update if support advises; note it before and after |
Clock drift: why it happens and why nobody notices
Devices with no network time source free-run on an internal oscillator. That oscillator is accurate to a small tolerance when new and drifts over months, and a device left unpowered or unmonitored drifts faster.
The reason it stays hidden is that the error is consistent. Every punch is wrong by roughly the same amount, so the attendance report looks coherent. Nobody notices until a single employee complains that their check-in time is impossible, or until an overtime figure reaches a level finance refuses to accept.
Time zone and DST settings
Two settings cause most of the badly wrong timestamps. An incorrect time zone puts every punch hours out in a way that is obvious once seen. A daylight-saving toggle left on in a country that does not observe it shifts every punch by an hour for part of the year, which is far harder to spot because it appears and disappears.
Pakistan does not observe daylight saving time, so a device configured for it will behave incorrectly. If timestamps look exactly one hour out for part of the year, this is the first thing to check.
Preventing it from recurring
The fix is not a one-time correction, it is a recurring check. Three low-cost habits cover almost every case.
- Enable NTP sync against a reliable internal or public time source
- Add device time to a monthly checklist, alongside checking the agent is running
- Record the time immediately after any power outage or firmware update
- Re-check after a long shutdown, particularly over a site holiday
Frequently asked questions
How do I check whether my ZKTeco device clock is correct?
Compare the time shown on the device against a known-good clock on the same network, ideally one that syncs automatically. Compare them a second time about ten minutes later: if the two are diverging, the device is drifting and needs NTP sync rather than just a one-off manual setting.
Why is my attendance one hour out for part of the year?
Most likely the device has daylight saving time enabled. Pakistan does not observe daylight saving time, so a device configured for it shifts every punch by an hour during part of the year. Check the DST setting on the device and disable it.
Does clock drift affect payroll as well as attendance?
Yes. Because overtime and working hours are calculated from punch timestamps, a device clock that is two hours fast inflates working hours and therefore overtime. The error is consistent and invisible in the attendance report, so it is usually found at payroll rather than at attendance.
Should I re-enter historical attendance after fixing the clock?
Not automatically. Fix the clock first, then check whether any previously calculated records are affected. Re-keying a whole month is a large, error-prone task and is rarely necessary — confirm the actual scope of the error before doing it, and correct records through an auditable adjustment rather than by overwriting them.
Can I stop the device time drifting permanently?
Yes, in most cases. Enable NTP time sync on the device against a reliable time source on your network, and check the time as part of a routine monthly visit. Drift is a maintenance issue, not a hardware fault.
See it against your own requirements
Bring your device model, shift pattern and employee count. We will confirm fit on a private 2-hour demo.
See Flowwkkr in action
Request a private 2-hour live demo and explore the HR workflow.