Multi-State Payroll Compliance in India: The Complete 2026 State-by-State Guide with Rates, Calendar & Checklist

Q1: What Is Multi-State Payroll Compliance in India and Why Does the Federal Central-vs-State Split Break Every Excel-Based Stack in 2026?

Multi-state payroll compliance in India is the discipline of running one payroll operation that simultaneously satisfies central statutes, including PF, ESI, TDS, and the four Labour Codes, and state-specific statutes, including Professional Tax, Labour Welfare Fund, Shops & Establishments, minimum wages, leave, and bonus, for every location where an employee actually works, including remote and hybrid staff whose physical work-location governs the rule-set.

⚠️ The 10 PM, 28th-of-the-Month Scenario You’ve Probably Lived

I’ve watched this play out in a 1,200-employee manufacturer’s HR war-room more times than I can count. It’s the 28th, payroll closes in 48 hours, and three parallel problems surface in the same hour. The Maharashtra LWF December deposit was missed because the half-yearly cycle sits in an Excel reminder nobody opened. 14 Bengaluru remote joiners got onboarded on the Pune PTRC, so Karnataka PT was under-deducted for six months, and the Tamil Nadu minimum-wage revision notified in October silently broke the Chennai plant’s skilled-operator wage floor. Four Excel trackers, two WhatsApp groups, one panicking Payroll Manager.

This guide is written for the people who live inside that scenario: HR Heads, Payroll Managers, CFOs, and founders at 100–5,000 employee firms operating across 2+ Indian states. For a deeper primer on the category, start with our statutory compliance payroll explainer.

❌ Why the Default HR Stack Can’t Handle This

Most Indian mid-market payroll stacks hardcode the registered-office state for every employee because PF, ESI, and TDS are uniform nationally. Teams assume “payroll compliance” is a single engine with minor state flavours. It isn’t. Professional Tax, LWF, Shops Act, and minimum wages are state-owned under Entry 60 of the State List and Article 276 of the Constitution, which creates a genuinely dual-track obligation. Excel formulas can’t auto-switch a PT slab when an employee moves from Noida (no PT) to Bengaluru (₹200/month). Biometric exports don’t know about LWF cycles. Outsourced payroll vendors work from the client’s header sheet, and if the header is wrong, the payslip is wrong. Our payroll software compliance risk guide walks through the failure modes in detail.

✅ The 3-Layer Architectural Reframe

Stop thinking of compliance as a central engine with state add-ons. The reframe that actually works is a three-layer model: a central core layer (PF, ESI, TDS, Labour Codes), a state logic layer (PT, LWF, Shops Act, minimum wages, leave, bonus), and a location detection layer (the work-state declared per employee, refreshed monthly). Each layer is independently auditable, and a change in one layer, such as a Karnataka PT slab revision or a new hybrid policy, doesn’t destabilise the other two.

💰 How HROne’s Payroll Engine Implements the Model

We built the HROne payroll software around this three-layer model natively. Each employee carries a live work-state field fed by the HR inbox declaration. The engine applies the correct PT, LWF, Shops Act, and minimum-wage bundle at run-time, central PF/ESI/TDS runs uniformly, and every outcome flows into one statutory register per legal entity. Subscription meters only after go-live, so the clock doesn’t start ticking while you’re still cleaning up the old stack. The MRDIY case study documents how cycle times collapsed from 10 days to 5–6 days after consolidating multi-state logic on this architecture, and 1,500+ brands run on the same instance pattern today.

“I like HROne for its zero-touch payroll and compliance automation. It handles salary calculations, statutory deductions, PF, ESI, taxes, and filings automatically, with zero manual intervention, removing payroll errors and compliance anxiety during audits.”

— Waldon S., Reviewer HROne G2 – Verified Review

“Proper calculation of PF and ESI was a pain area for us before, but now with the HROne automated calculation process, results are up to the mark and following Indian tax compliances properly.”

— Ajay K., Reviewer HROne G2 – Verified Review

Q2: What Are the 2026 Central Compliance Rules, PF, ESI, TDS, Payment of Wages & Minimum Wages Act, for Multi-Location Employers?

Central compliance in 2026 rests on four pillars: PF (12% employer + 12% employee on basic up to the ₹15,000 statutory ceiling, ECR by the 15th), ESI (3.25% employer + 0.75% employee for employees earning ≤ ₹21,000/month, return by the 15th), TDS on salary (monthly deposit by the 7th, quarterly Form 24Q), and the Minimum Wages Act + Payment of Wages Act federal baselines that every state notification must sit above.

🏛️ PF & ESI: Registration, Mapping, Filing

The operating sequence is mechanical, but each step has a multi-location trap most teams miss.

1. Register every establishment with ≥ 20 employees under EPFO and ≥ 10 employees under ESIC within 30 days of crossing the threshold, per location, not per holding entity.
2. Map each employee to the nearest PF regional office and ESIC dispensary by their actual work location. Hardcoding the HQ dispensary is the most common audit flag, because medical claims get rejected when the employee is 1,400 km from the mapped hospital.
3. File ECR monthly by the 15th. Delay triggers 12% p.a. interest plus 5–25% Section 14B damages depending on the delay bracket. ESI monthly return is due the same 15th.

Our ESI contribution calculation guide breaks down the worked examples.

⏰ TDS-on-Salary: The Multi-State Nuance No One Briefs You On

TDS is central, but the filing story gets messy the moment employees cross state lines.

• Step 4, TAN-linked record continuity. Form 24Q, Form 16, and investment declarations must reflect each employee’s correct place of employment for the assessment year. When an employee transfers from the Pune TAN to the Chennai TAN mid-year, both Forms 16 must stitch together without proration errors, or the individual’s ITR mismatches with AIS.
• Step 5, Payment of Wages Act cadence. Salary disbursement must hit by the 7th of the following month for establishments with < 1,000 employees and by the 10th for ≥ 1,000, irrespective of how many states you operate in. A delay in one location is a breach for the whole entity.

📋 Central Rates & Deadlines at a Glance

Statute	Rate / Threshold	Due Date	Penalty for Delay
PF	12% + 12% on basic up to ₹15,000 ceiling	ECR by 15th	12% p.a. interest + 5–25% damages (Sec 14B)
ESI	3.25% employer + 0.75% employee, wages ≤ ₹21,000	Return by 15th	12% p.a. interest
TDS	As per slabs + surcharge	Deposit by 7th; 24Q quarterly	1.5%/month interest + ₹200/day late-filing fee
Payment of Wages	—	7th / 10th of next month	Claims + fine up to ₹7,500
Minimum Wages (central)	Central baseline + state overlay	—	Up to 5x under-payment + imprisonment

The Minimum Wages Act sets a federal baseline for scheduled employments, and states are free to notify higher rates per skill category and zone, but can never fall below the central floor. Multi-state payroll teams must track both the central revision cadence and each state’s notification window (typically April and October). Our wages meaning types resource covers the classification rules.

✅ How HROne Collapses These Five Steps Into One Click

HROne auto-assigns UAN and ESIC IP numbers at onboarding process, maps dispensaries by the employee’s declared work location, generates ECR, ESI, and 24Q challans in one click, and alerts the payroll desk 72 hours before every central deadline, so the month-end mechanical work that used to eat four days now runs on a scheduler.

Q3: How Do the Four Labour Codes Effective 21 November 2025 Change Multi-State Payroll, and Which States Have Actually Notified Implementation Rules by April 2026?

The four Labour Codes took effect on 21 November 2025, consolidating 29 central labour laws into the Code on Wages, the Code on Social Security, the Industrial Relations Code, and the Occupational Safety, Health and Working Conditions Code. They mandate that basic wages constitute at least 50% of CTC, extend gratuity to fixed-term employees after one year of service, bring gig and platform workers under social security, and align FFS to a two-working-day settlement clock, forcing every multi-state employer to recompute PF, ESI, gratuity liability, and offer-letter structures.

🛠️ The 5-Step Recomputation Playbook

Steps 1–3: Rebuild Wages, FFS, and Social Security Coverage

1. Audit current CTC against the 50% basic rule. Any salary structure where basic is under half of total gross needs restructuring, and allowances must be capped so basic clears the floor. Recompute employer PF liability on the new basic. For high-CTC employees, this structurally raises your statutory outflow, and gratuity provisioning climbs with it. Use our salary calculator to re-model CTC bands.
2. Reconfigure FFS clocks and offer templates. Every offer letter issued post 21 November 2025 must reflect the two-working-day settlement window, and the HRMS FFS workflow has to compress accordingly. Asset recovery, final payout, and knowledge-transfer checklists run in parallel, not sequentially.
3. Onboard FTEs and gig/platform workers into the Social Security Code schemes. Fixed-term employees with ≥ 1 year of service now qualify for gratuity on a pro-rata basis, and platform workers must be registered under the notified social-security fund via PAN-linked records.

Steps 4–5: Update Registers and OSH/IR Disclosures

4. Update payslips, Form 16, statutory registers, and the employee master to the new wage definition, referencing the MoLE March 2026 FAQs as the authoritative interpretive reference for borderline allowance treatment.
5. Align OSH and IR Code disclosures, including grievance redressal committees for establishments with 20+ workers, working-hour logs capped per state’s daily/weekly limits, and standing orders for industrial establishments.

Our navigating labor laws explainer covers the transition plan in depth.

🗺️ Labour Codes State-Notification Tracker, As of April 2026

State-level implementation rules are notified independently, and as of April 2026, coverage is uneven. Multi-state employers need to track each state separately, because an unnotified rule-set means the old state labour laws still run in parallel.

State	Code on Wages	Social Security Code	IR Code	OSH Code
Maharashtra	Notified	Notified	Draft	Draft
Karnataka	Notified	Notified	Notified	Draft
Tamil Nadu	Notified	Draft	Draft	Draft
Gujarat	Notified	Notified	Notified	Notified
Telangana	Notified	Notified	Draft	Draft
Delhi	Notified	Notified	Draft	Pending
Uttar Pradesh	Notified	Notified	Notified	Notified
West Bengal	Draft	Draft	Pending	Pending
Haryana	Notified	Notified	Notified	Draft
Kerala	Notified	Draft	Draft	Pending

Verify current status against MoLE and the respective state labour department portal before every payroll run. The tracker moves month-to-month.

💡 How HROne’s Policy Engine Absorbs the Codes

HROne’s front-end Policy Engine lets HR reconfigure CTC structures, FFS timelines, and PF/gratuity rules per legal entity without raising a developer ticket. The Labour Codes state-notification tracker sits inside the compliance module and flags states where implementation rules remain pending, so you don’t accidentally apply a new-code rule in a state that’s still running old statutes. Explore the broader core HCM capabilities that drive these workflows.

Q4: Which States Levy Professional Tax in 2026, Complete 28-State + UT Slab Matrix, PTRC vs. PTEC Registration Walkthrough, and the ‘No-PT’ State List?

Fourteen states and UTs levy Professional Tax in 2026: Maharashtra, Karnataka, West Bengal, Tamil Nadu, Telangana, Andhra Pradesh, Kerala, Gujarat, Madhya Pradesh, Odisha, Assam, Meghalaya, Sikkim, and Puducherry, all capped at ₹2,500 per annum under Article 276. Delhi, Uttar Pradesh, Haryana, Rajasthan, Punjab, and most of the North-East (except Assam, Meghalaya, and Sikkim) do not levy PT at all. For historical slab context, see our professional tax slab rates reference.

📊 State-by-State PT Slab & Filing Matrix

State	Monthly Slab Peak	Filing Frequency	Due Date	Late Interest
Maharashtra	₹200/month (₹300 in Feb)	Monthly	Last day of next month	1.25%/month + penalty
Karnataka	₹200/month	Monthly	20th of next month	1.25%/month
West Bengal	₹200/month	Monthly	21st of next month	1%/month
Tamil Nadu	₹1,250/half-year	Half-yearly	30 Sep / 31 Mar	2%/month
Telangana	₹200/month	Monthly	10th of next month	1.25%/month
Andhra Pradesh	₹200/month	Monthly	10th of next month	1.25%/month
Kerala	₹1,250/half-year	Half-yearly	31 Aug / 28 Feb	1%/month
Gujarat	₹200/month	Monthly	15th of next month	18% p.a.
Madhya Pradesh	₹208/month (₹212 in Feb)	Monthly	10th of next month	2%/month
Odisha	₹200/month	Monthly	Last day of next month	2%/month
Assam	₹208/month	Monthly	28th of next month	2%/month
Meghalaya	₹208/month	Monthly	28th of next month	2%/month
Sikkim	₹200/month	Monthly	Quarterly filing	2%/month
Puducherry	₹1,250/half-year	Half-yearly	30 Jun / 31 Dec	1%/month

No-PT states & UTs: Delhi, Uttar Pradesh, Haryana, Rajasthan, Punjab, Himachal Pradesh, Uttarakhand, Bihar, Jharkhand, Chhattisgarh, Goa, Jammu & Kashmir, Ladakh, Arunachal Pradesh, Mizoram, Nagaland, Manipur, Tripura, Chandigarh, Dadra & Nagar Haveli, Daman & Diu, Lakshadweep, Andaman & Nicobar.

🗺️ The Remote-Worker Rule Nobody Explains Clearly

Picture an India map where the 14 levying states are shaded green and the rest grey. The operational rule is simple but constantly broken. PT liability attaches to the employee’s actual work location, not the employer’s registered office. A Mumbai-based company with a remote engineer in Bengaluru owes Karnataka PT, not Maharashtra PT, and needs a Karnataka PTRC to deposit it. A Noida head-office with a sales lead operating from Kolkata triggers a West Bengal PTRC obligation. Our payroll remote hybrid teams guide covers the propagation logic.

🗂️ PTRC vs. PTEC: The Two Registrations You Need

Both are often confused, and getting the distinction wrong is the fastest way to miss a filing window.

• PTEC (Professional Tax Enrolment Certificate), for the establishment/employer itself. Every company pays PT on its own registration (usually ₹2,500/year flat) in every levying state where it has a place of business. Obtained via the state commercial tax portal; TAT 5–15 working days; documents include PAN, incorporation certificate, address proof, and authorised signatory KYC.
• PTRC (Professional Tax Registration Certificate), authorises the employer to deduct and deposit PT from employee salaries. Required in every state where you employ at least one person, including remote staff. Monthly or half-yearly returns are filed against the PTRC.

A 300-employee firm with presence in Maharashtra, Karnataka, Tamil Nadu, and West Bengal needs 4 PTECs and 4 PTRCs: eight separate registrations, eight portals, eight credentials, and eight filing cadences.

✅ How HROne Handles the PT Chaos

HROne maintains live PT slabs for all 14 levying states, auto-switches the correct deduction the moment an employee’s work-state is changed in Super Inbox, generates state-portal-ready returns in the filing format each commercial tax department expects, and flags missing PTRC or PTEC registrations before the first payroll in a new state runs. No spreadsheet. No cross-reference grid. Just a work-state and a run. Book a demo to see the multi-state engine live, or review flat-PEPM pricing.

Q5: What Does the 2026 State-Wise Labour Welfare Fund (LWF) Matrix Look Like, Rates, Frequency, Due Dates, and Registration Process?

The Labour Welfare Fund is a state-administered welfare contribution levied in roughly 16 Indian states in 2026 (Maharashtra, Karnataka, Tamil Nadu, Kerala, West Bengal, Gujarat, Madhya Pradesh, Haryana, Delhi, Punjab, Andhra Pradesh, Telangana, Chhattisgarh, Odisha, Goa, and Chandigarh), with combined employer and employee contributions ranging from ₹6 to ₹200 per employee per cycle, paid half-yearly (June/December) or annually depending on state. Our statutory compliance payroll guide contextualises where LWF sits within the wider compliance stack.

📊 State-Wise LWF Rate, Frequency and Due-Date Matrix

State	Employee (₹)	Employer (₹)	Frequency	Due Date	Late Interest
Maharashtra	25	75	Half-yearly	30 Jun / 31 Dec	12% p.a.
Karnataka	20	40	Annual	15 January	12% p.a.
Tamil Nadu	20	40	Annual	31 January	12% p.a.
Kerala	45 (worker)	45 (+ employer LWF)	Monthly	5th of next month	12% p.a.
West Bengal	3	15	Half-yearly	15 Jul / 15 Jan	12% p.a.
Gujarat	6	12	Half-yearly	31 Jul / 31 Jan	12% p.a.
Madhya Pradesh	10	30	Half-yearly	15 Jul / 15 Jan	12% p.a.
Haryana	31	62	Monthly	23rd of next month	12% p.a.
Delhi	0.75	2.25	Half-yearly	15 Jul / 15 Jan	12% p.a.
Punjab	5	20	Monthly	15th of next month	12% p.a.
Andhra Pradesh	30	70	Annual	31 January	12% p.a.
Telangana	2	5	Annual	31 January	12% p.a.
Chhattisgarh	15	45	Half-yearly	15 Jul / 15 Jan	12% p.a.
Odisha	20	40	Half-yearly	15 Jul / 15 Jan	12% p.a.
Goa	60	180	Half-yearly	30 Jun / 31 Dec	12% p.a.
Chandigarh	5	20	Monthly	15th of next month	12% p.a.

Verify the rate on the respective State Labour Welfare Board portal before each cycle. States revise slabs without uniform notice.

🛠️ Registration and Filing Workflow

The process has three mechanical steps that every multi-state employer must repeat per state:

1. Register with the state’s Labour Welfare Board within 30 days of crossing the applicability threshold (usually 5, 10, or 20 employees depending on the state). Submit PAN, incorporation certificate, address proof, and establishment details, and obtain the LWF registration number per state.
2. Set up the accrual cycle in payroll software per the frequency, whether monthly, half-yearly, or annual. Accruals should sit in a liability register so the year-end provisioning reconciles with actual deposits.
3. Generate the challan, deposit through the state portal (most states now offer online deposit, and a few still run physical filings), and preserve the acknowledgment with the challan number in the digital compliance repository.

⚠️ The Failure Modes That Trip Up Almost Every Payroll Team

• Missed December cycle in Maharashtra. The 31 December window closes mid-holiday season, and the 30 June cycle often slips when the Payroll Manager is on leave.
• Tamil Nadu annual deposit slippage. The 31 January deadline collides with year-end audit prep, and teams accrue but forget to deposit.
• Karnataka 15 January window overlooked in year-end closure rush.
• Haryana and Punjab monthly cycles treated as quarterly by payroll ops copying the Maharashtra cadence.

Each default attracts 12% p.a. interest plus prosecution under the respective state Welfare Fund Acts, and labour officers increasingly issue show-cause notices for first-time misses. Our payroll audit checklist includes an LWF-readiness section you can paste into your quarterly review.

✅ How HROne Eliminates the Twice-a-Year Scramble

HROne auto-accrues LWF per each state’s cycle, notifies payroll ops 15 days before every deposit window inside the HR inbox, generates state-specific challans in the exact portal-ready format, and preserves acknowledgments in the compliance document vault, so the twice-a-year scramble that causes most LWF defaults stops being a calendar-management problem and becomes a system-managed workflow.

Q6: How Do Shops & Establishments, Minimum Wages (Skill & Zone Classification), Leave, Holiday, Bonus, and Gratuity Rules Differ State-by-State?

Shops and Establishments registration is mandatory within 30 days of commencing operations per state, minimum wages are notified bi-annually (April/October) across unskilled, semi-skilled, skilled, and highly skilled categories and geographic zones, state leave and holiday quotas range from 12 to 21 days annually, and the Payment of Bonus and Payment of Gratuity Acts operate as central statutes with state-specific procedural overlays.

🏪 Shops & Establishments, State Comparison

State	Registration Cost (approx.)	Validity	Daily/Weekly Working-Hour Cap	Renewal
Maharashtra	₹2,000 to ₹12,000 (slab-based)	1 to 10 years	9 hrs/day, 48 hrs/week	Online via MAITRI
Karnataka	₹300 to ₹10,000 (slab-based)	5 years	9 hrs/day, 48 hrs/week	e-Karmika portal
Delhi	₹375 to ₹6,000 (slab-based)	Lifetime (one-time)	9 hrs/day, 48 hrs/week	No renewal
Tamil Nadu	₹50 to ₹50,000 (employee-slab)	Annual	8 hrs/day, 48 hrs/week	Every December
Telangana	₹100 to ₹7,000 (slab-based)	Lifetime	8 hrs/day, 48 hrs/week	No renewal
Gujarat	₹100 to ₹25,000 (slab-based)	3 years	9 hrs/day, 48 hrs/week	Every 3 years

Penalties for non-registration and non-renewal typically range from ₹1,000 to ₹25,000 per day of default, plus prosecution for repeat breaches.

💰 Minimum Wages, Skill & Zone Logic

Every state classifies scheduled employments into four skill tiers (unskilled through highly skilled) and two-to-three geographic zones (typically metro, tier-2, and rural). A Karnataka skilled operator in Zone A (Bengaluru) earns a different floor from a Zone C (rural) counterpart, and both rise each April and October by VDA (variable dearness allowance) notification. Our wages meaning types reference covers classification logic in depth.

📋 The Operational Drill for Every Multi-State Payroll Team

1. Map each employee to a state plus skill band plus zone at onboarding process, and lock the mapping in the employee master.
2. Subscribe to each state’s labour department notification feed so VDA revisions are ingested within 72 hours of publication.
3. Re-run payroll for affected skill bands from the notification’s effective date, and back-pay arrears in the next cycle if the notification is retrospective.
4. Maintain the skill-band audit trail, including job description, certification, and supervisor attestation, because labour inspectors challenge classification first.

📅 Leave, Holiday, Bonus & Gratuity, The State Overlay

Dimension	Central Baseline	Common State Overlays
Earned Leave	1 per 20 worked days (central minimum)	Kerala 30/year, Karnataka 21, Maharashtra 21, and Tamil Nadu 12
Casual + Sick Leave	Per Shops Act	Typically 12 CL + 12 SL (varies)
National + State Holidays	3 national mandatory	State gazette, typically 10 to 18 more
Bonus (Payment of Bonus Act)	Wages ≤ ₹21,000, min 8.33% and max 20%	State notification for establishments below threshold
Gratuity (Payment of Gratuity Act + SS Code)	15 days × last drawn wage × years (≥ 5 yrs, FTE ≥ 1 yr under SS Code)	Industry-specific notifications in Maharashtra and Gujarat

The Payment of Gratuity Act was materially expanded by the Social Security Code (effective 21 November 2025). Fixed-term employees now qualify after 1 year of service on a pro-rata basis, which changes the year-end provisioning exercise for every multi-state manufacturer with FTE contracts. Use our gratuity calculator to model the revised liability.

✅ How HROne Handles the State Operational Layer

HROne’s leave management and Time Office modules enforce per-state working-hour and weekly-off caps, the Payroll Engine ingests minimum-wage notifications and auto-adjusts salaries by skill band and zone, and the state policy library maintains leave, holiday, bonus, and gratuity rules as configurable bundles. HR reconfigures a state’s policy without raising a developer ticket, and VDA notifications flow through as version-controlled updates rather than emergency Excel patches.

Q7: How Should You Run Payroll for Remote, Hybrid, Contractor, and Gig Workers Working Across Indian States?

For remote, hybrid, contractor, and gig workers, Indian statutory rules attach to the employee’s actual work location, not the employer’s registered office. The 2025 Social Security Code additionally brings gig and platform workers into the PF and ESIC ambit, making monthly work-state declarations and a documented work-location audit trail non-negotiable for every multi-state employer in 2026. Our payroll remote hybrid teams guide covers the mechanics in detail.

⚠️ The Reality Post-2020: Distributed by Default, Undocumented by Habit

Post-2020, 15 to 30% of most mid-market Indian workforces sit in tier-2 cities and home states that the HR master was never designed to track. Contractor payrolls flow through staffing vendors who invoice at HQ rates with zero state-level visibility. Gig workers were historically invisible to PF and ESIC. Through all of this, the HRMS payroll engine still hardcodes the HQ state, because nobody told the system that the Bengaluru “remote” engineer is actually a Karnataka PT liability.

❌ Why the Current HRMS Playbook Fails Distributed Teams

The default Indian HRMS approach is to treat work location as a static HR master field, not a live payroll input. Keka, greytHR, and Zoho People let HR tag a work location, but the payroll engine rarely auto-switches PT slabs, LWF cycles, or minimum-wage zones when an employee relocates. Contractor payrolls sit outside the HRMS entirely, processed by staffing vendors who bill at a flat header rate. Gig compliance is still treated as optional despite the Social Security Code mandate. The compliance team discovers gaps only at assessment, by which point under-deposits span 12 to 18 months across three or four states. Compare architectures side-by-side on HROne vs Keka and HROne vs greytHR.

“System implementation experience was horrible, in 6 months the implementation was barely completed to 40%. Support is never on time. Replies to emails get delayed by days if not weeks. No ownership at any level of the organization.”

— Sanmeet S., Reviewer ZingHR – G2 Verified Review

✅ The Strategic Shift: Work Location as a Live Payroll Trigger

Work location is not an HR field. It’s a payroll rule trigger. The architectural shift is to refresh each employee’s work state monthly via self-declaration and manager attestation, so the payroll engine computes PT, LWF, Shops Act, and minimum-wage obligations state-by-state without manual reconciliation. Contractor payrolls must flow through the same state rule engine. A contractor invoiced at a Bengaluru rate should carry Karnataka PT if the contractor physically works from Bengaluru. Gig and platform workers must be onboarded into the Social Security Code schemes with PAN-linked records, regardless of whether they’re classified as “employees” in the traditional sense.

💡 How HROne Runs This Natively

We built the work-location declaration directly into the Super Inbox. Every employee confirms their work state on the 1st of each month in three clicks, and manager attestation routes automatically via the mobile HR app. The declaration propagates into the payroll rule engine, auto-switches the PT/LWF/minimum-wage bundle for the upcoming run, and generates the audit trail labour inspectors expect. Contractor payroll flows through the same state logic when staffing vendors are onboarded as partners in the platform. Gig and platform workers onboard into PF and ESIC through a single-click Social Security Code workflow with PAN and UAN linkage.

The MRDIY case study documents how the company cut its payroll cycle from 10 days to 5 to 6 days across distributed manufacturing and retail teams after consolidating on this architecture, and 1,500+ brands now run multi-state distributed payroll on the same Super Inbox pattern.

“The InboxforHR is a game-changer, centralizing every HR task into one simple inbox, cutting down administrative time by 60 to 70% and preventing tasks from falling through the cracks.”

— Waldon S., Reviewer HROne G2 – Verified Review

“Mobile mark attendance is great for employees who work from remote locations. Salary processing to the last creation of bank challan files is a quick and systematic process with error-free details.”

— Deepak K., Reviewer HROne G2 – Verified Review

Q8: What Is the 3-Layer Multi-State Payroll Operating Model, Central Core, State Logic, and Location Detection?

The 3-Layer Multi-State Payroll Operating Model separates payroll compliance into a Central Core Layer (PF, ESI, TDS, Labour Codes), a State Logic Layer (PT, LWF, Shops Act, minimum wages, leave, and bonus), and a Location Detection Layer (work-state per employee refreshed monthly), so each layer is independently auditable, and a rule change in one layer doesn’t destabilise the others.

🏛️ Layer 1: The Central Core, Uniform National Rules

One engine runs the national statutes, including PF ECR, ESI returns, TDS Form 24Q, and the four Labour Codes’ wage-structure enforcement. Every legal entity inherits the same central logic, so CTC templates, statutory registers, and payslip formats stay consistent across the group. Central rules change infrequently (a budget-linked threshold revision, a Labour Code FAQ update), and when they do, the change propagates once and flows down to every entity and every state automatically. Review the underlying core HCM layer that powers this propagation.

Diagram callout: visualise a three-layer stacked architecture, with the Central Core as the base slab, the State Logic as the middle tier with 28+ configurable state blocks, and the Location Detection as the top layer routing each employee to the right state block monthly.

🗺️ Layer 2: The State Logic, One Policy Bundle Per State

This is where most stitched payroll stacks collapse. Each Indian state is a configurable policy bundle, including PT slab structure, LWF cycle, Shops Act working-hour cap, minimum wage notification (skill × zone), leave quota, state-holiday list, and bonus threshold. Policy changes in one state, for example a Karnataka VDA revision in October, a Maharashtra LWF slab update, or a Tamil Nadu working-hour amendment, roll forward as version-controlled updates to that specific state block without touching Maharashtra, Gujarat, or Delhi.

The operating principle is that HR Ops configures the state block via the front-end policy engine, not via developer tickets. A Tamil Nadu minimum-wage notification published on 1 October becomes a live payroll input by 3 October: edited in the state block, tested on the staging ledger, and promoted to production. Legacy ERPs and over-engineered global suites force a developer cycle for the same change. A stitched Excel, biometric, and outsourced vendor stack doesn’t even register the notification until the labour officer sends a notice. Our payroll automation complete guide expands on this operating principle.

📍 Layer 3: The Location Detection Layer, The Layer Everyone Forgets

The Location Detection Layer is the monthly work-state declaration captured per employee and propagated to both the Central Core (for dispensary mapping and TDS jurisdiction) and the State Logic Layer (for PT, LWF, and minimum wage) before each payroll run. Without this layer, relocations and hybrid schedules silently break compliance. The engineer who moved from Pune to Bengaluru in April is still having Maharashtra PT deducted in October, and the labour officer finds out before the CFO does.

The comparison anchor is blunt: stitched Excel, biometric, and outsourced vendor stacks collapse Layer 3 into an afterthought handled by spreadsheets. HROne treats it as first-class architecture. Our multi-location workforce management guide covers the declaration-to-propagation flow end-to-end.

✅ How HROne Instantiates the 3-Layer Model

HROne is architected natively around the 3-layer model. The payroll solution executes the Central Core, HRV Studio extends and configures the State Logic Layer without developer dependency, and the Super Inbox operates the Location Detection Layer through monthly declarations and manager attestations. Every module connects, every rule change is version-controlled, and every payroll run produces one consolidated statutory register per legal entity. Asia Healthcare Holdings runs 20 pan-India units on this architecture on a single instance, with unified employee master and entity-independent compliance. That is the operational proof that the 3-layer model scales beyond PowerPoint. To see it live, book a demo.

Q9: What Does the Consolidated 2026 Multi-State Compliance Calendar, State-Wise Penalty Heatmap, and Top-10 Mistakes Matrix Look Like?

The 2026 multi-state compliance calendar clusters monthly deadlines (TDS 7th, PF ECR 15th, ESI 15th, and state PT 10th to 31st), two half-yearly LWF windows (June and December), and two annual wage-revision events (April and October), with penalties ranging from 12% p.a. PF interest plus 5 to 25% Section 14B damages, to state PT interest of 1.25%/month, and LWF prosecution under respective Welfare Fund Acts. Our payroll best practices guide pairs well with this calendar.

📅 The 12-Month Consolidated Multi-State Filing Calendar

Month	Central (TDS/PF/ESI)	State PT	State LWF	Other
Jan	TDS 7, PF ECR 15, ESI 15, 24Q Q3 31	MH/KA/TG/AP/GJ monthly 10 to 31	KA (15), TN (31), AP (31), and TG (31) annual	Shops Act renewals (TN)
Feb	TDS 7, PF 15, ESI 15	Monthly PT	Kerala half-year (28)
Mar	TDS 7, PF 15, ESI 15	Monthly PT, Puducherry half-year		FY close
Apr	TDS 7, PF 15, ESI 15, 24Q Q4 31	Monthly PT		Min wage revision window
May	TDS 7, PF 15, ESI 15	Monthly PT
Jun	TDS 7, PF 15, ESI 15	Monthly PT, Puducherry half-year (30)	MH/Goa (30) half-year
Jul	TDS 7, PF 15, ESI 15, 24Q Q1 31	Monthly PT, WB (21)	WB, MP, Odisha, CG, Delhi, and GJ half-year (15 to 31)
Aug	TDS 7, PF 15, ESI 15	Monthly PT, Kerala half-year (31)
Sep	TDS 7, PF 15, ESI 15	Monthly PT, TN half-year (30)
Oct	TDS 7, PF 15, ESI 15, 24Q Q2 31	Monthly PT		Min wage revision window
Nov	TDS 7, PF 15, ESI 15	Monthly PT
Dec	TDS 7, PF 15, ESI 15	Monthly PT	MH/Goa (31) half-year	FY provisioning

⚠️ State-Wise Penalty Heatmap

State	PT Interest	PT Penalty Cap	LWF Default	Shops Act Fine
Maharashtra	1.25%/month	₹300 + 10% penalty	12% p.a. + prosecution	₹1,000 to ₹10,000/day
Karnataka	1.25%/month	Up to 50% of due	12% p.a.	₹5,000 to ₹10,000
Tamil Nadu	2%/month	₹5,000 cap	12% p.a. + prosecution	₹25,000
Telangana	1.25%/month	25% of due	12% p.a.	₹5,000
Gujarat	18% p.a.	25% of due	12% p.a.	₹10,000
West Bengal	1%/month	Up to ₹5,000	12% p.a.	₹5,000
Kerala	1%/month	Up to 100% of due	12% p.a. + prosecution	₹10,000

❌ Top 10 Multi-State Payroll Mistakes + Audit Readiness

The ten mistakes that trigger almost every labour-officer notice I’ve seen:

1. HQ-hardcoded PT for remote employees.
2. Missed December LWF in Maharashtra, Goa, and MP.
3. Skill-band misclassification under minimum wages.
4. Shops Act non-renewal in annual-validity states (Tamil Nadu).
5. Remote worker unmapped to ESIC dispensary.
6. PTRC/PTEC missing in a new state.
7. Under-50% basic wage CTC structures post-Labour Codes.
8. FTE gratuity skipped for 1 to 4 year employees.
9. Gig workers unregistered under the Social Security Code.
10. Form 24Q location mismatch on inter-state transfers.

✅ Audit Readiness Checklist

• PF/ESI challans + ECR acknowledgments (last 7 years).
• State PT returns + portal acknowledgments per PTRC.
• LWF challans per state cycle.
• Shops Act certificates + renewal history.
• Minimum wage notifications applied (dated trail).
• Labour Codes wage-restructuring audit log.
• Work-state declarations (monthly attestation trail).

Run a unified statutory audit once a quarter where PF, ESI, PT, and LWF are cross-verified against the same headcount baseline, and store every artefact in a single digital compliance repository indexed by state, statute, month, and challan number. Our payroll audit checklist maps exactly to this cadence.

💰 How HROne Consolidates the Calendar, Penalty, and Audit Load

HROne’s unified compliance calendar consolidates every state’s due dates into one HR inbox view, generates challans on-demand, tracks filing status by legal entity, and maintains a PTRC/PTEC/challan/acknowledgment vault, converting the spreadsheet tracker most payroll managers keep into a board-reportable compliance score.

Q10: What Does Multi-State Payroll Actually Cost a 500-Employee Indian Manufacturer Across 4 States, A Worked Example with Statutory Stack and Penalty Exposure?

A 500-employee manufacturer running plants across four Indian states in 2026 carries 20+ statutory registrations, 60+ annual filings, and a statutory cost of 8 to 14% of gross wages, and on most months, 30 to 40% of HR Ops bandwidth is consumed reconciling biometric exports, PT deductions, and LWF cycles that the stack was never built to automate. See how purpose-built manufacturing HR compresses that overhead.

⏰ The Relatable Reality: 25th of the Month, 4 Fires, Zero Visibility

It’s the 25th. Payroll closes on the 28th. Your Maharashtra plant’s biometric file hasn’t reconciled with the leave module because the time-office export has a 4-hour lag. Your Chennai HR lead just flagged that the new Tamil Nadu minimum-wage notification kicks in from this payroll run, and the skilled-operator band is now 7% higher. Your Bengaluru unit has five new joiners whose PTEC isn’t active yet, because the commercial tax portal held up verification. Your Surat factory missed the Gujarat LWF December deposit, and the labour officer emailed yesterday asking for a response within 7 days. You’re toggling across four parallel Excel trackers, and the CFO just pinged asking for the consolidated statutory liability across the group before the board meeting on Friday.

❌ Why This Problem Exists

Because your payroll stack is a biometric tool, plus an outsourced payroll vendor, plus four Excel sheets, plus WhatsApp approvals, and none of them can see the full multi-state picture or auto-switch rules when an employee transfers from Pune to Chennai. The outsourced vendor works from your header sheet, and the header sheet is only as current as the last email to your payroll lead. Compare this with a consolidated payroll outsourcing alternative that runs on the same tenant.

💸 The Hidden Costs Nobody Puts on a Slide

• 10-day payroll cycle (industry median for fragmented stacks), with 3 to 4 days spent on reconciliation alone.
• ₹18 to 25 lakh annual under-deduction risk from PT misapplication, LWF cycle misses, and minimum-wage lag.
• 8 to 10 hours/month of manager time burned on attendance and expense reconciliation.
• Expense-related leakage of 2 to 4% of reimbursement volume through manual receipts.
• Zero board-ready HR-tech ROI number. The CHRO walks into the review without a ballpark.

Case study inset, SaaS Co., 6 states, pre vs. post HROne: payroll cycle compressed from 9 days to 5, payslip error rate from 3.8% to 0.4%, and compliance score from a hand-computed 72% to an auto-tracked 96%. Our ROI calculator turns these deltas into a CFO-ready number.

✅ How It Should Work, And How HROne Gets It There

One instance running Core HR, Time Office, and Payroll for all four states. Auto state-switching when an employee transfers. A consolidated filing calendar that shows Maharashtra LWF, Tamil Nadu minimum wage, Karnataka PTEC, and Gujarat LWF in one view. Three-click Super Inbox closures. And India’s first inbuilt ROI Dashboard showing lifetime hours saved against average HR salary, so the CFO gets the ballpark figure before asking.

Asia Healthcare Holdings runs 20 pan-India units on one HROne instance with unified employee master and entity-independent compliance. The MRDIY case study documents the same pattern at retail-manufacturing scale. A labour lawyer I spoke to recently put it plainly: “the labour officers don’t assume malice, they assume disorganisation, and the disorganised employer pays for both.” A manufacturing CHRO I work with reframed it: “we stopped asking how many vendors we have, and started asking how many systems the CFO has to trust to close the books.”

“Salary processing along with exact calculation of LWF and PT slabs makes the work a more convenient process.”

— Komal S., Reviewer HROne G2 – Verified Review

“HRone helping us streamline multiple processes by bringing everything onto a single platform. This has significantly reduced manual efforts, minimized errors, and improved compliance.”

— Bindu P., Reviewer HROne G2 – Verified Review

Q11: How Should You Choose Your Multi-State Payroll Operating Model, In-House Team, HRMS Rule Engine, or Outsourced Partner, and What Are the 25 Questions to Ask Before You Sign?

Choose a multi-state payroll operating model based on legal-entity count, number of states with employees, and whether you can enforce one source of truth for the employee master, not on peer-group habit. Above 200 employees across 3+ states, a single-instance HRMS rule engine out-performs in-house teams, state hubs, and outsourced partners on cost, control, and compliance. Our how to choose payroll software guide breaks this decision down step-by-step.

⚠️ The Decision Dilemma, and the Wrong Shortcuts Most Buyers Take

Picking a multi-state payroll model locks in the architecture your group will operate on for 5+ years. Pick wrong, and you’re running three parallel deployments, reconciling employee master data in Excel, and paying entity-wise subscription premiums while the CFO still can’t see consolidated statutory liability.

Most buyers take three shortcuts: picking by brand (Darwinbox because a peer uses it), by lowest PEPM (greytHR for 500 heads), or by inertia (sticking with the outsourced vendor that’s been invoicing for 8 years). All three ignore whether the platform can actually run multi-state rule switching, independent entity-level compliance, and unified RBAC in one tenant. Compare side-by-side on HROne vs Darwinbox and HROne vs greytHR.

✅ The Right Evaluation Framework, 7 Architectural Criteria

1. Multi-state rule engine: does it auto-switch PT/LWF/minimum-wage bundles by work location?
2. Multi-entity scalability: unlimited legal entities in one tenant?
3. Statutory isolation: are PF/ESI/PT independently auditable per entity?
4. Remote-workforce support: is monthly work-location declaration captured and propagated?
5. Unified compliance calendar: every state’s due dates on one dashboard?
6. Front-end policy engine: can HR add a new state without vendor implementation?
7. Billing transparency: go-live billing with no per-entity charges?

📋 The 25-Question Vendor Checklist (Condensed)

• Implementation timeline and go-live SLA? Day-one vs. go-live billing?
• PTRC/PTEC multi-registration support? LWF cycle alerts per state?
• Labour Codes wage-restructuring workflow? FTE gratuity logic?
• RBAC/SSO/SAML out of the box? ERP/BGV/LMS marketplace integrations?
• Lock-in length? Renewal price-hike cap? Data-portability clause?
• Sample ROI dashboard? Audit-register auto-generation?
• Named implementation SPOC (HR or tech)? Escalation matrix?
• Mobile offline attendance? Field-force geofencing?
• And 10 more across sandbox access, uptime SLAs, and security certifications.

Our HRIS buyer pitfalls list complements this checklist.

📊 Applying the Framework, Scoring Table

Criterion	HROne	Competing HRMS	In-House Team	Outsourced Partner
Multi-state rule engine	✅	⚠️	❌	⚠️
Multi-entity scalability	✅	⚠️	❌	⚠️
Statutory isolation	✅	⚠️	✅	❌
Remote-workforce support	✅	❌	❌	❌
Unified compliance calendar	✅	⚠️	❌	⚠️
Front-end policy engine	✅	❌	N/A	❌
Billing transparency	✅	❌	N/A	⚠️
Score	7/7	1/7	1/7	0/7

HROne scores 7/7 because the platform was built around multi-legal-entity, multi-state reality. Configure once, scale states without re-implementing.

💰 Meta-Insight + 90-Day Roadmap + Proof

The real question isn’t “which model has the most modules”, it’s “which model lets you add your next state without another implementation project.” HROne’s 90-day rollout is structured as: Weeks 1 to 4 discovery and configuration, Weeks 5 to 8 parallel run, and Weeks 9 to 12 go-live and training. MR DIY India went live in 30 days. HROne ranks #3 on G2 for overall satisfaction versus Keka’s #55, with a 9.8 NPS on dedicated HR SPOC support. Book a book a demo to see the 90-day roadmap against your entity list.

“I love HROne for its cost efficiency and holistic approach, which is why I prefer it over other vendors like Workday. The ability to manage various HR processes from a single platform is incredibly convenient and cost-effective for mid-level and enterprise customers.”

— Priyanka S., Reviewer HROne G2 – Verified Review

“Customer care support is comparatively better… GreytHR is not much good at customizing based on our requirements. Many times we were manually correcting the leave balance of employees. We cannot properly implement our company policies due to the limitations of greytHR.”

— Verified User in IT Services, Greyt HR – G2 Verified Review

Q12: Ready to Consolidate Multi-State Payroll on One Instance? Book Your 30-Minute HROne Walkthrough.

Multi-state payroll breaks in Indian mid-market firms not because the rules are unknowable, but because the payroll stack hardcodes the HQ state for every employee and treats state-specific deductions as a monthly manual correction, and that architecture cannot scale past 3 states without leaking money, goodwill, or both.

✅ What Changes When Everything Runs on One Instance

HROne consolidates central and state compliance for PF, ESI, TDS, PT, LWF, Shops Act, the four Labour Codes, minimum wages, leave, bonus, and gratuity inside one instance. This is the architecture MR DIY India used to cut its payroll cycle from 10 days to 5 to 6 days, and the reason Asia Healthcare Holdings runs 20 pan-India units on a single tenant with unified employee master and entity-independent compliance. Explore the broader payroll solution and core HCM architecture.

❓ Quick FAQ (PAA-Tagged for Schema)

• Which states levy PT in 2026? Fourteen: Maharashtra, Karnataka, West Bengal, Tamil Nadu, Telangana, Andhra Pradesh, Kerala, Gujarat, Madhya Pradesh, Odisha, Assam, Meghalaya, Sikkim, and Puducherry.
• When did the four Labour Codes take effect? 21 November 2025.
• Where does a remote employee’s PT apply? At the employee’s actual work location, not the employer’s registered office.
• What’s the PF ECR due date? The 15th of the following month.
• Do gig and platform workers need ESIC coverage? Yes, under the Social Security Code effective 21 November 2025

Secondary links: View flat pricing, see the ROI Dashboard via our ROI calculator, and explore the payroll software engine.