Statutory Payroll Compliance (PF, ESI, PT, TDS): The Process, Start to Finish
The mechanics of Statutory Payroll Compliance (PF, ESI, PT, TDS) are what clients ask about once they have decided to proceed. 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 is the single biggest risk of managing PF, ESI, PT, and TDS through four separate vendors instead of one firm?
The four regimes do not communicate with each other, and neither, typically, do four separate vendors. A payroll data error — an incorrect basic salary entered for one employee in one month — will produce four different downstream errors: wrong EPF contribution, wrong ESI contribution, wrong PT slab application, and a skewed TDS projection. If four different specialists each see only their slice of the data, none of them is positioned to notice that the same root error is repeating across all four filings. A single integrated function reconciles the same underlying payroll data against all four computations every month, which is the only reliable way to catch this class of error before an external authority does.
In practice: We have taken over statutory payroll compliance from clients previously using four separate vendors on multiple occasions, and in nearly every case found at least one systemic data error that had been silently propagating across two or more of the four regimes for months or years before we caught it.
How is TDS on salary different from PF, ESI, and PT — why does it sit with the Income Tax Department rather than a labour authority?
TDS on salary is fundamentally a tax-collection mechanism, not a social-welfare contribution — it is an advance collection of the employee's own income tax liability, administered by the Income Tax Department under the TDS provisions of the Income-tax Act (the Income-tax Act 1961 for periods up to 31 March 2026, and its successor, the Income-tax Act 2025, thereafter). PF, ESI, and PT are welfare or state-revenue contributions administered by labour or state tax authorities. TDS requires a TAN (not the EPFO or ESIC codes), is computed on projected annual taxable income under the employee's elected tax regime rather than a flat percentage of a wage base, is deposited monthly by the 7th of the following month (except March deductions, which are due by 30 April), and reported via a quarterly salary-TDS return rather than a monthly ECR or challan-based return.
In practice: Because TDS sits in a completely different regulatory universe from the other three, it is the regime most often managed separately from PF/ESI/PT even within otherwise integrated payroll functions. We deliberately keep it in the same monthly reconciliation cycle as the other three specifically to catch cross-regime data inconsistencies early.
What is the old regime vs new regime choice, and how does it affect the TDS component of statutory compliance?
The employer deducts salary TDS based on whichever tax regime the employee elects — the old regime (with deductions such as 80C-type investments, HRA, and home loan interest) or the new, lower-slab-rate regime with fewer deductions, which has been the default since FY 2023-24 and continues as the default under the Income-tax Act 2025. The employee declares this election in the prescribed investment-declaration form and may switch once during the financial year. This choice has no bearing on EPF, ESI, or PT computation — those three regimes are unaffected by the employee's regime election — but it materially changes the monthly TDS amount and requires a mid-year recomputation for the remaining months if the employee switches.
In practice: We compute both regime liabilities for each employee at the start of the year and at joining, and flag the more beneficial choice — this is advisory work that payroll software does not perform on its own. The difference depends on the employee's income and deductions.
What is Form 24Q and how does it relate to Form 16?
Form 24Q was the quarterly TDS return specifically for salary payments under the Income-tax Act 1961, filed on TRACES for each of the four quarters (31 July, 31 October, 31 January, and 31 May for Q4). The Q4 filing included Annexure II — the consolidated, full-year tax computation for every employee — which was the source data from which Form 16 (the annual TDS certificate given to each employee) was generated. Form 16 had two parts: Part A, downloaded directly from TRACES after the Q4 return was accepted, and Part B, prepared by the employer with the detailed salary and deduction breakup. Both were issued to employees by 15 June. With the Income-tax Act 2025 in force from 1 April 2026, this quarterly return and annual certificate have been renumbered under a new form series with the same underlying function and the same 15 June annual issuance deadline; PNPC applies the correct form series for the relevant tax year and continues to use the widely-recognised 'Form 24Q' and 'Form 16' terminology where it aids client understanding.
In practice: A correction needed in the Q4 salary annexure after the annual certificate has already been issued requires a revised quarterly return and a reissued certificate — we run a pre-filing reconciliation specifically to avoid this before Q4 submission, and we track the FY 2025-26 to FY 2026-27 form transition closely for every client.
Can PNPC take over statutory payroll compliance mid-year, or does it need to start from the beginning of a financial year?
PNPC can onboard at any point in the financial year. The onboarding process for a mid-year takeover includes a review of the prior period's EPF, ESI, PT, and TDS records to confirm consistency, identification of any gaps or errors in the preceding months (a common finding when a business is switching from in-house or a previous vendor), and a plan to regularise any identified gaps before the ongoing monthly cycle begins. Waiting for a new financial year is not necessary and, if compliance issues already exist, is not advisable — the exposure continues to accrue interest and damages while unaddressed.
In practice: We have onboarded clients mid-quarter and mid-year on multiple occasions. The first engagement task is always a backward-looking reconciliation of the prior months' compliance across all four regimes, so that the ongoing cycle starts from a known-clean baseline rather than carrying forward an unquantified risk.
What is the realistic cost of getting statutory payroll compliance wrong across all four regimes?
Beyond the direct statutory cost, there is the professional cost of regularisation, management time diverted to inspections and notice responses, and — for EPF and ESI wilful defaults — the personal exposure of directors under the respective criminal provisions, now housed within the Code on Social Security 2020.
In practice: We quantify this trade-off explicitly for prospective clients who are weighing outsourced compliance against continuing an ad-hoc in-house approach. The comparison is rarely close once the compounding interest, damages, and professional regularisation cost are laid out against the retainer fee.
How does PNPC handle statutory payroll compliance for a business with employees in both India and the UAE?
PNPC has operating offices in Chennai, Bangalore, Hyderabad, and Dubai. Indian statutory payroll — EPF, ESI, state Professional Tax, and Section 192 TDS — is managed from our India offices. UAE payroll — Wage Protection System (WPS) compliance, end-of-service gratuity computation under UAE Labour Law, and UAE Corporate Tax payroll reporting — is managed by our Dubai office. For businesses with entities or employees in both jurisdictions, PNPC coordinates both under a single engagement rather than requiring the client to brief two separate firms in two countries.
In practice: India-UAE payroll coordination is a specific area we handle regularly. The two jurisdictions have entirely different statutory frameworks, and having one firm manage both prevents the context loss that occurs when a client has to separately brief an Indian CA firm and a UAE payroll provider on the same underlying business.
What is PNPC's process for taking over statutory payroll compliance from a business that has been managing it in-house?
The onboarding process begins with a comprehensive review of the prior 12 months (or since the establishment's most recent registration, whichever is shorter) across all four regimes: EPFO ECR history reconciled against the passbook, ESIC contribution history reconciled against monthly online contribution filings and challans, PT deduction registers reconciled against filed returns and Form 16 disclosures, and TRACES 26AS credits reconciled against filed 24Q returns. Any discrepancy identified is quantified and a regularisation plan is proposed before the ongoing monthly cycle begins. This upfront review is what allows PNPC to take over compliance with a known, documented starting position rather than an assumed clean slate.
In practice: We have found material discrepancies — usually in the ESI or EPF wage-base computation — in the majority of new client onboarding reviews. Surfacing this at onboarding, on our terms and timeline, is materially better for the client than having it surface during an inspection.
What does PNPC's statutory payroll compliance package actually include?
Registration or verification of EPFO Establishment Code, ESIC Employer Code, state PTRC/PTEC, and TAN. Monthly EPF ECR preparation and deposit by the 15th. Monthly ESI contribution computation and deposit by the 15th. Professional Tax deduction and deposit per each applicable state's own schedule. Monthly Section 192 TDS computation (old vs new regime) and deposit by the 7th. Cross-regime reconciliation of the same underlying payroll data every month. Quarterly Form 24Q filing. Quarterly consolidated multi-state PT reporting. Year-end Form 16 issuance (Part A + Part B) by 15 June. Response to any EPFO, ESIC, state PT, or Income Tax notice, demand, or inspection across all four regimes. A single monthly data submission process for your team, replacing four separate vendor relationships.
In practice: Everything above is included within the agreed fixed retainer fee. There is no additional charge for notice responses, inspection representation, or query resolution within the scope of the engagement — this is deliberate, because a compliance service that charges extra when problems arise creates a perverse incentive to under-invest in prevention.
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.