GST 2.0 Goes Live Today: 6 Software Updates Every Tally + POS Integration Needs by EOD

GST 2.0 is live today, September 22, 2025. The two-slab structure (5% / 18% with 40% for sin/luxury) kicks in from this morning per [CBIC Notification 14/2025](https://www.caclubindia.com/news/cbic-releases-faqs-3-on-gst-rate-changes-and-notifications-effective-september-22-2025-25487.asp) issued on September 17. We are doing the cutover for nine clients today — Tally Prime, Zoho Books, three Shopify stores, two custom Node billing apps, and two POS-heavy retail chains. The same six updates need to happen on every stack by EOD. Three of those updates are easy. Three are where ERPs trip up. This post is the EOD checklist. ## The answer in 60 words Six updates by EOD: (1) apply the slab remap to your stock items in Tally / Zoho Books, (2) update your POS rate config table, (3) refactor any hardcoded rate constant in code, (4) update the e-invoice rate values your IRP integration submits, (5) update your invoice template to drop the cess line for autos and consumer durables, (6) brief your CA on the cutover-date handling for in-flight orders and credit notes against pre-cutover invoices. ## Why today matters The cutover is mid-quarter, not at a financial year boundary. That means your September 2025 GSTR-1 (due October 11) will contain invoices at both rate structures — pre-cutover (Sep 1-21) at old rates, post-cutover (Sep 22 onwards) at new rates. Your software needs to apply the right rate based on the invoice date, every time, without exception. A single invoice with the wrong rate becomes a downstream GSTR-3B mismatch and a buyer-side GSTR-2B issue. The PM's framing of [GST 2.0 as "GST Bachat Utsav"](https://www.kotakmf.com/Information/blogs/gst-2-point-0) emphasises consumer savings, but the operational reality for SMBs is a 1-day software cutover with non-trivial code paths to verify. ## The 6 updates, in EOD priority order ## The 3 fields most ERP integrations miss These are the silent failures we see when a custom ERP is wired to Tally or to the IRP via API. All three are easy to fix once you know to look.

Field	What goes wrong	Fix on your stack
Cess amount on auto / durables invoices	ERP keeps sending cess = X for SKUs where cess is now zero (merged into 40% rate)	In your ERP's tax-detail builder, set cess = 0 for stock groups marked "compensation cess merged"
HSN code length for <₹5 Cr turnover taxpayers	Your ERP defaults to 6 or 8 digits but your turnover band requires 4 digits	Auto-truncate HSN to required length based on previous-FY AATO; verify against [GSTN HSN advisory](https://tutorial.gst.gov.in/userguide/returns/GSTR_1.htm)
Place of supply on services delivered remotely	ERP defaults POS to seller's state for service invoices when buyer is in a different state	For Section 13(8) services (intermediary, OIDAR, immovable property), POS is the place of recipient — fix the lookup logic

## The EOD cutover checklist ## The slab remap (canonical EOD reference) Cross-checked against [Tally Solutions' rate change explainer](https://tallysolutions.com/gst/new-gst-rates-september-2025-business-impact/) and [EnKash's 56th Council Meeting summary](https://www.enkash.com/resources/blog/56-gst-council-meeting-key-updates).

Category (HSN guide)	Old rate	New rate	Notes
Processed food, packaged snacks, dairy	12%	5%	Tally Stock Group "Foods" — bulk remap
Refrigerators, washing machines, dishwashers	28%	18%	Cess removed (was 0% but column drops)
Air conditioners	28%	18%	10% drop on consumer-facing price likely
Cars under 4m, ICE petrol <1200cc	28% + 1-3% cess	18%	Significant price drop for entry-segment
Cars over 4m, large engines, SUVs	28% + 17-22% cess	40%	Cess merged; total stays similar
Tractors, agricultural equipment	12%	5%	Major win for rural buyers
Hotel rooms below ₹7,500/night	12%	5%	Channel manager / OTA rate sync needed
Cement	28%	18%	Construction sector boost
Tobacco, pan masala, gutkha	28% + cess	40% + cess (cess retained)	Cess stays for unmanufactured tobacco, bidi
Most professional services	18%	18%	No change

## When NOT to rush the cutover Three cases where slowing down today is the right move. (a) Mid-month inventory audit in flight. If your physical stock count is happening this week (often the case for retail chains doing month-end early), do not change rates until the count closes — otherwise your books and your physical inventory disagree on rate-driven valuations. (b) Open warranty replacement orders. A pre-cutover sale may need a post-cutover replacement at the original rate (warranty claim). Your replacement issue process needs an explicit rate override option. (c) Vendor-managed POS without confirmed rate push. If Posist or Petpooja has not confirmed the rate push has landed at your stores, do not manually edit till the vendor confirms — you will create reconciliation issues with their cloud-side data. ## Real example — an Indore retail chain (7 stores) cutover at noon today A multi-store retailer in Indore (textiles + home goods, 22 employees, ₹14 Cr turnover, 1,840 SKUs across 14 HSN groups). The cutover was planned on Sep 3 (Council day), refined on Sep 17 (notification day), executed today. The Tally side took 90 minutes via TDL bulk update. POS side (Logic ERP at the front desk) took 4 hours of manual rate verification at all seven stores because the vendor's rate push only covered the standard SKUs and not the seasonal Diwali stock that had been added in the last week. The store managers ran ₹100 test transactions at each till; one store had a price-tag printer that was still hardcoded to the old 12% — fixed by editing the receipt template, six lines of PHP. Total elapsed time end-to-end: 6.5 hours. The 80% rule held: 80% of items remapped cleanly, 20% needed manual verification. The staff briefing for Sep 23 (the first full operating day under the new rates) was the most important deliverable — front-desk staff needed to be ready for customer questions on price changes. We drafted a one-page FAQ on Sep 21 and printed copies for every store. We have done similar cutovers for nine clients in the last 24 hours through our [AI automation services](/services/ai-automation). The engineering pattern is the same; the SKU count and POS vendor mix vary. ## The post-cutover hygiene week

• Sep 22 EOD: every till at every store has rung at least one ₹100 test transaction at new rates
• Sep 23: monitor first full operating day for customer queries on price changes; train staff
• Sep 24: audit first day's e-invoice batch — verify rates against new slabs
• Sep 25: bank reconciliation for first 3 days of post-cutover transactions
• Sep 26: customer refund processing for any in-flight orders where price dropped due to cutover
• Sep 27: open PO audit — confirm every PO that ships post-cutover uses new rates in invoice
• Sep 28: GSTR-1 prep starts — verify Sep 1-21 vs Sep 22-30 rate split is clean in Tally
• Sep 29: first GSTR-1A correction window opens — flag any reported issues
• Sep 30: end-of-month close; rate split visible in Tally GSTR-1 final report
• Oct 1: ITC manual entry regime begins; GSTR-3B prep for September starts

## What we tell clients about day 2 Day 2 (Sep 23) is when customer-facing surprises arrive. A buyer who paid an advance for a refrigerator on Sep 18 expects either the original rate (28%) or the new rate (18%) — and is annoyed if it is the wrong one. Have the answer scripted. The legal answer is: rate at time of invoice, which means new rate (18%) if invoice is on Sep 22 or later. Most customers prefer the lower rate; some require a refund of the difference if the original advance was at the higher. For complex contracts (annual maintenance, hosting, multi-month services), the contract date and invoice date may not match. Refer your CA's transition note for the per-contract treatment. We crosschecked our cutover playbook against [r/IndiaTax discussions](https://www.reddit.com/r/IndiaTax/) and the [BCAS GST 2.0 transition slides](https://bcasonline.org/wp-content/uploads/2025/09/GST-2.0-Sectorial-Impact-and-Transitional-challenges-CA-Divyesh-Lapsiwala.pdf). The dominant theme: customer comms is the most underrated cutover task. ## FAQ ### Are Tally and Zoho Books auto-applying the new rates today? No. Tally Solutions has published a [rate change explainer](https://tallysolutions.com/gst/new-gst-rates-september-2025-business-impact/) and a Stock Item bulk update template, but the user has to apply the change. Zoho Books similarly publishes the new tax rates in the library but you must update each Item's tax association. ### What rate applies to a sale on Sep 21 invoiced on Sep 23? The invoice date determines the rate. Sep 23 invoice = new rate. The transaction date and tax-rate effective date are both relevant to GSTR-1 reporting. ### Does the cutover affect my e-Way Bill rates? The e-Way Bill schema is rate-agnostic — it carries the consignment value, not the tax rate. No change needed in your e-Way Bill flow. ### What about credit notes against pre-cutover invoices? The credit note inherits the rate of the original invoice. A CN raised Sep 25 against an invoice dated Sep 15 carries the old rate (e.g., 28%) — not the new rate. ### How does cess work after the cutover? For most products that previously had compensation cess + 28% GST, the cess is merged into the new 40% rate. Exceptions: unmanufactured tobacco, bidi, gutkha, pan masala — cess stays as a separate line item at the original rate. Verify per-SKU against the [CBIC notifications](https://cbic-gst.gov.in/). ### My Shopify store has tax classes set in the admin. Do I update those? Yes. Shopify > Settings > Taxes > India > Tax classes. Update the rate against each class (Standard 18%, Reduced 5%, Sin/Luxury 40%). The store will apply the new rate to all post-cutover orders automatically. ### What if I file my September GSTR-1 with all transactions at old rates by mistake? You file GSTR-1A in the same tax period (October 11 deadline window) to correct. The correction flows through to GSTR-3B Tables 3.1/3.2 automatically. No portal penalty for the correction itself, but expect buyer-side ITC delays of about a month. For the pre-plan that should have happened on Sep 3 (Council day), see our [pre-plan post](/blog/gst-council-56th-meeting-september-3-2025-software-changes). For the cleanup that follows the September GSTR-1, see our [GSTR cleanup window post](/blog/advance-tax-yesterday-14-days-gstr-1-cleanup-gstr-3b-september). Email contact@softechinfra.com if you want our cutover playbook sent before our call.