Payroll & statutory
One company, several compliance positions: Professional Tax across states
A business with offices in three states experiences itself as one organisation. Professional Tax does not. This is where multi-state payroll goes wrong.
- Written for
- HR and finance leads in multi-branch, multi-state businesses
- Companies on HRMagix
- 120+
- Employees managed
- 9,000+
- Integrated modules
- 12
- Free trial, no card
- 14-day
Head office in Pune, a branch in Bengaluru, a unit in Hyderabad. To leadership this is one company: one set of numbers, one culture, people who move between locations. Statutorily it is nothing of the sort.
Professional Tax is levied by states, not by the Union. Each state sets its own slabs, its own exemptions and its own filing calendar. Registration is per location. There is no national schedule to configure once and forget.
The three things that differ, and the order they bite in
- Slabs, the wage bands and the amount deducted in each are set per state, so the same salary produces a different deduction in two offices of the same company.
- Periodicity, some states deduct monthly, others on a different cycle, and the due dates for remittance follow the state rather than your payroll calendar.
- Exemptions, several states provide specific exemptions, including gender-based ones, which a single national rule set cannot express.
There is also a timing quirk that catches out companies operating in Maharashtra: the amount deducted in one month of the year differs from the other eleven. A payroll configured with a flat monthly figure will be short by the difference, once a year, without anyone noticing.
Why software usually forces a bad choice here
Systems that cannot express per-location rules push companies into one of two workarounds, and both are common enough to be worth naming.
| Workaround | What it gives you | What it costs |
|---|---|---|
| WorkaroundRun a separate instance per state | What it gives youCorrect state-level deduction and filing | What it costsNo consolidated headcount or payroll cost view; employee transfers become re-onboarding |
| WorkaroundRun one instance and adjust by hand | What it gives youA single consolidated view | What it costsA manual adjustment every month, by one person, that nobody else can verify |
The configuration that avoids the choice
The resolution is to hold the rules against three axes rather than one, entity, location and grade, and to derive an employee's Professional Tax position from their work location on the record rather than from a company-wide default.
HRMagix carries state-specific rule sets configured for Maharashtra, Karnataka, Telangana, Tamil Nadu, Andhra Pradesh, Gujarat and West Bengal, including the February treatment and gender-specific exemptions where a state provides them. Payroll runs remain distinct per entity, as they must be, because filing is per entity, while reporting consolidates across them.
A transfer between states then behaves correctly on its own. Because the work location is an effective-dated field on the employee record, moving someone from Pune to Bengaluru in August changes their Professional Tax position from August, and leaves the months before it untouched.
The same logic applies to Labour Welfare Fund
LWF is the other state-level deduction that runs on its own calendar, half-yearly in some states, annual in others, on dates that have nothing to do with your payroll cycle. It is missed for exactly the same reason Professional Tax is: it is remembered rather than configured. Applying it inside the run is the only approach that survives a busy month.