GSTR-3B Auto-Lock: What Changes for Filers

For most of GST's life, GSTR-3B was where the month got tidied up. If GSTR-1 went out with a wrong taxable value, you typed the right number into Table 3, paid the right tax, and dealt with the mismatch later or never. That habit is gone. Hard-locking was announced in October 2024, deferred once, and took effect for the July 2025 tax period — the returns filed from August 2025 onward. The outward liability in GSTR-3B is now computed from your own GSTR-1, IFF and GSTR-1A and presented as a locked figure, and the credit side arrives shaped by GSTR-2B and your IMS decisions. What follows is what that does to your process: what is actually locked, what is still yours to fill, and which route replaces the edit you used to make. For the return walked through section by section, start with the GSTR-3B filing guide.

Where each GSTR-3B figure now comes from

GSTR-3B is no longer a form you fill. It is a statement assembled from returns you have already filed, with a small number of fields left open for things the system cannot know.

The outward side is drawn from GSTR-1 for monthly filers, from the Invoice Furnishing Facility for the first two months of a QRMP quarter, and from GSTR-1A where you have filed one. Every B2B invoice, B2C summary, credit note, debit note and export entry rolls up into Table 3.1 and 3.1.1, and the place-of-supply breakdown rolls into Table 3.2. What goes into each of those source tables is covered in the GSTR-1 filing guide.

The input side is drawn from GSTR-2B, which is itself a product of the Invoice Management System. What your suppliers filed lands in IMS, you accept, reject or leave it pending, and GSTR-2B is built from those actions. Table 4 is then pre-filled from that statement — the full sequence is in GSTR-2B and the Invoice Management System.

GSTN arrived at this in stages. The lock on outward liability was announced in an advisory in October 2024, deferred after the first date passed, and finally applied to the July 2025 tax period, which is to say the GSTR-3B filed from August 2025 onward. The ITC side is the part that is still moving: GSTN has signalled an intention to tighten Table 4 in a later phase, and that has not landed as a hard lock. If you are filing for a period after this article was last reviewed, confirm the ITC position on gst.gov.in before assuming Table 4 is still editable.

What "non-editable" actually means

"Non-editable" is doing a lot of work in the advisories. Three different things get described with the same phrase, and only one of them is a lock.

Locked means the field is not an input. The value is a computed total — no override box, no reason code, no "declare a difference" path. If GSTR-1 says ₹18,00,000 of taxable value at 18%, the liability in Table 3.1(a) is ₹3,24,000 and your only lever is the ₹18,00,000.

Flagged is not locked. Table 4 is pre-filled from GSTR-2B, you can change it, and a change beyond the tolerance band produces a warning rather than a block. An ITC figure you cannot justify is a risk you took, not a door the portal shut for you — and what you are entitled to claim is governed by the input tax credit rules, not by the tolerance.

Sequenced is not locked either. The portal has blocked GSTR-3B until GSTR-1 for the same period is filed for some years now. That is an ordering rule. Auto-lock layers something different on top: it makes the content of GSTR-1 binding, not merely mandatory.

Why GSTN closed the gap

The gap between GSTR-1 and GSTR-3B was the most productive source of departmental correspondence in GST, and it was trivially detectable: two numbers filed by the same taxpayer for the same period on the same portal, one reporting outward supplies and one reporting tax paid on them.

A difference produced two standard outputs. A system-generated intimation in Form DRC-01B, requiring you to explain or pay the excess liability declared in GSTR-1 but not discharged in GSTR-3B, with the portal blocking your next GSTR-1 until you respond. And a scrutiny notice in Form ASMT-10, where an officer picks the period apart line by line.

Most of those cases were not evasion. They were typos, a credit note entered in the wrong month, a classification changed after GSTR-1 went out. Auto-lock removes the possibility of the mismatch rather than policing it after the fact.

The correction routes that replace editing

Every correction you used to make inside GSTR-3B has a specific replacement. There are three, and which applies depends on what is wrong and how early you caught it.

Outward supplies, caught before GSTR-3B is filed: GSTR-1A. File it for the same tax period. You can add a missed invoice, amend the value, rate or place of supply of one you reported, or correct a credit or debit note, and the revised figures flow into the auto-populated GSTR-3B. One limitation: the recipient's GSTIN on an already-reported invoice cannot be changed through GSTR-1A.

Input tax credit: IMS, then regenerate GSTR-2B. Table 4 is not corrected by typing over it. Go into IMS, accept an invoice you left pending, reject one that is not yours, and recompute GSTR-2B so the statement and the return agree. Do it before you file, and before the limit under Section 16(4) closes on the credit — a credit deferred past that date is not deferred, it is lost.

Anything caught after GSTR-3B is filed: amend in a later GSTR-1. Use the amendment tables in a subsequent period's GSTR-1 — B2BA, CDNA and the rest. The corrected value lands in that later period's auto-populated GSTR-3B and the difference is settled there.

The pre-filing checklist this forces on you

The structural change is not in GSTR-3B at all. Your reconciliation has moved a week earlier and one return upstream, because reconciling GSTR-1 to books after filing it no longer works as a control — by then the liability is set. Before you file GSTR-1 or IFF, check these against your books of account:

• Total taxable value and tax by rate, matched to the sales register for the period.
• Credit and debit notes issued in the period, including ones raised against an earlier period's invoice.
• Exports and SEZ supplies, split correctly between with-payment and without-payment.
• Place of supply on every inter-state B2C entry, since Table 3.2 is built from it and is locked.
• Advances received and adjusted, which are reported in GSTR-1 but not in the invoice tables.
• Recipient GSTINs on B2B invoices — the one field GSTR-1A will not let you fix.

Then, after GSTR-1 is filed, open the auto-populated GSTR-3B and read it as a statement rather than a form. If any figure surprises you, that is a GSTR-1A job, and you have until you press submit to do it.

When a clerical error is caught too late

Suppose an invoice was reported at ₹5,00,000 instead of ₹50,000, GSTR-1 went out, GSTR-3B was filed on the strength of it, and someone notices the following month.

The excess tax is already paid, because the locked liability in Table 3.1 was discharged from the electronic cash or credit ledger when you filed. You cannot unpay it. You amend the invoice in the next period's GSTR-1 through the B2BA table, which reduces that period's auto-populated liability by the excess, and the benefit arrives as a lower payment next month rather than a refund.

If the error ran the other way and understated tax, the amendment increases the later period's liability and interest at 18% per annum runs from the original due date to the date of actual payment, not from the date you noticed. There is also a recipient-side consequence: your customer's GSTR-2B for the original month carried the wrong figure, and their IMS and ITC position moves when your amendment lands.

The outer limit on all of this is 30 November following the end of the financial year, or the date you file the annual return for that year, whichever is earlier. After that the error is permanent in the returns.

The QRMP wrinkle

Quarterly filers get the same mechanism with a longer fuse. Under QRMP, B2B invoices for the first two months go up through IFF, the rest goes into the quarterly GSTR-1, and one quarterly GSTR-3B draws its liability from all of it.

Two consequences follow. An error uploaded through IFF in month one does not surface as a liability figure you would notice until the quarter's GSTR-3B is generated, up to two months later. And the tax paid in months one and two went through a challan into the electronic cash ledger on an estimated or fixed-sum basis, so it validates nothing — it is an instalment against a total computed at quarter end.

So a QRMP filer should reconcile IFF uploads monthly anyway, even though nothing forces it. Waiting for the quarter to close means discovering three months of errors at the one moment when GSTR-1A is the only route left and the clock is short.

The control that sits upstream of all of it

Follow the chain back far enough and most of these mismatches did not originate in the return at all. They originated in master data: a supplier GSTIN keyed with a transposed character, a vendor whose registration was cancelled two quarters ago, a supplier who quietly stopped filing GSTR-1 so their invoices never reach your GSTR-2B.

Each produces a different downstream failure. A wrong GSTIN on a sales invoice means a B2B entry your customer cannot see and a recipient GSTIN that GSTR-1A cannot amend. A cancelled supplier means ITC in Table 4 that will not survive scrutiny. A non-filing supplier means a permanent gap between your purchase register and GSTR-2B.

All three are cheap to prevent and expensive to unwind, and the prevention is the same in every case: verify the GSTIN and check the filing history before the invoice is booked, not at the month end. The method for the second half of that is in how to check a supplier's GST return filing status, and the way to wire it into a purchase workflow is in vendor GST verification for accounts payable.

To automate it, our API returns registration details and GSTR filing history in a single call at ₹0.50 per verification, falling to ₹0.40 once a purchase crosses 2,500 credits, with no subscription and no expiry on purchased credits. Full details on pricing.

Frequently asked questions