Your housekeeping contractor sends a PF challan every month. Someone in accounts files it and releases the invoice. Nobody checks whether the challan covers the fourteen people actually working at your site, or whether it’s the same challan they sent in March with a new date on it.
Two years later the EPFO comes to you, not to them.
Transparian runs vendor compliance management for principal employers across India, one contractor or a full panel of third party vendor compliance relationships across every site. We verify what your contractors file rather than collecting what they send, track licences and registrations across every site, and give you a monthly position you can actually defend.
Most companies know the phrase. Fewer have looked at how far it reaches.
If your contractor doesn’t pay wages to the workers deployed at your premises, you’re liable for them. If they don’t remit PF or ESI for those workers, the authorities can recover it from you, and in practice they often prefer to, because you’re the solvent party with a registration and an address. Welfare facilities at the site are your responsibility too, not the contractor’s. This is what principal employer liability contract labour law creates not a technicality, but the core exposure of running any vendor relationship.
Your contractor's CLRA licence exists because you issued them a Form V certificate saying you've engaged them. Their authority to supply labour at your site traces directly back to a document with your signature on it — the core of your principal employer compliance responsibilities.
A recovery notice can arrive well after a contractor has gone, and by then nobody at their end has any reason to help you reconstruct anything. Long-deployed workers on core activity can also raise claims about the nature of their employment.
The OSH Code brings contract labour obligations under a new framework as states notify their rules, and ESIC has been paying closer attention to whether contract workers are actually enrolled. Both point at principal employers rather than contractors.
Most vendor compliance programmes collect documents. Collection proves a document exists. It doesn’t prove the contribution reached your workers, which is the only thing that helps you in an inquiry.
| Document | What it's supposed to prove | How we verify it |
|---|---|---|
| CLRA licence | Contractor is licensed to supply labour at your site | Validity dates, worker strength permitted against actual deployment, and that the licence names your establishment |
| PF ECR and challan | Contributions filed and paid for deployed workers | TRRN checked on the EPFO portal, and the ECR member list matched against your site attendance |
| ESIC challan and return | ESI contributions paid for the same workers | Challan verified on the ESIC portal, IP numbers matched to deployed workers |
| Wage register | Workers actually paid what was declared | Rates checked against the current state minimum wage schedule for the correct category and zone |
The gap that matters is between the second and third columns. A contractor with fourteen workers at your site can file a challan for six and still hand you a valid-looking document every month. It only shows up when someone matches the member list against attendance — the check almost nobody runs.
Whether you call it contractor compliance management services or vendor compliance management, it comes down to six pieces of work — covering manpower vendor compliance across every site you run.
Before a vendor starts, we verify registration, licence capacity, PF and ESI codes and past compliance history, and tell you what to fix in the contract while you still have leverage.
Documents collected, checked against the site's actual deployment, and reported with exceptions flagged. This is contractor compliance verification in practice, you get a position each month, not a folder.
Your own registration kept current as contractor numbers change, Form V certificates issued correctly, Form XII maintained, half-yearly and annual returns filed on time.
A full audit of one vendor or your whole panel, covering wages, PF, ESI, bonus, gratuity, licences and records for whatever period you want examined. Useful before a customer audit and essential after an inspection notice.
One view across every location, every vendor and every licence renewal date, the thing that falls apart fastest when a company runs contractors at more than two or three sites.
When state minimum wages are revised, contractor billing has to move with them. We flag revisions as they're notified so procurement isn't renegotiating three months late with arrears already accrued.
Where the same contractors also work inside your plant, this runs alongside factory compliance services, and the PF and ESI checks connect to our PF & ESIC consultant work.
Companies try three things. They write compliance clauses into the contract, which helps only when someone reads them later. They ask for documents monthly, which produces a folder nobody opens. Or they link the two: no verified compliance documents for the month, no invoice release.
The third one works because it’s the only one with money behind it. It also changes contractor behaviour within about two cycles, which no amount of correspondence does.
It needs three things in place:
01
A contract that gives you the right to audit and to withhold payment.
02
A verification step that happens before the invoice reaches accounts.
03
Someone who will actually hold the line in month one, when the contractor calls your plant head to complain.
We run the verification and hand you a clean release-or-hold position each month, so the decision is yours and the argument isn’t.
Vendor compliance software gives you a document repository, renewal alerts and a dashboard. That’s genuinely useful once you’re past ten or fifteen vendors, and if you already have a platform we’ll work inside it.
Store documents, send renewal alerts, and show you a dashboard. It can tell you a PF challan was uploaded.
Judgement. It can't tell you the challan covers six workers when nineteen are on site, that the wage rate is right for the trade but wrong for the zone, or that a licence covers a different address. Those are the findings that matter in an inquiry, and each one needs a person who knows what they're looking at.
Day 1
Map your vendors — who, where, under what scope and licence
Day 2
Baseline audit, returned as a gap register
Day 3
Monthly verification, exceptions flagged
Day 4
Release-or-hold position before invoices process
Day 5
Clean file close-out when a vendor exits
