Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Form 16 reflects what the employer has calculated and certified, while Form 26AS reflects what TRACES has actually credited. Discrepancies arise from late return filing, PAN errors, challan mismatches, or amount differences, and the Income Tax Department treats Form 26AS as authoritative — claiming only Form 16 amounts creates Section 143(1) demand notices.
Classify each Form 16 entry against Form 26AS Part A on four dimensions — employer TAN, Section 192, quarter, and amount — and route each discrepancy to its cause: late filing, PAN error (C1 correction), challan mismatch (C2 correction), or amount difference. Do not claim in ITR what Form 26AS does not show; trigger employer correction first.
Reconciliation rule mapping Form 16 Part A to Form 26AS Part A by employer TAN and quarter. Typed exception codes for late filing, PAN error, challan mismatch, and amount variance. Correction-return routing to C1 or C2 on TRACES.
ITR claims that match Form 26AS exactly, no Section 143(1) demand notices, and a closed correction loop with employer payroll for every pre-filing discrepancy.
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.
2026 Migration Update — Under the Income Tax Act 2025, effective 1 April 2026, Form 26AS is replaced by Form 168 and Form 16A is replaced by Form 131. Salary Form 16 itself carries forward under the new schedule, but the backing statements and non-salary certificates change name and format. Finance teams should plan ERP and certificate-download tooling updates before Q1 FY 2026-27. See the Form 168 new TDS statement guide and the Form 131 TDS certificate guide.
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.
Root Causes of Form 16 vs Form 26AS Mismatches
Beyond timing delays, there are four structural root causes that produce persistent Form 16 vs Form 26AS discrepancies. Each requires a different resolution path, and misidentifying the cause wastes weeks of follow-up.
Deductor did not deposit the TDS. The employer issued Form 16A certifying TDS deduction, but the corresponding challan was never deposited with the government. Form 16A exists in the employee’s hands, but Form 26AS shows no credit because the deposit never reached OLTAS. This is the most serious scenario — the employee has no mechanism to force the deposit. Section 205 bars the department from collecting the tax from the employee where TDS was deducted, but in practice, the credit remains unavailable until the employer deposits and files the correction. CBDT circulars direct AOs to pursue the deductor, but the employee must escalate formally with the employer and, if necessary, file a grievance on the income tax portal.
Wrong PAN filed in the TDS return. The employer deducted and deposited correctly, but entered an incorrect PAN in the quarterly TDS return. The credit flows to a different taxpayer’s Form 26AS entirely. Only the employer can rectify this by filing a C5 correction statement on TRACES to update the PAN. The employee cannot initiate or expedite this correction independently. Until the C5 is processed, the credit does not exist for the correct PAN holder.
Wrong quarter attribution. The employer attributed a March salary TDS deduction to Q1 of the next financial year instead of Q4 of the current year. The credit appears in Form 26AS but under the wrong financial year. This creates a cross-year timing mismatch that the employee discovers only when the current year’s Form 26AS falls short. The employer must file a correction return reassigning the entry to the correct quarter.
Late filing by employer. The quarterly TDS return was filed after the statutory deadline but before the employee’s ITR filing date. Form 26AS may not yet reflect the credit because CPC processing takes 7-10 working days after a late-filed return. In this case, the resolution is to wait — but the employee must confirm through TRACES that the return was actually filed, not merely promised.
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.