Provident fund and ESI on contract workers generate more confusion than any other part of Indian payroll compliance, and the confusion is nearly always about the same thing: who is actually answerable when it goes wrong.
The short answer
The contractor employs the worker and ordinarily remits the contributions under their own code. But the principal employer cannot treat that as the end of the matter. Where a contractor fails to remit for workers deployed on your premises, the obligation can come back to you.
Deducting a contribution and remitting it are two different events. Almost every serious problem lives in the gap between them.
How the monthly cycle actually runs
For each month, in order:
- Attendance is finalised and wages are computed against it
- Contributions are deducted from wages and the employer share is added
- The contribution is remitted and the electronic return is filed
- A challan is generated, which is the evidence that remittance happened
- That challan reaches you, and is stored against the month it belongs to
Steps one to four are the contractor's to perform. Step five is yours to insist on, and it is the step that most often does not happen.
Where it goes wrong
Deducted but not remitted
The worker's payslip shows a deduction. The remittance never followed. Nothing looks wrong from your side until a worker cannot claim, or an authority asks for challans and the months do not add up.
UAN and IP registration not completed
A worker is on site and being deducted, but was never registered, so the contribution has nowhere to land. This surfaces when the worker tries to use the benefit, which is the worst possible moment for everyone.
Contributions that stop when a worker moves site
Multi-site engagements are where continuity breaks. A worker moves between locations, the record follows late or not at all, and a gap appears in a contribution history that should have been unbroken.
Wages structured to reduce the contribution base
Occasionally a wage structure is arranged to minimise the contribution base. The saving is immediate and the exposure is long, because it accumulates quietly across every month it applies.
What to verify, and how
- Challans for every month, per contractor, stored by period and retrievable
- The count on the return reconciling with the people actually deployed
- UAN generated and linked for every eligible worker, and IP registration done
- The contribution base matching the wage register
- No month missing, which is the check people forget to run
The most effective control is contractual: monthly submission of challans and returns as a condition of invoice payment. It changes compliance from something you chase into something that arrives.
PF and ESI are not the same test
They are often spoken about together and they qualify differently, which is a frequent source of error on contract labour:
- Provident fund applicability turns on the establishment and on the employee's wages. Above a prescribed wage level an employee may be excluded, which is why a wage register and a contribution list can legitimately differ, and why a reviewer needs both to check either.
- ESI applicability turns on the establishment, the wage level and whether the location is an implemented area. The same contractor can therefore have ESI obligations at one of your sites and not at another.
The consequence is that you cannot verify a contractor's contributions by eye. You need the wage register and the return side by side, per site, for the month in question. A single consolidated figure for a multi-site contractor tells you almost nothing.
Exits, transfers and the records that outlive the engagement
Contract labour turns over, and each exit is a small compliance event. The worker's contribution history has to remain intact and portable, which means the UAN has to be correct, the exit has to be recorded, and the final month has to be remitted, even though the person has already left.
The same applies when an engagement ends. Registers, challans and returns for the period the contractor worked on your premises remain relevant to you after they have gone, so collect them monthly. Waiting until exit is not the only approach that reliably works. A contractor who has been replaced has very little reason to assemble paperwork for you.
Why this sits with payroll rather than with procurement
Contract labour is usually bought by procurement and managed by operations, which leaves the statutory layer belonging to nobody in particular. The records are payroll records. They reconcile against wages, attendance and filings, and they are read by the same authorities.
Putting them alongside your own payroll cycle, on the same calendar, with the same person responsible for both, removes the gap where these failures live.
Payroll management and compliance management run on the same monthly calendar at SourceIT, which is the point: your own payroll and your contractors' statutory evidence close in the same week rather than in different quarters.
