26 February 2012
hi. I am difficulty in filing a correction statement of TDS. New validity of SPECTRUM is asking for a Consolidated file name with path? I am confused which file should i take? Should i take the file which has been downloaded from NSDL or other? Also what is hase value?
26 February 2012
when u revise tds return first time then use .fvu file which is generated by u while filling the original return. when u rerevised the return then use the file downloaded from nsdl site
26 February 2012
Thanks for the reply Sir. But when I am using the file downloaded from NSDL, error file is getting generated for challan that is added to correction statement.
27 February 2012
I have checked everything. It also correct. Error fil is showing message as challan file is nt present in chall file imported. However challan is thr in CSI also
27 February 2012
I have contacted them also. Even they are not sure of this problem. File is proper nly. I have again downloaded the same but still the error is thr.
28 February 2012
Consolidated file name path. it will show the file extension ".tds" this file which consolidated file downloaded from NSDL site for correction
27 July 2025
It looks like you’re facing a tricky issue with the correction statement in SPECTRUM where the challan file isn’t matching properly in the consolidated file downloaded from NSDL, causing errors.
Here are a few things you can try/check:
1. **File Consistency:**
* The `.tds` consolidated file from NSDL should have all the details, including challan info. If challan data is missing or corrupted in this file, the software will throw errors. * Sometimes, downloading the consolidated file multiple times after a gap or using a different browser helps.
2. **Hash Value / Hash File:**
* Hash value is a checksum to ensure data integrity. If the file’s hash doesn’t match, it means the file got corrupted or altered. * Use the FVU (File Validation Utility) from NSDL to check if the file passes validation.
3. **FVU File:**
* For the first revision, you should use the `.fvu` file generated when you originally filled the return. For subsequent revisions, use the `.tds` file from NSDL. * Make sure the challan details are correctly entered and available in your correction file.
4. **Check Challan Status:**
* Verify the challan on the NSDL website you mentioned to confirm it is recorded correctly and no mismatch.
5. **Try Importing Without Challan in Correction File:**
* Sometimes the challan data causes issues if it is not exactly matching. If allowed, try excluding the challan entry from the correction file and check if it uploads. Then update challan separately if needed.
6. **Software Updates:**
* Make sure you are using the latest version of SPECTRUM and the latest FVU file.
7. **Contact Support:**
* Since you have already contacted IT department and visited commissioner office, follow up with them regularly and share all error logs/screenshots. They sometimes need to fix backend mismatches.
---
**Summary:**
* Use the `.tds` consolidated file from NSDL for correction returns. * Validate file with FVU utility before uploading. * Check challan data consistency carefully. * If error persists, contact IT helpdesk with error details and keep trying.