Multi-State Payroll Compliance in India: 2026 Guide

Why Multi-State Payroll Compliance in India Is Harder Than It Looks

Multi-state payroll compliance in India is the point where a tidy payroll process quietly becomes a risk register. One office, one state, one set of registrations, and payroll is a monthly chore. Add a second location, a sales team in three states, and a handful of fully remote engineers, and the same payroll turns into a set of parallel obligations that do not share deadlines, formats, rates, or even vocabulary.

Founders usually discover this the expensive way. A salesperson is hired in Karnataka, works from home, gets paid out of the Maharashtra entity, and nobody registers anything for eighteen months. The problem does not surface until due diligence, or an inspector's visit, or a state department notice arrives at an address the company forgot it had.

This guide is written for HR managers, founders, and payroll teams at Indian SMBs who are already running payroll in one state and are expanding, or who have accidentally become multi-state and now need to clean it up. It covers the map of state-level obligations, how to decide which state's rules apply to a remote employee, the data model your HRMS needs, a month-end operating rhythm, common audit red flags, and a rollout checklist for entering a new state.

A note on rates before we start: professional tax slabs, labour welfare fund contributions, minimum wage schedules, and filing frequencies vary by state and change over time. Every number in this article is illustrative and labelled as such. Always verify against the current notification issued by the relevant state department before you configure payroll.

The Core Problem: Central Rules Are Uniform, State Rules Are Not

Indian payroll has two layers. The central layer is broadly uniform across the country. Income tax and TDS under the Income-tax Act, provident fund under the EPF & MP Act, and employee state insurance under the ESI Act follow national rules with national portals and national deadlines. If you get these right in one state, the logic transfers to the next.

The state layer does not transfer. Professional tax, labour welfare fund, shops and establishments registration, minimum wages, leave entitlements, and a long list of registers and returns are set by each state independently. Two states can use the same statute name and mean quite different things by it.

This asymmetry is the whole story of state-wise payroll rules. Your gross-to-net calculation is mostly national. Your deduction schedule, remittance calendar, registration footprint, and record-keeping obligations are mostly local.

What "multi-state" actually means

Companies use the phrase loosely. In compliance terms there are at least five distinct situations, and they carry different obligations.

• Multiple physical offices in different states, each with employees reporting to that address.
• One office plus field staff who work across state lines but are attached to a single establishment.
• One office plus fully remote employees living in states where the company has no premises.
• Multiple legal entities, each registered in a different state, with separate PAN or at least separate GST registrations and separate books.
• One entity, many branch registrations under a single PAN, with state-level registrations layered on top.

Most SMBs end up in a hybrid of the second, third, and fifth. That hybrid is exactly where errors concentrate, because the org chart says "one company" while the statute books say "several establishments."

Why it breaks in practice

Multi-state payroll rarely breaks because someone misread a rule. It breaks for mundane operational reasons.

• The employee master has one "location" field and it means whatever the last HR person decided it meant.
• Nobody updates the work state when an employee relocates, so deductions keep flowing to the wrong state for years.
• Registrations are obtained once and never renewed, because renewal cycles differ by state and nobody owns the calendar.
• Payment challans are generated in the right state but under the wrong registration number, and reconciliation never catches it because the total matches.
• The payroll vendor supports one state well and the rest through manual overrides in a spreadsheet.

Every one of these is a process failure, not a legal knowledge failure. That is good news, because process is fixable.

The Map of State-Level Payroll Obligations

Before you design a process, you need a clear map of what varies by state and what does not. Here is the practical breakdown.

The right mental model: central rules define how much you pay, state rules define where and how you report it.

Professional tax by state

Professional tax is the most visible state-level deduction and the one most often misconfigured. A few structural points that hold generally, without getting into specific numbers.

Professional tax is levied by states under their own Acts, and not every state levies it. Where it exists, it is usually a slab-based monthly deduction on salaried employees, with a ceiling on the annual amount that can be collected. There are typically two distinct obligations: PT on employees (employer deducts and remits) and PT on the employer or on the establishment itself (an annual enrolment or "professional tax on business" liability).

Practical variance you must handle:

• Slab structure. Some states use a small number of wide slabs, some use several narrow ones. Some states have gender-based or category-based differences historically embedded in their Acts.
• Deduction base. Some states define the base as gross salary, some as salary and wages including allowances, some carve out specific components. Read the definition in the state Act rather than assuming "gross."
• Frequency. Monthly remittance in some states, quarterly or annual in others, and sometimes frequency depends on the size of your liability.
• Special months. A few states have a different deduction amount in one specific month of the year to reconcile the annual ceiling. Payroll engines that assume a flat monthly amount get this wrong.
• Two registrations. Many states require both a registration certificate (for deducting from employees) and an enrolment certificate (for the establishment's own liability). Having one and not the other is a common gap.
• Employee-level exemptions. Categories such as senior citizens, persons with disabilities, or parents of children with disabilities may be exempt in some states. These need to be flags on the employee record, not manual month-end adjustments.

The compliance rule for professional tax by state is simple to state and annoying to execute: PT follows the state where the employee works, not where the company is headquartered and not where salary is disbursed from.

Labour welfare fund

Labour welfare fund is a smaller amount and a larger nuisance. Not all states have an LWF Act. Where it exists, it typically involves a small contribution from the employee and a larger matching contribution from the employer, remitted on a half-yearly or annual cycle rather than monthly.

Things that trip people up:

• Contribution months. Many states collect LWF in specific months only, commonly June and December, or a single annual month. If your payroll deducts every month, you have collected money you should not have.
• Eligibility definitions. States define covered employees by wage ceiling, designation, or exclusion of managerial and supervisory staff. The same employee may be covered in one state and excluded in another.
• Headcount snapshot date. Liability is often computed on employees on roll as of a cutoff date, not average headcount. Someone who resigns before the snapshot may drop out entirely.
• Separate portal and challan. LWF rarely shares infrastructure with PT. Expect a separate login, separate reference number, and often a physical or semi-digital process.

The amounts involved are small. The exposure is that unremitted LWF sits on your books indefinitely, accrues interest and penalty, and shows up in due diligence as a "small but unquantified" liability, which is exactly the phrase investors dislike.

Shops and establishments registration

Shops and establishments registration is the foundational state-level registration for a non-factory workplace. It is what makes your presence in a state official, and many downstream registrations reference it.

Key characteristics:

• It is granted under the state's Shops & Establishments Act, and in several states administered at the municipal or local body level rather than the state department.
• Registration is generally per premises. Three offices in one state can mean three registrations.
• Timelines to register after commencing operations are short in many states, often measured in weeks, not months.
• Renewal cycles vary. Some states issue perpetual registrations, some require renewal every year or every few years.
• Amendments matter. Changing the name of the establishment, the manager, the address, or the number of employees typically requires filing an amendment within a defined period.

The S&E Act is also what sets your leave entitlements, working hours, weekly off, overtime rules, and holiday obligations in that state. This is the part teams routinely miss: your leave policy is not purely a company decision. If a state's S&E Act mandates a higher earned leave accrual or a specific carry-forward treatment, your policy has to at least meet it.

Minimum wages by state

Minimum wages are set by state governments for scheduled employments, revised periodically, and usually structured as a basic component plus a variable dearness allowance linked to a consumer price index.

The dimensions of variation are wider than most teams expect:

• By state, obviously.
• By zone or area class within a state. Metro, urban, and rural zones typically carry different rates.
• By skill category. Unskilled, semi-skilled, skilled, and highly skilled are treated separately.
• By scheduled employment. The rate for shops and commercial establishments differs from that for a specific industry.
• By revision cycle. VDA is commonly revised on a half-yearly cadence, with basic rates revised less frequently.

For most white-collar SMB payrolls, actual salaries sit comfortably above minimum wage. The risk is concentrated in three places: entry-level roles in high-cost zones, interns and trainees on stipends, and contract or outsourced staff where you may carry principal employer responsibility. Also note that some states scrutinise structure, not just total. A salary that meets the minimum in total but sets an artificially low basic component to reduce PF liability invites challenge.

The labour codes overhang

India has consolidated a large number of central labour statutes into four codes covering wages, industrial relations, social security, and occupational safety and working conditions. States are responsible for framing their own rules under these codes, and the pace of that framing has varied.

For planning purposes, treat the codes as a direction of travel rather than a settled operating manual. Two implications are worth building for now:

1. A common definition of "wages." The codes push toward a standardised wage definition with a floor on the proportion that basic and similar components must represent. If your compensation structure leans heavily on allowances to suppress PF and gratuity costs, model the impact of a stricter definition before it becomes mandatory.
2. More centralised registration and filing. The intent is fewer registrations and consolidated returns. Design your data model so that a state-level obligation is a configurable attribute, not a hard-coded assumption, and migration becomes an update rather than a rebuild.

Which State's Rules Apply? The Remote Employee Question

This is the single most common question from distributed teams, and it does not have a one-line answer. Break it into the specific obligation, because different obligations use different tests.

The three positions companies take on remote workers

There is genuine ambiguity when an employee works from home in a state where the employer has no premises. In practice, companies adopt one of three positions.

Position 1: Attach the employee to the nearest registered establishment. The employee is on the books of the Bengaluru office even though they live in Kochi. All state obligations follow Bengaluru. This is the simplest, and it is defensible when the employee genuinely reports to and occasionally visits that office. It is weaker when the employee has never set foot there and has worked from another state for years.

Position 2: Register in the employee's state. The company obtains PT registration and, where required, other registrations in the state where the remote employee lives. This is the most conservative approach and the most expensive per head. It makes sense above a threshold of employees in a state, or where the state has an active enforcement posture.

Position 3: Attach to the registered office / headquarters. All employees, regardless of location, are treated as belonging to the head office establishment. This is common in early-stage companies and is the position most likely to be challenged once a state notices a cluster of residents drawing salary from an out-of-state employer.

How to choose a position

Use a threshold model rather than treating every remote hire identically.

• One or two remote employees in a state, no premises, no client-facing presence. Attach to the nearest or head office establishment, document the rationale, and revisit annually.
• A growing cluster, roughly five or more, or any employee with a company-paid workspace. Move toward registering in that state. A leased desk, a co-working membership in the company's name, or a signboard generally creates a stronger argument that you have an establishment there.
• Any physical office, showroom, warehouse, or service centre. Register. This is not a judgement call.
• Field or sales staff who travel across states. Attach to the establishment they report to and are administered from, and keep tour records that show the base location.

Document whichever position you take, in writing, with the reasoning and the date. If a question is raised three years later, a contemporaneous note showing you applied a consistent, reasoned policy is materially better than reconstructing an explanation under pressure.

Common scenarios, resolved

• Employee relocated mid-year, still on the old office rolls, working from home. PT should generally shift to the new work state from the month of relocation if you have or obtain registration there. If you retain the old attachment, expect to justify it.
• Employee splits time between two offices in different states. Attach to the primary establishment, the one that administers their attendance, appraisal, and reporting line. Keep the split documented.
• Employee working from abroad temporarily. State-level deductions typically follow the Indian establishment they remain attached to. The larger questions here are tax residency and social security, which sit outside state payroll.
• Consultant on a professional services contract. Not a payroll compliance question, but a worker-classification one, and misclassification carries its own risk. Do not use "consultant" as a workaround for avoiding state registration.

One Entity, Many States vs Many Entities

The structural choice drives a large share of your ongoing compliance workload. Both models are legitimate. They fail in different ways.

One entity with branch registrations

A single company with a registered office in one state and branch or additional-place-of-business registrations in others. You get one PAN, one set of books, one income tax return. PF and ESI can often be managed under one code with sub-codes, simplifying central filings. Employee transfers between locations are internal, with no separation and rehire, no gratuity reset, no new PF member ID.

The catch is that state registrations still stack up. One entity does not mean one S&E registration, and each state's PT and LWF still apply per location. Your statutory records also have to be maintainable location-wise, which many small accounting systems do poorly.

Multiple entities

Separate companies or LLPs incorporated in different states, often for historical reasons, joint ventures, or state-specific incentives. The upside is clean ring-fencing of liabilities and genuine local management autonomy.

The downside is that everything multiplies: PAN, TAN, GST, PF code, ESI code, ROC filings, statutory audit, board meetings. Employee movement across entities becomes a legal transfer, with implications for continuity of service, gratuity, leave encashment, and PF transfer. Group-level reporting requires deliberate consolidation, and intercompany cost allocation for shared employees creates transfer pricing and GST questions.

A simple decision frame

For most SMBs the answer is one entity with disciplined branch registrations. Multiple entities should be a deliberate choice driven by a business reason, not an accident of how the company grew.

Registrations You Need Per Location

Here is a working checklist for what typically needs to exist when you open a location in a new state. Verify specifics against the state, because thresholds and authorities differ.

Establishment-level

1. Shops & Establishments registration for the premises, filed within the state's prescribed window after commencing operations.
2. Professional tax registration certificate, for deducting PT from employees in that state.
3. Professional tax enrolment certificate, for the establishment's own PT liability where applicable.
4. Labour welfare fund registration, where the state has an LWF Act and you meet the coverage criteria.
5. PF branch or sub-code mapping, so contributions and returns reflect the correct location.
6. ESI branch registration and mapping to the correct ESI local office and dispensary, where the area is notified.
7. GST registration for the state, if you have a place of business there. This is a tax question, not a payroll one, but it usually gets triggered by the same event.
8. Contract labour licence, if you engage contractors above the state threshold at that location.

Ongoing at each location

• Statutory registers as prescribed by the state, covering employment, wages, deductions, overtime, leave, fines, and advances.
• Mandatory notices and abstracts displayed at the workplace in the prescribed language.
• Internal Committee constituted under the sexual harassment law for every office meeting the threshold, with annual reporting.
• Periodic returns under the state's S&E Act and other applicable statutes.
• Renewal calendar for every registration with a finite validity.

Documents you will typically be asked for

Certificate of incorporation and MOA/AOA or LLP agreement, entity PAN and TAN, a board resolution or authorisation letter for the signatory, proof of premises (lease deed, utility bill, owner's NOC), an employee list with designations and salary details, and identity and address proof with photographs for directors and the designated manager.

Prepare a single "registration pack" with all of these in a shared folder, current and scanned. Half the delay in state registrations is document assembly, not government processing.

The Employee Master: Data Model for Multi-Location Payroll

Most multi-state payroll problems are data problems in disguise. If your employee master cannot express where someone works, it cannot compute the right deductions.

Fields you actually need

Effective dating is not optional

The single highest-value design decision is that location must be effective-dated. Storing "current work state" as a single overwritable field destroys the audit trail you need when a mid-year relocation is questioned.

An effective-dated record looks like this:

With this structure, payroll for any historical month can be recomputed correctly, and you can answer "which state did we deduct PT for in September 2024, and why" without archaeology.

Establishment master

Alongside the employee master, maintain an establishment master. This is the table your payroll engine reads to know what rules to apply.

If this table lives in a spreadsheet on someone's laptop, you do not have a compliance process, you have a dependency on that person.

The Multi-Location Payroll Process, Month by Month

A workable multi-location payroll process is built on a fixed rhythm with hard cutoffs. Here is a template that works for most SMBs running a calendar-month payroll with payment on or around the last working day.

Phase 1: Inputs (roughly days 1 to 18)

Continuous collection, not a month-end scramble.

1. New joiner and exit data entered on the day of the event, not at month end. Every joiner needs work state, establishment, entity, and structure assigned before their first payroll.
2. Attendance and leave captured location-wise, with state-specific holiday calendars applied. A national holiday list will misstate leave balances in states with different festival holidays.
3. Location change requests routed through a defined approval, because a relocation changes deductions, leave entitlement, and possibly minimum wage compliance.
4. Variable pay inputs, incentives, overtime, and reimbursements collected against a fixed date.

Phase 2: Cutoff and lock (around days 18 to 20)

1. Announce a single company-wide cutoff. Multi-location payroll fails when each office negotiates its own deadline.
2. Lock attendance and leave. Late items move to the next cycle as arrears, except for statutory items that cannot wait.
3. Freeze the employee master. Any change after this point requires an exception approval and is logged.

Phase 3: Computation and validation (roughly days 20 to 24)

1. Run gross-to-net.
2. Run state-wise validation before anything else. This is the step most teams skip.
3. Compare deduction totals by state against the prior month and investigate variances beyond a set threshold.
4. Verify that every active employee maps to a valid establishment with valid registrations.
5. Check minimum wage compliance by state, zone, and skill category for the lowest-paid band.
6. Confirm PT special-month logic, LWF contribution months, and any state-specific one-off.

Phase 4: Approval and disbursement (roughly days 24 to month end)

1. Route the register for approval with a state-wise summary attached, not just a company total.
2. Generate the bank file. If you have multiple entities, generate one file per entity from the correct bank account. Paying a Karnataka entity's employees from the Maharashtra entity's account creates an intercompany receivable and an audit query.
3. Disburse. Publish payslips showing the correct state-specific deductions with correct labels.

Phase 5: Statutory remittance and filing (early the following month)

1. TDS deposit and, at the prescribed intervals, quarterly returns.
2. PF and ESI contribution filing and payment through the central portals, correctly mapped to codes and sub-codes.
3. PT remittance per state, per registration, on that state's frequency and format.
4. LWF in the applicable contribution months only.
5. State-level returns under the S&E Act and other applicable statutes on their cycles.
6. Register updates, both physical and digital, at each location.

Phase 6: Reconciliation and close (mid-month following)

1. Reconcile deductions computed to amounts remitted, state by state and registration by registration.
2. Reconcile payroll cost in the payroll system to the general ledger by cost centre and entity.
3. Clear the statutory liability account. Anything more than one cycle old is a red flag.
4. Archive challans, acknowledgements, and filed returns against the establishment master.
5. Log open items with owners and due dates into the next cycle.

A month-end calendar you can adapt

Adjust the dates to your pay date. The principle that matters is that validation is a named step with a named owner, sitting between computation and approval.

Worked Example: A Three-State SMB

The following is a fully illustrative example. Names, amounts, and rates are invented for teaching purposes and do not represent any actual state's rates. Do not use these figures for configuration.

Illustrative Tech Pvt Ltd, one legal entity, registered office in Maharashtra.

Step 1: Determine the establishment footprint

Mumbai, Bengaluru, and Hyderabad each require their own S&E registration because each is a physical premises. The co-working arrangement in Hyderabad still counts, since the company has a dedicated, named space with employees reporting there. The nine remote employees have no premises, so the company attaches them to the nearest registered establishment and documents the decision.

Step 2: Map registrations to establishments

Note the "verify" entries. Not every state has an LWF Act, and ESI coverage depends on whether the area is notified. Those are lookups, not assumptions.

Step 3: Illustrative monthly deduction summary

Assume, purely for illustration, that the states apply monthly PT of Rs 200 per covered employee above a threshold salary, and that all 85 employees are above that threshold.

Three separate challans, three separate portals, three separate acknowledgements to archive. The total is small. The process cost is not, and it does not shrink as you grow, it multiplies.

Step 4: The failure mode this prevents

Before this mapping existed, the company deducted PT from all 85 employees under the Maharashtra registration, because that is where payroll was configured. The total deducted looked right. The reconciliation matched. Nothing flagged.

The actual position was that Karnataka and Telangana had 40 employees generating an unregistered, unremitted liability, while Maharashtra received remittances for 40 employees it had no claim to. Unwinding that means voluntary registration, back payment with interest, and a refund claim that is realistically not worth pursuing. The lesson is that a matching total is not a control. Only state-wise reconciliation is.

Step 5: Illustrative annual compliance calendar

Even a modest three-office company is running something like forty to sixty discrete compliance events a year once you count each state separately. That volume is why this needs to be systematised rather than remembered.

Multi-State Payroll Compliance Errors and Audit Red Flags

These are the issues that surface repeatedly in payroll reviews and due diligence at Indian SMBs. Run through them as a self-audit.

Registration and structure errors

• Operating in a state with no S&E registration. Often because the office started as "just two people" and nobody revisited it.
• Registration in the company's old name after a rebrand or conversion, with no amendment filed.
• The named manager on the S&E certificate left the company years ago. Amendment filings for manager changes are widely ignored and easy to check.
• Registered headcount far below actual headcount, where the state's registration is banded by employee count.
• PT registration obtained but PT enrolment never done, or the reverse.
• Expired registrations in states with finite validity, discovered only when a renewal-linked filing is rejected.

Deduction and computation errors

• PT deducted under the wrong state's registration, as in the worked example above.
• PT not adjusted for the special month in states that use one, leaving an annual shortfall or excess.
• LWF deducted every month in a state that collects half-yearly, creating an unremitted balance in the liability account.
• LWF not deducted at all in a covered state, usually because the payroll template was copied from another state.
• Minimum wage breach on structure, where total pay is compliant but the basic component is set artificially low.
• Zone misclassification for minimum wages, applying a rural rate at an urban location.
• State holiday calendars not configured, so leave balances and loss-of-pay calculations are wrong at non-HQ locations.
• Overtime computed on a single national rule when state S&E Acts prescribe different multipliers and spread-over limits.

Process and record errors

• Statutory registers maintained only at head office. Several states require them at the establishment, available for inspection.
• Notices and abstracts not displayed in the prescribed local language.
• Payslips that do not itemise statutory deductions with correct names, which is a wage-payment requirement, not a formatting preference.
• No effective-dated location history, making historical recomputation impossible.
• Statutory liability account carrying balances older than one cycle, which is the single fastest indicator an auditor uses.
• Bank transfers made from the wrong entity's account in multi-entity setups.

The five checks a reviewer will run first

1. Does the number of S&E registrations equal the number of physical locations?
2. Does the state-wise headcount in the payroll register match the state-wise remittance challans, month by month?
3. Is the statutory liability account clean at each month end?
4. Are all registration certificates current, in the correct name, with the correct signatory?
5. Does the lowest-paid employee at each location clear the applicable minimum wage on both total and structure?

If you can answer all five with evidence in under an hour, your multi-state payroll compliance is in reasonable shape. If any of them takes a week of digging, that is the gap.

Centralise or Localise? Drawing the Line

A recurring debate in distributed teams is how much payroll authority sits at head office and how much sits with local HR or a local consultant. The answer is not all one way.

Centralise these

• Payroll computation. One engine, one set of rules, one register. Never run separate payrolls per location if you can avoid it.
• Compensation structures and templates. Local variation should be a parameter, not a separate design.
• Master data governance. One team owns who can change work state, entity, and salary structure.
• Approval and disbursement. One approval chain, one bank release process per entity.
• Reconciliation and the general ledger. Consolidated, with state-wise breakdowns available.
• Policy on remote employee state attachment. A single documented position, applied consistently.

Localise these

• Physical registers, displays, and inspector interaction. Someone at the location has to hold these.
• Registration filing and renewal. Local consultants navigate state portals and offices far more efficiently, and several processes still require physical presence.
• Language-specific documentation. Notices, and in some states appointment letters and registers, in the local language.
• Local statutory committee constitution. Internal Committees under the sexual harassment law must exist at the office level with local members.
• Relationship with the local authority. This matters more than people from a pure process background expect.

The hybrid that works

The pattern most successful SMBs land on is a central payroll and compliance owner plus a network of local retainers. The central owner runs the calendar, holds the establishment master, chases evidence, and does the reconciliation. Local retainers execute filings in their state and provide the certificates and acknowledgements back.

The critical rule is that the central owner holds the master calendar. If each retainer holds their own calendar, you have no visibility, and gaps only appear when something goes wrong. Ask every retainer for a filing acknowledgement within a set number of days of every due date. No acknowledgement means no filing, until proven otherwise.

HRMS Requirements for Multi-State Payroll Compliance in India

Not every payroll tool handles multi-state work well. Many handle one state well and fake the rest with overrides. When evaluating a system for distributed team payroll in India, test against these requirements rather than the feature list on the website.

Non-negotiable capabilities

1. Multi-entity support with proper separation. Separate PAN, TAN, bank accounts, PF and ESI codes, and separate registers per entity, with the ability to view consolidated group reporting.
2. Establishment as a first-class object. Not a text field on the employee record. Registrations, calendars, and rules attach to it.
3. State-driven statutory logic. PT slabs, LWF cadence, and applicability rules configured per state and versioned by effective date, so historical months compute correctly.
4. Effective-dated employee attributes. Location, entity, structure, and designation must all have history.
5. Mid-month location change handling. The system should apply the correct state's rules by the correct proration logic, not force a manual adjustment.
6. State-wise reports out of the box. Deduction summaries, headcount, and remittance-ready outputs per state per registration.
7. State holiday calendars. Multiple calendars, mapped to locations, feeding leave and attendance.
8. State-specific leave rules. Accrual rates, carry forward caps, and encashment logic that vary by the governing S&E Act.
9. Register generation in prescribed formats. State-format registers, not a generic export.
10. Audit trail on everything. Who changed what, when, and with what approval.

Strong-to-have capabilities

• Compliance calendar with alerts, owner assignment, and evidence upload against each event.
• Minimum wage checks built into the payroll validation step, by state, zone, and category.
• Document vault holding registration certificates with expiry tracking.
• Bank file generation per entity with maker-checker.
• API or clean export to accounting, so the GL posting is not a re-keying exercise.

Questions to ask a vendor

• "Show me how an employee who moves from one state to another mid-month is handled, end to end."
• "Show me the state-wise PT remittance report for last month, split by registration number."
• "How do you version statutory rules when a state revises its slabs mid-year? Can I recompute a prior month on the old rules?"
• "Which states' LWF logic is natively supported, and what happens for the rest?"

Vendors who answer these crisply have built for multi-state. Vendors who redirect to a support process have not.

Rollout Checklist: Expanding Into a New State

Use this as a repeatable playbook. Assign an owner and a target date to each line. Timelines are indicative and vary by state.

Phase A: Before the first hire

1. Confirm whether the state requires a physical premises registration for your intended presence.
2. Decide the structure: branch of the existing entity, or a new entity. Default to a branch.
3. Identify a local consultant or retainer and get a scope and fee agreed.
4. Assemble the registration document pack: incorporation documents, PAN, TAN, board resolution, lease or NOC, director identity documents, signatory authorisation.
5. Check whether the state has an LWF Act and note the coverage criteria and contribution months.
6. Pull the current minimum wage notification for your scheduled employment and zone.
7. Note the applicable S&E Act provisions on leave, working hours, weekly off, and overtime, and compare them against your existing policy.
8. Budget for registration fees, retainer fees, and any professional tax enrolment liability.

Phase B: Setting up

1. Execute the lease or workspace agreement, with the entity name exactly matching your incorporation documents.
2. File the S&E registration within the state's prescribed window.
3. Apply for the PT registration certificate and the PT enrolment certificate.
4. Apply for LWF registration if applicable.
5. Add the location to your PF and ESI setup with the correct sub-code and local office mapping.
6. Obtain GST registration for the state if you have a place of business there.
7. Create the establishment record in your HRMS with all registration numbers, validity dates, and the filing calendar.
8. Configure the state-specific PT slabs, LWF cadence, holiday calendar, and leave rules.
9. Adjust the salary structure template if state minimum wage or structure rules require it.

Phase C: Going live

1. Assign employees to the new establishment with a correct effective date.
2. Run a parallel or test payroll and verify state-wise deduction outputs before the first live run.
3. Confirm the first month's remittance goes to the correct registration and archive the challan.
4. Set up the physical registers and display the mandatory notices in the prescribed language.
5. Constitute the Internal Committee for the office if it meets the threshold.
6. Brief employees on any changed leave entitlements or deductions with a short written note. Unexplained new deductions on a payslip generate more tickets than anything else in payroll.

Phase D: Steady state

1. Add every recurring due date for the location to the central compliance calendar with an owner, and set renewal reminders at least 60 days before each registration expiry.
2. Schedule an annual review of the location's registrations, headcount bands, and named manager.
3. Include the location in the monthly state-wise reconciliation from the first cycle.

Adapt this and reuse it every time. The value of a checklist is that it removes the need to remember, and multi-location payroll compliance is far more a memory problem than an intelligence problem.

Closing a Location or Offboarding a State

Exits get less attention than entries and cause more residual liability. When you shut an office or your last employee in a state leaves, the obligations do not end automatically.

The closure sequence

1. Complete final payroll for employees at that location, including full and final settlement, leave encashment, gratuity where eligible, and any notice pay adjustments.
2. Deduct and remit the final period's state deductions. PT for the final month, LWF if the closure falls in a contribution month.
3. File all pending returns up to the date of closure. Do not leave a partial year open.
4. Surrender or notify closure of the S&E registration in the prescribed manner and within the prescribed window. Many states require intimation of closure, and failure to do so leaves the registration live with continuing filing obligations.
5. Cancel or surrender the PT registration and enrolment for that establishment. This is the one most often forgotten, and it is the one that keeps generating notices.
6. Cancel the LWF registration if applicable.
7. Update PF and ESI mapping, closing the sub-code or reassigning employees who are transferring to another location.
8. Cancel the state GST registration if you no longer have a place of business there.
9. Retain records for the statutory retention period. Registers, wage records, and filings must be preserved even after closure. Store them digitally with a clear index.
10. Update the establishment master to closed status with the closure date and evidence attached, rather than deleting the record.

If employees are transferring, not exiting

Where an office closes but employees move elsewhere, issue a formal location change letter with an effective date, update the effective-dated location record so payroll switches state rules from the right month, and confirm whether the new state requires a registration you do not already hold. Check whether leave entitlement changes under the new state's S&E Act and communicate the difference explicitly. Preserve continuity of service: a location change within the same entity is not a break in service, and payroll should not treat it as one.

The commonest closure mistake

A company shuts a small office, informs the landlord, moves everyone remote, and considers the matter closed. Two years later a notice arrives for non-filing of returns under a registration nobody remembered was still active, with penalties accrued for every missed period. Closing registrations is cheap. Leaving them open is not.

Cost, Proportionality, and the Quarterly Review

Registering in every state where you have a single remote employee is expensive relative to the benefit for a small company, and the statutory amounts collected for one person are trivial. The sensible approach is proportionate risk management: register wherever you have physical premises without exception, register wherever a cluster builds past your defined trigger, and document the position for everything below that line.

A quarterly two-hour review catches the drift that monthly rhythm misses. Sweep registration validity, names, and designated managers. Compare headcount by state against registrations. Age the statutory liability account. Sample three establishments and three months of filing evidence. Refresh minimum wage rates. Check whether any state changed leave or hours rules that your policy now falls short of. Log the output with owners and dates, because over a year that log becomes the compliance history a diligence process will ask for.

FAQ

Do I need a separate payroll for each state?

No, and you should actively avoid it. Run one payroll engine with state-specific rules configured as parameters. Separate payroll runs per location fragment your data, break consolidated reporting, and make reconciliation nearly impossible. What you need is one computation with state-wise outputs, not multiple computations.

If an employee works from home in a state where we have no office, which state's professional tax applies?

Professional tax generally follows the state where the employee works. If you have no registration in that state, you have three practical options: attach them to your nearest registered establishment and document the reasoning, obtain a registration in their state, or attach them to head office. The first is common for one or two employees, the second becomes appropriate as a cluster builds. What matters is that you make an explicit, documented, consistently applied decision rather than defaulting silently.

Does every state in India have professional tax and labour welfare fund?

No. Professional tax is levied by some states and not others, and labour welfare fund exists only in states that have enacted an LWF Act. Both the applicability and the rates change over time, so treat any list you find as a starting point and verify against the current notification from the relevant state department before configuring payroll.

We have one company but offices in four states. Do we need four shops and establishments registrations?

Generally yes, and possibly more. Shops and establishments registration is per premises, not per company. Four offices in four states means at least four registrations, and if you have two offices in the same state, that state will typically require two. The registration is tied to the physical location and the address on the certificate must match your actual premises.

How do we handle an employee who relocates to another state mid-month?

Update the effective-dated location record with the correct date so the system applies each state's rules for the relevant part of the month. Check whether the new state requires deductions you were not previously making, verify that you hold the necessary registration there, and confirm whether leave entitlement changes under the new state's Shops and Establishments Act. Communicate any payslip changes to the employee in advance so the deduction change is not a surprise.

What is the difference between professional tax registration and professional tax enrolment?

In most states that levy professional tax, the registration certificate authorises you to deduct professional tax from employees' salaries and remit it, while the enrolment certificate covers the establishment's or employer's own professional tax liability. They are separate applications, separate numbers, and often separate payment cycles. Holding one and not the other is a common gap that surfaces during reviews.

Will the four labour codes make multi-state payroll compliance simpler?

The intent is consolidation, with fewer statutes, more standardised definitions, and simpler registration and filing. In practice, states frame their own rules under the codes, so meaningful state variation is likely to persist. Build your payroll system so that state-level rules are configurable data rather than hard-coded logic, and any future transition becomes a configuration update rather than a rebuild.

How much should a small company budget for multi-state compliance?

It varies too widely by state and scope to quote a figure responsibly, but the useful way to think about it is per-location rather than per-employee. Each new state adds a fixed annual cost made up of registration and renewal fees, a local retainer, and internal effort on the compliance calendar. Because it is largely fixed, the cost per employee falls sharply once you have more than a handful of people in a state. That maths is exactly why a headcount threshold, rather than a blanket rule, is the right trigger for registering in a new state.

Conclusion

Multi-state payroll compliance in India is not intellectually hard. It is operationally relentless. The rules themselves are knowable, but they are numerous, they differ by state, they change, and they arrive on separate calendars through separate portals. Almost every failure traces back to a missing data field, an unowned deadline, or a reconciliation that checked a total instead of a breakdown.

The fix is structural. Treat the establishment as a real object in your systems. Make location effective-dated. Reconcile state by state, registration by registration, every month. Keep one compliance calendar with named owners. Write down your position on remote employees and apply it consistently. Use a checklist every time you enter a state and a closure sequence every time you leave one. None of this is glamorous, and all of it compounds.

If you are managing this across spreadsheets, state portals, and a group chat with three consultants, it is worth seeing what a purpose-built system does instead. CozyHR handles multi-entity and multi-location payroll with state-wise statutory logic, effective-dated employee records, and a compliance calendar that surfaces what is due where. Take a look when you are ready to make the monthly scramble a routine.