https://help.tallysolutions.com/docs/te9rel66/Tax_India/gst/faq-gst-reports-for-jnk-ladakh.htm

FAQ - GST Reports in Tally.ERP 9 for Jammu & Kashmir and Ladakh

This topic has a few FAQ on using GST reports in Tally.ERP 9 for companies located in Jammu & Kashmir and Ladakh.

1. How to change the tax rate using GST Rate setup?

2. I'm using Release 6.5.5. When I upload the JSON files of GSTR-1 generated from Tally.ERP 9 for any period until Dec 2019, I'm getting an error regarding invalid GSTIN. How to resolve this?

3. I'm using Release 6.5.5. I have updated the new GSTIN of Ladakh in the Company GST Details screen. While uploading JSON files of GSTR-1 and GSTR-3B generated from Tally.ERP 9, I'm getting the error regarding invalid GSTIN. How to resolve this?

4. Why are transactions recorded before 1-Jan-2020 by selecting the Place of Supply as Ladakh appearing as exceptions in GST reports?

1.

How to change the tax rate using GST Rate setup?

Refer to the topic on GST Rate Setup for details.

2.

I'm using Release 6.5.5. When I upload the JSON files of GSTR-1 generated from Tally.ERP 9 for any period until Dec 2019, I'm getting an error regarding invalid GSTIN. How to resolve this?

We recommend you to upgrade to Release 6.6 as we have taken care of this issue.

If you want to continue to use 6.5.5 for some more time, you can refer to the cause and workaround of the issue in the explanation given below:

Cause

This problem may occur due to the following reasons:

The specified GSTIN is blacklisted or incorrect.

The State defined for party ledger was changed from Jammu & Kashmir to Ladakh along with the GSTIN. As on 1-Jan-2020, the State code was updated from 01 (of Jammu & Kashmir) to 38 (of Ladakh).

Solution

The scenarios with the corresponding solutions are given below:

If the GSTIN is incorrect, get the correct GSTIN from your party. Enter it in the party ledger and transactions.

If the GSTIN is blacklisted, you can convert the transaction to a B2C transaction and then upload it to the GST portal. Check with your tax consultant before you proceed with recording of such transactions.

In the party ledger, if you have selected the State as Ladakh and entered the GSTIN starting with 38, follow the steps given below:

o Export the GSTR-1 return in Excel (Spreadsheet) or CSV format.

o In the MS Excel or CSV files, search for GSTINs starting with 38, and replace them with the old GSTINs.

o Import the MS Excel or CSV files into the GST Offline tool and generate the JSON file.

o Upload this JSON file to the GST portal.

3.

I'm using Release 6.5.5. I have updated the new GSTIN of Ladakh in the Company GST Details screen. While uploading JSON files of GSTR-1 and GSTR-3B generated from Tally.ERP 9, I'm getting an error regarding invalid GSTIN. How to resolve this?

We recommend you to upgrade to Release 6.6 as we have taken care of this issue.

If you want to continue to use 6.5.5 for some more time, you can refer to the cause and workaround of the issue in the explanation given below:

Cause

This problem occurs when you had updated new GSTINs (applicable from 1-Jan-2020) in the Company GST Details screen.

The new GSTIN of the company will appear in JSON files of GSTR-1 and GSTR-3B generated till December 2019.

Solution

We recommend that you follow the steps given below:

Export the GSTR-1 and GSTR-3B returns in Excel (Spreadsheet) or CSV format.

Import the MS Excel or CSV files into the GST Offline tool and generate the JSON file.

Upload this JSON file to the GST portal.

4.

Why are transactions recorded before 1-Jan-2020 by selecting the Place of Supply as Ladakh appearing as exceptions in GST reports?

You might be aware that in Ladakh, GST was made applicable on 1-Jan-2020 and new GSTINs were issued to dealers on the same day. Hence, for the purpose of GST, the State and Place of supply should not be selected as Ladakh in transactions made until 31-Dec-2019. Hence, if the vouchers recorded before 01-Jan-2020 have the State and Place of Supply as Ladakh , the same will appear as exception. We recommend you to select the relevant State and Place of Supply for party ledgers selected in all such transactions.