Skip to main content
TDS · 4 min read

Form 16 vs Form 26AS: What to Do When They Don't Match

Form 16 and Form 26AS should show identical TDS figures for salary income, but they frequently diverge — with consequences that extend to demand notices after ITR filing. The discrepancy is almost always caused by an error in the employer's TDS return: a late filing, a PAN entry error, or a challan mismatch that prevents Form 26AS from reflecting what the employer has already certified in Form 16. Knowing the exact cause determines who to contact and how quickly it can be resolved.

Terra Insight
Terra Insight Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 8 March 2026
Domain expertise
TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

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

ScenarioForm 16 vs Form 26ASCauseResolutionITR Guidance
Employer filed TDS return lateForm 16 > Form 26ASQuarterly return pendingWait for return to be processed; Form 26AS updates in 7–10 daysFile ITR after Form 26AS updates
Employee PAN wrong in returnForm 26AS shows zeroC1 correction neededEmployer files C1 correction on TRACESWait for correction + Form 26AS update
BSR code or serial number wrongForm 26AS amount missingC2 correction neededEmployer files C2 correction on TRACESDo not claim excess; wait for correction
Form 16 issued before correction processedForm 16 > Form 26AS (temporarily)Processing lagNo action needed; Form 26AS will updateCheck 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.

Primary reference: TRACES portal — where Form 16 is generated by employers and Form 26AS is downloaded by employees.

Frequently Asked Questions

Can I claim TDS credit in my ITR based on Form 16 if Form 26AS shows a lower amount?
No. The Income Tax Department's return processing system validates TDS credit claims against Form 26AS, not against Form 16. If Form 16 shows ₹80,000 TDS but Form 26AS shows ₹60,000, and you claim ₹80,000 in your ITR, the system will generate a demand notice under Section 143(1) for the ₹20,000 difference. Claim only what appears in Form 26AS. If the employer's figure is correct, the resolution path is to ask the employer to file a correction return so Form 26AS updates before you file the ITR.
What should I do if my employer's Form 16 shows TDS that isn't in Form 26AS?
Contact the HR or payroll department and ask them to verify: (1) that the quarterly TDS return was filed on time for the relevant quarter; (2) that the challan BSR code and serial number in the return match the actual bank challan; and (3) that the PAN entered for you in the TDS return is correct. If any of these is wrong, the employer must file a correction return on TRACES. Provide them with the specific quarter and amount in question, and track the correction return status through TRACES.
How long after an employer files a TDS correction does Form 26AS update?
Form 26AS typically updates within 3–7 business days after the correction return is processed by the TDS CPC. Check Form 26AS after 7 business days. If unchanged, ask the employer to confirm the correction return status on TRACES. You should verify Form 26AS is fully updated before filing your ITR — do not rely on the employer's timeline estimate alone.
Is Form 26AS or Form 16 more authoritative for income tax purposes?
Form 26AS is the government's authoritative record of TDS credits linked to a PAN. Form 16 is the employer's certificate of TDS deducted and deposited — a useful document, but secondary to Form 26AS for ITR purposes. When the two conflict, the Income Tax Department treats Form 26AS as the primary source. If Form 16 shows higher TDS than Form 26AS, the resolution must come from the employer correcting the underlying TDS return and challan data, not from accepting Form 16 at face value.
What is AIS and how does it differ from Form 26AS?
AIS (Annual Information Statement), accessible from the Income Tax e-filing portal at incometax.gov.in, provides transaction-level data reported by financial institutions: interest income from banks, dividend receipts, securities transactions, mutual fund activity, and foreign remittances. Form 26AS aggregates TDS by deductor TAN at quarterly level. For TDS reconciliation — specifically verifying whether employer TDS is credited — Form 26AS remains the relevant document. AIS is more useful for verifying completeness of income disclosure across all sources.

See how TransactIG handles reconciliation for your industry

Configuration takes 2–4 weeks. No code development required. ISO 27001:2022 certified.