This article applies to Microsoft Dynamics AX for the Indian (in) region.
As per File Validation Utility (FVU) tool version 5.0, special characters are not allowed in the Deductor/Collector Name, Branch/Division and so on. New changes are incorporated for generation of the .txt file in the Indian version of Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, and Microsoft Dynamics AX 2009 SP1, which make sure you can:
1. Remove special characters from Deductor/Collector Name if any.
2. Remove special characters from Branch/Division.
Special characters in Deductor/Collector name and Branch/Division may cause failure of txt file for FVU validation.
This Current FVU Version is 5.0 for quarterly TDS returns.
The Key Features of the FVU 5.0 are as below:
Except point "D" all other changes listed below will have no impact as either configurable or compliant in the application.
A. Remark 'B' is made applicable for Section code 192A (Payment of accumulated balance due to an employee) for Form 26Q.
i. The above is applicable for regular as well as correction statements.
ii. The section code is denoted as '2AA' in the .txt file.
B. New Section code 194IA (Payment on transfer of certain immovable property other than agricultural land. i.e. TDS on sale of property) has been added under list of sections available for Form 26Q.
i. The above is applicable only for regular and correction statements (C3) of Form 26Q pertaining to FY 2013-14 onwards.
ii. The section code for the same to be populated under .txt file is "9IA".
C. Mandatory to mention Email ID and mobile number of responsible person in TDS/TCS Statement.
i. One of e-mail IDs of Deductor/Collector or Responsible person is required to be provided in the statement.
ii. The value in the field 'Mobile Number of responsible person' is mandatory.
D. Only blank values, special characters, dots or spaces (for example `~! @#$ %^&*() _+,. /? ;:’”[{]}\|) are not allowed for below fields of Batch Header in the FVU file.
i. The values as referred above are not allowed in the fields referred in the table below, in case, Deductor/Collector enters such values in the file prepared by them, FVU will generate relevant error message.
ii. Deductor/Collector should mention the correct values in the below fields as per the specified file format:
|
Field Name |
Field No. |
|
Name of Deductor |
19 |
|
Deductor's Branch/ Division |
20 |
|
Name of Person responsible for Deduction |
33 |
|
Designation of the Person responsible for Deduction |
34 |
iii. Similarly, only special characters are not allowed in the address fields of Deductor/Collector and Responsible person.
E. Incorporation of TAN and TAN name in the Challan Status Inquiry (i.e. .CSI) file and verification with the TDS/TCS statement during the time of validation through the FVU.
i. TAN: In case, the TAN of the Deductor/Collector as per CSI file does not match with the TAN as per the TDS/TCS statement, FVU will reject the TDS/TCS file and appropriate error message "TAN of deductor in statement does not match the TAN in CSI file" will be displayed to you at the time of validating the file through FVU.
ii. TAN Name: In case, the TAN Name (for example, Name of Deductor/Collector) as per CSI file does not match with the name as per the TDS/TCS statement, FVU will generate a popup message "Name of Deductor in the statement should exactly match the Name of deductor as per TAN Master Database of Income Tax Department".
F. Change of State name from "ORISSA" to "ODISHA".
i. Change of State name from "ORISSA" to "ODISHA" has been incorporated in the versions of FVU.
Resolution
The changes in the hotfix enable this update.
Hotfix information
A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website:
https://mbs.microsoft.com/support/newstart.aspx You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:
Partners
https://mbs.microsoft.com/partnersource/resources/support/supportinformation/Global+Support+ContactsCustomers
https://mbs.microsoft.com/customersource/support/information/SupportInformation/global_support_contacts_eng.htmIn special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.
Installation information
If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must apply these changes in a test environment before you apply the hotfix in a production environment.
For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
893082 How to install a Microsoft Dynamics AX hotfix
Prerequisites
You must have one of the following products installed to apply this hotfix:
-
Microsoft Dynamics AX 2012 R3
-
Microsoft Dynamics AX 2012 R2
-
Microsoft Dynamics AX 2009 SP1
Restart requirement
You must restart the Application Object Server (AOS) service after you apply the hotfix.
File information
The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
