GST 2.0 Is Live in 48 Hours: 6 Software Changes Before April 1

GST 2.0 goes live in 48 hours. The April 1, 2026 rollout brings the lowered ₹5 crore e-invoicing threshold, a non-editable GSTR-3B, mandatory MFA on every IRP login, and the IMS hard-block on mismatched ITC. We've audited 18 billing setups in the last three weeks — Tally Prime, Zoho Books, BUSY, and four custom Node/Laravel apps. This post is the exact 6-item software checklist we ran, with the gotchas that almost always break the first April invoice. ## What "GST 2.0" actually means on April 1 The label is informal — there's no single notification called GST 2.0. It's the cumulative effect of the 56th GST Council meeting (September 2025), the Union Budget 2026 confirmations, and a string of CBIC notifications that all switch on together on April 1, 2026. The shift is from "file-then-audit" to "validate-before-file". If your software was built for the older flow, four things will break on day one: invoice numbering, IRP authentication, GSTR-3B editing, and ITC claims that don't match GSTR-2B. ## The 6 changes, in priority order ## The 30-minute DIY walkthrough Run through this list on March 30 or 31. Each step has a verification check. ## What breaks first — and the fix These are the failures we've actually seen across three audits in the last two weeks.

Symptom on April 1	Root cause	Fix
"Duplicate invoice number" error from IRP	Document series not reset — system reused FY 2025-26 numbers	Step 1 above. Confirm with one test invoice before going live.
IRN generation hangs / times out	Stored IRP credentials don't have MFA enrolled	Re-login manually with OTP, regenerate the API token, update Tally/Zoho integration.
Buyer complains "ITC not showing in GSTR-2B"	Invoice uploaded to IRP more than 30 days after invoice date	The invoice can't be retroactively claimed. Issue a credit note + fresh invoice with current date if commercially feasible.
GSTR-3B Table 3.1 won't accept edits	Hard-locking active from July 2025 tax period	Make corrections via GSTR-1A in the same month, then file GSTR-3B with auto-populated values.
GSTR-3B filing blocked at submit	IMS hard-block — claimed ITC exceeds GSTR-2B	Reconcile via IMS, mark unmatched supplier invoices, ask supplier to amend, refile.

## When NOT to change your invoice prefix mid-month If you've already issued the first April invoice with the old (FY 2025-26) series, do not retro-renumber. That breaks audit trail and creates downstream confusion with buyers who've already taken delivery. The cleaner fix: issue a credit note against the misnumbered invoice, then issue a fresh invoice with the FY 2026-27 series. Document the reason in your tax invoice register. Your CA will thank you at audit. Similarly, if your custom billing app uses a global sequence (not GSTIN-scoped), don't add the GSTIN-scoping retroactively for old invoices. The unique constraint should apply going forward only. ## Pre-April 1 software checklist (print this)

• Tally Prime: F11 > Statutory > "Restart numbering" set to Yearly with prefix INV/2026-27/
• Zoho Books: Settings > Preferences > Invoices > "Reset every year" enabled
• Custom apps: financial_year column added; unique constraint on (gstin, financial_year, invoice_number)
• All IRP user accounts re-verified with MFA (OTP or authenticator)
• Stale IRP API tokens regenerated post-MFA enrolment
• 30-day alert configured in your ERP for invoices nearing the IRP cutoff
• Friday 4pm IMS review block on the team calendar
• GSTR-3B Table 3.1 / 3.2 override scripts disabled
• LUT for FY 2026-27 filed (exporters only)
• One end-to-end test invoice generated with FY 2026-27 prefix; IRN printed cleanly

## How the changes interact for a typical SMB workflow The six changes don't operate in isolation; they cascade. A simple example: a Surat textile trader issues an invoice on April 2 with the wrong prefix (continuation of FY 2025-26). The IRP accepts it because the invoice number is technically valid. But on May 14, when the same buyer's GSTIN appears again with a new invoice, the IRP throws a duplicate-number error because the new sequence (correctly reset to FY 2026-27) has now looped back to a number used in March. The fix at that point is messy — issue a credit note for the rogue April 2 invoice, reissue with the correct series, ask the buyer's accounts team to reverse and re-claim ITC. All of which is preventable by spending 15 minutes on March 31 to reset the prefix correctly. Similarly, the IMS hard-block and the GSTR-3B non-editable tables interact. If a supplier uploads an invoice with the wrong GSTIN (yours vs your sister concern), it lands in your IMS as "pending acceptance". If you don't reject it, it auto-flows to your GSTR-2B as accepted ITC. When you file GSTR-3B, your claimed ITC matches GSTR-2B (both wrong). Your sister concern's GSTR-2B doesn't show the credit. Three months later at audit, you have a mess. The discipline of weekly IMS review prevents this. Friday afternoon, 45 minutes, accept-reject every supplier line. Catch wrong-GSTIN claims before they cement into your filed returns. ## Three CA workflows that will change If your books are kept by an external CA, three changes need to be socialised before April 1: - Mid-month corrections move from GSTR-3B to GSTR-1A. Your CA's habit of "fix it in the 3B" no longer works for outward supply tables. Corrections must go through GSTR-1A in the same month before the 3B is filed. - IMS becomes a weekly task, not month-end. Most CA offices process IMS at the end of the month for all clients. That doesn't scale anymore — month-end becomes a bottleneck. Ask your CA to schedule weekly IMS review for your business. - The 30-day IRP rule shifts billing pressure to your sales team. If a customer asks for a backdated invoice (common in March), the IRP now rejects anything over 30 days. Your CA can no longer "make it work". Sales needs to communicate the new rule to buyers. ## Real example — a Pune logistics SMB, ₹6.4 Cr turnover Client: an Pune-based logistics aggregator running on Tally Prime with a custom REST API connector to their dispatch tool. FY 2025-26 turnover crossed ₹5 Cr in February 2026, putting them in scope for e-invoicing from April 1. The breaks we found in their pre-April audit: - Tally invoice numbering was set to "Continuous" — would have generated INV/2025-26/14501 on April 1 instead of INV/2026-27/00001. - Their dispatch API used a stored IRP token from 2024 — pre-MFA. The first IRN generation post April 1 would have failed with auth error. - Their CA's Excel macro was rewriting GSTR-3B Table 3.1(a) for inter-state vs intra-state allocation — that would have triggered a portal rejection. Total fix time: 90 minutes. Cost of NOT fixing: the dispatch tool would have refused to print delivery challans without an IRN, halting outbound shipments. For a logistics firm running 180 dispatches a day, every hour of downtime is direct revenue loss. The Reddit thread on [r/IndiaTax](https://www.reddit.com/r/IndiaTax/) is full of similar last-week panics in March every year — it's predictable. The fix is to not be the firm that finds out at 11am on April 1. ## FAQ ### Is GST 2.0 actually one new act, or a bundle of changes? It's a bundle. The "2.0" branding is informal — used by CBIC commentary and CA firms to capture the cumulative effect of the September 2025 GST Council decisions, Budget 2026 amendments, and roughly 8 CBIC notifications. There's no single notification labelled "GST 2.0". ### My turnover is ₹4.8 crore. Am I in scope for e-invoicing from April 1? Not yet. The e-invoicing threshold drops to ₹5 crore. The threshold check is on aggregate annual turnover (AATO) of any financial year from FY 2017-18 onwards. If you've never crossed ₹5 Cr in any of those years, you're not in scope — yet. Watch the CBIC notifications; the threshold has trended downward steadily. ### Does the 30-day IRP rule apply to all e-invoicing taxpayers? No. The 30-day reporting limit applies to taxpayers with AATO of ₹10 crore and above. Below ₹10 Cr but above ₹5 Cr, you must still issue e-invoices, but there's no hard 30-day cap at this stage. Build a 30-day alert anyway — the threshold may drop further in Budget 2027. ### What is GSTR-1A and when do I use it? GSTR-1A is the amendment form for the same tax period. From the July 2025 tax period, Tables 3.1 and 3.2 of GSTR-3B are auto-populated from GSTR-1/1A and are non-editable. If you need to correct an outward supply for the same month, file GSTR-1A before submitting GSTR-3B. ### Will Tally Prime auto-handle the series reset? Only if "Restart numbering" is set to "Yearly" under F11 > Features > Statutory. The default on most installs is "Never" — which means it just keeps incrementing. Manually verify before the first April invoice. Zoho Books has a similar setting under Preferences > Invoices. ### What is the IMS "hard block"? If your claimed ITC in GSTR-3B exceeds the ITC available in GSTR-2B for the same period, the GST portal blocks the filing entirely until the gap is resolved. The fix is to reconcile via the Invoice Management System — accept, reject, or keep pending each supplier invoice before filing. ### Where can I find the official CBIC notifications? The canonical source is [cbic-gst.gov.in](https://cbic-gst.gov.in/hindi/central-tax-notifications.html) under Central Tax Notifications. Search for notifications dated December 2025 onwards. The Institute of Chartered Accountants of India also publishes consolidated summaries that are easier to scan. For broader compliance reading on what changes year-over-year, our founder [Vivek Singh](https://viveksinra.com) writes on the same beat with a more first-person founder lens. Email us directly at contact@softechinfra.com if you'd like the audit checklist sent over before the call.