Kuzhu attendance collects punches from biometric devices, the web clock and the mobile app into one muster, applies your shift and grace rules automatically, and routes missed-punch regularisations to the right approver. Month end is a review, not a reconstruction.
Why it exists
Attendance management software earns its keep on the days that are not simple: the biometric machine at the factory gate, the sales executive punching in from a client site, the developer on a hybrid week, and the supervisor who has to answer for all of them. Kuzhu takes punches from biometric devices, the web clock and the mobile app with GPS, and turns them into one judged attendance day per person — first in, last out, worked hours, late minutes, overtime.
The judging is where most attendance systems quietly give up. A punch is not a verdict; it has to be read against the person’s shift, their week-off pattern, the branch holiday calendar and the company’s late policy before it becomes Present, Half Day or Absent. Kuzhu evaluates every day automatically and shows its working, so when an employee disputes a half-day the answer is the timeline of their own punches, not an argument.
Corrections happen where everyone can see them. A missed punch becomes a regularisation request with a reason, routed to the manager, and the change is recorded against the original — the muster never silently rewrites itself. Once payroll has consumed a month, those days lock: money that has been paid does not get to change its mind.
The outcome
“The muster your payroll runs on, correct without a day of fixing.”
Feature by feature
Start
01
Biometric device integration alongside web and GPS-tagged mobile punch
02
Late marks, half days and short-leave rules applied by policy, not by memory
03
Regularisation requests with an approval trail instead of WhatsApp messages
Outcome
How it works
Most teams have this live inside the first month — the workspace exists on day one, and week three is a parallel run against whatever you use today.
Biometric devices push punches directly; the web clock and the mobile app with GPS cover everyone else. All of it lands in one stream per employee.
Grace minutes, half-day thresholds, overtime rules and geo-fencing — defined as policy, applied every midnight without anyone running anything.
Each day is evaluated against the person’s shift and calendar into Present, Absent, Half Day, Week Off or Holiday, with late and overtime minutes computed.
Missed punches become regularisation requests with approvals. Nothing is edited in place; every correction keeps its reason and its approver.
Payable days flow straight into the payroll run. The muster your auditor asks for is a report, not a reconstruction.
Worth a closer look
Buyer questions
2 answers
The answer
Devices go offline, people punch twice, and night shifts cross midnight. The punch pipeline de-duplicates, pairs INs with OUTs, assigns a punch after midnight to the shift that started before it, and keeps the raw events forever so any judged day can be re-derived and explained. When a device is down for an hour, the punches arrive late and the affected days are re-evaluated — not lost.
The answer
Field staff punch from the mobile app with location attached. You decide per person whether attendance requires the office network, a geo-fence around a site, or is trusted anywhere — the same rules engine, different radius. Managers see the day’s punches on a map rather than in a phone call.
Questions
Something else on your mind? +91 82093 73274 — a person answers, mon–sat, 10am–7pm ist.
Terms used here
Loss of payLOP
Loss of pay is a deduction for days an employee was absent without available leave, computed on gross or on specified components per day.
Attendance
Attendance is the daily record of whether, when and for how long an employee worked, captured from punches and judged against shift rules to produce paid days.
Biometric attendance
Biometric attendance records punches using a fingerprint or face on a device at the workplace, sending them to the attendance system automatically.
Attendance regularisation
Attendance regularisation is a request to correct a missed or wrong punch, approved by a manager, so the day is paid correctly instead of becoming loss of pay.
Overtime
Overtime is work beyond the standard daily or weekly hours, paid at twice the ordinary rate under the Factories Act and most state shop acts.
ESSL, Realtime and any device that can push punches over the network. Existing machines keep working — attendance integration does not start with buying hardware.
Yes, with GPS captured and optional geo-fencing per person or site. Selfie capture can be required where identity at punch matters.
By policy you configure: grace period, late-mark thresholds, half-day cutoffs. The system applies it uniformly and shows the arithmetic on each day.
A punch-out after midnight is paired with the shift that began the previous evening. Night shift attendance does not need manual fixing.
No — days consumed by a payroll run are locked. Corrections before that go through regularisation requests with an approval trail.
Works best beside
Other people modules that share the same employee record, so information moves with the person instead of between spreadsheets.
No polished slides. No imaginary employee data. Walk us through how your HR actually works today and see where Kuzhu can take the work off your team.
30 minutes · Your numbers · Your questions
What happens in the demo
Attendance, payroll, approvals — whatever is creating the most work.
You see exactly how the workflows connect instead of hearing a feature list.
If Kuzhu is not the right answer, we will tell you.
Ready when you are.
Kuzhu HRMS
WhatsApp us
WhatsApp us