Multi-State Payroll Compliance in India (2026)

Multi-State Payroll Compliance in India (2026)

Running payroll for a team in a single city is hard enough. Running it for employees spread across Maharashtra, Karnataka, Tamil Nadu, Telangana, and West Bengal—each with its own registrations, rates, return formats, and deadlines—is a different discipline altogether. Multi-state payroll compliance in India is where many fast-growing companies quietly accumulate risk: a missed professional tax slab here, an unregistered branch there, a labour welfare fund deduction skipped because nobody knew the state mandated it.

This guide is a practical, ground-level walkthrough of how to keep payroll compliant when your workforce lives and works across multiple Indian states. It is written for HR managers, payroll teams, finance leaders, and founders who have crossed (or are about to cross) state borders with their hiring. We will cover what actually changes when you employ people in more than one state, the registrations and deductions that are state-specific, how the new labour codes affect the picture, a month-by-month compliance rhythm, and the most common mistakes that lead to notices and penalties.

A quick note before we start: statutory rates, slabs, and thresholds change, and they differ by state and sometimes by local body. Treat the numbers and rules described here as the structure to understand, then verify the current figures against the relevant state government notification or your professional advisor before you process a payroll run.

Why multi-state payroll is fundamentally different

When all your employees sit in one state, payroll compliance has a comforting sameness to it. There is one professional tax regime to learn, one set of Shops and Establishments rules, one labour welfare fund cycle (if applicable), one inspectorate to deal with. The moment you employ someone in a second state, that uniformity disappears.

Several things are genuinely national and travel with the employee regardless of location. The Employees' Provident Fund (EPF) is administered centrally by the EPFO, so the contribution structure does not change from state to state. The Employees' State Insurance (ESI) scheme is also national in its rules, though whether an area is "covered" or "non-implemented" can vary, which matters for eligibility. Tax Deducted at Source (TDS) on salary is governed by central income tax law and does not change by state. These are your constants.

What changes—and what trips companies up—are the state-administered levies and registrations. Professional tax is levied by individual states (and some states do not levy it at all). The Shops and Establishments Act is a state law, so every state and sometimes every municipal jurisdiction has its own registration, renewal, and record-keeping requirements. Labour Welfare Fund contributions exist only in certain states and follow different amounts and cycles. Minimum wages are notified state by state and by scheduled employment and skill category. Even the practical mechanics—where you register, which portal you file on, which deadline applies—fragment across jurisdictions.

The result is that a company with employees in five states is not running one payroll with five addresses. It is running what amounts to five overlapping compliance regimes stitched onto a single salary calculation. Understanding that mental model is the first step to getting it right.

The state-specific building blocks

Professional tax: the most common multi-state headache

Professional tax (PT) is a tax on income from employment, profession, or trade, levied by state governments and, in some cases, collected through local bodies. It is capped at a modest annual maximum per person under the Constitution, so the absolute rupee amounts are never large—but the administrative burden of getting it right across states is significant.

Several points make PT the classic multi-state pain point. First, not every state levies it. States such as Maharashtra, Karnataka, West Bengal, Tamil Nadu, Telangana, Andhra Pradesh, Gujarat, Madhya Pradesh, and several others do; many northern states do not. So an employee in one state has PT deducted and an identically paid employee in another does not. Second, the slabs differ. Each levying state publishes its own salary slabs and monthly deduction amounts, and these are revised from time to time. Third, the deduction frequency and a few quirks vary—some states have a special higher deduction in a particular month of the year, and the return filing frequency (monthly, quarterly, or annual) depends on the state and sometimes on your deduction volume.

To handle PT across states correctly you need two kinds of registration in each levying state where you have employees: a registration certificate (which authorises you, the employer, to deduct and remit PT for employees) and an enrolment certificate (which covers the entity's own PT liability where applicable). You then deduct PT from each employee based on the slab of the state in which they are employed, remit it to that state, and file that state's returns on that state's schedule.

The single most important principle: PT follows the state where the employee works, not where your head office is. A company headquartered in Bengaluru with a sales team operating out of Pune deducts Maharashtra PT for the Pune employees and remits it to Maharashtra. Getting this wrong—applying head-office-state rules to everyone—is one of the most common and most easily detected errors.

Shops and Establishments registration in every state

The Shops and Establishments Act is state legislation that governs working conditions: hours of work, weekly offs, leave, overtime, opening and closing hours, employment of women and young persons, and record-keeping. Because it is a state law, you generally need a separate registration for each establishment you operate in each state, and sometimes for each municipal area.

For a multi-state employer this means that when you open an office, a warehouse, a retail outlet, or in many interpretations even a co-working desk or a registered place of business in a new state, you should examine whether a fresh Shops and Establishments registration is required there. Registrations carry renewal obligations in many states, display requirements (you may need to display the registration certificate at the premises), and ongoing record-keeping for attendance, wages, and leave in the prescribed state format.

The rise of remote and hybrid work has muddied this further. If you have a single employee working from home in a state where you otherwise have no premises, whether and how you must register is a genuinely grey area that depends on state-specific rules and interpretations. The pragmatic approach is to map every state where you have a physical establishment, register those clearly, and seek specific advice for purely remote-employee states rather than assuming you are exempt.

Labour Welfare Fund: present in some states, absent in others

The Labour Welfare Fund (LWF) is a statutory contribution that funds welfare activities for workers. It exists only in certain states and union territories, and the design differs everywhere it exists. The contribution amounts (a small employee share and a usually larger employer share), the contribution frequency (monthly, half-yearly, or annual depending on the state), the eligibility (often based on designation or wage level, with managerial or supervisory staff sometimes excluded), and the due dates all vary by state.

For multi-state payroll this means you cannot apply one LWF rule everywhere. You determine, state by state, whether LWF applies, who is eligible, how much is deducted and contributed, and when it must be remitted. Because the amounts are tiny, LWF is easy to forget—and because it is easy to forget, it is a frequent finding in inspections and audits.

Minimum wages by state, employment, and skill

Minimum wages in India are notified by both central and state governments, and the operative figure for most private employers is the relevant state notification for the applicable scheduled employment and skill category (unskilled, semi-skilled, skilled, highly skilled), often with a separate dearness allowance component that is revised periodically.

The multi-state implication is direct: the same role can carry different minimum wage floors in different states. Your payroll must ensure that, for each employee, the wage structure meets or exceeds the minimum wage applicable in that employee's state and category. This is especially important for entry-level, field, warehouse, and frontline roles, and it interacts with how you structure components like basic pay and allowances. With wage definitions shifting under the new labour codes (discussed below), this is an area to watch closely.

ESI coverage and the implemented-area question

ESI rules are national, but ESI applies in notified "implemented areas." Most urban and industrial areas are implemented, but some locations are not yet covered, which can affect whether ESI applies to employees working there even if they fall under the wage threshold. For a multi-state employer with people in smaller towns or newer industrial zones, it is worth confirming the implementation status of each work location rather than assuming uniform coverage. EPF, by contrast, does not have this geographic nuance.

How the new labour codes change the multi-state picture

India has consolidated a large number of central labour laws into four labour codes covering wages, social security, industrial relations, and occupational safety and health. As these codes and their associated rules are operationalised, they reshape several things that matter for multi-state payroll.

The most consequential change for payroll is the standardised statutory definition of "wages." The codes introduce a common definition with the principle that certain excluded allowances cannot exceed a defined proportion of total remuneration—effectively requiring that the "wage" base (which drives PF, gratuity, and related calculations) be a meaningful share of total pay. For companies that historically kept basic pay low and loaded compensation into allowances, this can increase the wage base and therefore contribution and gratuity costs. Across multiple states, you want this restructuring applied consistently so that you are not compliant in one location and exposed in another.

The codes also aim to simplify registrations, returns, and record-keeping, with the intent of moving toward more consolidated, often digital, filings. The direction of travel is fewer, more unified compliances—but during the transition, employers must track both the new framework and the state-level rules that continue to apply (states issue their own rules under the codes, so state variation does not vanish). Practically, treat the labour codes as raising the importance of a clean, well-documented wage structure and a single source of truth for employee state mapping, because the cost of inconsistency rises when the wage base rises.

Because the timing and details of rule notifications can differ, confirm the current operative position for each state before assuming a particular code provision is live there.

Building a multi-state payroll process that holds up

Step 1: Map every employee to a work state

Everything downstream depends on knowing, authoritatively, which state each employee works in. Build and maintain a register that records, for every employee, their work state and work location, their home/remote location if different, and the establishment under which they are mapped. This register is the backbone of PT, LWF, minimum wage, and Shops and Establishments compliance. When an employee relocates—even from home—update it, because their PT and LWF treatment may change.

Step 2: Maintain a state compliance matrix

Create a master matrix with one row per state where you have employees and columns for each obligation: PT applicability and slabs, PT return frequency and due dates, Shops and Establishments registration status and renewal date, LWF applicability, amounts, and cycle, minimum wage notifications relevant to your roles, and the responsible filer. This matrix is the difference between proactive compliance and reactive firefighting. Review it whenever you enter a new state and on a fixed periodic cadence to catch rate revisions.

Step 3: Centralise calculation, localise rules

The most scalable model is a single payroll engine that holds state-specific rule sets. You run one consolidated payroll process, but the system applies the correct PT slab, LWF amount, and minimum wage floor based on each employee's mapped state. This avoids the error-prone approach of running separate spreadsheets per state, while still honouring local rules. A capable HRMS or payroll platform should let you configure state-wise PT slabs, LWF cycles, and wage floors and then apply them automatically per employee.

Step 4: Separate remittance and return workflows by state

Calculation can be centralised, but remittances and returns are inherently per-state. Build a workflow that, after each run, generates the state-wise liabilities, routes each payment to the correct state authority, and files each return on the correct portal by the correct deadline. Keep challans and acknowledgements organised by state and month so that any inspection or audit can be answered quickly.

Step 5: Reconcile every month

Reconciliation is where multi-state payroll either stays clean or silently drifts. Each month, reconcile total PT deducted against PT remitted per state, LWF deducted and contributed per state against the cycle, EPF and ESI contributions against the central filings, and TDS deducted against deposits. A monthly reconciliation habit catches a missed state remittance long before it becomes a penalty-bearing notice.

A month-by-month compliance rhythm

While exact dates vary by state and by levy, the shape of a compliant month looks broadly like this. Early in the month, finalise the prior month's inputs—attendance, new joiners, exits, location changes—and lock the employee-to-state mapping. Mid-month, process the run, generate state-wise statutory liabilities, and deposit central dues (EPF, ESI, TDS) and monthly PT for states on a monthly cycle by their respective deadlines. Through the month, file the state PT returns due that month, attend to any LWF remittances falling due (many states have half-yearly or annual LWF cycles, so these cluster in specific months), and renew any Shops and Establishments registrations approaching expiry. At quarter-end, handle quarterly PT returns where applicable and quarterly TDS returns. At year-end, complete annual PT returns where applicable, annual LWF in annual-cycle states, and the income tax year-end activities including issuing salary TDS certificates to employees.

The practical tool that makes this manageable is a compliance calendar built from your state matrix—one consolidated calendar that lists every state's every due date so nothing is governed by memory.

Common multi-state payroll mistakes (and how to avoid them)

Applying head-office rules to everyone. The most frequent error is deducting PT, or applying LWF and minimum wages, based on where the company is headquartered rather than where each employee works. Fix it by driving all state-specific logic off the employee work-state register, not the company address.

Forgetting to register in a new state. Teams often start hiring in a new state—particularly remote or sales hires—before sorting out PT registration, Shops and Establishments registration, or LWF enrolment there. Build a "new state checklist" that triggers automatically whenever the first employee is mapped to a state you are not yet registered in.

Missing LWF because the amounts are trivial. Because LWF deductions are small, they are easy to overlook, and the half-yearly or annual cycles make them easy to forget between runs. Put LWF due dates on the consolidated calendar with reminders, and treat them with the same seriousness as larger levies.

Stale slabs and wage floors. States revise PT slabs, minimum wages, and dearness allowance components periodically. Running last year's numbers is a quiet compliance failure. Schedule a periodic review of every state's notifications and update the system promptly when changes are notified.

Inconsistent wage structures across states. Under the new wage definition, keeping basic pay artificially low to reduce the wage base is increasingly untenable. If you restructure salaries, do it uniformly across all states so you are not compliant in some locations and exposed in others.

Poor documentation by state. When an inspector or auditor asks for proof, scrambling through mixed folders is painful and looks like non-compliance even when you have paid. Keep challans, returns, acknowledgements, and registration certificates organised by state and by month from day one.

Treating remote employees as a non-issue. A single remote employee in a new state can create PT, registration, and even Shops and Establishments questions. Don't assume "no office means no compliance." Map them, assess the state's rules, and seek advice where the position is unclear.

Technology: when to move off spreadsheets

Many companies start multi-state payroll in spreadsheets, and it works—until it doesn't. The signs that you have outgrown manual handling are familiar: you have employees in more than two or three states, you are spending the back half of every month chasing state deadlines, reconciliation regularly surfaces surprises, or a missed filing has already cost you interest or a penalty.

A modern HRMS or payroll platform earns its place by holding state-wise rule configurations (PT slabs, LWF cycles, minimum wage floors) and applying them per employee automatically, generating state-wise statutory reports and challans, maintaining a consolidated compliance calendar across all your states, and keeping audit-ready records organised by jurisdiction. The goal is not to remove human judgement—someone still owns the state matrix and verifies rate changes—but to remove the manual, error-prone arithmetic and the deadline-tracking that humans do poorly at scale.

CozyHR is built for exactly this kind of multi-state reality: configurable state-wise professional tax, labour welfare fund, and minimum wage handling, employee-to-location mapping that drives the right deductions automatically, and a unified view of what is due where and when. If your team is stretched across states, a platform that treats geography as a first-class input rather than an afterthought removes a large category of avoidable risk.

A worked example: one company, five states

To make the abstract concrete, consider a fictional company, Aarav Cloud Services, headquartered in Bengaluru. Over two years it has grown to 140 employees: 60 in Karnataka (the head office and engineering team), 30 in Maharashtra (a Pune sales and support office), 20 in Telangana (a Hyderabad delivery centre), 20 in Tamil Nadu (a Chennai office), and 10 fully remote employees scattered across states where the company has no premises, including a few in northern states.

Here is how the payroll team thinks through each levy for this footprint.

For EPF and ESI, nothing changes by state. Every eligible employee, wherever they sit, is covered under the same central rules, and the company files centrally. The only nuance is confirming that each work location for ESI-eligible employees falls within an implemented area; for the remote employees in smaller towns, the team checks coverage rather than assuming it.

For TDS, again, central rules apply uniformly. The team computes each employee's tax based on their declarations and the applicable regime, deducts monthly, deposits centrally, and files quarterly returns. State of residence does not change the salary TDS computation.

Professional tax is where the work fragments. Karnataka, Maharashtra, Telangana, and Tamil Nadu all levy PT, so the company holds PT registrations in each and deducts according to each state's slabs for the employees mapped there. The Bengaluru employees follow Karnataka slabs and remittance; the Pune employees follow Maharashtra slabs, including that state's particular pattern of deductions across the year; the Hyderabad and Chennai employees follow Telangana and Tamil Nadu respectively. For the remote employees, the team determines PT applicability based on each individual's work state—some of those northern-state employees may have no PT at all, while any remote employee located in a levying state is handled per that state. The team files each state's PT returns on that state's schedule, which means juggling monthly, quarterly, and annual cycles simultaneously.

Labour Welfare Fund is assessed state by state. Karnataka, Maharashtra, Tamil Nadu, and Telangana each have their own LWF treatment—different amounts, different eligibility, and different cycles (some half-yearly, some annual). The team maintains an LWF sub-section in its state matrix, contributes the correct amounts where eligible, and clusters the half-yearly and annual remittances on the consolidated calendar so they are not forgotten between the months they fall due.

Minimum wages are checked per state for the relevant scheduled employment and skill category, with particular attention to the support and entry-level roles where the wage floor bites. The team ensures each such employee's structure clears the floor in their own state, recognising that the Chennai floor and the Pune floor for a comparable role may differ.

Shops and Establishments registration exists for each physical office—Bengaluru, Pune, Hyderabad, Chennai—with renewals tracked. For the remote-only states, the team has taken specific advice rather than assuming either that registration is required or that it is exempt.

The lesson from Aarav Cloud Services is that the same 140-person payroll is, underneath, one uniform central layer (EPF, ESI, TDS) sitting on top of four-to-five parallel state layers (PT, LWF, minimum wages, Shops and Establishments). Once a team sees payroll this way, the process design—central calculation, localised rules, per-state remittance and reconciliation—follows naturally.

Handling transfers, deputation, and relocations

People move, and every move is a potential compliance event. When an employee transfers from a Pune office to a Bengaluru office, their professional tax treatment should switch from Maharashtra to Karnataka from the effective date, their LWF eligibility may change, and the minimum wage floor that applies to them changes. The cleanest practice is to treat the work-state field as the single trigger: update it on the effective date, and let the payroll system re-derive PT, LWF, and wage-floor logic from there.

Deputation and temporary assignments are trickier and benefit from a documented policy. If an employee is on the Karnataka payroll but spends several months on assignment in another state, you need a consistent rule for which state's PT and other levies apply during the assignment, and you should document the rationale. Because interpretations can vary, this is an area where written internal policy plus professional advice protects you—both from over-deducting (annoying employees) and under-deducting (creating liability).

Remote-work relocations deserve special attention because they are easy to miss. An employee who quietly moves from a non-levying northern state to, say, Maharashtra, and starts working from there, may now attract Maharashtra PT and raise registration questions—yet nothing about their role or office changed, so the move can slip past payroll entirely. Build a lightweight process for employees to report a change of work location, and tie it to the work-state register so the compliance consequences are picked up automatically.

Penalties, interest, and why timing matters

The individual rupee amounts in state levies are often small, but the cost of getting them wrong is not. Late deposit or non-deposit of professional tax typically attracts interest and penalties under the relevant state act, and persistent non-compliance can escalate to prosecution provisions in some states. Failure to register under the Shops and Establishments Act, or to renew on time, can attract fines and complicate other approvals. Missed Labour Welfare Fund remittances accumulate as arrears with interest in many states. On the central side, late deposit of EPF, ESI, or TDS carries its own interest and penal consequences, and late TDS deposit can even affect the deductibility of the corresponding expense.

The through-line is that timing is everything. Most of these penalties are not for paying the wrong amount—they are for paying late or not registering. That is encouraging, because timing is exactly what a consolidated compliance calendar and an automated payroll workflow are good at controlling. The companies that get penalised are rarely the ones that misunderstood a slab; they are the ones who lost track of a deadline in a state they don't think about often.

A practical implementation roadmap

If you are setting up multi-state payroll compliance from a standing start, or cleaning up an existing tangle, a staged approach works better than trying to fix everything at once.

Begin by establishing the work-state register and mapping every current employee accurately—this is the foundation everything else stands on. Next, build the state compliance matrix for every state you currently operate in, recording PT, LWF, minimum wage, and Shops and Establishments status against each. Then audit your current position state by state: are you registered everywhere you should be, are you deducting the right slabs, are there LWF cycles you have been missing, are any registrations lapsed? Treat this audit as discovery, not blame; the point is to surface gaps so you can close them.

With the picture clear, remediate registrations and any back-compliance with professional advice, then move calculation onto a single engine configured with state-wise rules so future runs are correct by construction. Finally, institutionalise the rhythm: a consolidated compliance calendar, a monthly reconciliation routine, a periodic rate-review cadence, and a new-state checklist that fires whenever you map the first employee to a new state. Done in this order, you convert a sprawling, anxiety-inducing obligation into a repeatable monthly process.

Frequently asked questions

Which payroll obligations change by state and which stay the same? EPF, ESI rules, and TDS on salary are governed centrally and do not change by state (though ESI's implemented-area status can affect coverage at a given location). Professional tax, the Shops and Establishments Act, the Labour Welfare Fund, and minimum wages are state-specific and vary in applicability, rates, formats, and deadlines.

For professional tax, do I use the employee's state or my head office state? The employee's work state. PT is deducted and remitted based on where the employee is employed, not where the company is headquartered. This requires per-state PT registration wherever you have employees in levying states.

Do I need a separate Shops and Establishments registration in every state? Generally yes for each establishment in each state, and sometimes for each municipal jurisdiction. The treatment of purely remote employees in a state where you have no premises is less settled, so confirm the specific state's position rather than assuming exemption.

Does the Labour Welfare Fund apply everywhere in India? No. LWF exists only in certain states and union territories, and where it exists the amounts, eligibility, and contribution cycles differ. You must check each state individually.

How do the new labour codes affect multi-state payroll? The most significant payroll effect is the standardised definition of wages, which can raise the wage base that drives PF and gratuity for companies that previously kept basic pay low. The codes also push toward simpler, more consolidated filings, but states issue their own rules, so state variation continues. Verify the current operative position per state.

What is the biggest single risk in multi-state payroll? Applying one state's rules (usually the head office's) to everyone. The fix is an authoritative employee-to-work-state mapping that drives all state-specific calculations and registrations.

Can spreadsheets handle multi-state payroll? For one or two states, often yes. Beyond that, the volume of differing slabs, cycles, deadlines, and registrations makes manual handling error-prone. A payroll platform with state-wise rule configuration becomes worth the investment.

How often should I review state rates and slabs? On a fixed periodic cadence and whenever you learn of a notification. PT slabs, minimum wages, and dearness allowance components are revised from time to time, and running stale figures is a silent compliance failure.

Conclusion

Multi-state payroll compliance in India is less about any single difficult rule and more about managing variation at scale: many states, many levies, many deadlines, all hanging off the simple-sounding question of where each employee works. The companies that handle it well do three things consistently—they map every employee to a work state, they maintain a living state compliance matrix and a consolidated calendar, and they centralise calculation while honouring local rules. Layered on top, the new labour codes raise the stakes by standardising the wage base, which makes a clean and consistent salary structure across states more important than ever.

You do not have to carry all of this in your head or in a fragile web of spreadsheets. If your workforce now spans several states and payroll has started to feel like five jobs instead of one, it may be time to let a purpose-built system do the heavy lifting. CozyHR handles state-wise professional tax, labour welfare fund, and minimum wage logic automatically, keeps your compliance calendar in one place, and maintains audit-ready records by state—so your team can spend less time chasing deadlines and more time on the people behind the payroll. Verify your current state-wise rates against the latest notifications, and consider a short demo to see how much of the manual burden you can hand off.