Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
When a TDS return contains an error — a wrong PAN, a mistyped BSR code, a missed deductee — the TDS correction return process on TRACES is the only mechanism to fix it. The correction does not replace the original return; it builds on it, applying specific changes to specific fields. Identifying the correct correction type before starting the process saves time and avoids rejection.
What a TDS Correction Return Is
A TDS correction return is a revised statement filed by the deductor on the TRACES portal to amend errors in an already-accepted quarterly TDS return (Form 24Q, 26Q, or 27Q). It is not a cancellation — except in the C5 type, which explicitly cancels a statement. For all other correction types, the department retains the original filing record and overlays the corrections.
The correction return is prepared using the same tools as the original: NSDL’s RPU (Return Preparation Utility) and the FVU (File Validation Utility). The key difference is that the source file is not prepared from scratch — it is the consolidated statement (Conso file) downloaded from TRACES for the relevant quarter, which already contains all accepted data from the original and any prior corrections.
Five Correction Return Types
C1 — Correct Deductee PAN
Used when the deductee’s PAN was entered incorrectly in the original return. After a C1 correction is processed, the TDS credit moves from the incorrect PAN to the correct PAN in Form 26AS. This is the most consequential correction type for deductees, since their tax credit claim in the ITR depends on the credit appearing under their PAN.
C2 — Correct Challan Details
Used when the BSR code, challan serial number, deposit date, or challan amount in the return does not match the actual OLTAS record. A C2 correction links the return entry to the correct challan, allowing Form 26AS to reflect the TDS as deposited rather than as unmatched.
C3 — Correct Deductee or Salary Details
Used for Form 24Q corrections involving salary computation details, deduction amounts, or deductee personal information other than PAN. Less common than C1 and C2 for non-salary returns.
C5 — Cancel the Statement
Used to cancel an entire quarterly TDS return that was filed for the wrong TAN or with systemic errors that cannot be addressed through record-level corrections. Cancellation is irreversible — the statement must be re-filed as a fresh original return.
C9 — Add a New Deductee Row
Used when a deductee was omitted entirely from the original return. C9 adds a new row with the deductee’s PAN, section, amount paid, and TDS deducted. Unlike C1 through C3, which modify existing rows, C9 creates a new entry in the return.
Correction Return Types at a Glance
| Correction Type | Error Addressed | Common Trigger | Typical Turnaround After Upload |
|---|---|---|---|
| C1 | Wrong deductee PAN | Typo in PAN field; PAN of related entity used | 3–7 business days |
| C2 | Wrong challan BSR code or serial number | Manual transcription error; branch change after bank merger | 3–7 business days |
| C3 | Wrong salary or deduction details (Form 24Q) | Revised salary computation post-filing | 3–7 business days |
| C5 | Cancel entire statement | Filed under wrong TAN; duplicate statement | 5–10 business days |
| C9 | Add missing deductee row | Deductee omitted during original preparation | 3–7 business days |
The Correction Filing Process
Download the Conso file from TRACES for the quarter to be corrected. Open the file in NSDL RPU, apply the required changes (PAN, challan fields, new row), and save. Run the FVU tool to validate the file — FVU will reject the file if the PAN format is invalid, if the challan amount does not balance, or if mandatory fields are missing. Upload the validated .fvu file on TRACES as a correction return and note the acknowledgement token.
After submission, check TRACES for the correction return status daily. Processing typically completes within 3–7 business days. Once processed, verify Form 26AS for one or two affected deductees to confirm the credit has updated correctly before communicating to the deductee that the correction is complete.
For finance teams handling quarterly corrections across multiple TANs and hundreds of deductee rows, the manual Conso file download and RPU editing process creates bottlenecks near filing deadlines. TDS reconciliation software that maintains a log of original return data, flags correction candidates by error type, and tracks correction return status per deductee eliminates the risk of a correction being missed or filed against the wrong version. Reconciliation software India built for enterprise-scale TDS workflows integrates TRACES data directly, reducing the cycle time from error detection to Form 26AS update.