How to use this guide
In our experience, most payroll problems don’t start with the payroll calculation itself. They start when an input reaches payroll late, incomplete, or without a proper approval trail behind it. This guide focuses specifically on what happens once payroll takes ownership of the cycle: how the monthly run should flow, how the resulting liabilities get provisioned in the books, what controls hold the process together, and how the calendar should be planned from day one of the month rather than assembled as an afterthought at month-end.
A note on scope — attendance capture, leave management, and the underlying statutory framework (EPF, ESI, Professional Tax, TDS and the Labour Codes) are each substantial subjects, and are covered as separate modules in the GrowthNest curriculum. This guide picks up from the point at which validated attendance and variable-pay data reach the payroll team, and carries the process through to reconciliation and closure.
Part 1 — The Monthly Payroll Processing Cycle
The diagram below sets out the eight stages of the processing cycle itself, from the input freeze through to reconciliation and closure. Stages 2 through 4 form the control zone where the maker-checker discipline does its heaviest work — an error caught here costs nothing; the same error caught after disbursement costs a correction cycle, a revised filing, and usually an anxious employee query.

Stage 1 — Input freeze
Validated attendance and variable-pay data — already approved upstream by HR and the relevant business functions — is locked for the month. The maker submits the consolidated input for processing. Everything after this point is a controlled environment; anything reopened after freeze should require a named approver and a documented reason.
Stage 2 — Statutory calculation
PF, ESI, professional tax, TDS, and any applicable labour welfare fund contributions are computed on the frozen wage data.
Stage 3 — Checker validation
A second person — never the maker — reviews the calculated output.
Practitioner note — A checker who simply re-runs the same calculation the maker already ran will usually reach the same wrong answer. The check that actually works is a variance review — comparing this month’s total gross, total PF, total ESI, and headcount against last month, and asking for an explanation of every number that moved more than expected. You have this part right if your checker’s first question is always “what changed, and why,” not “let me recalculate this.”
Stage 4 — Approval and disbursement
Finance signs off on the funding, the bank file is generated directly from the validated payroll register, and payslips are released. This is the last point at which a caught error is inexpensive to fix.
Common mistake — Generating the bank upload file from a manually maintained list rather than directly from the payroll system’s validated output. Every manual hand-copy between the two is a fresh chance for a transposed account number.
Stage 5 — Provisioning
GL entries are posted for statutory payables and accrual accounts — covered in full in Part 2.
Stage 6 — Statutory remittance
PF, ESI, professional tax, and TDS challans are paid within the due dates that apply to that establishment and state.
Stage 7 — Return filing
ECR, ESI returns, Form 24Q and other applicable statutory returns are filed. Filing on time but with figures that don’t tie back to the disbursed payroll is itself a control failure — filed numbers should be reconciled against Stage 4 output before submission, not assumed to match.
Stage 8 — Reconciliation and closure
Disbursement, provisioning, and filing are tied out against each other, and the audit trail for the month is closed and archived.
Part 2 — Provisioning
Provisioning is where payroll processing meets the books of account. Even before a rupee is remitted to EPFO, ESIC, or the tax department, the liability for that month has already been earned and needs to be recognised in the financial statements. Getting this step right matters as much for audit readiness as getting the payslip right matters for the employee.
What gets provisioned each month
| Provision item | Nature | Basis of computation | Typical true-up point |
| Employer PF payable | Statutory liability, short-term | 12% of PF wages for the month | Reconciled against ECR filed the following month |
| Employer ESI payable | Statutory liability, short-term | 3.25% of gross wages for the month | Reconciled against ESI challan for the month |
| Professional tax payable | Statutory liability, short-term | State slab applied to gross salary | Reconciled against PT challan for the month |
| TDS payable | Statutory liability, short-term | Monthly deduction under Section 192 | Reconciled against TRACES deposit and quarterly 24Q |
| Bonus provision | Accrued liability, builds through the year | Statutory minimum (8.33%) or declared rate, spread monthly | Trued up against actual bonus computation and payment date |
| Gratuity provision | Long-term accrued liability | Indicative monthly accrual, ideally aligned to the latest actuarial valuation | Trued up at actuarial valuation date and on each exit |
| Leave encashment provision | Accrued liability | Leave balance × per-day wage rate, revalued monthly | Trued up on encashment, exit, or year-end |
How the entries flow

The provisioning journal voucher should be prepared directly off the final, checker-validated payroll register from Stage 4 — not a parallel estimate built separately in a spreadsheet. The same maker-checker discipline that applies to the payroll run itself applies here: the person preparing the JV should not be the person posting it to the GL.
| EXAMPLE — A bonus provision that quietly drifted A company provisions bonus every month at a flat 8.33% of eligible wages. Partway through the year, a business unit’s actual eligible headcount grows faster than payroll’s provisioning template is updated to reflect. By year-end, the provisioned bonus liability understates the actual statutory bonus payable by a meaningful margin — not because the rate was wrong, but because the wage base feeding the provision hadn’t been refreshed for four months of headcount growth. |
Practitioner note — Provisioning is not a set-and-forget entry. Re-check the wage base feeding each provision line whenever headcount, salary structure, or eligible-employee count moves materially — not just once a year at audit time.
Common mistake — Treating provisioning as a finance-only activity with no payroll sign-off. Finance can post the entry, but only payroll can confirm the wage base and headcount behind it are current — so the JV should carry a payroll countersignature, not just a finance one.
Part 3 — Payroll Controls
Controls exist to catch the error before it reaches an employee’s bank account or the general ledger, not to add paperwork for its own sake. The table below maps where errors typically originate in the processing cycle, back to the root cause and the control that actually closes the gap.
| Stage | Common error | Root cause | Control that closes it |
| Input freeze | A late change is quietly added after freeze | No formal reopen process; informal edits made directly to the input file | Freeze enforced technically (locked file); any reopen requires a named approver and is logged separately |
| Statutory calculation | PF/ESI computed on the wrong wage base | Salary structure not re-checked against the current wage definition | Annual salary-structure compliance check, repeated whenever a statutory rule changes |
| Checker validation | Error passes through unnoticed | Same person effectively checks their own work, or checker has no variance baseline | True second-person review against a month-on-month variance report, not a re-run of the same calculation |
| Disbursement | Wrong bank account or duplicate payment | Employee bank detail changes not synced from HRIS to the banking file before generation | Bank file generated directly from the validated HRIS record, never a manually maintained parallel list |
| Provisioning | Provisioned liability drifts from actual | Wage base or headcount feeding the provision not refreshed | Provision JV countersigned by payroll, not posted by finance alone |
| Remittance & filing | Challan amount does not match disbursed payroll | Filing prepared independently of the final payroll output, often from an earlier draft | Filing figures reconciled line-by-line against the disbursed register before submission |
| Reconciliation & closure | Month closed with open items untracked | No single owner for tying disbursement, provisioning and filing together | Named closure owner signs off only once all three are reconciled |
The pattern behind the pattern
Look across the root-cause column and one theme dominates: information that existed but was never captured in a form the next person in the chain could act on. Almost every control in this guide is, underneath the process language, a documentation control. Fixing the process without fixing the documentation habit behind it rarely holds beyond a month or two.
Post-freeze changes
Not every post-freeze change is avoidable — a genuine last-minute correction sometimes has to go in. What separates a controlled exception from a process breakdown is whether it is named, approved, and logged, or simply made.
Part 4 — The Monthly Payroll Calendar
A checklist at month-end tells you what should have happened. A calendar published at the start of the month tells every stakeholder — payroll, HR, sales, finance — what is expected of them and by when, before the pressure of the freeze date arrives. Publishing the calendar on Day 1 is itself a control: most late-input problems in Part 1 and Part 3 trace back to a function simply not knowing, or forgetting, when payroll needed their data.

The exact dates will vary by organisation, but the discipline is the same everywhere: publish the calendar before the month begins, circulate it to every input-providing function — not just within payroll — and treat each date on it as a commitment, not a suggestion.
What the calendar should carry
- The variable-input due date, and who in each function owns submitting it.
- The input freeze date, stated as a hard cut-off with the named exception-approval route for anything after it.
- The checker validation window, distinct from the freeze date — the checker needs real time, not the same afternoon.
- The approval and disbursement date, communicated to employees as the salary credit date.
- The provisioning entry date, so finance can plan the GL posting alongside month-end close.
- The remittance date, built in with enough buffer before the statutory due date to absorb a bank-file delay.
Publishing it well
Practitioner note — A calendar that lives only in the payroll team’s own tracker doesn’t do its job. Circulate it — email, HRMS notice, whatever reaches the sales and finance teams who owe payroll their inputs — on the first working day of the month, not the week before the freeze.
Common mistake — Building the calendar once a year and reusing it unchanged every month, regardless of weekends, holidays, or a shifted bank processing window. The dates need to move with the actual calendar, or the freeze date quietly becomes a Sunday.
Closing note
This guide has deliberately stayed inside the boundary of payroll processing itself — the cycle, the provisioning that follows it, the controls that protect it, and the calendar that paces it. Attendance, leave, and the statutory compliance framework sit just outside that boundary, and are worth their own dedicated treatment rather than a compressed summary here. Within its scope, though, the pattern is the same one worth repeating: almost no payroll error is truly unavoidable. Nearly all of them are a documentation or planning step that someone, somewhere in the chain, skipped.
Key Takeaway
Stay informed, adapt to changing business needs, and build strategies that help your organization move forward with confidence.