Pull up a chair. Let me explain something that surprises almost every new HR person the first time a contractor’s workers gather outside the gate demanding unpaid wages: they are not your employees, and yet the problem is yours.

Start with the vocabulary, because the law is built on two words. The principal employer is the company that owns the establishment where the work happens, say your factory or your campus. The contractor is the outside firm that supplies the people: housekeeping staff, loaders, canteen workers, security guards, sometimes even technicians on the shop floor. The workers are on the contractor’s payroll. You pay the contractor an invoice. Simple, yes? That simplicity is exactly what the statute is designed to prevent from becoming an escape route.

The law you are really dealing with

For decades the governing law was the Contract Labour (Regulation and Abolition) Act, 1970. It applied to establishments that engaged twenty or more contract workers, and to contractors who employed twenty or more. Under the Occupational Safety, Health and Working Conditions Code, 2020, the same ground is covered, and the threshold moves to fifty workers. Do check which provisions have been notified in your state and what your state rules say, because implementation of the Labour Codes has been uneven and rules differ.

The structure survives the change. You, the principal employer, register your establishment. The contractor must hold a licence. Work is expected to go through licensed contractors only. If either side skips this, the arrangement is on weak ground from day one.

What stays with you even though you are not the employer

Think of it as three layers of responsibility.

Wages come first. The contractor is primarily liable to pay wages on time, and the law expects a representative of the principal employer to be present when wages are disbursed and to certify the payment. If the contractor does not pay, the principal employer must pay the contract workers and can then recover that amount from the contractor, typically by adjusting it against what you owe him. Notice what this means in practice: you may end up paying the same wage twice, once inside the contractor’s invoice and again to the workers directly, and then chase the money back.

Second layer, welfare and safety. The contractor is meant to provide drinking water, toilets, rest rooms and, above a size, a canteen and a creche. If he does not, the duty falls on you. The factory floor or the site is yours, so safety obligations there are yours too, whoever signs the worker’s pay slip.

Third layer, social security. Under the provident fund and ESI laws, the principal employer is answerable for contributions of contract workers if the contractor defaults, again with a right of recovery. This is where many unpleasant surprises come from, because an inspector looking at a missing PF payment for forty guards will not be interested in your commercial contract.

A small example with numbers

Suppose a warehouse engages a housekeeping contractor for 60 workers at ₹14,000 a month each. The contractor is late by one month because his own client has delayed his payment. The monthly wage bill is 60 × 14,000 = ₹8,40,000. You can wait and let workers stop work, which in a warehouse near a dispatch deadline costs far more. Or you pay the ₹8,40,000 directly, take receipts, and deduct it from the contractor’s next bill. The second option is the legally sanctioned one, and the better habit is to design the contract so that it is routine: a clause giving you the right to pay and adjust, plus a monthly proof-of-compliance pack before you clear any invoice.

Checking the contractor before the problem, not after

Here is the routine I would want from you, in the order it should happen:

  1. Verify the licence and its validity, and that the number of workers sent does not exceed what the licence permits.
  2. Ask for the monthly PF and ESI challans, and match the headcount on them against the attendance at your gate. A challan for 40 when 60 turn up is a flag.
  3. Confirm wages are paid by bank transfer, and that the minimum wage for the category and state is met.
  4. Keep the registers the law asks you to keep for the establishment, and make sure your contractor keeps his.

Only after this should accounts release payment. Many companies do it the other way round, and then wonder why finance and HR keep arguing.

The question of core work

The older law let appropriate governments prohibit contract labour in certain processes. The OSH Code goes further: it generally bars contract labour in core activities, with exceptions such as when the work is so specialised that the principal employer’s regular workers cannot do it, or when the activity does not need full-time workers, or when a sudden spike has to be met. What counts as core is defined in the Code as the activity for which the establishment is set up, and the activities directly related to it. Expect grey areas, for example whether machine operation in a plant is core. This is a place to take legal advice instead of guessing.

There is also a doctrine you should know exists. If a court finds that the contract is a sham, meaning the contractor is a mere name while you control the work, supervise the people and decide who stays, the workers may be held to be your direct employees, with all the rights that implies: regular status, back wages, the lot. Indian courts have looked at control and the genuineness of the contractor’s role rather than the label on the agreement. So the practical advice is dull but important. Let the contractor actually supervise his people. Do not hand out your own attendance cards and appraisal forms to them.

Next time someone says contract staff are not HR’s problem, ask them a gentler question: who will pay if the contractor disappears next month? The honest answer is the one that explains this entire law.

Figures and names in the examples are illustrative.

Leave a Reply

Trending