Statutory Payroll Compliance (PF, ESI, PT, TDS): Who Needs It and Who Does Not
Whether Statutory Payroll Compliance (PF, ESI, PT, TDS) applies to a given business is the first thing worth settling, and it is where most of the early questions land. The questions below are the ones raised most often in practice; the full scope of the service is on the Statutory Payroll Compliance (PF, ESI, PT, TDS) page.
What exactly is covered under 'statutory payroll compliance' — is this the same as running payroll?
No. Running payroll is computing gross-to-net salary and generating payslips. Statutory payroll compliance is the narrower but higher-stakes function of correctly deducting, depositing, and reporting the four mandatory withholdings that arise from that payroll run: Provident Fund (EPF), Employees' State Insurance (ESI), Professional Tax (PT), and Tax Deducted at Source on salary (TDS). PNPC offers both as an integrated service, but a business that already runs its own payroll computation can engage PNPC purely for the statutory compliance layer — the deposits, returns, registrations, and inspection responses across all four regimes.
In practice: Many businesses already have functioning in-house payroll software but no one with the specific statutory expertise to manage EPFO, ESIC, state PT, and TRACES correctly across four different portals and four different rule sets.
Do all four — PF, ESI, PT, and TDS — apply to every business from day one?
No. TDS on salary applies from the first employee whose estimated tax for the year, after rebate and declared deductions, is above nil — so an employer should check it from the first hire. Professional Tax, where the state levies it, has no minimum employee threshold — it applies from the first employee above the state's nil-PT slab. Under the Code on Social Security, 2020 (in force since 21 November 2025), ESI applies to establishments with 10 or more employees and EPF to establishments with 20 or more; wage ceilings determine which employees are covered, so confirm the current notifications with ESIC and EPFO. A small business with 5 employees in Bangalore is therefore likely subject to TDS and Karnataka PT immediately, but not yet to ESI or EPF.
In practice: We map exactly which of the four regimes currently apply — and which will apply as headcount grows — at the very first client meeting. This avoids both under-registration (missing an obligation that already applies) and unnecessary early registration (voluntary EPF/ESI before it makes business sense).
How does Professional Tax differ so much between states — and how do you manage that for a multi-state employer?
Professional Tax is entirely state legislation with no central coordination. Several states and union territories — for example Delhi, Uttar Pradesh, Rajasthan and Haryana — do not levy it (Punjab levies a similar monthly State Development Tax instead); confirm the current position for each state. An employer with offices in three PT-levying states runs three fully independent PT compliance tracks. PNPC operates from Chennai, Bangalore, and Hyderabad specifically to manage Tamil Nadu, Karnataka, and Telangana PT with CA teams physically present in each state, consolidated into a single quarterly report for the client.
In practice: We treat each state's PT as its own compliance track with its own calendar, even though it is reported to the client as one consolidated statement. Conflating the three states' due dates and slab logic into a single generic process is a common source of PT errors in businesses that manage this in-house across multiple locations.
Does Professional Tax apply to salaried directors?
Yes. Directors who receive a salary or remuneration as working or whole-time directors are treated as employees for Professional Tax purposes in every state that levies PT — their remuneration is included in the gross salary on which the PT slab is applied, in the same way as any other employee. Directors who receive only sitting fees (not a recurring salary) are generally not subject to employee-side PT deduction on those fees, though the company's own entity-level PTEC obligation (in Maharashtra and Karnataka) remains regardless of director compensation structure.
In practice: We include working directors in the PT deduction roster of every payroll we manage. This is sometimes overlooked by businesses that mentally separate 'director remuneration' from 'employee payroll' for internal accounting purposes, even though PT law does not make that distinction.
What happens during full-and-final settlement for an exiting employee — does it touch all four regimes?
Yes. EPF and ESI both require the employer to mark the employee's exit on the respective portal with the correct date and reason, enabling the employee's withdrawal or transfer claims. Professional Tax is applied on the employee's actual gross salary for the exit month (and, for Tamil Nadu, computed on the actual salary earned within the half-year up to the exit date, not a full half-year figure). TDS is recomputed on the final settlement components in the exit month and reflected in the employee's annual TDS certificate. Each of these four steps depends on the same exit data (last working date, final salary, settlement components) being applied consistently across all four systems.
In practice: Exit processing is one of the highest-error points in statutory payroll compliance precisely because it requires simultaneous, consistent action across all four regimes from a single data set. We treat every exit as a dedicated checklist item spanning EPF, ESI, PT, and TDS rather than a single generic 'FnF' task.
Is there a minimum headcount below which none of these four obligations apply?
No single minimum applies across all four — each regime has its own threshold, and Professional Tax (where levied) has none at all. TDS on salary can apply from the first employee, once that employee's estimated tax for the year (after rebate and declared deductions) is above nil. Professional Tax, in states that levy it, applies from the first employee earning above the state's nil-PT slab, with no minimum employee count. Under the Code on Social Security, 2020, ESI applies at 10 employees and EPF at 20 employees. A business with 3 employees in a PT-levying state can already be subject to two of the four regimes (PT, and TDS where salaries are taxable) despite having a headcount far below the EPF and ESI thresholds.
In practice: We map applicability against actual headcount and geography at the outset of every engagement rather than assuming a single threshold applies uniformly — a single uniform threshold is a common misconception.
If our company has zero revenue or is pre-launch, do any of these four obligations still apply?
None of the four apply until salary is actually paid to an employee — revenue or profitability of the business is irrelevant to the trigger. A pre-revenue startup that has hired its first paid employee can already have a salary TDS obligation (section 392 of the Income-tax Act 2025 from tax year 2026-27, formerly Section 192) if the employee's estimated tax is above nil and, if operating in a PT-levying state, a Professional Tax obligation from that first employee, regardless of the company's financial position. EPF and ESI remain dormant until the respective headcount thresholds are reached.
In practice: Early-stage founders often assume statutory payroll obligations only begin once the business is generating revenue. The trigger is the payment of salary, not profitability — we flag this at the very first hire, not once revenue starts.
Why should we choose PNPC over engaging separate specialists for PF, ESI, PT, and TDS?
A separate specialist for each regime is a defensible model in isolation, but it creates a structural blind spot: no single person or firm sees the complete monthly payroll data applied consistently across all four sets of rules. PNPC's model is to receive one monthly data submission and apply all four regimes' computations to it within a single reviewing team, so that a data error, a wage-base inconsistency, or a mid-year change is caught once, centrally, rather than potentially missed by three of four specialists who each only see their own slice. This is not a claim that individual specialists are less competent — it is a structural argument that integration catches a class of error that specialisation, by its nature, cannot.
In practice: Even where each individual PF, ESI, and TDS consultant is competent, cross-regime inconsistencies can arise that none of them has the visibility to catch individually. The value of integration is specifically in what falls between the cracks of otherwise good individual work.
What if our payroll headcount fluctuates — for example, we cross the EPF threshold, then drop below it later. Does the obligation end?
No. Once EPF coverage is triggered by crossing the 20-employee threshold — even on a single day — the establishment remains permanently covered, regardless of whether headcount later falls below 20. The same principle applies to ESI once the applicable threshold is crossed. There is no de-registration mechanism for a temporary or even sustained drop in headcount; the only way to end the obligation is a formal establishment closure with all dues settled and the appropriate closure intimation filed with each authority.
In practice: This misunderstanding is most likely in businesses with seasonal or project-based headcount swings. Crossing the threshold even briefly during a peak period creates a permanent obligation — we flag this proactively before a client makes hiring decisions that could inadvertently trigger it.
Where this sits in the wider engagement
Statutory Payroll Compliance (PF, ESI, PT, TDS) rarely arrives on its own. The statutory basis and the current requirements are set out on the Statutory Payroll Compliance (PF, ESI, PT, TDS) service page, and the related services are grouped under Accounting Payroll.
What PNPC does
PNPC Global has practised since 1986 across India and the UAE. On Statutory Payroll Compliance (PF, ESI, PT, TDS) we take the work end to end — reviewing the facts, preparing and filing what is required, and dealing with the authority through to closure.