GSTR for CA portal
How to Upload GSTR-1 JSON on the GST Portal and Fix Common Errors
Uploading a JSON file is the fastest way to fill GSTR-1 for clients with many invoices. You prepare the return offline – in a utility or a tool – and upload one file instead of typing hundreds of rows. Errors are reported row by row so you can fix and re-upload.
Since GSTR-3B now takes its outward liability from GSTR-1 (with only one chance to correct it through GSTR-1A), a clean GSTR-1 upload matters more than ever.
Before you upload
- Check that the GSTIN and return period inside the JSON match the return you are filing.
- Make sure invoice numbers are unique within the financial year and at most 16 characters.
- Confirm every B2B buyer GSTIN is valid and active.
- Review the HSN summary against the invoice tables.
Uploading the file
- Log in to the GST portal and open Returns Dashboard.
- Choose the financial year and period, then open GSTR-1 → Prepare offline.
- Under Upload, choose the JSON file and upload it.
- Wait for the status to change from "In progress" to "Processed" or "Processed with error".
- If there are errors, download the error report, correct the rows and upload again.
- Once processed, check the summary, then file with DSC or EVC.
Common errors and fixes
- Invalid recipient GSTIN – the buyer GSTIN is wrong or cancelled; correct it or move the invoice to B2C.
- Duplicate invoice – the invoice number already exists in the year; check for re-uploads and amendments.
- Place of supply mismatch – inter-state tax with an intra-state place of supply or the reverse.
- HSN validation – code not in the list or too few digits.
- Rate not allowed – a rate that does not exist for the table; check rounding in the source data.
Uploading in parts
Large clients can upload JSON more than once; new uploads add to or overwrite matching records. Keep a note of what each upload contained so nothing is counted twice.
After filing: GSTR-1A and GSTR-3B
If you find a mistake after filing GSTR-1 but before GSTR-3B, the client can correct it once through GSTR-1A for that period. The values then flow into GSTR-3B, where auto-filled outward liability can no longer be edited by hand.
Preparing the JSON
The GSTR for CA portal builds GSTR-1 JSON from marketplace reports and your B2B / B2C template, along with an Excel working to review first. Save the working to the client; the tracker marks the return as prepared, and you add the ARN when it is filed.
Frequently asked questions
Can I upload JSON for a QRMP client's IFF?
IFF has its own section; JSON for GSTR-1 tables is uploaded in the return that applies to the period.
Why does my upload say "Processed with error"?
Some rows failed validation. Download the error report from the same page, fix those rows and upload again.
Does re-uploading delete earlier data?
Matching records are replaced; others stay. Use "Reset" on the portal only if you want to start again.
Is the JSON from your tool accepted by the portal?
It follows the GSTR-1 offline JSON structure. Always review the processed summary on the portal before filing.