TDS || Error 13 - Type Mismatch
Solution:
This issue is related to
particular Client's database or Conso file issue.
To resolve this please follow the steps below:
Step 1:
Please re-import the consolidate file through Export/Import – Import from Text/FVU/TDS
file option and import the particular file with New Client Code No.
Step 2:
Select New Deductor master and after that import this
consolidate file in correction option and then do the correction in this
particular file.
Once the correction is done, after that go for efiling.
This will helps.
Related Articles
TDS || Conso Import → File is not valid, TAN mismatch
Consolidate File Import – File Invalid Due to TAN Mismatch Root cause of the error → This error occurs when attempting to import a consolidated file associated with one Deductor into a different Deductor’s account. A discrepancy in the TAN (Tax ...TDS || Correction E-Filing → Please Select correct Correction Consolidate File to Validate E-file
Root Cause of the Error → This error arises when multiple Consolidated Files are requested, and the incorrect file is selected during the e-filing process. Specifically, if you download multiple Consolidated Files, make corrections using the first ...TDS Correction Excel Import "Error converting data type varchar to numeric"
TDS Correction Excel Import Error:- 2147217913 Error converting data type varchar to numeric Possible Resolution To solve this excel import issue, here are some suggestions are given below. 1. In the Excel template, it is to be checked that the ...TDS || Import Challan / Bulk Challan Verification → Run time Error 430: Class Does Not Support Automation error
This error occurs due to various system or software configuration issues. Below is the root cause analysis and step-by-step solutions to resolve the problem. Root Cause of the Error → Application is not running with administrative privileges. Missing ...TDS || Run Time error 75: Path File access error
Root Cause of the error → This error occurs due to insufficient permissions for accessing the specified path or file (C:\KDK Data) or when the software is not executed with Administrator privileges. It can also occur if the KDK Data folder is ...