The day closes itself.
Timesheets are not submitted. The punch rollup already has the hours. A clean week closes. A missing clock out holds the week for a human.
Part of Employee Management
The clock is what payroll is allowed to trust.
Clock in lands on the same record everything else reads. Hours are judged against her own schedule. When overtime is approved it travels into the pay run without being typed again.
- Web, kiosk and a device at the gate write the same attendance events.
- The day on the board is her local day, not UTC by accident.
- On leave is a word, not a shortfall. Unrequested overtime is not payable.
- Approved overtime reaches payroll, capped at the hours the clock saw.
Today's attendance
Lena KovacsOperations lead · Wednesday, 19 August 2026- Lena KovacsIn at 08:52On time
Kai TanakaWednesday to FridayOn leave
Nadia RahmanIn, no clock outNeeds a fix
Her day, her clock
08:52Clock in09:00Her startOn timeStill open
Read against her schedule, not a shared 9am.
Soren, 2.5h Saturday. Requested first. Paid at the hours the clock saw.
286 of 296 against patternLeave taken out of the target. Week of Monday, 17 August 2026.
The problem
Hours live in a spreadsheet until payroll finds the mistakes.
The month end reconciliation.
Timesheets in one file, the roster in another, overtime in an email thread. Someone retypes it all into payroll and hopes.
Field teams, invisible.
Who actually arrived on site, and when? Paper registers and phone calls stand in for attendance, and disputes are settled by memory.
Overtime entered twice.
Approved hours are typed into the timesheet, then typed again into the pay run. Every re entry is a fresh chance to get someone’s pay wrong.
How Time & Attendance fixes it
What Time & Attendance does on the connected record.
Live attendance board: who is clocked in, late or absent right now, across every team and location
Clock in and out on the record: web, kiosk and shift tracking write to the same employee record everything else reads
Geofenced check in: field and remote teams clock in against a location, so presence is verifiable without paper registers
Overtime flows to pay: approved timesheet overtime feeds the pay run automatically, with no re entry
Read against the schedule: overtime, recurring lateness and flexi balances are computed against each person’s actual working schedule, with the working shown
Presence on the org chart: Organo shows who is in, out or on leave the moment someone clocks in or out
A real workflow
From a clock in to a correct payslip.
- The day starts with a clock in.On the web, at a kiosk, or geofenced against a site for field teams, presence lands on the record the moment it happens, with no paper register to transcribe later.
- The live board shows now.Who is in, late or absent is visible across every team and location while it still matters, not in next week’s report.
- Lateness is judged fairly.Arrivals are read against each person’s own working schedule, so a night shift is never marked late by a day shift’s clock.
- Overtime is approved once.Extra hours are approved on the timesheet, and that approval is the one the pay run reads. Nothing is retyped, so nothing is mistyped.
- Presence reaches the org chart.Organo shows who is in, out or on leave as it changes, so the whole company works from one truthful picture of today.
One record. Nothing entered twice.
Time & Attendance does not live on an island.
Time reads the working schedules and holiday calendars already on the record, feeds approved overtime straight into Payroll, and paints live presence onto Organo and the attendance dashboards.
Why teams switch
Hours the clock recorded, not a typed hope.
Overtime is requested.
Pay happens when someone submitted an overtime request and it was approved. Approved hours are then capped at what the clock recorded. Surplus is not paid.
Presence is today.
The live board and Organo read the same punches and the same leave ledger. A sticky employee status is not attendance.
A correction writes the clock.
Approve a punch correction and the events land, the day recomputes, and open exceptions clear. Hours are not invented beside the clock.
Already connected
The clock is what payroll is allowed to trust.
Web, kiosk and a device at the gate write the same attendance events. A geofence is opt in per building. Corrections and overtime have their own queues, with a manager then People when the day is already past.
- A ZKTeco machine can push punches live. An unknown serial is refused, so the device keeps the punches until HR registers it.
- Off site review is durable. Accept or turn it into a correction. The employee is not judged until a human decides.
- Punch corrections write real events and recompute the day. They do not invent hours beside the clock.
- Lateness is judged against that person’s schedule, including an after-the-shift band so an evening punch is not “500 minutes late”.
Who it is for
The people who actually start the day.
The employee
The person at the door.
Kai clocks in on the web or at the kiosk. The day on the board is his local day, not UTC by accident.
A manager
The person watching the week.
Needs you names the unpaired day. On leave is a word, not a shortfall. Unrequested overtime is not a payable number.
People
The person who decides a correction.
A past day or a request on someone else’s behalf comes to People in one step. Approve writes the punches.
Payroll
The person who pays the extra hours.
Only a fully approved overtime request is payable, and only up to the hours the clock recorded.
Keep reading
How hours should travel.
Questions people actually ask.
Do people still submit a timesheet?
No. A clean week closes itself. A missing clock out or an open exception holds the week for a human. Payroll never trusted a browser-written total.
Is overtime paid because the week ran long?
No. Someone must submit an overtime request and have it approved. Payable hours are then capped at what the clock recorded. Surplus is reported, not paid.
Is every site geofenced?
No. Geofence is opt in per building. Off by default. An unverified punch can be reviewed, accepted, or turned into a correction.
Can a device send punches before we register it?
No. An unknown serial is refused. Answering OK would make the machine delete punches we cannot store. Register the serial first.
Included with Employee ManagementTime & Attendance ships inside Employee Management at $5 per employee / mo · payroll included, with connected Organo included at no extra charge.Compare pricing →
More of Employee Management
The rest of the record.
Ready for time & attendance
that lives on one record?
Time & Attendance arrives as part of Employee Management, connected to the same record every other module reads. Nothing to sync, nothing entered twice.
← Back to Employee Management