Payroll processing steps in India are not just "calculate salary and pay." A clean run is an attendance lock, a leave and LOP pass, statutory calculations (PF, ESI, PT, TDS), then payslips and remittances. Skip the attendance gate and you will reverse payslips for a week.
This guide is the operator sequence we use when onboarding Indian SMEs on Zeba - the order matters more than the formulas.
Payroll processing steps (end-to-end checklist)
- Freeze master data - new joiners, exits, salary revisions, bank details, and tax regime choices must be in before you calculate.
- Close attendance - approve pending attendance regularization, outdoor duty, and missed punches. Lock the month.
- Close leave - approve leave, comp-offs, and holidays that affect payable days. See your leave management rules.
- Compute payable days and LOP - convert attendance + leave into paid days. LOP is where most disputes start.
- Run earnings and deductions - basic, allowances, variables, reimbursements, advances.
- Apply statutory - EPF / EPS / EDLI, ESI, professional tax, TDS. Watch the PF ceiling limit 2026 change if you are in the new wage band.
- Preview exceptions - mid-band PF wages, first/last month, unpaid absences, negative net pay.
- Lock payroll and generate payslips - publish to employees only after finance sign-off.
- Pay and remit - bank transfer / NEFT file, then PF ECR, ESI, PT, and TDS calendars.
- Archive - keep registers and payslips audit-ready.
If your team still builds payroll in spreadsheets, step 2 and step 4 are where silent errors hide. Payroll automation only helps when attendance is already trustworthy.
Step that most teams underestimate: attendance lock
Indian payroll arguments are rarely about the 12% PF rate. They are about "I was present but marked absent." That is an attendance regularization problem, not a payroll formula problem.
Practical rule: publish the attendance cut-off 3-5 days before payroll lock. Clear the AR queue. Then calculate. Running payroll while regularization is still open guarantees LOP reversals.
How LOP fits the payroll sequence
LOP (loss of pay) is unpaid absence after leave balances and approved exceptions are applied. A simple mental model:
- Calendar / payable days for the wage month
- Minus unpaid absences (and unpaid half-days, per policy)
- Earnings prorated on payable days
- Statutory recalculated on the reduced wage where rules require it
Exact day-count methods differ by company (calendar days vs paid days vs 30-day fixed). Pick one method, document it, and do not change it mid-year without communicating to employees.
Statutory block inside Indian payroll processing
- EPF: employee 12% on PF wages (subject to ceiling / voluntary rules); employer share split across EPF + EPS as configured.
- ESI: only when the employee is covered under the wage threshold rules for your location and applicability.
- Professional tax: state-wise slabs (for example Maharashtra) - usually a monthly or semi-monthly deduction logic.
- TDS: based on regime, proofs, and estimated annual income - not a flat surprise at year end.
Zeba's edge case that saves remittance pain: treat statutory ceilings by payroll month, not by inventing mid-month splits inside one payslip when the product policy is full-month application. See the EPF ceiling note linked above for September 2026 behavior.
Sample calendar for a month-end payroll
- T-7: remind employees to regularize attendance and apply pending leave
- T-5: managers clear AR and leave queues
- T-4: HR locks attendance
- T-3: payroll preview + exception list
- T-2: finance approval
- T-1 / T: payslips + bank file
- After pay day: statutory remittances on their legal due dates
Move the dates to match your salary credit day. The sequence stays the same whether you pay on the last working day or the 7th.
Where Zeba shortens the chain
- Attendance, leave, and payroll sit in one product - less CSV ping-pong
- Regularization and approvals happen before lock, not in email threads after payslips
- Statutory settings and payslips reuse the same wage month context
If you only need attendance + payroll first, start there and add modules later. Full HRMS scoping can wait until the monthly run is stable.
FAQs
What are the payroll processing steps in India?
Master data freeze, attendance and leave close, LOP and earnings calculation, statutory (PF/ESI/PT/TDS), preview, lock, pay, remit, archive.
Should payroll start before attendance is locked?
No. That is the most expensive shortcut. Lock attendance first, including regularization.
Where does attendance regularization sit in payroll?
Before LOP calculation. After lock, only controlled HR exceptions should change attendance.
How is LOP calculated in salary?
Unpaid days reduce payable days; earnings are prorated per your day-count policy; statutory may recompute on the reduced wage. Document the day-count method your company uses.