India's GSTR-3B Hard Lock: Your Input Credit Now Moves Only as Fast as Your Slowest Vendor

You paid the GST. The money left your bank account the day you paid your supplier's invoice. But when you open your GSTR-3B return, the portal refuses to let you claim the credit — because your supplier has not filed their return yet. Under India's new hard-locking regime, that is not a glitch. It is the design. Your input tax credit now flows through a locked pipeline — supplier filing to your Invoice Management System dashboard to GSTR-2B to Table 4 of GSTR-3B — and no step in that pipeline accepts a manual override anymore.

This guide explains what hard locking changed, how the new accept-reject-pending workflow governs your credit, the five traps that freeze a small business's working capital, and the monthly routine that keeps your cash flow moving.

What "Hard Locking" Actually Means​

GSTR-3B is the monthly summary return where every regular GST-registered business declares its output tax and claims its input tax credit (ITC). For years, the portal auto-populated parts of it but still let you edit the figures at filing time — a useful escape hatch when your books and the portal disagreed.

Hard locking removes the escape hatch in two phases:

• Phase 1 — outward liability locked. Tables 3.1 and 3.2 of GSTR-3B, which carry the tax on your sales, became read-only and flow directly from what you reported in GSTR-1, GSTR-1A, and IFF. If your GSTR-1 has a wrong invoice value, a wrong GSTIN, or a wrong place of supply, the error flows straight into GSTR-3B. The only fix is a correction through GSTR-1A before you file.
• Phase 2 — input credit locked. Table 4, which carries your ITC claim, is linked to GSTR-2B data with no manual ITC entry for business-to-business purchases. The invoices you accept in the Invoice Management System (IMS) feed GSTR-2B, which then feeds GSTR-3B. This phase was signalled for the July 2026 tax period as part of the government's drive against fake ITC claims.

The stated goal is fraud prevention: shell-invoice rackets that inflated ITC claims cost the exchequer heavily, and a return you cannot hand-edit is a return that cannot carry invented credit. But the same lock that blocks fraud also blocks legitimate corrections at filing time. Whether the portal flips the final switch this month or next, the only safe posture is to operate as if the return is already locked — because the reconciliation discipline it demands takes weeks to build and cannot be improvised on the 20th.

How Your Credit Flows Now: The Locked Pipeline​

Every rupee of B2B input credit you claim must now travel the same path, in order, on schedule:

1. Your supplier saves or files the invoice in GSTR-1, IFF, or GSTR-1A. Monthly filers report by the 11th of the following month. Until they do, the invoice does not exist as far as your credit is concerned.
2. The invoice appears on your IMS dashboard. The Invoice Management System, live on the portal since October 2024, shows you every invoice, debit note, and credit note your suppliers have attributed to your GSTIN.
3. You act on each record: accept, reject, or keep pending. Only accepted records flow into your credit statement. Rejected records are excluded; pending ones are carried forward to a later period.
4. GSTR-2B is generated on the 14th of the following month from your IMS actions. If you act on invoices after the 14th, you must recompute the draft GSTR-2B yourself, or your return will be built on stale data.
5. Table 4 of GSTR-3B auto-fills from GSTR-2B. Under locking, you file what the pipeline produced. GSTR-3B is due on the 20th.

Notice what disappeared: the step where you typed a credit figure from your own purchase register. Your books are now an input to a verification workflow, not the final word. That makes the monthly calendar — 11th, 14th, 20th — the skeleton of your entire compliance routine.

The Three IMS Actions, and When to Use Each​

IMS gives you three choices per supplier record, and each has a precise consequence:

• Accept when the invoice is genuine, the goods or services were received, and the details match your books. Accepted invoices become part of GSTR-2B and flow into your ITC. Accept deliberately, not by default — accepting a wrong invoice locks a wrong credit into your return.
• Reject when the invoice is not yours, is duplicated, or carries a material error such as the wrong GSTIN. Rejected records are excluded from your GSTR-2B, and the invoice goes back to the supplier's dashboard for amendment. Rejection is a communication act as much as a compliance act: tell the supplier the same day, because only they can fix the source document.
• Keep pending when the invoice is legitimate but premature — goods in transit at month-end, a debit note under dispute, a credit you prefer to claim next period. Pending records stay out of the current GSTR-2B and carry forward. Note the exception: credit notes cannot be kept pending. You must accept or reject them, so liaise with the supplier before the 2B generation date rather than parking the decision.

One habit matters more than any other here: verify each record against your purchase register before acting. IMS shows what suppliers say they sold you; your books show what you actually received and paid for. Acting on the dashboard without that cross-check is how businesses accept phantom invoices or reject genuine ones — and under locking, either mistake is baked into the return.

Five Traps That Freeze Your Working Capital​

1. The late-filing vendor: credit delayed is cash denied​

This is the headline risk of the locking era, and it is the most common trap of all. If your supplier files GSTR-1 late, their invoices miss your GSTR-2B for the month. You cannot claim the credit, so you pay that much more tax in cash — and recover the credit only in a later period when the supplier finally files.

For a business buying regularly from one large supplier, a single chronic late filer can drain working capital every month on a rolling basis. The credit is never lost, only deferred — but a permanent one-month deferral of, say, ₹80,000 of ITC is economically identical to an ₹80,000 interest-free loan you never agreed to give.

The defence is vendor management, not tax planning: track each regular supplier's GSTR-1 filing punctuality, follow up before the 11th, and for high-value relationships, tie payment release to the invoice appearing in your IMS dashboard.

2. The QRMP timing trap: quarterly suppliers, monthly hunger​

Suppliers under the Quarterly Return Monthly Payment (QRMP) scheme file GSTR-1 quarterly. If you file monthly and buy from a QRMP vendor, their invoices reach your IMS only in the quarter-end cycle — your January and February credits from that vendor arrive with the March filing.

This is entirely legal on the vendor's side and entirely painful on yours. Before signing a recurring purchase arrangement, ask every vendor whether they file GSTR-1 monthly or quarterly, and record the answer in your vendor master. A slightly cheaper quarterly-filing supplier can be the more expensive choice once you price in two months of deferred credit.

3. The wrong-GSTIN invoice: invisible until it hurts​

If your supplier types your GSTIN incorrectly or selects the wrong place of supply, the invoice never appears in your IMS at all. There is nothing to accept, nothing to follow up on inside the dashboard — the credit simply does not exist until the supplier amends via GSTR-1A.

The only way to catch this is the purchase-register reconciliation: every purchase invoice in your books must have a matching IMS record. An invoice with no IMS twin by the 12th or 13th is either a late filing or a data error, and both need a phone call, not patience.

4. The post-14th action without a recompute​

GSTR-2B generates on the 14th, but IMS lets you act on invoices right up until you file GSTR-3B. The catch: actions taken after the 14th do not update your GSTR-2B automatically. You must explicitly recompute the draft 2B on the portal.

Forgetting the recompute is the purest locking-era footgun: you did everything right — chased the vendor, accepted the invoice on the 17th — and still filed a return without the credit, because the return read the 14th snapshot. Put "recompute 2B" as a separate line item on your filing checklist, distinct from "act on IMS."

5. The reversals locking does not do for you​

Hard locking governs what flows in to Table 4. It does not compute what must flow back out. You still have to reverse ITC yourself for:

• Exempt and non-business use under Rules 42 and 43, including the personal-use and exempt-supply proportion for mixed businesses.
• Unpaid invoices past 180 days. If you have not paid the supplier the full invoice value including tax within 180 days of the invoice date, you must reverse the credit and pay interest from the original claim date. Under locking, the portal will not remind you — the reversal table still expects you to know.
• Blocked credits under Section 17(5): motor vehicles, food and beverages, works contract services for immovable property, and the rest of the blocked list. Accepting such an invoice in IMS does not make its credit legitimate.

Claiming excess ITC and sorting it out later now carries interest risk with no filing-stage correction available. The reversals deserve their own review pass before every filing.

Your Monthly Routine: The 11th, 14th, and 20th​

Turn the pipeline into a calendar ritual. A workable rhythm for a small business:

• By the 11th — supplier watch. Check that your regular vendors have filed GSTR-1. Follow up with anyone missing; a reminder on the 9th beats a crisis on the 19th.
• 12th to 13th — IMS first pass. Open the dashboard, match every record against your purchase register, and act: accept the clean ones, reject the wrong ones (and call the supplier immediately), park the premature ones as pending.
• On the 14th — verify generation. Confirm GSTR-2B generated correctly. Download it and reconcile the total against your books line by line.
• 15th to 18th — chase and recompute. Resolve stragglers, get suppliers to correct via GSTR-1A, act on late-appearing invoices, and recompute GSTR-2B after every post-14th action.
• 19th to 20th — reversals review, then file. Run the Rule 42/43, 180-day, and blocked-credit checks, confirm Table 4 matches your reconciled 2B, and file GSTR-3B.

The whole routine is perhaps two focused sittings a month for a business with a handful of regular suppliers — far cheaper than the interest, notices, and cash-flow gaps it prevents.

Why Your Books Are Now a Compliance Control​

Under the old editable return, bookkeeping accuracy and filing accuracy were loosely coupled: the return could paper over gaps in the books. Locking fuses them. Your purchase register is now the reference dataset against which IMS records are judged, the 180-day payment clock ticks per invoice in your payables, and the vendor master — GSTIN, filing frequency, punctuality history — is a working-capital management tool, not admin trivia.

That raises the bar for record-keeping in a specific way: it must be current, not reconstructed. A ledger you update as transactions happen lets you run the IMS cross-check on the 12th with confidence. A ledger you rebuild from bank statements at quarter-end leaves you accepting dashboard records blind — exactly the behaviour the locked return punishes.

A plain-text, version-controlled ledger fits this workflow well: every invoice entry is timestamped and traceable, reconciliations against GSTR-2B downloads can be scripted and repeated identically each month, and nothing about the month's position is a mystery on the 19th. You can read more about this approach in the documentation.

Keep Your Cash Flow Ahead of the Portal​

India's locked GSTR-3B turns supplier discipline into your working capital problem: a vendor who files late, files quarterly, or mistypes your GSTIN now directly controls when you recover tax you already paid. The businesses that sail through are not the ones with the cleverest tax positions — they are the ones with a monthly IMS routine, a vendor master that records filing behaviour, and books current enough to reconcile on the 12th instead of scrambling on the 20th.

Maintaining that kind of always-current financial record is exactly what plain-text accounting is built for. Beancount.io gives you transparent, version-controlled books you can reconcile against GSTR-2B every month with nothing hidden. Get started for free and see why developers and finance professionals are switching to plain-text accounting.