Understanding and Resolving Common GSTR-1 Errors

Created by Book Keeper Support, Modified on Fri, 12 Sep at 1:26 PM by Book Keeper Support

Before you file your GSTR-1 for the month, it's crucial to check for any uncertain transactions and fix them. These issues often appear at the bottom of the screen. Here’s a breakdown of the most common errors and how to resolve them.


Common GSTR-1 Errors and Solutions


1. Tax Account Mismatch

This error occurs when the default tax rate set for an account doesn't match the tax rate applied during voucher creation. To fix this, ensure that the tax rate used in the transaction is consistent with the one assigned to the account.

2. UQC Not Assigned

UQC, or Unit Quantity Code, is a mandatory field. This error means you haven't assigned a UQC to a unit of measure you've created. You need to go back and add the correct UQC to the unit of measure.

3. Zero Value Vouchers

GSTR-1 doesn't accept invoices with a value of zero. This error appears if you've created a voucher with no value. You must ensure all invoices have a positive value before filing.

4. Negative Quantity or Value in HSN Summary

This is a rare error that happens if you've created a sales return directly instead of linking it to a sales voucher. To avoid this, make sure all sales returns are properly linked to their original sales transactions.

5. Invalid Voucher Number Length

According to government regulations, an invoice number cannot be longer than 16 digits. If your voucher number exceeds this limit, you must shorten it to meet the requirement.

6. Decimal Place must be 2 Digits

This error indicates that a decimal value in your data has more than two digits. To fix this, you need to change your settings to enforce a two-digit decimal place.

Steps to correct the decimal place:

  • Go to Settings > General Settings > Decimal Place.
  • Select 2 digits.


Understanding and Resolving Taxable Value Mismatches in GSTR-1


A common issue businesses face is a mismatch between the taxable value reported in the B2B/B2C sections and the HSN summary. The key to fixing this is understanding the calculation logic and your settings.


Taxable Value Calculation Logic

The taxable value in your GSTR-1 sections should reconcile with the corresponding HSN summary tables. Here’s the formula:

  • For B2B (Business-to-Business) Transactions:
    1. The taxable value from your B2B invoices, minus any Credit/Debit Notes (CDNR) and plus any Nil-rated/Exempt items for B2B, should equal the taxable value in the HSN Summary (B2B).
    2. Formula: B2B - CDNR + Nil-rated Exempt(B2B) = HSN Summary (B2B)
  • For B2C (Business-to-Consumer) Transactions:
    1. The taxable value from your B2C invoices, minus any Unregistered Credit/Debit Notes (CDNUR) and plus any Nil-rated/Exempt items for B2C, should equal the taxable value in the HSN Summary (B2C).
    2. Formula: B2C - CDNUR + Nil-rated Exempt(B2C) = HSN Summary (B2C)



Handling GST @ 0% Items

The way items with a 0% GST rate are reported depends on the other items in the same invoice.

  1. Single Item Invoice: If an invoice contains only one item with a GST rate of 0%, the voucher's value will be reported in the Exempt Table of the GSTR-1 report.
  2. Multiple Item Invoice: If an invoice includes a mix of items, such as one item at 5% GST and another at 0% GST, the entire voucher will be reported in the B2B Table of the GSTR-1 report.




Important Settings to Enable

To ensure your Nil and Exempt item values are properly displayed and reported in the B2B and B2C sections, you must enable a specific setting.

Steps:

  • Go to Settings > GST India Settings.
  • Look for the option "Display Nil and Exempt item value in B2B and B2C" and enable it. 


Still you have any doubts, please connect us over our number: +91-9999176746 or even drop us a mail at Support@bookkeeperapp.net

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article