Form 3CD Clause 20(b): PF and ESI Late-Payment Checks for AY 2026-27
For employee contributions, the important deadline is the due date under the relevant welfare-fund law. Payment before the income-tax return deadline does not cure a late employee contribution under section 36(1)(va). Keep employer contributions separate: they have a different tax test. Section 36(1)(va), including Explanation 2.
Clause 20(b) reports contributions received from employees for the relevant funds. For FY 2025-26 / AY 2026-27, build the schedule from payroll, contribution records and settlement evidence, rather than treating the year-end payable balance as the complete answer. Department's tax-audit reporting summary.
Sources checked: 7 September 2026. The amounts and dates below are illustrative; check the applicable fund, wage period and any valid period-specific extension before determining a real liability.
Separate the employee deduction from the employer expense
The bank often shows one combined payment. That does not make every component subject to the same income-tax provision.
| Component | Audit analysis |
|---|---|
| Amount deducted or received from employees for the fund | Employee-contribution test under section 36(1)(va); Clause 20(b) schedule |
| Employer contribution | Separate section 43B analysis and applicable reporting |
| Interest, damages or administrative charges | Identify separately and assess the relevant treatment |
Section 43B expressly excludes the employee contributions described in section 2(24)(x) from its operation. Do not apply an employer-contribution payment rule to the whole challan. Section 43B, Explanation 5.
A good starting export therefore has separate columns for employee amount, employer amount, other charges and total payment. Reconcile those columns to the payroll deduction ledger and the challan details before assessing dates.
Use one line for each fund and liability period
The schedule should identify the establishment, fund, payroll period, employee amount, applicable due date, amount paid and actual payment date. Link the challan and payment evidence. Include a reference for any extension used.
Add reviewer fields for unmatched payments, duplicate challans, partial settlement and disallowance. These fields make it possible to see whether a zero in the final schedule means “tested and paid on time” or “evidence not yet received.”
A challan creation date is not, by itself, proof of payment. Check the successful settlement evidence and the date legally relevant to the contribution. If records conflict, resolve the difference before choosing a date for the report.
Worked example: part paid on time, part paid late
Assume an employee contribution of ₹1,20,000 has a verified due date of 15 May 2025, with no applicable extension. Reliable records show:
| Amount | Actual payment date | Result under the assumed facts |
|---|---|---|
| ₹90,000 | 14 May 2025 | Paid within the due date |
| ₹30,000 | 20 May 2025 | Paid after the due date |
The employee-contribution amount failing the due-date test is ₹30,000. Do not use the earlier payment date for the full ₹1,20,000, and do not disallow the timely ₹90,000 merely because the second instalment was late.
An export format with only one amount/date pair per row may need separate payment lines or an attached reconciliation. Check that the representation in the utility preserves the underlying facts.
If the full amount had been paid on 20 May, the full employee amount would fail the assumed due-date test even though it was paid long before the income-tax return deadline.
A nil year-end payable does not prove there were no late payments
An employee contribution can be paid late during the financial year and disappear from the closing liability. Reviewing only the March balance misses it.
For example, a May liability settled late in June produces no outstanding balance on 31 March. It still belongs in the year-wide payment-date review. Obtain all relevant periods, including payments after year-end that settle liabilities in the audit period.
Reconcile opening liability, current-period contributions, payments and closing liability. Then perform the due-date analysis on the underlying periods. The balance reconciliation and the deduction test are both necessary, but they answer different questions.
Common review failures to catch
- Using the bank debit for the combined challan without splitting employee and employer amounts.
- Carrying forward last year's due-date assumptions without checking the relevant period.
- Taking challan generation as successful payment evidence.
- Marking a partly paid liability as fully paid using the first instalment date.
- Ignoring late payments because the year-end balance is nil.
- Adding the same disallowance again when the tax computation already includes it.
Keep the final tax computation cross-reference beside the schedule so the reviewer can confirm the amount is reflected once. A representation that “all dues are paid” is not a substitute for the payment-date evidence.
Prepare the calculation and retain the evidence
The Clause 20(b) calculator helps organise employee contributions, due dates and payment dates. For instalments or disputed dates, retain the detailed payment reconciliation with the calculation.
Use the tax audit document request checklist to request the payroll and fund records together. The Form 3CD clause index can link the final schedule, computation and review note.
Frequently asked questions
Does payment before the ITR due date rescue late employee PF or ESI?
No. The employee-contribution test uses the relevant welfare-law due date; section 43B does not override that test.
Can a zero PF/ESI balance at year-end mean no disallowance?
Not necessarily. Contributions may have been paid late earlier in the year. Test the actual payment history for the relevant periods.
How should missing payment evidence be handled?
Keep the item unresolved, request the fund and settlement records, and document the reporting consequence if the evidence remains unavailable. Do not manufacture a payment date to complete the table.