Tds return revised but only partially updated

This query is : Resolved

Querist : Anonymous

Querist : Anonymous (Querist)

21 May 2013 Hello,

I have revised the TDS return of my company in Feb'2013 for the period Q1 F.Y.12-13 , entries are modified were 25.
Statement status of this return is showing as proceeded. But when i am downloading 16A form of vendors, i have noticed that only 7 entries are modified and other 18 entries are not modified.
I have dialed on Customer care number and dropped mail to them but they are not responding. Is there any way to sort out this problem.

Pls help me on above matter as we are getting continuous reminder from our vendors

Thanks in advance

Querist : Anonymous

Querist : Anonymous (Querist)

22 May 2013 Pls reply on my query

Aashok Kumar Sharma

Aashok Kumar Sharma (Expert)
Follow

28 July 2025 This is a fairly common issue with **revised TDS returns** — where only **some records get updated in TRACES**, even though the correction statement was processed.

Here's how to troubleshoot and resolve your issue:

---

### ✅ Step-by-Step Resolution:

#### 🔹 1. **Verify the Revised Return Acknowledgment**

Check the **FVU file summary** or **Correction Statement Token Number**:

* Confirm that **all 25 deductee records** were included in the correction statement.
* Ensure they were **flagged properly** as modified or deleted/added.

If only 7 were modified in the FVU or validation report, then only 7 got uploaded.

---

#### 🔹 2. **Download the Justification Report (JR)**

Login to [TRACES](https://www.tdscpc.gov.in/) → Go to:

> **Defaults** → **Request for Justification Report** → Select relevant FY, Quarter, Form

This report will show:

* Which deductee entries were processed
* Which were **rejected or ignored**, and **why** (e.g., mismatch, invalid PAN, etc.)

---

#### 🔹 3. **Possible Reasons for Partial Update**

* **Invalid PANs or formatting issues** for some entries
* **Duplicate record structure** (e.g., if same record is added again without proper deletion)
* TDS deposited through **different challans not included** in correction file
* **PAN not matching with NSDL database**

---

#### 🔹 4. **Next Steps**

Once you identify the failed entries from the Justification Report:

* **Prepare another correction statement**, including **only the failed/ignored entries**
* Make sure:

* Correct challan reference is used
* PAN details are accurate
* Record flag is set correctly (e.g., “C” for correction, “A” for add, “D” for delete)

Revalidate using **latest RPU and FVU** utilities before uploading.

---

#### 🔹 5. **Escalate if Still Unresolved**

If the issue persists and TRACES is unresponsive:

* **Raise a grievance** on TRACES via:

> **Communication** → **Request for Resolution** → Select Return & Token Number

* Or email **[contactus@tdscpc.gov.in](mailto:contactus@tdscpc.gov.in)** with:

* TAN
* FY/QTR
* Form type
* Token number of correction filed
* Screen shots or details of unmatched records

---

### 📝 Suggestion to Vendors

You may inform vendors:

> “Correction is under process and being updated in TRACES. Form 16A will be regenerated once all entries reflect. TDS has been paid and will reflect in 26AS once updated.”

---

Let me know if you want help reviewing your correction statement structure or drafting a follow-up email to TRACES.

You need to be the querist or approved CAclub expert to take part in this query .
Click here to login now