Labour Welfare Fund Compliance: A State-Wise Employer Guide

Labour Welfare Fund Compliance: A State-Wise Employer Guide

Labour welfare fund compliance is one of those statutory obligations that rarely makes headlines but quietly trips up growing Indian businesses. The amounts involved are small, the rules are set state by state, and the due dates do not line up with the monthly rhythm of PF, ESI and TDS. That combination is exactly why LWF gets missed, especially once a company opens a second office in another state.

This guide is written for HR managers, founders and payroll teams who want a practical, end-to-end understanding of LWF: what it is, who it covers, how applicability works across states, how to configure it in payroll, and how to build a calendar so nothing slips. It is not legal advice, and because every state sets its own rules, you must verify the current figures with the relevant state labour welfare board.

What Is the Labour Welfare Fund?

The Labour Welfare Fund (LWF) is a statutory fund created under state-level legislation to finance welfare activities for workers. Each participating state has its own Labour Welfare Fund Act and rules, and a state labour welfare board administers the fund. The money is typically used for things like housing support, medical facilities, educational assistance for workers' children, recreation, vocational training and similar programmes.

The fund is built from a few sources. The two that matter most for an employer are the employee contribution (deducted from wages) and the employer contribution (paid out of the company's pocket). Some Acts also route unpaid accumulations, such as unclaimed wages or bonus, and fines collected from employees into the fund.

Why LWF exists

Unlike PF or ESI, which are individual benefit schemes tied to a specific employee's account, LWF is a pooled welfare fund. An employee who contributes does not receive a personal balance or statement. Instead, the contribution supports welfare schemes that eligible workers in that state can apply for. This is why LWF amounts are modest and often flat rather than percentage-based.

LWF is a state subject

Labour appears on the Concurrent List of the Indian Constitution, but the welfare fund legislation itself has been enacted by individual states. There is no single central LWF Act that applies across India. This has several consequences for employers:

• Applicability differs: some states have an LWF Act, others do not.
• Contribution amounts differ, and they are revised by state notifications from time to time.
• Contribution frequency differs: monthly in some states, half-yearly or annual in others.
• Wage thresholds and covered employee categories differ.
• Due dates, forms, return formats and payment portals differ.

For a single-location company, this means learning one set of rules. For a multi-state company, it means maintaining a matrix of rules and updating it whenever a state issues a revision.

Which States Have a Labour Welfare Fund Act?

A number of states and union territories have enacted labour welfare fund legislation. The list below covers the ones most commonly encountered by employers with distributed teams. It is not exhaustive, and states occasionally amend, extend or restructure their schemes, so treat this as a starting point for verification rather than a definitive statement of law.

Important: the table deliberately does not include contribution amounts, wage thresholds or due dates. These values are set by state notification and change over time. Always confirm the current figures on the official website of the respective state labour welfare board or through your compliance advisor before running payroll.

A few observations that hold across most of these states, though you should confirm each in your own context:

• Where a wage threshold exists, employees earning above it are often excluded, and the wage definition used for the threshold matters.
• Many states exclude persons employed in a managerial or supervisory capacity, and how "supervisory" is interpreted varies.
• Some states apply LWF only to establishments meeting a minimum headcount; others apply it to any establishment covered under the Shops and Establishments Act or the Factories Act.
• Half-yearly states split the year into two periods with a contribution due after each; annual states typically collect once, often at the end of the calendar year.

States without an LWF Act

Several states and union territories do not have a labour welfare fund law at all. If your employees are located in such a state, no LWF deduction applies to them, even if your registered office is in a state that does have an Act. This point is central to multi-state applicability, which we cover next.

Determining Labour Welfare Fund Compliance Applicability for Multi-State Employers

The single most common conceptual error in LWF compliance is applying the rules of the state where the company is registered to every employee on the payroll. LWF applicability follows the place of work, not the corporate address.

Work location, not registered office

The state whose Act applies is the state in which the employee is employed, which generally means the establishment where they work. Consider a fictional company, Arkline Logistics Pvt Ltd, headquartered in Pune with a warehouse in Ahmedabad and a sales office in Chennai.

• Employees working in the Pune office fall under Maharashtra's Act.
• Employees in the Ahmedabad warehouse fall under Gujarat's Act.
• Employees in the Chennai sales office fall under Tamil Nadu's Act.

Arkline needs three sets of rules, three registrations (or coverage confirmations), three deduction schedules and three filing calendars. Running everything on Maharashtra's rules would under- or over-deduct for two-thirds of the workforce and leave two states unfiled.

Remote and hybrid employees

Remote work complicates this. Where an employee works from home in a state with no company establishment, many employers map the employee to the establishment they report to. There is no uniform answer, so document the basis you adopt, apply it consistently, and revisit it with your advisor as guidance evolves.

Steps to determine applicability

1. List every state in which you have employees physically working.
2. For each state, check whether an LWF Act exists.
3. For each covered state, check whether your establishment type is covered (factory, shop, commercial establishment, specific industries).
4. Check whether a minimum headcount applies and whether you meet it.
5. Identify the covered employee categories and exclusions (wage threshold, managerial or supervisory roles).
6. Note the contribution frequency, due dates and filing mechanism.
7. Record all of this in a state-wise LWF matrix and assign an owner to keep it updated.

Who Is Covered: Employee Categories and Exclusions

Each state's Act defines "employee" for LWF purposes. While the wording differs, the pattern is broadly similar: persons employed for hire or reward to do skilled, unskilled, manual, clerical, supervisory or technical work are covered, with exclusions carved out for certain categories.

Typical exclusions

• Persons employed primarily in a managerial capacity.
• Persons employed in a supervisory capacity drawing wages above a specified level.
• Employees whose wages exceed a wage ceiling, in states that have one.
• Apprentices under the Apprentices Act, in some states.

Because the exclusions are state-specific, an employee with the same designation and salary might be covered in one state and excluded in another. Your payroll configuration must therefore apply the exclusion logic per state, not globally.

Designations versus actual duties

A recurring audit issue is the "manager" title being used to exclude employees who do not actually perform managerial functions. Labour authorities look at the nature of the work rather than the title on the offer letter. If your organisation hands out manager titles liberally, do not assume that every one of them is outside LWF. Assess the role, document the basis, and when in doubt, include the employee. The cost of an unnecessary deduction is small; the cost of a systematic exclusion that fails scrutiny is higher.

Wage definition

The wage threshold, where it exists, is measured against the wage definition in that state's Act, which may be narrower than gross salary. Check what components count before comparing an employee's salary against the threshold, because a mistake here can misclassify a whole band of employees.

Registration with the State Labour Welfare Board

Before you can remit contributions, most states require the establishment to be registered or enrolled with the state labour welfare board. In some states this is a distinct registration; in others, the establishment's existing registration under the Shops and Establishments Act or the Factories Act is used as the reference and the board issues an LWF code on first payment.

Typical registration process

1. Identify the correct board for the state (the board's website is usually the authoritative source for forms and portals).
2. Gather establishment details: name, address, nature of business, Shops and Establishments or factory licence number, PAN, number of employees, and authorised signatory details.
3. Complete the prescribed enrolment form, online where available.
4. Receive the establishment code or registration number.
5. Record the code in your payroll system against that state's establishment so that challans and returns can reference it.

If your company has more than one establishment in the same state, check whether the board expects a single registration per state or one per establishment. Practice differs and the answer affects how you file.

Example: Meridian Tech Studio

Meridian Tech Studio, a fictional design agency, opened in Bengaluru with twelve people and registered under the Karnataka Shops and Establishments Act. When it opened a Hyderabad office two years later, the founders assumed the Karnataka registration covered everyone. It did not. The Hyderabad staff fell under Telangana's rules, with a different contribution schedule and a separate board. Meridian had to register separately in Telangana, and it discovered the gap only when a prospective investor's due diligence checklist asked for state-wise LWF challans.

Calculating and Deducting the Employee Share via Payroll

Once you know which employees are covered in each state, the mechanics of the deduction are straightforward. The challenge is timing.

How the deduction works

• The employee share is a fixed amount per employee per contribution period in most states, rather than a percentage of salary. In a few states the amount is linked to a wage slab.
• The deduction is taken from the employee's salary in the payroll month that corresponds to the contribution period.
• The employer share is a separate amount, often a multiple of the employee share, paid by the company and not recovered from the employee.

Monthly versus periodic deductions

In monthly-frequency states, the deduction appears on every payslip. In half-yearly and annual states, the deduction appears only in the specific payroll months designated for LWF, which are typically the last month of each contribution period. Payroll teams sometimes get this wrong in one of two ways: deducting monthly in a half-yearly state (over-deducting), or forgetting the designated month entirely (under-deducting).

Some employers in periodic states spread the employee share across the months of the period and remit the total at period end. Check whether the state's rules permit this before adopting it; where rules are silent, the simpler approach of deducting the full amount in the designated month is easier to defend.

Worked illustration (structure only, no amounts)

Suppose Riverbend Foods Pvt Ltd, a fictional food processing company, has staff in a half-yearly state. In the last month of each half-year, payroll:

1. Filters active employees mapped to that state's establishment.
2. Removes employees excluded by wage ceiling or managerial classification.
3. Applies the employee-share amount as a deduction on each remaining employee's payslip.
4. Calculates the employer share for the same headcount as a company cost.
5. Generates a state-wise LWF register and challan.
6. Remits the total to the board before the due date and files the return.

The same logic applies for monthly states, except steps one to five run every month.

Employer Contribution

The employer share is a statutory cost that should be provisioned in the same way as employer PF or ESI. Two practical points:

• Budget for it per state. In states where the employer share is a multiple of the employee share, the employer's total is larger than the sum of deductions, which surprises finance teams who assume LWF is a pass-through.
• Do not net it against anything. The employer share cannot be recovered from employees, and treating it as a deduction on the payslip is a compliance failure as well as a morale issue.

For cost-to-company (CTC) structures, decide whether the employer LWF share is part of the CTC quoted to candidates. Many companies include it as a line item in the CTC breakup along with employer PF and ESI so that the offer letter reconciles with actual payroll cost.

Remittance and Return Filing

Paying the contribution and filing the return are separate obligations. Many states have moved to online portals for both, though the maturity of these portals varies and some states still accept physical challans and returns.

Remittance

• Identify the payment mode for each state: online portal, bank challan, demand draft or cheque.
• Ensure the challan references the correct establishment code and contribution period.
• Retain the payment acknowledgement, since it is the primary evidence during an inspection or audit.

Return filing

• Most states prescribe a form for the periodic return that lists the number of employees, total employee contributions, total employer contributions and the amount remitted.
• Some states require an employee-wise statement to be uploaded or attached.
• Where a portal exists, the return is often generated from the data entered at the time of payment; verify that it has actually been submitted and download the acknowledgement.

Due dates

Due dates are set by each state and differ by contribution period. Rather than memorising them, put them in a calendar owned by a named person with reminders set well before the date. See the calendar template later in this guide.

Record-Keeping for Labour Welfare Fund Compliance

Good records make LWF compliance defensible. The following should be maintained for each state, for each contribution period:

• The LWF register listing every covered employee, their wages for threshold purposes, the amount deducted and the employer share.
• A list of employees excluded and the reason for exclusion (wage ceiling, managerial role, apprentice status).
• The challan or payment acknowledgement.
• The filed return and its acknowledgement.
• Board registration certificate or establishment code letter.
• Any correspondence with the board, including notices and responses.

Retention periods are prescribed by each state's rules. As a practical floor, keep records for as long as you retain other statutory payroll documents, and preferably in a system that can produce a state-wise report on demand.

Mid-Period Joiners and Leavers

Because LWF in many states is collected per period rather than per month, the treatment of employees who join or leave partway through a period generates frequent questions.

Common approaches

• Employee on rolls on the designated cutoff date: most states link the contribution to employees who are on the rolls on a specific date or in a specific month. If the employee is on the rolls on that date, deduct and contribute; if not, do not.
• Employee who left before the cutoff: usually no contribution for that period, since they are not on the rolls at the relevant time. If your payroll had already deducted a spread-out monthly amount, refund it in the final settlement or remit it, depending on the state's rules.
• Employee who joined after the cutoff: no contribution for that period; they are picked up in the next period.

Final settlements

Full and final settlements are where LWF is most often mishandled. Either the deduction is made without the corresponding remittance (because the employee is no longer on the active list when payroll runs the LWF report), or the deduction is skipped even though the employee was on rolls on the cutoff date. Include a specific LWF check in your F&F checklist.

Example: Sundar Retail Ventures

Sundar Retail Ventures, a fictional chain of stores, runs payroll in a half-yearly state. An employee resigned two weeks before the period-end cutoff. Payroll had been spreading the employee share monthly. On exit, the accumulated amount was refunded in the final settlement because the employee was not on the rolls on the cutoff date. Another employee joined three days before the cutoff and was included in full, because the rules in that state look at presence on the rolls on the cutoff date rather than the duration of service. Both outcomes were documented in the LWF register with a note.

Contract Labour and Principal Employer Considerations

LWF obligations for contract workers sit primarily with the contractor as their employer. However, principal employers are not fully insulated. Under the general framework of contract labour regulation, the principal employer bears responsibility if the contractor fails to comply with statutory obligations toward the workers deployed at its premises, and some state LWF rules explicitly reference contract labour.

Practical safeguards for principal employers

• Include LWF compliance in the contractor's statutory obligations under the service agreement.
• Collect LWF challans and returns from the contractor each period as a condition of invoice processing.
• Verify that the contractor's LWF filings cover the workers deployed at your site and in your state, not just workers at the contractor's home base.
• Maintain a contractor compliance tracker with LWF as a line item alongside PF, ESI and minimum wages.

Example: Northgate Business Park

Northgate Business Park, a fictional facility management company, engaged a housekeeping contractor for its Gurugram site. The contractor was headquartered in a state without an LWF Act and had never registered in Haryana. Northgate's compliance team caught this during quarterly contractor audits and required the contractor to register and remit for the site staff. Had an inspection occurred first, Northgate as principal employer would have faced awkward questions, even though the primary default was the contractor's.

Penalties and Consequences

Every state's Act provides consequences for non-payment, late payment or failure to file returns. These typically take the form of interest or damages on delayed contributions, fines, and in some cases prosecution of the employer or responsible officers for persistent default. The specific quantum varies by state and is revised over time, so it is not stated here.

Beyond statutory penalties, the practical consequences matter more for most SMBs: due diligence findings during fundraising or customer onboarding, inspection notices that consume management time, and employee grievances if deductions were made but not remitted. Deducting from employees and not remitting is treated far more seriously than simply failing to deduct, because it involves money held in trust for workers.

Interaction with the Labour Codes

India's four labour codes, covering wages, industrial relations, social security, and occupational safety, health and working conditions, have been enacted with implementation depending on central and state rules. The Code on Social Security consolidates several central welfare and social security laws and gives governments broad power to frame schemes.

What this means for LWF is not fully settled. State labour welfare fund Acts are state legislation and were not among the central laws subsumed by the codes, but states may amend or align their welfare fund laws as they notify rules under the codes. There may also be changes to wage definitions that affect how LWF thresholds are measured, since the codes introduce a standardised definition of wages.

The safe position for employers:

• Continue to comply with the existing state LWF Acts until a state formally notifies a change.
• Monitor state notifications under the labour codes for any impact on welfare fund contributions or definitions.
• Verify with your advisor whenever a state announces rules under the codes, since the effect on LWF may be indirect.

Month-End and Half-Year Labour Welfare Fund Compliance Checklist

The following checklist is designed to be run at each payroll close, with the periodic items triggered in the relevant months for each state.

Configuring LWF in Payroll Software

Manual LWF tracking works for a company with one office and thirty people. It stops working when you have three states, periodic deductions with different cutoffs, and a payroll team that turns over. Payroll software should carry the rules so that people do not have to remember them.

Step-by-step configuration

1. Set up establishments by state. Create one establishment record per state (or per registered location if the board expects it) and store the LWF registration code against each.

1. Map every employee to an establishment. The employee's work location, not the corporate address, drives this mapping. Ensure transfers update the mapping with an effective date.

1. Define state-wise LWF rules. For each state, configure the employee share, employer share, contribution frequency, designated deduction months, wage threshold and the wage components used to test the threshold. Store the effective date of each rule so that historical payroll is not altered when a rate changes.

1. Configure exclusion logic. Add an eligibility flag driven by rules (wage above ceiling, designation category marked as managerial or supervisory, apprentice status) with an option for manual override with a documented reason.

1. Set cutoff rules. Define, per state, whether eligibility is tested on the last day of the period, on the payroll date of the designated month, or another basis. This drives the joiner and leaver treatment automatically.

1. Set the deduction schedule. Choose whether the employee share is deducted in full in the designated month or spread across the period, according to what the state permits and what your policy is.

1. Configure payslip display. Show the deduction with the state name so it is transparent to employees.

1. Enable state-wise reports. The system should produce an LWF register per state per period, an exclusion report, a challan-ready summary and, where required, an employee-wise statement in the board's format.

1. Set reminders. Configure alerts for the designated deduction month and the remittance and filing due date for each state.

1. Test before the first live run. Use a sample of employees in each state, including one excluded employee, one mid-period joiner and one leaver, and verify the outputs.

Handling rate changes

When a state revises its contribution amounts, add a new rule version with the effective date instead of editing the existing one. This preserves the audit trail and prevents retroactive changes to closed payroll periods. Good payroll platforms ship these updates as part of their statutory maintenance so that you do not have to track every notification yourself, but you should still verify that the update matches the board's notification.

Example: Kestrel Analytics

Kestrel Analytics, a fictional data consultancy, grew from one office to four states in eighteen months. Its first attempt at LWF used a spreadsheet with a column per state. It worked until an employee transferred from Delhi to Bengaluru mid-year and was deducted under both states' rules. After moving to a payroll system with state-mapped LWF rules and effective-dated transfers, the transfer scenario resolved itself: the employee's eligibility was assessed against the establishment they were mapped to on each state's cutoff date.

Annual LWF Compliance Calendar Template

Because due dates differ by state and are revised, the template below uses placeholders. Populate it once with verified dates from each board's website, review it every quarter, and assign each row to a named owner.

The month placements above reflect the pattern many half-yearly and annual states follow, but they are illustrative. Some states use different period boundaries, and due dates may fall in a different month than the one shown. Replace the placeholders with the dates confirmed for your states.

Common Mistakes in Labour Welfare Fund Compliance and How to Fix Them

Audit Tips for HR and Payroll Teams

Whether the audit is internal, from a customer, from an investor or from a labour inspector, the same preparation applies.

Build a state-wise LWF file

For each state, maintain a folder containing the registration certificate or code letter, the LWF matrix entry showing the rules applied, the LWF register per period, challans, returns and acknowledgements. An auditor who receives a well-organised file will typically test a sample and move on. An auditor who receives scattered spreadsheets will dig.

Reconcile three numbers

For each period and state, the total employee deductions in the payroll register, the employer share in the general ledger, and the amount on the challan should reconcile exactly. Differences usually point to a joiner, leaver or exclusion that was handled inconsistently. Investigate and document every difference, even small ones.

Test your exclusions

Pick a sample of excluded employees and confirm that the exclusion basis holds up: the wage comparison uses the right definition, the managerial classification reflects actual duties, and the exclusion is permitted in that state. This is the area most likely to draw questions.

Check transfers, contractors and changes

For employees who moved between states during the year, trace their LWF treatment period by period and confirm there is no double deduction and no gap. Keep contractor LWF challans on file for each period. Finally, maintain a change log recording every rate or rule change you applied, the source you relied on, the date it took effect and who approved it.

Frequently Asked Questions

Is labour welfare fund compliance mandatory for every company in India?

No. LWF applies only in states and union territories that have enacted a labour welfare fund law, and only to establishments and employees covered by that law. If all your employees work in a state without an LWF Act, there is no LWF obligation. If you have employees in a state that has an Act, you need to check whether your establishment type is covered, whether a minimum headcount applies and which employees fall within the covered categories. Applicability follows the employee's work location, so a company can be subject to LWF in one state and not in another at the same time.

How do I find the current LWF contribution amount for my state?

Go directly to the official website of the state labour welfare board for the state in question, or the state labour department's site where the board's information is hosted. Look for the latest notification on contribution rates, the prescribed forms and the payment portal. Amounts are set by state notification and revised periodically, so a figure from a blog or a forum post may be outdated. If you use payroll software with built-in statutory rules, confirm that its configured amount matches the board's current notification before you run the designated deduction.

What happens if an employee's salary is above the wage threshold?

In states that specify a wage ceiling, employees earning above it are generally excluded from the deduction and the corresponding employer share. The important detail is which wage components count for the comparison, since the Act may refer to a narrower definition than gross salary. Configure the threshold test in payroll using the correct components, keep a list of excluded employees with the basis for exclusion, and re-test eligibility each period because salary revisions can move an employee across the threshold. Some states have no wage ceiling at all, in which case all covered employees contribute regardless of salary.

Do we have to deduct LWF for an employee who joined in the last week of the contribution period?

It depends on how the state's rules define eligibility for the period. Many states tie the contribution to employees who are on the rolls on a specific cutoff date or in a designated month. If the employee is on the rolls on that date, the full period contribution usually applies, even if they joined only days earlier. Some states or employer practices apply a pro-rata approach, but this is less common for flat-rate contributions. Check the rule for your state, apply it consistently, and document the treatment in your LWF register.

Can the employer share of LWF be recovered from employees?

No. The employer contribution is a statutory cost borne by the company. It must not be deducted from wages or netted against any employee payment. Only the employee share, as prescribed by the state, may be deducted from salary. Treating the employer share as a payslip deduction is a compliance breach and also creates employee grievances. For internal accounting, post the employer share as a company cost to the appropriate cost centre, and if you include it in CTC breakups for offer letters, label it clearly as an employer contribution.

Who is responsible for LWF for contract workers deployed at our premises?

The contractor, as the employer of those workers, is primarily responsible for deducting, contributing, remitting and filing LWF in the state where the workers are deployed. However, principal employers carry a supervisory responsibility under the contract labour framework and can face consequences if the contractor defaults. Protect your organisation by including LWF in the contractor's contractual obligations, collecting challans and returns each period as a condition of paying invoices, and verifying that the contractor's filings actually cover the workers at your site in your state.

Will the new labour codes remove or change LWF?

The labour codes consolidate central labour laws, but state labour welfare fund Acts are state legislation and were not directly subsumed. That said, states may amend their welfare fund laws or the way they operate when they notify rules under the codes, and the standardised wage definition introduced by the codes could affect how thresholds are measured. Until a state formally changes its LWF rules, continue to comply with the existing Act. Monitor state notifications and verify the position with your advisor whenever your state announces rules under the codes.

How should LWF appear on the payslip?

Show it as a clearly labelled deduction, ideally with the state name, for example "Labour Welfare Fund (Gujarat)". In monthly-frequency states it will appear every month; in half-yearly or annual states it will appear only in the designated month, which can prompt employee questions if it is not explained. A short note in the payroll FAQ or the payslip footer explaining that LWF is a state-mandated welfare contribution collected once per period helps reduce queries. Never show the employer share as an employee deduction.

Conclusion

Labour welfare fund compliance is small in rupee terms and large in complexity, because it is a state-by-state obligation with different amounts, frequencies, thresholds and due dates. The employers who get it right are not the ones who memorise every rule, but the ones who build a system: employees mapped to their work-location state, rules stored with effective dates, designated deduction months triggered automatically, remittance and returns tracked separately, and evidence filed as it is produced.

Start by listing every state where you have people, verifying the current rules on each state board's website, and building the matrix and calendar in this guide. Then let your payroll system carry the load so that LWF becomes a routine part of month-end rather than a periodic scramble.

If you would rather not maintain that matrix by hand, CozyHR has state-wise LWF rules built into payroll, with work-location mapping, designated-month deductions, exclusion logic and challan-ready registers. Start a free trial and see how LWF compliance looks when the rules live in the system instead of in a spreadsheet.