SAP's FV11 records don't know the rate changed on 22 September 2025 — and which document date SAP reads decides whether they find out
SAP has no automatic cut-over for a GST rate change. SAP's public KBA 3653105 (S/4HANA Cloud Public Edition) sets out four steps — tax codes valid from 22/09/2025 via SSCUI 101016, material tax classification, tax condition records closed at 21/09/2025 and re-created from 22/09/2025, and tax G/L accounts. Its siblings for SAP ERP and S/4HANA (3652860, and the FAQ 3658122) keep their resolution behind an SAP for Me login, though their public keyword lists name FV11/FV12. Which rate actually applies to a given supply is a separate question, governed by the six clauses of Section 14 of the CGST Act — not a simple before/after split. Whether an open PO priced before the change still calculates the old rate depends on which date your configuration reads when the invoice posts, and on which tax code the PO carries, so test it before you trust it.
The 56th GST Council's rate rationalisation took effect on 22 September 2025 — new tax codes, new condition records, a new rate on a long list of goods and services. SAP doesn't learn a new rate on its own. Until someone maintains new tax codes and condition records, nothing in the system carries the 22 September rates, and documents created before the change can keep calculating the old ones, depending on which date your configuration reads.
What actually changed, and on what date
The 56th GST Council met on 3 September 2025 and recommended collapsing the then four-tier rate structure — 5%/12%/18%/28% — into one built mainly around two slabs, 5% and 18%, with a separate 40% special rate kept for a short list of de-merit and luxury goods and services. The Ministry of Finance's own FAQ on the decision, PIB Press Release ID 2163560, states the new rates on goods and services would take effect from 22 September 2025 — except for cigarettes, chewing tobacco (zarda), unmanufactured tobacco and beedi, which stayed on the existing GST and compensation-cess rates, with the new rates to be implemented "at a later date to be notified". Secondary sources report pan masala and other manufactured tobacco products were also carved out and moved only later, via a notification reported effective 1 February 2026 — that specific date is not independently confirmed here, so treat it as reported, not settled.
The implementing instrument on goods is widely reported as Notification 9/2025-Central Tax (Rate), dated 17 September 2025. This article attributes the 22 September effective date to the Ministry's own FAQ above, not to the notification's text — the notification itself wasn't independently read for this piece.
This is the largest mid-year GST rate restructuring since GST began in 2017, but it is not the first time an annual return has had to straddle a GST rate change inside one financial year — the November 2017 cut of 178 headings from 28% to 18% fell mid-FY2017-18 too, and that year's reconciliation had the same before/after split to manage.
Section 14: a six-clause matrix, not a before/after split
The trap in many rate-change explainers, including one widely circulated PIB handout, is collapsing Section 14 of the CGST Act into "supply before the change, invoice or payment after it, means the new rate applies." A sentence shaped exactly like that — supply before, invoice or payment after, revised rate — is wrong: two of the three sub-cases it describes are actually old-rate outcomes under the statute, not new.
Section 14 actually runs six clauses, split by whether the supply itself happened before or after the rate changed, then by which of invoice date and payment date governs:
| Supply timing | Invoice / payment pattern | Rate that applies | Governing date |
|---|---|---|---|
| Before the change | Invoice and payment both after | New | Earlier of invoice date / payment date — s.14(a)(i) |
| Invoice before, payment after | Old | Invoice date — s.14(a)(ii) | |
| Payment before, invoice after | Old | Payment date — s.14(a)(iii) | |
| After the change | Invoice before, payment after | New | Payment date — s.14(b)(i) |
| Invoice and payment both before | Old | Earlier of invoice date / payment date — s.14(b)(ii) | |
| Invoice after, payment before | New | Invoice date — s.14(b)(iii) |
Three clauses land on the new rate and three on the old. In every case the rate follows the date the clause names, not the supply date alone.
Two mechanical details that trip up a date-field comparison: a payment is only "received" on the earlier of the date it's entered in the supplier's books of account or the date it's credited to the bank account — not the bank-credit date alone — and if that bank credit lands more than four working days after the rate change, the payment date reverts to the bank-credit date regardless of when it was booked. Neither of those is a field SAP's standard pricing or billing screens surface as "the Section 14 date" — someone has to apply the test manually, or build it as a custom check.
What SAP's own KBAs actually tell you to touch
SAP published three knowledge base articles around the September 2025 Council decision. All three open with the same symptom paragraph; 3653105 covers S/4HANA Cloud Public Edition and is fully public, while the other two cover SAP ERP, S/4HANA and S/4HANA Cloud Private Edition and keep their fixes behind a SAP for Me login:
| SAP KBA | Product | What's visible without a SAP for Me login (as of 6 November 2026) |
|---|---|---|
| 3653105 | S/4HANA Cloud Public Edition | Public KBA, full resolution visible, four steps: (1) modify existing tax codes in SSCUI 101016 "Define Tax Codes for Sales and Purchases" (role SAP_BR_BPC_EXPERT): set Valid From = 22/09/2025 and change the rate at the condition type; (2) material tax classification in Manage Product Master Data; (3) tax condition records, closing the existing record at Valid To = 21/09/2025 and creating new entries from 22/09/2025 with the updated tax codes (worked example 18% to 5%, CGST and SGST each 9% to 2.5%); (4) tax G/L accounts for new tax codes via SSCUI 101871. Its note says new tax codes are to be created wherever a tax rate changes. |
| 3652860 | SAP ERP, S/4HANA, S/4HANA Cloud Private Edition | Symptom only, the same paragraph as 3653105, ending "SAP systems must be updated to reflect the revised GST rates to ensure compliance in Logistics processes (Purchasing, Sales & Distribution, Inventory Management)." Keyword list names MM02, MM17, MASS, VK11, VK12, VK31, VK32, FV11, FV12, MEK1, MEK2, MEK31, MEK32, FTXP, OB40, VF01, VA02, ME22N, MIRO, CNV_OT_TB and the TAXINN procedure. Cause and resolution sit behind login. |
| 3658122 | SAP ERP, S/4HANA, S/4HANA Cloud Private Edition (FAQ) | Symptom only, the same paragraph: 22 September 2025 and "goods (excluding pan masala and tobacco products)". Its keyword list names "GST MIRO posting date", "SAP ME11 pricing date", "GST tax calculation MIRO", "SAP open sales order tax code" and "service rendering date". The answers sit behind login. |
Don't read "all three KBAs cover the same change" as "all three prescribe the same fix." 3653105's confirmed resolution is written for Public Edition: its steps run through SSCUIs (101016, 101871) and apps such as Manage Product Master Data, not the transaction codes 3652860's keyword list names. 3652860's keyword list — material tax classification (MM02/MM17/MASS), transaction codes spanning purchasing conditions (MEK1/MEK2/MEK31/MEK32), sales pricing (VK11/VK12/VK31/VK32), tax-code maintenance (FTXP), condition records (FV11/FV12), GL determination (OB40), and the sales-order, purchase-order, billing and invoice-verification documents that use them (VA02/ME22N/VF01/MIRO) — tells you the surface area is wide, not that one step closes it. The full cause-and-resolution text for 3652860 and 3658122 sits behind SAP for Me; treat the fix shape for those two as the documented surface area, not a transcription of SAP's own steps, and confirm the exact sequence against the live KBA for your release before changing config in a production client.
The open-PO trap
None of the three KBAs' public text says which date SAP uses to pick the GST condition record on a document that straddles the change: the PO's pricing date, the invoice or posting date in MIRO, or on the sales side a services-rendered date. That is the question SAP's FAQ KBA 3658122 is keyed to. Its public keyword list names "GST MIRO posting date", "SAP ME11 pricing date", "GST tax calculation MIRO", "SAP open sales order tax code" and "service rendering date", but the answers sit behind the SAP for Me login. So don't assume it either way. The case to test is a PO raised in August, still open on 22 September and invoiced in October. If your configuration reads the PO's original pricing date, MIRO can calculate the rate that expired in September even though the invoice is dated October; if it reads the invoice date, it picks up whichever record is valid on the invoice date, which is the new rate only if that record was updated as below. Run one such PO through MIRO in a non-production client, compare the GST it calculates with the rate valid on the invoice date to see which date your configuration reads, then re-price in ME22N wherever SAP's figure differs from the rate Section 14 gives that supply. Also check which tax code your open POs carry: KBA 3653105's step 1 modifies existing tax codes from 22/09/2025, while its note says new tax codes are to be created wherever a tax rate changes.
Condition-record validity windows matter as much as the rate itself. For S/4HANA Cloud Public Edition, KBA 3653105 (step 3) is explicit: close the existing tax condition record with Valid To = 21/09/2025, and create new entries with Valid From = 22/09/2025 assigned to the updated tax codes. On SAP ERP, S/4HANA and Private Edition the equivalent records are maintained in FV11/FV12, both named in KBA 3652860's keyword list. 3653105's step 3 also runs through sales and purchasing pricing apps, not tax condition records alone, and 3652860's keyword list likewise names VK11/VK12 and MEK1/MEK2. That KBA's own steps sit behind login, so confirm the sequence for your release, and what happens to a document that still points at a closed record or a superseded tax code, against the full KBA or your own IMG review before changing a production client.
What it costs the recipient's ITC if nobody catches it
A supplier who doesn't update their own SAP (or any) pricing before 22 September keeps charging the pre-change rate — say, an item that moved from 18% to 5%, the worked example SAP itself uses in KBA 3653105. That overcharged invoice still flows into the buyer's GSTR-2B at whatever figure the supplier declared in GSTR-1 — 2B mirrors the supplier's filing, built from what the supplier reported rather than any check that the rate was right for the goods (Rule 60(7)) — unless you reject it or mark it pending in IMS; a record you take no action on is deemed accepted. Relying on the 2B rupee figure as proof the ITC claimed is correct is not the same thing as confirming it against the correct rate.
The fix on the supplier side is a credit note under Section 34 of the CGST Act, adjusting the original invoice's tax down to the correct rate — not a fresh invoice at the new rate. From the October 2025 tax period, the first tax period after the one this rate change fell in, GSTN's IMS changes (set out in GSTN's FAQ on the October 2025 IMS changes, current as of 6 November 2026) let a recipient keep a credit note "Pending" for one tax period (a month for monthly filers, a quarter for quarterly filers), and declare the specific amount of ITC to reduce, including nil if the credit was never availed or was already reversed. After that one period it must be accepted or rejected, and a record left with no action is deemed accepted into GSTR-2B. That window is useful for cases like this, but only if you mark it: don't accept a credit note into your books faster than you can confirm which invoice, and which rate error, it's actually correcting. Where the rate moved the other way — up, for a line item that landed on the 40% special rate — the supplier must issue a debit note instead (s.34(3)). A debit note is declared in the return for the month it is issued, with no outer time limit (s.34(4)). A credit note is different: it must be declared by the earlier of 30 November after the end of the financial year of the supply and the date the supplier files that year's annual return (s.34(2)). For supplies made between 22 September 2025 and 31 March 2026, that window closes on 30 November 2026 at the latest, and sooner for any supplier who has already filed GSTR-9 for FY 2025-26 (as of 6 November 2026). The recipient's ITC on a debit note is still time-limited by Section 16(4), counted from the debit note's own financial year.
Where this leaves reconciliation, not just repricing
Fixing FV11/FV12 and the SSCUI tax-code dates is what lets documents post at the new rate — in KBA 3653105's own words, its steps "will allow you to post documents with new tax rates". That is not the same as every document being right: a supply made before 22 September whose payment was also received before it, but which was invoiced after it, still takes the old rate under s.14(a)(iii). And it does nothing for what already posted — every open PO that invoiced at the old rate, every supplier invoice that landed in your 2B at a rate the new slab structure doesn't support, and every invoice raised before 22 September for a supply and payment that both came after it (new rate, s.14(b)(i)) has to be found, checked against the Section 14 test above and, where the rate is wrong, taken up with the supplier or actioned in IMS, one line at a time. That's the same invoice-level matching SAP's own GSTR-2B reconciliation screens hand back to a person rather than resolving automatically, and it compounds with anything already wrong in your e-invoicing setup — an IRN generated off a stale condition record carries the wrong tax amount into the e-invoice itself, not just the accounting entry.
Finding every invoice that posted on the wrong side of 22 September, across however many open POs and SOs were live on that date, is exactly the kind of work that's painful to do manually: it's not a date filter, it's a line-by-line check against the Section 14 test above, repeated for every document that straddled the change. Recoup reconciles your books against IMS and GSTR-2B invoice by invoice, so where the tax you booked and the tax your supplier filed disagree, that invoice shows up as a named mismatch — not a bucket total that quietly nets out — before you file. It doesn't decide which rate Section 14 required: where you and your supplier both applied the same stale rate, the two sides agree, and the Section 14 check above still has to be run against the dates.
Find the invoices where your books and your suppliers' filings disagree — before you file
Recoup reconciles your books against IMS and GSTR-2B for every GSTIN, invoice by invoice, and names the vendor behind every gap before you file.
Book a demo →Related guides
GSTR-2B reconciliation in SAP
What SAP's own documentation says its GST inward-reconciliation module automates, and what still needs a human.
SAP e-invoicing and IRN setup
Getting IRN generation working per GSTIN inside SAP — the eDocument-to-GSP configuration most implementations get wrong.
GST reconciliation: the 2026 guide for finance teams
The four reconciliations that decide your input tax credit, ERP-agnostic.