Labour Welfare Fund: A State-Wise Employer Guide

The Labour Welfare Fund is one of those statutory deductions that looks trivial on a payslip and turns into a genuine headache the moment your company hires in a second state. The amounts are small — often the smallest line item in the whole salary structure — but the compliance surface is wide, the rules are set state by state rather than nationally, and the deduction cycles refuse to line up with a normal monthly payroll calendar. Plenty of otherwise well-run payroll teams discover an LWF gap only when a labour inspector, a due-diligence checklist, or an acquirer's compliance auditor goes looking for it.

This guide is written for HR managers, founders, finance leads and payroll teams operating in India. It explains what the Labour Welfare Fund is, why it exists, how to work out whether it applies to your establishment, how contributions are structured, how the half-yearly and annual cycles break payroll automation, and how to build a state-wise applicability matrix you can actually maintain.

One important caveat before we begin, and we will repeat it throughout: this article deliberately avoids quoting specific rupee contribution amounts, exact wage ceilings, or precise due dates for any state. Those figures are revised periodically by individual State Labour Welfare Boards, sometimes with little publicity, and a blog post is the wrong place to source them. Always confirm current rates, ceilings, thresholds and deadlines directly on the relevant State Labour Welfare Board website or with your labour law consultant before you configure payroll. What this guide gives you is the structure, the decision logic and the operating process — the parts that stay stable.

What Is the Labour Welfare Fund?

The Labour Welfare Fund (commonly abbreviated LWF) is a statutory fund created by a State government to finance welfare activities for workers and their families in that State. It is funded primarily through small periodic contributions collected from employees and employers in covered establishments, and in several States the government adds its own share on top.

The fund is administered by a State Labour Welfare Board — a statutory body constituted under the relevant State Act, usually with representation from government, employers and trade unions. The Board decides how the pooled money is spent within the boundaries set by the Act.

Two ideas define LWF and explain almost every complication that follows:

1. It is a welfare levy, not a savings scheme. Unlike Provident Fund, where the money sits in an identifiable account belonging to the employee, LWF contributions go into a common pool. An employee cannot withdraw "their" LWF balance. There is no individual account, no statement, no maturity, no transfer on job change. It is closer in spirit to a small earmarked tax than to a retirement benefit.

1. It is a State subject. Labour welfare falls in the domain where States legislate their own Acts. There is no single central Labour Welfare Fund Act covering all of India. Each participating State (and a few Union Territories) has enacted its own statute, with its own name, its own coverage rules, its own contribution structure, its own frequency, its own return formats and its own penalties.

Everything painful about LWF administration flows from point two.

What the Money Is Actually Used For

State Labour Welfare Boards typically deploy the fund toward welfare measures that sit outside an employer's normal obligations. The specific menu varies by State and by what the Board has chosen to prioritise in a given period, but the recurring categories include:

• Educational assistance and scholarships for workers' children
• Medical assistance, health camps and reimbursement schemes
• Housing and housing loan support in some States
• Recreation, sports, cultural activities and community centres
• Vocational training and skill development
• Assistance in cases of accident, disability or death of a worker
• Maternity and family welfare support
• Libraries, reading rooms and adult education programmes

Because the fund pools contributions across many employers, it functions as a modest social safety net for lower-wage workers who might otherwise have no access to these benefits. That is the policy rationale. Whether the schemes are well-publicised and heavily used varies considerably between States — but the legal obligation to contribute does not depend on utilisation.

Why LWF Is So Confusing: The State Subject Problem

If you have handled EPF or ESI, you are used to a national rulebook. One Act, one authority, one portal, one set of rates, one due date. LWF works nothing like that.

Here is what varies across States:

• Whether an LWF exists at all. Only some States and Union Territories have enacted and operationalised a Labour Welfare Fund Act. Many States have no LWF whatsoever, which means employees working there have no LWF deduction and the employer has no LWF liability in that State. Do not assume nationwide applicability.
• Which establishments are covered. Some Acts cover factories, shops, commercial establishments, motor transport undertakings, plantations and societies; others draw the boundary more narrowly. The definition of "establishment" in the State Act is the controlling text.
• The employee-count threshold. Several States apply the Act only to establishments employing at least a specified number of persons. Others apply it regardless of headcount. The threshold, where it exists, differs by State.
• The wage ceiling. Some States exempt employees earning above a specified monthly wage. Others have no ceiling at all and cover everyone who is not otherwise excluded. Where a ceiling exists, the definition of "wages" for the test also matters.
• Who is excluded by designation. Most Acts exclude persons employed in a managerial or supervisory capacity, often above a stated wage level. The precise carve-out language differs.
• Contribution amounts. Employee and employer shares are usually fixed rupee amounts per employee per cycle rather than a percentage of salary. The amounts differ by State and are revised from time to time.
• The employer-to-employee ratio. In many States the employer contributes a multiple of the employee's share — commonly double, sometimes three times, occasionally the same. The multiple is a State-level design choice.
• Frequency. Monthly in some States, half-yearly in others, annual in a few. This is the single biggest operational complication.
• Deduction and remittance dates. Cut-off dates for the contribution "snapshot", and the deadline for depositing the money, are State-specific.
• Return formats and filing mode. Some Boards run online portals with challan generation; others still expect physical forms, demand drafts or bank challans.
• Registers and records. Prescribed register formats and retention periods vary.
• Penalties. Interest, damages and prosecution provisions differ in both quantum and process.

The practical consequence: you cannot write one LWF rule and apply it company-wide. You need a State-by-State configuration, maintained as a living document, verified against each State Labour Welfare Board's own published notifications.

States and UTs That Operate an LWF — Handle With Care

It is legitimate to name States illustratively. States and Union Territories that have historically operated a Labour Welfare Fund regime include Maharashtra, Karnataka, Tamil Nadu, Andhra Pradesh, Telangana, Kerala, Gujarat, Madhya Pradesh, Chhattisgarh, Delhi, Haryana, Punjab, Odisha, West Bengal, Goa and Chandigarh, among others. Kerala in particular operates several sector-specific welfare fund boards in addition to the general one, which adds another layer for employers in that State.

Equally important: a number of large States have no general Labour Welfare Fund Act in force, so employees working there simply have no LWF line on their payslip.

Verify before you configure. State lists change. A State can notify a new Act, extend an existing one to new classes of establishment, or amend contribution amounts. Treat any list — including this one — as a starting point for verification on the relevant State Labour Welfare Board website, not as an authority.

How to Determine Whether LWF Applies to You

Applicability is a chain of tests. You have to pass every link for a deduction to arise. Work through them in this order.

Step 1: Identify the State of the Establishment, Not the Head Office

LWF applicability follows the State in which the establishment is located and registered, not where your company is incorporated or where your head office sits.

A company registered in Bengaluru with a branch office in Pune, a factory in Gujarat and a sales office in a State with no LWF Act will face three different answers for those four locations. Each registered establishment is assessed on its own.

This is why the first artefact any multi-state employer needs is a clean inventory of establishments: registered address, State, registration type (Shops & Establishments, Factories Act, etc.), registration number, headcount and the HR owner for that location.

Step 2: Check Whether the State Has an LWF Act at All

If the State has no Labour Welfare Fund legislation in force, stop. There is no contribution, no return and no register. Record the "not applicable" conclusion in your matrix with a date and a source link, so the next person who asks does not have to redo the research.

Step 3: Test the Establishment Type

Read the State Act's definition of "establishment" and its schedule of covered classes. Ask:

• Is a factory covered? A shop? A commercial establishment? A society or trust? A motor transport undertaking?
• Does the Act apply to establishments registered under the State Shops and Establishments Act, and is your office actually registered there?
• Are there notified exemptions for particular sectors, or for units registered under specific incentive schemes?

Many disputes come from employers assuming an "IT/ITES office" is somehow outside the net. In most States, an office is a commercial establishment and is covered like any other.

Step 4: Apply the Employee-Count Threshold

Where the Act specifies a minimum number of employees, you need to know:

• What counts as an employee for the threshold. Contract workers and apprentices may or may not count. Read the definition.
• On what date the count is taken. Some Acts use "employed on any day during the preceding period" rather than a point-in-time headcount, which pulls in seasonal peaks.
• Whether the count is per establishment or aggregated. Usually per establishment.

An establishment that crosses the threshold once may remain covered even if headcount later falls, depending on the Act's continuation language. Check this before you switch a deduction off.

Step 5: Apply the Wage Ceiling, If Any

Some States exempt employees whose monthly wages exceed a specified amount. Where such a ceiling exists:

• Confirm the current ceiling on the State Board's site. Ceilings are revised, and stale ceilings cause silent under- or over-deduction across your entire population.
• Confirm which components count as "wages" for the test. Basic only? Basic plus DA? Gross? The definition in the State Act governs, and it is not always the same as your EPF wage definition.
• Decide how you will handle employees who cross the ceiling mid-cycle — see the joiners and leavers section below.

Step 6: Apply the Managerial and Supervisory Exclusion

Almost every LWF Act excludes persons employed in a managerial capacity, and many also exclude supervisory staff above a stated wage. Two traps here:

• Designation is not the test; function is. An employee titled "Manager" who has no authority to hire, fire, sanction leave or direct subordinates may not be managerial in the legal sense. Conversely, a "Team Lead" who genuinely supervises may fall within the supervisory carve-out.
• Applying the exclusion too broadly is the more common error. Companies with title inflation sometimes exclude half their workforce as "managers", which is exactly the kind of thing that surfaces in an inspection.

Document the basis on which you classify each excluded role. A one-line rationale per role, kept with the matrix, is enough.

Step 7: Confirm Whether the Employee Is on Roll on the Snapshot Date

Most State Acts fix the liability by reference to employees on the rolls on a particular date or during a particular period. That single design choice drives the joiner/leaver logic covered later.

The Applicability Decision Chain, Summarised

Anything that survives all seven tests is a covered employee for that cycle.

How Contributions Are Structured

Set aside the numbers and look at the architecture. LWF contributions almost always follow the same three-part structure.

The Employee Contribution

A small fixed amount deducted from the employee's salary for the cycle. Two structural points matter:

• It is normally a flat rupee amount per covered employee, not a percentage of pay. A junior clerk and a senior engineer in the same State typically pay the same LWF amount, provided both are below any applicable ceiling.
• It is a deduction from the employee, so it must appear as a deduction on the payslip. You cannot quietly absorb it without showing it, and you certainly cannot deduct more than the notified amount.

The Employer Contribution

The employer pays its own share, usually a multiple of the employee share — commonly twice, sometimes three times, occasionally equal. This is a cost to the company, not a recovery from the employee.

The employer share is where CTC design questions arise. It is a genuine employer cost, so it can legitimately be shown in CTC in the same way as the employer PF or ESI share. Whether you do so is a policy and transparency choice. Given how small the amounts are, many employers keep the employer LWF share out of the CTC statement entirely to avoid cluttering an offer letter with a line worth a few rupees. Either approach is defensible; just be consistent, and make sure your CTC-to-payslip reconciliation accounts for the treatment you chose.

The Government Contribution

In several States, the State government adds a contribution to the fund. This has no effect on employer payroll processing — you neither collect nor remit it — but it explains why Board scheme budgets can exceed what employers alone contribute. Mention it in internal training so nobody assumes a mismatch between collections and scheme spend is an error.

Structural Summary

Verify the current employee and employer amounts, and the multiple between them, on the relevant State Labour Welfare Board website before every cycle. They change, and the change is often notified without much fanfare.

Deduction Frequency: Why LWF Breaks Payroll Calendars

This is the section to read twice.

Statutory deductions in India mostly run monthly. EPF, ESI, TDS and professional tax in most States all fall into a monthly rhythm that payroll software handles natively. LWF does not respect that rhythm.

Across States you will encounter three patterns:

1. Monthly. Some States require a deduction every month. Operationally the easiest — it behaves like any other recurring deduction.

2. Half-yearly. A number of States, Maharashtra among the best-known examples, collect on a half-yearly basis, with the contribution typically pegged to employees on the rolls around the end of June and the end of December, and remittance following shortly after. This means ten payroll runs a year with no LWF line and two runs where it suddenly appears. Confirm the exact snapshot dates and deposit deadlines for each such State on the Board's website — do not rely on remembered dates.

3. Annual. A few States collect once a year, typically anchored to a specified month with a filing deadline after the period closes. Again, the specific month and deadline are State-specific and must be verified.

Why This Causes Real Problems

• Payroll calendars assume monthly recurrence. If your payroll process is a monthly checklist, a half-yearly item is exactly the sort of task that gets missed — especially if the person who set it up has since left.
• Two months a year look wrong. In half-yearly States, June and December payslips show a deduction that did not exist in May or November. If nobody has briefed the helpdesk, you get a wave of "why is my salary lower this month" tickets in two predictable months.
• Different States, different months, one payroll run. A single June payroll may include monthly-State employees, half-yearly-State employees who are being deducted this month, and employees in non-LWF States with no deduction at all. Manual handling of that mix is where errors breed.
• Cycle boundaries fall mid-period. A half-yearly cycle that closes in June does not align to a financial year, a quarter, or an appraisal cycle. Reconciliations that assume clean quarters will not tie.
• Reminder fatigue. An annual task has to survive twelve months of organisational change — new payroll manager, new HRMS, new entity structure — before it fires.

The fix is not heroics. It is a calendar object per State that lives in your compliance system rather than in someone's head, with owners, reminders and evidence attached. We give the runbook and checklist for this later.

LWF on the Payslip and in CTC

On the Payslip

The employee contribution belongs on the payslip in the deductions block, clearly labelled. "LWF" alone is technically fine but generates questions; "Labour Welfare Fund" is better, and in half-yearly States a footnote such as "Labour Welfare Fund — deducted half-yearly as required under State law" removes most of the ticket volume.

Good practice on payslip presentation:

• Use the same label in every State so employees moving internally are not confused.
• Show a zero or omit the line entirely in months where no deduction applies — do not show a stale value carried forward.
• If your payslip has a year-to-date column, make sure LWF accumulates correctly across the half-yearly or annual pattern rather than being annualised from a single month.
• The employer share is normally not shown on the payslip, since the employee neither pays nor receives it.

In CTC

Three options, all workable, but pick one and document it:

1. Exclude both shares from CTC. The employee share is a deduction from gross, so it is inside CTC by definition through gross salary; the employer share is simply absorbed as a company cost and not shown. Simplest, and given the magnitudes, the most common.
2. Show the employer share in CTC. Consistent with how employer PF and ESI are usually treated. More transparent, but adds a very small line to the offer letter.
3. Show both, with a note. Maximum transparency, maximum clutter.

Whatever you choose, ensure the CTC template and the payroll engine agree, and that your finance team's cost bridge from CTC to actual payroll cost includes the employer LWF share somewhere, even if it is not itemised in the offer letter.

In Income Tax

The employee's LWF contribution is a deduction from salary in the payroll sense. Its treatment for income tax purposes should be confirmed with your tax advisor and configured accordingly in the payroll engine — do not assume a treatment by analogy with PF. The amounts are small enough that errors rarely produce material tax exposure, but consistency across employees matters for audit.

Registration and Remittance: The General Workflow

Specific mechanics differ by State. The general workflow, however, is consistent enough to plan around.

Registration

1. Confirm applicability using the seven-step chain above and record the conclusion.
2. Locate the State Labour Welfare Board's channel — most Boards now have a website, and many offer an online registration and payment portal. Some still operate through the State Labour Department's unified portal.
3. Prepare establishment documents. Typically the Shops and Establishments or Factories Act registration certificate, incorporation documents, PAN, address proof, a list of employees, and details of the authorised signatory. Requirements vary; check the Board's checklist.
4. Apply for registration or an establishment code where the State requires one. Some States do not issue a separate LWF registration and instead accept remittance against the establishment's existing labour registration number.
5. Store the credentials properly. Portal login, registration number, registered email and mobile, and the authorised signatory's details go into your compliance repository — not into one person's inbox. Portal OTPs going to a departed employee's phone number is a depressingly common cause of missed deadlines.

Remittance

1. Freeze the covered-employee list as at the State's snapshot date, after applying every applicability test.
2. Compute the employee and employer totals using the current notified amounts for that State. Verify the amounts before each cycle rather than trusting last cycle's configuration.
3. Generate the challan on the Board's portal, or complete the prescribed physical form where no portal exists.
4. Pay through the prescribed mode — online payment, bank challan, or demand drafts, depending on the State.
5. Capture the proof. Challan number, payment reference, UTR, date, amount, period, and a PDF of the receipt.
6. Reconcile the remitted amount to the payroll register: number of covered employees times the employee amount, plus number of covered employees times the employer amount. Any difference should be explainable line by line.
7. File the return in the prescribed form, within the prescribed time, where the State requires one.
8. Update the register and archive the evidence pack.

Returns and Record-Keeping

Most States require some combination of:

• A periodic return listing covered employees and contributions remitted, in a prescribed form.
• An employee register or muster showing names, designations, wages and contribution status.
• Retention of records for a prescribed number of years, often several.
• Production of records on demand to an inspector appointed under the Act.

Build an evidence pack per State per cycle, containing at minimum: the covered-employee list used, the computation sheet, the challan, the payment receipt, the filed return acknowledgement, and a signed sign-off from the compliance owner. If you can produce that pack within a day for any past cycle, an inspection or a due-diligence request becomes routine rather than traumatic.

Multi-State Employers: Build an Applicability Matrix

If you operate in more than one State, the single most valuable artefact you can create is an LWF applicability matrix — one row per State where you have an establishment, capturing every parameter that drives the deduction.

The matrix is not a nice-to-have document. It is the specification your payroll configuration must implement, the checklist your auditor will ask for, and the induction material for whoever inherits payroll from you.

What Goes in the Matrix

• The State and the specific establishment or establishments in it
• Whether an LWF Act exists in that State
• The name of the governing Act
• Whether your establishment class is covered
• The employee-count threshold, if any
• The wage ceiling, if any, and the wage definition used
• The role-based exclusions that apply
• The contribution frequency (monthly, half-yearly, annual)
• The snapshot or cut-off date for determining covered employees
• The employee contribution amount currently notified
• The employer contribution amount currently notified
• The remittance deadline
• The return form and filing deadline
• The filing mode (online portal, physical, bank challan)
• The registration or establishment code
• The internal owner
• The date you last verified the figures, and the source URL

That last pair of fields — last verified date and source URL — is what separates a matrix that stays accurate from one that quietly rots.

The Fill-In Template

Copy this table, one row per State, and populate it from the relevant State Labour Welfare Board's own published material. Every cell below is deliberately left blank because the correct value is State-specific and changes over time.

Set a recurring review — quarterly is sensible, half-yearly is the minimum — where the owner revisits every source URL and re-stamps the "last verified" date. A matrix nobody re-verifies is more dangerous than no matrix at all, because it creates false confidence.

Mid-Cycle Joiners and Leavers

In monthly States, joiners and leavers behave predictably: deduct in the months in which the employee is covered and on roll. In half-yearly and annual States, it gets interesting.

The controlling question is always: does the State Act fix liability by reference to employees on the rolls on a specific date, or by reference to employees who worked during the period?

• If liability is date-based, an employee who joins in July and is on roll on the December snapshot date is covered for that half-year, and an employee who resigns in November is not — even though they worked five of the six months. The full cycle contribution is typically deducted from whoever is on roll on the snapshot date, without proration.
• If liability is period-based, an employee who worked during the period may be covered even if they have since left, and you may need to recover the contribution from their final settlement.

Practical rules that follow:

1. Do not prorate unless the State Act says to. LWF contributions are generally flat amounts per cycle, not accruals. Proration invented by a payroll analyst produces a remittance that does not reconcile to headcount times rate, which is exactly what an inspector recalculates.
2. Handle leavers in the full-and-final process. If a leaver in a half-yearly State exits after the snapshot date but before the deduction month, the deduction should be taken in the F&F rather than lost. Build this into the F&F checklist per State.
3. Watch the leaver who exits just before the snapshot. No liability typically arises, but do not let a stale recurring deduction fire anyway. Deducting LWF from someone who is not covered is an unauthorised deduction, however small.
4. Watch the wage-ceiling crosser. In States with a ceiling, an employee promoted above the ceiling in September may or may not remain covered for the half-year ending December, depending on when the Act tests wages. Verify the timing rule, then encode it — do not decide it case by case.
5. Rehires and internal transfers. An employee who transfers from a non-LWF State to an LWF State mid-cycle needs their coverage recomputed from the receiving State's rules, not carried over.

Document your chosen treatment for each of these five cases per State in a short note attached to the matrix. When the payroll analyst changes, the treatment should not.

Interstate and Remote Employees: Which State's LWF Applies?

Remote and hybrid work has made this a live question. The general principle:

LWF follows the establishment to which the employee is attached, not the employee's home address.

If an employee is on the rolls of your Pune establishment but works from Indore, the Pune establishment's State rules generally govern their LWF treatment, because it is the establishment that is registered, covered and liable under the State Act.

That principle holds well in the straightforward cases and gets murky in these:

• Fully remote employees attached to no physical office. Assign them to a specific registered establishment for compliance purposes and be consistent across LWF, professional tax, Shops and Establishments coverage and state-specific leave rules. Assigning an employee to different States for different statutes is how contradictions get discovered during audit.
• Employees who relocate permanently. If someone moves States and is genuinely re-attached to a different establishment, update the establishment mapping, and let LWF, PT and other State-linked rules re-derive from the new mapping.
• Employees working long-term at a client site in another State. Where the employee is deployed at a client location for an extended period, examine whether your presence there itself constitutes an establishment requiring registration. This question is bigger than LWF, but LWF is often where it first surfaces.
• Field staff covering multiple States. Attach them to their reporting or base establishment and hold that consistently.

The operational takeaway: your HRMS needs a "work location / establishment" field that is distinct from "home address" and distinct from "reporting manager's location", and every State-linked statutory rule should read from that single field. Companies that derive professional tax from one field and LWF from another end up with employees who are simultaneously in two States according to their own systems.

Contract Labour: Who Bears the Responsibility?

Where you engage workers through a contractor, two questions arise: who deducts and remits, and who is on the hook if it does not happen?

The general position across State LWF Acts mirrors the pattern in other Indian labour statutes:

• The contractor, as the immediate employer of the contract workmen, is primarily responsible for deducting the employee share from those workers and remitting it along with the contractor's own employer share.
• The principal employer often carries a secondary or backstop responsibility. Many Acts, or the general scheme of principal-employer liability in Indian labour law, allow the authorities to look to the principal employer if the contractor defaults — with a right of recovery from the contractor.
• Contract workers may or may not count toward the principal employer's own employee-count threshold, depending on the State Act's definitions. Check this specifically; it can be the difference between coverage and non-coverage for a borderline establishment.

Because the exposure is real even though the amounts are small, protect yourself procedurally:

1. Put an explicit LWF clause in the contractor agreement requiring compliance with all applicable State labour welfare fund legislation, with an indemnity.
2. Collect evidence every cycle, not every audit. Ask contractors for the challan, payment proof and return acknowledgement for each LWF cycle covering the workers deployed to you.
3. Reconcile headcount. Compare the number of workers the contractor deployed at your site against the number covered in their remittance. A contractor remitting for four people while deploying forty is a problem you want to find first.
4. Withhold against non-compliance. Make the compliance evidence a condition of invoice release. It is the only lever that reliably works.
5. Keep the evidence in your own repository. If a contractor exits, their records leave with them; your inspection exposure does not.

The same logic applies to staffing partners, payrolling vendors and Employer-of-Record arrangements. Whoever is the employer of record for those workers should be running the LWF compliance, and you should be collecting proof.

Penalties, Interest and Enforcement

Because the underlying contribution amounts are small, employers sometimes assume the consequences of default are trivial. That is a mistake, for three reasons.

1. Consequences are usually structural, not proportional. State LWF Acts typically provide for some combination of:

• Interest or damages on delayed remittance, computed for the period of delay
• Recovery of unpaid contributions, often with the power to recover as arrears of land revenue
• Penalties or fines for failure to maintain registers, file returns or produce records
• Prosecution provisions for continued default, in some States extending to officers in default
• Cumulative exposure, because unremitted contributions across many employees and many cycles compound quickly

The exact quantum, the method of computing interest and the prosecution thresholds vary by State. Do not rely on generic figures; check the penal provisions in the specific State Act.

2. The lookback is what hurts. A missed half-yearly cycle discovered five years later is ten cycles of unpaid contributions for every covered employee, plus interest, plus penalties, plus the register and return failures alongside. The per-employee-per-cycle amount stays small; the aggregate does not.

3. It shows up at the worst time. LWF non-compliance rarely surfaces through an inspection. It surfaces during fundraising due diligence, an acquisition, a large-customer vendor audit, or a tender qualification — moments when "we'll fix it next quarter" is not an acceptable answer and a compliance certificate is being demanded on a deadline.

The good news: because contributions are small, remediating historical LWF gaps is usually financially manageable. The pain is administrative — reconstructing covered-employee lists for past cycles, computing State-wise arrears at the rates that applied at the time, and negotiating the process with the Board. Better to never get there.

The LWF Payroll Runbook: Step by Step

Here is the operating process. Run it every cycle, in every State where LWF applies.

Before the cycle

1. Open the matrix for the State whose cycle is due and read the current configuration.
2. Re-verify the figures on the State Labour Welfare Board website: employee amount, employer amount, wage ceiling, threshold, snapshot date, remittance deadline, return form. Stamp the verification date.
3. Confirm the payroll engine matches the matrix. If a rate changed, update the configuration and record who changed it and when.
4. Confirm portal access works. Log in before the deadline week, not during it. Reset credentials early if the registered mobile or email belongs to someone who has left.

Determining coverage

1. Pull the employee list for each establishment in that State as at the snapshot date.
2. Apply the exclusions: managerial and supervisory roles, employees above any wage ceiling, and any other State-specific carve-outs. Keep the excluded list, with reasons — you will need it if the count is questioned.
3. Handle joiners and leavers per the documented State treatment. Check the F&F queue for leavers who owe a contribution.
4. Freeze the covered-employee count and get it signed off by the compliance owner.

Processing payroll

1. Run the deduction for covered employees only, at the verified amount, in the correct payroll month.
2. Verify the payslip presentation on a sample: correct label, correct amount, appears only for covered employees, YTD accumulates correctly.
3. Book the employer share to the correct cost centre and GL account. It is an expense, not a liability recovery.
4. Reconcile before disbursement: covered headcount times employee rate equals total employee deduction in the payroll register; same for the employer share. Investigate any variance before you pay salaries, not after.

Remitting and filing

1. Generate the challan on the Board's portal or complete the prescribed form.
2. Remit within the State's deadline through the prescribed mode.
3. Capture proof: challan number, UTR, receipt PDF, amount, period.
4. File the return in the prescribed form within the prescribed time.
5. Reconcile remittance to payroll: the amount deposited must tie exactly to the payroll register. A rounding difference is still a difference — explain it.

Closing the cycle

1. Update the statutory register with the prescribed particulars.
2. Archive the evidence pack — covered list, exclusions with reasons, computation sheet, challan, receipt, return acknowledgement, sign-off.
3. Set the next cycle's reminder with enough lead time to re-verify figures and fix portal access before the deadline.
4. Log any issue encountered this cycle and the fix, so the next run is smoother.

Twenty-one steps looks like a lot for a deduction worth a few rupees. In practice, once it is encoded in an HRMS, most of them are automatic and the human effort collapses to verification and sign-off.

Half-Yearly LWF Compliance Checklist

Use this as a standing checklist for each half-yearly cycle, in each applicable State. Tick every line and retain the completed checklist as part of the evidence pack.

Configuration

• [ ] Matrix reviewed for this State and last-verified date is within the review window
• [ ] Employee contribution amount re-verified against the Board's current notification
• [ ] Employer contribution amount re-verified
• [ ] Wage ceiling re-verified, including the wage definition used
• [ ] Employee-count threshold re-verified and current headcount checked against it
• [ ] Snapshot date and remittance deadline re-verified
• [ ] Return form and filing mode re-verified
• [ ] Payroll engine configuration matches the matrix; changes logged

Access and ownership

• [ ] Portal credentials tested and working
• [ ] Registered mobile and email belong to current employees
• [ ] Authorised signatory details current
• [ ] Named compliance owner confirmed for this cycle

Coverage

• [ ] Establishment list for the State is current, including any new locations opened this half-year
• [ ] Employee list pulled as at the snapshot date
• [ ] Managerial and supervisory exclusions applied with documented reasons
• [ ] Wage-ceiling exclusions applied
• [ ] Joiners since the last cycle assessed
• [ ] Leavers assessed; F&F deductions raised where required
• [ ] Internal transfers into and out of the State reassessed
• [ ] Remote employees mapped to the correct establishment
• [ ] Covered-employee count frozen and signed off

Contract labour

• [ ] Contractor list for this State compiled
• [ ] LWF compliance evidence requested from each contractor
• [ ] Contractor deployed headcount reconciled to their remittance
• [ ] Non-compliant contractors escalated; invoice release withheld where applicable

Payroll and remittance

• [ ] Deduction applied only to covered employees, at the verified amount
• [ ] Payslip presentation sampled and verified
• [ ] Employer share booked to correct GL and cost centre
• [ ] Payroll register reconciled to headcount times rate
• [ ] Challan generated
• [ ] Payment made before the deadline
• [ ] Payment proof captured

Filing and records

• [ ] Return filed within the prescribed time
• [ ] Acknowledgement saved
• [ ] Statutory register updated
• [ ] Evidence pack archived in the compliance repository
• [ ] Next cycle reminder set with lead time
• [ ] Issues log updated

Communication

• [ ] Helpdesk and HR business partners briefed that a deduction appears this month in this State
• [ ] Employee FAQ published or refreshed

Common LWF Mistakes and How to Fix Them

Mistake 1: Applying one State's rules company-wide. A company headquartered in an LWF State applies the same deduction to every employee nationwide, including those in States with no LWF Act. Result: unauthorised deductions from employees who owe nothing, and money remitted against the wrong establishment. Fix: Derive LWF from the employee's establishment State, driven by the matrix. Never hard-code a single company-wide rule.

Mistake 2: Forgetting the half-yearly cycle entirely. The classic failure. Someone configured it once, it fired twice, and then a payroll migration or a resignation dropped it. Two years later nobody remembers the State ever had an LWF. Fix: Put the cycle in a compliance calendar with an owner and a backup owner, not in a personal reminder. Reconcile annually: for each State in the matrix marked applicable, confirm that the expected number of remittances actually occurred.

Mistake 3: Using stale contribution amounts. Rates get revised. A configuration set three years ago quietly under-deducts every cycle since. Fix: Re-verify amounts on the Board's site before every cycle and stamp the verification date in the matrix. Make "verified this cycle" a checklist line, not an assumption.

Mistake 4: Over-applying the managerial exclusion. Everyone with "Manager" in their title is excluded, halving the covered population. Fix: Test function, not title. Document the rationale per role. Review the exclusion list whenever the job architecture changes.

Mistake 5: Prorating a flat contribution. A payroll analyst decides a mid-cycle joiner should pay half. The remittance no longer equals headcount times rate, and the reconciliation fails. Fix: Follow the State Act's snapshot logic. No proration unless the Act provides for it.

Mistake 6: Ignoring contract labour. The principal employer assumes it is entirely the contractor's problem and collects no evidence. Fix: Contract clause, indemnity, cycle-wise evidence collection, headcount reconciliation, invoice hold as leverage.

Mistake 7: Remote employees mapped inconsistently. LWF derives from one location field, professional tax from another, and the employee appears to be in two States at once. Fix: One authoritative establishment field per employee. Every State-linked rule reads from it.

Mistake 8: No evidence pack. The money was remitted, but nobody can produce the challan, the covered list or the return acknowledgement for a cycle three years ago. Fix: Standardised evidence pack per State per cycle, stored centrally, with a naming convention and a retention rule.

Mistake 9: Portal access held by one person. Credentials, registered mobile and OTPs all sit with an employee who resigns two weeks before the deadline. Fix: Institutional email and phone for portal registration, credentials in a managed vault, backup owner named in the matrix.

Mistake 10: Not registering new establishments. A new branch opens, headcount grows past the threshold, and nobody revisits LWF applicability. Fix: Make LWF assessment a mandatory step in the new-location opening checklist, alongside Shops and Establishments registration and professional tax enrolment.

Mistake 11: Confusing LWF with an employee benefit. Employees are told LWF is "like PF" and will come back to them. Fix: Correct FAQ language. LWF is a pooled welfare levy with no individual account and no withdrawal.

Mistake 12: Treating the employer share as recoverable. The employer share is deducted from the employee, doubling their deduction. Fix: Only the employee share is deductible. The employer share is a company cost, booked as an expense.

How an HRMS Automates State-Wise LWF

Everything above can be done on spreadsheets. It just does not survive growth, staff turnover, or a second and third State. This is what proper HRMS and payroll automation should handle for LWF.

State-wise rule engine. Contribution amounts, frequency, thresholds, ceilings and exclusion logic maintained as configurable rules per State, versioned with effective dates so a mid-year revision applies from the right cycle without corrupting prior periods.

Establishment-driven derivation. Every employee carries an establishment, the establishment carries a State, and the State drives LWF, professional tax and other location-linked rules from a single source of truth. Change the establishment and everything re-derives consistently.

Automatic eligibility evaluation. The system applies the wage ceiling, the headcount threshold and the role-based exclusions each cycle and produces the covered-employee list, with an audit trail of who was excluded and why.

Cycle-aware scheduling. Monthly, half-yearly and annual cycles handled natively, so the deduction appears in the correct payroll month per State automatically. No manual switching on and off, no forgotten June and December runs.

Snapshot handling. Coverage determined as at the State's cut-off date, with joiner, leaver, transfer and ceiling-crossing logic encoded per State rather than decided case by case.

Payslip and CTC consistency. Correct label, correct months, correct YTD, with the employer share treated per your documented CTC policy across offer letters, payslips and cost reports.

Reconciliation and reports. State-wise contribution summaries that tie covered headcount to rate to total remittance, ready to attach to a challan or hand to an auditor.

Compliance calendar and alerts. Upcoming remittance and filing deadlines per State surfaced to the named owner with lead time, escalating if not actioned.

Document repository. Challans, receipts, returns, registers and sign-offs stored against the State and cycle, retrievable in seconds during an inspection or due diligence.

Change alerts and audit trail. A record of every configuration change — who changed the rate, when, and against which source — so the question "why did the amount change in this cycle" always has an answer.

Multi-entity and multi-establishment support. Group companies with several legal entities and many registered establishments handled without cloning the whole payroll setup per entity.

The point of automation here is not effort saved on a small deduction. It is eliminating the class of error where a rule exists only in one person's memory. That is the failure mode LWF punishes.

Frequently Asked Questions

1. Is the Labour Welfare Fund applicable across all of India? No. LWF is a State subject, and only some States and Union Territories have enacted and operationalised a Labour Welfare Fund Act. Employees working in States with no such Act have no LWF deduction. Confirm the position for each State where you have an establishment on that State's Labour Welfare Board website.

2. Can an employee claim their LWF contributions back? No. Unlike Provident Fund, LWF has no individual account. Contributions go into a pooled fund administered by the State Labour Welfare Board and are spent on welfare schemes for workers generally. There is no withdrawal, no balance statement and no transfer on job change. Employees may be able to access Board-run schemes such as scholarships or medical assistance, subject to the Board's eligibility rules.

3. Why does the deduction appear only twice a year on some payslips? Because several States collect LWF on a half-yearly basis rather than monthly, with contributions typically pegged to employees on the rolls around the middle and end of the calendar year. Maharashtra is a commonly cited example of a half-yearly State. Confirm the exact cycle dates for your State on the Board's website, and brief your helpdesk before those payroll runs so employees are not surprised.

4. Do we deduct LWF from senior managers? Usually not, but it depends on the State Act. Most Acts exclude persons employed in a managerial capacity, and many also exclude supervisory staff above a stated wage. Some States apply a general wage ceiling instead. The test is the employee's actual function and authority, not their job title — and applying the exclusion too broadly is a common audit finding.

5. Who pays LWF for contract workers? The contractor, as the immediate employer, is generally responsible for deducting and remitting for the workers it employs. However, the principal employer often carries backstop liability if the contractor defaults, and contract workers may count toward the principal employer's own threshold in some States. Put an LWF clause and indemnity in the contract, collect challans and returns every cycle, and reconcile the contractor's covered headcount to the workers actually deployed.

6. Which State's LWF applies to a fully remote employee? Generally, the State of the establishment to which the employee is attached on your rolls, not the employee's home address. Assign every remote employee to a specific registered establishment and use that same mapping for LWF, professional tax and other State-linked obligations so your systems never place one person in two States.

7. What happens if we have missed LWF for several cycles? Expect to pay the arrears with interest or damages, and potentially penalties for failure to file returns or maintain registers, with the quantum depending on the State Act. Because per-cycle amounts are small, the financial remediation is usually manageable; the hard part is reconstructing historical covered-employee lists and computing arrears at the rates that applied at the time. Address it proactively rather than waiting for it to surface in a due-diligence exercise.

8. Is the employer contribution part of CTC? It can be, and it is a genuine employer cost, so including it is defensible in the same way as employer PF or ESI. Many employers omit it from the CTC statement because the amount is negligible. Either approach is fine — choose one, document it, and make sure your offer letters, payslips and cost reports all reflect the same treatment.

9. How often do LWF contribution amounts change? There is no fixed revision cycle. State Labour Welfare Boards revise contribution amounts, wage ceilings and occasionally thresholds from time to time, through notifications that are not always widely publicised. This is precisely why you should re-verify the figures on the Board's own website before every cycle rather than trusting a configuration set years ago.

Getting LWF Off Your Risk Register

The Labour Welfare Fund is a small obligation with a disproportionate ability to embarrass a growing company. The contribution amounts barely register in a payroll cost sheet. The compliance structure — separate State Acts, different thresholds and ceilings, monthly versus half-yearly versus annual cycles, State-specific returns and registers, contractor liability, remote-worker mapping — is where the risk actually lives.

The path to control is not complicated:

1. Inventory every establishment and the State it sits in.
2. Determine applicability State by State using the seven-step chain.
3. Build the applicability matrix, with source links and verification dates.
4. Encode the rules in your payroll system rather than in someone's memory.
5. Run the cycle-wise runbook and keep an evidence pack for every remittance.
6. Re-verify the figures on each State Labour Welfare Board's website before every cycle, because they change.

Do those six things and LWF stops being a lurking liability and becomes a routine, boring, fully-evidenced part of your payroll close — which is exactly what a statutory deduction should be.

If you would rather not maintain State-wise LWF rules, cut-off dates and half-yearly cycles by hand, this is exactly the kind of work an HRMS should absorb. CozyHR handles India-specific statutory payroll — State-wise LWF configuration with effective-dated rules, automatic eligibility evaluation, cycle-aware deductions that appear in the right month for the right State, reconciliation reports that tie to your challans, compliance calendars with named owners, and a document repository that makes an inspection or a due-diligence request a ten-minute exercise instead of a two-week scramble.

Take a look at CozyHR and see how much of your statutory compliance calendar can simply run itself.

---

This article explains the structure and administration of the Labour Welfare Fund in general terms. It deliberately does not state specific contribution amounts, wage ceilings or due dates for any State, because those figures are revised periodically by individual State Labour Welfare Boards. Always confirm current figures, forms and deadlines on the relevant State Labour Welfare Board website, and consult a qualified labour law advisor before finalising your compliance approach. This content is for general information and does not constitute legal advice.