Who is Liable if My India Payroll Vendor Makes an Error?

The honest answer is: in almost every payroll error scenario in India, the company named as the legal employer pays the fine first. Whether that is your Indian subsidiary or your EOR partner depends entirely on how you set up your hiring structure.

This matters because Indian tax and labor authorities do not care about your service contract with a payroll vendor. They go to the entity that holds the PAN, TAN, EPF code, and ESI code. Your vendor agreement only governs what happens after the regulator has already issued the penalty.

This guide walks through how liability actually flows when something goes wrong, where the penalty money comes from, and how to structure your arrangement so a vendor error does not end up on your balance sheet.

Who is the legal employer under Indian payroll law?

The legal employer is the entity that registers employees with statutory authorities and signs their employment contracts. That entity carries all statutory liability for payroll compliance, regardless of which vendor processes the actual calculations.

Three setups are common when foreign companies pay employees in India:

1. You have an Indian entity and use a payroll vendor: Your entity is the legal employer. The vendor only processes payroll on your behalf. You sit on the hook for every statutory error.
2. You use an Employer of Record (EOR): The EOR is the legal employer. They sign the employment contract, hold the EPF and ESI codes, and file all returns under their own PAN and TAN. Statutory liability sits with them.
3. You use a global payroll platform or fintech for money movement only: These do not employ anyone. Your entity, or your EOR, is still the legal employer and still liable for filings.

From our experience helping foreign companies enter India, this is the single most misunderstood piece of the model. Many founders assume that hiring a "payroll provider" outsources the liability. It does not. It only outsources the work.

Who pays the fine when a payroll vendor makes an error?

The legal employer pays the fine first. Indian authorities issue the notice to the registered entity, not to the vendor running the calculations. Whether the vendor reimburses you afterward depends entirely on your contract.

This plays out in two distinct ways:

In the traditional vendor model, you are facing two simultaneous problems when something breaks. First, you pay the regulator immediately because penalties accrue daily. Second, you then need to recover the cost from the vendor through their indemnification clause, which is usually capped at the fees you have paid them. A 25% damages charge on missed EPF dues can dwarf a year of payroll service fees.

What kinds of payroll errors trigger penalties in India?

Five categories of errors regularly trigger statutory penalties under current Indian law. Most of them carry interest charges that compound daily.

• TDS errors. Under Section 392(1) of the Income Tax Act 2025, salary TDS must be deposited by the 7th of each month. Late deposits attract 1.5% interest per month plus a ₹200 daily late fee under Section 234E. Missing the quarterly Form 138 filing (which replaced Form 24Q in April 2026) triggers similar daily penalties.
• EPF errors. Late provident fund payments attract 12% annual interest plus damages of up to 25% of the dues under Section 14B of the EPF Act. Inspectors can also assess retrospective dues if salary structures violate the 50% basic wage rule under the Code on Wages.
• ESI errors. Late ESI contributions attract 12% interest plus damages. Wrong wage classifications can trigger retroactive dues across multiple years.
• Gratuity miscalculations. Underpayment of gratuity at exit can trigger labor commissioner action plus interest payable to the employee.
• Worker misclassification. Treating an employee as a contractor creates retroactive EPF, ESI, gratuity, and TDS liabilities, along with back wages.

One pattern we've consistently noticed is that companies treat each of these as a payroll problem. They are actually statutory employer problems. The vendor processes the transaction, but the statute names the employer.

What does a payroll vendor contract typically cover?

Most payroll vendor contracts in India include an indemnity clause that promises to reimburse the client for losses caused by vendor errors. The protection sounds strong on paper. In practice, it is usually limited in three ways.

• Liability cap. Vendor liability is often capped at fees paid in the preceding 6 to 12 months. If your monthly service fee is small, this can cover only a tiny fraction of a real penalty.
• Scope exclusions. Indemnification typically excludes errors caused by incorrect data provided by the client, regulatory changes, or consequential losses such as reputational damage or audit costs.
• Cause and proof requirements. The client usually has to prove the error was solely the vendor's fault, with no contributory negligence. In practice, this is hard.

Companies often underestimate how narrow these clauses really are. A serviceable contract should also require the vendor to maintain professional indemnity insurance, accept joint and several liability for statutory filings, and include service-level penalties for missed deadlines. Few standard vendor contracts go that far.

How does liability work under an EOR in India?

Under an EOR arrangement, the EOR is the legal employer in India. That single fact changes who the regulator pursues for a payroll error.

Here is what shifts:

• The EOR holds the PAN, TAN, EPF code, and ESI registration.
• Employment contracts are signed between the employee and the EOR.
• Statutory filings, including Form 138 quarterly and Form 130 annually, are submitted under the EOR's identity.
• Penalty notices from the income tax department, EPFO, and ESIC are issued to the EOR.

The foreign client company is not the named employer for statutory purposes, so it is not the primary party in any enforcement action. The EOR absorbs the regulatory risk and resolves it directly with the authority.

There are still client-side responsibilities. You provide accurate salary data, employee information, and approval workflows. If the error stems from data you provided (for example, an incorrect address that drives wrong professional tax), the EOR may seek to recover that under your service agreement. But for errors in the actual payroll computation, filing, or remittance, the liability stays on the EOR side.

This is why most foreign companies entering India choose the EOR route during their first 18 to 24 months. The risk profile is fundamentally different.

What should you ask a payroll vendor or EOR before signing?

Before you sign, get clear answers on liability allocation, insurance coverage, and how filings are made. The answers tell you exactly where the risk sits.

Useful questions include:

• Who is named as the legal employer on employment contracts and statutory filings?
• Whose PAN and TAN appears on TDS deposits and Form 138 filings?
• Do you carry professional indemnity insurance, and what is the coverage limit?
• What is your liability cap, and does it carve out statutory penalties?
• Will you indemnify us for late filing fees, interest, and damages, including penalties imposed by EPFO and ESIC?
• How quickly do you correct errors, and who pays for retroactive corrections?
• Do you provide audit-ready documentation for every statutory payment?

If a vendor cannot answer these clearly, that is the answer.

How can you reduce your exposure to payroll errors in India?

Reducing exposure is part contractual and part operational. The contract decides who eats the loss. The operations decide whether the loss happens at all.

Practical steps:

• Choose the right structure for your stage. If you have fewer than 30 employees in India and no permanent establishment plans, EOR usually shifts more risk than a vendor contract ever will.
• Audit your salary structures. The 50% basic wage rule under the Labour Codes drives EPF and gratuity calculations. A non-compliant structure creates retrospective dues during inspection.
• Verify your software is updated for 2026. The Income Tax Act 2025 changed section numbers, form names, and the "Tax Year" terminology. Old systems will fail validation on the income tax portal.
• Reconcile quarterly. Match TDS deposits against Form 138 filings and EPF challans against deductions. Catching mismatches early prevents compounding.
• Maintain digital records for seven years. This is now mandatory under the 2025 Labour Codes.

Based on our extensive experience supporting international teams, most penalty exposure can be reduced just by getting the salary structure right at the start and keeping statutory deposits ahead of the 7th and 15th deadlines.

How does Wisemonk handle payroll liability for global clients?

Wisemonk operates as the legal employer of record (EOR) for clients hiring in India. That means statutory liability for payroll, TDS, EPF, ESI, gratuity, and professional tax filings sits on the Wisemonk side, not on the client.

Wisemonk runs its own in-house payroll, compliance, and contractor infrastructure in India, instead of routing work through third-party providers. This gives clients tighter control over accuracy and avoids the multi-vendor finger-pointing that often follows when something goes wrong. Filings happen under Wisemonk's PAN and TAN, employment contracts are signed under Wisemonk's entity, and statutory deposits are made on Wisemonk's accounts.

For companies that want to eventually set up their own Indian entity, Wisemonk supports a clean entity transition, so the team and statutory continuity move with you when the time is right. For companies that prefer to stay with the EOR model, the same compliance accountability continues quarter over quarter.

The practical effect: a payroll error in your India team does not become a tax notice on your US, UK, or European balance sheet.