Time
Attendance & leave
Attendance that becomes payroll input without anyone retyping it.
Attendance only matters because it determines pay. EZER treats it that way: shifts, rosters, imports and regularisations all resolve into the day count that the payroll run reads directly.
Without a system
How this gets done today
The biometric machine produces a punch log. Payroll needs a day count. Between the two sits somebody with a spreadsheet, reconciling missed punches against leave applications sitting in an email folder.
By the time it is settled, half the month’s regularisations were approved verbally and the leave balance nobody trusts is the one on the register.
What it does
Inside attendance & leave
Shifts and rosters by location
Define shift patterns, weekly offs and location-specific rules. Night shifts crossing midnight are handled as one shift, not two half days.
Import from your existing device
Upload the punch log from the biometric system you already have. There is no hardware to replace to start using this.
Regularisation with an approval trail
A missed punch is raised by the employee, approved by the manager, and recorded with who approved it and when — not settled in a corridor.
Overtime on your rules
Configure how overtime is earned and at what rate, then let it carry into the payroll run as a calculated component.
Leave with balances that reconcile
Apply, approve, track. Balances, accruals, carry-forward and encashment follow the policy you configured, and the same balance appears to the employee, the manager and payroll.
Statutory leave by state
Leave entitlements that follow the applicable state Shops & Establishments rules, rather than one policy applied everywhere and reconciled later.
Holiday calendars per location
A Maharashtra location and a Tamil Nadu location do not share a holiday list. Neither should their attendance.
Reports that answer the question
Muster roll, late marks, absenteeism and shift coverage, by location and by month, exportable.
See it working
On screen
One balance, seen by everyone
The employee, the approving manager and payroll all read the same number.
Screenshot pending
Leave application and approval screen with the running balance shown
Build the demo company with fictional names, salaries and PAN/Aadhaar values first, then drop the image in — see site.config.ts.
Who it’s for
What each person gets out of it
HR
Attendance closes without a reconciliation spreadsheet.
Managers
Approve regularisations and leave in one queue, with the balance visible.
Employees
Apply for leave and see the balance without asking anyone.
Finance
Overtime and loss-of-pay arrive in payroll already calculated.
Works with
The modules this connects to
These are not integrations. They are the same system reading the same data.
Questions
About attendance & leave
Do we need to replace our biometric devices?
No. Attendance is imported from the punch log your existing devices already produce, so you can start without touching the hardware.
Can different locations have different shift and holiday rules?
Yes, and they generally must. Shift patterns, weekly offs, holiday calendars and statutory leave entitlements are all set per location, because the applicable Shops & Establishments rules differ by state.
See EZER on your own data
See attendance & leave on your own data
Tell us your headcount and your states, and we will walk through attendance & leave against your actual setup rather than a generic demo account.
- Thirty minutes in the live product. Not a slide deck, and not a recorded video.
- We ask first: how many entities, which states, how many employees, what you run payroll on today.
- Then we show your case — your salary structure, your statutory setup, your locations.
No obligation, no credit card, and we won't add you to a mailing list without asking.