Multi-State Payroll in India: An Operations Guide

Multi-state payroll in India is where a perfectly good payroll process quietly falls apart. The moment your company opens a second office, hires a remote employee in another state, or places field staff across a region, a single payroll run stops being one calculation and becomes several overlapping ones. Professional tax differs. Labour welfare fund differs. Minimum wages differ by state, by industry, by skill category and by zone within the state. Holiday lists differ. Registration obligations differ. And every one of those differences has to land correctly in the same salary register on the same day of the month.

This guide is an operations manual for payroll managers, HR leaders and founders running payroll across multiple Indian states. It covers what actually varies, how to build a state matrix that keeps you out of trouble, how to structure your payroll calendar, and how to scale the process without adding a person for every new location.

Nothing here is legal advice, and rates and rules are revised frequently. Treat this as a framework for organising the work and verify every specific rate, threshold and due date against current official notifications for your states.

Why multi-state payroll is structurally harder

Indian employment and payroll obligations sit at two levels. Some are central: provident fund, employees' state insurance, income tax and TDS, gratuity, maternity benefit, the framework of the labour codes. Others are state subjects, and this is where the complexity lives: professional tax, labour welfare fund, shops and establishments registration, minimum wage notifications, holiday lists, and various registers and returns administered by state labour departments.

The result is that a central obligation like provident fund needs one process, while a state obligation like professional tax needs one process per state you operate in, each with its own registration, slab structure, deduction rule, filing frequency and due date.

Add a second complication: the state that governs an obligation is not always obvious. For a remote employee working from a state where you have no office, the correct treatment of professional tax and labour welfare fund is not automatic and depends on where the employer is registered and how the state's law defines the trigger. Companies get this wrong in both directions — deducting where they need not, and failing to deduct where they must.

And a third: what triggers an obligation is not always headcount at a single site. Registration thresholds, applicability of specific establishment laws, and the requirement to appoint certain officers can turn on the number of employees at a location, the nature of the activity, or the total across the establishment. A company with nine employees in six states has a very different obligation map from one with fifty-four employees in one.

The dimensions that vary by state

Build your mental model around these seven dimensions.

1. Professional tax

Professional tax is levied by some states and union territories on income from salary and profession, deducted by the employer and deposited with the state. Several states do not levy it at all. Among those that do:

• Slab structures differ. Some states use a handful of monthly income slabs; others have flat annual amounts or different structures for different categories.
• Deduction frequency differs. Monthly in most states; some operate on a different cadence, and a few have an annual lump component.
• Filing frequency and due dates differ. Monthly returns in some states, annual in others, and the due day of the month is not standard.
• Registration is two-part in many states: an enrolment certificate for the establishment itself and a registration certificate for deducting on behalf of employees. Missing one of the two is a very common gap.
• Exemptions differ. Certain categories of persons may be exempt in specific states.

The operational implication: you need a professional tax master per state, with slab table, applicability rule, deduction schedule, deposit due date and return due date, and it must be reviewed each year because states revise slabs.

2. Labour welfare fund

Labour welfare fund is a small periodic contribution, part employee and part employer, applicable in a subset of states. What varies:

• Whether the state has an LWF at all
• Contribution amounts, which are typically small fixed sums rather than percentages
• Contribution frequency — monthly, half-yearly or annual depending on the state
• Which employee categories are covered, often with a wage ceiling or a designation-based exclusion
• The due date and the filing mechanism

Because the amounts are tiny, LWF is the obligation most often forgotten. Because the amounts are tiny, it is also the one where a lapse is cheapest to fix and most embarrassing to be caught on during due diligence.

3. Minimum wages

Minimum wage rates in India are notified by both central and state governments, and the applicable rate depends on:

• The state
• The scheduled employment or industry category
• The skill classification of the role — typically unskilled, semi-skilled, skilled and highly skilled
• The zone or area classification within the state, since metropolitan areas usually carry higher rates
• The current dearness allowance component, which is revised periodically, often twice a year

This is the dimension with the most moving parts and the highest financial exposure. A company paying below minimum wage in one zone of one state for one category of worker has a genuine compliance problem, not a paperwork problem.

Practical approach: maintain a rate table keyed on state, industry, skill category and zone, with an effective-from date on every row. Refresh it on a calendar schedule tied to when your states typically revise. Then run an automated check every payroll cycle that compares each employee's applicable minimum against the relevant components of their pay for the correct comparison basis — noting that what counts towards minimum wage compliance is defined in law and is not simply gross pay.

4. Shops and establishments registration

Every state has its own shops and establishments legislation, and each commercial location generally needs to be registered under the law of the state where it sits. What varies:

• Registration timelines after commencing operations
• Renewal frequency, with some states offering perpetual registration and others requiring periodic renewal
• Prescribed working hours, spread-over limits, weekly off rules and overtime provisions
• Rules on women working at night and the conditions attached
• Leave entitlements prescribed as a floor
• Registers and records to be maintained, and increasingly the acceptance of electronic maintenance
• Display requirements — notices, abstracts and registration certificates to be displayed at the premises

A co-working desk, a small sales office, and a warehouse can each trigger a registration obligation. Companies that expanded quickly often discover during a funding diligence that four of their eleven locations were never registered.

5. Holiday lists

Public holidays vary substantially by state. Each state notifies its own list, typically including national holidays plus regional festivals, and some holidays are declared as restricted or optional holidays that employees may choose from.

For payroll and attendance this means:

• A separate holiday calendar per location, not one company-wide list
• A rule for remote employees: whose calendar applies — the state they live in, or the office they are attached to?
• Correct treatment of work performed on a holiday, which may attract compensatory off or premium pay depending on the applicable rules
• Coordination with your leave system so that a holiday in Bengaluru does not consume a leave day for an employee in Bengaluru while an employee in Pune works normally

6. State-specific registers, returns and displays

Beyond the central returns, states require various registers — of employment, wages, leave, overtime, fines and deductions — and periodic returns to the state labour department. The formats and the filing mechanisms differ, and states have been moving these online at different speeds. Several states operate consolidated online portals; others still expect physical or hybrid submissions.

The practical burden here is less about difficulty and more about tracking: knowing which return is due in which state on which date, and having the underlying data available in the required format.

7. Contract labour and third-party staffing

If you engage contract workers, obligations attach to both the contractor and to you as principal employer, and registration and licensing requirements are administered at the state level. Operating in five states with contract labour means five sets of registrations to track, plus ongoing verification that your contractors are actually depositing statutory dues for the workers deployed at your premises.

Building your state compliance matrix

This is the single most useful artefact in multi-state payroll. It is a table with one row per state and columns for every obligation. Build it once, review it quarterly, and make it the master reference that everyone uses.

Columns to include

Presence and trigger

• State
• Locations and addresses
• Headcount at each location
• Nature of establishment — office, warehouse, retail, factory, project site
• Whether any employees are remote-only in this state with no physical premises

Registrations

• Shops and establishments registration number, issue date, expiry or renewal date
• Professional tax enrolment certificate number
• Professional tax registration certificate number
• Labour welfare fund registration, where applicable
• Contract labour registration, where applicable
• Any industry-specific or activity-specific registrations
• The person named as responsible or manager in each registration, and whether that person still works with you

Recurring obligations

• Professional tax: applicable yes/no, slab table reference, deduction frequency, deposit due date, return frequency and due date
• Labour welfare fund: applicable yes/no, employee and employer amounts, frequency, due date
• Minimum wage: applicable schedule, zone, current rate table reference, next expected revision
• Registers to maintain and in what form
• Returns to file, frequency and due dates
• Notices and abstracts to display

Operational

• Holiday calendar reference for the year
• Working hours and weekly off rules applicable
• Overtime rules and rate applicable
• Leave entitlement floor under state law
• Local advisor or consultant handling filings, with contact
• Portal credentials custodian — the person, not the shared inbox

Keeping it current

A matrix that is built once and never reviewed becomes actively dangerous, because people trust it. Establish a maintenance rhythm:

• Monthly: verify that all deposits and filings due that month were made, with acknowledgement numbers recorded.
• Quarterly: review for rate changes, new notifications and any new locations or remote hires in new states.
• Annually: full refresh — renewals, holiday calendars for the coming year, minimum wage tables, professional tax slabs, and a check that named responsible persons are still employed.
• Event-triggered: any new office, any first hire in a new state, any crossing of a headcount threshold, any change in the nature of activity at a location.

Assign an owner by name. "Compliance" as a team owning it means nobody owns it.

The multi-state payroll calendar

Multi-state payroll fails on timing more than on calculation. Build a calendar and work backwards from the pay date.

A workable monthly rhythm

Days 1–5 of the payroll month: previous month's statutory deposits and filings — provident fund, employees' state insurance, professional tax for states with early due dates, TDS deposit. Record every acknowledgement.

Days 6–15: state-level returns falling due, LWF contributions where monthly, and any pending registrations or renewals. Also the window for reviewing new notifications published in the previous month.

Days 16–20: attendance and leave finalisation for the current cycle. This is where multi-state complexity shows up operationally: each location's holiday calendar has to have been applied correctly, each location's weekly off pattern respected, and overtime computed at the rate applicable in that state.

Days 21–24: payroll input freeze. New joiners, exits, revisions, reimbursements, LOP, one-time payments. For multi-state, add a specific check: has anyone moved states, joined in a new state, or started working remotely from a state you have not mapped?

Days 25–27: payroll processing, validation and approval. Run the state-specific validation suite described below.

Days 28–end: salary disbursement, payslip publication, and preparation of the next cycle's statutory challans.

Cut-off discipline across locations

The single biggest operational problem in multi-state payroll is inputs arriving late from distant locations. Fixes that work:

• One named input owner per location with a published deadline
• Self-service submission so employees enter their own reimbursements and declarations directly, removing the location coordinator from the critical path
• A visible dashboard showing which locations have submitted and which have not
• A hard rule: inputs after cut-off go into the next cycle, except for statutory or exit-related items. Publish the rule and apply it.

Handling remote employees in states where you have no office

This is now the most common multi-state question, and it does not have a single clean answer. The considerations:

Professional tax. Whether professional tax is deductible for a remote employee generally turns on the state's own law — some frame the levy on persons carrying on a profession or employment within the state, others on employers registered within the state. It is genuinely possible to have an employee in a professional-tax state where you have no registration and no obligation, and equally possible that the state's law expects you to register. Get a state-specific view rather than applying one rule everywhere.

Shops and establishments registration. Registration typically attaches to an establishment — a premises. A single employee working from their own home is often not an establishment for this purpose, but several states have expanded or clarified their positions, and having any company-controlled space in the state changes the analysis.

Minimum wages. The applicable rate is generally tied to where the work is performed. For genuinely remote roles this rarely bites, because remote knowledge roles are typically paid well above any minimum, but it matters if you have remote workers in lower-paid categories.

Holiday calendar. A practical policy choice. Common approaches: apply the calendar of the employee's assigned base office; apply the employee's state calendar; or publish a company list of fixed holidays plus a pool of optional holidays employees select from. The third is the most workable for distributed teams and the easiest to administer, but check it does not fall below any state-mandated minimum for locations where you do have establishments.

Employees' state insurance. ESI applicability is linked to implemented areas and coverage rules. An employee working from a location outside an implemented area may sit differently from a colleague in a covered area. Verify per case rather than assuming uniformity.

Practical guidance: maintain a "state exposure register" listing every state where you have even one employee, with a documented position on each obligation and the date that position was reviewed. When the count in a state grows past a handful, or when you take any physical space there, re-run the analysis properly.

Payroll system configuration for multi-state operations

If you are running multi-state payroll on spreadsheets, the failure is a matter of time, not probability. Whatever system you use, it needs these capabilities.

Location as a first-class entity. Every employee is attached to a work location, and every location carries its own state, holiday calendar, working hours rule, professional tax applicability, LWF applicability and minimum wage schedule. Changing an employee's location should change their statutory treatment automatically from the effective date.

Effective-dated master data. Professional tax slabs, LWF amounts and minimum wage rates all change on specific dates. The system must store them with effective-from dates and apply the correct version for the period being processed — including when you reprocess an earlier month.

Rule-driven, not formula-driven, statutory computation. Deductions should come from configured rules per state, not from formulas an analyst copied into a column. When a state revises a slab, you should change one master record, not audit 400 rows.

Per-location attendance and leave rules. Weekly off patterns, overtime thresholds and multipliers, and holiday treatment must vary by location within one system.

Consolidated and split outputs. You need the payroll register consolidated for finance, and split by state for statutory filing. If producing a state-wise register means a manual pivot every month, that is a design gap.

Challan and return-ready exports. The system should produce the data in, or close to, the formats each state and central portal expects. Even where a portal requires manual upload, having a correctly shaped export removes most of the effort.

Audit trail. Who changed which master, when, and what the previous value was. During any audit or diligence, this is what you will be asked for.

Multi-entity support, if applicable. Groups often operate several legal entities across states. Employees should sit under the correct entity for statutory purposes even if they report into a cross-entity structure operationally.

The validation suite: checks to run every cycle

Run these before payroll is approved. Ten minutes of checks prevents most multi-state errors.

Automate as many as your system allows and run the rest as a saved report. The value is in running them every month without exception, not in their sophistication.

Scaling without adding headcount per state

The instinct when opening a fifth location is to add a local HR coordinator. Sometimes that is right; often it just distributes the problem. Better levers:

Centralise the calculation, localise only what must be local. One payroll team, one system, one calendar. Local presence is needed for physical inspections, portal submissions requiring local credentials, and relationships with local authorities — not for computing salaries.

Use a single compliance partner with multi-state coverage, or a small number of them, rather than a different consultant per state. Consolidated partners give you one dashboard, one escalation path and one contract. Verify their actual on-ground coverage before signing; many claim national coverage and subcontract locally anyway.

Standardise employee-facing processes. One leave policy structure, one reimbursement process, one self-service portal, with state variations handled by configuration rather than by different processes. Employees moving between locations should not have to relearn anything.

Build a location opening runbook. A checklist that fires whenever you open a location or make a first hire in a new state:

1. Confirm the state's obligations against the matrix; add the state if new
2. Initiate shops and establishments registration within the state's timeline
3. Initiate professional tax enrolment and registration if applicable
4. Register for LWF if applicable
5. Load the state's holiday calendar for the current and next year
6. Load the applicable minimum wage schedule and zone
7. Configure the location in the payroll system with all state parameters
8. Assign a named responsible person and record them
9. Add the state's filing due dates to the compliance calendar
10. Confirm display requirements and arrange the required notices at the premises
11. Diarise the first renewal date

Ten items, mostly clerical, and doing them in the first month costs a fraction of doing them after a notice arrives.

Treat the compliance calendar as a system, not a document. Due dates should generate assignable tasks with owners and reminders, and completion should be recorded with the acknowledgement number. A shared spreadsheet of due dates is where compliance goes to be forgotten.

What to do when you find a gap

You will find gaps. Every multi-state company that looks honestly finds several. The response matters more than the discovery.

Assess scope first. Which state, which obligation, from what date, how many employees affected, what the quantum is. Do not start filing before you know the shape of the problem.

Get professional advice on the remediation route. Most states have mechanisms for late registration and delayed payment, typically with interest and penalty. Voluntary regularisation is almost always better positioned than being found in an inspection, but the sequencing and the disclosures matter, and they are state-specific.

Fix the root cause simultaneously. If professional tax was missed in a state for eight months because nobody added the location to the matrix, the remediation is incomplete until the location-opening runbook exists and the matrix has an owner.

Document the whole thing. What was found, when, what was done, what it cost, what changed. This file is what turns an uncomfortable diligence question into a two-minute answer.

Decide on the employee side deliberately. Where a deduction should have been made from employees and was not, recovering many months of arrears from salaries in one go is legally awkward and practically brutal. Take advice on whether to absorb the employee portion, and if you do recover it, spread it and communicate it clearly in advance.

Common multi-state payroll mistakes

Treating the registered office state as the default for everyone. A surprising number of companies deduct professional tax at the headquarters state's slabs for every employee regardless of where they work. It produces both over-deduction and under-deduction simultaneously, and it is immediately visible in any audit.

Configuring location as a text field. If "location" in your HR system is a free-text field where someone typed "Bangalore", "Bengaluru", "BLR" and "Bangalore Office", no rule can key off it reliably. Location must be a controlled master record carrying the state and all its statutory parameters.

Forgetting that headcount thresholds move. A location that had six employees last year and eighteen this year may have crossed a threshold that triggers a new registration, a committee constitution requirement, or an additional register. Nobody gets a notification when this happens. Build a monthly headcount-by-location report and review the thresholds relevant to your establishment types.

Letting portal credentials live with one person. When the payroll executive who holds the login for four state portals resigns, filings stop. Credentials should sit in a managed password vault with at least two people holding access, and the named responsible person on each registration should be reviewed annually.

Assuming your consultant is watching for rate changes. Many compliance partners file what you tell them to file and do not proactively monitor rate revisions for your specific schedules and zones. Confirm explicitly whose job it is to catch a minimum wage notification, and put the answer in the contract.

Applying one leave policy calendar company-wide. An employee in a location whose state prescribes a higher statutory leave floor than your company policy has an entitlement you may not be honouring. Check your policy against each state's floor, not just against the most generous or the most familiar one.

Running the state-wise split manually every month. If someone pivots the payroll register by state each cycle to prepare challans, that is both a recurring cost and a recurring error source. It should be a saved report.

No documentation of positions taken. When you decided that a particular state's professional tax did not apply to your two remote employees there, someone made a judgement. Write down what was decided, on what basis, on what date, and by whom. Two years later that note is the difference between a considered position and an oversight.

A short worked example

Consider a 320-person technology services company. Head office in one state, delivery centres in two others, small sales offices in two more, and about forty fully remote employees spread across seven additional states.

Before restructuring, the payroll team ran one consolidated calculation and handled state differences through a manual adjustment sheet maintained by a senior executive. Professional tax was applied from a lookup table last updated eighteen months earlier. Holiday lists were emailed each January and applied manually to attendance. Labour welfare fund had been deducted in two of the four applicable states. Nobody could produce a current list of which registrations existed in which state.

The remediation ran over one quarter:

1. Exposure mapping. Every employee mapped to a work location; every location mapped to a state; every state's obligations documented in a matrix with an owner. This alone surfaced two states with employees and no documented position on any obligation.
2. Registration audit. Existing registrations collected, verified against the establishments actually operating, and gaps listed with remediation advice from a compliance partner.
3. System configuration. Location made a controlled master with state parameters. Professional tax and LWF converted from a lookup sheet to effective-dated rule masters. Holiday calendars loaded per location for the current and following year.
4. Validation suite. Twelve automated checks built into the pre-approval step of each payroll run.
5. Runbook and calendar. A location-opening checklist and a compliance calendar generating assigned tasks with due dates and acknowledgement capture.

The measurable outcomes after two cycles: the manual adjustment sheet disappeared entirely, payroll approval moved two days earlier in the month, and the state-wise register that previously took half a day to prepare became a one-click export. The compliance gaps found were regularised over the following quarter with professional advice, at a cost far below what an inspection-driven discovery would have been.

The lesson is not that the company had problems — most do. It is that the problems were invisible until someone built the matrix, and trivially manageable afterwards.

Frequently asked questions

Which state's professional tax applies to a fully remote employee?

It depends on the specific state's legislation. Some states frame the levy on persons employed within the state, which can create an obligation even without an employer office there; others tie it to employers registered in the state. Because the answer varies and the amounts are small but the exposure is cumulative, get a state-specific written position from your advisor for each state where you have remote employees, record that position in your compliance matrix with the date it was taken, and revisit it annually.

Do we need a separate shops and establishments registration for every office?

Generally yes — registration attaches to the premises and is governed by the law of the state where the premises sits, so each commercial location needs its own registration under the applicable state law. Requirements for co-working spaces, warehouses and small sales offices vary, and some states have simplified or exempted certain categories. Confirm per location and per state, and do it within the timeline the state prescribes after commencing operations, since late registration usually attracts penalty.

How do we manage different holiday lists across states?

The cleanest structure for distributed companies is a small set of company-wide fixed holidays plus a pool of optional or restricted holidays from which employees select a defined number, subject to a location-level check that you meet any state-mandated minimum where you have establishments. Configure the calendar per location in your HR system so attendance and payroll apply the right list automatically, and publish the full year's calendar in advance so teams can plan around regional differences.

How often do minimum wage rates change and how do we keep up?

State governments typically revise the dearness allowance component of minimum wages periodically — commonly twice a year — and revise base rates less frequently. The practical approach is a rate table with effective-from dates, a calendar reminder aligned to each state's usual revision months, a subscription to your compliance partner's notification service, and an automated payroll check comparing every employee against their applicable minimum each cycle. Manual monitoring across five or more states does not survive contact with a busy month.

Can one payroll run cover employees across all states?

Yes, and it should. A properly configured system processes one payroll run while applying state-specific rules through the location attached to each employee, then produces both a consolidated register for finance and state-wise splits for statutory filing. Running separate payrolls per state is a symptom of system limitations, and it multiplies both effort and error rates.

What happens when an employee transfers from one state to another mid-month?

Handle it with an effective-dated location change so the system applies each state's rules to the correct portion of the month. Practically, check four things: professional tax treatment for the transition month, whether the applicable minimum wage changes, which holiday calendar applies to the days in each location, and whether the transfer affects ESI coverage. Document the transfer date in writing, because it drives all four.

Do we need labour welfare fund registration in every state?

Only in states that operate an LWF and where your establishment falls within the applicable coverage. Several states have no LWF at all. Where it applies, note that contribution frequency varies — monthly in some states, half-yearly or annual in others — so the item may not appear in your monthly rhythm and is easy to forget. Put the specific due months for each state in your compliance calendar rather than relying on a recurring monthly task.

How many people do we need to run multi-state payroll?

Far fewer than most companies assume, provided the system is configured properly and inputs come through self-service. A well-configured setup can run payroll for a few thousand employees across ten or more states with a small central team plus a compliance partner for filings. The headcount goes up when the system cannot handle location-specific rules, forcing manual adjustment — which is a tooling problem presenting as a staffing problem.

Bringing it together

Multi-state payroll is not intellectually difficult. It is an exercise in structured record-keeping: know exactly where you have people, know exactly what each state requires, encode those requirements in a system rather than in someone's memory, and check every cycle that what was supposed to happen actually did.

The companies that struggle are the ones treating each new state as an improvisation. The companies that scale smoothly built the matrix, the runbook and the calendar when they had two states, and then simply added rows.

CozyHR handles location-aware payroll natively — state-specific professional tax and labour welfare fund rules, per-location holiday calendars and shift rules, minimum wage checks, and consolidated plus state-wise registers from a single payroll run. Explore CozyHR and stop running a separate payroll in your head for every state you have entered.