Most factories that use contract labour ask their contractor for proof of PF and ESI payment. Most contractors send something back: a payment receipt, a challan copy, sometimes just a line on the invoice saying statutory dues have been paid. Very few factories check whether that document actually covers the workers standing on their floor. That gap matters, because under both the EPF and ESI schemes the principal employer can be asked to pay contributions the contractor did not. This post explains what a contractor should be sending you each month, how to read it against your own attendance records, and the patterns that suggest something is wrong long before an inspector or an EPFO notice tells you so.
Why this is the principal employer's problem
The contractor is the direct employer of contract workers and carries the primary obligation to register them and deposit PF and ESI contributions. But both schemes look past the contractor when it fails. Under the Employees' Provident Funds Scheme, the principal employer is liable to pay the contributions due for employees engaged through a contractor if the contractor does not, and may then recover that amount from the contractor, typically by deducting it from bills. The ESI Act works the same way: the principal employer is liable for contributions in respect of employees engaged through an immediate employer, with a right of recovery against that immediate employer. The Code on Social Security, 2020 carries this principal-employer responsibility forward; confirm with your labour-law consultant how its rules apply to your establishment. In practice this means a default can surface months or years later, with interest and damages attached, at an address the contractor has long since left. The only real defence is evidence, collected every month, that the money was paid for the right people.
What the contractor should send you every month
For PF, ask for three things. First, the Electronic Challan cum Return, the ECR, filed on the EPFO employer portal for the wage month. The ECR is member-wise: it lists each employee's UAN, name, wages and contribution. Second, the challan generated from that ECR, which carries a TRRN, the Temporary Return Reference Number. Third, the payment confirmation showing that challan was actually paid, not just generated. A challan that was generated but never paid looks almost identical to one that was. For ESI, ask for the monthly contribution statement from the ESIC employer portal, which lists each insured person's IP number, days and wages, along with the payment receipt for that month's challan. If the contractor deploys workers at more than one client, ask them to mark which entries relate to your site, or to file a separate statement for it. A document that shows only a lump-sum amount, with no names, tells you that some money went somewhere. It does not tell you it went to your workers.
Matching the return against your own attendance
The useful check is a reconciliation, and your own records are what make it possible. Take the attendance register or biometric export for the month and compare it with the ECR and the ESI statement. Three questions cover most of it. Does every worker who attended appear in both returns? Does the wage reported for each worker look consistent with the days you recorded and the rate you are being billed? Do the totals roughly match what you paid the contractor for wages that month? You do not need to recompute every rupee of contribution. Rates and wage ceilings are set by notification and revised from time to time, so leave the exact arithmetic to the contractor and your consultant. What you are checking is coverage and consistency: the right people, the right month, wages in the right range. A factory that does this for a sample of workers each month, and for the whole roster each quarter, will catch most problems while they are still small.
Patterns that should worry you
Some mismatches are clerical. Others are signs that contributions are being avoided. Watch for headcount gaps, where the ECR lists fewer members than you have on the floor, often with the newest joiners missing. Watch for under-reported wages, where workers appear in the return but on a wage visibly lower than what attendance and your billing imply, which lowers the contribution paid. Watch for the same small group of names month after month while your actual roster turns over. Watch for returns filed under an establishment code you do not recognise, or under a different entity from the one named in your contract. And watch timing: PF and ESI contributions for a wage month fall due by a fixed date in the following month, so a contractor whose proof keeps arriving late, or arrives for alternate months only, is telling you something about their cash position. Any one of these deserves a direct question. Two or more together deserve a conversation about whether this contractor should still be on your floor.
Checking from the worker's side, with consent
A return is the contractor's own account of what it paid. The independent check is what the worker can see. A worker with an activated UAN can view their PF passbook through the EPFO member portal or the UMANG app, and the monthly credits there come from the employer's actual remittances. ESI insured persons can likewise check their contribution history through ESIC's own channels. Some factories ask a few workers each quarter, voluntarily, to show their passbook to the site HR team, and compare it with the contractor's ECR for the same months. Two cautions apply. It must be the worker's choice, done on their own phone, and nobody on your side should ask for their password or OTP. And it should be framed as protecting the worker, because it is: a worker whose PF was never credited is the person who loses most. Done this way, a quarterly passbook sample is the cheapest audit available to a principal employer.
Writing the checks into the contract
Verification is easier to enforce when the contract already requires it. The agreement with your contractor should oblige them to submit, by a fixed date each month, the member-wise ECR, the paid PF challan with TRRN, the ESI contribution statement and payment receipt, all for the previous wage month and all specific to your site. It should allow the factory to withhold release of the next invoice, or the statutory component of it, until those documents arrive. It should give the factory the right to recover from the contractor's bills any contribution, interest or damages it is compelled to pay on the contractor's behalf, and back that with an indemnity. And it should require the contractor to register every new worker with EPFO and ESIC before, or on, their first day of deployment, not at the end of the month. None of these clauses is unusual. Their absence is what lets a gap run for a year before anyone notices.
A monthly routine that takes an hour
This does not need a compliance team. Assign one person on the factory side, usually site HR or the accounts executive who clears the contractor's invoice. Each month, before the invoice is released, they confirm that the PF and ESI documents for the previous wage month have arrived and that the payment confirmations are genuine paid receipts. They compare the member count in each return with the attendance headcount and note any difference with a reason. They spot-check five or ten workers by name, UAN and IP number, and look for anyone in attendance who is missing from either return. Every quarter, the same person runs the full roster reconciliation and, where workers agree, a passbook sample. Keep each month's documents in one folder per contractor. If a labour inspector or an EPFO enforcement officer ever asks what you did to ensure compliance, that folder is the answer, and it is a much better answer than a contractor's assurance.
PF and ESI defaults by a contractor rarely stay the contractor's problem. Both schemes give the principal employer a liability and a right of recovery, and the right of recovery is only worth something if you find the gap early, while you still owe the contractor money and can withhold it. The fix is not complicated: ask for member-wise returns rather than lump-sum receipts, reconcile them against your own attendance, sample the workers' passbooks with their consent, and write the requirement into the contract. If you are reviewing your current arrangements or evaluating a manpower agency, FactoryForce can walk you through the monthly statutory documents we provide to clients; request a quote or reach us on WhatsApp. Contribution rates, wage ceilings, due dates and the rules under the Code on Social Security are revised periodically, so verify current requirements with your labour-law consultant before relying on any figure.
Related reading
Ready to Get Started?
Need workers for your factory?
Let's talk.
Tell us your requirement — role, quantity, site. We'll have workers on your floor within 48 hours.
Looking for work instead? हैदराबाद में काम चाहिए →