Form 16 and Form 26AS serve different functions, and when their TDS figures diverge, it is Form 26AS that determines what the Income Tax Department will allow as a credit in the ITR. Understanding the four root causes of form 16 vs form 26AS reconciliation mismatches is essential for any salaried individual or employer payroll team preparing for ITR season.
What Each Document Covers
Form 16 is the annual TDS certificate issued by an employer to an employee for salary TDS deducted under Section 192. It has two parts. Part A, generated directly from TRACES, summarises TDS deposited quarter by quarter with challan details. Part B, prepared by the employer, shows the salary computation, exemptions, and deductions used to arrive at the taxable income and TDS figure.
Form 26AS is the Income Tax Department’s consolidated annual tax credit statement, maintained at the PAN level. It records TDS from all deductors — not just the salary employer — along with TCS, advance tax, and refunds. For the purpose of Form 16 vs Form 26AS reconciliation, the comparison is confined to the employer’s TAN and the salary TDS entries under Section 192 in the relevant financial year.
Four Causes of Mismatches
Late TDS Return Filing
If the employer filed the Q3 or Q4 TDS return after the statutory deadline, Form 26AS may not reflect the full year’s TDS at the time the employee downloads it for ITR filing. Form 16 (which reflects what the employer has calculated and deducted) will show more than Form 26AS in this case. The resolution is to wait for the return to be processed, which takes 7–10 working days after filing.
PAN Error in TDS Return
If the employer’s payroll team entered an incorrect PAN in the TDS return, the TDS credit flows to the wrong PAN — or to no PAN at all. Form 26AS for the correct PAN will show zero or a lower credit. The employer must file a C1 correction return on TRACES to correct the PAN, after which the credit moves to the correct PAN within 3–7 business days.
Challan Mismatch
Part A of Form 16 is generated from TRACES, which requires the underlying challan to be matched in OLTAS. If the employer’s TDS return contains a wrong BSR code or serial number, the challan is unmatched, and TRACES cannot generate an accurate Part A. The employer must file a C2 correction return.
Form 16 Downloaded Before Return Correction Was Processed
Employers sometimes issue Form 16 after filing a correction return but before TRACES has finished processing it. The Form 16 reflects the corrected figures, but Form 26AS still shows the pre-correction amount. In this case, the resolution is simply to wait.
Common Differences and Resolution Paths
| Scenario | Form 16 vs Form 26AS | Cause | Resolution | ITR Guidance |
|---|---|---|---|---|
| Employer filed TDS return late | Form 16 > Form 26AS | Quarterly return pending | Wait for return to be processed; Form 26AS updates in 7–10 days | File ITR after Form 26AS updates |
| Employee PAN wrong in return | Form 26AS shows zero | C1 correction needed | Employer files C1 correction on TRACES | Wait for correction + Form 26AS update |
| BSR code or serial number wrong | Form 26AS amount missing | C2 correction needed | Employer files C2 correction on TRACES | Do not claim excess; wait for correction |
| Form 16 issued before correction processed | Form 16 > Form 26AS (temporarily) | Processing lag | No action needed; Form 26AS will update | Check Form 26AS again after 5 days |
What Employers and Employees Should Each Do
For employees, the process is to download Form 26AS from the TRACES portal before starting ITR preparation, compare the Section 192 entries against Form 16 Part A, and contact HR payroll with the specific quarter and amount of any discrepancy. Claiming only what is in Form 26AS, then following up for the correction, is the only approach that avoids a demand notice.
For employer payroll teams, TDS reconciliation software that validates PAN, BSR codes, and challan serial numbers against TRACES records before the return is filed eliminates most correction returns. Reconciliation software India platforms with TRACES integration can flag mismatched challan entries at the draft stage rather than after Form 26AS fails to update. The Income Tax India portal provides access to AIS data that can further validate income and TDS figures before filing.