The last five working days of the month decide whether payroll is calm or chaotic. Most of the stress is not about calculation. It is about changes arriving late, approvals nobody has time for, and statutory work that starts too late. This checklist gives each day a job. Shift the days to match your pay date, but keep the order.
Figures here reflect the rules as we understand them at the time of writing. Verify against the current rules and notifications before relying on them.
The five-day plan at a glance
| Day | Focus | Output |
|---|---|---|
| Day -5 | Freeze inputs | Cut-off passed; joiner, exit and revision lists final |
| Day -4 | Attendance and leave | No pending corrections; paid days and LOP agreed |
| Day -3 | Calculate and review exceptions | Register with exception notes |
| Day -2 | Approve and lock | Locked payroll, payslips generated |
| Day -1 | Bank file and payment | Paid, or sent to the bank, with totals checked |
| Day 0 and after | Reconcile and file | Challans, returns, accounting entries |
Day 0 is pay day. If you pay on the last working day, Day -5 may already be in the third week. Count backwards from your own date.
Day -5: freeze the inputs
- Remind everyone of the cut-off. Late items go to next month or an off-cycle payment.
- Joiners: confirm joining date, structure, bank details, PAN, UAN where applicable, work state.
- Exits: confirm last working day, final settlement status, any notice-period recovery.
- Salary revisions: effective dates and approvals present. Backdated revisions need a stated arrears amount.
- One-time items: incentives, arrears, recoveries, each with a reason and an approver.
- Loans and advances: this month’s instalments and any skips.
- Reimbursements: approved claims to be paid with this payroll. Anything approved after the period end waits.
A frozen input list should be something you can email to the approver in one message.
Day -4: attendance and leave
- Ask managers to clear pending leave requests and attendance corrections.
- Check for employees with no attendance at all in the month. They are either on long leave, exited or missed.
- Confirm half days, comp off and work-from-home days are coded correctly.
- Approve overtime hours, and look at anyone with more than 50 hours in the month, which usually deserves a second look.
- Review LOP days for the month and send the list to managers for a quick yes or no.
- Make sure no corrections are still pending before approval, since a payroll built on pending data will need reopening. Our post on loss of pay calculation shows how paid days convert to pay.
Day -3: calculate and review exceptions
- Run the calculation once, on the frozen inputs.
- Review exceptions rather than every payslip:
- net pay changed by more than a set percentage from last month;
- new joiners and leavers;
- zero or negative net pay;
- anyone below the applicable minimum wage (see minimum wages for payroll teams);
- duplicate bank accounts across employees;
- missing bank details or PAN;
- large one-time payments.
- Write a one-line reason beside each exception.
- Compare totals with last month: headcount, gross, PF, ESI, PT, TDS, net.
- Spot-check five employees by hand, including one at the PF wage ceiling and one near the ESI limit of Rs 21,000.
- Decide on salary holds, with a reason and an owner. A held salary is released later, not forgotten.
Day -2: approve and lock
- The preparer sends the register and exception notes to the approver.
- The approver reviews exceptions and signs off. The preparer and approver must be different people.
- Lock the month. After this, edits require a recorded reopening with a reason.
- Generate payslips from locked data.
- Publish payslips, or schedule them for pay day.
- If you must reopen, regenerate everything downstream: payslips, compliance files and the bank file.
Day -1: bank file and payment
- Create the bank file in your bank’s layout. Test the layout with a small file if the bank changed it.
- Check the file total and count against the register. Held salaries and missing details should be excluded.
- Watch for duplicate account and amount pairs.
- Have someone with payment approval rights approve the batch, separate from the person who prepared it.
- Upload to the bank and keep the acknowledgement.
- Prepare a retry plan for anything that fails.
Day 0 and after: pay, reconcile, file
Pay and reconcile
- Confirm that the bank has processed the file.
- Upload the status file or mark payments paid or failed.
- Retry failed payments after correcting details, so that the next file contains only the retries.
- Tell employees whose payment was returned.
Statutory work
| Item | Typical due date | Action |
|---|---|---|
| TDS deposit | 7th of next month | Pay challan from locked payroll |
| PF contribution and ECR | 15th of next month | Generate ECR, validate, pay challan. See the PF ECR checklist |
| ESI contribution | 15th of next month | Prepare contribution file, pay |
| Professional Tax | By the state’s due date | Pay per state; see Professional Tax basics |
| Labour Welfare Fund | State-specific, usually half-yearly or yearly | Pay in the relevant month |
All dates are as we understand them. Verify them for your establishment and state.
Accounts
- Post the payroll summary by department or cost centre.
- Post employer contributions and statutory liabilities as payable until paid.
- Reconcile salary payable against the bank.
- Record reimbursements and advances separately from salary.
Evidence
- Save the approved register, exception notes, bank file, bank acknowledgement, challans and portal acknowledgements in one folder named for the month.
- Note what went wrong, if anything, and the change you will make next month.
Common close mistakes
- Starting the review on the pay day. It leaves no time for a second look.
- Approving while corrections are pending. You will reopen.
- Creating the bank file before locking. The file and the register disagree.
- Reopening quietly. Everything downstream becomes unreliable.
- Filing statutory returns on the due date. An error on the 15th has nowhere to go.
- No exception notes. The same questions come back next month.
Where software helps
Software can enforce the order. In Saralix the payroll wizard follows a similar order: payroll month, input checks, attendance and LOP, calculate, review, approve and lock, then payslips and the bank file. Approval is blocked while attendance corrections are pending, whoever calculates cannot approve (unless they are a super admin), and reopening needs a reason and is not allowed once the bank file has been exported. Payments are reconciled by uploading the bank’s status file, and statutory liabilities carry due dates and a paid, overdue or due-soon status. See the payroll and compliance and tax feature pages for detail.
Related reading
For the process in general, read how to run payroll in 7 steps. For the full set of recurring tasks, see the payroll checklist for 10 to 100 employees.
Closing thought
A close that takes five calm days beats one that takes two frantic ones. If you want the lock, the bank file and the reconciliation to sit in one flow, the payments module in Saralix covers approval, bank files for HDFC ENet, ICICI CIB and a generic CSV, and matching against the bank’s status file.



