Professional Tax (PT) trips up multi-state employers more than almost any other payroll item, because it is not a single national tax. It is levied by individual state governments under Article 276 of the Constitution, and the rules — whether PT applies at all, the slab values, the due dates and the return formats — differ from state to state.

Not every state levies PT

Several states and union territories do not levy Professional Tax at all — Delhi, Haryana, Uttar Pradesh, Uttarakhand, Rajasthan, and others have historically not imposed it. States that do levy PT include Maharashtra, Karnataka, West Bengal, Tamil Nadu, Andhra Pradesh, Telangana, Gujarat, Madhya Pradesh, Kerala and more. If you operate across states, you must check each state separately rather than assume a uniform rule.

The constitutional ceiling

Whatever a state’s slabs, the maximum Professional Tax is capped at ₹2,500 per person per year under Article 276(2). Within that ceiling, each state sets its own monthly slabs based on salary, and in some states a final-month adjustment applies so the annual total lands at the slab maximum.

Two registrations, two duties

Employers in a PT state typically need both:

• Professional Tax Registration Certificate (PTRC) — to deduct PT from employees’ salaries and remit it; and
• Professional Tax Enrolment Certificate (PTEC) — for the entity’s own PT liability.

The employer is responsible for deducting the correct slab amount from each employee’s salary, depositing it with the state, and filing the periodic PT return (monthly or annual depending on the state and the size of liability).

Where employers slip

• Branch blind spots: opening a branch in a new PT state creates a fresh registration and filing obligation that head-office payroll often misses.
• Wrong slab mapping: applying one state’s slab to employees physically working in another.
• Missed due dates: PT due dates are state-specific and do not align with EPF/ESI’s 15th.

A simple control

Maintain a state-by-state matrix: does PT apply, what are the current slabs, what is the return frequency, and what is the due date. Review it whenever you add a work location. A compliance calendar that is keyed to your actual operating states — rather than a generic template — removes most PT risk.

EPF and ESIC are the two social-security pillars most Indian employers deal with every month, and they are also the two most frequently confused. They are governed by different Acts, administered by different bodies, apply at different thresholds and are computed on different wage bases. Getting either wrong invites interest, damages and inspection notices. This guide sets them side by side.

Two different laws, two different administrators

The Employees’ Provident Fund is governed by the Employees’ Provident Funds and Miscellaneous Provisions Act, 1952 and administered by the EPFO. It is a retirement-savings scheme. The Employees’ State Insurance is governed by the Employees’ State Insurance Act, 1948 and administered by the ESIC. It is a medical and cash-benefit scheme for sickness, maternity, disablement and dependants.

Who is covered

EPF generally applies to establishments employing 20 or more persons (and to certain notified classes at a lower headcount). ESI generally applies to non-seasonal establishments employing 10 or more persons (20 in a few states for certain categories). Once an establishment is covered, it remains covered even if numbers later fall.

• EPF wage ceiling: mandatory coverage applies to employees drawing up to ₹15,000 per month (basic + DA). Above this, coverage is at the employer’s option, subject to the scheme rules.
• ESI wage ceiling: employees drawing up to ₹21,000 gross per month are covered (₹25,000 for employees with disability).

Contribution rates

The wage base and the split differ materially:

EPF also carries EDLI (life-insurance) and administrative charges on the employer. ESI is computed on gross wages, while EPF is computed on basic + dearness allowance. This single difference — gross vs basic — is where most calculation errors originate.

Filing and due dates

For EPF, the monthly Electronic Challan-cum-Return (ECR) is filed and contributions paid by the 15th of the following month. For ESI, contributions are likewise paid monthly by the 15th, with two defined contribution periods (April–September and October–March) that map to benefit periods. Every covered employee should have a UAN for EPF and an IP number for ESI.

The 50% wages point worth planning for

Under the Code on Wages, the statutory definition of “wages” requires that excluded allowances not exceed 50% of total remuneration. As this takes operational effect, the wage base for PF, gratuity and similar computations rises for salary structures that are heavily allowance-loaded. Employers with such structures should model the impact now rather than discover it at the first inspection.

The Labour Welfare Fund (LWF) is small in rupee terms and large in nuisance value. It is a state-administered contribution toward worker welfare, and like Professional Tax, it has no single national rule. Whether LWF applies, who contributes how much, and how often, all depend on the specific state’s Labour Welfare Fund Act.

Why there is no one LWF rule

LWF is levied by individual states and union territories — roughly a dozen-and-a-half of them operate a fund — each under its own statute. That means three things vary by state:

• Applicability and thresholds — which establishments and which categories of employee are covered.
• Contribution amounts — the employee share and the (usually larger) employer share.
• Frequency and due dates — some states collect monthly, others half-yearly (commonly with June and December cycles), others annually.

The employer’s duties

• Determine LWF applicability for each state you operate in.
• Deduct the employee share, add the employer share, and remit to the state board.
• Meet the state-specific frequency — mixing up a half-yearly state with a monthly one is a common slip.
• Keep proof of remittance for inspection.

Where multi-state employers trip

The recurring failures are familiar from PT: a new branch in an LWF state that head office forgets to register; a half-yearly due date that quietly passes; the wrong state’s rate applied. The amounts are minor, but missed remittances accrue and surface awkwardly in audits and inspections.

Keeping LWF boring

LWF should be uneventful. The way to make it so is a state-keyed calendar: for each operating state, does LWF apply, what is the current contribution, what is the cycle, when is it due, and who owns it. Reviewed whenever you add a location, that single control retires most LWF risk.