Challans

Payroll withholds money that does not belong to the employer: tax, provident fund contributions, state insurance contributions, professional tax, labour welfare fund. Each of those has to reach the authority that collects it, and each authority accepts payment through its own instrument. That instrument is the challan.

The definition sounds administrative, and the consequence is not. A challan is a record that a sum was paid by a payer for a period, and that is all it is. It does not say whose tax or whose contribution it was. An employer can deposit every rupee correctly and on time, and no employee will see the benefit until a separate return maps that deposit to individual names and account numbers.

Holding the two apart is the whole discipline here. Payment and reporting are different obligations with different deadlines, and being right about one says nothing about the other.

A typical Indian payroll pays four or five of these every month, to four or five different authorities, on deadlines that do not coincide.

Confirm the due date for each against the statute and state in force, since they differ and several have been revised.

Two of these behave differently from the rest. Provident fund payment is tied to a statement that already carries member-wise detail, so payment and reporting travel together. Tax deducted at source is the opposite: the payment is entirely anonymous and the reporting happens up to three months later, which is why it produces most of the reconciliation work.

When a tax payment is made through a bank, the payment is stamped with an identifier made up of the bank branch code, the date of deposit and a serial number for that day. Together these form the challan identification number, and it is the reference the quarterly TDS return uses to say which deposit each employee's deduction came out of.

Government deductors who pay by book adjustment rather than through a bank receive a book identification number instead, which serves the same purpose in the return.

The reason this matters to payroll rather than only to accounts is that the return will not reconcile without it. Every deduction reported in the return has to point at a challan, and the total of the deductions pointing at a challan cannot exceed what that challan paid. Where the identifier is entered wrongly, or the challan is claimed for more than it holds, the statement is processed with a short payment default even though the money is sitting with the government.

Keep the identifier with the payment record at the time of payment. Reconstructing it in the week the return is due, from bank statements, is a recurring and avoidable exercise.

Each statute has its own reconciliation, and each should be run before the corresponding return is filed rather than after.

• Tax deducted at source. Total deductions reported for the quarter must equal the total of the challans claimed for it. Check also that the assessment year and the section codes on the challan match the deductions being mapped to it.
• Provident fund. The contribution the electronic statement computes must match the payment made against it, and the member-wise total must reconcile to the payroll register for the month.
• State insurance. The contribution declared must match what was paid, and the employee count on the declaration should reconcile to the payroll for the period.
• Professional tax and labour welfare fund. The amount paid per state must reconcile to the employees attributed to that state, which is where multi-state payrolls come unstuck.

The general rule is that a challan reconciles to a return, not to a bank statement. A payment that ties to the bank and not to the return is still a problem, because the return is what the authority reads.

Challan errors are unusually expensive because they are quiet. The money leaves the account, so nothing looks wrong until a return fails to reconcile or an employee finds a missing credit.

• Wrong assessment year. The payment lands in the wrong year and cannot be claimed against the return for the period it was meant for.
• Wrong section or nature of payment code, so a deduction under one section is paid under another and the mapping fails.
• Wrong tax deduction account number, common where a group operates several. The payment is credited to a different deductor entirely.
• Wrong minor head, so a regular monthly payment is recorded as a payment against a demand, or the reverse.
• Wrong establishment or registration code for provident fund or state insurance, in groups with more than one registration.
• Rounding and part payments, where the challan is short of the liability by a small amount that nobody notices until a default notice arrives.

Most of these can be corrected, through the collecting authority or through a correction in the return, but each correction costs weeks. Verifying the header fields before the payment is released is the cheapest control available.

Challans are evidence, and they are asked for long after the year has closed. Retain, for each period and each statute, the challan or receipt with its identifier, the return or statement it was claimed in, and the payroll register the amount was computed from.

Keep them in a way that supports the question actually asked, which is almost never "show me the payment for March". It is usually one of these.

• An employee's provident fund account is short for a period, and the question is whether the contribution for that month was paid and reported.
• A tax credit is missing from an employee's Form 26AS, and the question is which challan their deduction was mapped to and whether the return quoted it correctly.
• An inspection asks for state insurance contributions for a half year, employee by employee.

Storing challans by statute and period, with the return reference alongside, answers all three in minutes. Storing them as a folder of bank receipts answers none of them.