Revising TDS returns

Revising TDS Returns: The 2026 Step-by-Step Guide to TRACES Correction Statements

A TDS return can be revised — online, unlimited times — by filing a correction statement on the TRACES portal (traces.gov.in). You download the consolidated (.tds) file for the relevant quarter, correct it in the Return Preparation Utility (RPU), validate it with the File Validation Utility (FVU), and re-upload. Every error type has a defined correction category (C1 to C9). Act promptly and you cap your exposure. Leave errors unaddressed and you face Section 234E late fees, Section 201(1A) interest, blocked Form 26AS credits for your deductees, and, eventually, a formal default notice from CPC-TDS. This guide covers every step for FY 2026-27 / AY 2027-28.

When a TDS Correction Statement Is Actually Mandatory

Not every bookkeeping slip requires a revision — but the following situations require one without delay.

The deductee cannot claim credit. If your PAN entry, challan mapping, or payment amount is wrong, the deductee's Annual Information Statement (AIS) and Tax Information Summary (TIS) will not reflect the TDS credit. When the deductee's ITR is processed, the mismatch generates an automatic demand notice. The only way to clear it is your correction.

You have received a TRACES Justification Report flagging defaults. CPC-TDS cycles through your statement and raises row-level defaults — short deduction, short payment, PAN mismatch, challan mismatch. Each code in the Justification Report is a mandatory correction item. Ignoring them does not make them go away; it lets interest accumulate.

PAN-Aadhaar non-linkage has made a PAN operative again — or inoperative. From FY 2023-24 onwards, deductees with an unlinked PAN are treated as having an inoperative PAN, requiring TDS at 20% under Section 206AA. If you deducted at the standard rate, you need a C3 correction and a supplementary payment for the shortfall.

A Section 197 certificate was applied but not referenced. When a deductee provides a lower- or nil-deduction certificate under Section 197, the certificate number must appear in the deductee row of the quarterly statement. If it is missing, CPC-TDS computes a short-deduction default at the standard rate. Fix it with a C3 correction referencing the certificate number and the TRACES-verified certificate details.

An employee's Form 16 will be incorrect. Errors in Form 24Q Annexure II — wrong gross salary, inflated 80C deductions, unvalidated PAN — flow directly into the Form 16 issued to the employee. A wrong Form 16 means the employee's ITR will not reconcile with the employer's filed return, generating a mismatch that takes months to unwind.

The Nine Correction Types: C1 to C9

Selecting the wrong correction type is among the most common reasons a correction statement is rejected before processing even begins. Use this as a quick reference.

Multiple correction types can be combined in a single correction statement. If you are simultaneously fixing a challan BSR code and a deductee's PAN, select C2 + C3 in RPU — you do not need to file two separate statements.

What to Download from TRACES Before You Begin

Rushing into RPU without the right files creates the largest category of wasted effort in TDS compliance. Before touching the utility:

Three mandatory downloads

1. Consolidated (.tds) file. Navigate to TRACES → Statements / Payments → Request for Conso file. Always request the file for the latest processed statement. Using an older conso file overwrites corrections already accepted by CPC-TDS — one of the costliest mistakes in the revision workflow.

1. Justification Report. This is your correction checklist. It lists every default row with an error code — for example, "B01" for PAN mismatch, "T01" for challan mismatch, "T03" for challan over-claim. Work through every row systematically; do not skip rows with small amounts, because interest accrues on each one.

1. Latest RPU and FVU. Download both from tin.tin.nsdl.com (Protean eGov Technologies) or the downloads section on TRACES. As of Q1 FY 2026-27, RPU version 5.4 and FVU version 8.8 are current — but always verify the version on the site before starting, since Protean releases updates with each quarterly cycle. A file generated on an outdated FVU is rejected at the upload portal.

TRACES login and conso request sequence

• Go to traces.gov.in → Login as Deductor using your TAN credentials
• Navigate: Statements / Payments → Request for Conso file
• Select: Form type (24Q / 26Q / 27Q / 27EQ), Financial Year 2026-27, Quarter
• If status shows "Submitted", wait 24-48 hours for CPC-TDS to process the request before downloading
• Status must show "Available" for download to proceed

Filing the Correction Statement: Step-by-Step

Once you have the conso file and Justification Report in hand, follow this sequence without deviation.

1. Open RPU. Launch TDS_RPU.jar (requires Java 8 or above). Select the form type matching your original statement — Form 24Q for salary TDS, Form 26Q for non-salary domestic payments, Form 27Q for NRI payments, Form 27EQ for Tax Collected at Source.

1. Import the conso file. Go to File → Open Conso file. The utility pre-populates every previously accepted data field. Never type values from scratch or import from your own spreadsheet — always work from the TRACES-issued conso file.

1. Mark the correction type. In the header of the relevant challan row or deductee row, select the applicable correction type (C2, C3, C5, C9, etc.). For an entirely new entry — a challan or deductee not in the original return — select C9.

1. Make your corrections. For challan corrections, match the BSR code, serial number, and deposit date exactly to the bank challan counterfoil or the OLTAS challan verification output at tin.tin.nsdl.com. For deductee corrections, verify every PAN through the income-tax PAN verification utility before entering it.

1. Run RPU validation. Click Validate. The utility flags structural errors — missing mandatory fields, invalid formats, amount overflows. Resolve every flag before proceeding; partial validation is not accepted.

1. Generate the FVU file. Click Create File. RPU hands off to FVU, which runs a deeper checksum and format validation. FVU produces a line-by-line error report if it finds issues. Address each line; do not guess at fixes.

1. Upload the .fvu file. Two channels are available:
2. Income-tax e-filing portal (preferred for FY 2026-27): Login with your TAN at incometax.gov.in → TDS → Upload TDS. Attach the .fvu file and authenticate with a valid DSC or Aadhaar OTP.
3. TIN-FC counter: Available for deductors without a DSC or Aadhaar-enabled mobile number.

1. Track processing and regenerate certificates. After upload, go to TRACES → View Filed Correction Statement and record the token number and processing status. Processing takes 3-7 working days. Once the status shows "Processed" or "Accepted", regenerate Form 16 or Form 16A for every deductee affected by the correction.

Penalties and Interest Exposure

Understanding the financial cost of delay — to the rupee — is what drives urgency.

Section 234E — Late filing fee

• Rate: Rs. 200 per day for every day after the due date
• Cap: Total fee cannot exceed the TDS deducted for the quarter
• Due dates for original statements, FY 2026-27: Q1 — 31 July 2026 | Q2 — 31 October 2026 | Q3 — 31 January 2027 | Q4 — 31 May 2027

Section 271H — Penalty for incorrect statements

• Range: Rs. 10,000 to Rs. 1,00,000
• Waiver: Available if you file the correct statement within one year of the original due date and have paid the TDS, Section 234E fee, and Section 201(1A) interest. Miss this window and the penalty becomes discretionary but very real.

Section 201(1A) — Interest for short deduction or short payment

• Short deduction: 1% per month (or part thereof) from the date the tax was deductible to the date it is actually deducted
• Short payment: 1.5% per month from the date the tax was deducted to the date it reaches the government account
• Calculated on the shortfall amount, not the gross TDS liability

Worked Example: Challan Mismatch in Form 26Q, Q2 FY 2026-27

The situation. A private limited company pays contract charges of Rs. 18,00,000 to three vendors during August 2026. TDS at 2% under Section 194C = Rs. 36,000. The accountant deposits Rs. 36,000 on 7 September 2026 via net banking under BSR code 0009876, challan serial 003456.

When preparing Form 26Q for Q2 FY 2026-27 (due 31 October 2026), the accountant enters BSR code 0009867 — a two-digit transposition. CPC-TDS cannot locate challan 003456 under BSR 0009867 because the branch does not exist in OLTAS. The outcome:

• Default raised: Short payment of Rs. 36,000 (the payment is treated as missing in its entirety)
• Form 26AS of all three vendors: Shows zero TDS credit; each vendor follows up during ITR filing

The correction file is uploaded on 18 November 2026 — 18 days after the Q2 due date.

Cost calculation:

Had the accountant reconciled BSR codes against the OLTAS challan status query before filing — a five-minute check on tin.tin.nsdl.com — this cost would have been zero.

Form 24Q Annexure II: The Q4 Special Case

Form 24Q for Q4 (January–March, due 31 May 2027) is structurally different from the Q1–Q3 filings. It requires Annexure II — a complete salary detail record for every employee for the full financial year, covering:

• Gross salary, value of perquisites, and profits in lieu of salary
• Section 10 exemptions: HRA under Section 10(13A), LTA under Section 10(5), and other allowances
• Chapter VI-A deductions: 80C (with sub-breakdown), 80CCD(1B) NPS, 80D health insurance, 80G donations, 80E education loan interest
• Section 24(b) home loan interest deduction
• Quarter-wise TDS deducted and the year-end balance to ensure total TDS equals tax on total income

What goes wrong in Annexure II — and how to fix it

Investment proof shortfall. Employees declare investments in April–May 2026 and submit proofs in January–February 2027. If the payroll system carries the declared figures into Annexure II without updating them against actual proofs, 80C deductions are overstated, taxable salary is understated, and the employee receives a demand when the ITR is assessed. Fix: run a payroll-vs-proof reconciliation in March 2027 before closing the Q4 payroll, and recompute TDS on the shortfall.

PAN not validated. Any employee PAN that fails the income-tax PAN verification API defaults the TDS rate to 20% under Section 206AA. A C5 correction after filing is expensive in time. Validate every PAN before payroll is processed for April 2026.

Perquisite valuation errors. Car perquisites, employer-provided accommodation, and ESOP taxation at the time of exercise are frequently misstated. A wrong perquisite figure changes the gross salary in Annexure II, creates a Form 16 Part B error, and leaves the employee unable to reconcile their ITR with employer data.

The C4 correction. In RPU, select C4 to correct Annexure II records. You must update the complete record for the affected employee — RPU does not allow partial field edits within a single Annexure II row. For a payroll with more than 100 employees, run corrections in alphabetical or department-wise batches to ensure no record is missed.

Common Mistakes That Get Correction Statements Rejected

These are the errors that guarantee your file bounces before CPC-TDS even begins processing it.

• Outdated RPU or FVU. The portal checks FVU version compatibility at upload. A file generated in an older version is rejected automatically, regardless of how accurate the data is. Download fresh before every correction run.
• Stale conso file. If CPC-TDS accepted a correction you filed last month and you now start from the conso file downloaded last month, you will overwrite the accepted change. Always request a fresh conso file on the day you begin.
• Wrong token number. The upload form asks for the token number of the original accepted statement — not the most recent correction. Find the original token under TRACES → View Filed Statements → Original.
• Challan over-allocation. You cannot map more TDS liability to a challan than its deposited amount. If you are increasing a deductee's TDS through a C3 correction, first verify that the challan pool has sufficient headroom — or add the shortfall challan via C9 before making the allocation change.
• Correcting TDS amount without a matching challan. Increasing a deductee's TDS via C3 without a corresponding challan deposit results in a fresh short-payment default immediately on processing. Deposit the additional TDS first, verify the challan in OLTAS, then file the correction.
• Leaving "PANNOTAVAIL" rows uncorrected. Every row with PANNOTAVAIL or PANINVALID generates a fresh default in each processing cycle. Update them via C5 as soon as the correct PAN is confirmed — do not defer because the amount seems small.

Monthly Reconciliation: The Correction You Never Have to File

The cheapest TDS revision is the one that never needs to be made. Build this three-point reconciliation into your month-end close for FY 2026-27.

Step 1 — Challan verification, first week of each month. Pull the bank's TDS remittance confirmation and match every challan against the OLTAS Challan Status query at tin.tin.nsdl.com using BSR code, serial number, and deposit date. Mark each challan as "matched" or "unmatched" before the quarter's statement is prepared. An unmatched challan discovered after filing costs Rs. 3,600+ in fees; discovered before filing, it costs nothing.

Step 2 — PAN and section code checks at the point of payment. Before making the first payment to any new vendor, run their PAN through the income-tax PAN verification service and check Aadhaar linkage status on the income-tax portal. Confirm the applicable section code — Section 194C for a works contract, Section 194J for professional or technical service fees, Section 194I for rent, Section 194H for commission. The 194C-vs-194J misclassification is the most frequent section code error in practice, particularly for software-related engagements where the nature of service straddles both categories.

Step 3 — Three-way quarterly reconciliation before filing. Before uploading the quarterly statement, reconcile (a) total TDS per your accounting books, (b) total TDS per the draft return, and (c) total TDS challan payments per OLTAS. All three must agree to the rupee. Any gap is a default waiting to happen. For Form 24Q Q4 specifically, add a fourth column: Annexure II gross salary totals per the return vs. the payroll system's payslip totals for the full year.

Key Takeaways

• No statutory limit exists on TDS return revisions, but every revision is evidence of a process failure upstream — trace it to the root cause and fix it there.
• Always start from the latest conso file downloaded from TRACES on the day you begin; a stale file overwrites corrections already accepted by CPC-TDS and creates new defaults.
• Match the correction type to the error: C2 for challan details, C3 for deductee details, C5 for PAN-only updates, C9 for new additions — selecting the wrong type is the leading cause of rejection.
• The Section 271H penalty waiver (which can reach Rs. 1,00,000) requires you to correct, pay TDS, pay interest, and pay the Section 234E fee within one year of the original due date — the window closes faster than most deductors expect.
• Section 201(1A) interest runs monthly at 1% (short deduction) and 1.5% (short payment) — on a Rs. 5,00,000 short-payment situation, that is Rs. 7,500 per month accruing silently until the challan is matched.
• Form 24Q Annexure II errors in Q4 block correct Form 16 issuance and create ITR mismatches that bring employees back to you repeatedly — invest time in the February proof submission reconciliation to prevent Q4 C4 corrections.
• PAN validation and Aadhaar linkage checks at the first payment, not after the quarterly return is filed, eliminate the single largest category of TDS defaults in practice.