Changing a contract labour vendor looks like a procurement decision and behaves like a compliance one. The workers on your floor mostly stay. Their service history, their statutory records and any unpaid dues stay too, and if the outgoing contractor left gaps in any of that, those gaps are now sitting inside your establishment rather than inside a contract you have ended.
Why the exposure does not leave with the contractor
Under the Contract Labour (Regulation and Abolition) Act, 1970, the principal employer carries residual liability where a contractor fails to pay wages or to maintain the records the Act requires. That liability attaches to the work done at your premises. Ending your relationship with the contractor who failed does not detach it.
In practice this means an inspection or a claim arriving after a handover will be answered out of records you now have to produce, covering a period you did not administer. The question that decides how painful that is has nothing to do with your new vendor. It is whether anybody audited the old records before the handover happened.
What actually transfers
- The people. Most of the deployed workforce usually stays, because they live near the site and know the work. What changes is who employs them on paper.
- Their service history. Date of joining, continuity of service and accrued entitlements do not reset because an invoice now comes from a different company.
- Their statutory identities. A worker's universal account number for provident fund and their ESIC insurance number belong to the individual, not to the contractor. They carry across.
- The record period. Registers, wage records and filings for the outgoing contractor's period remain producible at your site.
- Anything unpaid. Wages, statutory contributions and settlements that the outgoing contractor did not clear do not disappear when the contract ends.
Before the final invoice is settled is the one point at which the outgoing contractor still has a reason to produce records and close dues. After that you are asking a company with no commercial relationship to you for paperwork it has no incentive to find. Audit first, settle second.
The audit to run before you sign anything
Licensing and registration
- The outgoing contractor's licence for your site, and whether it covered the headcount actually deployed rather than the headcount originally contracted.
- Your own principal employer registration, and whether it needs amending to name the incoming contractor.
- Whether the incoming contractor's licence application is in motion for your site, because deployment cannot wait on it afterwards.
The people records
- A reconciled headcount: who is actually on site today, against who is on the outgoing contractor's rolls. These lists differ more often than anyone expects.
- Date of joining per worker, which is what every continuity question later depends on.
- Statutory registers in the prescribed formats for the full period.
- Verification and onboarding files, so the incoming contractor is not re-verifying people who have worked at your site for years.
Money
- Provident fund and ESIC contributions filed and reconciled to the wage register, month by month.
- Full and final settlements for anyone who exited during the outgoing contractor's term.
- Any wage revision that was notified during the term and whether it was actually applied.
- Bonus and leave encashment positions, stated per worker.
What to ask for, and what an answer looks like
| Ask for | A good answer | A warning sign |
|---|---|---|
| Reconciled headcount against the wage register | The two lists match, and any difference is explained per person | A single total, or a list that has to be prepared for you |
| Registers for the full contract period | Produced from the site, in the prescribed formats, written as events occurred | Reconstructed recently, or held only at a head office elsewhere |
| Contribution filings reconciled monthly | Challans matched to the wage register month by month | Annual totals, or filings that do not reconcile to wages paid |
| Settlements for leavers | Closed and acknowledged, with dates | Open items, or no list of leavers at all |
Running the cutover
A transition done well is boring for the people on the floor. Their shift does not change, their supervisor does not change on the first day, and their pay arrives on the usual date. Everything that does change happens in the paperwork behind them.
- Agree a cutover date that is not a payroll boundary. Splitting a wage period across two contractors creates a reconciliation problem in month one and an audit question later.
- Complete the incoming contractor's onboarding before the date. Registration, documentation and appointment paperwork should be finished while the old contract is still running.
- Keep the outgoing period's records at the site. They will be asked for at your gate, not at a vendor's office.
- Hold a retention against the final invoice until the record handover is complete and reconciled.
- Run the first month in parallel review. Attendance, wage register and payroll output should be checked against each other before the first invoice is approved.
The workers do not change. The employer of record changes, and every obligation attached to their history comes with them.
What to expect afterwards
A properly run handover does not make the previous period disappear. It makes it documented, reconciled and defensible, which is a different thing and the only one available. If the audit turns up gaps, you want to know that while the outgoing contractor is still commercially engaged and while you can decide deliberately how to close them.
A vendor who treats the transition as an administrative formality is telling you how they will treat the records they are about to start keeping for you. The audit is not an obstacle to the handover. It is the first piece of work the new engagement does.
