Payroll Compliance: PF, ESIC and TDS

Quick View

Why It Matters

Applicability for PF, ESIC and other labour requirements depends on current law, establishment facts, employee coverage and wage definitions. Thresholds and ceilings should be checked rather than copied from an old payroll file.

Salary TDS requires a year estimate, declarations, evidence where applicable, prior-employer income and final reconciliation. Income arising before and after the 1 April 2026 tax transition must use the correct legal period and forms.

Payroll data includes sensitive identity and bank information. Access should be restricted, changes independently approved and final payment reconciled to the bank and general ledger.

Control Framework

Action Checklist

1. Lock payroll input deadlines.
2. Review joiners, exits and master changes.
3. Reconcile attendance and approved pay.
4. Validate statutory applicability and calculations.
5. Pay and file through official portals.
6. Reconcile payroll ledger to bank and returns.

Practical Example

Evidence to Keep

• Employment contract and salary approval.
• Employee master change log.
• Attendance and leave data.
• Payroll computation and review.
• Challans, returns and acknowledgements.
• Bank payment and ledger reconciliation.

Warning Signs

Management Decision

Maintain an applicability memo for every state and employee category. Update it after headcount, wage, location or legal changes.

Report old statutory differences and employee recoveries monthly. Small payroll errors repeated across many people can become material.

Document the decision, owner, due date and evidence expected. A verbal explanation should be converted into a board note, approved working, contract amendment, portal acknowledgement or reconciliation before the item is treated as closed.

Rules, forms, thresholds and interpretations can change. The operating team should use the latest official source and the actual company facts instead of copying a control from another entity or prior year.

Monthly Review Test

Ask four questions: Is the obligation or accounting treatment applicable? Has the underlying transaction been completely recorded? Does the evidence agree with the books and portal? Has an independent reviewer challenged the exception?

The review should distinguish a timing difference from an error, a judgement from a missing document, and a control failure from a one-time operational delay. Repeated small exceptions deserve root-cause action because they often become material during audit, fundraising, notice or distress.

Exception Review

The operating record should connect the control stages—employee master, gross-to-net, statutory layer, exit layer—to the same transaction population. If the source list, accounting ledger, tax return, board record and management dashboard use different populations, the review can appear complete while exceptions remain outside the test.

Management should define an exception threshold, but the threshold must not hide repeated failures. A small error occurring every month can signal weak master data, unclear ownership or a broken interface. The reviewer should record root cause, immediate correction and preventive action separately.

Closure requires evidence. At minimum, the file should show who prepared the work, who reviewed it, which source documents were used, what differences remained and when the next follow-up is due. Screenshots without context or spreadsheets without source references are not a durable control record.

Tag every working with the legal entity, tax period and governing law. The filing date alone does not decide which Act, rate, form or limitation period applies, especially during the 2026 income-tax transition or where a notice covers earlier GST periods.

Portal data should be downloaded and preserved with the filing version. Later supplier corrections, updated statements or portal changes can otherwise make it difficult to prove what information management used when the return or response was approved.