The monthly people-ops loop: attendance, leave, and payroll

The monthly people-ops loop is the repeating sequence that closes attendance exceptions, leave decisions, and payroll inputs on one calendar. Regularisation and leave approvals must finish before loss-of-pay (LOP) and payslip calculation. The payroll-run checklist is the last mile — inputs locked, calculation run, payslips issued. This article is the path that feeds that checklist. It is not a second copy of pay-run steps, and it is not government filing.

If attendance, leave, and payroll close on three different informal calendars, you will keep discovering LOP after payslips. Growing Indian teams usually fail here from cutoff drift, not from a missing feature checkbox.

Name one cutoff calendar before you open the pay-run

Write three dates (or three windows) that the whole company can see:

1. Attendance close: last punch, last regularisation, last shift exception you will still accept for this pay period.
2. Leave close: last approval that will affect this period’s paid days or LOP.
3. Payroll input freeze: the moment HR or payroll may calculate, after which attendance and leave changes wait for the next cycle or a named off-cycle exception.

Those dates can sit on the first working days of the next month, or a few days before payday. The exact day is a company choice. The requirement is that they are ordered: attendance and leave finish first; calculation second; payslip release third. Statutory due dates for deposits and returns are a different calendar — verify those on official portals, and do not treat this loop as law.

Publish the order in the same place managers already look (intranet, SOP, or a pinned ops note). If only payroll knows the freeze, managers will keep approving leave on payday morning.

Attendance close: exceptions are a queue, not a rumour

Attendance management only helps the monthly loop if punches and exceptions land on the same employee identity payroll will use. Biometric names that do not match employee IDs are a system-of-record problem; fix identity in the employee system of record before you argue about minutes.

What must be finished

• Missing punches and forgotten check-outs that policy allows to regularise.
• On-duty, work-from-home, or outdoor marks if you use them as attendance types.
• Shift or roster corrections that change which day a punch belongs to.
• New joiners who started mid-period and must appear in the roster.
• Exits whose last working day must stop attracting “absent” noise.

What must not leak into payroll as a surprise

Open regularisation after the freeze, “the device was down so we will add days later,” and manager chats that never hit the attendance record. Those become LOP disputes. The loop’s job is to force exceptions into a queue with an owner and a close time — not to hope someone remembers.

If you run multiple sites or vendors, still freeze one company period. Site-level delays should be visible as incomplete queues, not as a silent second calendar.

Leave close: decisions before paid-day math

Leave is an input to payroll, not a parallel people list. Leave management should apply and approve against the same employee record as attendance. Sandwich rules, restricted holidays, and compensatory off only matter to the monthly loop if the approved result is in the system before freeze.

Close these before calculation

• Pending applications that overlap the pay period.
• Cancellations that return days to balance and change LOP.
• Leave without pay already marked, so it is not double-counted against attendance absence.
• Mid-period joiners’ and leavers’ pro-rata eligibility if your policy uses it.

Managers who approve after freeze create a choice you should make explicit: hold the payslip, run an off-cycle correction next month, or refuse the late approval for this period. Implicit “we will adjust later” is how trust in payslips dies.

Leave close is not “HR looking at a shared inbox.” It is a dated decision: this application is in or out of this period’s paid days.

LOP as an input, not a debate after payslips

Loss of pay should be a derived input: unpaid absence after attendance exceptions and leave decisions are applied, according to your written policy. If LOP is typed into payroll from a hallway conversation, you have skipped the loop.

Typical derivation, in plain language:

1. Start from calendar working days (or your shift calendar) for the period.
2. Subtract approved paid leave and holidays your policy treats as paid.
3. Reconcile remaining absence against attendance (including regularised presence).
4. What remains unpaid, under policy, is LOP (or another unpaid code you actually use).

Do not invent a national formula here. Policies differ on sandwich leave, late regularisation, and half-days. The operating rule is: LOP is calculated from closed attendance and leave, then handed to payroll calculation. Arguing LOP on payslip day means the earlier queues were not closed.

Payroll calculation is not filing and not bank payment

Payroll in an HRMS may calculate earnings, deductions, and statutory amounts, and issue payslips. That is not the same as filing returns with EPFO, ESIC, or the Income Tax Department, and it is not the same as paying the bank file. Growing teams blur the three and then blame “the HRMS” when a challan is late.

Step	What it is	Where it belongs in the month
People-ops loop	Attendance exceptions, leave decisions, LOP inputs, status changes	Before calculation
Payroll run	Lock inputs, calculate, review exceptions, release payslips	After the loop; use the payroll-run checklist
Filing and deposit	Statutory returns and payments your finance or consultant files	On official due dates you verify externally
Bank disbursement	Salary credit from your bank process	Your payday process — not assumed to be inside calculation software

Dayzen HRMS publishes payroll calculation and payslips as part of hire-to-exit people operations. It does not claim to file statutory returns or disburse bank payments. Dayzen PMS is a Project Management System, not performance management — do not hang a monthly review cycle on this loop.

A practical week-by-week rhythm (adapt the days)

Use this as a shape, not as law. Shift the weekdays to match your payday.

During the attendance month

Employees punch or mark attendance as policy requires. Managers watch exception queues weekly, not only at month end. HR watches joiners and exits so the roster is not a surprise on freeze day. Self-service for punches and leave applications belongs here so HR is not a ticket desk for routine transactions — see employee self-service versus HR tickets.

Close week

Publish reminders: regularise by date A, approve leave by date B. HR runs a list of pending items by manager. Incomplete managers are a named risk, not a silent delay. Freeze inputs. Only then start calculation.

Calculation and payslips

Follow the payroll-run checklist: confirm headcount and status, confirm LOP and attendance inputs, calculate, review a short exception list (new joiners, exits, unusual LOP), then release payslips. Do not reopen attendance for convenience unless you have a written off-cycle rule.

After payslips

Collect disputes that are genuine data errors versus disputes that are late regularisation. Genuine errors get a correction path. Late regularisation gets a “next cycle” path. If every dispute is treated as an emergency recalculation, you have no freeze.

Ownership: one name per queue

Loops fail when “HR” is the owner of everything and therefore of nothing. Assign:

• Attendance exception queue: operations or HR coordinator, with managers responsible for their team’s pending items.
• Leave approval SLA: managers, with HR chasing only breaches.
• Input freeze decision: one payroll or HR lead who may say “closed.”
• Calculation and payslips: payroll owner (who may be the same person in a small team, but the role is still named).

The yearly view of when these closes sit next to joining peaks, festival leave, and bonus cycles belongs on the HR operating calendar for Indian teams. This page stays the monthly mechanics.

If you are still evaluating software, ask vendors to show one employee moving through attendance close, leave close, and calculation — the same identity test as evaluating an HRMS for a growing team and hire-to-exit module connection. Labels such as HRMS vs HRIS matter less than whether LOP is an input produced by closed time and leave.

---

Close attendance. Close leave. Derive LOP. Freeze. Then run payroll. Filing and bank pay are later, separate jobs. If you skip the freeze, the checklist at the end of the month will only document the mess.

Two operating habits keep the loop honest in a growing Indian company. First, treat mid-month joiners and exits as first-class queue items in close week, not as “payroll will notice.” A person who joined on the 18th with no activated record will either be unpaid or invented in a side sheet. A person who exited on the 12th with an active directory flag will attract false absence and false LOP. Second, keep one written exception log for anything you allow after freeze: who asked, why, whether this cycle or next. Without that log, every manager believes their case is unique, and the freeze exists only on the slide.

If you outsource calculation, still own the people-ops loop in-house. The vendor can wait for a frozen file. They cannot guess which regularisations you meant to accept. Send them a closed attendance extract, a closed leave extract, and status changes — against one employee ID list — then let them calculate. That is still this loop, even when the calculator sits outside your office.