An employee's home address, assigned branch and payroll processing office can be in three different states. Labour Welfare Fund treatment cannot be settled simply by choosing whichever address is easiest to extract from the payroll master. The employer must establish the relevant employment and establishment connection, then apply each potentially relevant state's law.
There is no single residence-based rule in the state provisions discussed here that can safely replace that assessment. Equally, centralising salary processing at a head office does not establish that the head office state's Fund applies to every employee. Remote-work labels describe an arrangement; they do not resolve statutory coverage by themselves.
A defensible process separates location facts, legal classification and contribution timing. This matters particularly on transfers, where two states can have different reference dates, service conditions and employee exclusions. A payroll change that prevents all possible overlap may also remove a contribution that was properly due for an earlier period.
Build a location map before choosing a state
For each employee, identify the legal employer, contractual establishment, normal actual work location, reporting location, payroll processor and any permanent or temporary assignment. Record the dates on which those facts changed.
The location map should distinguish:
| Fact | Why payroll needs it |
|---|---|
| Home address | Evidence of residence and possibly actual remote work, without deciding liability alone |
| Assigned establishment | Connection to the employer's branch and employment records |
| Actual work site | Whether work occurs regularly in another state or premises |
| Reporting and operational control | Evidence of the arrangement and establishment relationship |
| Payroll processing location | Administrative fact that may differ from the employment location |
| Effective dates | Connection to reference rosters and service periods |
A worker may remain attached to a Maharashtra establishment while temporarily working from a family home elsewhere. Another may have been recruited permanently to work in a new state where the employer has no conventional branch. These are not necessarily the same legal arrangement.
Obtain appointment terms, remote-work approvals, assignment letters, transfer orders, joining reports and establishment records. Ask the employee and manager to confirm actual working arrangements where the HR master is unclear. Do not backfill a convenient branch code without documenting why it represents the facts.
Test establishment coverage independently
A location connection matters only within the relevant statutory framework. Determine whether the employer has an establishment of a covered category, whether employment thresholds and lookbacks apply, and whether a notification or exemption affects it.
Do not use one threshold across Maharashtra, Karnataka, Haryana, Tamil Nadu and Telangana. Each state has its own categories. Factories can be covered through a different limb from shops or ordinary commercial offices. The headcount used to establish coverage is also not necessarily identical to the final contribution population after employee exclusions.
Maharashtra's shops-linked establishment limb uses five persons and a preceding-twelve-month lookback, with continuation and cessation provisions. It also expressly treats different branches or departments as parts of an establishment. That explanation needs to be read with the Act's territorial operation and the actual establishment relationship; it is not authority to merge all state welfare accounts nationwide.
Karnataka amended its general establishment limb in January 2026 from more than fifty persons to ten or more. A workforce map using an old fifty-person test can therefore miss a currently covered Karnataka office. Apply the category and effective period correctly, particularly when reconstructing a transfer that occurred before the amendment.
A remote arrangement creating a disputed new-state establishment connection should be referred for a specific assessment. Do not assume either that one home worker always creates a covered establishment or that no physical branch registration means the state can never be relevant.
Apply the employee definition afresh in each state
An employee's inclusion status can change across states without any change in salary. The definitions differ. Maintain a classification matrix rather than copying an exclusion flag from the old payroll record.
Maharashtra excludes mainly managerial employment, a supervisor meeting its statutory wage or managerial-function condition, and apprentices under the specified apprenticeship law. The supervisory wage amount is ₹3,500; it is not a general salary ceiling for all employees.
Karnataka's employee definition does not reproduce that Maharashtra managerial and supervisory exclusion structure. Do not automatically carry a “manager exempt” flag into Karnataka LWF simply because it was used in Maharashtra. Determine the category using Karnataka's actual definition.
Haryana recognises direct and supplied employment within its definition and has its own establishment test and monthly contribution structure. A transfer should include agency and deployment evidence where relevant, rather than treating the change as only a direct-payroll exercise.
Tamil Nadu has a thirty-day service condition and its own managerial, supervisory, apprentice and part-time treatment. The supervisory wage boundary is ₹15,000 under its amended definition; salary must again be read within the supervisory condition.
Telangana includes a thirty-day service condition during twelve months and excludes mainly managerial employment, supervisors meeting its ₹1,600 wage or managerial-function condition, and the specified apprentice or part-time employment. A non-supervisory employee does not become excluded merely by earning above ₹1,600.
These examples demonstrate why a job title, group grade or common salary ceiling cannot decide every state's population. Retain actual duties, relevant wages and engagement evidence for each exclusion.
Distinguish permanent transfers from temporary assignments
A permanent transfer normally needs an effective-date record, release from the former establishment, joining at the receiving establishment and consistent updates to payroll and employment records. Review the real change in location and responsibility, including any period between release and joining.
A temporary assignment should identify its purpose, duration, continuing attachment, reporting arrangements and expected return. A travel claim or hotel booking may support the chronology, but does not alone determine the legal establishment. Do not change LWF state every time an employee travels for a meeting.
A change of residence without a change in work arrangement should trigger a factual enquiry, not necessarily an automatic statutory switch. Conversely, repeated remote work in another state may require review even if HR never issued a formal transfer. Written labels cannot displace the actual arrangement.
For hybrid employees, document regular working patterns and the establishments involved. Working three days at one branch and two elsewhere cannot be resolved by a universal “majority of days” rule invented for payroll convenience. Establish the applicable legal connection and seek clarification where both states remain materially relevant.
Secondments and employer changes need an additional layer. Determine whether the legal employer changes, who controls and pays the worker, and whose statutory account is involved. An intercompany recharge does not by itself establish the statutory employer.
Compare contribution periods before changing deductions
A state switch is not complete until payroll checks the contribution calendar. The following framework illustrates why a single “active on year-end” rule is unsafe:
| State | Timing issue to examine on transfer |
|---|---|
| Maharashtra | Register position at 30 June and 31 December; half-year contributions |
| Karnataka | Annual contribution population linked to 31 December |
| Haryana | Monthly employee-register and contribution calculation, with the separately prescribed annual remittance requirement |
| Tamil Nadu | Annual exercise includes the December register and specified employees leaving during the year after the qualifying service |
| Telangana | Annual establishment-register framework and service condition, with January payment and statement requirements |
Maharashtra contributions must be paid before 15 July and before 15 January; the Rules' statement timing must also be addressed. Karnataka's annual payment date is 15 January. Tamil Nadu Rule 12 states payment before 31 January of the succeeding year. Telangana Rule 6 provides payment by 31 January with Form F. These differences matter when scheduling the handover.
Haryana's monthly liability should not be confused with an assumption of mandatory monthly remittance. The amended section 9A requires both shares online before 31 December annually. Preserve the month-wise calculation even though payment follows that separate deadline.
Do not treat a payment made after transfer as a contribution for the payment-date location. Identify the original liability period and establishment. The bank transaction date does not replace the roster or service test.
Examine overlaps without promising a universal credit
Consider a worker genuinely attached to a covered Maharashtra establishment on 30 June who permanently joins a covered Karnataka establishment in August and remains there on 31 December. Subject to each state's employee test, Maharashtra's first-half liability and Karnataka's annual liability may both require attention. The employer should not delete the earlier Maharashtra item solely because it wants one state entry for the whole year.
That example does not create a general rule that every interstate transfer requires two payments. Change the facts or dates and the result can change. The purpose is to assess each state's charge independently rather than enforce an artificial one-payment ceiling.
Tamil Nadu creates another important review point. Rule 12 expressly addresses employees discharged, dismissed or resigned during the year after at least thirty days' work. Someone absent from the December payroll is therefore not automatically outside the annual exercise. Where an interstate transfer is recorded as resignation or movement to a different employer, examine the actual legal event and that rule.
For a move into Haryana, examine the relevant monthly register facts and component calculation. For a move into Telangana, examine the annual register and service condition. A group payroll system applying one snapshot date to both can create gaps.
There is no general inter-state credit or refund mechanism established merely because a worker appears in two states' records. Do not net a Maharashtra contribution against Karnataka or Haryana without authority. Resolve genuine duplicates with the relevant Board and retain the adjustment evidence.
Document remote-work nexus questions clearly
Some cases remain uncertain after the ordinary establishment and employee tests. Prepare a short factual memorandum instead of issuing a conclusion from a generic online article.
The memorandum should identify the states in question, legal employer, premises and registrations, actual work location, contractual attachment, supervision, duration, headcounts and contribution periods. Explain the competing classifications and the specific provision needing clarification.
Ask the competent Board or Labour authority a precise question: which establishment account and employee population should reflect this arrangement for the identified period? Include the material facts and request a written response. Where more than one state is involved, do not assume one Board's answer conclusively decides the other's legislation.
Pending resolution, preserve the employee's rights and the employer's calculation records. A provisional internal treatment should be approved, dated and revisited. Do not conceal uncertainty in a permanent payroll code or make an unauthorised recovery solely to hedge a legal risk.
No general official remote-work instruction has been established in this guide that makes either residence or payroll processing the single controlling factor across these five states. The state definitions and facts remain the basis of the analysis. A court decision about another law or a different arrangement should not be presented as a universal LWF answer without examining its actual scope.
Turn the conclusion into an auditable payroll change
Once the treatment is approved, update the effective-dated establishment mapping, inclusion or exclusion reason, contribution schedule and recovery instructions. Retain earlier versions so the employer can explain what was done before and after the change.
Reconcile the old and new payroll runs. Look for duplicate employee recoveries, missing employer funding, an earlier state's deduction that was never remitted, and current-year leavers omitted from an annual roster. Do not refund an already remitted amount simply because the payroll state code later changed; establish the accepted correction route first.
Where a vendor operates payroll, provide the approved facts and legal instruction in writing. Require confirmation of the effective date, calculation and period allocation. The vendor should not choose the state from the bank account branch or a default company setting.
An adviser using assureOffice for related financial and practice work can organise the transfer assessment and reconciliation within the client workflow. assureoffice.in should not be represented as determining territorial nexus or filing multi-state LWF corrections automatically. Preserve actual Board responses, statements and receipts.
Review the mapping at onboarding, residence changes involving actual work, transfers, long assignments, promotions and establishment reorganisations. The closing checklist is factual location map, state-specific establishment test, employee classification, effective date, reference-period review, prior recoveries, outstanding payments, authority clarification and final reconciliation. This keeps a mobile workforce from becoming an unexplained set of payroll exceptions.
Frequently asked questions
1. Does home address alone determine LWF?
No universal rule follows from the state provisions discussed here. Establish the actual work arrangement and connection to the employing establishment, then apply the relevant state's definitions.
2. Can the payroll office's state be used for everyone?
No. Payroll processing is an administrative location. It does not replace the establishment, employee and territorial analysis for workers connected to other states.
3. Does every remote worker create a new covered establishment?
Do not assume so. Examine the actual arrangement, applicable category, threshold and notifications. A one-person home arrangement cannot be classified from the remote-work label alone.
4. Can a remote worker remain attached to an existing branch?
That may be part of the factual arrangement, but the attachment must be genuine and assessed against applicable law. A branch code selected only for convenience is weak evidence.
5. What documents support a permanent transfer?
Keep the transfer order, release and joining dates, revised assignment, establishment records and payroll change. Resolve any interval or conflicting dates before preparing contribution rosters.
6. Should short business travel change the LWF state?
Not automatically. Identify whether the employment attachment changed or the employee merely travelled temporarily. A travel expense record alone does not settle establishment nexus.
7. Is there a universal majority-of-working-days rule for hybrid staff?
No such rule is established here. Assess the relevant state provisions and actual establishment relationship, and obtain a specific clarification for a genuinely divided arrangement.
8. Can an exclusion flag move unchanged between states?
No. Employee definitions differ. Reassess duties, wages, service and engagement status under the receiving state's law rather than copying the old payroll code.
9. What changed in Karnataka's general threshold in 2026?
The January 2026 amendment replaced more than fifty persons with ten or more in the relevant establishment limb. Other categories and historical periods still require their own assessment.
10. Does Maharashtra's branch explanation merge all state Funds?
No such nationwide conclusion should be drawn. Read it with territorial operation and the actual establishment facts; keep each state's account and obligations separately assessed.
11. Does salary above ₹1,600 exclude everyone in Telangana?
No. The wage condition is part of its supervisory exclusion. Non-supervisory staff must not be removed solely because their pay exceeds that amount.
12. Are managers automatically excluded in Karnataka as in Maharashtra?
Do not import Maharashtra's exclusion structure. Read Karnataka's employee definition and assess the actual person under it. A group managerial grade is not a universal exemption.
13. Can two states be relevant in one calendar year?
Yes. Different periods and genuine transfers can make each state's charge relevant on its own facts. This is not necessarily an erroneous duplicate payment.
14. Does leaving Tamil Nadu before December always remove annual liability?
No. Rule 12 includes specified leavers who worked at least thirty days during the year. Examine the actual departure event and the employee test.
15. Does Haryana's monthly calculation mean monthly remittance?
Do not conflate the two. Keep the month-wise liability, while the amended section 9A specifies online payment of both shares before 31 December annually.
16. Can one state's contribution be credited against another automatically?
No general automatic credit is established. Seek the relevant Board's accepted adjustment or refund process for an actual error and retain evidence of its decision.
17. What if salary is paid after the transfer date?
Identify the liability period and establishment to which the amount relates. The payment date alone does not move a historic contribution to the new state.
18. Who should resolve an uncertain territorial connection?
Prepare the facts for the competent Board or Labour authority, with legal advice where necessary. One state's response should not be assumed to decide another state's law automatically.
19. What should a payroll vendor receive?
An approved, effective-dated state and establishment mapping, classification and contribution instruction. Require a reconciliation of both old and new runs so prior deductions and employer shares remain traceable.
20. How should the employer maintain the conclusion?
Keep the factual memorandum, legal basis, authority response, payroll versions and matched contribution evidence. assureOffice may support related work organisation; it does not replace the nexus assessment or government acknowledgement.