Skip to content

Payroll mistakes startups make (and how to avoid them)

Twelve common payroll mistakes in Indian startups, from missing cut-offs to wrong PF wages and late TDS, with a quick fix for each and a monthly self-check.

Saralix Team5 min read
On this page

Startups rarely get payroll wrong on purpose. They get it wrong because the founder did it in a sheet when there were four people, and the sheet grew with the company. Each mistake below is small on its own. Together they produce late filings, unhappy employees and an unpleasant surprise during due diligence. For each one we describe what goes wrong and a fix you can apply this month.

Figures here reflect the rules as we understand them at the time of writing. Verify against the current rules and notifications before relying on them.

1. No cut-off date

Changes arrive until the minute salaries are paid. The run is never final, and the same employee is recalculated three times.

Fix: announce a cut-off two to five working days before pay day. Anything later goes to next month or an off-cycle payment. See how to run payroll in 7 steps.

2. One person prepares and approves

When the founder or the one HR person calculates, checks and pays, nobody catches errors, and fraud risk is real.

Fix: a maker and a checker, even if the checker is the founder reading a one-page summary. Record who approved.

3. Paying salaries before registrations are in place

Deducting PF or tax without a registration, or not deducting where it applies, creates a backlog that is awkward to unwind.

Fix: register for TAN first, then PF, ESI and Professional Tax as they apply to you. Our onboarding walkthrough gives the order.

4. Not knowing what counts as PF wages

Teams apply 12% on gross or on whatever number feels right. As we understand it, PF wages are basic plus dearness allowance, commonly with contributions on a wage ceiling (Rs 15,000 until 16 September 2026, Rs 25,000 for mandatory coverage after that), and above-ceiling contribution is by agreement. The EPFO wage ceiling for mandatory coverage was raised to Rs 25,000 from 17 September 2026 (EPFO’s circular awaited), discussed in our EPFO wage ceiling update.

Fix: write your PF policy in one paragraph, apply it to everyone, and check it against the PF guide.

5. Ignoring Professional Tax until a notice arrives

PT is a state levy, so a founder in one state who hires in another can miss it completely. Slabs, due dates and registration differ by state.

Fix: list the work state of every employee. For each state, confirm enrolment, slabs and due dates. See Professional Tax by state basics.

6. Depositing TDS late

TDS on salary is typically due by the 7th of the following month (30 April for March). Late deposit attracts interest, and the 24Q return and Form 16 depend on it being right.

Fix: put the 7th in the calendar as a recurring task with an owner. Pay after payroll is locked, not before.

7. Using a different LOP rule every month

One month the founder divides by 30, another by 26, a third by calendar days. Employees notice.

Fix: pick one rule, document it, and apply it to everyone. Details are in our loss of pay explainer.

8. Paying below the minimum wage

Minimum wages are set by the Centre and by states, by zone and skill category, and the variable dearness allowance is revised periodically. Startups with interns, support staff or field teams can fall short without realising.

Fix: check the current notification for your state and category before you set a salary, and recheck after each revision. See minimum wages for payroll teams.

9. Treating fixed allowances as reimbursements

A flat monthly mobile allowance with no bills is part of salary and is generally taxable. Calling it a reimbursement does not change that.

Fix: use reimbursements for actual, documented business expenses. Put fixed allowances in the salary structure and let tax treatment follow.

10. Messy joiner and leaver data

A joiner appears in payroll with no UAN, a leaver stays on the list for two months, and an ex-employee is paid because the bank file was copied from last month.

Fix: a joiner checklist (bank, PAN, UAN, structure, work state) and a leaver checklist (last working day, assets, settlement). Review both lists at every run.

11. Skipping the exception review

Founders scan the total and move on. A decimal slip or a duplicated bank account goes through.

Fix: review exceptions only: net pay changes above a set percentage, new joiners and exits, zero or negative net pay, below-minimum-wage cases, duplicate accounts and large one-time payments. Keep one-line notes.

12. Weak records

Payslips are regenerated after the fact, challans sit in someone’s email, and Form 16 is prepared in a rush in June.

Fix: one folder per month with the approved register, bank file, challans and acknowledgements. Prepare for Form 16 from April, not May. Our Form 16 explainer lists what to check.

A quick self-check table

Question Yes / No
Is there a published cut-off date?
Are preparer and approver different people?
Do we know which registrations apply to us?
Is the PF policy written down?
Do we know every employee’s PT state?
Is the TDS deposit date in the calendar?
Is the LOP rule documented?
Is each salary above the applicable minimum wage?
Are allowances classified correctly?
Are joiner and leaver lists reviewed every month?
Do we review exceptions with notes?
Are records filed monthly?

If you cannot answer yes to at least ten, pick the two weakest and fix those first. A short list done properly beats a long list planned and abandoned.

Which mistakes cost the most

Different mistakes have different costs. As a rough ordering, based on what usually goes wrong rather than on any statistics:

  • Late statutory deposits carry interest and possible penalties, and they accumulate.
  • Wrong PF or ESI coverage can create back-dated liabilities.
  • Below-minimum-wage payments carry legal exposure and morale costs.
  • Loss of pay disputes cost time and trust.
  • Poor records cost the most at the worst moment: funding, acquisition or inspection.

A simple fix for the sequence

You cannot remove all errors, but you can remove the ones caused by sequence. Freeze inputs, calculate once, review exceptions, approve, lock, then pay. In Saralix this is the payroll wizard, with maker-checker approval, a lock after approval and a reason required to reopen. Everything is audited. The payroll feature page has the detail, and the startup solutions page covers how smaller teams use it.

Closing thought

Most of the fixes above cost nothing but a decision and a calendar entry. If you would like the same discipline built into the tool you use, see the compliance and tax features or start with the free plan for up to 10 employees.

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.