When you prepare GSTR-1 in software, or download it from the GST portal, you often get a JSON file. JSON is a plain-text format that computers read easily. People do not. A small return can be one very long line of brackets and codes.
This guide shows what is inside the file, how to open it, and what to check before you upload it. To see your own file as tables, use our GSTR-1 JSON Viewer. It reads the file in your browser and never uploads it.
Where a GSTR-1 JSON comes from
You usually get one in one of these ways:
- Your accounting or billing software makes it for you to upload.
- A converter, such as our Amazon MTR to GSTR-1 JSON tool, makes it from a marketplace report.
- The GST portal gives it to you. In GSTR-1, choose Prepare Offline → Download, then generate the file. It can take a few minutes. The portal gives you a .zip file. Open it to get the .json file inside.
Why you should open it
- Before you upload: to check that the totals match your books.
- After you file: to see exactly what was reported, invoice by invoice.
- Before GSTR-3B: GSTR-3B takes your sales tax from GSTR-1. A mistake in GSTR-1 flows into GSTR-3B.
- When a buyer asks: to check that their invoice and GSTIN were reported, so they get the input tax credit.
Three ways to open it
| Way | Good | Not so good |
|---|---|---|
| GST Returns Offline Tool | Official. Can also change the return. | Must be installed on a Windows computer. |
| A text editor or browser | Nothing to install. | Very hard to read. Easy to break the file by mistake. |
| Our GSTR-1 JSON Viewer | Works on any computer or phone. Shows plain tables and totals. Excel download. | Only reads the file. It cannot change it. |
If you only need to read or check the file, the viewer is the quickest. If you need to change the return, use the Offline Tool or the GST portal.
What the parts of the file mean
A GSTR-1 JSON has a few keys at the top, then one section for each table of the form.
The top of the file
| Key | Meaning | Example |
|---|---|---|
gstin | Your GSTIN | 27AAPFU0939F1ZV |
fp | Return period, as MMYYYY | 102026 is October 2026 |
version, hash | Used by the portal. You can ignore them. | GST3.1.2 |
The sections
| Key | GSTR-1 table | What it holds |
|---|---|---|
b2b | Table 4 | Invoices to buyers with a GSTIN |
b2cl | Table 5 | Invoices to another state above ₹1 lakh, buyer without a GSTIN |
exp | Table 6A | Exports |
b2cs | Table 7 | All other sales to buyers without a GSTIN, added up by state and rate |
nil | Table 8 | Nil rated, exempt and non-GST sales |
b2ba, b2cla, cdnra | Table 9A, 9C | Changes to invoices and notes of earlier months |
cdnr, cdnur | Table 9B | Credit and debit notes, to registered and unregistered buyers |
b2csa | Table 10 | Changes to Table 7 of earlier months |
at, txpd | Table 11 | Advances received, and advances adjusted |
hsn | Table 12 | HSN summary, with a B2B part (hsn_b2b) and a B2C part (hsn_b2c) |
doc_issue | Table 13 | Invoice and note numbers you used, and how many were cancelled |
supeco | Table 14 | Sales through e-commerce operators like Amazon |
A file only has the sections you used. If you had no exports, there is no exp.
The amounts
The same short names are used everywhere in the file:
| Key | Meaning |
|---|---|
ctin | Buyer's GSTIN |
inum, idt, val | Invoice number, date, and full invoice value |
pos | Place of supply, as a state code: 27 is Maharashtra, 29 is Karnataka |
rt | GST rate |
txval | Taxable value (before GST) |
iamt, camt, samt, csamt | IGST, CGST, SGST, and cess |
A worked example
Here is one B2B invoice, as it looks in the file:
"b2b": [{
"ctin": "29AAPFU0939F1ZR",
"inv": [{
"inum": "INV-101", "idt": "05-10-2026", "val": 59000, "pos": "29",
"itms": [{ "num": 1, "itm_det": { "rt": 18, "txval": 50000, "iamt": 9000 } }]
}]
}]
Read it like this:
- You sold to the buyer with GSTIN 29AAPFU0939F1ZR, in Karnataka (state code 29).
- Invoice INV-101, dated 5 October 2026, for ₹59,000 in total.
- The taxable value is ₹50,000 at 18%. Since the buyer is in another state, the tax is IGST ₹9,000.
The GSTR-1 JSON Viewer shows this as one row in the Table 4 list. It adds up all tables, takes credit notes away, and shows the total tax.
What to check before you upload
- GSTIN: it must be yours, in capital letters. The portal accepts the file only for the GSTIN you log in with.
- Return period:
fpmust be the month you are filing. - Totals: compare the taxable value and tax of each table with your sales register.
- Credit notes: check they are in Table 9B, and are not counted as sales.
- HSN summary: the Table 12 total should be close to the total of your sales tables.
- Table 14: if you sell on Amazon or Flipkart, check it against the TCS amounts the operator reports.
- Table 13: check the invoice numbers and the cancelled count.
If you change the JSON by hand, one missing comma or bracket breaks the whole file. Open it in the viewer again after the change. If the file is broken, it tells you.
Summary
- A GSTR-1 JSON is your return as a computer file. Each section is one table of the form.
b2bis Table 4,b2csis Table 7,cdnris Table 9B,hsnis Table 12, andsupecois Table 14.txvalis taxable value, andiamt,camtandsamtare IGST, CGST and SGST.- Open it with the Offline Tool to change it, or with the GSTR-1 JSON Viewer to read it and get it in Excel.
- Before you upload, check the GSTIN, the period, and the totals.
Sources
- Form GSTR-1 and Section 37 of the CGST Act, 2017
- GST portal and the GST Returns Offline Tool
- GSTR-1 JSON field names as used by the portal's offline format and open-source GST software
We wrote this from the GSTR-1 form and the JSON layout used by the portal, as we understood them in November 2026. The portal does not publish a full guide to every JSON key, and it can change the layout. Please check the latest on the GST portal and ask your CA for your case. This is not legal advice.