TDS Correction: How to Fix Errors and Avoid Penalties

TDS Correction: How to Fix Errors and Avoid Penalties

A TDS correction return filed on TRACES lets you fix almost any error in a previously submitted TDS statement — wrong PAN, incorrect challan details, misapplied section, short deduction, or missing deductee rows — without penalty escalation, provided you act quickly. In FY 2026-27, the CPC-TDS (Centralised Processing Centre for TDS) engine cross-validates your filing against four independent data sources simultaneously and flags mismatches within days of upload. The correction mechanism exists and the law fully supports it; the only real question is whether you use it before interest, late-filing fees and penalties compound into a much larger problem than the original error.

Why TDS Errors Have Become Harder to Ignore in 2026

The CPC-TDS engine now validates every filed return against four simultaneous data streams: the challan data from OLTAS (Online Tax Accounting System), the live PAN master database, the deductee's AIS (Annual Information Statement), and payment data cross-reported by counterparties under their own TDS obligations — for instance, under Section 194Q or 194-O.

Any discrepancy across these four streams generates a "default" visible on your TRACES (Tax Reconciliation Analysis and Correction Enabling System) dashboard. In earlier years defaults sometimes sat unresolved for months before intimations were issued. In FY 2026-27, default summaries are generated more frequently, and CPC-TDS intimation letters reach deductors within weeks of filing — sometimes before the deductor has even logged into TRACES to verify the filing was processed.

Three categories of defaults are generated most often:

• Short deduction defaults: The TDS you deducted is lower than what CPC-TDS calculates based on your declared payment and the applicable rate for the section you cited.
• PAN-mismatch defaults: The PAN you entered does not match the PAN master for the deductee's name and date of birth — or the PAN is inactive, inoperative, or structurally invalid.
• Challan mismatch defaults: The BSR (Basic Statistical Returns) code, challan serial number, or deposit date mapped to a deductee row does not match the corresponding challan in OLTAS.

Each category has a specific remedy on TRACES. All remedies cost more the longer they are deferred.

The Seven Most Common TDS Errors — and How CPC-TDS Spots Them

Understanding how each error is detected helps you prevent it at source.

1. Wrong or invalid PAN. CPC-TDS validates every deductee PAN against the live PAN master. A PAN that belongs to a different name, has been inactivated, or contains even a single character typo fails instantly. The deductee also loses TDS credit in their Form 26AS and AIS — creating a downstream dispute entirely separate from your compliance exposure.

1. Incorrect challan details. The BSR code, challan serial number, and deposit date form the three legs of a Challan Identification Number (CIN). If any one is wrong, the challan cannot be matched to OLTAS, and all deductees mapped to that challan lose their TDS credit.

1. Wrong assessment year or quarter. Mapping a payment made in Q1 FY 2026-27 to Q2, or citing Assessment Year (AY) 2026-27 instead of AY 2027-28 for FY 2026-27 deductions, lands the credit in the wrong year in the deductee's 26AS.

1. Wrong section code. A contractor payment (Section 194C) booked as a professional fee (Section 194J), or vice versa, triggers a rate mismatch. Section 194C applies at 1% for individuals/HUFs and 2% for others; Section 194J applies at 2% for technical services and 10% for professional services. The wrong section means either under-deduction (a default) or over-deduction (a vendor dispute and a refund claim).

1. Short deduction or short payment. Short deduction arises when the rate or the base amount is understated. Short payment arises when the correct TDS is deducted but the deposit to the government is lower — for example, a rounding error, a challan mapped to the wrong quarter, or a payroll adjustment that was not matched to the corresponding challan.

1. Missing deductee rows. If a payment was made, TDS was deducted and deposited, but the deductee was never added as a row in the return, the deposited tax appears "unmatched" in OLTAS and no credit reaches the payee.

1. Duplicate deductee rows. The same deductee entered twice — a copy-paste error in the RPU (Return Preparation Utility) — results in double credit appearing in Form 26AS, which CPC-TDS flags as an anomaly and may disallow.

Correction Types on TRACES: C1 to C9 Explained

TRACES classifies correction returns into six types. A single correction return can include multiple types simultaneously. Using the wrong type — or omitting the required type — causes rejection at the FVU (File Validation Utility) stage before the file is even uploaded.

One critical constraint you must know: Once a correction return is accepted, you cannot delete a deductee row or a challan row through a subsequent correction. You can only modify amounts or add new rows. If a row was entered by mistake, you must zero out the amounts and remap it — refer to the TRACES technical help document for the exact zero-amount workaround applicable to your form type before attempting this.

Step-by-Step: Filing a TDS Correction Return Today

Follow these steps in order. Skipping steps 2 and 3 is the single most common reason correction returns are rejected or generate new defaults.

1. Log in to TRACES (traces.gov.in) using your TAN credentials.
2. Download the Conso (Consolidated) File for the relevant form (24Q / 26Q / 27Q / 27EQ), financial year, and quarter. The conso file is the authorised base for corrections — never work from your original RPU file or a local copy.
3. Download the Justification Report for the same period. This report lists every default CPC-TDS has raised: short deduction amounts, PAN mismatches, challan mismatches. Work through every line of the justification report before opening the RPU.
4. Open the conso file in the latest version of the RPU, available for download from the NSDL TIN website (tin.tin.nsdl.com). Do not use an older RPU version; RPU releases are updated regularly and earlier versions may not support current validation rules.
5. Make corrections in the RPU, selecting the appropriate correction type(s). If adding a new challan under C9, confirm the challan has already cleared in OLTAS — this typically takes 3–4 banking days after payment — before mapping deductees to it.
6. Validate using the FVU. The FVU checks structural integrity: all mandatory fields, PAN format, section codes, challan mapping. Resolve every FVU error before proceeding; a file that fails FVU cannot be uploaded.
7. Generate the `.fvu` file and the Form 27A control chart.
8. Upload on the e-filing portal (incometax.gov.in) under the TDS/TCS returns section. Provide the acknowledgment number of the original return when prompted.
9. Track processing on TRACES. Allow 3–5 working days. The default status for corrected items should move from "Open" to "Closed" in your default summary once CPC-TDS processes the correction.
10. Deposit any additional TDS, interest, or late-filing fee through the TIN 2.0 portal using Challan 281, and map the new challan through a subsequent C9 correction if needed.

What a TDS Default Actually Costs: A Worked Example

Abstract penalty sections become concrete when you put numbers to them.

The scenario: ABC Consulting Pvt Ltd deducts TDS under Section 194J from a consultant at 2% (technical services rate) instead of 10% (professional services rate) for Q2 FY 2026-27 (July–September 2026). Gross fee: Rs. 5,00,000. TDS deducted and deposited: Rs. 10,000. TDS that should have been deducted: Rs. 50,000. Short deduction: Rs. 40,000. The company catches the error when reviewing its TRACES default summary in December 2026 — approximately 75 days after the quarter-end date of 30 September 2026.

Cost if corrected promptly in December 2026:

Interest under Section 201(1A) — short deduction limb (1% per month): Period: 30 September 2026 (date tax was deductible) to 15 December 2026 (date of actual deduction) = October, November, December — 3 months (partial months count as full). Interest = Rs. 40,000 × 1% × 3 = Rs. 1,200

Interest under Section 201(1A) — deposit delay limb (1.5% per month): Period: 15 December 2026 (deduction) to 20 December 2026 (deposit) = 1 month. Interest = Rs. 40,000 × 1.5% × 1 = Rs. 600

Total additional outflow: Rs. 40,000 (shortfall TDS) + Rs. 1,200 + Rs. 600 = Rs. 41,800.

Cost if the same error is caught 12 months later (December 2027):

Section 201(1A) — short deduction limb: Rs. 40,000 × 1% × 15 months = Rs. 6,000 Section 201(1A) — deposit limb: Rs. 40,000 × 1.5% × 1 month = Rs. 600 Section 271H penalty (minimum): Rs. 10,000 — and the Assessing Officer has discretion to levy up to Rs. 1,00,000 if the incorrect section coding is considered deliberate.

Total additional outflow after 12-month delay: Rs. 40,000 + Rs. 16,600 + Rs. 10,000 = Rs. 66,600 minimum — plus the management time spent responding to assessment proceedings.

Late-filing fee scenario (standalone):

A company files Form 26Q for Q1 FY 2026-27 (due 31 July 2026) on 5 November 2026 — a delay of 97 days. Total TDS shown in the return: Rs. 14,000.

Section 234E fee: Rs. 200 × 97 days = Rs. 19,400. But Section 234E caps the fee at the TDS amount in the return. Since Rs. 19,400 exceeds Rs. 14,000, the fee is capped at Rs. 14,000 — equal to 100% of the tax itself, purely for late filing.

Common Mistakes in Correction Returns — Pitfalls to Avoid

These are the errors that cause correction returns to be rejected or, worse, to generate new defaults on top of the originals.

• Using a stale conso file. If a previous correction has already been processed by CPC-TDS, the conso file on TRACES will have been updated. Preparing a second correction from an old conso file causes a version mismatch and instant rejection. Always download a fresh conso file immediately before starting work.
• Using an outdated RPU version. Check the NSDL TIN website for the current RPU release before every correction, not just quarterly filings. A structural change in the FVU may silently pass an older RPU but fail on upload.
• Mapping deductees to an uncleared challan. A new challan added under C9 must already appear in OLTAS (verified in the "Challan Status" check on TRACES) before you map deductees to it. Paying the challan and filing the correction on the same day almost always results in rejection.
• Using C3 to update a previously invalid PAN. When the original return carried a PAN reported as PANNOTAVBL or PANINVALID, the correction requires C5 — not C3. C5 triggers a separate TRACES verification step. Using C3 for this purpose causes the correction to be processed without updating the PAN, leaving the default open.
• Correcting without depositing the shortfall first. Filing a correction return that acknowledges a short deduction, but without depositing the balance TDS and interest before upload, means CPC-TDS will close the correction but immediately re-raise a short payment default. The sequence is: deposit first, then correct.
• Errors in the Form 27A control totals. The control chart (Form 27A) must exactly match the totals generated by the FVU. Any discrepancy — even Rs. 1 — causes the upload to be rejected.
• Correcting the wrong quarter. Q2 FY 2026-27 and Q2 FY 2025-26 have completely separate conso files and acknowledgment numbers. Confirm the quarter from the original acknowledgment slip before initiating any correction.

Section 194 Hotspots Generating the Most Defaults in 2026

Certain sections account for a disproportionate share of CPC-TDS defaults. Audit these first when reviewing your TRACES default summary.

Section 194C — Contractor payments. The highest-volume TDS section for most businesses and therefore the highest-volume error source. Rate: 1% for individuals/HUFs, 2% for all others. Annual aggregate threshold: Rs. 1,00,000 per contractor. The most common error is misclassifying a labour or works contract as a professional service (Section 194J), which applies a different rate. Build a clear internal rule: if the dominant element of the contract is labour and material, it is 194C; if it is intellectual skill or expertise, it is 194J.

Section 194J — Professional and technical fees. The 2% (technical) versus 10% (professional) distinction continues to be a major source of short-deduction defaults. Technical services — IT support, maintenance, repair, assembly — attract 2%. Legal, medical, architectural, management consultancy, and film-related services attract 10%. When a single invoice covers both, apportion if the invoice itemises the charges; otherwise apply 10% to the whole.

Section 194-IB — Rent paid by individuals and HUFs. Applies when an individual or HUF (not subject to tax audit) pays monthly rent exceeding Rs. 50,000. TDS at 5% is deductible once — either in the last month of the tenancy or the last month of the financial year (31 March) — on the total rent for the year. Many individuals still deduct monthly, which generates confusion. Equally common: forgetting to deduct at all because the provision feels less familiar than the corporate 194-I.

Section 194Q — Purchase of goods. Applicable to buyers whose turnover in the preceding financial year exceeded Rs. 10 crore, on purchases from any resident seller once the aggregate crosses Rs. 50 lakh in a financial year. Rate: 0.1%. The critical error here is treating the Rs. 50 lakh threshold as an aggregate across all vendors rather than tracking it vendor by vendor. Maintain a cumulative purchase tracker per vendor in your accounts payable system and flag the threshold breach as a system alert.

Section 194-O — E-commerce operators. Applicable to e-commerce operators on amounts credited or paid to e-commerce participants. Rate: 1% on gross amount. The most frequent error is deducting TDS on the net settlement (after platform fees) rather than the gross amount credited to the participant before deductions.

Responding to a CPC-TDS Default Notice Within 30 Days

When a default notice arrives — by email or under "Default Summary" on your TRACES dashboard — follow this sequence without delay.

1. Read the notice completely before acting. Identify the quarter, form type, and nature of each default line — short deduction, short payment, late deposit, late filing, or PAN-related.
2. Match each default line to your records. Pull the original return acknowledgment, the challan details, and the payment vouchers for each flagged deductee.
3. Categorise each default line: genuine error (you agree with CPC-TDS), data-entry mismatch (correct underlying transaction, wrong data entered), or disputed default (you believe CPC-TDS is incorrect based on the facts).
4. For genuine errors and data-entry mismatches: Deposit the shortfall TDS plus Section 201(1A) interest immediately, then file the correction return. Do not file the correction before the challan clears in OLTAS.
5. For disputed defaults: File a rectification request on TRACES and, if required, submit a written response to the Assessing Officer with supporting documentation — bank confirmation of the challan, payment vouchers, PAN verification output.
6. Maintain a notice register. Log each notice with its receipt date, nature, default amount, response date, correction or rectification tracking number, and closure date. This register is essential if the same default recurs or if a scrutiny assessment is opened.

The standard response window in a CPC-TDS intimation is 30 days. Missing it does not close the case permanently, but it allows CPC-TDS to raise a demand — and that demand attracts Section 220 interest (1% per month) in addition to the Section 201(1A) interest already accruing on the underlying default.

Building a TDS Hygiene Cadence: Prevention Is Cheaper Than Cure

The most expensive TDS correction is the one you file in response to a penalty notice. A structured monthly-and-quarterly cadence eliminates the majority of errors before the filing stage.

Monthly (within 7 days of month-end):

• Run a bulk PAN verification on all new vendors and employees added during the month using the TRACES bulk PAN verification utility. Never deduct TDS against an unverified PAN.
• Reconcile TDS deducted in the books against challans deposited via TIN 2.0 for the same month. The difference should be zero. Investigate immediately if it is not.
• Record CINs (BSR code + serial number + date) accurately in your TDS register at the time of challan payment — not retrospectively at quarter-end when memory fails.

Quarterly (within 10 days of quarter-end, before filing):

• Validate every TDS entry against a TDS master — a static internal reference document listing each vendor or payment category, the applicable section, the rate, and the aggregate threshold. Update the master whenever a section amendment is notified.
• Reconcile Form 26Q or 24Q totals against your accounts payable or payroll ledger for the quarter. Every rupee paid in a TDS-liable category must either appear in the return or be documented as below-threshold with the year-to-date running total recorded.
• Download the TRACES default summary for the preceding quarter — which will have been fully processed by now — and resolve every open default before filing the current quarter's return.

Annually (before 31 May, the Q4 filing deadline):

• Reconcile the year's TDS with Form 16A issued to vendors and Form 16 issued to employees. Every deductee who has received a TDS certificate must find the corresponding credit when they view their Form 26AS or AIS.
• For Form 24Q, verify that Annexure II (the salary computation sheet) is consistent with each employee's individual tax working, including the correct Chapter VI-A deductions and exempt allowances, before submitting the Q4 return.

For organisations processing more than 500 TDS entries per quarter, consider TDS automation software that integrates with your ERP, validates PAN automatically, maps sections from your vendor master, and produces FVU-ready files. The implementation cost is typically recovered within two quarters through avoided interest, late-filing fees, and professional rework.

Key Takeaways

• A correction return on TRACES can fix virtually any TDS error — challan details, PAN, section, amounts, missing rows — but the cost rises sharply the longer you wait; the same Rs. 40,000 short deduction costs Rs. 1,800 in interest if corrected in 75 days and Rs. 16,600+ if corrected after 12 months.
• Know your correction type before opening the RPU: C2 for challan detail errors, C3 for deductee detail and amount corrections, C5 specifically for updating an invalid or dummy PAN to a valid PAN, and C9 for adding entirely new challans or omitted deductee rows.
• Always start from the most recently downloaded conso file from TRACES — never from your original RPU file or a local copy from a prior correction session.
• Section 234E late-filing fee of Rs. 200 per day is capped at the TDS amount in the return, but even at 100% of tax, it is entirely avoidable by filing on the due date: 31 July (Q1), 31 October (Q2), 31 January (Q3), 31 May (Q4).
• Deposit the shortfall TDS and Section 201(1A) interest before uploading the correction return — not simultaneously, not after. CPC-TDS will re-open a short payment default if the balance challan has not cleared in OLTAS when the correction is processed.
• The five sections generating the most defaults in 2026 are 194C (contractors), 194J (professional and technical fees), 194-IB (individual rent payers), 194Q (goods purchases over Rs. 50 lakh), and 194-O (e-commerce operators). Build explicit mapping rules and threshold trackers for each.
• A monthly PAN verification, challan reconciliation, and quarterly default-summary review eliminates the vast majority of errors before filing — prevention takes a few hours a month; remediation after a penalty notice can take days and tens of thousands of rupees.