Payroll Processing in India: A Step-by-Step Guide

Payroll processing in India looks simple on paper: collect attendance, apply the salary structure, deduct what the law requires, and pay people on time. In practice, it is one of the most unforgiving operational processes a company runs. It happens every single month, it touches every employee, it involves multiple statutory authorities, and it has a hard deadline that cannot slip. A late invoice is an inconvenience. A late salary is a crisis.

This guide walks through the complete monthly payroll cycle as it is actually run in Indian companies — from the day you lock attendance to the day you close the books and file returns. It is written for HR managers, founders, finance leads, and payroll executives who want a repeatable system rather than a monthly scramble.

We will cover the payroll calendar, payroll inputs, salary structure logic, pro-rata and LOP calculations with worked examples, statutory deductions, the pre-payroll checklist, the payroll run and variance checks, approvals, bank disbursement, payslip publishing, post-payroll compliance, reconciliation, common errors, and when it is time to move off spreadsheets.

One important note before we begin: statutory rates, wage ceilings, thresholds, and due dates change. This guide explains the mechanics of payroll processing and deliberately avoids quoting specific rates or dates. Always verify current numbers with the relevant government portal or your compliance advisor before you run payroll.

What Payroll Processing Actually Means

Payroll processing is the end-to-end monthly cycle of converting employment data into accurate net pay, statutory contributions, and accounting entries — and then proving that you did it correctly.

It is useful to think of it as five distinct phases rather than one big task:

1. Input collection — gathering everything that affects pay this month.
2. Pre-payroll validation — checking those inputs before any calculation happens.
3. The payroll run — computing earnings, deductions, and net pay.
4. Review, approval, and disbursement — variance checks, sign-off, and money movement.
5. Post-payroll compliance and close — filings, payments, reconciliation, and accounting.

Most payroll failures are not calculation failures. Modern systems calculate correctly. Failures happen in phase 1 and phase 2 — somebody forgot to tell payroll about a resignation, a salary revision was approved on WhatsApp and never recorded, or attendance was locked before the night shift regularised their punches. Everything downstream inherits that error.

The discipline of good payroll processing is therefore less about arithmetic and more about cut-offs, ownership, and evidence.

The Payroll Calendar and Cut-Off Dates

Every organisation needs a published payroll calendar. Not a vague understanding — an actual document that says what happens on which date, and who owns it.

Defining your payroll period

Indian companies typically run one of three period conventions:

• Calendar month (1st to last day) — simplest, most common, and the easiest to reconcile with statutory filings that are month-based.
• Offset cycle (e.g. 21st to 20th) — gives the payroll team a buffer to process attendance before month end. Common in manufacturing, retail, and staffing.
• Split cycle — attendance from the 21st to 20th, but all other components on a calendar-month basis. This is the most confusing and the most error-prone; avoid it unless you have a genuine operational reason.

Whichever you choose, document it and stop debating it. Changing the payroll period mid-year creates a transition month that will haunt your reconciliation for a year.

Setting the cut-off

The cut-off date is the moment after which no input is accepted for the current cycle. Anything received later moves to next month as an arrear or adjustment. This is the single most valuable rule in payroll processing, and it only works if leadership backs it.

A practical cut-off structure for a calendar-month cycle with pay on the last working day:

Shift the dates to suit your pay date, but keep the shape: inputs close well before the run, the run happens before sign-off, and sign-off happens before money moves.

Building in buffers

Two buffers matter enormously:

• Bank holiday buffer. If your pay date falls on a Sunday or a bank holiday, decide in advance whether you pay early or late — and publish the policy. Most Indian employers pay early. Build a check into your calendar for months with clustered holidays.
• Correction buffer. Reserve at least one full working day between the trial run and the final run. Teams that schedule the run and the sign-off on the same day always end up approving something they have not read.

Payroll Inputs: The Real Source of Errors

Payroll inputs are every data point that changes what an employee is paid this month. Collecting them reliably is 70% of payroll processing.

The complete input checklist

Workforce and master data - New joiners: date of joining, salary structure, PAN, Aadhaar, bank account, UAN/PF details, ESI details where applicable, tax regime declaration - Exits: last working day, notice period served or shortfall, recovery items, leave encashment, full and final trigger - Transfers: location changes (affects professional tax and LWF), entity changes, cost centre changes - Salary revisions: effective date, new structure, whether arrears apply - Promotions and role changes affecting allowances or eligibility - Status changes: probation to confirmed, contract to permanent, full-time to part-time - Employees on long leave: maternity, sabbatical, unpaid leave, suspension

Time and attendance - Days present, days absent, weekly offs, holidays - Approved leave by type (earned, casual, sick, comp-off, maternity, paternity) - Loss of pay (LOP) days and half-days - Overtime hours by category, where applicable - Shift allowances, night shift differentials, on-call allowances - Attendance exceptions: missed punches, regularisations, biometric failures

Pay elements - Variable pay, incentives, and commissions with the approved payout schedule - Bonus payouts, retention payments, joining bonuses - Arrears for revisions with retrospective effect - Reimbursement claims: fuel, telecom, books and periodicals, meal cards, LTA - One-time payments: referral bonuses, awards, relocation support - Recoveries: salary advances, loan EMIs, notice pay shortfall, asset non-return, excess leave availed

Statutory and tax - Tax regime election (new vs old) for the year - Investment declarations and, at the appropriate point in the year, investment proofs - Previous employer income and TDS details for mid-year joiners - House rent details and landlord PAN where required - Perquisite information: company car, accommodation, interest-free loans, ESOP exercise events

Where inputs typically break

• Late resignation intimation. An exit communicated after the payroll run means an overpayment you now have to recover — awkward and sometimes unrecoverable.
• Verbal salary revisions. If the increment letter is not in the system before the cut-off, the revision moves to next month with arrears. Publish that rule.
• Reimbursement claims sent by email. Any input arriving outside the system is an input that will be missed. Force everything through one channel.
• Attendance treated as an HR problem. Attendance is a manager's responsibility. If managers do not approve on time, escalate on the calendar, not after the run.
• Mid-month joiners with incomplete documents. A joiner without a valid bank account or PAN creates a payment failure or a higher tax deduction. Make document completion part of onboarding day one.

The single-source-of-truth principle

Every input should have exactly one authoritative system of record. Attendance lives in the attendance module. Salary structures live in the HR master. Claims live in the expense module. Payroll reads from these; it does not maintain parallel copies.

The moment payroll starts keeping its own side spreadsheet of "actual" salaries because "the HR system is not updated", you have two versions of the truth and you will eventually pay from the wrong one.

Salary Structure: Earnings and Deductions Logic

You cannot process payroll correctly without a clean salary structure. Structures in India are usually expressed as an annual CTC that breaks into monthly components.

Typical earnings components

Typical deduction components

• Employee provident fund (PF) — employee's share, deducted from salary
• Employees' State Insurance (ESI) — employee's share, where the establishment and the employee are covered
• Professional tax (PT) — a state-level tax, applicable only in some states, with state-specific slabs
• Labour Welfare Fund (LWF) — applicable in certain states, usually a small amount at defined intervals
• Income tax (TDS) — computed on estimated annual taxable income
• Voluntary provident fund (VPF), NPS contributions, and other opted-in deductions
• Recoveries — advances, loans, notice shortfall, asset recovery
• Any court-ordered or garnishment deductions, where applicable

CTC vs gross vs net — get the vocabulary right

This distinction causes more employee escalations than any calculation error.

• CTC (Cost to Company) = everything the employer spends: gross salary + employer retiral contributions + insurance premiums + any other employer-borne cost.
• Gross salary = the sum of monthly earnings before deductions.
• Net pay (take-home) = gross salary − employee deductions.

A worked illustration for an employee with an annual CTC of ₹9,00,000:

Now the employee side for a full month worked:

The numbers above are illustrative only — PF wage definitions, ceilings, and PT slabs vary, and TDS depends entirely on the individual's declarations and regime choice. Use your own configuration. But the shape of the explanation is what employees need: CTC is not take-home, and the gap is made up of employer contributions and employee deductions.

Structure design principles

• Keep the number of components small. Every component you add is a component you must calculate, pro-rate, tax, and explain — every month, forever.
• Make special allowance the balancing figure so that structures scale cleanly across salary levels.
• Define clearly which components are pro-rated for partial months and which are not. Ambiguity here creates disputes.
• Decide the treatment of reimbursements up front: are they part of CTC, paid on claim, and do they lapse if unclaimed?
• Review structures at least annually against current wage-definition rules, especially the treatment of allowances for PF purposes.

Pro-Rata and LOP: Worked Examples

Partial-month pay is where payroll processing gets genuinely technical. Two calculations dominate: pro-rata for joiners and leavers, and loss of pay for unpaid absence.

Choosing your denominator

The most consequential decision is what you divide by. Three conventions are common:

1. Calendar days — divide by the actual days in the month (28, 29, 30, or 31).
2. Fixed 30 days — divide by 30 regardless of the month.
3. Payable days / working days — divide by the number of working days, excluding weekly offs and holidays.

Each produces a different answer for the same absence. Consider an employee with a monthly gross of ₹60,000 who has 2 LOP days in a 31-day month with 4 weekly offs and 1 holiday (26 working days):

None of these is universally "correct" — but you must pick one, document it in the payroll policy, apply it consistently, and be able to explain it. The most common practice for monthly-rated staff is the calendar-day method, because it keeps the annual total exact and handles February cleanly. The working-day method penalises absence more heavily and is generally used where the employment contract or wage-period rules require it.

A related and often forgotten rule: how do you treat a weekly off that is sandwiched between two LOP days? Some policies deduct the sandwiched holiday, some do not. Write it down.

Worked example 1 — mid-month joiner

Priya joins on 12 September. September has 30 calendar days. Her monthly gross is ₹75,000. The company uses the calendar-day method.

• Days payable: 12 September to 30 September = 19 days
• Per-day gross = 75,000 ÷ 30 = ₹2,500
• Payable gross = 2,500 × 19 = ₹47,500

Component-wise, with basic ₹30,000, HRA ₹15,000, special allowance ₹30,000:

PF and ESI are then computed on the pro-rated wages as per the applicable rules. Professional tax is generally a full monthly amount if the employee is on the payroll at any point in the month, but the treatment is state-specific — check yours. TDS is computed on projected annual income, so a part-month first salary usually results in a lower monthly TDS that catches up over the year.

Worked example 2 — exit with LOP and recoveries

Rahul resigns with a last working day of 14 November (30 days). His monthly gross is ₹90,000. He had 2 LOP days during the month, has 6 days of earned leave to be encashed, and owes ₹10,000 on a salary advance.

Step by step:

1. Days from 1 to 14 November = 14 days
2. LOP days in that period = 2
3. Payable days = 14 − 2 = 12
4. Per-day gross = 90,000 ÷ 30 = ₹3,000
5. Payable gross = 3,000 × 12 = ₹36,000
6. Leave encashment (assume computed on basic of ₹36,000/month, per-day basic = 36,000 ÷ 30 = ₹1,200) = 1,200 × 6 = ₹7,200
7. Total earnings = 36,000 + 7,200 = ₹43,200
8. Less: employee PF on eligible wages (illustrative ₹1,800), PT (₹200), TDS (illustrative ₹2,000), advance recovery (₹10,000)
9. Net payable = 43,200 − 1,800 − 200 − 2,000 − 10,000 = ₹29,200

Note the sequencing discipline: LOP is applied to the days within the served period, not to the full month. Getting this backwards — applying LOP to the full month and then pro-rating — double-counts the absence and is one of the most common exit-settlement errors.

Worked example 3 — arrears after a retrospective revision

Meera's salary was revised from ₹60,000 to ₹72,000 per month with effect from 1 April, but the revision letter was only processed in the July payroll.

• Monthly difference = 72,000 − 60,000 = ₹12,000
• Months of arrears (April, May, June) = 3
• Arrears payable = 12,000 × 3 = ₹36,000
• July salary at the new rate = ₹72,000
• Total July gross = 72,000 + 36,000 = ₹1,08,000

Two things to watch:

• Statutory recomputation. PF, ESI, and PT on arrears may need to be recalculated for the affected months, not just added to the current month. The rules differ by statute; confirm how your system handles arrear-period contributions.
• TDS smoothing. A large arrear in one month spikes taxable income. Good payroll systems recompute the annual projection so tax is spread across remaining months rather than deducted entirely in the arrear month. Employees should be told what happened; a sudden jump in TDS without explanation generates immediate escalations.

If an employee has LOP in a month for which arrears are being paid, the arrear must be pro-rated for that month too. Paying full arrears for a month in which the employee was on unpaid leave is a silent overpayment that rarely gets caught.

Statutory Deductions: What Payroll Must Handle

This section deliberately stays at the mechanics level. Rates, wage ceilings, and thresholds change — verify current values on the relevant government portals before configuring your system.

Provident Fund (PF)

• Applies to establishments meeting the prescribed employee-count threshold.
• Both employee and employer contribute a percentage of "PF wages", with the employer's share split between the provident fund and the pension scheme.
• A statutory wage ceiling exists; employers may contribute on actual wages above the ceiling or restrict to the ceiling, depending on policy — decide and apply consistently.
• Employees may contribute over and above the statutory rate through voluntary provident fund (VPF).
• Each covered employee needs a UAN, and it must be linked correctly. UAN errors are the number one cause of PF filing rejections.
• The definition of what constitutes "wages" for PF has evolved through judicial interpretation. Review your allowance structure periodically with your advisor.

Employees' State Insurance (ESI)

• Applies to establishments in notified areas above a size threshold, and only to employees whose wages fall below the prescribed wage limit.
• Both employee and employer contribute at prescribed percentages.
• ESI has defined contribution periods; an employee who crosses the wage limit mid-period generally continues to contribute until the end of that period. Configure this correctly or you will under-deduct.
• Employees need valid IP numbers and correctly recorded family details for benefits to work.

Professional Tax (PT)

• A state-level tax. Some states levy it; others do not.
• Slabs, amounts, and deduction frequency vary by state, and some states have different rules for particular months.
• The applicable state is generally the state of the employee's work location, not the head office. Multi-state employers must map every employee to a location and update it on transfer.
• Registration obligations exist at both employer and employee-deduction levels in most PT states.

Labour Welfare Fund (LWF)

• Applicable in some states only, usually with small employee and employer contributions.
• Often deducted at half-yearly or annual intervals rather than monthly — a frequent source of "why is my salary lower this month" queries.
• Eligibility can depend on wage level or employee category in some states.

Tax Deducted at Source (TDS) on salary

TDS is the most computation-heavy part of payroll processing:

1. Estimate the employee's annual taxable salary for the financial year.
2. Apply the employee's chosen tax regime.
3. Factor in eligible exemptions and deductions based on declarations (and later, verified proofs).
4. Include previous-employer income for mid-year joiners, where declared.
5. Add perquisite values where applicable.
6. Compute annual tax liability, subtract tax already deducted, and divide the balance across the remaining months.
7. Recompute every month as inputs change.

Practical points:

• Collect regime elections at the start of the financial year and treat changes carefully — the ability to switch is governed by rules that differ for salaried employees, so confirm the current position.
• Run a proof-collection window well before the year end so that the final quarter's TDS is not a shock.
• If proofs are not submitted, TDS must be recomputed without the claimed deductions. Communicate the deadline aggressively; the last-quarter tax spike is a predictable annual crisis you can prevent.
• Perquisites — company car, accommodation, interest-free or concessional loans, ESOP exercises — are frequently missed. Build a quarterly checkpoint with Finance to catch them.

Other obligations to keep on the radar

• Maternity benefit payments and their treatment in payroll
• Gratuity payouts at exit, where eligibility conditions are met
• Bonus payable under applicable law, and whether you pay it monthly or annually
• Minimum wages applicable to the state, industry, and skill category — a compliance area that is easy to breach at the entry-level end of the workforce
• Contract labour records, where you engage workers through contractors

Due dates for payments and returns differ by statute and change from time to time. Maintain a compliance calendar with the current dates and review it every quarter.

The Pre-Payroll Checklist

Run this before you press "process". It takes 30 to 60 minutes and it prevents the vast majority of payroll incidents.

Headcount and master data - [ ] Active employee count matches the HR system and the previous month's count ± known joiners and exits - [ ] All new joiners have: salary structure assigned, bank details validated, PAN captured, UAN/ESI where applicable, date of joining correct - [ ] All exits have: last working day recorded, payroll stop flag set, F&F triggered - [ ] No duplicate employee IDs or duplicate bank account numbers (a classic fraud and error signal) - [ ] Employees on long leave correctly flagged with the right pay treatment

Attendance and leave - [ ] Attendance cycle closed and locked for the period - [ ] All regularisation requests actioned — none pending - [ ] LOP days reconciled against the leave balance report - [ ] Overtime approved by managers, with hours within policy limits - [ ] Employees with zero payable days identified and confirmed as intentional

Pay elements - [ ] Salary revisions loaded with correct effective dates - [ ] Arrears calculated and reviewed line by line - [ ] Variable pay and incentive files received, approved, and matched to the plan - [ ] Reimbursement claims approved and within entitlement limits - [ ] Recoveries scheduled correctly, with remaining balances checked

Statutory - [ ] PF/ESI eligibility flags reviewed for new joiners and for employees crossing thresholds - [ ] Professional tax state mapping correct for all employees, including transfers - [ ] LWF month flagged if this is a deduction month - [ ] Tax declarations and any proof-verification status updated - [ ] Employees with pending or invalid PAN identified (higher deduction may apply)

Banking - [ ] Bank account numbers and IFSC codes validated - [ ] Accounts flagged from previous failed transactions corrected - [ ] Employees to be paid by an alternate mode identified and handled separately

Convert this into a signed checklist with a name against each item. A checklist nobody signs is a checklist nobody reads.

The Payroll Run and Validation

Running the trial payroll

Always run a trial (or "draft") payroll first. Never run a live payroll as the first computation of the month. The trial run produces the payroll register — the master output of payroll processing — which lists, for every employee: payable days, each earning component, each deduction, gross, total deductions, and net pay.

Variance analysis: the most valuable 45 minutes in payroll

Compare this month's payroll register to last month's, employee by employee, and investigate every difference. This single practice catches most errors before they reach a bank account.

Checks worth running every month:

Document the explanation for every material variance. This document is your audit trail and it takes five minutes to produce at the time — and five hours to reconstruct six months later.

Exception handling

Some situations always need manual attention:

• Negative net pay. Never push a negative to the bank file. Decide whether to reduce the recovery this month, carry it forward, or handle it separately, and record the decision.
• Employees with no bank details. Hold and pay separately once details are confirmed; do not guess.
• Off-cycle payments. Full and final settlements, emergency advances, and correction payments should run as clearly labelled off-cycle runs so the regular register stays clean.
• Retrospective exits. If an employee left last month and was paid, compute the recovery, document it, and coordinate with the manager before deducting.

Correcting and re-running

If the trial reveals errors, fix the input — not the output. Editing the register directly creates a payroll where the calculation cannot be reproduced from the inputs, which fails any audit. Fix the attendance record, the master data, or the claim, then re-run and re-check the variance report.

Approvals and Sign-Off

Payroll should never be released on one person's judgement. A minimal approval chain:

1. Prepared by — payroll executive who ran the cycle and produced the register and variance report.
2. Reviewed by — payroll manager or HR Ops lead who checks the variance explanations and exception list.
3. Approved by — Finance (funding, GL impact, statutory totals) and HR leadership (headcount, structures, exceptions).
4. Released by — a separate person or role who uploads the bank file, with maker-checker at the bank.

A simple RACI for monthly payroll processing

The key segregation-of-duties rule: the person who can change salary data should not be the person who releases the payment. In small companies where one person does both, compensate with a mandatory second-person review of the register before release.

What to sign off on

Approvers should receive a fixed pack, not a raw dump:

• Payroll summary: headcount, total gross, total deductions, total net, employer statutory cost
• Month-on-month variance summary with explanations
• Exception list with resolutions
• New joiner and exit list with amounts
• Arrears and one-time payment list with references to approvals
• Statutory liability summary

Keep the pack under five pages. Approvers who receive 400 rows of raw register data approve without reading, which defeats the control.

Bank Disbursement

Preparing the bank file

Once approved, generate the salary payment file in your bank's required format — commonly a structured CSV, a fixed-width text file, or a direct API/host-to-host integration. Typical fields include employee name, account number, IFSC, amount, and a payment reference or narration.

Checks before upload:

• Control total. The sum of the bank file must exactly equal the total net pay in the approved register. Reconcile to the rupee, every month, without exception.
• Record count. Number of rows must equal the number of employees to be paid.
• No zero or negative amounts. Remove and handle separately.
• Encoding and format. Special characters in names, extra header rows, and Excel silently converting long account numbers to scientific notation are perennial causes of rejection. Generate the file from the payroll system rather than hand-editing in a spreadsheet.
• Duplicate account numbers. Investigate before payment, not after.

Funding and timing

• Confirm the account is funded, including the buffer for statutory payments due shortly after.
• Understand your bank's cut-off time for same-day credit. Missing the cut-off by ten minutes moves the credit to the next working day.
• Use maker-checker at the bank. Whoever uploads should not be the person who authorises.
• Keep the payment confirmation and the UTR/transaction reference file — it is the evidence for any "I didn't get paid" query.

Handling failures

Some transactions will fail — closed accounts, name mismatches, incorrect IFSC after a bank merger. Have a defined process:

1. Download the bank return file the same day.
2. Notify affected employees immediately, before they notice.
3. Collect corrected details with proof (a cancelled cheque or bank statement header).
4. Reprocess as an off-cycle payment within a committed timeframe, typically 24 to 48 hours.
5. Update the master record so the same failure does not repeat next month.

Payslips and Employee Queries

Publishing payslips

Payslips should be published promptly after the salary credit — same day if possible. A payslip should clearly show:

• Employee identifiers: name, ID, designation, department, location
• Period, payable days, LOP days, and leave balances
• Each earning component with its amount
• Each deduction with its amount
• Gross, total deductions, and net pay
• Year-to-date figures for earnings, deductions, and tax
• Employer contributions (PF, and ESI where applicable), so employees can connect payslip to CTC
• Bank account (masked) and UAN/PF number

Publish through a self-service portal or app rather than email attachments. Portals give employees permanent access, remove the "please resend my March payslip" ticket category entirely, and avoid sending compensation data over email.

Managing the query window

Expect queries every month. Handle them systematically:

• Open a defined query window (say, five working days after payslip release) with a single intake channel — a ticket queue, not individual WhatsApp messages to the payroll executive.
• Categorise queries: LOP disputes, tax deduction questions, reimbursement not paid, arrears missing, deduction not understood.
• Publish an FAQ that pre-answers the top five categories. The single biggest query — "why is my take-home less than my CTC" — can be largely eliminated with a good CTC breakup document at the offer stage and a clear payslip.
• Commit to a response SLA and track it. Payroll queries left unanswered become manager escalations, then leadership escalations.
• Track query volume by root cause monthly. If tax queries spike in January, your proof-collection communication failed in November. Fix the upstream cause rather than answering the same question 200 times.

Correction policy

Publish a clear rule: genuine errors are corrected off-cycle within a stated timeframe (for material amounts) or adjusted in the next cycle (for small amounts). Define "material" with an actual number so the decision is not argued each time.

Post-Payroll Compliance and Filings

Payroll processing is not finished when salaries are credited. The compliance tail matters just as much, and it is where penalties live.

Typical monthly obligations:

• PF — deposit contributions and file the monthly electronic return with member-wise details
• ESI — deposit contributions and file the monthly return for covered employees
• Professional tax — deposit and file as per each applicable state's frequency (monthly, quarterly, or annual, depending on the state and employer size)
• TDS on salary — deposit tax deducted within the prescribed timeline and file the quarterly return; issue the annual salary TDS certificate to employees after the year end
• Labour Welfare Fund — deposit as per the state's prescribed frequency

Periodic and annual obligations:

• Quarterly TDS returns and correction statements
• Annual salary TDS certificates for employees
• Bonus payment and related registers, where applicable
• Statutory registers and muster rolls under applicable labour laws
• Returns required by shops and establishments legislation in the relevant state

Operational discipline that keeps this clean:

• Maintain a compliance calendar with the current due dates for every registration, refreshed at least quarterly.
• Assign a named owner and a backup for each filing.
• Save the challan, acknowledgement, and return file for every filing in a structured folder by month and statute. Auditors will ask, and searching an inbox is not a system.
• Reconcile what was deducted, what was deposited, and what was reported. These three numbers should be identical. When they are not, fix it in the same month — carried-forward mismatches compound.
• Track multi-state registrations actively. Remote and hybrid work has quietly created PT and LWF obligations in states where companies never had an office, and it is a growing source of unexpected exposure.

Reconciliation and Month Close

The three reconciliations that matter

1. Payroll register to bank payment Total net pay in the register must equal total salary debits in the bank statement, adjusted for any failed and reprocessed payments. Any difference must be explained to the rupee.

2. Payroll to general ledger Salary cost, employer contributions, statutory liabilities, and recoveries must post correctly to the GL. Confirm: - Salary and wage expense matches the register's gross plus employer contributions - Statutory payable accounts are credited with the amounts deducted and the employer's share - Those liability accounts are cleared when the payments are made — a liability account that keeps growing means a filing or a payment was missed - Recoveries reduce the correct advance/loan control accounts

3. Statutory deducted vs deposited vs filed For each statute, the amount deducted in payroll, the amount paid to the authority, and the amount reported in the return should reconcile. Build this as a standing monthly schedule.

A month-close pack worth keeping

Archive the following for every payroll month:

• Final payroll register (locked)
• Variance report with explanations
• Approval evidence (email, workflow record, or signed pack)
• Bank file, payment confirmation, and return/failure file
• Statutory computation sheets, challans, and return acknowledgements
• GL posting journal and reconciliation statements
• Off-cycle and F&F payment records
• Exception log with resolutions

Store it in a fixed folder structure by financial year and month. When an auditor, a labour inspector, or a departing employee's lawyer asks a question three years later, this pack answers it in minutes.

Preparing for a payroll audit

A payroll audit — internal, statutory, or a due-diligence review during fundraising or acquisition — typically tests:

• Existence: does every employee paid actually exist and work here?
• Authorisation: was every salary, revision, and one-time payment approved by someone with authority?
• Accuracy: does the computation follow the documented policy and the applicable law?
• Completeness: was everyone who should have been paid, paid?
• Compliance: were deductions correct, deposited on time, and reported correctly?
• Segregation of duties: can one person change data and release money?

If you produce the month-close pack described above every month, a payroll audit becomes a document-retrieval exercise rather than a three-week reconstruction project.

Common Payroll Errors and How to Prevent Them

Beyond the mechanics, three cultural fixes prevent most repeat errors:

1. Make the cut-off real. Every exception granted teaches the organisation that the cut-off is negotiable.
2. Run a blameless post-mortem after every payroll incident. Ask what process allowed it, not who did it. Payroll people who fear blame hide errors, and hidden errors compound.
3. Keep a payroll issue log. Every month, review the previous month's issues and confirm the process change that prevents recurrence actually happened.

When to Move From Spreadsheets to Payroll Software

Spreadsheets work at very small scale. They stop working sooner than most founders expect.

Signals you have outgrown spreadsheets

• Payroll processing takes more than two working days a month
• More than one person maintains "the" payroll file, or there are multiple versions of it
• You operate in more than one state (PT, LWF, and minimum wage complexity multiplies)
• Headcount is above roughly 25 to 50 employees
• You have variable pay, shift allowances, or overtime that changes every month
• Employees email to ask for payslips, and someone generates them manually
• Statutory returns are prepared by re-keying data from the payroll sheet
• You have had at least one payroll error that required an apology
• An audit or due diligence is coming and you cannot produce an approval trail
• Attendance and leave live in a different system with no automated link to payroll
• The person who understands the payroll formulas is a single point of failure

The last one deserves emphasis. Spreadsheet payroll is usually one person's undocumented logic. If that person resigns, is ill, or simply forgets which of 14 nested formulas handles February, the risk is not theoretical.

What good payroll software should do

When you evaluate a system, test these specifically:

• Integrated attendance and leave, so LOP flows into payroll automatically instead of being typed in
• Configurable salary structures with your own components, pro-rata rules, and eligibility conditions
• Automated statutory computation for PF, ESI, PT, LWF, and TDS, with state-wise handling and timely updates when rules change
• Arrears and retrospective revisions handled natively, including statutory recomputation
• Full and final settlement as a built-in workflow, not a manual spreadsheet
• Approval workflows with a genuine audit trail showing who approved what and when
• Variance and exception reports out of the box
• Bank file generation in your bank's format, with control totals
• Employee self-service for payslips, tax declarations, proof upload, and reimbursement claims
• Statutory reports and return-ready files for each filing
• GL export mapped to your chart of accounts
• Role-based access and data security, since payroll is your most sensitive dataset
• Complete history, so you can reproduce any past month exactly as it was run

Making the transition

Move at a financial-year boundary if you can, or at least at a quarter boundary. The migration checklist:

1. Clean the employee master first — a migration will faithfully reproduce your existing data errors.
2. Migrate year-to-date earnings, deductions, and TDS so tax computation continues correctly.
3. Carry over leave balances and loan/advance balances with opening figures.
4. Run parallel payroll for at least one month: process in both the old and new systems and reconcile employee by employee. Do not skip this.
5. Investigate every difference in the parallel run. Differences are usually configuration issues you would otherwise discover in production.
6. Cut over only after a clean parallel month, and keep the old records archived and accessible.

A Monthly Payroll SOP You Can Adopt

Bringing it together, here is a compact standard operating procedure for payroll processing. Adjust dates to your cycle.

(T = pay date.)

Print it. Put a name against every row. Review it once a quarter and adjust based on what actually went wrong.

Frequently Asked Questions

What is the payroll processing cycle in India?

The payroll processing cycle is the repeating monthly sequence of collecting payroll inputs (attendance, leave and LOP, joiners, exits, revisions, arrears, claims, and variable pay), validating them against a pre-payroll checklist, computing earnings and statutory deductions, reviewing the payroll register through variance checks, obtaining approvals, disbursing salaries through the bank, publishing payslips, making statutory payments and filings, and finally reconciling and closing the month. Most Indian companies run this on a calendar-month basis with a hard input cut-off roughly five to seven days before the pay date.

How is loss of pay (LOP) calculated?

LOP is calculated by determining a per-day rate and multiplying it by the number of unpaid days. The per-day rate depends on the denominator your policy specifies: total calendar days in the month, a fixed 30 days, or the number of working days. For an employee with a gross of ₹60,000 and 2 LOP days in a 31-day month, the deduction is ₹3,870.97 under the calendar-day method, ₹4,000 under the fixed-30 method, and ₹4,615.38 under a 26-working-day method. Choose one method, document it in your payroll policy, and apply it consistently across all employees.

What is the difference between CTC, gross salary, and net pay?

CTC is the total annual cost the employer bears, including gross salary plus employer contributions such as PF and gratuity provisions and any insurance premiums. Gross salary is the sum of monthly earnings before deductions. Net pay, or take-home, is gross salary minus employee deductions such as PF, professional tax, and TDS. The gap between CTC and take-home is normal and expected — most of it is money going into the employee's own retirement account or to tax, not money disappearing.

What are the main statutory deductions in Indian payroll processing?

The common ones are provident fund (PF), Employees' State Insurance (ESI) where applicable, professional tax (a state-level tax levied only in some states), Labour Welfare Fund in certain states, and TDS on salary income. Applicability depends on the size of the establishment, the employee's wage level, and the work location. Rates, wage ceilings, and thresholds change from time to time, so verify current figures with the relevant government portal or your compliance advisor before configuring payroll.

How should arrears be handled in payroll?

Arrears arise when a salary revision takes effect from a past date but is processed later. Calculate the monthly difference, multiply by the number of affected months, and pay the total in the current cycle — but pro-rate for any month in which the employee had loss of pay. Statutory contributions may need to be recomputed for the arrear period rather than simply added to the current month, and TDS should be recalculated across the remaining months of the year so the employee is not hit with the entire tax impact in one payslip. Always tell employees when a large arrear affects their tax deduction.

What should a pre-payroll checklist include?

At minimum: headcount reconciliation against the previous month, complete data for all new joiners, payroll stop flags for all exits, closed and locked attendance with no pending regularisations, LOP reconciled against leave balances, salary revisions loaded with correct effective dates, arrears reviewed, variable pay and claims approved, PF/ESI eligibility flags checked, professional tax state mapping validated, tax declaration status updated, and bank details verified with no duplicates. Make it a signed checklist with a named owner per item.

How do you check that a payroll run is correct before paying?

Run a trial payroll and compare the register to the previous month, employee by employee. Investigate every net pay variance beyond a threshold such as ±10%, reconcile headcount as opening plus joiners minus exits, flag zero and negative net pay, review any newly added bank accounts, compare statutory totals per head against last month, and match arrears and reimbursements to their approvals. Document the explanation for every material variance. This variance review typically catches more errors than any other single control.

When should a company move from spreadsheets to payroll software?

When payroll processing takes more than a couple of days a month, when you operate across multiple states, when headcount crosses roughly 25 to 50 employees, when variable pay or overtime changes monthly, when statutory returns are prepared by re-keying data, when you cannot produce an approval trail for an audit, or when the payroll logic exists only in one person's head. Migrate at a financial-year or quarter boundary, carry over year-to-date figures and leave balances, and run at least one month of parallel payroll before cutting over.

Who should approve payroll?

Payroll should have at least three distinct roles: a preparer who runs the cycle, a reviewer who checks variance explanations and exceptions, and an approver from Finance and HR leadership who signs off on totals and exceptions. Payment release should sit with a separate person, with maker-checker at the bank. The core control is segregation of duties — the person who can change salary data must not be the person who releases the payment. In very small teams, compensate with a mandatory second-person review of the payroll register before release.

Conclusion: Make Payroll Boring

The goal of payroll processing is not excellence in the heroic sense. It is boredom. A well-run payroll cycle should be predictable, documented, repeatable, and slightly dull — the same steps, in the same order, with the same checks, every month.

That predictability comes from five things:

1. A published calendar with real cut-offs that leadership actually enforces.
2. Single sources of truth for attendance, master data, and claims, feeding payroll automatically.
3. A pre-payroll checklist that is signed, not assumed.
4. Variance analysis before every payment, with explanations recorded.
5. A month-close pack archived every cycle, so compliance and audit are retrieval exercises rather than reconstruction projects.

Everything in this guide can be run on spreadsheets if you are small enough and disciplined enough. But the moment your headcount grows, your states multiply, or your pay components get complex, the manual version stops scaling — and the failure mode is not a slower payroll, it is a wrong one.

If your payroll cycle currently involves several spreadsheets, a WhatsApp group, and one person who knows how it all works, it is worth seeing what an integrated system feels like. CozyHR brings attendance, leave, salary structures, statutory computation, approvals, bank files, payslips, and employee self-service into a single payroll cycle — so the monthly run becomes a process you follow rather than a problem you solve.

Take a look at CozyHR and run your next payroll cycle with everything in one place. Your future self, on the 28th of next month, will thank you.

This guide explains payroll processing mechanics and is not legal, tax, or compliance advice. Statutory rates, wage ceilings, thresholds, and due dates change periodically — always verify current requirements with the relevant government authority or your professional advisor before processing payroll.