Contract Labour Compliance for Principal Employers India

If you run a factory, a warehouse, an office campus or a retail chain in India, there is a good chance that a meaningful share of the people working on your premises are not on your payroll. They belong to a staffing agency, a facility management firm, a security provider or a manufacturing job-work vendor. That arrangement is perfectly legal and often sensible. But it comes with a catch that many founders and HR heads learn about only during an inspection or a dispute: contract labour compliance India-wide is not just the contractor's problem. It is yours too.

This guide is written for HR managers, compliance leads and founders of small and mid-sized businesses who engage contractors and want to do it safely. We will walk through who is a principal employer, how the legal framework works, what to check before you sign a vendor, what to collect every month, how to supervise wage payment, and how to exit a contractor cleanly. There are checklists, tables and worked examples throughout.

A quick note before we begin. Labour law in India has been in a period of transition, with the older Acts and the newer Labour Codes coexisting in discussion and, depending on notification status, in practice. Thresholds, forms and procedures also vary by state. Treat this article as a practical operating guide, not legal advice, and always verify the current position with your labour counsel or the relevant state labour department before you act.

Why contract labour compliance deserves a seat at the leadership table

Most small businesses treat contractors as a procurement matter. You get a quote, you compare rates, you sign, and the invoice arrives monthly. Compliance is assumed to be "included in the rate."

That assumption is where the risk sits. The cheapest quote is frequently cheapest because something is being skipped: provident fund contributions that are paid on a fraction of actual wages, ESI that is not remitted, or wages paid in cash with no record. When the contractor disappears or defaults, workers do not go looking for the contractor. They come to the gate of the place where they actually worked, which is yours.

Three things make this topic worth your attention:

• Shared exposure. In general terms, Indian labour law places certain obligations on the principal employer as a fallback when a contractor fails to meet them.
• Reputation and continuity. A wage default by a contractor can lead to a stoppage on your shop floor, a union approach or a complaint to authorities.
• Audit and diligence. Customers, lenders and investors increasingly ask about contract workforce compliance during due diligence, especially in manufacturing, logistics and services.

The good news is that a disciplined, repeatable process takes most of the risk out. You do not need a large legal team. You need a clear framework, a monthly rhythm and a system that keeps the records in one place.

Principal employer vs contractor: who is who?

Before anything else, get the vocabulary right, because obligations attach to roles.

The principal employer

In broad terms, the principal employer is the establishment, owner or occupier that engages contract labour for work in or around its premises or for its business. If your company has a factory, shop, office or site, and a contractor supplies workers who perform work there, your company is typically the principal employer.

The contractor

The contractor is the entity that undertakes to produce a given result for the establishment, or to supply workers, through contract labour. This can be a proprietorship, partnership, LLP or company. Common examples include manpower suppliers, housekeeping agencies, security agencies, canteen operators, loading and unloading vendors and job-work units that place their own staff at your site.

The contract worker

A contract worker is generally someone engaged through a contractor, not directly by you. The key tests used in practice include who hires and fires, who pays wages, who controls the manner of work and who has the real day-to-day supervisory authority.

A simple role table

The exact division of duties differs by statute and by state rules, so use this table as an orientation, not a substitute for the text of the law.

The legal framework in plain language

The Contract Labour (Regulation and Abolition) Act

For decades, the central law governing contract labour has been the Contract Labour (Regulation and Abolition) Act, 1970, supported by central and state rules. Its core ideas, in general terms, are:

• It applies above a threshold. The Act covers establishments and contractors that engage a specified number of contract workers. The threshold has historically been twenty workers, though states have varied it. Verify the current figure for your state.
• Registration of the principal employer. Establishments covered by the Act are expected to register with the designated authority.
• Licensing of the contractor. A contractor who employs workers above the threshold must hold a licence, and the principal employer should not engage an unlicensed contractor where a licence is required.
• Wage payment supervision. The contractor pays wages, and a representative of the principal employer is expected to be present to certify payment in the prescribed manner.
• Fallback liability. If the contractor fails to pay wages, the principal employer is generally required to pay and can recover the amount from the contractor.
• Welfare and health facilities. Canteens, rest rooms, drinking water, washing facilities and first aid are expected for workers, with the contractor responsible in the first instance and the principal employer stepping in if the contractor fails.
• Prohibition powers. Appropriate governments may prohibit contract labour in certain processes or operations, on the basis of conditions of work, whether the work is perennial and whether it is incidental to or necessary for the establishment.

How the Occupational Safety, Health and Working Conditions Code approaches this

The Occupational Safety, Health and Working Conditions Code, 2020 (often shortened to OSH Code) consolidates multiple older laws, including the contract labour law, into one code. In general terms, the Code retains the idea of a principal employer, a contractor and a licensing regime, but it changes some of the mechanics. Commentators have pointed in particular to a revised threshold for applicability, a more explicit treatment of core activities and the permitted exceptions for contracting them, and an emphasis on licensing for contractors and registration for establishments.

Here is the sensible way to approach this as a business owner:

1. Check notification status. Whether the Code, its central rules and your state's rules are in force for your establishment is a factual question. Confirm it on the Ministry of Labour and Employment portal and your state labour department website.
2. Check the threshold. Both the old Act and the new Code use headcount thresholds. Do not rely on a figure you read in a blog, including this one. Verify the current number applicable to you.
3. Check transition provisions. When laws change, there are usually provisions about existing licences and registrations. Your counsel can tell you whether your current licences remain valid and for how long.
4. Build to the stricter standard. If you are uncertain, run your contract workforce programme to the higher standard of documentation. The practices in this article are sound under either regime.

The practical point is that the underlying controls barely change: know your contractors, verify licences, supervise payment, keep records, provide facilities and be ready for inspection. A process built on these will survive a change in section numbers.

Related laws that touch contract workers

Contract labour compliance does not sit alone. Contract workers are typically also covered, depending on their wages and the headcount, by:

• Employees' Provident Fund and Miscellaneous Provisions law
• Employees' State Insurance law
• Minimum wages provisions, which are state-specific and scheduled by employment type
• Payment of Bonus and Gratuity provisions, where applicable
• Professional tax in states that levy it
• Equal remuneration, maternity benefit and other labour provisions as applicable
• Labour Welfare Fund, in states where it applies

Again, the Labour Codes on wages and social security are also in the picture. The same advice applies: confirm what is in force.

Core vs non-core activities and the idea of prohibition

One of the most misunderstood areas is the question of what you are allowed to outsource through contract labour at all.

The general idea

Labour law has long worked with the concept that certain work, particularly work that is perennial in nature, essential to the main business and normally done through regular employees, should not be routinely handed to contractors. Where it is, the arrangement can be challenged as a sham or camouflage, and the workers may claim to be treated as direct employees of the principal employer.

The newer framework, in general terms, takes a more explicit approach by distinguishing between core activities of an establishment and non-core activities, and by permitting contracting of core activities only in specified circumstances. Which circumstances qualify, and how "core" is defined for your sector, must be read from the current Code text and rules.

Core and non-core: practical examples

These are illustrations only. Your own analysis should be based on your business.

A short test to run internally

Ask these questions before outsourcing any role:

• Is this work a regular, continuing part of our main business?
• Would our own supervisor direct this worker's tasks hour by hour?
• Is the worker substituting for a vacancy we would otherwise fill with an employee?
• Does the contractor have its own supervision, tools and accountability for results?
• If the contractor vanished tomorrow, would we immediately hire these same people?

If the honest answers lean toward direct control and continuing core work, the arrangement is at risk of being treated as disguised employment. We will return to this under misclassification.

Registration and licensing: the basics

Without quoting form numbers or section references, the general structure works like this.

For the principal employer

• Check if your establishment falls within the scope based on the number of contract workers engaged.
• If it does, register the establishment with the appropriate government authority, which in most cases is the office of the labour department for your state or the central labour authority for establishments under central jurisdiction.
• Keep the registration certificate on file and display or produce it as required.
• Renew or amend when conditions change, such as a new work site or a change in the nature of the business.

For the contractor

• Confirm that the contractor holds a valid licence for the relevant work, location and headcount.
• Match the number of workers authorised in the licence with the number actually deployed. A licence for 40 workers does not cover 90.
• Check the validity dates and renewal status, and diarise the expiry.
• Check that the licence covers the correct establishment and the correct type of work.

Verification steps

1. Ask for a clear copy of the licence and the contractor's registrations.
2. Cross-check the licence number and details with the issuing office or the official portal wherever a lookup is available.
3. Record the verification date, the person who verified and the evidence.
4. Store everything against the vendor's profile so it can be produced on request.

If the threshold in your state means that a small contractor with only a handful of workers does not require a licence, you should still collect every other registration and compliance proof. A low-headcount exemption from licensing does not exempt anyone from paying minimum wages or PF and ESI where they apply.

Vendor due diligence: before you sign

A decent due diligence process takes a few days and saves months of trouble. Here is a checklist you can adapt.

Vendor due diligence checklist

Identity and standing - Constitution documents: incorporation certificate, partnership deed or proprietorship proof - PAN and GST registration, with a check that the GST return filing is regular - Address proof for registered office and operating office - Details of directors, partners or proprietor, with their KYC

Statutory registrations - Contract labour licence, where applicable, covering your location and headcount - PF establishment code and ESI employer code, where applicable - Professional tax registration, where applicable in the state - Shops and establishments registration or factory licence, if relevant to their own operations - Labour welfare fund registration where applicable

Track record - List of current clients and references, with at least two reference calls - Any past notices, disputes or inspection findings - Any litigation involving workers, PF or ESI authorities - Length of operations and attrition levels

Financial and payment capacity - Bank statements or a banker's reference showing the ability to meet payroll before invoices are paid - Willingness to pay wages by bank transfer, not cash - Working capital strength to survive delayed payment from clients

Operational readiness - Supervisor structure for the workers deployed to you - Training and safety processes, especially for hazardous work - Background verification and identity checks for workers, including age proof - Process for replacement and leave cover

Compliance maturity - Sample of last three months' PF challans, ESI challans, wage registers and bank transfer evidence from other clients, with confidentiality redactions as needed - Named person responsible for compliance - Willingness to share data digitally every month

Scoring the vendor

You can turn the checklist into a simple scorecard before onboarding. Give each section a score out of ten, weigh statutory registrations and payment capacity more heavily, and set a minimum passing threshold. A vendor who fails on licensing or on cash wage practices should not proceed regardless of price.

Contract clauses that protect you

A contract cannot erase the principal employer's fallback liability to the authorities, but it can allocate cost, set expectations and give you the leverage to act early. Work with counsel on the wording. Here are the clauses worth discussing.

Compliance warranty

The contractor represents that it holds, and will maintain, all licences and registrations required for the work, pays at least the applicable minimum wages, remits PF and ESI on time and complies with all labour laws. It undertakes to notify you immediately of any notice, inspection or claim.

Document delivery clause

The contractor must deliver a defined set of compliance documents by a fixed date every month (for example, the seventh) as a condition of invoice processing. This is the most powerful practical clause, because it ties your payment to their proof.

Payment mechanics and withholding

Many principal employers pay the contractor in two parts: the wage and statutory component on a fast track, and the service fee after document verification. Some arrangements permit you to withhold payment of an invoice, or a portion, if the monthly compliance pack is incomplete. Draft this carefully so it is not penal or ambiguous.

Right to pay directly

If the contractor defaults, you may want the contractual right to pay wages or statutory dues directly to workers or authorities and to deduct the amount from amounts payable to the contractor. This aligns with the recovery right the law generally gives principal employers, and it makes it simple to act in a hurry.

Indemnity

The contractor indemnifies you against losses, penalties, claims, legal costs and liabilities arising from its non-compliance or from claims by its workers. An indemnity is only as good as the contractor's balance sheet, so pair it with a security deposit or a bank guarantee for larger engagements.

Audit and inspection rights

Reserve the right to audit the contractor's records, wage payment, attendance and compliance filings, on reasonable notice or without notice for statutory or safety reasons. Include the right to speak to workers and to engage a third-party auditor.

Worker conduct, safety and facilities

Set out responsibilities for safety equipment, training, ID cards, uniforms, working hours, overtime payment and the facilities at site. Clarify who bears which cost.

No direct supervision and no employment relationship

Record that workers remain employees of the contractor, that the contractor supervises them, and that the principal employer's contact with them is limited to operational coordination. Of course, the clause is only credible if your day-to-day conduct matches it.

Replacement, continuity and transition

Specify notice periods, the handover of records, the obligation to settle all dues at exit and cooperation during any transition to a new vendor.

Termination for non-compliance

Give yourself a clear right to terminate on repeated or serious non-compliance, with a defined cure period.

Contract clause summary table

Contractor onboarding: the first thirty days

Signing the contract is the start, not the finish. A structured onboarding avoids confusion later.

Step-by-step onboarding plan

1. Create the vendor master. Record legal name, PAN, GST, licence numbers, PF and ESI codes, bank details, authorised signatories and compliance contact.
2. Set the licence and headcount cap. Record the licensed headcount and set a system alert when deployment approaches it.
3. Collect the opening document pack. Licence, registrations, a list of workers with identity and age proof, bank account details of each worker, UAN and ESI IP numbers where applicable.
4. Share the compliance calendar. Tell the contractor exactly what documents are due and when.
5. Brief on site rules. Safety induction, gate entry, ID cards, conduct, facilities and escalation contacts.
6. Register workers at the gate and in your system. Each contract worker gets a unique ID linked to the contractor, the work area and the licence.
7. Name a relationship owner. One person in HR or administration who owns the vendor and a backup.
8. Hold a thirty-day review. Check the first month's pack, attendance reconciliation and any worker feedback.

Worker-level opening checklist

• Government photo ID and age proof
• Bank account in the worker's own name
• UAN and ESI number where applicable, or confirmation that they will be generated
• Signed joining acknowledgement from the contractor
• Safety induction record
• Emergency contact

Deployment and attendance tracking of contract workers in your HRMS

You cannot supervise what you cannot see. The single most useful operational habit is to keep a live record of who from which contractor is deployed where, and for how many days.

What to track

• Contractor-wise headcount against the licensed limit
• Worker-wise attendance, including in and out times, shifts and overtime
• Deployment location and role, so that skill category and minimum wage category can be validated
• Start and end dates, to catch long-tenure patterns that look like disguised employment
• Gate or biometric logs reconciled with the contractor's attendance register
• Absence, leave and replacements, so that the contractor's wage sheet makes sense against your records

Why the reconciliation matters

Contractor invoices are usually based on man-days or man-hours. If your records show 1,840 man-days in a month and the invoice says 2,050, you either have a billing issue or a wage-record issue. The same data supports your wage payment certification and any inspector's question about who was on site.

Worked example: reconciling attendance with a wage sheet

A packaging company engages a housekeeping contractor with a licensed strength of 30. In June, the contractor submits a wage sheet for 34 workers and an invoice for 34 workers.

What to do: hold the invoice, ask for an explanation within a defined number of days, and review whether the extra five names are real workers at another location, ghost names or workers deployed without gate records. Any of these is a compliance or cost problem. Without your own deployment data, you would have paid the invoice.

Within an HRMS such as CozyHR, you can set up contract workers as a separate worker category, link each to a vendor, record attendance through whichever method you use and export contractor-wise summaries for reconciliation. The point is not the tool but the discipline: your record of who was present is independent of the contractor's.

Monthly document collection: the compliance pack

The heart of contract labour compliance is a monthly cycle in which the contractor proves, with documents, that last month was handled properly. Think of it as a mini audit every thirty days.

The monthly compliance pack

A practical note on timing

Statutory due dates for PF, ESI and professional tax differ and may change. Verify the current dates and ask your contractor to deliver documents by a fixed internal date that falls after the statutory payment date, so you are checking evidence of completed payment. Many businesses use the seventh or tenth of the month for wages-related proof and a later date for challans.

Step-by-step monthly workflow

1. Day 1 to 3: Close the month's attendance and deployment data in your system. Share the summary with each contractor.
2. Day 4 to 7: Contractor submits wage sheets and attendance for reconciliation.
3. Before wage day: Compare, resolve differences, and clear the wage sheet for payment.
4. Wage day: Where applicable, an authorised representative of your company is present or verifies payment in the manner required by the rules.
5. Within a week of wage day: Collect bank proof of wage credit.
6. After statutory due dates: Collect PF, ESI and PT challans.
7. Verify. Compare headcount across the wage sheet, ECR, ESI list and your attendance data. All four should tell the same story.
8. Approve the invoice. Only after the pack is complete and verified.
9. Log exceptions. Record any non-compliance, the follow-up date and the resolution.

The four-way match

This single test catches most problems. For each contractor, compare:

1. Workers present in your attendance records
2. Workers on the wage register
3. Workers on the PF ECR
4. Workers on the ESI contribution list (for those eligible)

If the number of workers shrinks as you move down the list, find out why. Some difference can be legitimate: ESI has a wage ceiling, for instance, and some workers may be exempt from PF under the applicable rules. Verify any such exemption claim by looking at the actual wages and the rules rather than accepting the contractor's word.

Principal employer liability: what happens if the contractor defaults

This is the question that keeps compliance leads awake, so let us be direct about the general position while flagging that specifics depend on the statute and facts.

Wages

Under the contract labour law framework, generally, if a contractor fails to pay wages, the principal employer can be required to pay the wages due and then recover from the contractor, either by deduction from amounts payable or as a debt. The Labour Codes retain the broad concept.

Provident fund and ESI

Social security laws commonly provide that where a contractor fails to pay contributions for workers employed through the contractor, the principal employer may be required to pay and can seek recovery from the contractor. The detail, including how the principal employer is defined and how recovery works, comes from the specific statute, so verify under the current provisions.

Facilities, safety and compensation

Where the contractor does not provide statutory welfare facilities, the principal employer is generally expected to step in. In matters of workplace safety and injury compensation, the principal employer's responsibility on its premises is also a practical concern, regardless of the contract.

Worked example: a contractor defaults

A mid-sized electronics assembly unit engages a manpower contractor for 60 workers for general assembly support. In month seven, the contractor delays wages by three weeks, then stops responding. Workers gather at the gate.

What should the principal employer do?

1. Stabilise. Meet the worker representatives, acknowledge the situation and commit to a plan with dates.
2. Establish the facts. Pull your attendance data and the last wage sheet to identify exactly who worked how many days and what is due.
3. Issue notice. Send a written notice to the contractor invoking the contract's right to pay directly.
4. Verify and pay. Pay the verified wage amount to workers' bank accounts, with a signed acknowledgement or a clear transaction record.
5. Check statutory dues. Review PF and ESI status for the period and clear shortfalls through the proper channels, taking advice on the right procedure.
6. Recover. Adjust the amounts against the contractor's pending invoices, security deposit or guarantee, and pursue the balance through the contract's remedies.
7. Transition. Move to a new vendor or direct engagement, and document it.

The company in this story lost time and cash, but not control. The reason is that it had attendance data, a pay-direct right and a deposit in hand. A company without these would have faced the same workers with none of those tools.

The takeaway

Liability exists mostly as a fallback, but it is a real one. The best response is not to hope the contractor never defaults. It is to catch the early signs of trouble, which is what the monthly pack is for.

Wage payment supervision

The contract labour framework has historically expected principal employers to supervise wage payment, in general terms by having an authorised representative present and by certifying the amounts paid. Even if your state or current regime handles this differently, supervising payment is sound practice.

How to supervise without becoming the employer

• Prefer bank transfers. Ask contractors to pay through bank transfer to each worker's own account. This produces evidence and reduces disputes.
• Collect the bank advice. Get the batch file or statement showing individual credits.
• Spot-check. Randomly call a handful of workers each month to confirm the amount received and the date. Do this respectfully and in a way that does not suggest you are directing them.
• Certify what you verified. If you sign a certificate of payment, be sure of what it says. Do not sign a blank or pre-printed certificate without checking.
• Match to the wage sheet. Net pay on the bank statement should equal net pay on the wage sheet.
• Watch deductions. Unexplained deductions for uniforms, tools, "commission" or "advances" are a red flag, and unlawful deductions can create liability.
• Treat the due date seriously. A late wage payment is not a technicality. It is the most common trigger for worker unrest.

Minimum wages for contract workers

Minimum wages are set by state governments (and by the central government for certain central-sphere establishments) and are scheduled by industry or employment category and by skill level. Rates are periodically revised, often with a variable dearness component.

What this means in practice

• Contract workers are entitled to at least the applicable minimum wage for their category. The contractor's margin cannot come out of the worker's statutory minimum.
• Classification matters. Whether a worker is unskilled, semi-skilled, skilled or highly skilled, and which schedule applies, determines the rate. Mismatches are a frequent inspection finding.
• Overtime has its own rules. Verify the overtime rate and working hours rules in your state.
• Parity and equal pay concepts may apply. Where contract workers perform the same or similar work as regular employees, the law and the courts have in certain contexts looked at pay parity. Take advice for your sector.

Worked example: checking a contractor's pricing

A company in a state where the applicable minimum wage for unskilled housekeeping work is, say, a given monthly figure W (use the actual current notified number in your case) receives two quotes for 20 housekeeping workers.

The sanity check is simple. Take the minimum wage for the category, add the employer's statutory contributions that apply, add provision for bonus and leave where applicable, add a reasonable service fee and GST. If a quote is below the total, ask the vendor how it expects to comply. A price that cannot cover compliance is a warning.

Pricing structure that works

Ask vendors to price in a transparent format: wages, statutory contributions, bonus and leave provisions, other benefits, service fee, taxes. This makes it easier to see when something has been left out and easier to adjust when minimum wages are revised.

Equal facilities and welfare at the workplace

Workers who work in your premises are going to use your canteen area, your restrooms and your drinking water. The law generally expects basic welfare arrangements, and good practice expects dignity.

The common baseline

In general terms, the following facilities should be available to contract workers in line with the applicable law and the size and nature of the workplace:

• Safe and sufficient drinking water
• Clean toilets and urinals, with separate arrangements for women
• Washing facilities
• Rest rooms or rest shelters where work requires them
• A canteen where the headcount and the law require one
• First aid arrangements
• Crèche facilities where the law requires and the number of women workers reaches the threshold
• Personal protective equipment for hazardous or specific tasks
• Lighting, ventilation and basic safety standards at work stations

Who provides what

The contract and the law usually give first responsibility to the contractor for the facilities for its own workers, with the principal employer expected to step in if the contractor does not provide them. In practice, since the work happens on your premises, the sensible approach for most SMBs is to extend your own facilities to contract workers and settle the cost in the commercial terms.

Equal treatment as a culture issue

Separate and visibly inferior facilities for contract workers create friction and can create legal exposure. Use common-sense standards:

• Same drinking water points and clean toilets
• Same safety rules, with the same enforcement
• Same access to the canteen, with subsidised pricing based on a clear policy
• Same grievance channel, or a clear route to the contractor's grievance mechanism and to HR

Facility audit checklist

• Are drinking water points working, clean and accessible to contract workers?
• Are there sufficient toilets for the headcount on each shift?
• Are women's facilities separate, safe and lit?
• Is there a place to rest, eat and store belongings?
• Is first aid stocked and are trained people on each shift?
• Are PPE and training provided for relevant tasks?
• Is there a contact for complaints that workers know about?

Misclassification risk: when the contractor is a label

Misclassification is the biggest strategic risk in contract labour. It happens when workers are treated as contract workers on paper but function as your employees in reality.

Warning signs

• Workers have been on the same contractor roll doing core work for years, with no change
• Your managers assign tasks, set hours, grant leave and conduct performance conversations
• Contract workers wear your uniform and carry your identity cards that are indistinguishable from employees
• The contractor has no supervisor and exists only to run payroll
• The contractor changes, but the same workers stay and continue
• The headcount of contract workers exceeds regular employees in core operations
• The contractor is owned or controlled by someone close to the principal employer

What is at stake

If the arrangement is judged to be a sham or a camouflage, in general terms the consequences can include claims by workers to be treated as direct employees, liability for differences in wages and benefits, penalties and, in some regimes, prosecution. The legal tests and the outcomes depend on the facts and the law in force, so take advice if you spot several warning signs.

Reducing the risk

1. Map your workforce. List each contract role and classify it as core or non-core, using the questions in the earlier section.
2. Move true core roles to direct employment. If a role is permanent and central, consider hiring directly.
3. Respect the separation. Instruct contractor supervisors and let them instruct workers. Avoid managers giving individual direction to workers.
4. Keep identity distinct. Different ID cards, clear signage of the contractor's name.
5. Review tenure. Flag any contract worker with a long continuous stay in the same role for review.
6. Document the contractor's independence. Its own supervisors, its own tools, its own accountability and its own results.
7. Consider fixed-term employment. Where the law permits, a fixed-term direct arrangement can be a cleaner option for defined-duration needs. Verify the current rules.

The audit calendar

Compliance happens when it is scheduled. Here is a sample calendar you can adapt.

Set reminders in your HRMS or your calendar tool so that none of this relies on memory. The calendar looks long, but each item is small if done on time. It is only expensive when it accumulates.

Red flags that should trigger action

Keep this list near the vendor file. Any one of these is a reason to ask questions. Several together are a reason to escalate.

• The contractor submits documents late, repeatedly, or in an incomplete pack
• PF or ESI returns filed but payment is not evidenced
• Workers say they have not received wage slips or that deductions are unexplained
• Wages are paid in cash or into one account, or paid in instalments over a long period
• Headcount on invoices differs from your gate records
• The contractor's quoted rate is well below the compliant cost
• The licence is expired, for another site or for fewer workers than deployed
• Workers do not know the name of their employer or whom to call
• Frequent contractor staff changes, with workers complaining of unpaid dues
• Contractor staff unreachable, or your calls routed to an unrelated number
• Sudden demands for advance payment or bulk payment
• Workers under the legal age or without any identity records
• Safety incidents that are unreported or not recorded
• Resistance to audit

How to respond

1. Record the observation with date and evidence.
2. Raise it in writing with the contractor and set a deadline.
3. Increase scrutiny, such as a surprise wage verification.
4. Withhold a portion of the invoice if the contract allows.
5. Escalate to leadership and counsel if unresolved.
6. Prepare a contingency plan for replacement, in case you need to move quickly.

Handling inspections

Labour inspections are a normal part of operating. Inspectors may visit your premises, ask for records of your own employees and your contractors' workers, and speak to workers. How you prepare matters more than how you respond on the day.

Before an inspection: readiness

• Keep a central file or folder for each contractor, with licence, contract, and the last twelve months of monthly packs.
• Display the required notices and registrations as the rules require.
• Maintain the registers expected of the principal employer in the current rules, in the prescribed format, whether in paper or electronically where permitted. Verify what is accepted in your state.
• Make sure someone senior knows where everything is, and who to call.
• Brief security and reception on how to receive an inspector courteously and whom to alert.

During an inspection

1. Be courteous and cooperative. Verify the inspector's identity and authority.
2. Call your compliance lead and, if appropriate, counsel.
3. Provide what is asked for, and no more. Hand over copies, not originals, and keep a log of what was provided.
4. Do not coach or pressure workers. Honest answers from workers matter, and any appearance of interference creates trouble.
5. Take notes. Record the questions, requests and observations.
6. Ask for a written record of any observations or deficiencies, and note timelines for rectification.

After an inspection

• Prepare a gap list from the inspector's observations.
• Assign owners and dates and close the gaps.
• Communicate with the contractors concerned.
• Respond within the time given, with documents as evidence.
• Update your checklists to prevent repetition.

Record retention

Records are your defence. The right retention period depends on the statute, but the general principle is to keep records for longer than you think you need.

Practical approach

• Follow the longest applicable period. Different laws specify different periods for registers, returns and wage records. Confirm these and apply the longest across the set.
• Keep records until disputes are resolved. If a claim, notice or inquiry is open, hold the relevant records until it is closed, regardless of normal schedules.
• Keep records of exited contractors. Dues and claims can surface after a contract ends.
• Digitise and back up. Scan the paper originals, index them by vendor and month and store access-controlled copies.
• Protect personal data. Contract workers' identity documents and bank details are personal data. Limit access, and follow your data protection obligations.

A suggested record structure

For each contractor, maintain a folder with:

1. Vendor master data and due diligence file
2. Contract, amendments and annexures
3. Licence and registration copies, with validity dates
4. Worker master list with deployment history
5. Monthly compliance packs, by month
6. Wage payment verification and certificates
7. Correspondence on compliance issues
8. Inspection records and responses
9. Scorecards
10. Exit documentation

The vendor scorecard

A scorecard converts opinions into numbers and makes renewal decisions easier to defend. Keep it simple enough that it is actually completed each quarter.

A sample scorecard

How to score and use the result

1. Score each dimension from one to five each quarter.
2. Multiply by weight to get a total.
3. Define bands. For example, a strong score means continue as is, a middle score means a corrective plan, and a low score means a notice and possible replacement.
4. Share the scorecard with the vendor. Vendors improve when they see what is measured.
5. Use scores in renewal and rate negotiations.

Note the weighting. Compliance and wage payment carry half the weight, since those are the areas of greatest legal and human consequence.

Exiting a contractor and transitioning workers

Contractor exit is where many principal employers get caught. The relationship ends, dues are unresolved, workers are anxious and the new vendor is not yet ready.

Planning the exit

1. Decide the reason and the date. Whether non-renewal, termination for cause or a business change, give notice as the contract requires.
2. Freeze new deployment. No new workers from the outgoing contractor from the notice date, unless needed.
3. Request a closing compliance pack. All final-month wages, PF, ESI and PT proofs, bonus and leave accruals, and any other dues.
4. Reconcile final dues. Prepare a settlement statement of amounts owed to workers and to authorities, and amounts owed by you to the contractor.
5. Hold back a reasonable retention. Keep a portion of the final payment until the contractor produces proof of final settlements and statutory filings, as the contract allows.
6. Collect the records. Ask for a handover of worker lists, attendance and wage records for your period.
7. Collect assets. ID cards, uniforms, tools, access cards.
8. Close access. Remove system and physical access for the contractor's staff.
9. Obtain a no-dues confirmation. From the contractor, and where possible, acknowledgements from workers that dues are cleared.
10. Keep the file. Retain the full vendor file under your retention policy.

Worker transition

When a new contractor takes over, the workers often want to continue. A few points of good practice:

• Be clear about rights. Ask counsel whether any statutory or contractual rights of workers are affected by the change, such as retrenchment compensation, notice or benefits, and who owes them.
• Treat workers fairly. Where the new vendor is willing to absorb them, make sure the transition is smooth and well documented.
• Avoid orchestrating retention. Do not tell the outgoing contractor to pressure workers or tell workers to resign from the old contractor in a way that damages their entitlements.
• Check continuity. For PF and ESI, make sure the UAN and IP numbers are carried forward and that service history is not lost.
• Communicate early. Workers who hear about a transition from rumours become anxious. A clear message on dates, pay and continuity prevents disruption.
• Watch for misclassification risk. Moving the same workers from contractor to contractor with no change in work can reinforce the appearance of disguised employment. Review whether those roles should become direct hires.

Worked example: a clean exit

A logistics SMB decides not to renew a loading and unloading contractor with 45 workers. They issue a ninety-day notice and ask for a closing pack. They reconcile attendance and discover one month of PF contributions is unpaid. They withhold an amount equal to the dues and the contractor pays the contributions within two weeks and sends the challan. The new contractor is introduced to workers in week eight, the PF and ESI numbers are carried over and the final payment goes out after the no-dues confirmation. Because the retention clause existed and the data was in one place, the transition took no stoppage.

Checklists you can copy

Before engaging a contractor

• Scope and nature of work classified as core or non-core
• Applicability of licensing and registration confirmed
• Due diligence checklist completed
• Quote analysed against minimum wage and statutory cost
• Contract includes compliance, indemnity, audit and pay-direct clauses
• Security deposit or guarantee agreed where appropriate
• Compliance calendar shared

Every month

• Attendance and deployment closed and shared
• Wage sheets reconciled and approved
• Wage payment verified with bank proof
• PF, ESI and PT challans collected and checked
• Four-way match completed
• Licence headcount cap respected
• Invoice approved only after the pack is complete
• Exceptions logged

Every quarter

• Vendor scorecard completed
• Facilities audit done
• Worker spot-checks completed
• Legal updates reviewed
• Red flag log reviewed

Every year

• Licence and registration renewals verified
• Contract and rate review, including minimum wage revisions
• Misclassification review
• Inspection drill
• Record retention clean-up, with legal holds respected

Using an HRMS to make this repeatable

None of this requires software, but it gets easier with the right system. A spreadsheet-based approach works with two contractors. At ten contractors and several hundred workers, it breaks down in subtle ways: versions diverge, a document goes missing and no one notices that a licence expired in March.

What to look for in an HRMS for contract labour compliance:

• A separate worker category for contract workers, linked to the vendor
• Vendor profiles with licence numbers, validity dates and headcount limits
• Attendance capture and contractor-wise summaries
• Document tracking with due dates and reminders for the monthly pack
• Alerts for licence expiry and headcount breach
• Exportable reports for audits and inspections
• Role-based access, so that vendor data and worker identity documents are protected
• Payroll integration where you pay some workers directly, so that your direct employees and contract workers are visible in one place without being confused

CozyHR is built for Indian SMBs and takes this kind of operational record-keeping seriously, so that your compliance evidence lives with your people data rather than in scattered folders.

Frequently asked questions

1. Who is a principal employer under contract labour law?

In general terms, a principal employer is the owner, occupier or person responsible for the establishment where contract workers are engaged to work. If a contractor supplies workers to your premises or for your business, your company is typically the principal employer. The exact definition varies by statute, so check the text under the law applicable to you.

2. Is the principal employer responsible if the contractor does not pay wages or PF?

Generally, yes, as a fallback. Labour and social security laws commonly require the principal employer to pay if the contractor defaults, with a right to recover from the contractor. The specific mechanism and the extent differ by law, so take advice. The most reliable protection is early detection through monthly document checks.

3. Do all contractors need a licence?

Not always. Licensing generally applies where the contractor engages workers above a headcount threshold, and the threshold has varied across laws and states. Verify the current threshold under the law in force for your state. Even where a licence is not required, minimum wages, PF, ESI and other obligations may still apply.

4. Can we outsource our core activities to contractors?

Traditionally, contracting perennial core work has been risky because it can be treated as a sham arrangement. The newer framework approaches core and non-core activities more explicitly, with limited exceptions. Check the current Code text, the rules and your state position, and seek advice before outsourcing core functions.

5. What documents should we collect from contractors every month?

At a minimum: the wage register, attendance register, bank proof of wage payment, PF ECR and payment challan, ESI challan and employee list, professional tax challan where applicable, wage slips and proof that the licence and insurance remain valid. Reconcile them against your own attendance data using the four-way match.

6. How is contract labour different from fixed-term employment?

Contract workers are employed by the contractor, who is responsible for their wages and compliance. Fixed-term employees are employed directly by your company for a defined period and typically receive benefits comparable to permanent employees as the law provides. The right choice depends on the nature of the work, and fixed-term employment can reduce misclassification risk for defined-duration needs. Verify the current rules.

7. Can we pay contract workers directly to avoid problems?

Paying workers directly can be a risk in itself, since it can strengthen the argument that they are your employees. Where you need to pay directly as a contingency after default, do it under a clear contractual right and legal advice, and record the reason and recovery.

8. How long should we keep contractor compliance records?

Keep them for at least the longest period required by the applicable laws, and longer if any dispute is open. Many businesses keep contractor files for several years after exit. Confirm the retention periods applicable to you with counsel, and keep records indexed by vendor and month.

Conclusion: build the rhythm, and the risk shrinks

Contract labour compliance India-wide can look intimidating because the legal framework is layered, state rules differ and the rules are evolving. But the practical programme is surprisingly consistent: choose vendors carefully, write a contract that gives you leverage, onboard properly, track who is on site, collect proof every month, supervise wage payment, treat workers fairly, review vendors on a schedule and exit cleanly when needed.

You do not need to be a labour law expert to do this well. You need to know the questions to ask, to make sure the answers arrive in writing, and to keep them where you can find them. Verify the current notification status, thresholds and procedures with your counsel or labour department, and adjust the process as the rules settle.

If you are managing contractors with spreadsheets, shared drives and reminders in your head, it may be time to bring this into the same system where you manage your people. You can try CozyHR to track contract worker deployment and attendance, keep vendor details and compliance documents in one place, and stay ahead of monthly deadlines, without turning HR into a full-time paperwork shop. Start small with your largest contractor, build the monthly rhythm, and extend from there.