Companies headquartered outside Gujarat — Mumbai, Bangalore, Delhi, Chennai, Hyderabad, Pune — keep missing the same five things when they begin hiring or operating inside the state. Here are the five, in order of frequency, with how we close each one.
When a company is headquartered in another state, Gujarat compliance is rarely the central HR or finance team's daily focus. The team in Mumbai or Bangalore is fluent in its own state's rules; Gujarat sits at the edge of visibility — until a Gujarat sales engineer is hired, a Gujarat branch opens, or a Gujarat contractor is engaged.
Across the engagements we begin every year, the same five items come up repeatedly. None of them are exotic. All of them are routine, well-defined work — once someone is looking. They get missed because nobody at the centre is looking specifically at Gujarat.
This post lists the five, in the order we see them, with how we audit and close each one as part of a single Gujarat engagement.
The single most common miss across out-of-state companies.
Skipped because the office isn't "the head office".
Missed once the team crosses the applicable headcount.
Forgotten when contractors are engaged locally.
The records that should exist month after month — and often don't.
Professional Tax is a state-level obligation. The moment a company employs someone whose place of work is in Gujarat, PT compliance is triggered in Gujarat — regardless of where the company is headquartered.
That payroll is "centrally compliant" because the head office is registered for PT in its own state. Or that the Gujarat employee's tax is fully handled inside the salary stack the HQ already runs.
What's actually true: PT follows the place of work. A Gujarat-based employee triggers a Gujarat obligation, registered and filed locally — separate from the HQ state. That includes the employer-side registration and, separately, the entity-side enrolment.
We map every Gujarat employee — by district and place of work — and register the company with the relevant Gujarat authorities. From there, the monthly cycle becomes part of one engagement: calculation, challan, return, acknowledgement, archive.
Each month you send us your Gujarat headcount; we send back a single consolidated report covering every district. The HQ team sees one line in their compliance summary instead of trying to staff up for a state they don't operate from.
If you have an office, a co-working seat, a small sales hub or a service desk in Gujarat — Shop Act compliance is on the table. Whether the space is rented in your company's name, or sub-let from a partner, doesn't change the obligation: an establishment exists, and it needs to be registered.
The Gujarat office isn't perceived as "the head office", so it doesn't appear on the HQ team's establishment register. It might be small. It might be one or two people. It might be a desk inside a co-working operator. The assumption is that the operator's own registration covers the seat — which it doesn't, for the company occupying that seat.
The other variant: the office is opened, the Shop Act registration is taken once at inception, and then renewals quietly lapse because no one at HQ owns the diary.
We register the establishment under the applicable Gujarat law, prepare and put up the required displays, set up the statutory registers and own the renewal diary so the certificate doesn't lapse. If the office moves or changes address, we run the modification at the right authority.
For companies opening a second or third Gujarat location, we add each one into the same engagement — one folder, one renewal calendar, one point of contact.
The prevention of sexual harassment framework applies across the country, and obligations trigger once headcount crosses the applicable threshold. For an out-of-state company with a growing Gujarat team, this is often the third item to slip — and the one with the biggest reputational downside.
HQ has its own POSH committee, set up in the head office state. Once the Gujarat team grows past a certain headcount, the question of whether the central committee adequately covers Gujarat-based employees becomes real. Members may not be reachable; geography may make participation difficult; awareness sessions may never reach the field.
Even where a committee exists on paper, the supporting habits — policy circulation, awareness training, annual reporting — sometimes fade once the team is geographically spread.
We assess the Gujarat headcount against the applicable thresholds and advise on whether a separate internal committee is appropriate, or whether the existing committee can be extended properly. We then help constitute the committee, draft the policy in the right language, run awareness sessions on the ground, and set up the annual reporting cycle.
Done once properly, POSH stops being something the HQ team worries about every quarter.
The moment your Gujarat operation engages contractors — for housekeeping, security, warehousing, on-site staff, project labour or any service involving people physically working at your location — contract labour compliance becomes relevant.
The HQ team treats the contractor relationship as a vendor invoice. The contractor sends staff; the principal employer pays the bill; nobody asks whether the principal employer needs its own registration, whether the contractor holds a current licence, or what the wage and attendance records of contractor staff look like.
It works fine — until an inspector asks for the engagement file, or there's a workplace incident, or the contractor's licence comes under question. Then the principal employer's lack of paperwork becomes the issue.
We map the contractor engagements your Gujarat operations rely on, confirm what each side needs in place, and put the registrations or licences through with the relevant authorities. We also set up the wage, attendance and remittance records of contractor staff in a format that holds up if anyone walks in to verify.
From there, the same monthly engagement keeps everything current — including the day a contractor demobilises or a new one is brought in.
Behind every registration and certificate sits a quiet stack of working records — attendance, wages, leave, overtime, deductions, returns lodged, acknowledgements received. For Gujarat establishments of out-of-state companies, this is the most commonly thin file.
Central HRIS systems generate payroll data, but the statutory register formats are local. A central system may produce attendance reports — but not in the format the inspector expects to flip through on the desk. Returns may have been filed centrally — but acknowledgements weren't archived in a way anyone can produce a year later.
The gap isn't always between "compliant" and "non-compliant". Often it's between "the work was done" and "we can prove it was done, today, on demand".
We set up the registers in the right format — paper or digital, depending on what works for your team — and we maintain them as part of the monthly cycle. Returns are lodged, acknowledgements are filed, headcount changes are reflected, and the file reads cleanly from cover to cover.
For older periods that came to us in poor shape, we reconstruct what can be reconstructed, document what can't, and reset the file forward so the next twelve months are clean.
Individually, each gap is fixable. Collectively, they're what create the gap between "we're a national company with a Gujarat team" and "we're confidently compliant in Gujarat".
Each of the five is local in some way — local registration, local committee, local contractor, local register, local authority. Central teams optimised for one state can't extend that optimisation outward without on-the-ground support. Hence the same five gaps, in the same order, across very different companies.
Treating each gap as a separate vendor leads to a different headache: too many points of contact, mismatched timelines and no single source of truth. The companies that close all five cleanly tend to engage one Gujarat-specialist team to run them together.
Most of our out-of-state engagements start the same way — a one-time Gujarat compliance audit, followed by a single ongoing monthly cycle that keeps every item current.
We walk through every Gujarat employee, office, contractor and committee — and produce a clean readout: what's in place, what isn't, and which of the five gaps applies to you.
We file the registrations that should already exist — PT, Shop Act, CLRA where applicable — and obtain the certificates. Renewals come into our calendar from day one.
We help constitute the right committee for your Gujarat footprint, circulate the policy, run on-the-ground awareness sessions and own the annual reporting cycle.
We document each contractor engagement — registrations or licences in force, wage and attendance records, payment proofs — so the principal employer's file is ready for any review.
We rebuild the statutory registers in the right format, archive returns and acknowledgements, and reset the file forward so the next year is clean from day one.
From audit to ongoing — one engagement covering every Gujarat compliance item, one consolidated monthly report, one point of contact for your HR and finance teams.
If any of the five gaps sounded familiar, a one-time audit is the fastest way to know exactly where you stand — and what it takes to close every item under one engagement.
Get in TouchOther posts and guides on Gujarat labour compliance, written from the work we do every month.
What inspectors check in practice and the monthly habits that keep companies calm when a visit happens.
Why a single engagement across services beats juggling separate vendors — for time, cost and consistency.
The pillar overview — PT, PF/ESI, LWF and returns support for Gujarat payroll, in one place.
