Biometric Attendance to Payroll: The Missing Rules Layer

Raw biometric punches are not payroll-ready, which is why a biometric attendance payroll integration needs a rules layer in between. A punch only records that an employee's finger or face was scanned at a certain time. Payroll needs to know whether that time counts as a full day, a late arrival, overtime, leave, or nothing at all. That depends on the employee's shift, your attendance policy, and approvals the device never sees. The rules that turn punches into payable time have to live somewhere between the device and payroll.

In many companies that "somewhere" is one person with a spreadsheet and a few days at the end of each month. This article covers what that person is actually doing in the attendance to payroll process, and what a proper rules layer needs to handle instead.

What the device actually gives you

A biometric device produces a log. Each line usually holds an employee ID, a date and time, and the device it came from. Some devices also record whether the punch was meant as an entry or an exit, but staff often press the wrong key or none at all.

That log has no idea what a shift is, which days are holidays, who is on approved leave, or whether the extra two hours someone stayed were authorised. It also inherits some practical problems:

• Device clocks drift unless they are synced, so the same moment can be recorded differently on two devices.
• The employee ID on the device does not always match the ID in HR or payroll, especially after re-enrolments or transfers between branches.
• People punch twice, punch on the wrong device, or forget to punch at all.

Problem 1: turning punches into shifts

The first job is pairing punches into a worked period. For a single nine-to-five office shift this looks easy: first punch in, last punch out. It stops being easy quickly.

A night shift that starts in the evening and ends the next morning crosses midnight, so "the punches for Tuesday" belong partly to Monday's shift. A factory running rotating shifts needs to know which shift each employee was rostered on that day before it can judge whether they were late. A split shift has two in-and-out pairs. Field staff may punch at a different branch from the one they belong to.

None of this can be worked out from the log alone. The rules layer needs the shift definitions and the roster, and it needs to know which punch belongs to which shift.

Problem 2: missed and duplicate punches

Missed punches happen every month. Someone came in through a side door, the device was down, a finger did not read. The common fix is that HR edits the attendance sheet directly. That works until an auditor or an employee asks why a day was marked present or absent, and nobody can say who changed it or on what evidence.

A better pattern is missed punch regularisation through a request: the employee states what happened, their manager approves or rejects it, and the system records both. The raw punch log stays untouched. The correction sits on top of it, with a name and a date attached.

Duplicates are simpler but still need a rule. Two punches a minute apart are almost always one event. Two punches an hour apart might be a lunch break or might be a second shift.

Problem 3: late arrivals, early exits, and grace periods

Most companies allow some grace before an arrival counts as late, and many treat repeated lateness differently from a single occurrence. Some deduct pay, some count it against leave, some only report it. Whatever your policy is, it needs to be written down and applied the same way to everyone. A rule that is applied by hand gets applied inconsistently, and inconsistent deductions are the ones employees complain about.

Problem 4: overtime rules

A punch log shows how long someone was on site. It does not show overtime. Staying late to finish a task or waiting for a ride home is not overtime unless your policy says it is.

The rules layer has to decide:

• Whether overtime needs approval before it is worked, or can be approved afterwards.
• How much time beyond the shift must be worked before overtime starts counting.
• Whether overtime on a weekly day off or a public holiday is treated differently.
• What the limits are, per day and per period.

Nepal's Labour Act sets limits on working hours and overtime and requires overtime to be paid at a higher rate than normal hours. Confirm the current figures with the labour authorities or your legal adviser rather than copying them from a blog post, including this one. Your own policy can be more generous than the law but not less.

Problem 5: leave and holiday overlap

Attendance and leave are usually managed in different places, and payroll needs both to agree. Common conflicts:

• An employee has approved leave for a day but also has punches, because they came in for a meeting. Is that a worked day, a leave day, or half of each?
• A half-day leave with a single punch at lunchtime.
• Absence with no leave request at all, which may become unpaid leave or may be waiting for a late application.
• Public holidays. Nepal's holiday calendar is published by the government each year and some holidays apply only to certain groups of employees, so a single company-wide list is often not enough.

Each of these needs a rule, and the rule needs to be applied before payroll runs, not discovered after payslips go out.

Problem 6: approvals and the monthly cut-off

Regularisations, overtime, and leave all depend on managers approving things on time. Some will not. Payroll needs an attendance cut-off date, after which the period is closed and locked. Anything approved later is carried into the next month as an adjustment rather than reopening a period that has already been paid.

Without a lock, attendance keeps changing after payroll has used it, and the two records quietly drift apart.

What the rules layer contains

Put together, the layer between the device and payroll covers shift and overtime management, leave, and corrections. It holds:

• Shift definitions and the roster for each employee.
• Punch pairing and duplicate rules, including shifts that cross midnight.
• Grace, lateness, and early-exit rules.
• Overtime rules, with approval.
• Approved leave and the holiday calendar, by employee group.
• A regularisation workflow for missed punches, with an audit trail.
• A period close that locks attendance before payroll uses it.

Its output is a status for every employee for every day, rolled up into the figures payroll needs: payable days, unpaid days, late counts, and approved overtime. Payroll should read those figures. It should never read raw punches.

Before you start a biometric attendance payroll integration

• Match the IDs. Make sure every enrolled employee on every device maps to exactly one employee record.
• Sync the clocks. Set all devices to the same time source and check them regularly.
• Write the rules down. Most attendance policies exist partly as habit. Anything not written down cannot be configured.
• Run one month in parallel. Process attendance the old way and the new way, and reconcile every difference. Each one is a configuration error or a rule nobody had documented.

If you are comparing HR systems or a biometric attendance system in Nepal, our buyer's checklist for choosing an HRMS in Nepal covers what to test on the attendance side before you commit.

Yoddha Lab builds NepalHRM, a cloud HRMS that pulls attendance from biometric devices and applies shifts, overtime, and leave rules before the figures reach payroll, which is built around Nepal statutory requirements including PF, CIT, SSF, and eTDS. See NepalHRM or talk to our team.

This article is general information, not legal advice. Confirm current working-hour, overtime, and holiday rules with the relevant government office or your legal adviser.