Third-Party Payroll in India: A Smart Business Decision—or a Hidden Liability Trap?
What every Indian business owner, CEO, CFO and Board must know before outsourcing its workforce
Who carries the risk when the vendor fails?
Imagine a company has 500 workers supplied through a staffing agency.
The agency submits its monthly invoice, the company's HR team confirms that the deployment is satisfactory, Finance releases the payment, and management assumes that salaries, provident fund and other statutory obligations have been handled.
Six months later, employees complain that their provident-fund contributions have not been credited. Some salary payments are disputed. The vendor stops responding, its financial position deteriorates, and the directors discover that the company cannot readily reconcile the names of the workers who entered its facilities with the records submitted by the agency.
The vendor's contract says that it is responsible for payroll and statutory compliance.
But the contract does not, by itself, answer the questions that matter most:
- Can the company still be required to pay amounts that the vendor failed to pay?
- Can regulators investigate the company’s records and controls?
- Can workers pursue remedies against the company under applicable law?
- Can the company recover the money from a vendor that has become insolvent or disappeared?
- Why did the company’s internal controls fail to detect the problem?
Indian legal decisions demonstrate that these are not merely theoretical concerns. In Senior Regional Manager, Food Corporation of India v. Tulsi Das Bauri (1997), the Supreme Court upheld the principal employer's liability to pay contract workers' unpaid wage arrears under the then-applicable Contract Labour (Regulation and Abolition) Act. In Food Corporation of India v. Regional Provident Fund Commissioner (Delhi High Court, 2024), the Court upheld assessed provident-fund dues against the principal employer in the circumstances of the case, emphasising statutory responsibility and the need to maintain and produce records.
These decisions do not mean that outsourcing is inherently wrong. They mean that an outsourcing task is not the same as outsourcing accountability.
The Topic for discussion
Third-party payroll is a potentially useful operating model when it provides measurable benefits, has a genuine business rationale and is supported by strong contractual and compliance controls.
It becomes a governance risk when management accepts the vendor's claims without independent verification, treats the service fee as the total cost, or assumes that the company's legal responsibilities have disappeared.
For boards and owners, the relevant question is not:
“Can a staffing agency handle these employees?”
It actually is:
“Does this arrangement create enough verified business value to justify its full cost and residual risk—and can we prove that the people working for us are being paid and protected as the law requires?”
1. The first misconception:
Third-party payroll means the employees are no longer our responsibility
The phrase “third-party payroll” is used to describe several different arrangements. Confusing them can lead management to approve the wrong solution.
Model 1 — Outsourced payroll processing
The company remains the employer but engages a specialist to process salary calculations, payslips, payroll reports and other administrative tasks.
The employment relationship remains with the company. This arrangement may improve processing efficiency without introducing a staffing contractor into the employment relationship.
Model 2 — Third-party employment or contract staffing
A staffing agency recruits or supplies workers, formally employs them under the agreed arrangement and administers their payroll. The client company uses their services.
The contractor may be responsible for specified employment and payroll activities. However, the principal employer may retain duties under the applicable legal framework.
Model 3 — Managed services
A service provider takes responsibility for a defined function, service level or deliverable. Depending on the arrangement, the provider may exercise greater operational responsibility than a labour supplier.
The contract must reflect the actual arrangement. A service agreement cannot transform a supply-of-labour relationship into a genuinely independent managed service simply by changing the terminology.
Why the distinction matters
If the business's problem is "salary processing", the company may be able to outsource the administration while retaining direct employment.
If the problem is "recruitment speed or variable workforce demand", third-party staffing may be more relevant.
If the problem is "operational performance", the company may need a properly designed managed service rather than a vendor that merely supplies individuals.
Board principle:
● First identify the problem.
● Then select the operating model.
● Do not begin with a vendor proposal and work backwards to justify it.
2. Few legal precedents that Indian employers should study
The following cases illustrate distinct areas of exposure. The historical cases arose under legislation applicable to their respective periods. They should be read alongside the current Labour Codes, applicable rules, transitional provisions and the facts of a particular arrangement.
Case 1 — Unpaid contract-worker wages: The principal employer may have to pay
Case: Senior Regional Manager, Food Corporation of India, Calcutta v. Tulsi Das Bauri & Others
Court: Supreme Court of India
Date: 21 April 1997
Relevant provision: Section 21(4), Contract Labour (Regulation and Abolition) Act, 1970
What happened?
Contract workers engaged through a contractor were not paid their full wages. The dispute reached the Supreme Court after the principal employer challenged the direction requiring it to pay the outstanding wage arrears.
What did the Court hold?
The Supreme Court rejected the principal employer's argument. Under the then-applicable section 21(4), if the contractor failed to pay the wages due, or made a short payment, the principal employer was required to make good the unpaid amount and could recover it from the contractor.
The Court dismissed the appeal.
Why this matters to a private company
Suppose a staffing agency supplies 300 workers to a factory, warehouse, hotel, retail chain or logistics operation. The agency fails to pay wages in full.
The client cannot safely assume that the clause saying “the contractor shall pay all wages” ends the matter. Where the applicable law imposes a corresponding duty on the principal employer, the company may need to pay workers first and pursue recovery separately.
Boardroom lesson:
A vendor's wage obligation is not a substitute for the company's statutory compliance process.
Read the judgment: Senior Regional Manager, FCI v. Tulsi Das Bauri
Case 2 — Provident-fund defaults involving contract workers: Food Corporation of India
Case: Food Corporation of India v. Regional Provident Fund Commissioner
Court: Delhi High Court
Date: 8 April 2024
Proceedings: A connected batch of writ petitions concerning assessed EPF dues for contract workers
What happened?
Various Food Corporation of India units challenged provident-fund assessments relating to workers engaged through contractors. In one of the matters described in the judgment, an assessment of ₹46,38,332 was made for contract workers. The contractor could not be traced or did not participate effectively in the proceedings, and disputes arose over worker identification, records and the principal employer's responsibility.
What did the Court hold?
The Delhi High Court upheld the assessed liability in the relevant proceedings. It explained that paragraph 30(3) of the Employees' Provident Funds Scheme, 1952 placed responsibility on the principal employer to pay the applicable contributions for workers employed directly or through a contractor. The Court also emphasised the importance of maintaining and producing the required records.
The judgment discussed the historical statutory framework and the specific proceedings before it. It should not be interpreted as a ruling that every EPF assessment against every principal employer is automatically valid, regardless of evidence, worker identification or procedure.
Why this matters to a company owner
If the company cannot identify who worked at its facilities, for which periods and through which contractor, its ability to defend an assessment or resolve workers' claims may be impaired.
This case exposes a particularly important failure mode: the vendor becomes untraceable, but the company still has to deal with the consequences of missing contributions and incomplete records.
Boardroom lesson:
Worker-level records and contribution evidence are essential controls. An invoice marked “salary and PF processed” is not equivalent to independently verified compliance.
Read the Delhi High Court judgment: FCI v. Regional Provident Fund Commissioner
Case 3 — ESI contributions: A principal employer can face statutory proceedings
Case: Bharat Heavy Electricals Ltd. v. Employees' State Insurance Corporation
Court: Supreme Court of India
Date: 14 February 2008
Relevant framework: Employees' State Insurance Act, 1948
What was the issue?
The dispute concerned the determination of ESI contributions relating to workers engaged through contractors. The question included whether proceedings could be taken against the principal employer and how the contractor should participate in determining the relevant facts and amounts.
What did the Court decide?
The Supreme Court explained that the statutory process under the ESI Act can involve determination of liability in respect of contract workers. It also stressed procedural fairness: the contractor may need to be impleaded or summoned so that the relevant facts and contribution amounts can be determined properly.
The Court set aside the challenged judgment and remitted the matter for fresh consideration, including appropriate participation by the contractors. This was not a blanket final finding that every disputed ESI amount was payable by BHEL. Its importance lies in the statutory exposure and the procedural requirements surrounding the determination.
Why this matters
Employers should not assume that the ESI authority must always pursue only the staffing agency and cannot examine the principal employer's position.
Equally, the case shows why worker identification, contribution calculations and contractor records matter. Liability should be determined through the appropriate legal process rather than by assumptions about which party ought to have paid.
Boardroom lesson:
Require auditable evidence of applicable ESI compliance and a clear process for resolving discrepancies, while preserving the right to contest an incorrect assessment through the proper procedure.
Read the judgment: BHEL v. ESIC
Case 4 — EPF compliance and the employer's duty cannot be ignored merely because the workers came through contractors
Case: Food Corporation of India v. Provident Fund Commissioner & Another
Court: Supreme Court of India
Reported citation: (1990) 1 SCC 68
Legal context: Section 7A of the Employees' Provident Funds and Miscellaneous Provisions Act, 1952.
This Supreme Court precedent was discussed in later litigation concerning contract workers and EPF assessments, including the 2008 BHEL v. ESIC judgment and the 2024 FCI proceedings.
Why it matters
The EPF framework has long required authorities to determine contributions payable in respect of covered workers, including those engaged through contractors, where the statutory conditions are satisfied.
The key governance lesson is that the existence of an intermediary does not automatically remove the need for the principal employer to establish the relevant facts, maintain required records and meet any obligations imposed by the applicable EPF framework.
The exact contribution liability, the identification of beneficiaries, the opportunity to be heard and the evidence produced remain important. This precedent should not be cited as a blanket rule that every contractor default is automatically payable by the client in every circumstance.
Boardroom lesson:
Do not treat the vendor's EPF registration or undertaking as conclusive proof that the company's own compliance position is secure.
Consult the Supreme Court precedent through the discussion in BHEL v. ESIC
What the cases collectively establish—and what they do not
Issue
What the authorities support
What they do not establish
Unpaid wages
A principal employer may be required to make good qualifying wage defaults under the applicable statutory framework.
That every dispute over every employment payment automatically becomes the client’s liability.
EPF contributions
The principal employer may have statutory duties concerning contributions for workers engaged through contractors, with required records and procedural safeguards.
That every assessment is correct without identifying workers, periods, evidence and applicable law.
ESI contributions
Statutory proceedings may examine the principal employer’s position and contributions for contract workers.
That a principal employer is automatically liable for every amount asserted by the authority.
Vendor recovery
The principal employer may have contractual or statutory recovery rights against the contractor.
That recovery will be quick, complete or commercially possible if the vendor is insolvent or untraceable.
The right conclusion is neither “outsourcing is legally unsafe” nor “the vendor carries all the risk.”
The conclusion is that legal responsibility must be mapped obligation by obligation, and the employer needs controls capable of proving compliance.
3. The hidden cost of a cheap staffing proposal
A staffing agency may quote a management fee that appears attractive. But the vendor fee alone does not tell the board whether the arrangement is economical.
A proper comparison must include:
- Wages and benefits
- Applicable statutory contributions and other employment costs
- Recruitment and onboarding
- Vendor management and internal supervision
- Payroll reconciliation and compliance audits
- Replacement hiring and training
- Attrition and lost productivity
- Data security and business-continuity controls
- Legal advice and dispute management
- Transition costs if the provider must be replaced
Illustrative financial comparison
Assume a company has 100 workers and the following monthly costs. These figures are illustrative only; they are not industry averages, vendor quotations or statutory rates.
Cost item
Direct employment
Third-party staffing
Wages and benefits
₹30.00 lakh
₹30.00 lakh
Statutory costs
₹4.50 lakh
₹4.50 lakh
Internal administration
₹1.50 lakh
₹0.30 lakh
Vendor service fee
Nil
₹1.50 lakh
Additional oversight and transition reserve
₹0.20 lakh
₹0.60 lakh
Total
₹36.20 lakh
₹36.90 lakh
Under these assumptions, third-party staffing costs ₹70,000 more per month, or ₹8.4 lakh more annually.
The staffing model could still be worthwhile if it produces measurable value through faster deployment, better recruitment, variable-capacity management or reduced vacancy costs. But management should identify and measure those benefits rather than treating the outsourcing decision as self-justifying.
The Key Question for the Board is:
“What incremental business outcome are we buying with the vendor fee, and how will we verify it?”
4. The governance question: Is the company buying a service—or merely adding an intermediary?
The vendor may be competent and the arrangement entirely legitimate. Nevertheless, a company can end up paying an intermediary without receiving the expected operational benefit.
The following warning signs deserve independent examination:
- The business case focuses on “reducing HR workload” but does not quantify the current workload or the expected saving.
- The vendor’s fee is compared with salary cost rather than with the full cost of delivering the workforce outcome.
- No alternatives are assessed, including direct employment, outsourced payroll processing or a genuinely managed service.
- The same small group of managers selects the vendor, evaluates its performance and approves its invoices without independent checks.
- The vendor cannot provide clear evidence of salary payment, statutory contributions or worker-level reconciliation.
- The company cannot identify all deployed workers, their work locations and their contractual employer.
- The vendor’s proposal is accepted without a competitive process or documented explanation of why it offers better value.
- Repeated payroll discrepancies are dismissed as administrative errors rather than treated as control failures.
- The arrangement continues despite poor worker experience, high attrition or recurring compliance exceptions.
- The business cannot explain how it would transition the workforce if the vendor failed tomorrow.
These are risk indicators, not proof of misconduct. A preferred vendor may be selected for valid reasons, and a non-competitive procurement process may be justified in particular circumstances. The concern is the absence of transparent evidence, independent challenge and documented rationale.
What if an internal manager has an undisclosed relationship with the vendor?
The appropriate response is not to assume that every HR recommendation is compromised. It is to establish controls that make conflicts of interest difficult to conceal and easier to detect.
The company should require declarations of relevant personal or financial interests, document vendor selection criteria, segregate selection from invoice approval, retain procurement records and provide an escalation channel outside the reporting line of the manager involved.
Where credible concerns arise, the company should commission an independent review through the appropriate governance function. Allegations of collusion or improper benefits should be investigated on evidence, not circulated as fact without substantiation.
The board's responsibility is to create a process in which the business case can survive independent scrutiny.
5. A board-level due-diligence framework
Before approving a material third-party workforce arrangement, the board, audit committee or delegated executive committee should require a written assessment addressing the following questions.
A. Strategic necessity
- Why is third-party staffing preferable to direct employment?
- Why is it preferable to outsourcing payroll administration only?
- Is the requirement temporary, variable, specialised or long-term?
- Does the model improve operational performance, or merely change how headcount is recorded?
B. Commercial value
- What is the fully loaded cost under each feasible model?
- Are recruitment, onboarding, replacement, oversight and transition costs included?
- What assumptions support the claimed savings?
- Who will measure realised value, and how often?
C. Legal exposure
- What is the precise legal structure of the arrangement?
- Which obligations sit with the contractor, the principal employer and any other relevant party?
- What registrations, licences, rules and worker protections apply to the relevant locations and roles?
- Has the arrangement been reviewed against current Central and state requirements?
D. Vendor integrity and capability
- Has the provider been independently vetted?
- Can it demonstrate relevant experience and a sustainable financial position?
- Are its statutory filings and employee-level records verifiable?
- Are there unexplained related-party connections, conflicts of interest or unusual commercial terms?
- Does the provider use subcontractors, and if so, under what controls?
E. Operational resilience
- Can the company continue operations if the provider fails?
- Can worker records be retrieved promptly?
- Is there a workable transition plan?
- Who owns the relationship with workers when an issue arises?
6. The monthly compliance dashboard that should reach management
The board need not approve individual payroll calculations. It should, however, ensure that management receives reliable information about material risks.
Indicator
Minimum management expectation
Active worker reconciliation
The deployed workforce reconciles with approved headcount and contractor records.
Salary payment
Payment evidence is available and exceptions are resolved promptly.
EPF and ESI, where applicable
Employee-level records, calculations and deposit evidence are reconciled.
Attendance and overtime
Approved records support payroll and invoice amounts.
Employee grievances
Complaints are tracked, assigned and closed within defined timelines.
Vendor invoices
Charges reconcile with authorised headcount, rates, service levels and evidence of delivery.
Compliance exceptions
Material exceptions have an owner, a deadline and an escalation path.
Vendor financial health
Material deterioration triggers a review of continuity and exposure.
Audit findings
Repeat findings are escalated and corrective action is independently verified.
Exit readiness
Records and transition arrangements remain available if the contract ends.
For a large or higher-risk workforce, Finance, HR, Legal and Operations should share responsibility for this control environment. No single function should be able to certify its own work without appropriate challenge.
7. The Indian legal framework: What leadership should verify now
India's Labour Codes and applicable rules must be reviewed in their current form, together with state-level requirements and any relevant transitional provisions. Employers should not rely on a vendor's generic compliance checklist or on a historical judgment without checking the law applicable to their specific facts.
Before signing or renewing an agreement, obtain legal advice on:
- The applicable wage-payment and contract-labour framework
- Social-security contributions and the respective obligations of the employer, contractor and other relevant parties
- Registrations, licences and establishment-specific requirements
- Worker classification and the actual substance of the arrangement
- Workplace safety, welfare and employment records
- Applicable leave, bonus, gratuity and other benefits
- Termination, transition and employee-data requirements
A contract may allocate responsibilities and provide indemnities or recovery rights. Those provisions are important, but they do not necessarily prevent a worker, regulator or court from pursuing a party that has a statutory obligation.
The legal precedents in this paper demonstrate why the company must verify the arrangement rather than rely exclusively on its contractual wording.
8. A practical 90-day action plan
Days 1–15: Establish the facts
Inventory all third-party workforce arrangements, locations, vendors, headcount, job categories, contract values and compliance records. Identify any gaps in worker-level documentation or contribution evidence.
Days 16–30: Challenge the business case
For each material arrangement, compare direct employment, payroll processing outsourcing and third-party staffing. Recalculate the total cost and document the expected operational benefits. Ask an independent function to review material assumptions and potential conflicts of interest.
Days 31–60: Strengthen controls
Correct missing documentation, establish employee-level reconciliation, review contractual responsibilities, set audit rights and implement a monthly dashboard. Prioritise any unresolved wage or statutory-contribution discrepancies.
Days 61–90: Decide what to retain, change or exit
Renew only those arrangements that demonstrate a sound business case and adequate control. Renegotiate, replace or redesign arrangements that repeatedly fail to meet requirements. Develop a transition plan before a vendor crisis makes transition unavoidable.
Where a suspected statutory default is discovered, the company should obtain prompt legal advice, preserve relevant records and take appropriate steps to protect affected workers and meet applicable obligations. It should not wait for the next routine vendor review.
9. The question every owner should ask the HR head, CFO and procurement leader
Before approving a third-party payroll arrangement, ask each function to answer the same question independently:
“If the vendor fails to pay workers or deposit statutory contributions tomorrow, what exactly happens to our company—and what evidence do we have that our controls will detect the failure before it becomes a serious problem?”
If management cannot answer clearly, the proposal is not yet ready for approval.
