Payroll outsourcing vs in-house: which makes sense, and when

Payroll has to run either way, so the real question is not whether you pay people, but who owns the process. In-house payroll on spreadsheets is fine at a certain scale. It stops being fine at a point that moves with your headcount and how many states you operate in. This post lays out the trade-off so the decision is about cost and risk, not about habit. For what a compliant outsourced run looks like end to end, see how payroll outsourcing works in India.

What in-house payroll actually costs

Running payroll yourself is not free just because there is no invoice. The cost is people time, software, and the quiet cost of being the accountable owner on filing day.

• A salary-run owner — someone who collects attendance and leave data, applies the changes, validates the inputs and answers the “why is my pay wrong” calls (payroll process).
• Statutory tracking — registering, depositing and filing PF, ESI, professional tax, TDS and the state returns, each on its own date. The EPFO employer filing and ESIC contribution requirements alone have their own calendars, and the reference checklist runs to a page of monthly, yearly and situation-based obligations.
• Keeping up with change — rates move. The wage ceiling, the ESI ceiling, the labour codes and state notifications change, and someone has to know when (labour codes).
• The penalty line — a missed 15th carries interest and damages (EPF and Miscellaneous Provisions Act, 1952); deducted-but-undeposited contributions are a worse category entirely (PF, payroll errors and their cost).

Spreadsheets handle low complexity well. What they do not handle is complexity multiplying. Add a second state, a different professional tax slab, a minimum wage that differs by skill level, and a welfare fund with its own cadence, and one careful person doing payroll well becomes a team doing it barely.

The real driver: state complexity

The single biggest factor is not headcount — it is how many states you run. PF and ESI use central thresholds, but professional tax, minimum wages, welfare funds and the registers vary by state. Two sites in different states mean two sets of rules for components that look identical. The more states, the more statutory variation in a run, and the more spreadsheets stop being the right tool. This is the situation where the labour-cost calculator stops being an estimate and becomes essential — because the components differ, your cost differs per site.

What outsourcing changes

A payroll service does not change the statutory amounts. It changes who owns them. The provider runs the payroll to a documented calendar with cut-offs and disbursement dates agreed up front, keeps a register of statutory filing dates and reports status rather than missing deadlines, and retains an audit trail for every run. Corrections are documented, not silently edited. In short, you buy an accountable process and an inspectable record instead of a pile of spreadsheets and a prayer.

The handover matters. A good transition reconciles the current payroll first — headcount, states, statutory components and any gaps — and agrees the calendar before the first run, so the changeover does not break the payroll. That is the same Assess → Design → Mobilise → Stabilise → Review sequence Knighthood runs for any operation.

When in-house stays the right call

In-house payroll is reasonable when it is genuinely simple: a single state, a single site, a stable workforce, and someone already owns the process competently. If your statutory dates are tracked, your structure is built right and the one person running it is not a bottleneck holding the whole business hostage on the 15th of every month, there is no urgent reason to change. The costs only become visible at the point where the owner is stretched, the calendar slips, or a new state arrives.

When to switch

Switch when any of these is true, and a payroll provider is likely to be cheaper and lower-risk than your in-house setup:

• The workforce sits across multiple states with different statutory components, and the run keeps growing.
• Payroll is manual or spreadsheet-based with no audit trail, and you have already corrected a run after payment.
• The single person who “owns” payroll is the same person who is also handling HR, accounts and everyone’s questions.
• A filing date has slipped, an inspector asked for registers you could not produce, or an employee has challenged a payslip.

Outsourcing scales the process with headcount; in-house scales the stress with the 15th.

The bottom line

The decision is not in-house versus outsource as a matter of principle — it is about complexity and ownership. Simple and stable, run payroll yourself if it is under control. Add states, add headcount, or let an error slip through, and the cost shifts toward the provider that owns the process, the calendar and the audit trail. Price the whole thing — a wage is not a cost until the statutory build-up is on top — and the answer usually follows.

Frequently asked questions

At what headcount does outsourcing payroll start to make sense?

Headcount is the wrong trigger; the number of states you operate in is the right one. A hundred people in one state, one wage notification and one professional tax slab is a payroll one careful person can run well. Twenty people across four states, with four wage notifications, four registers and a welfare fund in two of them, is where spreadsheets start failing — and where a provider’s fixed calendar earns its fee.

What does outsourcing not fix?

It does not clean up a salary structure that was built wrong, and it does not remove your responsibility as an employer. If basic pay is set below the statutory share of wages, a provider will calculate the wrong contributions accurately and on time. The structural rebuild comes first, then the process moves. Expect the provider to raise the structure as a finding during handover.

How long does a payroll transition take?

For a single-state operation, a few weeks — enough to reconcile headcount, statutory components and open gaps, and agree the calendar before the first run. Multi-state transitions with several establishment codes take longer, and the risky part is always the first parallel month. Run one cycle in parallel where you can, and agree in advance what happens if the two outputs disagree.

Do I lose control of my payroll data if I outsource?

Not if the contract says otherwise. Insist on data ownership staying with you, a defined export format, an audit trail for every run and every correction, and the right to the underlying records on exit. Payroll data identifies individuals, so it is personal data under the Digital Personal Data Protection Act, 2023 — the provider should be able to tell you where it is held and who can see it.

Is the payroll provider liable if it misses a statutory date?

That depends entirely on the contract, and it is worth settling before the first run rather than after the first penalty. Decide who is the employer of record, who bears interest and damages for a late deposit, and how a correction is documented. A provider that will not put its own process obligations in writing is telling you something about how it will behave when a date slips.

Can I outsource payroll and keep HR in-house?

Yes, and it is a common split — the provider runs the calculation, disbursement and statutory filing, while your own team keeps recruitment, performance and employee relations. It works best when the boundary is explicit: who collects attendance, who approves a correction, who answers the employee’s question about their payslip. Blur that line and both sides will assume the other is handling it.