Attendance and Payroll Integration (2026): How It Works, With a Worked Example

In most Indian companies, attendance decides pay. Unpaid leave, half days, late marks, absences, mid-month joiners and leavers all change what an employee is paid. Yet many companies still run attendance in one system and payroll in another — a biometric machine here, a payroll spreadsheet there — and someone rebuilds the connection by hand every month.

That handover is where payroll errors start. This guide explains how attendance and payroll integration works, what exactly should flow between them, a worked example, what to look for in software, and how to set it up.

Updated 30 September 2026.

The short answer

• Attendance–payroll integration means attendance, leave and regularisation data flow directly into salary, with no export or re-typing.
• What should flow: days present, paid leave, unpaid leave, half days, late-mark penalties, weekly offs and holidays, joining and exit dates.
• What it drives: loss of pay, proration, PF and ESI on the wages actually earned, and TDS on the resulting salary.
• The best setup is one system for attendance, leave and payroll. The next best is a reliable, automatic integration.
• Test it by running one real month and checking every payslip against attendance.

Why the handover goes wrong

When attendance and payroll are separate, a typical month looks like this:

1. On the 1st, HR exports attendance from the biometric software.
2. Someone matches it against leave approvals in email or a spreadsheet.
3. Late regularisations arrive after the export, and get missed or pushed to next month.
4. Loss-of-pay days are typed into the payroll sheet.
5. PF and ESI are calculated — sometimes on the full salary instead of the wages actually earned.

Every step is a chance to make a mistake, and nobody can easily trace a payslip back to the attendance behind it.

What should flow from attendance to payroll

Attendance data	Effect on payroll
Days present	Paid days
Approved paid leave (casual, sick, earned)	Paid days
Approved unpaid leave	Loss of pay
Absent without leave	Loss of pay (if your policy says so)
Half days	Half a day of pay, or half a day of leave
Late marks beyond the allowed number	Half-day deduction, if your policy says so
Weekly offs and holidays	Paid, as per policy
Comp off	Paid leave against extra days worked
Regularisations	Corrected attendance before payroll runs
Joining and exit dates	Proration for days not employed

What attendance drives in payroll

• Loss of pay — every component of salary reduced by unpaid days, not just basic.
• Proration — joiners and leavers paid only for the days they were employed.
• PF — calculated on basic actually earned, within the wage ceiling.
• ESI — calculated on gross wages actually paid in the month.
• TDS — recalculated on the resulting salary.

If attendance is wrong, all five are wrong.

A worked example

Rohan earns ₹30,000 a month (basic ₹15,000). In September (30 days):

• 2 days of approved unpaid leave
• 1 absence with no leave applied
• 4 late marks; policy allows 3, then each extra late mark costs half a day
• A regularisation for a missed check-out, approved on the 30th

Paid days = 30 − 2 (unpaid leave) − 1 (absence) − 0.5 (one late mark over the allowance) = 26.5

Gross earned = ₹30,000 × 26.5 ÷ 30 = ₹26,500 Basic earned = ₹15,000 × 26.5 ÷ 30 = ₹13,250 Employee PF = 12% × ₹13,250 = ₹1,590

The regularisation on the 30th prevented another absence from being counted. In a manual process, it would probably have arrived after the attendance export — and Rohan would have lost another day's pay by mistake.

Two ways to integrate

1. One system for attendance, leave and payroll

Attendance, leave and payroll share the same data. There's no export and nothing to sync. A late regularisation is reflected in payroll as soon as it's approved. This is the most reliable option for most SMEs.

2. Separate systems connected by an integration

An attendance system (or biometric software) sends data to a separate payroll product through an API or scheduled file. This can work well, but check:

• How often data syncs, and what happens to changes after the sync.
• How leave approvals and regularisations are included.
• Who fixes it when the sync fails.

What to look for in software

1. Attendance methods that fit your team — biometric machines for offices and factories, geofenced mobile check-in for field and site staff.
2. Leave and regularisation in the same system, with manager approvals.
3. Configurable rules — office timings, grace minutes, late-mark allowance, weekly offs, holidays.
4. Automatic loss of pay and proration in payroll.
5. PF and ESI on the wages actually earned.
6. Traceability — from a payslip back to the attendance days behind it.
7. An attendance grid to review the whole month before running payroll.

How PeopleVio connects attendance and payroll

In PeopleVio, attendance, leave and payroll are one system:

• Attendance from geofenced GPS check-in in the browser, or from ZKTeco/eSSL biometric machines that push punches directly to PeopleVio.
• Rules for office start and end times, late grace minutes, a monthly late-mark allowance (then half a day), weekly offs, holidays and optional holidays.
• Leave and comp off with manager approvals.
• Regularisation requests for missed punches or wrong status, approved before payroll.
• Optional auto-absent — treat a working day with no attendance record as an unpaid absence, if you switch it on.
• Payroll that reads paid and unpaid days directly, prorates mid-month joiners and leavers, and calculates PF and ESI on the wages earned.
• An attendance grid for the whole team, and an hours report you can export.

What it doesn't do: shift rostering or overtime rules. Overtime is added to payroll as an earning.

What it costs

Active employees	Monthly billing	Yearly billing (per month)
25	₹1,475	₹1,225
50	₹2,450	₹2,050
100	₹4,900	₹4,100
300	₹11,700	₹9,900

Attendance, leave, payroll, PF, ESI and TDS are all included. Prices exclude GST. See the pricing page. Biometric machines are bought separately — see our biometric machine price guide.

How to set it up

1. Decide the attendance method for each group: biometric, geofenced mobile, or both.
2. Set the rules: office timings, grace minutes, late-mark allowance, weekly offs, holidays.
3. Import employees with salary structures and joining dates.
4. Connect biometric machines or add office locations for geofencing.
5. Run a month: let employees check in, apply for leave and request regularisations.
6. Review the attendance grid before payroll, then run payroll and check payslips.

Frequently asked questions

What is attendance and payroll integration? It's when attendance, leave and regularisation data flow automatically into payroll, so loss of pay, proration, PF and ESI are calculated from actual attendance without manual export.

Can biometric attendance be linked to payroll? Yes. Machines that support cloud push (ZKTeco, eSSL and similar) can send punches directly to software like PeopleVio, where they feed payroll.

How is loss of pay calculated from attendance? Commonly: monthly salary × unpaid days ÷ days in the month (or 26 or 30, as per your policy), applied to every salary component.

What happens to regularisations after payroll has run? In an integrated system, they're approved before payroll runs. Anything approved later is corrected in the next payroll as an adjustment.

Does PeopleVio support late-mark deductions? Yes. You set grace minutes and a monthly allowance of late marks; after that, late marks can cost half a day.

The bottom line

Attendance decides pay. Keep attendance, leave and payroll in one system, or connected by a reliable automatic integration, and most payroll errors disappear.

See PeopleVio's pricing or book a demo to run a real month of attendance and payroll on your own data.

Related reading: Biometric attendance software with payroll · Connect a ZKTeco/eSSL machine to HRMS · Attendance regularization software · Geofenced attendance explained