[Analysis] Principal Employer and Contractor Wage Compliance under the Code on Wages 2019 – Worker-wise Verification | Invoice Release Control | Contractor Scorecard
- Blog|Labour & Industrial Laws|
- 15 Min Read
Section 55 of the OSHWC Code makes the principal employer liable if a contractor fails to pay or short-pays wages. Monthly checks, invoice holds and scorecard.
- By Taxmann
- |
- Last Updated on 16 November, 2026

Table of Contents
- Is a principal employer liable for unpaid contractor wages?
- Which contractor arrangements need review under the new labour codes?
- What is a core activity, and when can contract labour be used in it?
- What should be checked before a contractor is engaged?
- What does the monthly contractor compliance flow look like?
- What should a contractor submit every month?
- How should contractor wages be verified worker-wise?
- What should be checked before releasing a contractor invoice?
- What are the red flags, and how does the contractor scorecard work?
- Which records and contract clauses protect the principal employer?
- Quick answers
1. Is a principal employer liable for unpaid contractor wages?
Yes, where the contractor defaults. Section 55 of the Occupational Safety, Health and Working Conditions Code, 2020 (the OSHWC Code) makes the contractor responsible for paying wages to each contract labour employed by him before the expiry of the period prescribed by the appropriate Government. If the contractor fails to pay within that period or makes short payment, the principal employer is liable to pay the wages in full or the unpaid balance to the contract labour concerned and recover the amount from the contractor (paras 13.10 and 18.15). Taxmann’s HR Guide to Code on Wages calls this the main reason contractor payroll must be verified every month.
Yet principal employers often verify contractor invoices but not worker wages: the file may hold the invoice, GST details and an attendance summary, but not the worker-wise wage register, bank payment proof or PF and ESI proof (para 28.31). When wages go unpaid, workers may approach the principal employer, the Inspector-cum-Facilitator or the claims authority.
The law sits in more than one code, as the book explains (paras 18.3, 18.14, 18.15, 18.22 and 32.3):
| Subject | Where the book places it |
|---|---|
| Contract labour provisions, including licensing and the restriction on contract labour in core activities | OSHWC Code, mainly Chapter XI, Part I |
| Contractor’s responsibility for wages, and the principal employer’s liability if the contractor fails to pay or short-pays | Section 55 of the OSHWC Code |
| Welfare facilities to be provided by the principal employer to contract labour employed in the establishment | Section 53 of the OSHWC Code, with sections 23 and 24 |
| Inter-State migrant workers, where ten or more are employed or were employed on any day of the preceding twelve months | Part II of Chapter XI of the OSHWC Code |
| Minimum wages, overtime, payment of wages, authorised deductions, wage slips and claims | Code on Wages, 2019 |
| Social security obligations | Code on Social Security, 2020, wherever applicable |
Principal employer responsibility also covers the site. Under the Occupational Safety, Health and Working Conditions (Central) Rules, 2026 (the Central OSHWC Rules), where contract labour works at its premises, the principal employer is responsible for facilities such as toilets, drinking water, a first aid box, a canteen and a crèche. These rules apply to Central sphere establishments; State sphere establishments must check the relevant State Rules.
2. Which contractor arrangements need review under the new labour codes?
Any arrangement that places a contractor’s workers in or in connection with the work of the establishment, once the legal thresholds and conditions are met. The contract labour part of the OSHWC Code applies to every establishment in which fifty or more contract labour are employed, or were employed on any day of the preceding twelve months, through contract, and to every manpower supply contractor who employed fifty or more contract labour on any day of that period (para 18.3).
Intermittent or casual work is excluded, but work is not intermittent merely because the employer calls it temporary. Broadly, work done for more than one hundred and twenty days in the preceding twelve months, or seasonal work done for more than sixty days in a year, may not get the exclusion. The threshold should be monitored periodically during the year, not only at vendor onboarding.
Coverage is not limited to factories, and an agreement titled “service agreement” may still involve contract labour if the substance is manpower deployment. The book tells genuine outsourcing from manpower supply this way (para 18.23):
| Factor | Genuine outsourcing | Manpower supply risk |
|---|---|---|
| Vendor delivers a defined result | Yes | Usually weak |
| Vendor supervises workers | Yes | Principal employer supervises |
| Payment basis | Service output, SLA or deliverable | Headcount, man-days or hours |
| Control over attendance | Vendor | Principal employer |
| Tools and systems | Vendor may provide | Principal employer provides |
| Substitution of personnel | Vendor controls | Principal employer controls individual persons |
| Integration with the principal employer’s team | Limited | High |
| Compliance risk | Lower | Higher |
Where the principal employer selects the individual, controls attendance, assigns daily work, approves leave, supervises output and treats the person like its own employee, the arrangement should be reviewed carefully.
3. What is a core activity, and when can contract labour be used in it?
A core activity is any activity for which the establishment is set up, including any activity essential or necessary to that activity, as the OSHWC Code defines it (para 18.7). The OSHWC Code generally prohibits contract labour in core activities, allowing it only in limited situations. These include an activity ordinarily done through a contractor in the normal functioning of the establishment, an activity that does not require full-time workers for the major portion of working hours or for longer periods, and a sudden increase in the volume of core work that must be completed within a specified time.
The OSHWC Code also recognises that support activities such as sanitation, security, canteen, loading and unloading, housekeeping and transport are not to be treated as essential or necessary if the establishment is not set up for them. The nature of the establishment still matters: security may be a support activity for a software company but core for a security agency. A one-line statement that “the activity is non-core” is not enough where the facts are complex (para 18.8). The book’s classification control (para 28.32):
| Classification | Review required before deployment |
|---|---|
| Core | Avoid or legally review |
| Non-core | Document support nature |
| Intermittent | Record temporary requirement |
| Temporary volume increase | Document sudden demand |
| Specialist outsourced service | Record expertise and service output |
| Manpower supply | Apply contractor controls |
The work order should state whether the activity is core or non-core, and where a core deployment relies on an exception, the reason should be documented separately. While that note is prepared, Taxmann AI, a legal research and drafting assistant, can be asked the specific question against the law.
In the book’s example, a manufacturer deploys 90 contract workers in machine operation throughout the year, with no seasonal pattern, no documented surge in volume and no legal review. The steps are to stop automatic invoice clearance, prepare a core activity review note, check whether a statutory exception applies, review fixed-term employment or direct hiring, obtain legal review and document the management decision (para 32.29). Contract labour in core activity, the book says, should never be a silent practice.
4. What should be checked before a contractor is engaged?
The licence, the work order and the contractor’s compliance set-up, before anyone is deployed. A contractor covered by the contract labour provisions cannot supply or engage contract labour except under and in accordance with a licence, which deals with matters such as the number of contract labour, the nature of work and conditions including hours of work, wage fixation and essential amenities. GST registration, PAN, MSME registration or a commercial invoice is not a substitute for labour licence compliance.
The risk is the principal employer’s too: employing contract labour through a contractor who is required to obtain a licence but has not obtained it is deemed to be in contravention of the OSHWC Code (para 18.12). The book’s practical control is to block vendor code activation until licence documents are uploaded and verified, with alerts from the vendor master before licence expiry. Under the Central OSHWC Rules, the contractor must also intimate details of the contract work order within fifteen days of receiving it (para 18.13). The pre-engagement review (para 18.30):
| Area | Check before engaging the contractor |
|---|---|
| Legal status | PAN, GSTIN, incorporation or registration |
| Labour licence | Required and valid where applicable |
| PF and ESI | Registrations available where applicable |
Three of the fourteen areas are shown here. The full pre-engagement review is in para 18.30 of the book.
Mistake 31 in the book’s list is engaging a contractor on a commercial quote alone, without checking the licence, worker count and statutory registrations (para 28.33).
5. What does the monthly contractor compliance flow look like?
An eight-step cycle that runs from the contractor’s submission to the invoice decision and archiving. The book’s monthly rule is that no contractor invoice should be approved unless the contractor has submitted worker-wise wage proof and the principal employer has reviewed minimum wages, overtime, deductions and statutory remittance proof (para 32.4). The steps and their owners (para 32.5):
| Step | Action | Owner |
|---|---|---|
| 1 | Contractor submits the invoice and compliance documents | Contractor |
| 2 | Site team verifies worker deployment and attendance | Site/Admin |
| 3 | HR verifies the worker list, skill category, minimum wages, overtime and deductions | HR/Payroll |
| 4 | Finance verifies bank payment proof and statutory remittance documents | Finance |
| 5 | Compliance or legal team checks the licence and core activity risk, where needed | HR/Legal |
| 6 | Exception report is prepared | HR/Payroll |
| 7 | Invoice is approved, partly held or fully held | Finance |
| 8 | Monthly records are archived | Admin/HR |
The flow should be part of the procurement-to-payment process, with the contractor’s wage timeline built into the monthly bill cycle. The contractor must fix wage periods of not more than one month, and under the Central OSHWC Rules wages of contract labour must be paid before the expiry of the seventh day after the last day of the wage period (para 18.16). Contractor bills should not be approved merely because attendance has been certified.
For Central sphere establishments, Rule 11 of the Wages (Central) Rules, 2026 requires the proprietor of the establishment to pay the contractor the amount payable in respect of wages of employees employed through the contractor. The book reads this as a need for timely funding: the principal employer should not delay payment to the contractor where the delay affects wage payment to contract labour, and should release wage-related amounts sufficiently in advance, subject to contract terms and compliance verification (para 8.19).
6. What should a contractor submit every month?
A fixed set of documents, collected before invoice approval and uploaded month-wise and contractor-wise. The book’s contractor compliance checklist sets it out (para 32.9):
| Document | Collect before invoice approval | Verified by |
|---|---|---|
| Contractor invoice | Yes | Finance |
| Work order copy | Yes | Admin |
| Labour licence copy | If applicable | HR/Compliance |
The first three of nineteen documents are shown here. The full checklist is in para 32.9 of the book.
Each contractor should also submit a monthly wage compliance certificate before invoice release. The book’s sample in Annexure 8 has a worker deployment summary, worker-wise annexures and thirteen declarations, the last an undertaking to indemnify the principal employer against liability arising from non-payment, short payment, delayed payment, unauthorised deduction or non-remittance of statutory dues. The certificate should support worker-wise verification, not replace it (para 32.21).
7. How should contractor wages be verified worker-wise?
Worker by worker, against the worker list, site attendance, the applicable minimum wage and the bank proof. The book calls its worker-wise monthly verification format the most important table in contractor compliance (para 32.10). Its seven verification points:
| Item | Verification point |
|---|---|
| Worker name | Should match the worker list |
| Attendance | Should match the site record |
| Skill category | Should match the actual work |
| Gross wage | Should meet the applicable minimum wage |
| Overtime | Should be paid where applicable |
| Net payment | Should match the bank proof |
| PF and ESI records | Should match worker-wise wages where applicable |
Minimum wages. Section 5 of the Code on Wages prohibits payment below the minimum rate notified by the appropriate Government, and this applies equally to contract labour. The check should be worker-wise and category-wise, by location, skill category and current notification, not only on the total invoice value. The action rule (para 32.11):
| Situation | Action |
|---|---|
| No shortfall | Proceed to the next check |
| Shortfall identified | Hold the invoice or hold an equivalent amount |
| Contractor accepts the shortfall | Require arrear payment proof |
| Contractor disputes the classification | Escalate to HR and legal |
| Repeated shortfall | Consider termination or blacklisting |
Payment proof. Bank proof should show worker-wise payment or be supported by a reliable worker-wise statement, not only a lump-sum debit from the contractor’s bank account, and cash payments should be justified and documented. Headcounts should broadly reconcile: if the wage register shows 100 workers but PF records show 70, the difference should be explained (para 18.21).
Overtime. Section 14 of the Code on Wages requires overtime payment where an employee whose minimum rate of wages has been fixed works beyond the normal working day, and the Additional FAQ dated 16 March 2026 clarifies that such an employee includes a worker. Overtime records should be reconciled with gate, biometric or site attendance records, and contractor overtime should not be ignored merely because the workers are not on the principal employer’s payroll.
Deductions. Deductions must be authorised under the Code on Wages, and contractors should not deduct arbitrary amounts for uniforms, ID cards, transport, canteen, accommodation, training or placement charges unless legally and contractually permitted. If deductions are not explainable, the invoice should be held until corrected records are submitted. The book’s red flags for deductions (para 32.14):
| Red flag | Why it is risky |
|---|---|
| Uniform deduction without policy | May be unauthorised |
| Canteen deduction without worker acceptance | May be disputed |
| Excessive accommodation deduction | May reduce net wages unfairly |
| Tool or PPE recovery | High risk |
| Damage recovery without show cause | Procedural violation |
| Unexplained “other deduction” | Not defensible |
| Advance recovery without schedule | Cap and consent issue |
| Net wages very low due to recoveries | Wage claim risk |
PF and ESI. Where PF and ESI apply, the worker list should reconcile with the PF ECR and the ESI contribution sheet, UAN and ESIC IP numbers should not be missing for covered workers, and new workers should be enrolled promptly.
8. What should be checked before releasing a contractor invoice?
Whether every compliance document has been submitted and verified. The book’s invoice release control sets out what happens when documents are missing or a default is found (para 32.20):
| Condition | Invoice treatment |
|---|---|
| All documents submitted and verified | Release |
| Wage proof missing | Hold |
| Minimum wage shortfall | Hold the equivalent amount or the full invoice |
| PF or ESI proof missing | Hold until proof is submitted |
| Licence expired | Hold and escalate |
| Worker count exceeds the licence | Hold and escalate |
| Core activity issue unresolved | Hold and legal review |
| Overtime unpaid | Hold the overtime amount or the invoice |
| Illegal deductions found | Hold and require correction |
| Repeated non-compliance | Consider termination |
Finance should not override a compliance hold without management approval. In the book’s worked example, a housekeeping vendor with 60 workers raises a monthly invoice of Rs. 9,00,000, with a minimum wage shortfall of Rs. 45,000, the PF challan missing and bank wage proof submitted for only 40 workers (para 32.28):
| Step | Action on the housekeeping vendor’s invoice |
|---|---|
| 1 | Do not release the full invoice |
| 2 | Hold at least the wage shortfall and the statutory risk amount |
| 3 | Require the contractor to pay the wage arrears |
| 4 | Obtain bank proof for all 60 workers |
| 5 | Obtain the PF challan and the worker-wise ECR |
| 6 | Release the invoice only after compliance clearance |
| 7 | Record the exception in the monthly contractor dashboard |
The hold should have a contractual base: an invoice hold condition in the contractor agreement and the purchase order, allowing payment to be withheld where compliance documents are not submitted or wage defaults are identified (para 18.25). It should not be used arbitrarily, but tied to documented compliance gaps and communicated to the contractor. Where the contractor fails to pay wages or makes short payment, the principal employer should consider direct payment and recovery from the contractor as permitted under the legal framework. If the hold rule has to be written into an SOP and set up in the ERP, Taxmann Advisory offers implementation support for compliance SOPs and ERP automation for compliances.
9. What are the red flags, and how does the contractor scorecard work?
Red flags call for immediate escalation, while the scorecard rates each contractor over time. The book’s red flag checklist, to be reviewed by HR, finance and management (para 32.24):
| No. | Red flag requiring immediate escalation |
|---|---|
| 1 | Contractor does not submit a worker list |
| 2 | Worker count exceeds the licence limit |
| 3 | Licence is expired |
Three of the fifteen red flags are shown here. The full checklist is in para 32.24 of the book.
The book’s contractor scorecard gives each contractor a score out of 100, with a suggested rating (para 32.25):
| Parameter | Weight |
|---|---|
| Timely wage payment | 20 |
| Minimum wage compliance | 20 |
| PF and ESI compliance | 15 |
Three of the eight parameters are shown here. The full scorecard, which totals 100, is in para 32.25 of the book.
| Contractor score | Rating | Action |
|---|---|---|
| 85 and above | Low risk | Continue |
| 70 to 84 | Moderate risk | Monitor |
| 50 to 69 | High risk | Corrective plan |
| Below 50 | Critical risk | Stop or replace the contractor |
The scorecard should be reviewed quarterly, and repeated exceptions in the monthly exception report should affect the contractor’s rating. The main risk, the book says, “is that the principal employer has people working in its establishment without a reliable record of wage payment and statutory compliance” (para 18.38).
10. Which records and contract clauses protect the principal employer?
A contractor master, a monthly compliance file and an agreement that lets the principal employer see records and hold payment. A contractor master may include, among other fields, licence validity, the core or non-core classification with reasoning, maximum workers permitted, actual workers deployed and invoice status. For the monthly file, the book suggests a seventeen-folder structure, maintained digitally where possible (para 32.26):
| Folder | Contents |
|---|---|
| 01 Contractor invoice | Invoice and supporting commercial documents |
| 02 Work order and licence | Agreement, work order and licence |
| 03 Worker list | Worker-wise deployment list |
Three of the seventeen folders are shown here. The full structure is in para 32.26 of the book.
Where contractor wage slips, attendance and bank proof are not available at inspection, the answer that the contractor is responsible may not satisfy compliance expectations (para 12.32).
The agreement should not merely say that the contractor will comply with all laws; it should provide evidence submission and invoice hold rights, and require monthly worker-wise records, without which the principal employer may have difficulty insisting on documents at invoice approval (paras 18.33 and 32.31). Section 61 gives the Code on Wages overriding effect over an inconsistent agreement, and the book warns that a contractor agreement saying “principal employer has no responsibility whatsoever” may not be enough if contractor wage compliance fails (para 12.28). The book’s model direct payment and recovery clause reads (para 18.37):
“If the Contractor fails to pay wages or makes short payment to any contract labour, the Company shall be entitled, without prejudice to other remedies, to pay the wages or unpaid balance directly to the concerned contract labour or as required by authority and recover such amount from amounts payable to the Contractor, security deposit or as a debt due from the Contractor.”
The process ends only after final worker settlement and record preservation. Before the final contractor payment or release of the security deposit, the principal employer should obtain final wage payment proof, PF and ESI proof for the last wage period, worker-wise settlement confirmation and a no-dues declaration, among other documents (para 18.32). Worker-wise exit settlement proof should also be required whenever contractor workers are removed from deployment, and State sphere establishments should check the State OSHWC Rules as well (para 17.21).
11. Quick answers
Is a principal employer liable for unpaid contractor wages?
Yes, where the contractor defaults. Under section 55 of the Occupational Safety, Health and Working Conditions Code, 2020, the contractor is responsible for paying wages to contract labour, but if the contractor fails to pay within the prescribed period or makes short payment, the principal employer is liable to pay the wages in full or the unpaid balance and recover the amount from the contractor.
What should be checked before releasing a contractor invoice?
The work order, licence and worker count, the core or non-core classification, attendance against site records, the worker-wise wage register, minimum wages by category and location, overtime, deductions, bank or electronic payment proof, PF and ESI proof where applicable, worker complaints and the contractor’s monthly declaration. If wage proof is missing, the invoice should be held, and a minimum wage shortfall calls for holding the equivalent amount or the full invoice.
What should a contractor submit every month?
At a minimum the invoice, the worker list, attendance, the wage register and worker-wise bank payment proof, with the labour licence copy, PF and ESI records and other statutory proof where they apply. The monthly contractor compliance checklist in Taxmann’s HR Guide to Code on Wages runs to nineteen documents, all to be collected before invoice approval and filed month-wise and contractor-wise.
What is a core activity?
Under the Occupational Safety, Health and Working Conditions Code, 2020, a core activity of an establishment is any activity for which the establishment is set up, including any activity essential or necessary to that activity. Contract labour is generally prohibited in core activities, subject to limited exceptions, and the same activity may be core in one industry and support in another.
What are the red flags in contractor wage compliance?
The red flag checklist in Taxmann’s HR Guide to Code on Wages calls for immediate escalation where, among other things, the contractor does not submit a worker list, wages are paid below minimum wage, wage payment proof is not available, PF or ESI proof is missing, or overtime is worked but not paid. It runs to fifteen red flags, to be reviewed by HR, finance and management.
How does the contractor scorecard work?
The contractor scorecard in Taxmann’s HR Guide to Code on Wages scores each contractor out of 100 across eight parameters, with the most weight on timely wage payment and minimum wage compliance. Its suggested rating treats 85 and above as low risk, 70 to 84 as moderate, 50 to 69 as high risk needing a corrective plan, and below 50 as critical, calling for the contractor to be stopped or replaced. The scorecard should be reviewed quarterly.
Can a contractor’s compliance certificate replace the principal employer’s own checks?
No. The monthly contractor wage compliance certificate should support worker-wise verification, not replace it. The principal employer should still verify the worker-wise wage register, attendance, bank proof, PF, ESI and minimum wage compliance before releasing the invoice.
This article draws mainly on Chapters 18 and 32 and Annexure 8 of Taxmann’s HR Guide to Code on Wages by CA Venugopal Gella (2026 Edition), which set out contractor and outsourced labour compliance with model agreement clauses, a monthly contractor compliance checklist with worker-wise verification formats, invoice release control, a red flag checklist and a contractor scorecard, and a sample contractor wage compliance certificate with a principal employer verification and an invoice release note. Law stated as updated till August 2026. The wider position across all four labour codes is covered in Taxmann’s Employer-Employee’s Guide to New Labour Laws.
Labour law Acts and Rules, case laws, circulars and notifications are available on Taxmann.com | Research under Labour Laws.
Related reading: the complete guide to the OSHWC Code, 2020 · the complete guide to the Code on Wages, 2019.
More in this series: full and final settlement under the Code on Wages · wage slip format under the Code on Wages · statutory bonus calculation · new labour code salary structure · deductions from wages and the 50% limit · payment of wages: wage period and time limits · overtime rules under the Code on Wages · minimum wages as per the new labour code · 34 common payroll mistakes · monthly payroll compliance · labour code implementation roadmap · appointment letter format.
Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.
The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:
- The statutory material is obtained only from the authorized and reliable sources
- All the latest developments in the judicial and legislative fields are covered
- Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
- Every content published by Taxmann is complete, accurate and lucid
- All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
- The golden rules of grammar, style and consistency are thoroughly followed
- Font and size that’s easy to read and remain consistent across all imprint and digital publications are applied


CA | CS | CMA