Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A Section 200A intimation is auto-generated after TDS return processing and itemises short deduction, Section 201(1A) interest (1 percent per month pre-deduction plus 1.5 percent per month pre-deposit), Section 234E late fees (₹200 per day capped at quarterly TDS), and challan or PAN mismatches. Each line requires a different remediation path — correction statement versus Section 154 rectification versus challan deposit.
Download the intimation and classify each demand line by type — interest, late fee, short deduction, or challan/PAN mismatch. Route challan mismatches and PAN errors to TRACES correction statements (C2 or C1), route genuine shortfalls to a new challan plus correction return, and route CPC computation errors to a Section 154 rectification filed within 4 years. Deposit accrued interest with the shortfall challan.
Demand-line classifier mapping to C1/C2/C3 correction route, new challan route, or Section 154 rectification. Interest calculator implementing 1 percent and 1.5 percent monthly logic. Ageing counter against the 4-year Section 154 window.
Each 200A line item closed through the correct remediation route, revised intimation within 3 to 7 working days of TRACES processing, and documented audit file showing demand-line-to-correction traceability.
TDS demand notice reconciliation India typically begins with a Section 200A intimation landing in the deductor’s inbox after a quarterly TDS return is processed. The notice is system-generated and itemises every variance the CPC identifies between the filed return and OLTAS challan records — short deduction amounts, interest charges, late fees, and PAN-linked adjustments. Each line item requires a separate reconciliation path.
What Section 200A Covers
Section 200A grants the Income Tax Department authority to process filed TDS returns and raise a prima facie demand without a full assessment. The intimation covers four categories: short deduction (where the rate applied was lower than required), interest under Section 201(1A) for late deduction or late deposit, late filing fees under Section 234E at ₹200 per day, and adjustments where challan or PAN data in the return does not match government records.
The intimation is not an assessment order — it is a computational output. That distinction matters because correction statements filed through TRACES can revise the underlying records, which in turn revises the demand. A Section 154 rectification is the appropriate response only when TRACES records are already correct but the intimation contains an error in computation.
Section 206AA applies where deductees have not furnished valid PANs — TDS in those cases must be at 20% or the applicable rate, whichever is higher. Section 206AB, effective from 1 July 2021, applies a higher rate — twice the specified rate or 5%, whichever is higher — for deductees who have not filed ITRs for the two preceding financial years and whose TDS or TCS exceeded ₹50,000 in each of those years.
Where Reconciliation Breaks Down
Challan data entry errors. The most frequent cause of a Section 200A demand is a transposition error in BSR code, challan serial number, or deposit date when filing the quarterly return. The challan amount may match but the wrong serial number means OLTAS cannot confirm the deposit, triggering a short deduction flag on every deductee mapped to that challan.
PAN not updated in deductee records. Where a vendor or contractor has changed their PAN (business restructuring, correction) and the deductor’s records still carry the old PAN, the TDS credited against the old PAN will not appear in the deductee’s 26AS. The deductee raises a dispute; the department raises a demand against the deductor for a PAN mismatch.
Late filing of quarterly return. The Section 234E fee of ₹200 per day accrues automatically. Finance teams that file one or two days late — particularly the Q4 return due 31 May — routinely receive demand notices for late fees that could have been avoided with a filing calendar aligned to actual return processing timelines.
Response Process
Step 1: Download and itemise the intimation. Log in to TRACES and download the Section 200A intimation. Export each demand line item into a working spreadsheet. Categorise by type: interest (201(1A)), late fee (234E), short deduction, or challan/PAN mismatch.
Step 2: Cross-reference against TRACES challan register. For each challan-related demand, pull the TRACES challan status report. Identify whether the mismatch is in BSR code, serial number, amount, or date. If the challan exists in OLTAS but was entered incorrectly in the return, the path is a correction statement.
Step 3: File correction statement where applicable. Correction statements submitted via TRACES resolve challan mismatches, PAN errors, and rate corrections. After CPC processes the correction, typically 3–7 working days, the revised intimation reflects the corrected position.
Step 4: Deposit valid shortfall plus interest. Where the demand reflects a genuine short deduction — wrong rate applied, or a payment missed — deposit the shortfall and accrued interest before responding. Generate the challan and map it in a correction return.
Step 5: File rectification under Section 154 for computation errors. Where TRACES records are correct and the demand appears to result from a CPC computation error, file a rectification request under Section 154 with supporting documents — OLTAS challans, filed return acknowledgement, and TRACES consolidated statement.
TDS Demand — Root Cause and Response
| Demand line item | Root cause | Correction action | Portal | Timeline |
|---|---|---|---|---|
| Short deduction — rate | 206AA / 206AB applied incorrectly or omitted | Deposit shortfall + interest; file correction return | TRACES + income tax portal | Within 30 days of intimation |
| Interest under 201(1A) | Late deposit of TDS after deduction | Pay interest; no return correction needed if principal is correct | Challan payment portal | Immediately |
| Late fee under 234E | Quarterly return filed after due date | Fee is mandatory; pay via challan; no waiver mechanism | Challan payment portal | Before response deadline |
| Challan mismatch | BSR code / serial number entry error in return | File correction statement in TRACES | TRACES | 3–7 days processing |
| PAN mismatch | Incorrect PAN of deductee in return | File correction statement; update deductee PAN | TRACES | 3–7 days processing |
What Automated Reconciliation Changes
Finance teams that reconcile TDS quarterly — matching challan deposits to OLTAS confirmations and deductee-level return data before filing — catch challan mismatches and PAN errors before the Section 200A intimation is generated. Teams that reconcile only at year-end typically discover these errors after the notice arrives, compressing the response window and adding interest exposure for the intervening period.
TDS reconciliation software India that validates challan BSR codes against OLTAS data before quarterly filing eliminates the most common category of Section 200A demand. Reconciliation software India that maintains a deductee PAN validation register catches Section 206AA exposures at the point of payment, not after the intimation is issued.
Recovery Paths Beyond Standard Rectification
When a Section 200A demand cannot be resolved through correction statements or Section 154 rectification — because the underlying TDS was genuinely short-deducted, the challan was never deposited, or the correction window has lapsed — two additional recovery mechanisms exist under Indian tax law.
Section 119(2)(b) condonation of delay. Where the deductor missed the deadline for filing a correction return or the deductee missed the ITR filing deadline that would have reflected the corrected TDS credit, Section 119(2)(b) empowers the CBDT to condone the delay if the taxpayer demonstrates genuine hardship. CBDT Circular 11/2024 governs the current condonation framework, permitting applications within a five-year window from the end of the relevant assessment year. The applicant must establish that the delay was caused by circumstances beyond their control — system errors, deductor non-cooperation, or medical incapacity are accepted grounds. The application is filed with the Principal Commissioner or Commissioner of Income Tax having jurisdiction. Approval is not automatic; the CBDT applies a genuine hardship test that requires documented evidence of the delay cause and the steps taken to resolve it.
ITR-U under Section 139(8A). Introduced in the Finance Act 2022, Section 139(8A) allows a taxpayer to file an Updated Return (ITR-U) within 24 months from the end of the relevant assessment year. This is relevant where the original ITR was filed without claiming TDS credits that have since appeared in Form 26AS after a deductor correction. The ITR-U mechanism requires payment of additional tax: 25% of the aggregate tax and interest if filed within 12 months of the assessment year end, and 50% if filed between 12 and 24 months. The additional tax is computed on the difference between the tax payable under the updated return and the tax already paid. While the additional tax cost is significant, ITR-U provides a structured path to recover TDS credits that were unavailable at the original filing date — particularly relevant for credits that arrived after the deductor filed a belated correction return.
Both paths require meticulous documentation: the original demand notice, all correction attempts and their TRACES acknowledgements, communication records with the deductor, and the timeline of credit appearance in Form 26AS.