Key takeaways
- Payroll errors in growing Indian companies stem from inputs arriving late from scattered sources, not from wrong salary formulas.
- A payslip subtracts loss of pay from basic, HRA and allowances, then deducts PF, ESI, professional tax, TDS and advances.
- Maintain one employee master with joining date, salary structure, bank details, PAN, KYC, UAN and ESI number, collected at joining.
- Define basic, allowances, overtime and incentives in writing and have your CA confirm which components count as PF and ESI wages.
Managing payroll for an Indian company means getting four inputs right before every run: attendance, leave, salary structures and statutory deductions. It also means filing the PF, ESI, professional tax and TDS outputs that follow the run. Most of the pain sits in the inputs.
Picture a 60-person packaging unit in Pune on the 29th. The accountant is still matching the muster roll against three supervisors' WhatsApp messages about who took a half-day. Overtime is in a notebook, and two new joiners have no PAN on file. The PF figures also have to agree with a salary register nobody updated after the April increments. Salaries go out on the 1st, but with a list of corrections that carries over into next month.
This guide sets out the steps, checks, filings and tools that break that cycle.
Why payroll goes wrong in growing Indian companies
Short answer: Payroll goes wrong in growing Indian companies because its inputs arrive from too many places too late, not because the salary formula is wrong. Attendance sits with supervisors, leave approvals sit on managers' phones and advances sit with the owner, so every branch or shift adds another hand-off where a figure can be mistyped.
Payroll breaks because its inputs come from too many places too late, not because the salary formula is wrong. Attendance sits with site supervisors and leave approvals sit in managers' phones. Advances sit with the owner, and statutory deductions sit in a spreadsheet the CA last touched at year-end.
Whoever runs payroll spends the last week of the month collecting these pieces rather than calculating. The trouble grows with every new branch, shift pattern or batch of contract workers.
A garment unit in Tiruppur with 40 operators on piece rates has a very different month-end from a 15-person software agency on fixed salaries. Yet both usually run on the same mix of registers and memory. Each manual hand-off is a place where a figure gets mistyped, a leave gets missed, or an employee who left mid-month gets paid in full.
How a payslip is built up
Short answer: A payslip starts with the earnings in the appointment letter, then subtracts unapproved absence, statutory contributions, tax and recoveries. Basic, HRA and allowances less loss of pay give gross earnings; employee PF, ESI where applicable, professional tax and labour welfare fund where levied, TDS and advance instalments then come off to leave net pay.
A payslip starts with the earnings agreed in the appointment letter. It then subtracts pay for unapproved absence and deducts statutory contributions, tax and any recoveries. Laying it out line by line shows which figures come from attendance, which come from the salary structure, and which depend on rules your CA should confirm.
How one payslip is built up, line by line LineWhat it isRef Basic salaryAs per the appointment letterA House rent allowanceCompany-defined; often linked to basicB Other allowancesConveyance, special allowance, overtime, shift allowance and similarC Loss-of-pay deductionPay for days absent without approved leave, taken from attendanceD Gross earningsA + B + C − DE Employee PF contributionStatutory rate applied to PF wagesF Employee ESI contributionApplies only below the wage ceilingG Professional taxSet by the state; not levied in every stateH Labour welfare fundEmployee share, only in states that levy itI TDSAs per the employee's chosen tax regime and declarationsJ Advance recoveryThis month's scheduled instalment of any salary advance or loanK Net payE − (F + G + H + I + J + K)Professional tax is not levied in every state, and labour welfare fund applies only in some. Rates and ceilings for PF, ESI, PT and LWF are set by statute and change over time. Check the current EPFO, ESIC and state notifications with your CA before running payroll.
Payroll management India: steps to set up a process that holds every month
Short answer: Set up payroll by fixing inputs first and calculations second. Build one employee master with joining date, salary structure, bank details, PAN, KYC and UAN, define salary components in writing with your CA, track state minimum wage revisions, and capture attendance at the source, so each monthly run becomes a review of exceptions.
Set up payroll by fixing your inputs first and your calculations second. When the employee master, salary structure, attendance and leave are clean before the month starts, the run becomes a review of exceptions. Nobody has to rebuild the month from registers and messages.
Build one employee master. Every employee needs a single record covering:
- Joining date
- Salary structure
- Bank details
- PAN
- Aadhaar-based KYC
- UAN and ESI number, where applicable
Collect these at joining, not when the first challan is due.
Define salary components clearly. Split basic, allowances, overtime and incentives in writing, because statutory contributions are calculated on specific wage heads. Ask your CA to confirm which components count as wages for PF and ESI. That decision depends on your business, and software cannot make it for you.
Track minimum wage and VDA revisions. State governments notify minimum wage revisions, and many schedules include a variable dearness allowance that is revised from time to time. When a notification applies to your workers, update the affected salary structures from the effective date it states. If you skip this, the next run will underpay without anyone noticing.
Capture attendance at the source. Staff may work at a shop counter, in a warehouse or on field visits. Either way, attendance should be recorded where the work happens. GPS-based punching from a phone removes the month-end job of retyping registers.
Move leave out of WhatsApp. Requests and approvals should land in the same system that calculates salary. That way, an approved leave adjusts pay without anyone copying it across.
Fix a monthly calendar. Pick an attendance cut-off date, a review day for the owner or finance head, and a payout date. Then hold everyone to it, including the managers who send late approvals.
What gets filed after payroll runs
Short answer: After payroll runs, a company files PF and ESI contributions, pays professional tax to the state where it applies, and deposits TDS deducted from salaries. Each filing draws on figures from the same run, so a salary register left stale after April increments will push mismatched numbers into every challan and return.
Each payroll run produces statutory outputs:
- A PF electronic challan-cum-return
- An ESI contribution filing
- A professional tax return in states that levy it
- TDS returns for salaries
- Form 16 at year-end
HR usually prepares the contribution data, while the CA typically owns the tax filings. Agree that split in writing.
Who owns each output:
- PF ECR: HR owns this. HR prepares the electronic challan-cum-return from the payroll register and uploads it on the EPFO employer portal, then pays the challan. The CA may review it, but the data comes from HR.
- ESI contribution: HR owns this. HR files employee-wise contributions on the ESIC portal for everyone covered and pays the amount due.
- State PT return: Ownership is shared, depending on your setup. Where the company holds a PT registration, HR supplies the deduction summary. Either HR or the CA files the return, according to the state's procedure and whoever holds the login.
- TDS return on salaries: The CA owns this. The CA files the quarterly return using the TDS figures and employee PAN details from payroll. HR's job is to make sure the PAN data and deductions are correct before it goes out.
- Form 16: Both are involved. The CA generates it from the filed TDS data after the financial year closes. HR checks the details and distributes it to employees, including those who left during the year.
Your CA will confirm the current due date for each filing. Put those dates on the same calendar as your payout date, so filing is planned rather than remembered.
Leavers and contract workers
Short answer: Leavers and contract workers need their own checks before every run, because they are where overpayments and missed deductions hide. An employee leaving mid-month should be paid only for days worked, with outstanding advances recovered, while contract workers need attendance and statutory details recorded, whether supplied directly or through a contractor.
Two groups fall outside the normal monthly run. Employees who leave need a full-and-final settlement that closes every pending earning and recovery. Workers supplied by a contractor are paid by the contractor, but the principal employer still has to see proof that their wages and contributions were paid.
Full-and-final settlement. Start from a confirmed last working day, then pay salary up to that date. Add leave encashment as your policy allows, and gratuity where the employee is eligible. Recover any notice shortfall, outstanding advance or company asset. Apply TDS to the final payment.
After the settlement, mark the exit on the EPFO and ESIC portals so the employee's records close cleanly. Then issue the settlement statement and relieving letter. Some state laws set a timeline for paying final dues, so confirm the one that applies to you with your CA.
Contract labour. Suppose a facility-management agency supplies your housekeeping and security staff. The agency pays them, but as principal employer you can be held liable if their wages or PF and ESI contributions go unpaid.
Ask the contractor every month for proof:
- The wage register
- Bank payment records
- PF and ESI challans covering the workers deployed at your site
Payroll software for your own staff does not cover this, because those workers are not on your payroll. Keep a separate monthly check for contractor compliance.
Manual payroll versus software: what actually changes
Short answer: Software changes where payroll inputs come from, not the salary rules themselves. Attendance, leave and advances flow into one system instead of registers and WhatsApp messages, so the month-end becomes a review of flagged exceptions; the CA still decides which components count as wages for PF and ESI, because software cannot make that call.
The main difference is where errors get caught. In a manual process they surface after payday, when an employee complains about a short credit. With software they surface before payday, when a figure fails to match an attendance record, a statutory number is missing, or a bank account has changed.
Done manually, the run looks like this:
- The admin exports attendance from a biometric device or copies the muster roll.
- Last month's salary sheet is opened and its formulas edited.
- Leave deductions are added by hand.
- PF and ESI are calculated in another sheet.
- Bank transfer details are typed into the net-banking portal.
Each of those is a copy-paste step, and each can drift without anyone noticing.
With salary management software, attendance and approved leave already sit against each employee, so gross pay is computed from them directly. Statutory deductions follow rules configured once. The platform also flags gaps such as a missing UAN or a bank account that changed mid-month.
The payout file and payslips come from the same run as the register. All three match unless someone edits one of them by hand afterwards.
Software does not fix everything, though. A wrong salary structure will be calculated wrongly every month, only faster. It will not tell you whether your contractor's workers have been paid their dues. It also does not replace your CA's review of TDS on salaries.
A 10-person studio with fixed salaries, no overtime and one office can run payroll on a well-kept spreadsheet and a monthly CA check. Automating payroll starts to pay off once you have shifts, multiple sites, variable pay or frequent joiners and leavers.
An illustrative example: a pharmacy chain in Nagpur
Short answer: An illustrative pharmacy chain in Nagpur, with several outlets and staff on rotating shifts, shows how scattered inputs cause errors. Each store manager sends attendance separately for month-end reconciliation; once counters record attendance into one system, head office reviews exceptions instead of rebuilding every store's month.
This example is an illustrative composite, built from situations common to small multi-branch retailers rather than one named customer. It shows how branch-level attendance, shift allowances and mid-month exits create payroll errors. It also shows how moving those inputs into one system changes the owner's month-end work.
Picture a pharmacy owner in Nagpur with three outlets and about 30 people: pharmacists, counter staff and two delivery riders. Each branch manager keeps a paper attendance register and sends a photo of it to the owner's son. He handles payroll on the 28th of every month.
His problems are specific:
- One branch runs two shifts, and the register does not show which shift a person worked, so night allowance is paid on trust.
- Delivery riders take half-days that only the branch manager knows about.
- A pharmacist who resigns mid-month is paid in full because nobody tells the son until the 3rd.
- ESI deductions are worked out on a separate sheet, and the totals sometimes fail to match the salary register.
After moving to AnudaHRM, staff punch in by phone at their outlet location, with a shift code attached to each punch. Riders apply for leave in the app in Marathi or Hindi, and the branch manager approves it there.
On the 28th, the son reviews a list of exceptions instead of rebuilding the month from photographs. That list covers missed punches, unapproved absences and exits. He still sends the statutory summary to the CA before filing, a step worth keeping.
Pre-run payroll checklist
Short answer: Before each payroll run, confirm that attendance and leave are approved, new joiners have PAN, bank details and UAN on file, leavers are marked with their last working day, overtime and advances are entered, and salary structures reflect any increments or notified minimum wage revisions. Then compare totals against last month and investigate unexplained changes.
Run through this list two or three days before your payout date. It targets input errors such as missing employee data, unsettled leave, unscheduled recoveries and outdated wage rates. Left unchecked, these reach employees as short or incorrect salary credits and turn into complaints on payday.
- Joiners and leavers: every new employee has bank details, PAN, KYC and statutory numbers. Every exit has a recorded last working day and a full-and-final settlement in progress.
- Attendance closed: missed punches are resolved and the cut-off date has passed.
- Leave settled: pending requests are approved or rejected, not left hanging.
- Variable pay entered: overtime, incentives, piece-rate output and shift allowances are in, with someone's sign-off.
- Advances and loans: this month's recovery amounts are scheduled.
- Salary revisions: any increment or structure change is effective from the correct date.
- Wage notifications: any minimum wage or VDA revision notified by the state has been applied to the affected structures.
- Statutory check: PF, ESI, professional tax, LWF where applicable, and TDS reflect the current rules your CA has confirmed.
- Contractor proof: wage and PF/ESI payment evidence for last month's contract workers is on file.
- Bank file match: the total in the payout file equals the net pay total in the register.
What good payroll looks like after the switch
Good payroll is boring. Salaries land on the same date every month and payslips match the bank credit. Statutory filings go out without a last-minute scramble, and nobody in HR works late at month-end. The person running payroll spends their time reviewing exceptions rather than collecting data from registers and phones.
You will notice it in small ways. Employees stop asking why their pay was short, because each deduction ties back to a dated attendance or leave record. Branch managers stop sending register photos.
Your CA gets a clean statutory summary instead of three spreadsheets. The owner can also see headcount cost before approving the run rather than after.
Does your month-end still depend on WhatsApp messages and a salary sheet only one person understands? If so, try a cleaner process with a small group first. AnudaHRM offers a free setup for 5 employees, so you can run one real month through it before deciding. After that, pricing is ₹30 per employee per month. Start your free 5-employee setup at https://anudahrm.com/#hero-login.
Sources
Short answer: Payroll rules should be checked against primary sources: the Employees' Provident Fund Organisation for PF, the Employees' State Insurance Corporation for ESI, state labour and tax departments for professional tax, labour welfare fund and minimum wages, and the Income Tax Department for TDS. Confirm current notifications with a chartered accountant before each change.
- EPFO — Contribution Rates — Employees' Provident Fund Organisation
- ESIC — Contribution — Employees' State Insurance Corporation
Official references, checked on 6 November 2026. Statutory rates and thresholds change — confirm against the source before acting on them.
Frequently Asked Questions
Can a small company in India run payroll on Excel?
Yes, if headcount is small, salaries are fixed and nobody works shifts or overtime. Excel starts failing once attendance comes from several sites, leave requests arrive on WhatsApp, or statutory deductions change with each increment. At that point the risk is in the manual copying between sheets, not in the spreadsheet itself.
Does payroll software file PF and ESI returns for me?
Good software calculates contributions and prepares the data in the format the EPFO and ESIC portals expect. Someone in your team or your CA usually still logs in, checks the figures and submits. Treat the software as the preparer and a person as the approver.
How does GPS attendance connect to salary calculation?
When staff punch in on their phones at a verified location, those records feed straight into the payroll month as present, absent, half-day or late. HR no longer retypes the attendance register, and every deduction traces back to a dated, location-stamped entry. AnudaHRM links GPS attendance, leave and payroll in one system for this reason.
Start with 5 Employees Free for Lifetime
GPS attendance, payroll, leave management and KYC in one platform. ₹30 per employee per month. No credit card required.
Start Free Setup →