IT Declaration

An employer paying salary has to deduct tax every month, and Section 192 requires that deduction to be based on the estimated income of the employee for the whole financial year at the average rate. Estimating the year in April means knowing things the employer has no way of seeing: whether the employee pays rent, holds a housing loan, is repaying an education loan, has joined mid-year from another employer, or earns interest elsewhere.

The IT declaration is how the employee supplies those facts. Payroll takes the declaration, projects the year's taxable income after the claims, works out the tax, divides it across the months remaining and deducts accordingly. Nothing about it is a payment or a filing. It is an input to an estimate.

The word declaration is doing real work here. What the employee submits in April is a statement of intent, not evidence. The evidence comes later, and the gap between the two is where nearly all the friction in the annual cycle sits.

A complete declaration has four parts, and payroll teams that collect only the second one create work for themselves later.

The fourth row carries a restriction worth knowing. An employee may furnish particulars of other income so the employer can take it into account, but doing so cannot reduce the tax deducted from salary below what it would otherwise have been. The single exception is a loss under the head income from house property, which can reduce it, and that loss is itself capped for set-off against other income. So declaring bank interest raises the monthly deduction, and declaring housing loan interest on a let-out property may lower it, up to the cap.

Most employers run four stages, and the dates vary by company rather than by statute.

• April, or the joining month. The employee records a regime choice and submits the declaration. Payroll applies it from the first run, so TDS is lower from month one rather than being over-deducted and refunded later.
• Through the year. Revisions are allowed as circumstances change, and each revision reprojects the tax across the months still to run.
• December or January. Payroll calls for proof. Claims with evidence stand, claims without evidence are removed from the estimate.
• February and March. The corrected tax is recovered from the last payslips, and the year is closed out into Form 16 with Form 12BB and Form 12BA behind it.

Take an employee who declares 1,50,000 under 80C in April and proves nothing in January. Payroll has been deducting on an income lower by 1,50,000 for nine months. That relief is now withdrawn for the whole year, and the tax on it has to come out of two payslips rather than twelve. At a thirty percent slab the correction is roughly 45,000, plus cess, arriving in February. The employee reads it as a payroll error. It is arithmetic working exactly as designed.

The claim is disallowed for TDS purposes and the shortfall is recovered from the remaining months. That is the whole of the consequence at the payroll end, and it is a cash flow event rather than a loss of the deduction.

An employee who actually made the investment can still claim it when filing their income tax return. The return computes the correct tax on the full year, sets the TDS already deducted against it, and refunds the difference. What the employee has given up is the use of that money between February and whenever the refund lands.

The employer's position is the opposite. Allowing a claim without holding evidence for it exposes the employer to short deduction, with interest under Section 201(1A) and consequences for the deductor rather than for the employee. Section 192(2D) puts the duty to obtain evidence on the employer explicitly. That is why proof deadlines are enforced rigidly, and it is worth explaining that to employees who read the deadline as an internal preference.

The default regime carries lower slab rates and withdraws most exemptions and deductions, including house rent allowance, leave travel concession and the bulk of Chapter VI-A. Under it, a detailed declaration changes very little. Under the alternative, the same declaration can be worth a large amount.

Two practical points follow. First, the regime applies by default where the employee records nothing, so an employee who submits a full declaration and never confirms a regime can find none of it applied and be unable to understand why. Collect the regime choice and the declaration in the same step. Second, the comparison is specific to the employee's own numbers. An employee paying substantial metro rent with a housing loan and a full 80C often lands better under the alternative, while an employee with no rent and no investments almost never does. A blanket recommendation from HR is the wrong instrument here.

A salaried employee without business income is generally able to choose afresh each year when filing, so the choice recorded with payroll governs the deduction rather than fixing the final liability. Confirm the current position on switching before advising anyone, since the rules around it have changed more than once.

The declaration cycle is largely a communication problem wearing a compliance costume, and a handful of practices remove most of the pain.

• Collect the regime choice as a required field rather than an optional one, before the first payroll run of the year.
• Ask a mid-year joiner for Form 12B at onboarding. Without it, both employers apply the standard deduction and work up the slabs from the bottom on their own slice, and the employee is left with tax payable at filing.
• Show the projected annual tax and the month-by-month deduction on the payslip or the self-service portal, so a reversal is visible before it lands.
• Reproject on every change rather than once at the proof deadline, so corrections arrive in small pieces across many months.
• Tell employees plainly that a missed proof deadline costs them cash flow and not the deduction. It reduces the volume of escalations sharply.