Statutory Calendar for Multi-Location Businesses

Jun 23
4 min read

How to manage compliance deadlines across multiple establishments and state jurisdictions — without a single missed filing bringing the whole system down.

Vatsal Mashar

Advocate & Labour Laws Consultant, Mashar Associates

A compliance calendar that works flawlessly for a single office tends to fall apart the moment a business opens its second one in another state. The reason is simple: a large part of Indian labour compliance is not national but state-specific, and the obligations that vary — professional tax, labour welfare fund, shops-and-establishment returns, the very forms and frequencies themselves — do not announce that they have changed when you cross a state line. They simply apply differently, and a calendar copied from one location to the next will quietly be wrong. For multi-location businesses, the central challenge is not knowing the law. It is keeping track of how the same law behaves differently in each place you operate.

This piece sets out how to think about — and build — a compliance calendar that scales across establishments and jurisdictions. The aim is a system that is resilient by design, rather than one that depends on a single diligent person remembering everything.

01. Three layers of obligation

It helps to stop thinking of compliance as one long list of dates, and instead to separate obligations into three layers. Each behaves differently across locations, and each fails in a different way.

02. The uniform rhythm you can rely on

Start with the predictable core. A handful of obligations run on the same cadence across the country, and these should be the backbone of your calendar. Build everything else around them.

These are uniform, but uniformity is not the same as safety: the provident-fund regime in particular enforces late payment harshly, a point I return to below. Treat the monthly 7th and 15th as immovable anchors.

03. The state-variation trap

This is the layer that catches multi-location businesses, because it resists a single rule. Consider how widely the same obligation can differ:

Professional tax. Levied by states, with different slabs, different periodicities (monthly in some states, annual in others) and different due dates and return formats. Some states do not levy it at all.
Labour welfare fund. Contribution amounts and remittance cycles — monthly, half-yearly or annual — vary by state, and several states have no fund at all.
Shops & Establishment annual returns. Due dates fall anywhere between January and April depending on the state. Gujarat and Tamil Nadu, for instance, sit early in the year, while Maharashtra runs later. The form differs too.
Factory returns. Annual returns under the Factories Act follow state-specific forms and timelines.

The discipline that prevents this is to maintain the calendar by establishment and by state, mapping each location to its own set of registrations and its own due dates — and to confirm those dates against the relevant state portal each cycle rather than carrying them forward on trust.

04. The event-based obligations everyone forgets

Recurring filings get systematised because they recur. Triggered obligations do not, which is precisely why they are missed — and they often carry tight, unforgiving windows. The common ones include registering a new office under the Shops & Establishment Act within the prescribed window of opening; enrolling a new employee for provident fund and state insurance shortly after joining; and reporting a serious or fatal workplace accident within hours, not days. The practical fix is to attach a compliance checklist to the business events that trigger them — so opening a branch, onboarding an employee, or an incident on site automatically surfaces the obligation, rather than relying on someone to remember it.

05. The transition factor — and why it cuts both ways

The compliance landscape is in motion. With the four labour codes now notified, the registration-and-return regime is being consolidated — the Occupational Safety, Health and Working Conditions Code, for example, moves towards a single registration, single licence and single return in place of the old, fragmented filings. In the long run, this should simplify multi-location compliance considerably.

In the short run, however, it adds a layer of caution. Because labour is a concurrent subject, the new framework becomes fully operational in each state only as that state notifies its rules, and states are doing so at different speeds. During this transition, the prudent course is not to assume a clean national reset has already happened. Map the position state by state, watch for each state’s notifications, and confirm whether a given establishment is filing under the old regime or the new one. Getting this wrong in either direction — filing the old return when the new one applies, or vice versa — is itself a compliance failure.

06. Building a system that scales

A calendar is only as good as the governance around it. The businesses that handle multi-location compliance well tend to share a few habits:

07. Why the discipline pays for itself

The cost of a missed deadline is rarely just the filing. Late provident-fund remittance, for instance, attracts interest as well as damages that escalate sharply with the length of the delay — and the authority has real recovery powers. Across the various labour statutes, penalties can run from modest sums to several lakh rupees per violation, with repeat defaults drawing heavier consequences. Beyond the rupee figure sit the costs that do not appear on a challan: inspections, show-cause notices, audit observations, a weakened compliance record, and the management time consumed by all of it. Set against that, the effort of maintaining a disciplined, location-aware calendar is modest — and almost always cheaper than the first serious default.

A note from Vatsal Mashar

In my experience, multi-location compliance fails not because anyone was careless about the law, but because the system relied on memory and on the assumption that one state’s calendar fits the next. It rarely does. The organisations that stay clean are the ones that treat the calendar as infrastructure — owned, reviewed, location-specific, and updated the moment a new branch opens or a state changes its rules.

At Mashar Associates we help businesses build and run exactly that: establishment-wise compliance mapping across states, calendars with clear ownership and lead times, register and record maintenance, and end-to-end support on PF, ESIC, professional tax, shops-and-establishment and factory obligations — now reconciled against the transition to the labour codes. If you operate across locations and want a compliance health-check, we would be glad to assist.