TDS Correction Return Filing: How to Fix PAN, Challan and TRACES Defaults
Errors in a filed TDS return can create problems for both deductors and deductees. An incorrect PAN may prevent tax credit from appearing correctly, while an unmatched challan or short deduction can result in defaults on the TRACES portal.
Fortunately, many reporting errors can be resolved through TDS correction return filing, provided the appropriate correction procedure is followed.
In this guide, we explain how to identify PAN and challan mismatches, download TRACES justification reports, file correction statements and resolve common TDS defaults.
What Is a TDS Correction Return?
A TDS correction return, also called a TDS correction statement, is submitted to rectify incorrect or incomplete information in an original TDS/TCS statement.
It allows deductors to correct eligible reporting details without submitting an entirely new original return.
Common reasons for filing a correction statement include:
- Incorrect or invalid deductee PAN.
- Unmatched or overbooked challans.
- Incorrect deductee or salary details.
- Missing TDS transactions.
- Errors in reported tax deduction or payment information.
- Defaults identified after processing by TRACES.
Corrections must follow the prescribed procedure for the relevant financial year, statement and error type.
Common Errors That Require TDS Correction Filing
1. Incorrect or Invalid PAN Details
PAN errors occur when the PAN reported in the TDS statement does not match the correct deductee information.
These errors can affect the deductee's tax credit and may trigger higher-rate deduction implications.
How to fix PAN errors:
- Log in to the TRACES portal using the deductor account.
- Verify the deductee's correct PAN.
- Open the applicable correction facility for the relevant statement.
- Select the PAN correction option, where available.
- Update the relevant deductee details and submit the correction.
- Track the correction request until processing is complete.
TRACES restricts certain PAN correction attempts. For example, changing one valid PAN to another valid PAN is generally permitted only once for the relevant statement entry.
Therefore, confirm the correct PAN before submitting the correction.
2. Unmatched or Overbooked Challans
A challan may become unmatched when its details in the TDS statement differ from the corresponding payment records.
Common causes include an incorrect:
- BSR code.
- Challan serial number.
- Date of deposit.
- Challan amount.
- TAN or other relevant challan details.
An overbooked challan occurs when the amount allocated to deductee entries exceeds the available amount of that challan.
How to resolve challan mismatches:
- Check the challan status and consumption details on TRACES.
- Compare the reported details with the actual challan records.
- Identify whether the problem is incorrect reporting, challan allocation or the underlying tax payment.
- Use the applicable challan correction, tagging or deductee-row adjustment facility.
- Submit the required correction and verify its processing status.
If insufficient tax has actually been deposited, an additional payment may be necessary.
Important: Correcting challan details in a TDS statement is different from correcting the underlying tax-payment challan. The appropriate procedure depends on the error. Certain payment-challan corrections require a separate TRACES or Assessing Officer process.
3. TRACES Defaults and Short Deduction Errors
TRACES may identify defaults when a filed statement contains inconsistencies or unpaid amounts.
Examples include:
- Short deduction of TDS.
- Short payment of deducted tax.
- Interest for late deduction or late payment.
- Applicable late-filing fees.
- Incorrect challan allocation.
Before making changes, deductors should download the TRACES Justification Report to understand the exact reason for the default.
How to Download the TRACES Justification Report
The Justification Report provides transaction-level information about defaults detected during processing of a TDS/TCS statement.
To obtain the report:
- Visit TRACES and log in as a deductor.
- Open the applicable Justification Report request facility.
- Select the financial year, quarter and statement type.
- Complete the required authentication.
- Submit the download request.
- Download the report when it becomes available.
- Review the identified defaults and their calculations.
The report helps distinguish genuine short deductions or unpaid liabilities from reporting mistakes that may be corrected through an updated statement.
How to File a TDS Correction Return Online
The following workflow applies where the relevant online correction facility is available.
Step 1: Log in to TRACES
Access the TRACES portal with the registered deductor credentials.
Step 2: Request a Correction
Navigate to Defaults → Request for Correction.
Select the relevant financial year, quarter and statement type.
Step 3: Choose the Correction Type
Depending on the statement and the options available, select the appropriate correction category.
This may include PAN correction, challan correction, adding a challan, modifying deductee details or correcting personal information.
Step 4: Update the Incorrect Details
Enter the revised information and verify it against original records.
For PAN corrections, confirm the deductee's PAN before submission.
For challan corrections, verify the actual payment details and available challan balance.
Step 5: Submit the Correction
Complete the required authentication and submit the correction request.
Some correction categories may require a registered Digital Signature Certificate (DSC), while others support different authentication methods.
Step 6: Track the Correction Status
Navigate to Defaults → Track Correction Request to review the status.
Save the relevant request details and token number when generated.
If online correction is unavailable, an eligible correction statement may need to be prepared using the consolidated file and prescribed return preparation and validation utilities.
TDS Correction Return: Common Defaults and Solutions
| Error or default |
Possible reason |
Recommended solution |
| Invalid PAN |
Incorrect deductee PAN |
Verify PAN and submit the permitted PAN correction |
| Unmatched challan |
Incorrect challan details |
Reconcile with payment records and correct or tag the challan |
| Overbooked challan |
Allocated TDS exceeds challan balance |
Reallocate eligible deductee entries or pay the shortfall |
| Short deduction |
TDS deducted below the applicable amount |
Verify the applicable rate and liability; pay and correct where required |
| Short payment |
Deposited amount is insufficient or incorrectly linked |
Verify challan balance, correct reporting or deposit the shortfall |
| Late payment interest |
TDS deposited after the applicable due date |
Verify calculation and discharge the applicable interest |
| Incorrect deductee details |
Data entry or reporting mistake |
File the permitted deductee-detail correction |
A default should not automatically be treated as an unpaid tax liability. First identify whether it arose from a reporting mismatch or a genuine shortfall.
Important TDS Correction Rules to Know in 2026
The Income-tax Act, 2025 came into effect on 1 April 2026, creating a transition between old and new TDS reporting requirements.
For statements relating to periods up to 31 March 2026, corrections continue under the applicable Income-tax Act, 1961 framework.
Corrections relating to periods beginning 1 April 2026 must follow the new Act's applicable forms, formats and procedures.
The Income Tax Department's guidance also specifies a two-year correction period, calculated from the end of the relevant tax year in which the original statement was due, subject to the applicable transitional framework.
Always verify the relevant correction deadline and utility before submitting a statement.
How TDS Filing Software Helps Reduce Correction Errors
For Chartered Accountants and businesses managing multiple TDS statements, manually identifying discrepancies and preparing corrections can be time-consuming.
CompuTds TDS Filing Software provides features designed to simplify TDS compliance and correction workflows.
These include:
- PAN validation: Identify incorrect, blank or duplicate PAN entries before filing.
- Challan verification: Import challan records and review payment allocation.
- Justification Report support: Retrieve and work with information required to investigate TRACES defaults.
- Correction return preparation: Prepare correction statements using guided workflows.
- Pre-filing validation: Identify potential errors before generating and submitting returns.
- TRACES integration: Access supported statement, download and correction-related facilities.
Using these features can help reduce repetitive data entry and make correction preparation more organised.
However, software validation should complement, not replace, verification of the underlying tax records and statutory requirements.
Best Practices to Avoid Repeated TDS Corrections
Prevention is usually more efficient than correcting a processed statement.
Before submitting a TDS return, verify PAN details, tax deduction calculations, challan information and deductee records.
Check that payments have been correctly allocated and that the statement uses the applicable form and schema for its reporting period.
After filing, monitor the processing status and review any TRACES defaults promptly.
For additional guidance, read TDS Filing Software: Avoid 7 Common Filing Mistakes.
Frequently Asked Questions
1. What is TDS correction return filing?
TDS correction return filing is the process of correcting eligible errors in an already filed TDS statement, including PAN details, challan information and deductee records.
2. Can I correct a wrong PAN in a filed TDS return?
Yes. Eligible PAN errors can be corrected through the prescribed TDS correction procedure. However, TRACES places limits on certain PAN changes.
3. How do I correct an unmatched challan on TRACES?
Compare the challan details reported in the statement with the actual payment records. Use the applicable TRACES challan correction or tagging facility to resolve the mismatch.
4. What is a TRACES Justification Report?
It is a report containing details and calculations of defaults identified during the processing of a TDS/TCS statement. It helps deductors determine the corrections or payments required.
5. Is paying a TDS default enough to remove it?
Not always. Where a correction statement is required, the deductor must submit the necessary correction even after paying the outstanding amount.
6. Can TDS correction returns be filed after April 2026?
Yes, subject to the applicable statutory time limit. Corrections for periods governed by the Income-tax Act, 1961 continue under the corresponding old Act framework, even after 1 April 2026.
Conclusion
Accurate TDS correction return filing is essential for resolving PAN mismatches, unmatched challans and TRACES defaults.
The correct approach is to identify the source of the error, verify the underlying records, make any required tax payment and submit the appropriate correction statement.
For CAs and businesses managing multiple deductors, a structured correction workflow can improve accuracy and reduce repetitive compliance work.
Simplify TDS correction return preparation with CompuTds TDS Filing Software. Explore its PAN validation, challan reconciliation, TRACES-related features and guided correction return workflows.
Disclaimer: This article is intended for general informational purposes. Tax laws, forms, utilities and due dates may change through notifications or amendments. Taxpayers should verify the latest official guidance and obtain professional advice based on their facts.