TDS > Error 13 - Type Mismatch

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 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 ...

    • Express TDS- Correction process for TDS return

      Express TDS- Correction process for TDS return Process for offline correction for 24Q, 26Q, 27Q & 27EQ from TDS software >> The Correction from TDS software can be processed once you have the Consolidate file (.tds File). Select Respective Deductor , ...

    • How to import text/consolidate file in software

      How to import text/consolidate  file in software The purpose of importing a text/conso  file is that all your old filed data gets into the software. You do not have to enter the master and transactions information of the Deductor and the Deductee ...

    • Invalid file format or BCP Utility error while importing consolidate file

      SOLUTION: To resolve the "Invalid file format or BCP Utility error" error which generally occurs while importing txt\tds\fvu file please go to Tools > Option Settings, Here set default path in all Export Utility Path and then OK. Export Utility path ...

    • Error in income tax Auditor > Run time error 339

      Error in income tax Auditor > Run time error 339 Component 'KDKClient.ocx' or one of its dependencies not correctly registered: a file is missing or invalid.                           Solution: Step 1. To resolve the error, Go to Root location of the ...