Contract Labour Compliance in India: Employer Guide 2026

Most Indian SMBs discover contract labour compliance the hard way — during an inspection, a PF authority notice, or a customer's vendor audit — long after the housekeeping team, the security guards, the warehouse loaders and the "contract" data-entry staff have been working on site for years. The uncomfortable truth is that when a contractor fails to pay wages, deposit PF or maintain registers, the liability does not politely stop at the contractor's door. It travels upstream to you, the principal employer.

This guide is a practical operating manual, not a legal treatise. It is written for founders, HR managers, plant heads and payroll teams at Indian small and mid-sized businesses who engage people through manpower contractors, staffing agencies, facility management vendors, security agencies and specialist service providers. It covers registration and licensing basics, principal employer obligations, what belongs in the vendor contract, the monthly document-collection checklist, registers and records, how to run a vendor compliance audit, the failure modes that actually cause trouble, and how an HRMS turns all of this from a panic activity into a routine one.

A standing caveat before we begin: contract labour law in India is a mix of central statute, state rules, state-specific thresholds and periodic notifications. Employee counts that trigger registration, licence fee slabs, form numbers, minimum wage rates and welfare-amenity standards vary by state and are revised from time to time. Treat everything here as directional. Verify the current position for your specific state and industry with the relevant labour department or your compliance advisor before you act.

What "Contract Labour" Actually Means

A worker is contract labour when they are hired for your establishment through a contractor, with or without your knowledge, and are paid by that contractor rather than by you. Three parties exist in the arrangement:

• The principal employer — you. The establishment where the work is performed and which ultimately benefits from the work.
• The contractor — the manpower agency, facility management company, security agency or labour supplier who employs and pays the workers.
• The contract workman — the individual on the ground.

The defining test is not what the paperwork says. It is the practical reality: who supplies the workers, who pays them, who supervises them, who can remove them, and whose business the work forms a part of. A "vendor agreement" title on a document does not convert a labour-supply arrangement into a service contract.

Contract labour vs other engagement models

Founders routinely mix up four very different arrangements. The distinctions matter because each carries a different compliance burden.

The riskiest category for Indian SMBs is the third — the "consultant" who sits at your desk, uses your laptop, reports to your manager, works your hours, and has done so for three years. If a dispute arises, the substance of the relationship, not the label on the contract, is what gets examined.

Why the distinction between "core" and "non-core" work matters

Indian contract labour policy has long distinguished between peripheral activities (housekeeping, security, canteen, gardening, loading, courier) and the core activity of the establishment. Engaging contract labour in the core activity attracts far more scrutiny and, in some situations and states, may be prohibited outright by notification.

Under the Occupational Safety, Health and Working Conditions (OSH) Code framework, this core/non-core distinction is expressed explicitly, with a list of activities that are generally treated as non-core support functions. The practical takeaway for an SMB:

• Using a contractor for facility upkeep, security, transport, catering, gardening, waste handling, courier or similar support activity is normal and defensible.
• Using a contractor to staff the actual production line, the primary service delivery function or the revenue-generating activity for extended periods invites questions about whether the arrangement is a sham to avoid direct employment.
• Seasonal or genuinely intermittent work — where the activity is not performed for most of the year, or is performed for only a limited number of days — is treated differently. Document the seasonality; do not just assert it.

The Legal Framework in Plain English

Two frameworks matter, and for a period they coexist in practice.

The Contract Labour (Regulation and Abolition) Act framework. The long-standing central statute, with state-specific rules layered on top. It requires the principal employer to register the establishment, requires the contractor to obtain a licence, imposes obligations around wages, welfare amenities and records, and gives government the power to prohibit contract labour in specified processes.

The Occupational Safety, Health and Working Conditions Code. Part of India's labour code consolidation, this Code subsumes contract labour regulation along with factories, migrant workers, contract labour, working journalists and several other statutes. It restates the registration/licensing architecture, brings in the concept of an all-India or multi-state licence for contractors, formalises the core-activity concept, and modernises record-keeping toward electronic filing and common registers.

Implementation of the labour codes has been phased and state rule-making has proceeded at different speeds. In practice, many establishments in 2026 are operating under a hybrid: central code provisions where notified, older state rules where they remain in force, and state-specific forms throughout.

What this means operationally: do not build your compliance calendar around a single national template. Build it around the states you operate in. If you have a Bengaluru office, a Pune warehouse and a Gurugram sales floor, you have three sets of state rules, three sets of forms, three minimum-wage notifications and potentially three registration positions.

Other statutes that ride along

Contract labour compliance never stands alone. Whenever contract workers are on your premises, these run in parallel:

• Provident Fund — the contractor must enrol eligible workers and deposit contributions. The principal employer has a well-established backstop duty to ensure this happens for workers engaged through contractors.
• ESI — where the establishment and the wage level fall within coverage, contractor workers must be covered, and the principal employer carries a similar backstop duty.
• Minimum Wages — the applicable state minimum wage for the relevant scheduled employment and skill category applies to contract workers. This is the single most common failure point.
• Payment of Wages / Payment of Bonus / Payment of Gratuity — the contractor is the employer for these purposes, but continuous engagement of the same workers across contract renewals can create exposure.
• Equal Remuneration principles — contract workers doing the same or similar work as direct employees raise pay-parity questions.
• Maternity Benefit — applies to eligible women workers including those engaged through contractors.
• POSH (Sexual Harassment of Women at Workplace) — your Internal Committee's jurisdiction extends to workers at your workplace, including contract workers, interns and visitors. This is frequently missed.
• Shops & Establishments / Factories — hours, weekly off, overtime, night-shift conditions for women, leave.
• Labour Welfare Fund and Professional Tax — state-specific, and often overlooked for contractor headcount.
• Building & Other Construction Workers legislation — where construction, alteration or repair work is involved, a separate and heavier regime applies.

Registration and Licensing: Who Needs What

This is where most SMBs get confused, so let's separate the two obligations clearly.

Principal employer: registration of the establishment

If you engage contract labour at or above the threshold number of workers, you must register your establishment as a principal employer with the appropriate labour authority. Key points:

1. The threshold is a head count of contract workers engaged (in many states measured as workers engaged on any day of the preceding twelve months), not your direct employee count. A 30-person startup with 25 contract housekeeping and security staff can cross the line while a 300-person software firm with two contractors does not.
2. Thresholds differ between the older state rules and the OSH Code framework, and several states have their own numbers. Verify your state's current threshold. Do not assume the number a peer company quoted you.
3. Registration is establishment-specific and often address-specific. A new branch, plant or warehouse usually needs its own registration or an amendment.
4. The registration certificate typically specifies the maximum number of contract workers you may engage. Exceeding that number without amendment is itself a violation — a very common one when a company scales headcount at a warehouse mid-year.
5. Amendments are required on change of address, change of nature of business, change of contractor, or increase in permitted headcount.

Contractor: licence

The contractor must hold a valid licence to supply contract labour, issued by the labour authority for the state (or, under the Code framework, potentially a multi-state or all-India licence). Key points:

• The licence application generally requires a Form V certificate (nomenclature varies by state) issued by the principal employer, confirming that the contractor is engaged by you and that you are the principal employer for the work. You must issue this — it is your document, and issuing it carelessly to a contractor you have not diligenced is a mistake.
• The licence specifies the maximum number of workers the contractor may deploy at your site and the validity period. Both matter. A contractor with a licence for 20 workers deploying 45 at your warehouse creates exposure for both parties.
• Licences require renewal before expiry. Lapsed licences are extremely common and are the first thing an inspector or auditor checks.
• Licences are typically site- and principal-employer-specific under the older framework. The same contractor serving your Chennai and Hyderabad sites may need separate licences.

A worked example

Bharat Components Pvt Ltd runs a 60-person unit in Maharashtra. It has:

• 42 direct employees on payroll
• 14 housekeeping and canteen staff via CleanCo Facilities
• 8 security guards via SecureLine Agency
• 11 seasonal packers via ManpowerBridge for four months a year

Total contract workers on a peak day: 33. The company assumed it was below any threshold because it "only has 60 people". Wrong analysis. The relevant count is contract workers engaged — 33 on peak days, across three contractors. Depending on the applicable Maharashtra threshold, registration is likely required, and each of the three contractors likely needs its own licence naming Bharat Components as principal employer.

The company also assumed the seasonal packers "don't count because they're temporary". Also wrong. Seasonality may affect certain obligations, but it does not make workers invisible for headcount purposes on the days they are engaged.

What Bharat Components should do:

1. Confirm the current Maharashtra threshold and registration procedure.
2. Apply for principal employer registration with a headcount buffer above current peak (so a busy quarter does not breach the certificate).
3. Collect and verify each contractor's licence; issue Form V certificates properly for those that need to apply.
4. Backfill twelve months of wage, PF and ESI evidence from each contractor and identify gaps.
5. Fix any minimum-wage shortfall going forward and take advice on the historical position.

Principal Employer Obligations: The Backstop Liability

This is the heart of the matter. Understand it once and the rest of the guide follows logically.

You are not the employer of contract workers — until the contractor defaults, at which point you effectively become the payer of last resort.

The framework works like this:

The three practical consequences

One: you must supervise payment, not just receive an invoice. A common practice — and a good one — is for an authorised representative of the principal employer to be present at, or to certify, the disbursement of wages to contract workers. In modern practice this becomes: verify bank-transfer proofs for each worker, match them to the attendance you recorded, and sign off before releasing the contractor invoice.

Two: your recovery right is only as good as the money you still hold. The law lets you recover amounts you were forced to pay from money due to the contractor. If you have already paid the contractor in full and they have vanished, your recovery right is a piece of paper. This is why payment terms and retention matter enormously (more on that below).

Three: sustained control creates employment risk. If your managers directly supervise, appraise, discipline, roster and reward contract workers exactly as they do direct employees, and this continues for years, you accumulate risk that the arrangement will be characterised as direct employment. Absorption is not automatic — but the exposure is real, and it is expensive.

What to Put in the Vendor Contract

Most SMB contractor agreements are two pages: scope, rate, payment terms, termination. That is not enough. Here is what a defensible manpower or facility services agreement should contain.

Core commercial clauses

1. Scope of services — described as an outcome or service, not as "supply of X bodies". Where headcount is inherent (security posts, housekeeping shifts), specify deployment schedules and coverage standards.
2. Rate card with statutory build-up — the per-worker cost should be broken into basic wage, allowances, employer PF, employer ESI, bonus provision, leave provision, gratuity provision, uniform/PPE, and the contractor's service charge. If you cannot see the wage component, you cannot verify the minimum wage.
3. Automatic revision on minimum wage notification — the contract must say that rates adjust when the state revises minimum wages, and that the contractor may not absorb the increase by underpaying workers.
4. Invoice conditions precedent — no invoice is payable unless accompanied by the previous month's compliance pack (defined in a schedule).
5. Retention / security deposit — hold back a percentage or a fixed sum, released only after final compliance clearance at contract exit. This is your only real leverage.

Compliance clauses

1. Representation and warranty on holding all applicable registrations and licences — CLRA/OSH licence, PF and ESI registration codes, GST registration, shops or factories registration, LWF and PT registration where applicable — with copies annexed and an obligation to notify lapses within a stated number of days.
2. Obligation to pay wages by a fixed date each month, through bank transfer to the worker's own account, with no cash payments permitted.
3. Obligation to deposit PF and ESI by statutory due dates and share challans and ECR statements.
4. Right to audit — the principal employer may inspect the contractor's records, premises and payroll data, on reasonable notice, including through a third-party auditor.
5. Right to pay workers directly and set off against contractor dues on default, without prior notice beyond a short cure period.
6. Indemnity covering statutory dues, damages, penalties, interest, legal costs and claims arising from the contractor's default, surviving termination.
7. No employer-employee relationship clause — necessary but not sufficient. Behaviour on the ground is what determines the outcome; the clause only helps if your practice matches it.
8. Prohibition on further subcontracting without written consent. Sub-sub-contracting is where compliance chains break.
9. Data protection and confidentiality, including obligations on workers who access your systems or customer data.
10. Background verification standards for deployed workers, with your right to reject any individual.
11. Exit obligations — full and final settlement of workers, PF/ESI clearance, return of assets and access cards, and a compliance certificate before release of retention.

Governance clauses

1. Named compliance contact at the contractor with escalation matrix.
2. Service levels on replacement time, attendance accuracy, uniform standards and grievance turnaround.
3. Worker grievance route into your systems — contract workers must have a way to escalate to you if the contractor is withholding wages. This protects you, because the alternative is that they escalate to the labour officer first.
4. POSH cooperation — the contractor must cooperate with your Internal Committee and share worker details.

Sample rate card structure

Here is how a defensible rate build-up looks. The numbers below are illustrative placeholders to show the structure — do not treat them as current rates. Actual minimum wages vary by state, zone, scheduled employment and skill category, and are revised periodically.

The negotiation discipline that follows: when a contractor undercuts a competitor by 20 percent, ask which line item shrank. If the service charge went from 8 percent to 6 percent, fine. If the wage line dropped below the notified minimum wage, you are buying a liability, not a saving.

The Monthly Document Collection Checklist

This is the operational core of contract labour compliance. Run it every month, without exception, and most of your risk disappears.

Before you release the invoice

Collect, for each contractor, for the previous wage month:

1. Attendance/muster register for deployed workers, reconciled against your own gate or biometric records.
2. Wage register / wage sheet showing per-worker gross, deductions and net, with the wage rate visible.
3. Bank transfer proof — the payment advice or bank statement extract showing credit to each worker's account. Not a consolidated single transfer to a "site account".
4. Wage slips issued to workers (signed acknowledgement or system-generated with delivery evidence).
5. PF ECR (electronic challan-cum-return) for the month, listing the workers deployed at your site.
6. PF challan / payment confirmation with transaction reference.
7. ESI contribution statement and ESI challan for the month, where applicable.
8. Professional Tax challan where applicable in the state.
9. Labour Welfare Fund remittance where applicable and due (many states are half-yearly or annual).
10. New joiner and exit list for the month, with UAN and ESIC IP numbers for joiners.
11. Declaration from the contractor that all statutory dues for workers deployed at your site have been paid, with no arrears.

Quarterly / half-yearly / annual

1. Licence validity check and renewal evidence.
2. PF and ESI registration status check (active codes, no defaults flagged).
3. Bonus payment evidence in the applicable season.
4. Gratuity settlements for exiting long-service workers.
5. Statutory returns filed by the contractor.
6. Insurance — workmen's compensation or equivalent, where relevant.
7. Refreshed KYC of the contractor entity — GST status, PAN, address, directors.

The three reconciliations that matter

Collecting documents is easy. Reconciling them is where the value is.

Reconciliation 1 — Headcount. Number of workers on your gate/attendance record = number on the contractor's wage register = number in the PF ECR = number in the ESI statement. Mismatches are the single strongest early-warning signal. A contractor deploying 40 people at your site but showing 26 in the PF ECR is under-reporting, and that gap is your exposure.

Reconciliation 2 — Wage rate. Lowest wage on the wage register ≥ applicable state minimum wage for that skill category and zone. Check this every time a new minimum wage notification is issued, not once a year.

Reconciliation 3 — Payment reality. Net wage on the wage register = amount actually credited per the bank proof. Contractors under cash pressure sometimes show correct registers while paying late or short.

A worked reconciliation example

Site: Pune warehouse. Month: illustrative. Contractor: ManpowerBridge.

Three red flags in one month. The right response is not to terminate immediately — it is to issue a written non-compliance notice, withhold the invoice under the contract, require rectification with evidence within a defined period, and escalate to termination and retention forfeiture if not cured. Document every step; if the matter later reaches an authority, your file is the difference between "the principal employer was diligent" and "the principal employer knew and did nothing".

Registers, Records and Displays

The paperwork obligations split between the two parties. Under the older framework these are specific numbered forms that vary by state; under the OSH Code framework there is a move toward common and electronic registers. Verify your state's current forms — but the substance is stable.

Records the principal employer typically maintains

• Register of contractors — name, address, nature of work, period of contract, number of workers, licence details.
• Certified copies of contractor licences.
• Copy of the establishment registration certificate, displayed at the premises.
• Attendance / gate records for contract workers.
• Certification of wage disbursement where your representative supervises payment.
• Annual return to the labour authority, where prescribed.
• Notice of commencement and completion of contract work, where prescribed.
• Abstract of the Act and Rules and details of the establishment, displayed in English, Hindi and the local language.

Records the contractor typically maintains

• Register of workmen employed
• Muster roll and wage register
• Register of deductions, fines, advances and overtime
• Wage slips and employment cards
• Service certificate on termination
• Half-yearly return, where prescribed
• PF and ESI records for the deployed workforce

Display and facility obligations at the site

Practical items that inspectors check on a walkthrough, and which SMBs frequently miss:

• Notice of wage rates, wage period, wage payment date and the name of the inspector, displayed prominently.
• Drinking water at accessible points.
• Separate and adequate toilets and washing facilities for men and women.
• First aid box, adequately stocked and not expired.
• Rest room / shelter where the work requires it.
• Canteen where headcount thresholds require one.
• Creche facility where applicable thresholds are met.
• PPE issued and actually worn.
• Emergency exits unobstructed, extinguishers serviced.

Note the pattern: if the contractor fails to provide these, the obligation lands on you. And since the site is yours, providing them yourself is usually cheaper and simpler than arguing about it.

Running a Vendor Compliance Audit

Once a year — twice for high-risk vendors — go beyond document collection and audit properly.

Step-by-step audit process

Step 1: Build the vendor register. List every entity that puts people on your premises. Include the ones nobody thinks of: the pantry boy from the tea vendor, the AMC technician who comes weekly, the courier who sits in your mailroom, the driver pool, the marketing agency's promoter staff. You cannot audit what you have not listed.

Step 2: Risk-tier the vendors. A simple three-tier model works.

Step 3: Issue a pre-audit document request with a deadline. Ask for twelve months of the monthly pack, plus licences, registrations, returns and financial evidence of solvency.

Step 4: Verify licences and registrations independently. Do not accept a PDF at face value. Check PF and ESI codes on the respective portals. Confirm GST status. Confirm the licence number and validity with the issuing authority where possible.

Step 5: Sample-test the payroll. Pick 10 to 15 workers across skill categories and months. For each, trace: attendance record → wage register entry → wage slip → bank credit → PF ECR line → ESI record. A clean trace across all six for every sample is a healthy vendor. Any break is a finding.

Step 6: Walk the site. Check displays, amenities, PPE, ID cards, uniforms and the first aid box. Photograph what you find.

Step 7: Interview workers. Speak to five or six workers privately, without the contractor supervisor present. Ask simple questions: When were you last paid? How much? Into your own bank account? Do you have an ESIC card? Has anyone asked you for money to get this job? Do you get a payslip? Worker interviews surface problems that documents hide — particularly cash-back arrangements, where a worker is shown as paid the correct amount and is then made to return part of it.

Step 8: Grade and report. Produce a findings report with a severity rating, an owner and a due date per finding.

Step 9: Track closure. An audit with no closure tracking is theatre. Findings should sit in the same tracker as any other business action, with reminders.

Step 10: Link outcomes to commercials. Repeat high-severity findings should affect contract renewal, retention release and volume allocation. If there is no commercial consequence, the contractor learns that compliance is optional.

Audit finding severity guide

Common Failure Modes (And How to Avoid Them)

These are the patterns that repeatedly cause trouble for Indian SMBs.

1. "The contractor handles compliance, it's in the agreement." An indemnity clause allocates cost between you and the contractor. It does not remove your statutory obligation, and it is worthless if the contractor is a shell with no assets. Contractual protection and statutory liability are separate things.

2. Paying the contractor 100 percent upfront or immediately on invoice. Your recovery right depends on holding money. Structure payment so that some part is always outstanding, and always hold a retention.

3. Buying on rate alone. The cheapest quote in a manpower tender is often the one that is not paying full statutory dues. Insist on a broken-down rate card and reject bids where the wage line is below the notified minimum.

4. Ignoring headcount drift. Your registration certificate permits a maximum. Festival season, a big order, or a new shift can push you past it without anyone noticing. Set an alert at 80 percent of your permitted number.

5. Letting licences lapse. Contractor licences and your own registration have expiry dates. Put them in a calendar with 90, 60 and 30 day reminders. Renewal applications often need lead time.

6. Cash wage payments. If the contractor pays cash, you have no verifiable proof of payment and no protection. Mandate bank transfer to the worker's own account, and collect the proof.

7. Treating "consultants" as outside the system. A long-tenure "consultant" who works your hours at your desk under your manager is a misclassification risk with tax, PF and employment consequences. Review your consultant list annually and convert those who fail the substance test.

8. Not extending POSH coverage to contract workers. Your Internal Committee's remit covers your workplace. Ensure contract workers know how to complain, are covered by awareness sessions, and that the contractor cooperates.

9. Direct supervision creep. When your team manager rosters, appraises, disciplines and rewards contract workers exactly like employees, the arrangement starts looking like direct employment. Route instructions through the contractor supervisor. Keep performance conversations at the service-level rather than individual-appraisal level where you can.

10. Undocumented subcontracting. You audit ManpowerBridge. ManpowerBridge quietly sources 12 of the 38 workers from a smaller agency with no licence. Your audit trail stops at the wrong layer. Prohibit subcontracting without consent and check worker ID cards against the contractor's own roll.

11. No exit clearance process. A contractor is replaced, workers move to the new agency, nobody settles the old dues, and the claim surfaces eighteen months later. Build an exit checklist: full and final settlements, PF/ESI clearance, no-dues declaration from workers, then retention release.

12. Site records living in someone's drawer. Registers kept in loose files at the site, wage proofs in a WhatsApp group, licences in the plant manager's email. When an inspection happens, you cannot produce anything in time. Centralise.

13. Ignoring state-specific differences in a multi-state footprint. Applying Karnataka's practice to your Haryana site is a reliable way to get something wrong.

14. Treating the annual return as the whole compliance programme. Filing a return is the visible output. The monthly reconciliation is the actual control.

Building the Compliance Calendar

Here is a workable rhythm for an SMB with two to six contractors.

Monthly

• Day 1-5: Freeze attendance for contract workers, share with contractors.
• Day 7-10: Contractor pays wages by the contractual date; collects bank proofs.
• Day 10-15: Contractor deposits PF and ESI within statutory due dates and shares challans.
• Day 15-20: Compliance pack submitted with invoice; HR/payroll runs the three reconciliations.
• Day 20-25: Queries raised and cleared; invoice approved or withheld with written non-compliance notice.
• Month end: Update the vendor compliance dashboard; escalate open items.

Quarterly

• Licence and registration validity review across all vendors.
• Headcount vs registration ceiling review.
• Minimum wage notification check for each state of operation.
• Risk-tier review — has any vendor moved tier?

Half-yearly

• Full audit of high-risk vendors.
• Site walk-through with a physical checklist at each location.
• Worker interview round.
• Review of consultant/freelancer population for misclassification risk.

Annual

• Statutory returns.
• Full vendor re-KYC and financial health check.
• Contract review and renewal, with rate card refresh.
• POSH annual report and awareness refresh covering contract workers.
• Insurance renewals.
• Compliance training for site managers and the procurement team.

What Good Looks Like: A Maturity Model

Most Indian SMBs sit at Level 1 or 2. Getting to Level 3 is a matter of discipline, not budget, and it removes the large majority of practical risk.

How an HRMS Helps

Contract labour compliance is fundamentally a data problem: many workers, many documents, many due dates, many states, and evidence that must be produced quickly when someone asks. Spreadsheets and email do work — until the third contractor and the second state.

Here is where a system like CozyHR changes the day-to-day.

Single vendor master. Every contractor with entity details, PAN, GST, PF code, ESI code, licence number, licence validity, registered address, contact matrix and contract dates in one place — not scattered across email threads.

Expiry alerts. Licences, registrations, insurance and contracts all have dates. Automated reminders at 90/60/30 days stop the single most preventable failure.

Contract worker roster. Contract workers tracked separately from employees, with deployment site, contractor, skill category, ID card status, joining and exit dates, UAN and ESIC IP number. This roster is what you reconcile everything else against.

Attendance capture at source. Biometric, mobile or gate-based attendance for contract workers gives you an independent headcount record — the foundation of Reconciliation 1. Without your own attendance data, you are reconciling the contractor's numbers against the contractor's numbers.

Document workflow with invoice gating. Define the required monthly pack per vendor. The system requests it, tracks what is received, flags what is missing, and holds the invoice approval until the pack is complete. This one control changes contractor behaviour faster than any clause.

Reconciliation reports. Automated comparison of site headcount, wage register headcount and PF ECR headcount, with variance highlighted. Same for wage rates against a maintained minimum wage table per state and category.

Registers and returns. Digital maintenance of the registers you are required to keep, exportable in the formats your state expects, with an audit trail of changes.

Audit module. Checklists, findings with severity, owners, due dates, evidence attachments and closure status — so an audit produces a tracked action list rather than a PDF nobody opens.

Multi-state configuration. Different states, different thresholds, different forms, different minimum wage tables, different LWF and PT rules — configured once, applied automatically.

Evidence on demand. When an inspector visits or a customer runs a vendor audit, you export the last twelve months of compliance evidence for a site in minutes rather than reconstructing it over a fortnight.

Grievance channel. A route for contract workers to raise wage or workplace issues directly to you, so problems surface internally before they surface at the labour office.

A 30-Day Get-Compliant Plan

If you are starting from Level 1 and want to reach Level 3 quickly, this sequence works.

Week 1 — See the picture. 1. List every vendor with people on your premises, at every location. 2. Count contract workers per site, per day, at peak. 3. Collect existing agreements, licences and registrations into one folder. 4. Identify which states you are exposed in and confirm each state's registration threshold and current forms.

Week 2 — Close the obvious gaps. 5. Apply for or amend principal employer registration where required, with headroom. 6. Chase contractors for valid licences; issue Form V equivalents properly for pending applications. 7. Check that every contractor has active PF and ESI codes. 8. Compare current wage rates against each state's current minimum wage notification and fix shortfalls going forward.

Week 3 — Install the control. 9. Define the standard monthly compliance pack and communicate it to every vendor in writing. 10. Amend contracts, or issue an addendum, to make invoice payment conditional on the pack, add retention, add audit rights and add the right of direct payment and set-off. 11. Set up your own attendance capture for contract workers. 12. Build the reconciliation template (or configure it in your HRMS).

Week 4 — Prove it works. 13. Run the first full monthly cycle end to end, including invoice hold for any missing document. 14. Walk each site with the display and amenity checklist. 15. Interview a handful of workers. 16. Build the compliance calendar with all expiry dates and recurring tasks, with named owners. 17. Brief site managers and the procurement team so that nobody signs a new vendor without going through the same gate.

Special Situations

Startups with a single office and a housekeeping vendor. Your exposure is small but not zero. Get the licence copy, get monthly PF/ESI proof, make sure wages meet the state minimum, and keep the file. Ten minutes a month.

Warehousing and logistics. High headcount volatility, high seasonality, multiple contractors at one site, and physical safety risk. This is where headcount ceilings get breached and where safety incidents create the fastest escalation. Track daily deployment against your registration ceiling.

Manufacturing units. Overlapping Factories Act obligations, safety committees, canteen and creche thresholds, and the core-activity question if contract labour is used on the line. Get advice on the core-activity position specifically.

IT and services firms using staffing agencies. The workers may be white-collar and well paid, but the structure is still contract labour. PF is the usual pain point — verify the agency is depositing on correct wages, not on an artificially low basic. Also watch the misclassification risk on long-tenure "contractors".

Construction, renovation and fit-out work. A separate and heavier framework applies to building and construction work, including cess and worker registration obligations. Do not treat a six-month fit-out as ordinary contract labour; get specific advice.

Gig and platform workers. The labour codes introduce specific concepts for gig and platform work, including social security arrangements. If your model relies on delivery riders, field agents or task-based workers, the applicable framework may differ from classic contract labour. Confirm which regime applies before designing your engagement model.

Multi-state remote support staff. If you place a single office assistant or field executive in a state through a local agency, that state's rules apply to that engagement — including its minimum wages, PT and LWF. A one-person deployment still needs a compliant paper trail.

Frequently Asked Questions

1. We only have eight housekeeping staff through a vendor. Do we still need to worry about contract labour compliance?

Registration and licensing thresholds may not be triggered at low headcount, and those thresholds vary by state — verify yours. But the substantive obligations do not vanish. Minimum wages, PF and ESI still apply to those workers, and your backstop liability for the contractor's default still exists. Keep the licence copy (if the contractor has one), collect monthly wage and statutory proof, and keep the file. It is a small amount of work that prevents a disproportionate problem.

2. If our contractor doesn't pay PF for the workers, are we really liable?

The principal employer's backstop duty in respect of workers engaged through contractors is well established in practice. Authorities routinely look to the principal employer where a contractor has defaulted, particularly where the principal employer cannot show it took steps to verify compliance. Your protections are practical ones: verify the ECR and challan every month against your own headcount, hold retention, and preserve the evidence that you exercised diligence.

3. Can we ask our contractor to enrol workers under our own PF code?

Some establishments do operate this way, particularly where the contractor is small or lacks its own code. It simplifies verification but increases the closeness of your relationship with those workers. It is workable, but it needs to be a deliberate decision documented in the contract, not an informal arrangement. Take advice on how it interacts with your establishment coverage.

4. Our contract workers have been at our site for five years. Are we required to absorb them?

Absorption is not automatic, and the answer depends on facts, the nature of the work, whether contract labour has been prohibited in that activity, and the degree of control you exercise. What raises risk sharply is a pattern where the same individuals work continuously for years, are supervised entirely by your managers, do work identical to your direct employees, and the contractor is little more than a payroll conduit. If that describes your situation, get specific legal advice rather than relying on general guidance.

5. What is the single most common finding in a vendor compliance audit?

Headcount mismatch — more workers physically on site than appear in the PF ECR or ESI statement. It is usually driven by the contractor keeping some workers off the statutory books to protect a thin margin. It is easy to detect if you maintain your own attendance record, and almost impossible to detect if you rely solely on contractor data.

6. Do POSH obligations cover contract workers?

Yes. The protection under the sexual harassment legislation extends to women at the workplace, which includes contract workers, trainees, interns and visitors — not just those on your payroll. Your Internal Committee should be equipped to handle complaints from contract workers, awareness sessions should include them, and your contractor agreement should require cooperation with the IC.

7. How do the labour codes change contract labour compliance?

The Occupational Safety, Health and Working Conditions Code consolidates contract labour regulation with several other statutes, restates registration and licensing, formalises the core-activity concept, and enables multi-state or all-India contractor licences along with electronic and common records. The practical direction of travel is toward fewer forms, more digital filing, and clearer definition of where contract labour may be used. Implementation and state rule-making have progressed at different rates, so check the current position for each state where you operate.

8. Should we just convert contract workers into direct employees to be safe?

Sometimes yes — particularly where the workers perform core activity, have long tenure, and are supervised entirely by you. That resolves the ambiguity and often improves retention. But it is not automatically the right answer for genuine support functions like security, housekeeping and catering, where specialist vendors deliver real operational value. Decide function by function: if the work is core, long-running and directly supervised by you, direct employment is usually cleaner. If it is a genuine outsourced support service, keep the vendor model and run it properly.

9. What documents should we be able to produce within 24 hours if an inspector arrives?

Establishment registration certificate; contractor licences; register of contractors; contract worker roster with deployment details; last three months of wage registers, bank payment proofs, PF ECRs and challans, and ESI statements and challans; attendance records; display notices at site; and evidence of welfare amenities. If assembling that takes more than a day, your records are too scattered.

10. Can we terminate a contractor immediately for non-compliance?

Your contract should allow it, with a short cure period for anything remediable and immediate termination for serious defaults such as non-payment of wages or fraudulent records. But the practical sequence matters: issue a written non-compliance notice, withhold the invoice, require rectification with evidence, and only then terminate. That sequence protects the workers (who should be paid regardless), preserves your set-off rights, and creates the documentary record that demonstrates diligence.

Bringing It Together

Contract labour compliance in India is not complicated in concept. It is complicated in administration — many small obligations, spread across states, owned by third parties you do not control, with evidence that must be produced quickly when someone asks.

The controls that actually work are few and unglamorous:

• Know exactly who is on your premises and through which vendor.
• Register your establishment, verify every contractor licence, and never let either expire.
• Write a contract that ties payment to compliance evidence and holds retention.
• Collect the monthly pack and — this is the part most companies skip — reconcile headcount, wage rate and payment reality every single month.
• Maintain your own attendance record so you have an independent number.
• Audit the high-risk vendors properly, including talking to workers.
• Keep everything in one place so the evidence is a report, not an archaeology project.

Do those seven things and you move from "hoping the contractor is compliant" to "knowing, with evidence". That is the difference between a routine inspection and an expensive one.

Everything above can be run on spreadsheets. It just gets harder every time you add a vendor, a site or a state — and the failure modes cluster exactly where manual tracking breaks down: a lapsed licence nobody noticed, a headcount ceiling quietly breached, an ECR that never matched the gate register.

If you would rather have the vendor master, expiry alerts, contract worker roster, attendance capture, document workflow with invoice gating, reconciliation reports and audit tracking running in one place, CozyHR is built for exactly this — HR, payroll and statutory compliance for Indian SMBs, in one system. Start a free trial at CozyHR.com and set up your first vendor compliance workflow this week. Your future self, standing in front of an inspector, will be grateful.

---

This article is general guidance for HR and payroll practitioners and is not legal advice. Thresholds, rates, forms and procedures under contract labour law vary by state and are revised periodically. Verify the current position with the relevant state labour authority or your compliance advisor before acting.