GSTR-1 save draft — return will not file

Every B2B invoice from the week is in. You clicked Save until the page showed a friendly success. The helper packed the invoice files. You switched off the second monitor. Next morning a buyer says your invoice is not in their GSTR-2B. You log in. GSTR-1 status is still not filed. Draft. Saved. Not filed. The File Return button was never the same as Save.

This happens on the night the session dies while you are in Table 12. You saved invoices. You did not generate the summary. You did not file. Or you filed in your head because the Excel import said OK. The GST portal does not file in your head.

Sometimes File is visible but dead. Summary of invoices does not match the details you entered. B2B count on the tile is 14. The table has 13. One invoice saved with a GSTIN error and fell out. Or B2C large and B2C small are mixed. Or HSN in Table 12 does not add up to the supply tables. The portal wants the story to be one story.

JSON upload nights are worse. Offline utility creates a file. You upload. Error list is long. You fix two rows, save draft online, upload again, and now two drafts fight. The return will not file until the live GSTR-1 is consistent.

What the draft is doing to the shop

A draft GSTR-1 does not push invoices to the buyer’s 2B. Your customer’s credit is delayed. They call. You think they are impatient. They are looking at a portal that does not show your GSTIN for that invoice.

Your own GSTR-3B later should broadly talk to GSTR-1. If 1 stays draft and you still file 3B from a notebook, you build a mismatch for a future notice. Saved is a parking bay. Filed is the road.

If the due date is close, a draft also means late fee risk once the clock passes. Check this month’s official date on Returns Dashboard. Do not use a printed calendar from last year.

Session timeout after a long invoice punch is the shop-floor version of this article. You return from tea. Login expired. You think Save stored everything. Some tables save per section. Some need an extra confirmation. You find B2B intact and HSN empty.

Where to click on the GST portal

gst.gov.in → Login → Services → Returns → Returns Dashboard. Choose financial year and return period. Open GSTR-1 (or IFF in a QRMP month, which is a different article). Prepare Online is the usual path for a small invoice count.

Work table by table: B2B, B2C, credit notes, advances if you use those, then documents issued, then HSN-wise summary (Table 12 on many screens). After each table, use the Save that belongs to that table. Then use the GSTR-1 Generate Summary / Proceed to file type of button — labels change, the idea does not: details must roll into a summary the portal accepts.

Only after summary is clean do you File Return. Filing needs EVC OTP or DSC. OTP on authorized signatory mobile. If you stop at Save, status stays unfiled.

If you use the Excel/JSON offline utility: download the current template from the portal, fill, generate JSON, then GSTR-1 → Prepare Offline → Upload. Read the error file. Do not upload a JSON from a different GSTIN or a different month.

To see whether you actually filed, stay on Returns Dashboard and read the status tile for that period. Acknowledgement number appears after a real file, not after a draft save. Download the filed GSTR-1 PDF when it is available so a buyer argument can be answered with a document.

What to try tonight

Open GSTR-1 and look at the dashboard of tiles inside the return. Compare counts with your invoice book. If B2B tile says 0 and you issued five taxable invoices to registered buyers, those five never saved or they saved under another period.

Click into B2B. Check GSTIN of the buyer, invoice number, date, taxable value, tax rate. A duplicate invoice number in the same year is a common save-but-not-file poison. Change the number in your books only if the invoice was truly wrong; do not mint fake series to silence the portal.

For B2C, confirm you did not put a registered buyer in B2C. That mismatch shows up in summary. Small shops do this when the buyer GSTIN was not copied in time.

Open Table 12 HSN. If it is mandatory for your case on the current portal rules, empty HSN or HSN totals that do not match supplies will block filing. Fill HSN from the invoice, not from a guess. If you are unsure of a code, get local help. Do not pick a random HSN to pass the validator.

Generate summary. Read every warning. Fix the table it names. Save again. Generate summary again. Only then File.

If the session is old, save, log out, log in, open GSTR-1, confirm data is still there, then file. Filing on a dying session is how people say “I filed” and the dashboard says no.

If JSON failed, download the error report. Fix source rows. Upload once. Avoid mixing online edits and a fresh JSON without knowing which is master.

Keep the phone free for filing OTP. The same OTP delay that blocks login can block GSTR-1 file at 11:55 p.m.

Mistakes that make the night longer

Thinking Save Draft equals File. Tell the helper the difference before they go home.

Editing invoices after generating summary without generating summary again.

Uploading JSON, then punching the same invoices online, doubling supplies. Summary explodes. Filing dies.

Leaving Table 12 for “tomorrow” because HSN is boring. Tomorrow File is still grey.

Using an invoice date outside the tax period. The table may save and the summary may refuse.

Staying on GSTR-1 while someone else opens the same return in another city. Parallel sessions.

When to stop and get local help

Stop if summary errors mention amendments, notes, or tables you never use and you cannot see why. Forcing File can file a wrong 1.

Stop if you already clicked File, OTP failed, and status is unclear — neither draft nor filed. Do not File twice without reading the tile.

Stop if JSON error list is hundreds of rows and the shop only had twenty invoices. The template or GSTIN mapping is wrong.

Stop if HSN rules for your turnover are unclear on the live screen. Check current portal validation; if it still will not accept a honest total, a practitioner should look.

Bring invoice list, GSTR-1 screenshots of tiles, error text, and the period. Do not send a JSON with every customer’s GSTIN to a random “helper” on chat.

FAQ

I see Saved successfully. Why is GSTR-1 still not filed?

Save writes the table to GSTN as a draft. Filed means you completed File Return with EVC or DSC and the dashboard status changed. Buyers do not see draft invoices in 2B. Open Returns Dashboard for that month and look at the status, not at the last green toast message.

What is an invoice summary mismatch?

The portal adds your detailed tables and compares them with the summary it generates. If one B2B invoice failed validation, or HSN totals differ from supply totals, or B2B/B2C classification is mixed, File stays blocked. Fix the named table, save, generate summary again. Do not delete random invoices just to make counts pretty.

Session timed out after I entered fifty invoices. Did I lose them?

Often table-wise Save kept the tables you saved. Open GSTR-1 again and check tiles. If a table is empty, you must re-enter that table. From now on, save after every small batch. Do not type for an hour without Save. Timeout is normal on a slow line; lost unfiled data is the expensive part.

Should I upload JSON and also type the same bills online?

No. Pick one master. Offline JSON is for volume. Online is for a short list. Mixing both without clearing the return is how duplicates appear and filing fails. If an upload error remains, fix the JSON or delete the bad draft rows as the portal allows, then file once.

GST Atka is not a GSTN office. File on gst.gov.in. Rules change. Do not evade tax. Personal case: get local help.