Skip to content

How to run payroll in 7 steps (without month-end panic)

A repeatable seven-step payroll process for Indian companies: freeze inputs, check data, apply attendance, calculate, review, approve and lock, then pay and file.

Saralix Team5 min read
On this page

Most payroll problems are not calculation problems. They are sequencing problems: someone changes a salary after the numbers were checked, a joiner is missed because the form arrived late, or the bank file is generated from a version nobody approved. A fixed sequence, run the same way every month, removes most of that. Here is a seven-step process that works for a team of ten or a team of a thousand.

Statutory rates mentioned here (PF at 12% on wages capped at Rs 15,000, ESI at 0.75% and 3.25% up to Rs 21,000 gross) are those we understand to be current. Verify them against the latest notifications.

Step 1: Set the payroll month and the cut-off

Decide the payroll period (a calendar month is the norm) and, just as important, the cut-off date after which changes wait for next month. A typical cut-off is two to five working days before the pay date. Publish it in your HR calendar and in the company chat. Everything that arrives after the cut-off, such as a late leave application or a new joiner form, is handled next month or as an off-cycle payment, on purpose.

Why it matters: a payroll with no cut-off is a payroll that is never finished.

Step 2: Check the inputs

Before calculating anything, verify the master data that drives the calculation:

  • Joiners: date of joining, salary structure assigned, bank account, PAN, and UAN where applicable.
  • Exits: last working day, notice-period status, and whether full and final settlement is being processed separately.
  • Revisions: new salary effective dates, and whether they include arrears.
  • Missing data: anybody without a bank account or PAN will cause a failed payment or higher TDS.

Fix these now. It is far cheaper to correct a bank account before the file is created than to retry a failed payment next week.

Step 3: Bring in attendance and leave

Pull in the month’s attendance, approved leave and holidays. Convert them to paid days and loss of pay (LOP) days. Two policies need to be written down and applied consistently:

  • Per-day rate. Many companies divide monthly gross by the calendar days in the month, others by a fixed 26 or 30. Pick one and document it. The choice changes LOP amounts.
  • Pending items. Attendance corrections or leave requests still waiting for approval should be resolved or consciously deferred. A payroll built on unapproved data is a payroll you will have to reopen.

Overtime, where you pay it, should be approved hours multiplied by your overtime rate. Establishments covered by the Factories Act must pay double the ordinary rate. Check what applies to you, and remember overtime is generally part of ESI gross wages but not PF wages.

Step 4: Calculate

Run the calculation for the whole population. For each employee, the system should:

  1. Prorate fixed pay for paid days.
  2. Add one-time earnings (incentives, arrears, bonus).
  3. Compute statutory deductions: PF on capped wages, ESI where gross is within the ceiling, professional tax per the employee’s work state, labour welfare fund where applicable.
  4. Compute TDS from the projected annual income under the employee’s chosen regime.
  5. Subtract other deductions such as loan instalments and recoveries.
  6. Add reimbursements that are due.

Do the calculation once, on frozen inputs. If you have to change an input, recalculate everything, not only the affected employee.

Step 5: Review exceptions

This is the step that separates careful payroll from lucky payroll. Do not scan 200 payslips. Look at exceptions:

  • Net pay up or down more than a set percentage from last month.
  • New joiners and exits in the period.
  • Employees whose net pay is zero or negative after deductions.
  • Anyone paid below the applicable minimum wage.
  • Duplicate bank accounts across employees.
  • Large one-time payments.

For each exception, write a one-line reason. Keep that note with the payroll file. It becomes your audit trail, and it makes next month’s review faster.

Step 6: Approve and lock

Payroll should have a maker and a checker. The person who prepares the run should not be the person who approves it. That is not bureaucracy: it is the single cheapest fraud and error control you can add.

On approval, lock the payroll. Locking means nobody can edit the numbers without a recorded reopening, with a reason. Payslips are generated from the locked data so they never change afterwards. If you must reopen, regenerate everything downstream, including compliance files and the bank file.

Step 7: Pay, distribute and file

With a locked payroll you can finish the month:

  • Create the bank file in the format your bank accepts, check totals against the payroll register, and upload. Hold the salary of anyone whose details are incomplete rather than guessing.
  • Publish payslips to employees by email or a portal. Employees should not need to ask HR for a copy.
  • Reconcile payments. When the bank returns a status, mark payments as paid or failed and retry the failures.
  • Record statutory liabilities and file: PF and ESI by the 15th of the next month, TDS deposit by the 7th, professional tax and LWF per state schedule, and quarterly 24Q.
  • Post to accounts using the payroll summary by department or cost centre.

A calendar you can copy

Day of month Task
20th Cut-off for joiners, exits and revisions
22nd Attendance and leave locked
24th Calculate and review exceptions
25th Approval and lock
26th to 28th Bank file, payments, payslips
7th (next month) TDS deposit
15th (next month) PF and ESI

Adjust the dates to your pay day, but keep the order.

Common failure points

  • No cut-off: changes keep arriving, and the run is never final.
  • One person does everything: errors are not caught because nobody else sees the numbers.
  • Reopening quietly: edits after approval with no reason recorded.
  • Statutory files built outside payroll: numbers in the challan differ from the register.
  • No exception notes: the same questions are asked every month.

Where software fits

Software cannot fix the sequence, but it can enforce it. In Saralix the payroll run is a seven-step wizard that follows this order: payroll month, input checks, attendance and LOP, calculate, review, approve and lock, then payslips and the bank file. Whoever calculates cannot approve, and every action is audited. Whatever you use, the principle is the same: do the steps in order, and do not let later steps change earlier decisions without a trace.

Free up to 10 employees

Run your first payroll free.

Attendance, leave, payroll and PF, ESI, PT and TDS compliance in one place. See the plans, or ask for a walkthrough.