TDS Return

TDS Return Correction: C1 to C9 Explained — TRACES Conso File, RPU-FVU Workflow, and Section 271H Penalties (FY 2026-27)

If you have already filed a TDS return for FY 2026-27 and spotted an error — wrong PAN, wrong BSR code, incorrect section code, or a missed challan — you can fix it without incurring a fresh round of penalties, provided you act within the right window. The Income Tax Department's TRACES portal recognises six correction types (C1, C2, C3, C4, C5, and C9), each targeting a distinct layer of the filed statement. This guide tells you exactly which correction to use, how to move through the TRACES → RPU → FVU upload pipeline step by step, and what sections 234E and 271H will cost you if you delay or ignore the default notice.

Why TDS Returns Develop Errors — and What They Cost Downstream

A TDS return consolidates three layers of data: your own deductor information (TAN, name, address, responsible person), challan information (BSR code, challan serial number, date of deposit, and amount), and deductee information (PAN, name, section code, amount paid, TDS deducted, TDS deposited). Any one of these layers can carry an error — and because all three feed directly into the deductee's Form 26AS, Annual Information Statement (AIS), and Taxpayer Information Summary (TIS), a mistake in your return creates a credit mismatch that the deductee cannot resolve unilaterally.

The downstream chain is predictable. You file Form 26Q with an incorrect PAN for a sub-contractor. The contractor's TDS of ₹18,500 lands under an unknown or unrelated PAN on TRACES. The contractor files their ITR, claims ₹18,500 as TDS credit, but CPC (Centralized Processing Centre) cannot match it to their return because the credit sits under a different PAN. CPC raises a demand or withholds the refund. The contractor contacts you. You file a C3 or C5 correction. TRACES takes three to seven working days to process. The contractor eventually refiles a revised ITR or submits a grievance. You have lost goodwill, time, and professional credibility.

Scale this to an employer filing Form 24Q for 250 employees and Form 26Q for 500 vendors. One formula error during bulk PAN import can corrupt dozens of records simultaneously. The operational cost — staff time, professional fees, TRACES queries, vendor escalations — routinely exceeds the cost of the TDS itself. Investing in a clean, validated pre-filing workflow is straightforwardly a cost-saving decision.

The Four TDS and TCS Return Forms at a Glance

Before choosing a correction type, confirm which return you are correcting. Different forms have different schedules and correction mechanics.

• Form 24Q — TDS on salary payments to resident employees under Section 192. Includes Annexure I (challan and deductee-level data) and, uniquely in Q4, Annexure II (year-end salary breakup, perquisites, and Chapter VI-A deductions that drive Form 16).
• Form 26Q — TDS on all non-salary payments to residents: contractor fees (194C), professional services (194J), rent (194I, 194IB), interest (194A), commission (194H), immovable property (194-IA), and around forty other sections.
• Form 27Q — TDS on payments to non-residents under Section 195 and allied sections. Requires DTAA (Double Tax Avoidance Agreement) analysis and tax residency certificates.
• Form 27EQ — TCS (Tax Collected at Source) returns for sellers of specified goods, e-commerce operators, and buyers required to collect under Section 206C and related provisions.

Each form is filed quarterly. The due dates for FY 2026-27 are:

These are the original filing deadlines. A correction return filed after the original due date does not reset section 234E consequences — but you must file the correction for TRACES to propagate the updated credit to the deductee's AIS.

Six Correction Types: C1, C2, C3, C4, C5, and C9

TRACES currently supports the correction types listed below. Note that C6, C7, and C8 are not defined as standalone correction categories in the standard TRACES framework. The operative types you will encounter in practice are:

C1 — Deductor Details

Use C1 when the error is in your own information: the company name, registered address, or the name and PAN of the responsible person (typically the CFO or a director). C1 does not touch challan or deductee data, so it has no downstream impact on Form 26AS credits. File it to keep your TRACES profile accurate and prevent jurisdictional notices arriving at the wrong address.

C2 — Challan Details

Use C2 to fix errors in the challan header: wrong BSR code (the seven-digit code uniquely identifying the bank branch where TDS was deposited), wrong challan serial number, wrong date of deposit, or a wrong amount mapped to the challan. C2 corrections are operationally critical. TRACES matches every challan in your return against actual deposits in OLTAS (Online Tax Accounting System). If the BSR code or serial number does not match, TRACES marks the challan as "unmatched" and no deductee credit under that challan is confirmed — no matter how correct the deductee-level data is.

Before filing any C2, verify the correct challan details on OLTAS via the Challan Status Inquiry tool at tin.tin.nsdl.com. Do not guess or reconstruct from your books — pull the actual OLTAS record.

C3 — Deductee Details

C3 covers all errors at the deductee row level: a wrong PAN where the entered PAN is a valid but incorrect PAN (belonging to a different person), a wrong name, a wrong section code (e.g., 194C entered instead of 194J), a wrong payment amount, or a wrong TDS figure. This is the most frequently used correction type in large organisations. A single transposed digit in one vendor's PAN requires a C3 for that specific record.

C4 — Addition or Deletion of Salary Records (Form 24Q Only)

C4 is exclusive to Form 24Q Annexure II — the year-end salary schedule filed with Q4. Use it to add a salary record omitted from the original filing (for example, an employee whose records were accidentally excluded during bulk import), to delete a duplicated record, or to insert or correct the breakup of salary components and Chapter VI-A deductions that determine the Form 16 computation. Any C4 correction that changes the tax liability figure in Annexure II requires a revised Form 16 to be issued.

C5 — PAN Correction from PANINVALID or PANNOTAVBL

C5 is a specialised variant for one specific scenario: the deductee's PAN was originally reported as PANINVALID (the PAN failed a structural check) or PANNOTAVBL (the deductee did not furnish a PAN, so TDS was deducted at the higher rate under Section 206AA). Once the deductee provides a valid PAN, file a C5 to replace the placeholder tag with the actual PAN.

One point that often catches deductors off guard: C5 does not automatically refund the excess TDS deducted under Section 206AA. If TDS was correctly deducted at 20% for a PANNOTAVBL record and the actual rate is 10%, the 10% excess remains deposited with the government. The deductee must claim it as a refund in their own ITR. Make this clear to your vendor or employee when filing the C5, so they do not wait for you to return the money directly.

C9 — Addition of a Completely Missed Challan

C9 is used when an entire challan — and all the deductee rows mapped to it — was completely left out of the original return. You had four challans in Q2 FY 2026-27, but only three were imported into the RPU before filing. The fourth challan and all the payments against it are absent. You cannot use C2 to add a challan that was never filed (C2 only corrects existing challan records). C9 inserts the new challan and its deductee rows as a fresh addition.

Critical caveat: C9 requires a processed original return to attach to. If no original return was ever filed for the quarter, there is nothing for C9 to reference. File the original return first — even if late, with the attendant 234E consequences — wait for TRACES to complete processing, and then file the C9 to add the missed challan.

Step-by-Step Correction Filing: TRACES → RPU → FVU → Upload

The correction workflow has five sequential steps. None can be skipped or reordered.

Step 1 — Confirm "Statement Processed" Status on TRACES

Log in to TRACES (www.tdscpc.gov.in) with your TAN credentials. Navigate to Statements / Payments → Statement Status. The status must read "Statement Processed with Default" or "Statement Processed without Default" before you can download the Conso File. If the status shows "Uploaded" or "Pending for Processing", wait. Attempting to download the Conso File prematurely returns an error.

Step 2 — Download the Conso File

Navigate to Defaults → Request for Conso File. Select the form type, financial year (2026-27), and quarter. Complete the TRACES KYC verification (which typically requires confirming a token number, challan details, or PAN of the responsible person). The Conso File is generated asynchronously and becomes available under Requested Downloads within 24–48 hours. The file carries a .tds extension and is password-protected. The standard password format is: TAN in uppercase + date of incorporation or birth of responsible person in DDMMYYYY format — for example, AAAA00001A01041985. The Conso File contains your entire processed return in machine-readable format; it is the source of truth for all corrections.

Step 3 — Import into the RPU and Make Corrections

Download the latest version of the Return Preparation Utility (RPU) from the Protean (formerly TIN-NSDL) portal. The RPU is a Java-based application updated quarterly — always download a fresh copy rather than using a version from a previous quarter, as new section codes and validation rules are introduced regularly.

Open the RPU and select "Correction" on the opening screen (not "Regular"). Import the Conso File. The RPU auto-populates all existing data. Navigate to the relevant tab:

• Deductor Details tab → for C1 changes
• Challan Details tab → for C2 changes
• Deductee Details tab → for C3 and C5 changes
• Salary Detail (Annexure II) tab → for C4 changes
• Add Challan option → for C9 additions

You do not manually enter correction type codes. Edit the field, and the RPU stamps the correction type automatically based on what changed.

Step 4 — Validate Using the FVU

Save the prepared file from the RPU. Download the latest File Validation Utility (FVU) from Protean — there are separate versions for pre-2013 and post-May 2013 statements. Run the FVU against your saved file. A successful validation produces a .fvu file and a validation report. Read the report carefully: warnings about PAN format or section code mismatches sometimes indicate the same underlying error you were trying to fix, suggesting the correction was incomplete.

Step 5 — Upload the Correction Statement

Upload the .fvu file on the TIN-NSDL portal under e-TDS/TCS → Upload TDS. Authenticate using either a Digital Signature Certificate (DSC) or an EVC (Electronic Verification Code). On successful upload, you receive a Provisional Receipt Number (PRN) — save this as your filing evidence. Track processing on TRACES under Statement Status. Once the correction statement shows "Processed", the updated data propagates to the deductee's AIS within five to seven working days.

Penalties: What Sections 234E, 271H, 201(1A), and 40(a)(ia) Actually Cost

Section 234E — Late Filing Fee

₹200 per day for every day of delay after the due date, capped at the total TDS or TCS amount in the return. This is a statutory fee, not discretionary — it accrues automatically and appears as a "default" on TRACES.

Worked calculation: Your Q1 FY 2026-27 Form 26Q was due on 31 July 2026. You filed on 18 November 2026 — a delay of 110 days. Total TDS in the return: ₹85,000.

• Calculated fee: 110 × ₹200 = ₹22,000
• Cap test: ₹22,000 < ₹85,000, so the full ₹22,000 is payable.

If total TDS in the same return were only ₹15,000, the fee would be capped at ₹15,000.

Pay the 234E fee under Challan 281, Minor Head 400 before uploading any correction statement for a late return.

Section 271H — Penalty for Incorrect or Non-Filing

₹10,000 to ₹1,00,000 at the Assessing Officer's discretion, triggered by:

• Furnishing incorrect information in a TDS statement, or
• Failing to file the statement within one year of the due date.

The proviso to Section 271H provides a critical safe harbour: no penalty is levied if (a) TDS was deposited to the government, (b) the section 234E late filing fee has been paid, and (c) the return is filed within one year of the due date. This is your insurance policy. If you missed a quarter, file it (with 234E payment) before the one-year anniversary of the due date to preserve the safe harbour.

Section 201(1A) — Interest on Short Deduction or Late Deposit

• Short deduction (TDS deducted at a lower rate than prescribed): 1% per month from the date TDS was deductible to the date of actual deduction.
• Late deposit (TDS correctly deducted but deposited after the due date): 1.5% per month from the date of deduction to the date of actual deposit.

Part months are treated as full months.

Example: TDS of ₹60,000 deducted on 20 August 2026. Due date for deposit: 7 September 2026. Actual deposit: 15 October 2026 — spanning two months (September and October).

• Interest: ₹60,000 × 1.5% × 2 = ₹1,800.

Section 40(a)(ia) — Expense Disallowance

If TDS was not deducted, or once deducted was not deposited by the due date for filing the deductor's own Income Tax Return, 30% of the gross payment is disallowed as a business expense. On a ₹10,00,000 contractor payment where TDS was never deposited, you lose ₹3,00,000 in deductible expense. At a 25% corporate tax rate, that translates to ₹75,000 in additional tax — far more than the TDS you avoided depositing.

Worked Example: The Real Cost of a Bulk PAN Import Error

You are the accounts manager of a mid-sized manufacturing firm. In Q2 FY 2026-27, you file Form 26Q covering 148 vendors. A formula error in your Excel consolidation sheet transposes two digits in 15 vendor PANs. You file on 30 October 2026 — one day before the deadline. The return is processed by TRACES on 12 November 2026.

What unfolds:

• 15 vendors' TDS credits totalling ₹4,20,000 appear under incorrect or non-existent PANs in Form 26AS and AIS.
• TRACES raises a "PAN mismatch" default against your TAN.
• All 15 vendors contact you when their AIS shows no TDS credit in December 2026.
• You need C3 corrections for all 15 records.

Timeline under the best-case scenario:

• Conso File downloaded on 15 November 2026.
• RPU correction prepared and FVU validated: 1 working day.
• Upload and TRACES processing: 7 working days.
• Credit visible in vendors' AIS: approximately 25 November 2026.

The indirect cost if you had delayed by three months:

• Three vendors, unable to claim TDS credit, file ITRs without the credit and receive CPC demands.
• Each demands a rectification or grievance resolution — professional fee for resolving each: approximately ₹10,000.
• Three grievances: ₹30,000 in additional professional cost.
• Section 271H exposure if TRACES issues a show-cause notice for the incorrect statement.

The preventive fix — implement before the next quarter: Use the TRACES Bulk PAN Verification tool (login → Statements/Payments → Bulk PAN Verification) to upload your full vendor PAN list at least five working days before the filing deadline. The tool confirms which PANs are active, which are invalid, and which are PANNOTAVBL. This single step eliminates the most common source of C3 and C5 corrections. It is free, accessible from your existing TRACES login, and takes under an hour for a list of 500 PANs.

Common Mistakes and Pitfalls to Avoid

Attempting C9 before an original return exists. C9 attaches a missed challan to a processed return. If no original return was filed, TRACES has nothing to attach it to. File the original return first, accept the 234E consequences, and then file C9.

Using an outdated RPU or FVU version. Protean updates these utilities periodically. Filing with an outdated FVU generates a portal rejection. Download fresh versions before every quarterly filing cycle.

Confusing C3 with C5. C3 corrects a wrong but structurally valid PAN (one belonging to a different person). C5 replaces a PANINVALID or PANNOTAVBL placeholder. Applying the wrong type causes the RPU to flag a validation error or the return to be processed without the correction taking effect.

Correcting a challan's BSR code without first verifying it in OLTAS. If the corrected BSR code is not present in OLTAS — because the challan was paid under a different TAN, or the deposit was at a branch that does not match — TRACES will mark the corrected challan as "unmatched." Always confirm the OLTAS record at tin.tin.nsdl.com before filing any C2.

Not issuing revised Form 16 or Form 16A after a deductee-level correction. Filing a C3 or C5 updates the deductee's AIS but does not automatically regenerate the TDS certificate. Download the revised Form 16A from TRACES under Downloads → Form 16A and re-issue it. For salary corrections involving C4, generate a revised Form 16 from TRACES and reissue it before the deductee files their ITR.

Assuming the correction resets the 234E late filing fee. It does not. The fee for late filing of the original return remains payable regardless of how promptly you file the correction.

Building a Correction-Free Quarterly Filing Routine

The most effective correction strategy is preventing corrections in the first place. Run the following checks before every quarterly return:

1. PAN validation before filing — Upload your full deductee list to TRACES Bulk PAN Verification at least five working days before the deadline. Resolve every mismatch before the return is prepared.
2. Challan reconciliation against OLTAS — For each challan, confirm BSR code, serial number, date, and amount against the OLTAS Challan Status Inquiry. Document the confirmation in your monthly closing checklist.
3. Section code audit — Technical services to a domestic company attract 194J(b) at 2%; professional fees (doctor, lawyer, architect, consultant) attract 194J(a) at 10%. Mixing these codes causes incorrect TDS deduction and 201(1A) interest exposure.
4. Year-end salary true-up for Form 24Q Q4 — In March 2027, recompute each employee's annual tax liability against actual salary, perquisites, and Chapter VI-A deductions. Adjust Q4 TDS withholding accordingly. The accuracy of Annexure II in Q4 directly determines the correctness of Form 16.
5. Maintain a correction log — Record every correction you file: quarter, form type, correction type, root cause, date resolved. Review the log each quarter to identify recurring patterns (a specific source file, a vendor onboarding step, a payroll system export) and fix the upstream problem.

Key Takeaways

• C1 fixes deductor details; C2 fixes challan details; C3 fixes deductee PAN, name, or section code; C4 adds or deletes salary records in Form 24Q Annexure II; C5 replaces PANINVALID/PANNOTAVBL tags with valid PANs; C9 adds a completely missed challan and its deductees.
• The Conso File on TRACES is mandatory as your starting point — the original return must show "Statement Processed" status before you can download it. Never rebuild the correction from scratch.
• Section 234E accrues at ₹200 per day, capped at the TDS amount — it is not waivable. Pay it under Challan 281 (Minor Head 400) before uploading any correction for a late return.
• The Section 271H safe harbour — file within one year of the due date and pay 234E — is your only protection against a discretionary penalty of up to ₹1,00,000. Do not let the window expire through inaction.
• Section 40(a)(ia) disallows 30% of the gross payment if TDS was not deducted or deposited on time — on a ₹10,00,000 invoice, that is ₹75,000 in extra corporate tax at a 25% rate.
• TRACES Bulk PAN Verification eliminates the most common correction trigger. Run it before every quarter, not after TRACES raises a default.
• After every deductee-level correction, issue a revised Form 16 or Form 16A. The deductee cannot correct their ITR without an updated certificate.