FY 2025-26's annual return spans two GST rate regimes. Here is where that actually bites.
FY 2025-26's annual return has to carry the GST rate rationalisation that took effect on 22 September 2025 for most goods and services (tobacco products are a separate, later boundary), so GSTR-9's Table 17 may report the same HSN code at two different tax rates within one return where the item was sold on both sides of that date -- part of the wider GST reconciliation exercise. Table 17's HSN-wise summary already carries a "Rate of Tax" column built for exactly this -- the fix is one more row per HSN per rate, not a blended average. Which side of 22 September a given sale actually falls on is decided by Section 14's time-of-supply rule -- a six-way test on the supply, invoice and payment dates, not a single field.
Most GSTR-9s you have filed covered a financial year where the GST rate on a given HSN code was the same in April and the same in March. FY 2025-26 mostly isn't that year. The 22 September 2025 rate rationalisation sits inside it -- a far wider mid-year restructuring than the November 2017 cuts -- which means a lot of HSN codes carry two different rates in the same annual return.
Why this FY 2025-26 return is genuinely different
The 56th GST Council met on 3 September 2025 and recommended collapsing the then four-tier rate structure -- 5%, 12%, 18% and 28% -- into a structure built mainly around two slabs, 5% and 18%, with a separate special rate of 40% for a short, specifically-listed set of de-merit and luxury goods and services. The Ministry of Finance's own FAQ on the Council's decisions states the effective date directly: "the changes in GST rates on services and goods other than cigarettes, chewing tobacco products like zarda, unmanufactured tobacco and beedi will be effective from 22nd September, 2025. For the specified goods namely, cigarettes, chewing tobacco products like zarda, unmanufactured tobacco and beedi, the existing rates of GST and compensation cess will continue to apply and the new rates will be implemented at a later date to be notified." The change on goods was carried through Notification No. 9/2025-Central Tax (Rate), dated 17 September 2025.
Scale is still what makes FY 2025-26's annual return a genuinely bigger reconciliation job than most years'. A business selling the same product across April–March 2025-26 may have genuinely charged 12% up to 21 September and 5% from 22 September on the identical HSN code, in the identical financial year, in the identical annual return -- and this year that is true for a much wider slice of the rate schedule than an ordinary year's handful of notified changes.
Which side of 22 September a transaction actually falls on
The instinct is to split everything by invoice date: invoices up to 21 September carry the old rate, invoices from 22 September carry the new one. That instinct is wrong often enough to matter, in both directions. Section 14 of the CGST Act governs the rate that applies when a supply straddles a rate change, and it is a six-way test on the relative timing of the supply, the invoice and the payment -- it depends on which side of the change the supply itself fell, and then on which of the invoice or the payment came first.
In substance, Section 14 provides: where the supply was made before the change, (i) invoice and payment both after the change → time of supply is whichever of the two dates is earlier (so the new rate); (ii) invoice before the change but payment after → time of supply is the invoice date (the old rate); (iii) payment before the change but invoice after → time of supply is the payment date (the old rate). Where the supply was made after the change, (i) payment after the change but invoice before → time of supply is the payment date (the new rate); (ii) invoice and payment both before the change → time of supply is whichever is earlier (the old rate); (iii) invoice after the change but payment before → time of supply is the invoice date (the new rate). A proviso fixes "date of receipt of payment" as the bank-credit date only if that credit lands more than four working days after the change -- otherwise, and in every other case, it is whichever is earlier of the date the payment is entered in the books or the date it is credited to the bank.
| Supply relative to 22 Sep | Invoice vs payment | Time of supply is... | Rate |
|---|---|---|---|
| Before | Invoice and payment both after | Earlier of the two dates | New |
| Before | Invoice before, payment after | Invoice date | Old |
| Before | Payment before, invoice after | Payment date | Old |
| On/after | Payment after, invoice before | Payment date | New |
| On/after | Invoice and payment both before | Earlier of the two dates | Old |
| On/after | Invoice after, payment before | Invoice date | New |
The two rows that break a naive "just look at the invoice date" heuristic are rows 3 and 4. Row 3: supply happened before 22 September and payment was also received before it -- an advance, or payment on delivery -- but the invoice was only raised afterwards; an invoice-date-only check would wrongly call this the new rate, when it is actually the old one, fixed by the payment date. Row 4 is the mirror image: supply happened on or after 22 September and payment also landed on or after it, but the invoice had already been raised beforehand; invoice-date-only bucketing would wrongly call this the old rate, when the payment date actually fixes it at the new one. Both shapes are ordinary in practice: row 3 is a payment-before-billing workflow (an advance, or cash-on-delivery, followed by a delayed invoice); row 4 is an advance invoice raised ahead of time, with both payment and delivery following later.
Where this lands on the return: Table 17's HSN summary
FORM GSTR-9's Table 17, the HSN-wise summary of outward supplies, has carried a "Rate of Tax" column since the form was first notified -- it is not a new field added for this year. Its columns are HSN code, UQC, total quantity, taxable value, rate of tax, and the tax amounts by head. An amendment to the form's instructions in force from FY 2021-22 (Notification 30/2021-CT) separately made the HSN digit level mandatory -- six digits for taxpayers with turnover above Rs 5 crore in the preceding year, four digits for B2B supplies for taxpayers up to Rs 5 crore. That amendment is about how many digits of the HSN code you report, not about rate, and it is unrelated to the dual-rate question this article is about.
Because rate of tax is already its own column, an HSN code sold at both 12% (pre-22 September) and 5% (post-22 September) in the same year simply needs two separate rows in Table 17 for that code -- one per rate -- not one row with a blended average rate or a single consolidated taxable value. The form's own instructions say "Table 12 of FORM GSTR-1 may be used for filling up details in Table 17" -- if those filings (monthly, or quarterly under QRMP) correctly split the taxable value by the rate actually in force each period, Table 17 is a straightforward roll-up. If any period's GSTR-1 instead reported the wrong rate for a transition-period invoice -- the Section 14 trap above -- that error carries straight into the annual return's HSN summary, and has to be caught here; the underlying liability itself still needs fixing through the proper channel (a GSTR-1/GSTR-1A amendment within the Section 37(3) window, or DRC-03 for any shortfall), not by editing the figure directly in GSTR-9.
And on GSTR-9C: the rate-wise liability table fills in differently
If your turnover crosses the GSTR-9C threshold, the dual-rate year shows up again in Part III of that form -- Table 9, titled in the form itself "Reconciliation of rate wise liability and amount payable thereon." Table 9 is a fixed set of pre-printed rate rows, not a table you add lines to -- a business that charged both the old 12%/28% rates before 22 September and the new 5%/18% rates after it is simply filling in more of those existing rows than a year without a rate change would. Any gap between what Table 9 computes and what was actually paid still has to be explained in Table 10's reasons, the same as any other unreconciled rate-wise difference.
Whether the form's pre-printed rows have a dedicated line for the new 40% special rate is not something we have confirmed -- Notification 13/2025-CT (dated 17 September 2025, in force 22 September 2025) added only one new Table 9 row (for e-commerce-operator liability under Section 9(5)) and did not touch the rate rows themselves. If your business has 40%-rate supplies, check the notified form or the portal directly for where that liability actually goes, rather than assuming a row exists.
A worked example
A distributor sells an HSN code that moved from 12% to 5% on 22 September 2025. Four transactions near the boundary, each tagged to its own clause above:
| Transaction | Supply date | Invoice date | Payment date | Rate charged |
|---|---|---|---|---|
| A | 15 Sep (before) | 15 Sep (before) | 18 Sep (before) | 12% -- entirely before the change; no Section 14 question arises |
| B | 18 Sep (before) | 25 Sep (after) | 26 Sep (after) | 5% -- supply before, invoice and payment both after: new rate, by the earlier of the two post-change dates |
| C | 19 Sep (before) | 26 Sep (after) | 20 Sep (before) | 12% -- supply before, payment before (20 Sep), invoice after: old rate, fixed by the payment date -- an invoice-date-only check would wrongly call this 5% |
| D | 24 Sep (after) | 19 Sep (before) | 25 Sep (after) | 5% -- supply after, payment after (25 Sep), invoice before: new rate, fixed by the payment date -- an invoice-date-only check would wrongly call this 12% |
Transactions C and D are the pair that actually matter for a reconciliation built on invoice-date buckets -- they are exactly the two rows where that shortcut gets the rate backwards. Both shapes are common: C is a payment-before-billing workflow, where an advance or on-delivery payment arrives before 22 September but the formal invoice is only raised afterwards; D is an advance invoice raised ahead of time, with payment and delivery both following later. Either wrong bucket shows up twice -- once in the monthly GSTR-1/GSTR-3B for that period, and again when Table 17 rolls up the year and the rate-wise total doesn't match what GSTR-9C's Table 9 expects against the audited books.
Where Recoup fits
Catching a Transaction-C- or Transaction-D-shaped error means checking all three dates -- supply, invoice, payment -- against Section 14's rule for every transaction that falls within a few weeks of 22 September 2025, not just eyeballing invoice dates in a spreadsheet. Doing that by hand, invoice by invoice, for every supplier and customer touching that window, so the mismatch surfaces before it reaches the annual return rather than being caught cold at GSTR-9C time, is exactly the kind of invoice-level reconciliation that doesn't scale past a few hundred transactions done manually.
Recoup doesn't decide which rate applies to a given transaction -- that is a Section 14 judgement your own team or advisor makes. What it does is carry every flagged mismatch between your books, your filed returns and your bank forward to whoever has to resolve it, so a transition-period rate error doesn't sit undiscovered until the annual return forces the question.
Don't find your rate-change errors at GSTR-9C time
Recoup carries every unresolved reconciliation flag forward through the year, so a transition-period mismatch surfaces when it happens, not when the annual return is due.
See how Recoup reconciles →