One Compliance Manager, Three States: A Month in the Job

1. The Setup

This is a composite, not a client story. Meet a Compliance Manager at a mid-size business with a plant in one state, a warehouse in another and a handful of retail outlets in a third. About 600 employees, plus contract workers at the plant and the warehouse. She reports to the CFO. She is the only person who knows where everything lives.

2. Week One: The Wage Month Closes

Payroll closes. She needs headcount, wages and any arrears to feed the provident fund and ESIC files, and the numbers come from payroll in a spreadsheet that has changed format twice this year. She checks them by eye because there is nobody else to check. Registers for the plant, including the muster roll and overtime register, are updated by a supervisor who sends photos of the sheets.

3. Week Two: The 15th

The EPF ECR and the ESIC contributions are due on the 15th. She prepares both, checks them herself and files. One year it all goes smoothly. Another year the payroll lead is on leave, a challan is delayed and she finds out on the 14th. Late EPF remittance attracts interest and damages, and the details are published on EPFO's portal. It is not the amount that worries her. It is the pattern, because repeat delays are what draw attention.

4. Week Three: The Contractor Problem

A contractor at the warehouse has not sent proof of provident fund payment for two months. She emails. No reply. She calls. A promise. Under the Contract Labour (Regulation and Abolition) Act, 1970, the company as principal employer can carry liability for specified contractor failures, so this is her problem as much as the vendor's. But there is no system that flags the gap, so it only surfaces because she remembered to look.

5. Week Four: A Circular and a Renewal

A state labour department circular changes a register format. It reaches her through a forwarded email from a consultant. On the same day she realises the factory licence renews in ten weeks and the file is not started. Either could have been missed. Neither was caught by anything other than her own attention.

6. The Pattern Underneath

Nothing in this month went catastrophically wrong. That is the point. The system works because one capable person is holding it together. The risks are all single points of failure: her memory, her leave, her inbox, her spreadsheet. When she is on holiday, or leaves, or is simply overloaded, the entire arrangement is exposed.

The four Labour Codes took effect on 21 November 2025, with detailed rules still being notified. That adds a fifth task to her month: working out what has changed for her.

7. Questions Worth Asking Yourself

• If she were unavailable for three weeks, who would file the ECR?
• Who checks her work?
• How would you know a contractor had stopped paying provident fund?
• How many days' notice do you get before a licence expires?
• Where would you find last year's register from the warehouse?

If several of these have no good answer, that is the case for a system. Our guide to regulatory compliance software explains what such software does and who needs it, and a free compliance audit from Iztty can show you where your own single points of failure sit.