One Challan, Two Sections: PF and ESI After Checkmate

One payment. Two halves. Two completely different sections, two different due dates, and one of them has no second chance.

The PF and ESI challan your client pays every month covers the employer's contribution and the employee's contribution together. It is a single transfer, it is posted as a single entry in most ledgers, and it is governed by two provisions that do not behave alike at all.

The split

The employer's share is the firm's own contribution. It falls under section 43B(b), and 43B carries a proviso: pay it by the due date for filing the return under section 139(1) and the deduction stands.

The employee's share is not the firm's money at all. It is deducted from the employee's salary, which makes it income in the employer's hands under section 2(24)(x), and it becomes deductible under section 36(1)(va) only if deposited by the due date under the relevant fund's own law.

That is the fifteenth of the following month for PF. March's deduction is due by 15 April.

And section 36(1)(va) has no proviso relief. Paying in September, before the return is filed, does not save it. The Supreme Court settled this in Checkmate Services, and the position since then has been unambiguous: the two halves of one challan are tested against two different clocks, and a late deposit of the employee share is disallowed permanently — it does not even move to the year of payment.

The employer share paid late is deferred. The employee share paid late is gone.

Why ledgers make this hard

The provision is clear. Finding the number is not, and the difficulty is entirely about how the books are kept.

Most clients maintain one ledger. "PF Payable". "ESI A/c". "Provident Fund". The challan hits it, the salary journal hits it, and the two shares are never separated anywhere in the accounts. To split them you need the payroll working, not the ledger.

Where clients do split, the naming is unpredictable. "PF — Employer" and "PF — Employee" is the tidy case. Real ledgers say "PF Ees", "Staff PF Contribution", "PF Own Share", "EPF Members Contribution", "Workmen PF". A review that looks for the word employee misses most of them, and every one it misses is an understated add-back under 36(1)(va).

The failure is asymmetric, which is what makes it dangerous. Miss an employer-share ledger and you have over-disallowed something the proviso would have saved. Miss an employee-share ledger and you have under-disallowed something with no remedy at all.

The month that gets forgotten

There is a timing trap that catches otherwise careful files.

The March deduction is due by 15 April — after the year end. Whether it was deposited in time is a fact that lives in the next financial year's books, and if you are only looking at the year under audit, you cannot see it.

Firms handle this by asking the client, taking the answer, and moving on. That answer is frequently wrong, not dishonestly, but because the person answering is recalling a challan from eleven months earlier.

The same problem runs the other way for every month: a deduction made in a month and deposited a few days late is a disallowance even though the annual total of deductions and deposits agrees perfectly. Testing the year foots nothing.

How Audcrix runs it

Audcrix separates the two shares before it computes anything, and routes each to its own section.

• Employer share goes to 43B(b), with the section 139(1) proviso available. Employee share goes to 36(1)(va), tested against the fund due date, with no proviso relief.
• Ledger identification goes well beyond the word "employee" — worker, staff, member and the abbreviated forms clients actually use, because a missed employee-share ledger is the expensive direction of the error.
• Where a ledger genuinely cannot be split, the row is flagged for the CA to route, and the head override then drives the clause and the routing together rather than only relabelling the line.
• March deposits are read from the following financial year's books where that year has been synced, so the 15 April question is answered from the challan rather than from memory.
• The test runs month by month, so a deduction deposited late in a single month surfaces even when the annual totals agree.

Where the evidence is not available — no next-year sync, no payroll split — the position is reported as unresolved with the reason stated. A 36(1)(va) add-back is not a number to infer. Getting it wrong in one direction costs the client a deduction they were entitled to; getting it wrong in the other leaves an exposure in a file with your signature on it.

Audcrix is audit and compliance intelligence for Indian CA firms. Everything between the books and your signature. See how it works.