One company, several compliance positions

Multi-state payroll fails when a single organisational dimension is asked to carry three different kinds of rule. Separating them is the whole of the solution, and most of the difficulty is in deciding which axis a given rule belongs to.

An employee sits at the intersection of all three, and each of their statutory and policy positions derives from the relevant axis rather than from a company-wide default.

Professional Tax is levied by states. Each sets its own wage bands, its own amounts, its own exemptions and its own remittance calendar. There is no national schedule, and registration is per location rather than per company.

• Slabs differ, so the same salary produces a different deduction in two offices of one company.
• Periodicity differs, and due dates follow the state rather than your payroll calendar.
• Several states provide specific exemptions, including gender-based ones, which a single national rule set cannot express.
• Maharashtra deducts a different amount in one month of the year, which a flat monthly configuration will miss every year.

HRMagix carries state-specific rule sets configured for Maharashtra, Karnataka, Telangana, Tamil Nadu, Andhra Pradesh, Gujarat and West Bengal. Applicability follows the employee's work location on the record, which means a mid-year transfer changes the position from the transfer date without rewriting earlier months.

Minimum leave entitlements are set by the applicable state Shops and Establishments Act, and by the Factories Act for covered establishments. A company operating in three states may therefore face three statutory floors.

An employer's policy may be more generous than the floor but not less. The common failure is to adopt one national scheme set at the level of the least generous state, which is compliant nowhere except there. The alternative failure, setting it at the most generous, is compliant everywhere and expensive.

The workable arrangement is a single policy with per-location quotas and per-location holiday calendars, so that the team calendar an employee sees combines their own location's holidays with their team's approved leave rather than showing another state's public holidays.

Leadership asks for one number. Finance needs several. Both requirements are legitimate and they are usually treated as a trade-off, which is why companies end up running separate instances per state and losing the consolidated view.

The resolution is to keep runs distinct at the entity level, because filing is per entity, while allowing reporting to combine them. Multi-entity structures sit under a single login, with role-based permissions determining who can see which entity.

• Consolidated headcount, department distribution and payroll cost across all entities, for the board.
• Entity-level statutory totals that reconcile to what was actually filed, for finance.
• Location-level overtime and attendance, for the person running that site.

LWF is deducted half-yearly in some states and annually in others, on dates set by the state. Because the cycle does not align with the monthly payroll rhythm, it is the deduction most often remembered rather than configured, and therefore the one most often missed.

The only durable approach is to apply it inside the payroll run against the employee's work location, so that the correct months carry the deduction automatically and no one has to hold a calendar in their head.