In some cases, transactions accidentally appear in the Marked for Deletion on Portal section of GSTR-1 due to some changes in the transaction details, as explained below. You can easily address such cases by making the suggested updates.

• Change in company GSTIN
• Change in party
• Change in party GSTIN/UIN
• Change in GST amount
• Change in voucher number
• Deletion of transaction from books

This exception occurs when the Voucher No. or Document No. is duplicate. In case of duplicate voucher numbers, drill down to the voucher and update the voucher number. In case of duplicate document numbers, you can update the voucher numbering from the respective voucher type master. Refer to Duplicate Voucher No./Document No. for the detailed procedure.

This error may appear while uploading the JSON file to the GST portal. Below are the possible solutions.

1. Copy the data as a backup.
2. Download and install the latest release of TallyPrime.
3. Open the company data in TallyPrime.
   1. Ensure all Incomplete/Mismatch in information in GSTR-1 are resolved, and all masters GSTIN including HSN details are validated.
   2. In case, e-Invoice is applicable to your business, you need to open the GSTR-1 report in CSV format, and upload the files created for sections other than B2B, and exports. For more information, refer to the Use the GST Offline Tool.

If the error appears again, and the Status is Processed with Error, then error report is generated in the GST portal.

To know the cause, under the Error Report column click Generate error report.

1. Download the error report from the GST portal.
   1. On GST portal > Downloads > Offline Tools > Returns Offline Tool.
   2. Click Download to download the error report.

2. Open the downloaded error report file. Refer to the Use the GST Offline Tool.
   The errors are listed for transactions. While filing GSTR-1, the common errors and solutions are mentioned on the table below:

   Error	Cause & Solution
   Invalid UQC	Cause: UQC for HSN is blank or not valid or created New UQC where GSTIN accepts values only from the recommended list.
   	Solution: Gateway of Tally> Alter > Unit. Press Enter to select the Unit Quantity Code (UQC) from the list of Units. On Unit Quantity Code (UQC) field, select the UQC from List of UQCs. The list is published as per the GSTIN updates. If a new UQC is selected from the list, press Ctrl+A to save and try to upload on GSTR-1.
   Inactive GSTIN	Cause: According to GST norms, if your GST Registration is cancelled, your GSTIN is no longer valid.
   	Solution: Make a note of the inactive GSTINs and follow the steps below to convert those transactions (where inactive GSTIN was used) from B2B to B2C sales. Press Alt+G > search GSTR-1. Press Enter on B2B Invoices 4A, 4B, 4C, 6B, 6C. Select the inactive GSTIN and change the nature of transactions as Sales to Consumer – Taxable. Note: In case you need to move multiple transactions to B2C, then alter the party master’s Registration Type as Consumer and remove the GSTIN to avoid the same error for upcoming Transactions billed for the customer.
   State code is not available. or, The place of supply and state code of the supplier should be different for Inter State Supply.	Cause: New state created by the users instead of selecting state from List of States Data is imported from other software Due to spelling errors while creating a new state Letters of the state is created with upper case The state code starting and Place of supply are different
   	Solution: TallyPrime has listed all the states and their state code as per the GSTN Master sheet. Recommend selecting the state from List of states, so that the respective state code can be assigned accordingly while exporting returns. In case the place of supply is modified during voucher entry, ensure the place of supply is the same as the supplier state when IGST is collected, or the place of supply code is the same as the supplier state when CGST / SGST is collected. For example, when the place of supply is Karnataka, GSTIN / State Code should be always starting with 29.
   HSN does not belong to the service/Goods or, Invalid HSN/SAC	Cause: Type of supply is wrongly configured in inventory or accounting Master.
   	Solution: In case of Services, HSN/SAC should begin with the number 99, which identifies the code as a SAC and not an HSN. Click here to know the correct HSN details. Make a Note of HSN/ SAC for reference. Gateway of Tally > Alter > select the Ledger, and press Enter. Under Statutory Details, ensure the Type of Supply is selected as Goods, and HSN/SAC starting with other than 99, and if the Type of Supply is Services, the HSN/SAC is starting from 99. In case of incorrect HSN code, validate the details from HSN code and enter the appropriate HSN/ SAC.
   Voucher number not maintained for invoices. or, Invoice number does not exist.	Cause: An invoice number is must for any GST transactions not exceeding 16 characters, containing alphanumeric with/without special characters including “-“or “/” for any financial year. Generally, this is found in Journal or Receipt vouchers wherein GST is levied and doesn’t have voucher number series.
   	Solution: Check the voucher type and ensure that all Invoices with GST have Invoice Numbering set. In GSTR-1, select Document Summary and check the serial number for any voucher type. If it is blank, provide the voucher number in the relevant vouchers and try to upload with a new JSON.
   IGST is mandatory for interstate supply and CGST & SGST should not be present.	Cause: The nature of transactions is overridden. The place of supply is changed during the entry. In case the transaction supplies covered under section 7 of IGST Act, SGST and CGST, and IGST are counted as wrong for the interstate supply. Wherein IGST to be charged although supplier and buyer in the same state in case of courier services.
   	Solution: Follow the steps below to resolve the error: Make a note of the invoice number displayed in error report. Check the place of supply and the State of the Buyer to whom goods are billed. Select the appropriate nature of transaction if the nature of transaction is overridden. In the Statutory Details screen, set the option Supplies under section 7 of IGST Act to Yes. For more information, click here.
   Date is invalid, the invoice date cannot be before the registration date.	Cause: The invoice date is earlier than the date buyer obtained for GST registration or GSTIN.
   	Solution: Before the date of GST registration, all such transactions should be B2C sales. After confirming the date from the customer, or check the effective date of registration from Goods & Services Tax (GST) | Services, create a new party with GSTIN Number and then start issuing GST invoice.
   Please enter some value in IGST tax amount field / Export Sales Transactions.	Cause: Sales invoice for a foreign party with a Nil Rated item, wherein by default the nature of the transaction will Export Nil Rated, and GST Payment type should capture as WOPAY instead of picking WPAY.
   	Solution: From the error report, note the transaction. Open JSON file through Notepad and search for exp_typ:WPAY. Update WPAY to WOPAY. Save the file and re-upload the JSON file.
   Error in JSON structure validation.	Cause: The GSTN portal cannot recognize the uploaded JSON file, or there are structural errors in the uploaded JSON file.
   	Solution: Follow the steps below to resolve the error: Ensure that the GSTIN is specified on the JSON file. If the same is blank or not available, Gateway of Tally > press F11 > set Enable Goods and Services Tax (GST) as Yes. Check whether the Company GSTIN is provided, if not provide the same and re-export the JSON file. Secondly, ensure that the uploaded JSON file is the latest and has been exported from the latest TallyPrime Release.
   Errors encountered while uploading the file.	Cause: Due to multiple users accessing the GSTN portal to upload the file.
   	Solution: Try to upload the JSON file after some time or login to the GST portal from another browser and retry.

This exception occurs when certain GST Registration Details are missing or invalid for your party. 

You can resolve this exception using any one of the following:

• Update transactions party-wise
• Update transactions using Multi Alter
• Update transactions one by one

This exception occurs when the Tax Ledger is missing in the transaction. To resolve this exception, you can update the relevant tax ledgers in the transactions. Refer to Tax Ledger is not specified for the detailed procedure.

This exception occurs when the Taxability Type is missing or invalid in the GST details for stock items. You can resolve this exception using any one of the following:

• Update transactions Ledger-wise or Stock Item-wise
• Update transactions one by one

This exception occurs when the HSN/SAC is missing or invalid in the GST details for stock items.

You can resolve this exception using any one of the following:

• Update transactions Ledger-wise or Stock Item-wise
• Update transactions one by one

This exception occurs when the Tax Rate is missing in the GST details for stock items.

You can resolve this exception using any one of the following:

• Update transactions Ledger-wise or Stock Item-wise
• Update transactions one by one

This exception occurs when an incorrect Tax Ledger is selected in the transaction. You can resolve this exception by updating the transaction with the correct tax ledger. To learn more, refer to Incorrect Tax Ledger is selected for a detailed resolution.

The duplicate IRN error occurs when an IRN for an e-invoice has already been generated and canceled, and then reused for another voucher. It also appears while creating a new voucher using the same voucher number as the canceled e-invoice.

Say, for voucher number 1, you generated an e-invoice and canceled it later. If you are now generating an e-invoice for another voucher with the same voucher number, you will be prompted with a duplicate IRN error.

In this case, record the new voucher with a different voucher number. Also, remove the IRN from the e-invoice details and then generate the e-Invoice using the new voucher.

• If the IRN/QR code does not exist for the said invoice, you can use “Get IRN” instead of re-generating. This can be done within 72 hours of IRN generation.
• In case of auto-numbering, it is recommended not to delete the voucher. But in case you have deleted the voucher, insert the same voucher and select ‘Get IRN’. If more than 72 hours have passed, you will need to issue a credit note for the transaction.

You can easily mark an e-Invoice for cancellation from the e-Invoice – Voucher Register and then send the e-Invoice for cancellation from the Exchange menu. Refer to Cancel IRN/e-Invoice for the detailed procedure.

To enjoy the benefits of e-Way Bill in TallyPrime, you have to enable the e-Way Bill facility in your company features under the GST details. Once configured, you can easily generate an e-Way Bill while saving your invoice. Refer to Enable e-Way Bill in TallyPrime and Generate e-Way Bill for the detailed procedures.

If you’re on TallyPrime Release 3.0 or later, you can access the portal directly from the product to calculate the distance.

1. During voucher creation, set Provide e-Way Bill details to Yes.
   The e-Way Bill Details screen appears.
2. Press Alt+L (Calculate Distance on Portal).

You will be redirected to the portal on which you can calculate the distance between the pincodes.

However, if you are using TallyPrime Release 2.1 or earlier, then you can open the following link in a browser and calculate the distance between the pincodes:

https://ewaybillgst.gov.in/Others/P2PDistance.aspx

The facility of generating e-Way Bills on saving a voucher is provided for Sales Invoice and Delivery Note so that you can conveniently generate an e-Way Bill at the time of voucher creation. For other voucher types, including Credit and Debit Notes, Sales-POS, Journal Voucher, Receipt Note, and others, you can use the Send for e-Way Bill option under Exchange, which is on the top menu. The option enables you to upload multiple transactions for e-Way Bill activities.

This error occurs in the following scenarios,

• a foreign party is selected in both the Bill to and Ship to sections of the Party Details or Additional Details screen
• you may have specified the Pincode as 999999 and the State as Other Territory in the Ship to section
• you may have skipped the necessary Ship to details.

You can easily fix this error by updating the necessary details in the recorded transaction’s Party Details or Additional Details screen. Refer to Error description: Ship to details are mandatory for export transactions to generate EWB for the detailed procedure.