Troubleshoot GST Setup and Compliance
Start with the exact GSTIN, location, document date, document number, compliance period and issue number. Preserve source evidence before changing a record.
Setup and invoice issues
Section titled “Setup and invoice issues”| Problem | Checks and supported remedy |
|---|---|
| GST registration is not available | A Business Owner checks Settings → Locations & GST for Active registration, effective dates and a valid GSTIN. Check the invoice date against those dates. |
| Location is not mapped | In GST registrations & location coverage, select Map location and add non-overlapping dated coverage. Check the unmapped-location notice. |
| Wrong CGST/SGST or IGST | Compare registration state with invoice Place of Supply. Matching states use CGST/SGST; different states use IGST. Correct a draft before saving; use the approved historical correction path for an issued invoice. |
| Customer GSTIN is missing or invalid | Enter Billing GSTIN on the invoice and check all 15 characters and checksum. The customer directory does not currently expose this tax field. Without it, the outward working record is B2C. |
| HSN/SAC or UQC is missing | Correct the active product, service or variant and retest. A GST invoice needs a numeric 4-, 6- or 8-digit code; products with HSN also need UQC. Turnover rules may require more digits. |
| Tax rate is wrong | Check the item GST % and business-wide Tax Mode. A 0% rate is not an exempt/nil/non-GST classification; do not guess a reporting treatment. |
| Invoice number is rejected | Leave it blank for automatic numbering. A manual value is unique within the registration, no more than 16 characters, uses letters/numbers///-, and ends in a number. |
Reports and period issues
Section titled “Reports and period issues”| Problem | Checks and supported remedy |
|---|---|
| Invoice is missing from a period | Match GST registration, dated location mapping, invoice date and period. Confirm the invoice is issued/finalized rather than draft or cancelled, then Sync GST data and Run validation. |
| Credit note is not reflected | Confirm the supported credit note was created against the paid invoice, belongs to the selected registration/period and is current, then sync and validate. |
| Totals differ from GST Reports | Match date, GSTIN and location filters. Check credit notes, payment-versus-document status, ITC decisions, purchase returns, standalone expense exclusion and whether the compliance snapshot is older than live data. |
| Filing period is incorrect or unavailable | Registration Filing frequency decides monthly versus QRMP. The UI creates only the current period and lists existing periods. Do not change frequency to manufacture a historical period; contact Support with the GSTIN and expected period. |
| Period cannot become Ready or Locked | Run synchronization and validation, resolve all blockers and generate a current snapshot. Mark ready needs Manage access; Lock period needs Lock access. |
| Period is locked but a source needs correction | A Lock-authorized user uses Reopen period with a specific reason. Correct the source, then repeat sync, validation, snapshot, ready and lock. Confirm statutory consequences first. |
Return and export issues
Section titled “Return and export issues”| Problem | Checks and supported remedy |
|---|---|
| GSTR-1 cannot be prepared | The period must be Locked with a current non-stale snapshot and no compliance blockers. The registration must be valid for the period. |
| GSTR-1 package cannot be generated | Resolve all GSTR-1 blockers and confirm the current preparation reconciles. Reopen and prepare a replacement if the source or registration changed. |
| GSTR-3B cannot be prepared | Confirm a current GSTR-1 and an approved authoritative GSTR-2B reconciliation exist for the same locked snapshot and period. |
| Validation issue remains after correction | Old preparation evidence does not change. Reopen, sync, validate, snapshot, mark ready, lock and prepare a replacement version. |
| Export download fails | Return to the current return panel and select download again. Authorized private links are short-lived. If it still fails, note the package name, time and error and contact Support. |
| GST Portal rejects the JSON | Keep the portal response. Correct operational source data, rebuild the controlled package and upload the replacement. Do not hand-edit JSON to bypass validation. |
Historical corrections
Section titled “Historical corrections”Issued invoices retain their tax snapshot; changing settings, mappings, customers or catalog items does not rewrite them. Use a supported credit note for an eligible full paid-invoice reversal. If the relevant return was already filed, ask your GST professional which amendment or adjustment process applies before reopening Yepsta evidence.
Last reviewed: