ZN ERP
Docs v9.13
xnservices.net

How to Run a GST Report

Generate GSTR-1 / 3B-ready outputs.

6 min read Updated Jun 2026   How-To

Purpose

Produce GSTR-1 (outward supplies) and GSTR-3B (summary) reports in formats ready for upload to the GST portal. This is a monthly (or quarterly, if you are on QRMP) routine — never wait until the last day, because reconciling 2B against your purchase register always throws up something to fix.

Before you begin

  • All outward and inward invoices for the period are entered and posted.
  • Day Closure done up to the last date of the return period.
  • GSTIN of your business and your suppliers / customers are accurate in their master records.
  • GSTR-2B downloaded from the portal for the period (for reconciliation against your purchase register).

Steps

  1. Start → Accounts & Finance → GST Reports → GSTR-1.
  2. Pick the return period (month or quarter, based on your registration).
  3. Click Run. The grid splits into B2B, B2C-Large, B2C-Small, CDNR, Export, etc.
  4. Spot-check totals against your sales register. Any mismatch usually means an invoice has the wrong GSTIN or wrong tax structure.
  5. Click Export → JSON for direct upload to the GST portal, or Export → Excel for offline review.
  6. For GSTR-3B, go to GST Reports → GSTR-3B. The summary populates from posted invoices. Export and use as a worksheet for portal entry.
  7. For reconciliation, open GSTR-2B Match, import the JSON downloaded from the portal, and review unmatched rows — chase the supplier or your data-entry team for any mismatch before filing 3B.

What success looks like

  • A GSTR-1 JSON file ready to upload to the portal; row counts match the GSTR-1 summary screen.
  • A GSTR-3B Excel file with the period's outward and inward summary, ready for portal entry.
  • The 2B match report shows zero unmatched rows (or a documented list of supplier follow-ups).

Troubleshooting

Portal upload fails with "Invalid GSTIN".
At least one invoice has a customer with a malformed or wrong GSTIN. Run the GSTIN Validation sub-report under GSTR-1 to find the offending invoice and fix the customer master.
GSTR-3B does not match GSTR-1 totals.
Usually one of: invoices entered after the 3B was computed, RCM entries missed, or a credit note dated wrongly. Re-run both and compare summary totals.
HSN-summary section is empty.
Items are missing HSN codes. Run the Items Missing HSN sub-report and update them in Item Master.

Tips

  • Do not modify exported JSON by hand — the portal validates strictly and a hand edit usually corrupts the file.
  • Reconcile GSTR-2B (auto-populated by the portal) against your purchase register before filing 3B — mismatches become input-credit losses.
  • Run GSTR-1 weekly during the month, not only on filing day — you catch tax-structure mistakes when they are still easy to fix.
  • Warning. If you amend an invoice after exporting JSON, re-export — uploading the stale file will mismatch with the portal's view.