Clocking devices record when employees start and finish shifts, take breaks, or move between jobs. They can be physical terminals, cards, PINs, mobile apps, web forms, or biometric systems. For a payroll manager, the important question is not simply whether a clock entry exists. It is whether the organisation can turn those entries into accurate, approved, and explainable pay.
This module explains how to manage clocking data in business as usual payroll. It covers the daily process, common exceptions, payroll checks, system controls, and the evidence needed when a payment is challenged. The examples assume a New Zealand workplace. Always apply the employee's agreement and current law to the facts of the case.
A clocking device normally captures an employee identifier, a timestamp, an event type such as clock in or clock out, and sometimes a device or location. It does not know whether an employee started work before clocking in, stayed after clocking out, worked through a meal break, or clocked in early for personal reasons.
For example, an employee may be rostered from 9:00 am to 5:30 pm, clock in at 8:53 am, and clock out at 5:48 pm. The roster gives the planned hours. The clock entries show events at the device. A manager must establish what work actually occurred. Payroll then applies the correct pay rules to the verified time.
Do not assume that the roster, the raw clock entries, and the payable hours will always match. A difference is a question to investigate, not an automatic error or an automatic entitlement.
Rostered time is the planned shift. It helps explain expected attendance but may not reflect what happened.
Raw clock events are the original records captured by a device or app. Keep them available even when later corrections are made.
Approved timesheet is the reviewed account of actual work, breaks, leave, and any changes. It should show the supporting reason and approval.
Payroll result is the hours and earnings sent to the payroll engine, split into the correct pay codes. An approved timesheet can still produce the wrong pay if the mapping or pay rule is wrong.
The employee should clock in and out as instructed, record breaks where required, and report missing or incorrect entries promptly. They should have a practical way to explain a missed clock, a break that did not happen, or work done outside a rostered shift.
The manager confirms what happened on the shift. They review unusual entries, check employee explanations, approve corrections, and ensure the approved timesheet reflects actual work. An approval should be based on evidence, not simply on what was rostered or budgeted.
Payroll checks completeness, pay codes, calculations, exceptions, and the transfer into payroll. Payroll should challenge unclear or inconsistent approvals. It should not invent start and finish times to clear an exception queue.
The payroll manager owns the control process: deadlines, exception reports, access, reconciliation, escalation, and periodic review. They ensure there is a documented way to correct mistakes after a pay run and that repeated issues lead to a system or process fix.
HR helps interpret employment agreements and policies. Rostering owns planned shifts and changes. IT or the system administrator maintains devices, employee mappings, integrations, access, and technical logs. These teams must agree which system is the source of truth for each data item.
Document the full path: clocking device or app, time and attendance platform, roster and manager approval, export or API, payroll engine, payslip, and archive. At each step, ask whether records can be changed, filtered, rounded, combined, or rejected.
Record the owner of each interface, the timing of transfers, the file or batch identifier, and what happens when a transfer fails. A successful upload message alone does not prove that every employee and every hour reached payroll.
The same person must have the correct identifier in each system. Check employment status, start and end dates, manager, job, site, cost centre, pay category, and effective dates. Avoid matching people only by name. Where an employee works in more than one job, confirm that time can be assigned to the right job and pay rate.
Confirm that devices use the correct local time zone, keep accurate time, and handle offline events. Test daylight saving changes, shifts crossing midnight, and clock events entered on different devices. Define how an offline batch is imported and how duplicates are prevented when a device reconnects.
Document rules for rounding, grace periods, breaks, minimum paid time, extra shifts, overtime where agreed, allowances, public holidays, and job changes. Each rule needs an owner, approval, version, and effective date. Test a rule change before it reaches a live pay run.
A daily review prevents a large backlog at payroll cut-off. Look for employees with no clock events, missing in or out events, duplicate punches, reversed events, unusually long or short shifts, overlapping shifts, and records from offline devices. Check whether a person marked absent is actually on approved leave.
Assign each exception to an owner and record its status. A useful status sequence is new, awaiting employee information, awaiting manager approval, ready for payroll review, resolved, and carried forward for investigation. Keep an ageing report so unresolved items do not disappear.‘
Ask what time the employee actually worked, whether a break took place, whether work was performed before or after the roster, and whether the employee changed jobs or sites. Use the employee's account, manager confirmation, roster, work orders, system records, and other appropriate evidence. No single source should be treated as infallible.
A correction should show the original event, the corrected value, the reason, the person who requested the change, the approver, and the date and time of approval. If the system cannot preserve this history, export or otherwise retain the underlying events and the correction log. Avoid silent edits.
Check the employee ID, agreement, pay category, job, site, local date, and relevant roster. Confirm whether a shift crosses midnight, a public holiday, or a daylight saving change.
Pair clock in and out events carefully. Investigate a missing event rather than defaulting to the roster. An early arrival or late departure is not automatically work, but actual work cannot be removed simply because it fell outside the roster or was not approved in advance.
Check whether paid rest breaks and unpaid meal breaks were actually taken, and whether a meal break was interrupted. A system's automatic 30 minute deduction is a calculation rule, not proof that the employee stopped working. Apply the current New Zealand break requirements and any better terms in the agreement.
Separate ordinary work, agreed overtime or extra hours, public holiday work, different jobs, allowances, paid breaks, unpaid breaks, and leave. For a shift across midnight, identify the hours that fall on each calendar day. Do not infer public holiday entitlement solely from the shift's start date.
Check the employee's gross pay against applicable minimum entitlements for all hours worked, including for salaried staff. Compare the approved timesheet with the hours and pay codes that reached payroll. Escalate an unclear contractual or legal interpretation before final approval.
Ask the employee for the time and reason, and obtain manager confirmation. Compare the explanation with the roster, nearby punches, work records, and any relevant access logs. Enter the verified time with a reason code and retain the approval. Never fill the gap from the roster without checking whether the roster reflects actual work.
A device may send the same event twice after reconnecting, or an employee may press the wrong button. Identify the duplicate or incorrect event, preserve the raw record, and show which events were excluded from the timesheet. Check the interface for repeated batches if the same pattern affects several people.
Determine whether the employee was working, required to prepare or close down, waiting on site without working, or present for personal reasons. If work occurred, assess and pay it under the applicable rules. Address any failure to follow an overtime approval process separately from the factual question of whether work occurred.
Ask whether the employee stopped work for the full break, took a shorter break, or was called back to work. Correct the timesheet and pay where necessary. Repeated missed breaks should be escalated to operational management because the issue may involve both pay and the ability to take required breaks.
Check the time spent in each job and the dates on which each rate applies. Do not apply a single rate across the whole shift merely because the clocking system has only one employee ID. Reconcile job transfers against the approved timesheet and payroll codes.
Use a controlled manual timesheet while the device is unavailable. Require an employee declaration and manager approval, then compare the manual entries with the recovered device data. Investigate differences and prevent a recovered batch from creating duplicate paid hours.
Do not erase time that was actually worked because an approval arrived late. Record the late item, decide whether payroll can still process it in the current run, and use the documented correction or additional payment process if needed. Link the correction to the original period and tell the employee what has changed.
Sample long shifts, busy service periods, single coverage roles, and employees with frequent corrections. Compare recorded breaks with employee and manager accounts. Monitor how often automatic deductions are reversed. A high reversal rate points to a process or configuration problem.
Distinguish a display format from the rule used to calculate pay. Test cases just before and after a shift start and finish, and check the cumulative result across many shifts. Keep unrounded raw events. A rule that repeatedly removes actual work time can create underpayment risk even if each single difference looks small.
Pay at least time and a half for hours actually worked on a public holiday. If the holiday is an otherwise working day for the employee, an alternative holiday may also be due. Split an overnight shift at midnight and assess each part. The otherwise working day test depends on the employee's work pattern and circumstances; the device cannot decide it by itself.
A fixed salary does not remove the need to understand hours worked. Reliable records help test minimum wage compliance and public holiday payments. Review unusually long hours and the salary calculation over the relevant pay period under the current rules.
Clocking data is personal information. Restrict access to people who need it and set clear purposes and retention rules. Fingerprint or facial recognition systems require a specific privacy assessment under New Zealand's Biometric Processing Privacy Code 2025. Involve the privacy officer before introducing or materially changing such a system. Do not transfer biometric templates or detailed location histories into payroll without a defined need.
Confirm the period and employee population. Review outstanding exceptions, pending approvals, leave, overnight shifts, public holidays, and records changed after initial approval. Save a snapshot of the approved source data and record employee count, record count, and total hours.
Compare the source and payroll counts and totals. Identify rejected rows, unmapped pay codes, missing employees, duplicates, and differences caused by legitimate transformations. Explain each difference. The reconciliation should show source totals, imported totals, excluded records, and approved adjustments.
Review unusual total hours, gross pay movements, zero pay for active employees, negative hours, minimum wage risks, public holiday premiums, and manual overrides. Use an independent reviewer for high impact corrections or changes made by someone with broad access. Record the review and any unresolved items explicitly.
Archive the raw events, approved timesheets, exception log, interface batch, reconciliation, payroll output, approvals, and later corrections in a retrievable form. New Zealand employers must retain wages and time records and holiday and leave records for six years. A device log by itself may not contain every detail needed in the statutory records.
A payroll manager should review trends across periods. Track missed punch rate, manual edit rate, unresolved exceptions at cut-off, late approvals, automatic break reversals, device downtime, interface failures, and correction payments. Break results down by site, team, and device.
If one manager regularly approves identical finish times despite varied raw entries, examine the reason. If one device repeatedly loses records, fix the device or integration. If employees regularly report missed meal breaks, review staffing and operating practices. The goal is to improve the accuracy of work records and pay, not to discourage staff from reporting time worked.
An employee clocks in at 8:00 am and out at 5:00 pm. The system automatically deducts 30 minutes, producing 8.5 hours. The employee says they worked continuously during an urgent customer incident, and the manager confirms this.
Retain the raw events and the explanation. Check whether there was any other period when the employee was not working. If the employee worked throughout the nine hours, remove the incorrect deduction and pay the verified hours under the applicable rules. Separately review the missed break and whether similar shifts have been affected.
An employee works from 11:00 pm to 7:00 am. The second calendar day is a public holiday. They take a genuine unpaid meal break from 3:00 am to 3:30 am.
The first calendar day contains one hour of work. The public holiday contains 6.5 hours of work: midnight to 3:00 am and 3:30 am to 7:00 am. Apply at least time and a half to the public holiday hours, subject to the applicable agreement. Assess separately whether the public holiday was an otherwise working day and whether an alternative holiday is due.
An employee is rostered until 5:00 pm but has no clock out. They say they worked until 7:00 pm to finish stocktake. The manager says the extra time was not approved, while a work record shows a submission at 6:50 pm.
Investigate the actual end time with the employee and manager and retain the work record. Pay verified work under the applicable agreement and legal minimums. The manager and HR can address the separate question of approval and future scheduling.
The roster says 9:00 am to 5:00 pm, but the employee clocked out at 6:10 pm. What should payroll do?
Answer: Obtain the employee's and manager's account of what happened, verify actual work, and apply the agreement and pay rules. Neither the roster nor the clock event alone settles the question.
Can an automatic meal break deduction be used if nobody has confirmed that the break was taken?
Answer: It may be a system starting point, but it is not proof of a break. The organisation needs a way to identify and correct breaks that were missed or interrupted.
The time system reports 2,010 hours and payroll imports 1,995 hours. Is a successful import notification enough?
Answer: No. Explain the 15 hour difference by employee and pay code, including any legitimate exclusions or rejected records, before approving payroll.
An employee works two hours on a public holiday that would otherwise have been a working day. What needs review?
Answer: Pay for the actual public holiday hours at no less than time and a half and assess the alternative holiday entitlement. Review the specific facts and agreement.
Employment New Zealand, Record keeping.
Employment New Zealand, Hours of work.
Employment New Zealand, Rest and breaks.
Employment New Zealand, Working overtime or extra shifts.
Employment New Zealand, Public holiday pay and Alternative holidays.
Employment New Zealand, Minimum wage changes from 1 April 2026.
Office of the Privacy Commissioner, Biometric Processing Privacy Code 2025.
.png)
.png)