Softechinfra
Business

GST Council Meeting (3 September 2025): 4 Software Changes Indian SMBs Should Pre-Plan For Before Two-Slab GST 2.0

The 56th GST Council met on 3 September 2025, expected to approve a 5%/18% two-slab structure. The 4 software changes Indian SMBs should pre-plan for in Tally, Zoho Books, POS, and e-invoicing flows.

Softechinfra EditorialSoftechinfra Editorial
May 15, 202612 min read
GST Council Meeting (3 September 2025): 4 Software Changes Indian SMBs Should Pre-Plan For Before Two-Slab GST 2.0

The 56th GST Council meeting took place on 3 September 2025 under FM Nirmala Sitharaman in New Delhi. Industry watchers, Tally Solutions' own commentary, and Goodreturns' live blog all expected the same outcome: the 12% and 28% slabs would go away, leaving a two-slab structure of 5% and 18% with a 40% sin/luxury rate. If that lands, every Indian SMB software stack — from Tally Prime to Shopify checkout to a custom POS in a retail chain — needs four specific changes before the cutover (likely a 2-3 week window). This post is the pre-plan list, written for meeting day.

5% / 18%
Expected new merit / standard slab structure
40%
Special rate for sin / luxury goods
~175
Items expected to get cheaper at the cutover
2-3 weeks
Likely cutover window once notified

The answer in 60 words

Four software changes pre-plan for: (1) build a slab remap table in your accounting software keying old rates (12%, 28%) to the new ones (likely 18%, 18% or 5%/40% case-by-case); (2) refactor any hardcoded rate lookup in your POS or billing app into a config table; (3) plan an e-invoice schema validation pass for the 30-day post-cutover window; (4) write a one-time GSTR-1 transition note for your CA.

Why pre-plan on meeting day, not a week later

The Council's decisions take effect via CBIC notifications, usually issued within 14 days. Once notified, the cutover date is typically 7-15 days out. That gives Indian SMBs a 21-day prep window — except most of the SMBs we audit do not start prep until the cutover date is announced. We watched the 2017 GST rollout and the December 2018 28%-to-18% rationalisation. The pattern is identical: businesses that pre-planned during the Council meeting day shipped clean cutovers, businesses that waited for the notification scrambled for two weeks.

The fix is to do the four pre-plan items before the notification lands, so the post-notification work is verification rather than implementation.

What the expected outcome changes: Items currently at 12% (mid-market consumer durables, processed foods, packaged snacks, restaurant inputs) get pushed mostly down to 5%. Items at 28% (ACs, refrigerators, automobiles, tractors) get pushed mostly down to 18%. A small list of sin/luxury goods stays at 40% via a new special rate. The exceptions list is where the work lives.

The 4 software changes to pre-plan

1
Build a slab remap table
In Tally, this is the GST Rate Setup screen by Stock Group or Stock Item. In Zoho Books, it is the Tax Rate library. In a custom Node/PHP app, it is whatever table holds your tax_rate column. Build the remap as a JSON file today: old_rate, new_rate, effective_date, hsn_code. Keep it review-ready.
2
Refactor hardcoded rates out of code
Search your POS, billing app, and Shopify checkout extensions for any constant like TAX_RATE = 0.18 or const GST = 12. A hardcoded rate buried in code is one of the most common problems in SMB stacks. Move it to a config table or environment variable today.
3
Plan an e-invoice schema validation pass
The IRP schema does not change with the slab restructure, but the rate values it accepts will. Your e-invoice integration pulls TAX_RATE from your books and submits it. After cutover, run a 30-day audit script that checks every IRN for rate consistency vs the new slab table.
4
Write a one-page GSTR-1 transition note
For your CA: the cutover date splits the tax period into two rate regimes. Invoices dated before cutover use old rates; invoices dated on or after use new rates. Both flow into the same GSTR-1 month if they share a tax period. The note clarifies which rate applies to advance receipts, post-cutover credit notes against pre-cutover invoices, and reverse charge transactions in flight.

Where rates likely move (the high-confidence cases)

This is the directional list based on Council leak reporting and pre-meeting analysis from Dhruva Advisors. Treat as planning inputs, not gospel — verify against the actual notification when it lands.

Category Current rate Likely new rate Software action
Processed food, packaged snacks 12% 5% Update HSN-to-rate mapping in Tally Stock Item master
Mid-segment consumer durables 12% / 18% 18% (mostly) Re-test invoice templates for 12% line items moving up to 18%
Air conditioners, refrigerators 28% 18% POS price tags need re-print; web checkout cart needs CSS audit for new totals
Cars, motorcycles > 350cc 28% + cess 40% (cess merged) Cess line item disappears in invoice template; total stays roughly same
Tractors and agri equipment 12% 5% Refund / credit note flow for in-flight orders straddling cutover
Hotel rooms below ₹7,500/night 12% 5% PMS / channel manager rate sync; OTA rate replication
Restaurants (non-AC) 5% no ITC 5% no ITC (likely unchanged) No change expected, verify after notification
Tobacco, pan masala, gutkha 28% + cess 40% (cess retained for some) Special rate handling — cess stays for unmanufactured tobacco and bidi

The 90-minute pre-plan sprint (run this on your stack today)

1
Minutes 0-20: Inventory your rate-keyed assets
List every place in your stack where a GST rate is referenced: Tally Stock Item master (Statutory Info > GST Details), POS terminal config files, e-commerce platform tax classes (Shopify "Collections" or WooCommerce tax classes), invoicing app templates, accounting integrations. Spreadsheet it.
2
Minutes 20-50: Build the remap JSON
For each HSN code in your catalog, write a row: { hsn: "8418", current_rate: 28, expected_new_rate: 18, confidence: "high", source: "Dhruva Advisors note" }. Mark "low confidence" rows for items in the 12% pharmaceutical / education / healthcare zones — those rates may not move.
3
Minutes 50-70: Hardcoded-rate audit
In your codebase: grep -rn "0\.18\|0\.12\|0\.28" --include="*.js" --include="*.php" --include="*.py". Every match is a refactor candidate. Replace with a TAX_RATE_LOOKUP(hsn_code) function that hits a database table or config file. Test on staging.
4
Minutes 70-90: Draft the CA transition note
One page. Cover: cutover date handling, advance receipts straddling the cutover, credit notes against pre-cutover invoices, reverse charge in flight, and a procedure for any open purchase order that ships post-cutover. Send to your CA today; expect feedback within a week.

When NOT to pre-plan

Three cases where the right answer is "wait for the notification". (a) You sell exclusively services that are currently at 18%. Most professional services (consultancy, software development, hosting) stay at 18%. The two-slab structure does not move you. Read the notification when it lands, but do not pre-plan. (b) You are on a vendor-managed POS like Petpooja or Posist. The vendor will push a config update on cutover day. Your job is to keep the vendor's number handy. (c) Your invoice volume is under 100 a month. The manual rework cost is lower than the engineering cost of a remap pipeline. Wait for the notification, fix invoice-by-invoice.

Example: a 7-store retail chain

Take a hypothetical multi-store retailer (textiles and home goods, 22 employees) running Tally Prime with a front-desk POS such as Logic ERP, pre-planning the cutover on meeting day.

Say the slab remap table touches about 1,800 SKUs across 14 HSN groups. The Tally side is straightforward: the Stock Item master allows bulk update via TDL. The POS side is where surprises hide, for example a rate lookup hardcoded in the receipt printer template rather than the price master. Find those spots now and plan QA across every store's display screens.

If the cutover lands September 22 (the most-cited Council outcome date), the retailer spends that day verifying the remap under live load while stores stay open. A POS with dynamic pricing needs no rate-tag reprint; a static-pricing system means hours of re-tagging per store.

The engineering pattern is the same on every stack; the SKU count changes the effort. Our AI automation services cover this kind of pre-plan.

The pre-plan checklist (print this)

  • Slab remap JSON drafted with HSN → old rate → expected new rate → confidence level
  • All hardcoded rate constants in code identified via grep, refactor PR opened
  • Tally Stock Item master GST Details audited; bulk update TDL drafted
  • Zoho Books / WooCommerce / Shopify tax class list exported and annotated
  • POS vendor support contact saved on the CTO's phone
  • E-invoice integration audit scheduled for cutover day + 1 week
  • One-page CA transition note drafted, sent for review
  • Invoice template tested for cess removal on auto / appliances categories
  • Customer comms drafted for any open advance receipts straddling the cutover
  • CFO and ops manager briefed on the 21-day post-Council window

What our take is on the likely outcome

The two-slab structure is genuinely simpler. The 5/12/18/28 grid is easy to get wrong, and SMBs regularly mis-classify their own SKUs under it. A 5/18/40 structure with a clean luxury bracket is easier to explain, easier to enforce, and easier to audit. The transition cost is real — engineering work per SMB that scales with stack complexity — but the steady-state cost goes down. Most SMBs should recoup the prep cost through reduced misfiling and fewer CA hours.

The risk is the implementation date. If CBIC pushes the cutover within 14 days of the Council meeting, businesses that have not pre-planned will eat the rework cost in scramble mode. If the cutover gets pushed to April 1, 2026 (the start of the next financial year, which would be the cleaner administrative date), the prep window is comfortable but the temptation to procrastinate is high. Either way, the pre-plan work is the same.

For broader context on Indian regulation and tech, see our founder's GEO and Indian SMB perspective — the regulatory cadence is the same beat we cover for SEO and AI policy.

FAQ

When does the new GST structure take effect?

The new rates took effect on 22 September 2025, the date floated before the 3 September 2025 Council meeting. The date comes in the CBIC notification issued after a Council meeting, so for any future rate change, plan for a cutover window of 7-21 days from notification.

Will my Tally Prime install auto-update to the new rates?

No. Tally Solutions will publish a rate change template once CBIC notifies, but you have to apply the change in your Stock Item master (or via TDL bulk update). Do not assume an auto-update.

What happens to in-flight orders straddling the cutover?

The rate is determined by the date of the invoice, not the date of the order. An order placed September 10 but invoiced September 23 attracts the new rate. Build a customer-comms template for orders where the price changes due to the rate move — most notably AC / refrigerator orders moving from 28% to 18%, where the customer expects a refund of the difference.

Does the cutover affect my pending GSTR-1 for August?

No. GSTR-1 for August 2025 (due September 11) is filed under the current rate structure for transactions dated in August. The new rates apply to transactions dated September 22 onwards.

What about the compensation cess on autos and tobacco?

The cess on most products is being merged into the new 40% rate. The exception is unmanufactured tobacco, bidi, gutkha, pan masala, and similar — the cess stays separate. Confirm against the CBIC notification when it lands.

How does my POS app handle the rate change at the till?

Best case: your POS reads tax rate from a config table, you update the table, you are done. Worst case: rate is hardcoded in the receipt template, the price-tag print routine, or even the inventory display — three places to fix. Audit today, fix this week.

Will GST 2.0 affect my GSTR-3B filing for September?

The September 2025 GSTR-3B (due October 20, later extended to October 25 for Diwali) covers a tax period that straddles the cutover. Tally and Zoho Books will compute the tax correctly per invoice date, but verify line-by-line for any mid-September invoice that should have used new rates from the 22nd onwards.

Want a GST 2.0 readiness audit on your software stack?

We run a 90-minute audit on your Tally, Zoho Books, custom billing app, and POS integrations against the expected GST 2.0 rate restructure. You get a written remap plan, a list of hardcoded-rate fixes, and a fixed-scope quote if you want us to ship the changes. Suitable for SMBs in the ₹2 Cr to ₹50 Cr turnover band.

Book a GST 2.0 Audit

For the live cutover playbook on day one, our follow-up post on the GST 2.0 cutover at September 22 walks the same six-item checklist with notification numbers attached. Email contact@softechinfra.com if you want the audit checklist sent before our call.

Tags:
GST 2.0GST CouncilTallyPOSE-InvoicingIndian SMBCompliance
Share this post:
Softechinfra Editorial

Softechinfra Editorial

Articles published by Softechinfra without a personal byline.

How we pick topics, use AI, check claims and correct mistakes: our editorial policy.