The monthly payroll process, step by step

Payroll feels chaotic when it is a monthly scramble and calm when it is a repeatable process. The difference is not the tool alone; it is a disciplined cycle that the same person can run the same way every month. Here is a five-stage cycle that works for mid-market companies.

Stage 1: Inputs

Payroll quality is set here, before any calculation happens. Freeze attendance and leave for the period, then gather every variable input:

• New joiners and their prorated first month.
• Exits and their full and final settlements.
• Salary revisions effective in the period.
• Loss of pay from unapproved absences.
• Arrears from backdated changes.
• Reimbursements, incentives and one-time payments.
• Loan and advance EMIs to recover.

A missing input here becomes a correction later, so the freeze and the checklist matter.

Stage 2: Compute

Run the calculation: apply each employee's salary structure, compute gross, then statutory deductions (PF, ESI, PT and TDS) and other deductions. Loss of pay should reduce both the pay and the statutory base correctly, not just the net. Arrears should recompute cleanly against the earlier period.

Stage 3: Verify

This is the stage teams skip and regret. Before anyone is paid, review the run:

Check	Why it matters
Net variance versus last month	Catches structure and LOP errors
New joiners and exits	Confirms proration and F&F correctness
Statutory deductions present	Prevents shortfalls
Minimum-wage floor	Prevents underpayment
Large one-off movements	Catches data-entry errors

A good verify step compares this month's net for every employee against last month, and asks a human to explain the biggest movements.

Stage 4: Approve

A single sign-off gate between verification and payment creates accountability. One named approver confirms the run is reconciled and authorises payment. This one control prevents a surprising number of errors, because it forces a final look.

Stage 5: Publish

Once approved, generate the outputs:

• The bank file (NEFT or RTGS) for disbursement.
• Payslips for employees.
• The GL journal for finance.
• The statutory returns and challans (ECR, ESI, PT, and the TDS challan), filed by their due dates.

Building it repeatable

The more of this the system does automatically, the fewer late nights and the fewer errors. The goal is a cycle where inputs flow in from attendance and leave, computation is one click, verification is a clear grid, sign-off is deliberate, and outputs are generated rather than assembled.

Common mistakes to avoid

• Not freezing attendance before computing.
• Skipping the verify step.
• No single approver, so no accountability.
• Missing a statutory due date after disbursement.

Frequently asked questions

When should payroll be locked? After sign-off; later changes go into the next cycle or an off-cycle run.

What is an off-cycle run? A separate run for a held employee or a correction, outside the main monthly cycle.

How do we handle a held salary? Hold at verify with a reason, pay the rest, and settle the held employee in an off-cycle run.

Key takeaways

• Payroll is a five-stage cycle: inputs, compute, verify, approve, publish.
• Freeze inputs and check LOP and joiners and leavers carefully.
• Verify by comparing net to last month before paying.
• A single sign-off gate creates accountability.

NeevHR runs exactly this five-stage cycle, with a verify grid that compares net movements, a sign-off gate, and ready outputs for the bank and the authorities.