The page has list of FAQs on transition to new UT Dadra & Nagar Haveli and Daman & Diu.
Generic
1. Why and when are the union territories Dadra & Nagar Haveli and Daman & Diu merged?
2. What will be the name and state code of new UT? What will be the short form?
3. Will there be any change in existing registration of Daman & Diu.
4. Does Daman & Diu business have to manually opt for re-registration?
5. Will there be any change in existing GST registration for Dadra & Nagar Haveli?
6. As per the trade circular will the new UT name and GSTIN be made effective from 01-Aug-2020?
Master
Transactions
2. If GSTIN is changed in party master what will happen to the transaction recorded already?
Invoicing in Release 6.6.3
Return Filing in Release 6.6.3
Others
5. What will be the states names to be captured for e-Way bill?
6. Why will the Annual computation header part displays current GSTIN/UIN always?
10. What will happen if a company is created in Release 6.6.3 with state Dadra & Nagar Haveli and Daman & Diu, books beginning date after 01-July-2020 and GST applicable from date is before 01-Jul-2020?
The proposal to merge UT was tabled to reduce the duplication of services and the cost of administration, in this act the Government of India (GoI) proposed merging of two Union Territories into a single Union Territory(UT) in July 2019. The existing two UT's i.e Daman & Diu (DD) and Dadra & Nagar Haveli (DNH) will be merged in to single UT called Dadra & Nagar Haveli and Daman & Diu (DNHDD .
The Merger Act 2019, was passed in both the houses (Lok Sabha & Rajya Sabha) of the Parliament on 9th December 2019. This announcement was made by President of India on 24-Jan-2020 and it has come into force from 26-Jan-2020.
The name of new UT is Dadra & Nagar Haveli and Daman & Diu and state code will be 26 . The short form will be DNHDD .
Yes, there will be a change in existing GST registration. The current Daman & Diu state code is 25, and post merge, state code and new GSTIN will be issued by GSTN.
No, the GSTIN registration numbers of Daman & Diu would be automatically migrated at the backend by the GSTN department.
As per notification No. 10/2020 Central Tax dated - 21-March-2020, there will not be any change in existing GST registration of Dadra & Nagar Haveli and state code of 26 will be continued for new UT Dadra & Nagar Haveli and Daman & Diu.
The new UT Dadra & Nagar Haveli and Daman & Diu has come into existence from 26-Jan-2020 as per the merger act. However, the New State Code 26 for Dadra & Nagar Haveli and Daman & Diu will be applicable from 1st August 2020 as per the trade circular (issued on 13-Jul-2020) and therefore new GSTIN will be applicable from 1st August 2020.
After upgrading to Release 6.6.3, the state details are updated automatically in company and party master. It will display State as ' Dadra & Nagar Haveli and Daman & Diu and State (before reorganisation) as Daman & Diu or Dadra & Nagar Haveli respectively.
After upgrading to Release 6.6.3, it will automatically captures the GSTINs starting with 25 in both GSTIN/UIN and GSTIN/UIN( (before reorganisation) fields. When you get new GSTNs, to to F11: Features > F3 and in the Company GST Registration details screen, specify in the GSTIN/UIN field.
After upgrading to Release 6.6.3, the GSTIN/UIN will not be copied automatically. It will be captured only in GSTIN/UIN field and GSTIN/UIN( (before reorganisation) field left empty.
Currently, we are not migrating Transporter ID. If the party state is selected as Daman & Diu with Transporter ID starting with 25 in Release 6.6.2, the same ID will be available after migrating to Release 6.6.3.
In this case, user has to manually change the GSTIN registration starting from 25 to 26 in master and use the same in e-Way bill. OR
User can specify the GSTIN/UIN in the e-way bill details screen, which will be considered for the invoice.
Company Creation/Alteration
Existing users : In case the state is selected as Daman & Diu or Dadra & Nagar Haveli in release 6.6.2 then post upgrading to Release 6.6.3, the State field will appear as Dadra & Nagar Haveli and Daman & Diu and the State (before reorganisation) will be pre-filled as Daman & Diu or Dadra & Nagar Haveli .
New Users: In Release 6.6.3, while creating new company if the state is selected as Dadra & Nagar Haveli and Daman & Diu then by default the field State (before reorganisation) will appear with following drop down.
o Daman & Diu
o Dadra & Nagar Haveli
o Not applicable
You have to select applicable State details and save.
The prior state field will be available to support those who want to buy Tally.ERP 9 and maintain books of accounts after 01-Jul-2020 by specifying books beginning date as 01-Apr-2020. Also, due to this pandemic situation, after 01-Jul-2020, if you want to maintain previous year books in Tally.ERP 9.
The transactions which are made in Release 6.6.2 and updated to Release 6.6.3, will have earlier information as is.
1 If the company is created before 01-Jul-2020 with state Daman & Diu or Dadra & Nagar Haveli and later the state is changed to Dadra and Nagar Haveli and Daman and Diu, then:
2 If any backdated transaction is made prior to 01-Jul-2020, the state name captured is Daman & Diu or Dadra and Nagar Haveli .
3 In the transactions made on or after 01-Jul-2020, the state name captured is Dadra & Nagar Haveli and Daman & Diu .
4 Party ledger is created with state as Daman & Diu or Dadra and Nagar Haveli and later changed to Dadra & Nagar Haveli and Daman & Diu , then:
5 If any backdated transaction is made prior to 01-Jul-2020, the state name captured is Daman & Diu or Dadra and Nagar Haveli .
6 In the transactions made on or after 01-Jul-2020, the state name captured is Dadra and Nagar Haveli and Daman and Diu .
The above points are applicable for all the statutory and non-statutory purposes.
The GSTIN saved in transaction Party Details (supplementary details) will not be refreshed unless user explicitly presses space bar in Party Details screen and empties the existing GSTIN.
All transactions passed from 1st August 2020 onwards will have old GSTIN numbers and once again those invoices have to be reissued with new GST registration number else this may have impact on ITC claim.
If you want to print Dadra & Nagar Haveli and Daman & Diu name in transactions recorded prior to 01-Jul-2020, export invoice to MS Excel and change the name. Similarly, if you want to print Daman & Diu or Dadra & Nagar Haveli even on or after 01-Jul-2020, you have to export invoice to MS Excel and change the company and party state name and code manually.
Tally.ERP 9 supports Dadra & Nagar Haveli and Daman & Diu changes from 01-Jul-2020, which were made based on implementation dates released earlier. When you record transactions in the month of July, the GSTIN specified in the current GSTIN/UIN field of the company or party master will be applied and printed. To print invoice with old GSTIN, you can export invoice in excel format and modify the GSTIN from 26 to 25 then print.
Whenever you get the new GSTIN number from the department, update the same in GSTIN/UIN field in Company GST Details screen (F11-> F3) and Party master.
As Dadra & Nagar Haveli and Daman & Diu GSTIN change is implemented from 1st August 2020, you can file two separate returns for each GSTIN/UIN:
For the financial year 2020-21, two Annual returns has to be generated as below:
01-Apr-2020 to 30-Jun-2020 with old GSTIN
01-Jul-2020 to 31-Mar-2021 with new GSTIN.
Based on the government directives (2 annual returns or one return with new GSTIN) you are expected to generate using Tally.ERP 9 or consolidate the values outside Tally.ERP 9 and file Annual Returns.
The new UT Dadra & Nagar Haveli and Daman & Diu implementation date as per Tally.ERP 9 will be 1st Jul 2020. Hence, user can load GSTR-1 returns for the proper quarter.
If the new GSTIN implementation date is from 1st Aug 2020, then you can follow the below process:
Method 1 : Need to file two separate returns for the periods,
01-Jul-2020 to 31-Jul-2020
01-Aug-2020 to 30-Sep-2020
You can export return in excel or CSV formats. In GSTR-1 offline tool give respective GSTIN/UIN and import the file to generate JSON file. Upload the generated JSON file in GSTN portal to file the returns. OR
Method 2 : As stated in method 1, export the returns for respective period in JSON format from Tally.ERP 9 and upload the JSON in GSTN portal.
As of now, there is no clarity by the NSDL department on the new FVU tool changes regarding new UT name Dadra & Nagar Haveli and Daman & Diu for TDS, TCS and Payroll returns. Hence, we will export the returns with states as below.
For the returns prior to 01-Jul-2020, old state codes will be sent.
The state code for DADRA & NAGAR HAVELI will be 07.
The state code for DAMAN & DIU will be 08.
For the returns after 01-Jul-2020, the state code for Dadra & Nagar Haveli and Daman & Diu should be sent as 99.
If department comes up with a code in the future, then we need to analyse and re-look on this functionality.
Until GSTN comes up with new Place of supply for new UT name Dadra & Nagar Haveli and Daman & Diu, as per the current understanding it should export Place of Supply as 26-Dadra & Nagar Haveli.
Transactions accepted as is in 6.6.2 or earlier releases till 30-Jun-2020 are retained with accepted as is status in 6.6.3.
However, transactions accepted as is in 6.6.2 or earlier releases on or after 01-Jul-2020 with UT's that are not valid any more ( Daman & Diu and Dadra and Nagar Haveli ) are treated as exception under Vouchers with invalid State and Place of Supply .
Whenever the GST returns are exported from Tally.ERP 9, it will consider the GSTIN specified in the current GSTIN/UIN field Company GST Details screen (F11 > F3).
Because once department issues new GSTIN/UN for Daman & Diu dealers, the old GSTIN will be deactivated. Post this you have to use new GSTIN/UIN number for all statutory purposes.
If the transactions are made with state Dadra & Nagar Haveli and Daman & Diu before 01-Jul-2020 and transactions made on or after 01-Jul-2020 with UT's no more valid ( Daman & Diu and Dadra & Nagar Haveli ) prior to 6.6.3, they will be treated as exception under Vouchers with invalid State and Place of Supply in Release 6.6.3.
Either user can temporarily update old GSTIN in current GSTIN/UIN field in Company GST Details screen (F11 > F3) and generate returns and then change to new number.
OR
Generate JSON with new GSTIN number, edit the JSON to update old GSTIN and upload the same in GSTN portal.
OR
Export the returns into Excel or CSV format where company GSTIN is not exported. Open the GST offline tool and provide Old GSTIN. Import the files into offline tool to generate the JSON file. Upload the same in GSTN portal.
When a purchase was done in April/May (with old state/GSTIN), and if that invoice is made after 1-Jul-2020 then as per voucher date reference system will pre-fill new state (Dadra & Nagar Haveli and Daman & Diu ) and GSTIN/UIN number. There will not be an option to alter the invoice to choose the old state (Daman & Diu or Dadra & Nagar Haveli). Hence, we recommend customer to record purchases prior to intervening period in that respective period itself.
There is a change in Annual Computation Report opening as below:
If the books beginning from date is 1st April 2020, then by default report will open for the period 1st April 2020 to 30th June 2020.
When the books beginning from date is 1st April 2019, then by default report will load for the period 1st April 2019 to 31st March 2020.
In Current Release 6.x, when the transaction is made with flag Increase of Input Tax credit and additional details other than Transfer of ITC, the following will be the entry and amount considered for Taxable Value .
|
Entry |
GSTR-3B (All other ITC drill down values) |
|
Dr. Union Territory Tax Cr. Expenses |
Display the taxable value as empty. |
|
Dr. Central Tax Cr. Expenses |
Display the taxable value given for Central Tax ledger under Taxable Amount column. |
|
Dr. Central Tax Dr. Union Territory Tax Cr. Expenses |
Display the taxable value given for Central Tax ledger under Taxable Amount column. |
|
Dr. Integrated Tax Dr. Union Territory Tax Dr. Central Tax Cr. Expenses |
Display the taxable value given for Interstate Tax and Central Tax ledgers under Taxable Amount column. |
In case of Ladakh- when statutory journal voucher is recorded with Transfer of ITC flag the only the UT Tax ledger taxable value and tax amount will be shown in GSTR-3B drill down report. This is because of tax type change i.e., SGST is changed as UT Tax.
In case of Dadra & Nagar Haveli and Daman & Diu,
1. There is no change in tax types and it will be same as other UT's.
2. As per existing Rel 6.x behavior, CGST/CGST + IGST duty ledgers taxable value will be considered for capturing taxable value. Therefore, same will be considered for Dadra & Nagar Haveli and Daman & Diu.
For Example : When stat JV is recorded with flag Reversal of ITC and Others and only UT Tax duty ledger is selected, then it will display taxable value as empty and tax amount as per transaction.
When stat JV is recorded with flag Reversal of ITC and Others and only with CGST ledger, then it will show both taxable value and tax amount.
Until NIC department comes up with the new UT name Dadra & Nagar Haveli and Daman & Diu changes in the e-Way bill offline tool, the current understanding is to export state as DADRA AND NAGAR HAVELI.
When user gets new GSTINs then old GSTIN number will be no more valid. Therefore, in Annual computation report the current GSTIN/UIN mentioned in Company F11 > F3 will be shown.
Until the NIC department comes up with changes considering new UT Dadra & Nagar Haveli and Daman & Diu,
7 Current understanding is that state name for Dadra & Nagar Haveli and Daman & Diu should be exported as DADRA AND NAGAR HAVELI.
8 Party GSTINs starting with 25 and the state code for DADRA AND NAGAR HAVELI is 26.
As the state codes of To_GSTIN is not matching with the Bill To_State and Ship To_State state codes. Therefore, the e-Way bill template validation and JSON generation fails.
Whenever you get new GSTIN/UIN, update the same in current GSTIN/UIN field of master and transactions. Alternatively, you can change the state manually to Daman & Diu to generate e-Way bill.
For e-Way bill, all the information available in the transaction will be taken. However, when e-Way bill is generated in JSON format, therefore UserGSTIN field value is picked from current GSTIN/UIN field of Company GST Details screen (F11 > F3).
Because once department issues new GSTIN/UN for Daman & Diu users, the old number will be deactivated. Post this you have to use new GSTIN/UIN number for all statutory purposes.
When e-Way bill is exported in excel format, as per existing behavior You have to mention first line information manually.
The auto migration of balance ITC from old to new GSTINs books of account will be made at the backend by the GSTN department.
When you get the new registration from department for Dadra & Nagar Haveli and Daman & Diu , the balance ITC needs to be reversed in old GSTN registration. If Net ITC available is negative (i.e if ITC reversed is more than available ITC) and you try to upload the same in portal, the upload will fail and a message Negative values are not allowed is displayed.
In this case, the State (before reorganisation) and GSTIN/UIN (before reorganisation) fields will not be available in company and party master.
We have changed the way DPI settings are handled in the product. Earlier, it was left to Windows OS to scale (zoom) the text displayed in Tally.ERP 9 based on the DPI setting. For DPI settings other than 100%, all the text in the product used to be blurred and difficult to read.
From Tally.ERP 9 Release 6.6.2 onwards we have taken the charge of scaling the text used in the product internally, which will result in the text being rendered sharp and easy to read. You will get much enhanced experience in our next release TallyPrime .
However, due to this if you feel that the text is compressed, it could be due to Text Size applied in your Windows Display Settings.
We request you to follow the steps given below:
Right click on your Desktop> Display Settings> Under Scale and Layout, there is an option to Change the size of text, apps and other items .
Here ensure that the setting is 125% or lower. Apply these changes and now check the fonts. The compression would have been taken care of.
You have to maintain two copies of your company data, one in your existing version of Tally.ERP 9 and other in Tally.ERP 9 Release 6.6.3.
Case 1 : In case you have already replaced your existing release of Tally.ERP 9 with Release 6.6.3 by upgrading, you have to retain the upgraded version and install the version also. To do so,
1 Rename the Tally icon on your desktop as Tally.EPR9 Rel 6.6.3.
2 Download the earlier version used by you from Tally website.
3 Install it in a different folder and name the Tally.ERP9 icon on desktop with the respective release number.
4 Use the earlier release until 31st July 2020. From 1st August 2020 onwards, you can start using Tally.ERP9 Release 6.6.3 with your latest data from the earlier release being using till 31-Jul.
Case 2 : If you have downloaded Release 6.6.3 and installed in different folder and using both versions simultaneously.
1 Open the earlier version of Tally from its installation folder.
2 Use the earlier release until 31st July 2020. From 1st August 2020 onwards, you can start using Tally.ERP9 Release 6.6.3 with your latest data from the earlier release being using till 31-Jul.
This eliminate the confusion caused when transactions are recorded by selecting state as Dadra & Nagar Haveli and Daman & Diu before 01-Jul-2020 as they will be treated as exception under Vouchers with invalid State and Place of Supply in Release 6.6.3. Similarly,transactions made on or after 01-Jul-2020 with UT's no more valid (Daman & Diu and Dadra & Nagar Haveli ) using earlier releases of Tally.ERP 9 will be treated as exceptions.
