Which Is Better for India Payroll: a Platform or a Specialist Provider?

We have watched the India Payroll Platform or Specialist Provider decision go wrong in the same way at least a dozen times in the last three years. A foreign company signs up for a payroll SaaS tool, runs its first two cycles clean, and then hits a Provident Fund inspection in month four because nobody configured the EPFO challan correctly for a mid year salary revision. That is not really a platform failure. It is a gap between what software calculates and what a compliance literate human catches before it becomes a notice.

Why the India Payroll Platform or Specialist Provider Question Is Harder Than It Looks

Foreign finance teams often assume Indian payroll works like the UK or Germany, just cheaper: one national withholding system, one filing calendar, done. It does not work that way. India runs statutory payroll compliance at two layers at once, central and state.

At the central level you have the EPF and Miscellaneous Provisions Act, 1952, the ESI Act, 1948, the Payment of Bonus Act, 1965, and TDS obligations under Section 192 of the Income Tax Act. At the state level, Professional Tax has a different slab, due date, and filing portal in Karnataka versus Maharashtra versus Delhi, and it does not exist at all in some states. A company with ten employees split across Bengaluru, Pune, and Delhi NCR is technically running three separate PT compliance calendars inside one payroll run.

This is exactly where the India Payroll Platform or Specialist Provider question starts to matter in practice. A pure payroll platform, meaning a SaaS tool with an India module attached, will calculate gross to net correctly nine times out of ten. What it usually will not do on its own is flag that your Pune employee's PT slab changed after the Maharashtra government's last revision, or that an employee who crossed the ESI wage ceiling mid year needs to be dropped from ESI contribution the following month, not immediately.

We have seen this exact ESI ceiling crossing error trigger a labour department query for a Bengaluru based GCC with 40 employees, purely because the platform's default rule treated the ceiling as a hard cutoff rather than a month boundary event, which is how the ESI Corporation actually applies it. The demand for clarity on this has grown as more foreign companies open global capability centers in India instead of routing everything through one outsourcing partner back home. Each GCC now has to decide, often for the first time, whether payroll runs on software it controls or a provider who owns the outcome.

What Does a Payroll Platform Actually Do Versus a Specialist Provider?

A payroll platform such as Keka, GreytHR, ADP's India module, Deel, or a similar global tool with an India layer gives you a system of record, self service payslips, a calculation engine, and usually a dashboard. You, your India entity, or your EOR still own the judgment calls: which allowances are taxable, how to structure CTC to stay compliant with the Code on Wages, when a contractor classification risks being reclassified as employment under the Industrial Disputes Act. The platform executes. It does not advise.

A specialist provider, a boutique payroll and compliance outsourcing firm sometimes bundled with HR outsourcing or delivered alongside an employer of record arrangement, takes on those judgment calls as part of the service. They file your PF, ESI, and PT returns under their own compliance calendar, they carry professional indemnity for filing errors, and they typically have a named compliance manager who has personally handled a labour inspection before. The trade off is cost and, sometimes, slower turnaround on ad hoc requests because you are going through a person rather than clicking a button.

Our team at AnjuSmriti Global tells clients bluntly that if India headcount is under 15 and stable, a platform plus a good chartered accountant on retainer is often sufficient. Past 15 people, or the moment you have a mix of contractors, full time employees, and people in more than two states, the judgment call volume rises fast enough that a specialist provider usually pays for itself in avoided penalties within the first year.

Getting the India Payroll Platform or Specialist Provider Choice Right, Legally

The law that trips up more foreign employers than any other in this decision is the Payment of Wages Act, 1936, specifically its rules on the timing and mode of wage disbursement, combined with state level Shops and Establishments Act registration requirements. These vary enough between states that a platform's default template rarely covers all of them correctly out of the box.

Add the EPF and Miscellaneous Provisions Act, 1952, which makes PF contribution mandatory once an establishment crosses 20 employees and optional but common below that, the ESI Act, 1948, mandatory below a wage ceiling that gets revised periodically, and TDS obligations under Section 192, and you have five separate statutory regimes running under one payroll cycle.

The mistake we see most often: a company hires its 20th employee in India, crosses the EPF mandatory threshold, and keeps running payroll on a platform still configured for voluntary PF. That means the employer contribution rate, the wage ceiling application, and the UAN registration timeline are all wrong from that pay cycle onward. A platform does not know your headcount crossed a legal threshold unless someone tells it to change the rule. A specialist provider, because it is watching headcount as part of the relationship, catches this before the first non compliant cycle runs.

Contract Hiring vs Full Time Hiring: Why the Compliance Load Is Different

Full time hiring in India means the employee sits on your entity's rolls, is covered by PF and ESI where applicable, receives statutory bonus eligibility under the Payment of Bonus Act, and is taxed through TDS deducted at source every month. The compliance calendar for a full time employee is predictable once it is set up correctly, because the same person, the same wage structure, and the same filings repeat month after month.

Contract hiring works differently, and it is where a large share of hiring mandates start for foreign companies testing the India market before committing to a full entity build out. The compliance question is not gross to net calculation, it is classification.

Does the engagement genuinely meet the tests for independent contractor status, or does it risk reclassification as employment?

This matters because reclassification exposes the employer to retrospective PF and ESI liability, not just liability going forward. A platform has no way to judge this. It will process whatever payment structure you feed it. A specialist provider, or an EOR handling the same relationship, is trained to flag functional employment characteristics, fixed hours, exclusive engagement, company issued equipment, before they turn into a labour department finding.

For companies running both models at once, a mix of full time staff in Bengaluru and contract hires in two other states for example, the India Payroll Platform or Specialist Provider decision often is not one or the other. It becomes a question of which parts of the workforce need software execution and which parts need a human owning the classification risk.

The Decision Framework We Actually Use With Clients

This is the grid our compliance team walks through with a new client before recommending a model. Adapt the thresholds to your own situation.

Factor	Lean Platform	Lean Specialist Provider
India headcount	Under 15, one state	15+, or spread across 2+ states
Entity status	Registered India entity with in house finance oversight	No India entity, or entity run remotely with no local compliance staff
Employee mix	All full time, salaried	Mix of contractors, full time, and consultants
PF/ESI complexity	Below mandatory thresholds, voluntary only	At or near the 20 employee PF threshold, or ESI wage ceiling crossers
Internal bandwidth	Someone can review a payslip and catch an error	Finance team has zero India specific compliance experience
Risk appetite	Comfortable owning statutory judgment calls	Wants indemnity and a named accountable party
Growth trajectory	Flat or slow headcount growth	Planning to double India headcount within a year

If you want a clear answer for your own headcount and state mix rather than a general framework, run our free two week diagnostic. Start here and we will tell you which side of the table you actually fall on.

How the Diagnostic Works, and What Nearly Went Wrong Once

When a client asks us to help decide between a platform and a specialist provider, we run a two week diagnostic. We pull current India headcount by state and employment type, check which statutory thresholds the company is near, and audit one full payroll cycle line by line against the applicable Acts. That is usually enough to tell us which side of the framework the client falls on.

One case that stays with our compliance lead involved a mid size European SaaS company that had been running India payroll on a well known platform for 18 months, self managed, with its Amsterdam finance controller reviewing outputs remotely. Fourteen employees, all in Bengaluru, all full time. On paper, textbook platform only territory.

During our diagnostic we found that three employees had been auto enrolled in voluntary PF at signup, which pushed the company's effective contributing headcount calculation into a grey zone the platform's rule engine did not recognise, because voluntary enrollees count differently than mandatory ones when EPFO calculates whether the 20 employee threshold has been crossed for enforcement purposes. It had not yet caused a problem. It was about four months from becoming one.

We flagged it, restructured the PF enrollment to remove the ambiguity, and the client stayed on the platform. They did not need a specialist provider, they needed one diagnostic conversation and a configuration fix.

Where we do recommend a full specialist handover, the transition typically takes three to four weeks: one week to audit the existing setup, one to two weeks to migrate statutory registrations and historical filing data, and a final week running the old system and the new provider in parallel on one live cycle before cutover, so nothing breaks mid quarter.

What Does Each Model Actually Cost in India?

These are current rates we quote clients for a company with roughly 20 to 30 India employees across Bengaluru and Pune, blended full time and contract.

Platform only model

• Per employee platform licence: ₹350 to ₹600 a month

• Statutory filings handled internally by the client's finance team or a local CA on retainer: ₹15,000 to ₹35,000 a month flat retainer

• No indemnity for filing errors, liability sits entirely with the employer entity

Specialist provider model

• Per employee payroll processing fee: ₹800 to ₹1,400 a month, inclusive of PF, ESI, PT, and TDS filing

• One time onboarding and statutory registration fee: ₹40,000 to ₹75,000

• Indemnity for filing accuracy typically included or available as a rider

For a 25 person India team, that works out to roughly ₹9,000 to ₹15,000 a month on a platform only model versus ₹20,000 to ₹35,000 a month with a specialist provider, a gap of about ₹11,000 to ₹20,000 a month, or ₹1.3 to 2.4 lakh a year.

Clients who move to a specialist provider almost always tell us the internal finance hours freed up, the ones no longer spent chasing PT deadlines across two states, get redirected toward closing the India entity's books faster at quarter end.

Conclusion

Payroll technology in India is absorbing more compliance intelligence than it used to. A handful of the larger India focused platforms now flag statutory threshold crossings automatically, run PF and ESI edge cases through rule engines that update closer to real time, and offer cloud dashboards that give a remote finance controller visibility they did not have a few years ago. Artificial intelligence is showing up inside these tools too, mostly in anomaly detection: flagging a payslip that looks structurally different from the same employee's previous cycle, or catching a PT deduction that does not match the employee's registered state.

None of this has closed the gap between platform and specialist provider, though it is narrowing it in specific areas. What AI and cloud tooling handle well is pattern deviation. What they still do not handle well is legal judgment, the kind that decides whether a contractor's working pattern crosses into employment, or how a new state level wage notification should change a CTC template. That judgment still sits with a person, whether that person is an in house compliance hire, a specialist provider's account manager, or an EOR's legal team.

Not sure which side of that split your company falls on? Run the same free diagnostic we use with every new client, no obligation attached.

---

Interesting Reads:

What Is a Good Omnivoo Alternative for Hiring in India?

What Does It Cost Japanese Companies to Hire Full-Time Recruitment in India? Payroll Outsourcing for Startups India: What Founders Must Know

FAQs

1.Does the 20 employee EPF threshold count contractors, or only full time staff?

The EPF Act counts employees on the establishment's rolls, which in most enforcement interpretations includes anyone under a contract of service rather than a contract for service. If your contractors are functionally supervised like employees, fixed hours, exclusive engagement, company equipment, a labour inspector can argue they should count toward the threshold regardless of contract labels. Audit against actual working conditions before assuming you are under the limit.

2.Can a payroll platform alone handle Professional Tax across multiple Indian states?

Most platforms calculate PT correctly once configured per state, but the configuration itself is the risk point. PT is not a central tax. Each state sets its own slabs, due dates, and filing portal, and several revise slabs periodically with little national coverage. A platform applies whatever rule it was set up with and will not notice a slab change on its own. This is a common gap in platform only setups with employees in more than one state.

3.What happens if ESI contributions are not stopped correctly when an employee crosses the wage ceiling?

The common error is treating the ceiling as an immediate cutoff rather than the month boundary rule ESIC actually applies, where contribution continues for the rest of the contribution period even after a mid period raise. Getting this wrong in either direction creates a mismatch between what is remitted and what is owed, which surfaces during an ESIC audit rather than immediately. This is checked during every platform diagnostic we run.

4.Is a specialist payroll provider in India required to hold professional indemnity insurance?

It is not a legal requirement, but it is a strong signal of a mature provider. Indemnity coverage means that if the provider makes a genuine filing error, a missed PF challan deadline or an incorrect TDS calculation, there is a financial backstop beyond an apology. When advising clients on selecting a provider, indemnity coverage and its claim history are among the first things worth asking to see, along with references from similar sized clients.

5.How does the Code on Wages affect CTC structuring for foreign employers running India payroll?

The Code on Wages requires that at least 50% of an employee's total CTC be classified as wages for calculating statutory dues like PF and gratuity, which changes how allowances can be structured. Companies that built CTC templates before this rule, or copied one from another country, often have allowance heavy structures that no longer comply once fully notified state by state. This shows up often during independent diagnostics.

6.Do payroll platforms handle statutory bonus calculations under the Payment of Bonus Act?

Most modern platforms can calculate statutory bonus if configured correctly, but eligibility rules, which employees qualify based on wage ceiling and tenure, and how the bonus percentage is set based on the Act's available surplus calculation, require judgment a template rarely captures on its own. Platform only setups either skip statutory bonus entirely or apply a flat percentage that does not match the Act's method, both compliance gaps.

7.What is the realistic timeline to switch from a platform to a specialist provider mid year?

Typically three to four weeks end to end: roughly a week to audit the existing setup and historical filings, one to two weeks to transfer statutory registrations such as the PF establishment code, ESI code, and PT registration numbers, and a final week running old and new systems in parallel on one live cycle before full cutover. Switching mid quarter is generally safer than switching right at a filing deadline.