Biometric Attendance Software with Payroll in India (2026): How Punches Become Salary

Buying biometric attendance software with payroll sounds simple: the machine records who came in, and the payroll deducts for who didn't. In practice the whole value sits in the gap between those two steps. Where does a punch go, who decides what counts as late, what happens to a day with no punch at all, and does the payslip match what the machine shows? Software that answers those questions clearly saves a day of payroll work every month. Software that hides them creates disputes.

This guide explains what to look for in biometric attendance software with payroll in India, walks through how punches turn into salary, and describes exactly how PeopleVio does it, including the parts you need to review by hand.

What "biometric attendance with payroll" should mean

There are three links in the chain, and each can fail:

1. Machine to software. Punches must reach the HR software without someone exporting a file.
2. Punches to attendance. Raw scans must become a daily record with a check-in, a check-out and a status.
3. Attendance to payroll. The month's records must decide how much salary is paid.

Many products do the first link well and leave you to bridge the other two in Excel. A good one connects all three and shows its working.

What to look for

• Live sync from common machines. ZKTeco, eSSL, Realtime and Mantra machines are the ones most Indian offices already own. Ask whether cloud push is supported, and what happens to machines that can't push.
• Clear rules for late and half-day. Office start time, grace period and monthly late allowance should be configurable, and the same rules should apply whether someone checks in on a machine or a phone.
• Duplicate and backlog handling. People scan twice, and machines go offline and upload later. The software should handle both without creating false records.
• A way to see unmatched punches. Punches from an ID nobody enrolled should be visible, not silently dropped.
• A review step before payroll. You should be able to see and correct the month's attendance before you run salary.
• A payslip that explains itself. Paid days, unpaid days, variable pay, deductions and net pay, in one view.
• Payroll that fits your structure: Basic, HRA, allowances, incentives and reimbursements.
• TDS and statutory support where you need them, and a clear statement of what is not covered.

How PeopleVio turns punches into salary

1. Punches arrive. A ZKTeco-protocol machine pushes each punch live through its Cloud Server (ADMS) setting. Machines that can't push can send punches through an API or a small script on an office PC, and a punch log exported as CSV can be imported. Employees are matched by machine user ID, employee code or email. Our connection guide covers setup.

2. Punches become a daily record. The earliest punch of the day is the check-in and the latest is the check-out. Scans within two minutes of each other count as one touch. Repeats and late uploads produce the same result, and punches for unknown or inactive employees are not applied.

3. Status follows your rules. A check-in after office start plus the grace period is marked late. Once the employee's monthly late allowance is used up, further late days become half-days. This is the same policy the in-app check-in uses, so machine and phone staff are treated identically. A day already marked as leave keeps its status.

4. Payroll reads the month. When an admin runs payroll, PeopleVio starts from the fixed monthly salary (Basic, HRA and other allowances) across the calendar days of the month, and reduces it for unpaid days: each day recorded as Absent counts as a full day and each Half Day counts as half a day. If the company has switched on the auto-absent setting, past working days with no attendance record at all count as unpaid too (see below). Variable pay entered for the month, such as an incentive, is not prorated. Approved expense claims are added as reimbursements, TDS is calculated when it is enabled, and a PDF payslip is produced.

What happens to a day with no punch

A machine only records people who punch. So the question every payroll buyer should ask is: what does the software do with a working day where nobody punched and nobody marked anything?

In PeopleVio this is a setting you control, under attendance settings ("Missing Punches in Payroll"):

• Ignore (the default). Payroll deducts only for days recorded as Absent or Half Day. A working day with no attendance record is not deducted, so you review the team grid before payroll and mark absences by hand. Half-days from exhausted late allowances are created automatically, but absences are not. The default is off so existing payslips never change without you choosing.
• Count as absent. Payroll also treats a past working day with no attendance record as an unpaid absent day. The payslip records how many of its unpaid days came from this.

When auto-absent is on, these days are never counted: weekly offs, any holiday on your calendar, days before the employee's joining date, today and future days, days covered by approved or pending leave, and days redeemed as comp off. A pending leave request protects the day until someone decides it, so an undecided request never turns into a silent deduction.

Either way, build a month-end review into your routine. Open the team attendance grid, check anyone with unusual gaps, and use the hours report (total hours per employee for any date range, exportable as CSV) to spot people with far fewer punches than expected. Run one parallel payroll cycle before you turn the setting on, and compare paid days against your old process.

How the main options fit

Option	Fit
Machine vendor's own software	Included with the device, but payroll integration is often basic, so many companies export attendance manually into another tool
Zimyo, Keka, greytHR, HROne	Broader suites with biometric integration, shift rosters and deeper statutory payroll, at higher price points and more setup
Specialist attendance tools	Strong on devices and shifts, often separate from payroll
PeopleVio	Biometric and phone attendance, payroll with TDS, expenses and offer letters in one flat per-employee price, with the limits below

An honest note on limits

• Auto-absent is opt-in. With the setting off, days with no record are not deducted, so review and mark absences before payroll. With it on, the rules above decide which days count.
• No shift scheduling or overtime. Attendance uses your configured office timing and grace period, so overnight shifts aren't modelled separately.
• Only first and last punch count. Break punches are not tracked.
• Not every machine supports cloud push. Confirm your model.
• PF, ESI, Professional Tax and gratuity are not calculated or filed. See our PF and ESI guide.
• TDS is opt-in. An admin enables it in company settings, and it has no surcharge or previous-employer income handling.

A worked example: a 30-person company, one machine

Suppose a company has 30 employees on a fixed monthly salary, with one eSSL machine at the door.

• Setup: register the machine, match employees by employee code and set the timezone offset to 330.
• During the month: punches arrive live. Two employees exceed their late allowance, so two of their late days become half-days automatically.
• Month end: the admin opens the team grid and checks the hours report for anyone with unusually low hours. An employee with no punches for three days after a family emergency is either marked Absent by hand, or counted automatically if the company has turned on auto-absent. Approved leave for those days would protect them either way.
• Payroll run: one click. Paid days equal calendar days less recorded absences (with half-days counting as half), the incentive for the sales lead is added unprorated, and PDF payslips are generated.
• Cost: at 30 employees the 26 to 100 band applies, ₹49 per employee per month on monthly billing (₹41 on yearly). That is ₹1,470 a month, or ₹1,230 a month billed yearly, with all modules included. The band rate applies to your total active employee count, so check the pricing page for current numbers.

Common mistakes

• Assuming missing punches mean lost pay. Check how your software treats a day with no record before the first payroll, and choose the setting deliberately.
• Skipping the month-end review. Ten minutes on the grid prevents overpaying or underpaying, whichever way your setting is.
• Inconsistent employee IDs. Half the punches go unmapped and half the team looks absent.
• Wrong machine clock. Every late mark is wrong by the same amount.
• Not running a parallel payroll cycle. Compare paid days against your old process for one month.

Frequently asked questions

Can biometric attendance feed payroll automatically? Yes. In PeopleVio, punches from ZKTeco-protocol machines update attendance, and monthly payroll uses the recorded absences and half-days. Days with no record at all are deducted only if the company has turned on the auto-absent setting, so review the month's attendance first either way.

Does a missing punch cause a salary deduction? That depends on a setting. By default payroll deducts only for days recorded as Absent or Half Day. If an admin turns on auto-absent, past working days with no record are counted as unpaid, except weekly offs, holidays, days before joining, approved or pending leave and comp-off days.

How is a half-day decided? Once an employee has used their monthly late allowance, further late check-ins are marked as half-days, whether they punch on a machine or a phone.

Are holidays and weekly offs deducted? No. Salary is calculated over the calendar days of the month, less recorded unpaid days.

Are incentives prorated for attendance? No. Variable pay entered for the month is added unprorated, while fixed pay is prorated.

Which machines work with PeopleVio? Machines that use the ZKTeco protocol with Cloud Server (ADMS) push, including ZKTeco, eSSL, Realtime and Mantra devices, plus any source that can send punches through the API or a CSV export.

Does PeopleVio handle shifts and overtime? No. It has no shift roster or overtime module.

How much does it cost for a 60-person company? On PeopleVio, 60 employees falls in the 26 to 100 band at ₹49 per employee per month (₹41 yearly), so about ₹2,940 a month on monthly billing, with biometric connection and payroll included. You buy the machine separately.

The bottom line

Biometric attendance software with payroll is only as good as the two handoffs, punches into attendance and attendance into salary. PeopleVio connects both in one portal at a flat per-employee price, with clear rules for late marks and half-days. Decide how missing punches should be treated, using the auto-absent setting, and build a month-end review of the attendance grid into your routine. Test the full chain with your own machine and one parallel payroll cycle before you rely on it.

Want to test it with your machine and your payroll? Request a demo or check the pricing.