Biometric Attendance to Payroll: Where the Hours Get Lost
EK Ra Sunya Team ·
The fingerprint device by the office door does its job: every punch, with a timestamp. Then at month end someone exports a file from it, opens it in Excel, deletes the rows that look wrong, adds the field staff from a WhatsApp group, and sends a total to whoever runs payroll. That spreadsheet is the attendance system. The device on the wall is just its input.
**The short answer.** An attendance management system for a Nepali business has to do three things a biometric device alone doesn't:
- join device punches with staff who clock in elsewhere
- apply rules for incomplete days the same way every time
- hand a closed month to payroll without anyone retyping totals
When attendance causes a payroll dispute, look for the cause in one of those three gaps.
## The export step is where the record stops being a record
A device keeps every punch with a timestamp. The export keeps whatever the person exporting chose to keep. Once the file has been cleaned by hand there is no trail showing why Ram's Tuesday became a full day. When Ram disputes his salary in Bhadra, nobody can say what the device recorded in Shrawan.
This is the strongest argument for syncing punches straight from the device into the system that runs payroll. You still review the month, but you review the original data, not a copy someone already edited.
## Single punches need a rule before they need a decision
Every month brings days with one punch: someone came in and forgot to punch out, or arrived during a power cut and the device was off. Every office handles these. Few handle them the same way twice.
Decide once, in writing:
- **What a single punch means.** A full day, a half day, or an absence until a manager confirms?
- **Who can correct it, and by when.** A correction made after payroll is a payroll rerun.
- **Whether the employee is told.** A reminder on the day costs nothing. A deduction discovered on the payslip costs trust.
Then make the system apply the rule, so the answer doesn't depend on who is doing the export that month.
## The staff who never pass the device
Sales staff, drivers, site engineers and people working from a client office don't walk past the fingerprint reader. Their attendance usually arrives as messages, and messages don't reconcile.
The fix is a second way in that lands in the same record: staff clock in from their phone, and only when they are inside an agreed location. One record per employee, whichever way they came in.
## Leave and attendance have to agree
An approved leave day and a missing punch look identical on a device report. If leave lives in one place and attendance in another, someone matches them by hand every month. Approved leave should sit in the same system as attendance, so a leave day is never counted as an absence.
## How EK ERP joins it up
In EK ERP:
- Punches sync from biometric attendance devices.
- Staff without a device clock in and out from the mobile app, inside a geofence you set.
- Both routes land in one attendance history per employee.
- Staff who miss a check-in get a reminder the same day, while they still remember what happened.
[Leave requests and approvals](/features/leave) sit in the same system, and the holiday calendar runs in Bikram Sambat and AD. Payroll then works from a month that has already been closed, as in our [step-by-step guide to a monthly payroll run](/blog/payroll-in-nepal-monthly-run).
Before you buy a new device, check whether the one on your wall can be synced. Ask us about your model through the [attendance page](/features/attendance).
## Frequently asked questions
### Can EK ERP sync with biometric attendance devices?
Yes. EK ERP syncs punches from biometric attendance devices. Ask the team whether your device model is supported before buying a new one.
### How do field staff mark attendance in EK ERP?
From the EK ERP mobile app, which lets staff clock in and out only inside a geofence you set. Device punches and app check-ins land in one attendance history per employee.
### How should single punches be handled?
Decide one written rule for what a single punch means, who can correct it and by when, then have the system apply it the same way every month.
## A test you can run this month
Pick three employees at random and compare three numbers for last month:
1. what the device recorded
2. what the exported sheet said
3. what their payslip paid
If all three agree, your process works and you can stop reading. If they don't, you have found the gap, and you know which of the three sections above it falls into.
