The Report Generation Utility can be used to generate validated Form 61A XML Reports which is to be submitted to ITD. Report Generation Utility is a desktop utility based on java
The utility contains Toolbars, messages and buttons. The Report Generation Utility toolbar has a list of pre-arranged command buttons. These buttons in the toolbar are action interfaces that allow the user to perform utility functions.
The utility displays following types of messages:
|Information||Informs about the results of a command.||File saved successfully|
|Option||Informs the user about multiple options. User can choose to proceed or cancel.||Any data present in the form will be erased. Do you wish to continue?|
Once the JRE version 1.8 Update 101 or later is installed, the utility can be deployed on user machine by extracting the downloaded file to the folder using tools like WinZip or WinRAR.
After the JRE version and utility is installed, the Report Generation Validation Utility can be run as follows:
1. Go to the folder where the contents of the Utility have been extracted.
2. Click on RGU-Form61A-v1.jar file. It displays the General Instructions window.
The downloaded zip file has to be extracted using WinZip or WinRAR tools. For more details refer section 3.4 of the user guide.
Yes. Report Generation Utility requires JRE to run on Windows based operating system. Download and install JRE version 1.8 Update 101 or later. For more details, refer section 3.2 of the user guide.
Click on RGU-Form61A-v1.jar file to run the utility. For more details, refer section 3.4 of the user guide.
Form 61A has four parts. Part A contains statement details, which is common to all transaction types. Other three parts relate to report level information (depending on transaction type), which are as follows:
Reporting person/entity is required to furnish separate Form 61 A for each transaction type.
1. Open Form 61A utility. Select the SFT code from the Drop down on the Instructions page
2. Utility will ask permission to proceed, click on OK to continue
User needs to click on ‘Statement (Part A)’ and fill statement details consisting of Reporting Entity Details, Statements Details and Principal Officer Details. User needs to enter all mandatory fields.
Report details can be captured by importing CSV files or manual data entry.
User can use Coma Separated Values (CSV) file to capture report details.
1. Click on Export CSV button to download CSV Template
2. Save the CSV at desired location
3. Open the CSV file and fill the details by data entry or pasting values
4. Click on Import CSV button
5. Select the pre saved CSV from file system and then click on Open button to upload
6. CSV imported successfully dialog box will be displayed. Click on OK button to complete the import
1. Click on Add Row button to add a new information record
2. Click on Delete Row button to delete the selected information record
3. Click on Edit Row button to edit the selected information record
4. Fill the details and click on Save button to save the details
Data can be captured by importing CSV or data entry.
User should use DD-MM-YYYY format while entering data in CSV. If date is entered in incorrect format then CSV will not be imported successfully.
Yes. Save the data using Save button in the tool bar. The data is saved with a draft extension. To retrieve the data in the utility, use the Open button from the tool bar.
Data format to be used for various fields is described in Form 61A or Annexure B of the user guide.
For Accounts with more than one account holder, user needs to enter multiple record rows for each account, where Account detail (including “Report serial Number”) will be repeated for each account holder. The utility will automatically create reports with unique Report serial Number from the CSV data.
After successful CSV import, data is visible in the relevant tab of the utility.
The utility allows the user to validate the information and identify errors before submission. The errors have been classified in following categories:
|Mandatory Errors||Mandatory Schema level errors need to be resolved by user for successful generation of XML report.|
|Defects||Defects can be Statement level defects or Report level Defects. Statement Defects are those which render the Statement (Part A) defective. Such Statements will be rejected and the reporting entity needs to resubmit the statement. Report defects are those which render a particular report(s) (Part B/C/D) as defective in the statement. A statement may have multiple reports and only reports with defects would be rejected. The reporting entity needs to correct and submit the reports again in the corrected statement.|
|Exceptions||Exceptions do not result in the statement/report being rejected. The exceptions should be reviewed by the reporting person/entities and if any information is available, the reporting entity may provide the information. If any defect is noticed, the reporting entity needs to rectify the defect by submitting a correction statement.|
1. Click on Validate button on the tool bar
2. Utility will display validation errors on Validation Tab
3. Click on Validation row to see details of Validation errors on the right window pane of screen
2. Fix the errors and then click on Validate button again to check whether error has been removed.
3. If there are no validation errors, “Validation Successful” dialog box is displayed to the user.
The errors have been classified as mandatory errors, defects and exceptions. . For more details refer Annexure B of the user guide.
Mandatory errors need to be resolved by user for successful generation of XML report. These are generally schema level errors. For resolving these type of errors, the data filled should be as per the Form 61A schema validation
Defects can be Statement level defects or Report level Defects. Statement Defects are those which render the Statement (Part A) defective. Such Statements will be rejected and the reporting entity needs to resubmit the statement. Report defects are those which render a particular report(s) (Part B/C/D) as defective in the statement. A statement may have multiple reports and only reports with defects would be rejected. The reporting entity needs to correct and submit the reports again in the corrected statement.
Exceptions do not result in the statement/report being rejected. The exceptions should be reviewed by the reporting person/entities and if any information is available, the reporting entity may provide the information. If any defect is noticed, the reporting entity needs to rectify the defect by submitting a correction statement.
When user clicks on validate button, validation summary is displayed in Validation Error tab. On selecting a particular Row on the validation error screen, error details are displayed on screen on the right side. On selecting the error, user is directed towards the erroneous field on the screen.
User can navigate to erroneous fields via Validation Error Details screen on the right side of the screen. Erroneous fields are highlighted in Red and are editable for user to correct.
1. Click on Generate XML button on the toolbar
2. If there are no validation errors, Utility will display Form Validation Successful dialog box, click on OK button.
3. Give the desired path where user wants to save XML on machine and click on save button
Validations have to be performed before generating an XML file. User is not allowed to generate XML Report with invalid data. In Form 61A utility validations are of 3 types – Mandatory, Defects and Exceptions. It is required to resolve any Mandatory Errors before generation of XML report.
The XML Report generated from utility needs to be submitted through e-Filing Portal (https://incometaxindiaefiling.gov.in/)
Generated XML file should have ‘.xml’ extension.
2. Save the CSV at desired location
1. Click on Save button in toolbar
2. File window will be displayed to select the folder where file needs to be saved.
3. Give desired path to save draft XML file
1. Click on Open button in toolbar
2. Select the desired saved file from machine and click on Open button
3. The information in the saved XL file will be loaded
Utility allows user to generate SFT (XML) with no financial transactions in it. This functionality is useful when Reporting Entity has no financial transaction to report.
1. Fill required information in Statement (Part A) and select ND (No Data) from Statement Type drop down field.
2. Save XML to desired location on machine.
In an event, if user needs to send correction statement for a previously submitted statement, User can generate a correction statement.
Steps for correction in previously submitted information:-
1. Open existing XML which need to be corrected
2. Select CB- Correction statement containing correction for previously submitted information selection from Statement Type dropdown list
3. Mention the statement ID of the original Statement which is being corrected in the element ‘Original Statement ID’.
4. Mention the Report Serial Number of the original report which is being corrected in the element ‘Original Report Serial Number’. Only reports which are to be corrected /revised/deleted should be retained and other reports may be deleted.
Yes. User can save the data using Save button in the tool bar. To retrieve the data in the utility, use the Open button from the tool bar
Select the saved XML file using the Open button from the tool bar.