Income-tax Act 2025 in SAP — remapping withholding tax keys before the quarterly statement goes in
SAP has no single fix for the Section 393 withholding tax remap. SAP Business ByDesign adds a Section 393 income-type dropdown to existing withholding tax codes (KBA 3735111); SAP S/4HANA Cloud Public Edition applies mandatory configuration via SAP Note 3773580, reached through KBA 3705622. On-premise S/4HANA and S/4HANA Cloud Private Edition have guidance too — KBAs 3702151, 3737702 and 3780432 — but only a preview is readable without an SAP S-user login, as of 12 November 2026. Confirm which KBA covers your product before touching a withholding tax code.
SAP has not published one remap for the Income-tax Act, 2025. It has published separate guidance for each of three product lines — SAP Business ByDesign, S/4HANA Cloud Public Edition, and on-premise S/4HANA together with S/4HANA Cloud Private Edition — and the guidance differs by product, not by disagreement between SAP's own sources. Here is what each actually says, where the on-premise chain still needs an S-user login, and the 194Q mapping the bare Act itself now settles.
Three SAP products, one deadline — the guidance for each, read directly
The Income-tax Act, 2025 (Act 30 of 2025) received Presidential assent on 21 August 2025 and came into force on 1 April 2026, repealing the 1961 Act outright under its own section 536(1) — no CBDT notification substituted anything; the repeal is the Act's own text. SAP's plainest description of what that does to withholding tax comes from its own support knowledge base: "Due to the introduction of the Income tax Act, 2025, all non salary withholding tax sections (194, 195, 196 series) will be consolidated into a new TDS section, Section 393" (SAP KBA 3735111). That single sentence is the clearest plain-English framing available from any SAP source — but it governs SAP Business ByDesign only. SAP has published separate guidance for its other two product lines too — S/4HANA Cloud Public Edition, and on-premise S/4HANA together with S/4HANA Cloud Private Edition — and the guidance differs by product because the configuration screens differ, not because SAP's own sources disagree with each other.
SAP's KBAs on this, as read 12 November 2026 (SAP revises and republishes these without a visible changelog, so re-check before acting on an older copy):
| KBA | SAP product | What it actually covers |
|---|---|---|
| 3735111 | SAP Business ByDesign, all versions | Config steps: a Section 393 income-type dropdown added to existing withholding tax codes |
| 3705622 | SAP S/4HANA Cloud Public Edition, all versions | No config steps itself — points to SAP Notes 3773580 (mandatory public-cloud configuration) and 3774399 (manual income-tax TDS/TCS data download), and to SAP's Regulatory Change Manager; lists KBA 3702151 under “See Also” |
| 3717443 | SAP S/4HANA Cloud Public Edition, all versions | A separate, narrower reclassification (manpower supply) — not part of the Section 393 remap itself |
| 3702151 (preview only) | SAP ERP Central Component, SAP ERP, SAP S/4HANA, SAP S/4HANA Cloud Private Edition and the ERP enhancement packages, all versions | “Impact of Indian Income Tax Act 2025 Amendments on Official Withholding Tax Keys” — symptom: all official withholding tax keys need to change; resolution text not visible without an SAP S-user login |
| 3780432 (preview only) | SAP ERP Central Component, SAP ERP, SAP S/4HANA, SAP S/4HANA Cloud Private Edition and the ERP enhancement packages, all versions | Troubleshooting a failed SNOTE implementation of SAP Note 3776054, named by KBA 3702151 as tied to the withholding-key remap |
| 3737702 (preview only) | SAP ERP, R/3, S/4HANA on-premise and enhancement packages (India/CIN localization), all versions | Confirms “Section 393(1)(8)(ii)” as a keyword against the old Section 194Q exemption logic; resolution gated behind login |
SAP Business ByDesign: the documented path
For ByDesign, KBA 3735111 gives an actual sequence. Before touching anything, the KBA states, verbatim, that entries should be fully booked "until 31st March 2025" — quoted exactly as SAP wrote it. That date reads as a likely typo for 2026, given the 1 April 2026 effective date stated everywhere else in the same KBA; confirm against your own tenant before relying on either date, and don't silently correct SAP's text for them. Then:
- Business Configuration work center → Implementation Projects → Open Activity List → Fine Tune.
- Open "Withholding Tax – India".
- Check Withholding Tax Codes, and for each code in use, select the applicable new Section 393 income-type subsection from the dropdown.
- Simulate a supplier invoice and confirm the income type shown on the withholding tax line matches what you selected.
- Post. Income-tax TDS returns and the certificate for entries up to 31 March 2026 still use the old forms; the renumbered certificate — SAP's KBA calls it "Form 131" — applies only to deductions made on or after 1 April 2026.
On that last point, SAP's own number is corroborated: under Rule 215 of the Income-tax Rules, 2026 (notified by G.S.R. 198(E), 20 March 2026, as amended), the certificate for non-salary deductions under Sl. No. 2 of the Rule 215(1) Table is Form 131, due within fifteen days of the Rule 219 statement's own due date — not a fixed calendar date, because it moves with the statement deadline. Cite the Rule for that, not the KBA's casual mention. The Rules were amended again by G.S.R. 830(E) (the Income-tax (Fifth Amendment) Rules, 2026, dated 22 September 2026, in force 1 October 2026) — that amendment touched Rule 215(1) Sl. No. 3 (Form 132), not Sl. No. 2 (Form 131), so the Form 131 citation above still stands as read, but cite Rule 215 as a whole "as amended" rather than as a single, static instrument, and check it hasn't moved again before you rely on it.
S/4HANA Cloud Public Edition: a note chain, not a wizard
KBA 3705622 does not give you steps directly — it names two further SAP Notes, plus SAP's Regulatory Change Manager, and tells you to go there. By number, since their content sat behind a login and could not be independently read for this article: SAP Note 3773580 (the mandatory public-cloud configuration changes) and SAP Note 3774399 (how to download quarterly income-tax TDS/TCS transactional data if you're filing the statement outside SAP); KBA 3705622 also directs readers to "Regulatory Change Manager for further updates and changes related to The Income-tax Act, 2025." It separately lists KBA 3702151 — the on-premise/Private Edition remap KBA, covered below — under "See Also", which is not the same as naming it as a step in this chain. Confirm the substance of both Notes and the Regulatory Change Manager guidance against your own S-user access before acting on them — this article can confirm they exist and what KBA 3705622 says they're for, not what they themselves say.
The dates KBA 3705622 gives for the surrounding government timeline — per SAP's own wording, not independently verified here: the Income Tax Department published FVU (File Validation Utility) data structures for the new quarterly forms on 19 June 2026, updated the file structure again on 30 June 2026, and the changes reached the Cloud Public Edition customer environment from 20 July. SAP's KBA does not state the year for that last date in the passage read for this article; it is almost certainly 2026 given everything else on the same timeline, but confirm the year in your own S-user session rather than assume it.
On-premise and S/4HANA Cloud Private Edition: the guidance exists, it's just gated
SAP's on-premise and Private Edition guidance is published, but only a preview is readable without an SAP S-user login. As read 12 November 2026, KBAs 3702151 and 3780432 are tagged for SAP ERP Central Component, SAP ERP, SAP S/4HANA, SAP S/4HANA Finance, SAP S/4HANA Cloud Private Edition and the ERP enhancement packages; KBA 3737702 is tagged for SAP ERP Central Component, SAP ERP, SAP R/3, SAP S/4HANA, SAP S/4HANA Finance and the ERP enhancement packages, and is not separately tagged for Private Edition. Don't carry forward a claim that on-premise has "no published remap walkthrough" from any source: it has three KBAs; they're just login-gated past the preview.
KBA 3702151, "Impact of Indian Income Tax Act 2025 Amendments on Official Withholding Tax Keys", states the symptom plainly: "all Official withholding tax key need to change" — SAP's own wording, quoted as written — once the Income-tax Act, 2025 takes effect on 1 April 2026. Its own example: "Section 194Q has been replaced by Section 1031." Read that number carefully: 1031 is not a section of the Act. It is the code Form 140 (Income-tax Rules, 2026) assigns to the s.393(1), Table, Sl. No. 8(ii) row covered in the next section — Form 140's own code table heads that column "Section Code", but it is a form-level reporting code, not a section of the Act sitting alongside 393 or 402. The KBA's resolution — the actual SNOTE/config steps for on-premise and Private Edition — is not visible without logging in; this article has not read it and does not assert what it says.
PREPARE_INVOICE_DATA, FILL_TDS_TAB and PROCESS_CREDITMEMO. The KBA's own title attributes the error to unmet prerequisites: a KSCHL (pricing condition type) field that only gets added once a prerequisite note is implemented, so implementing 3776054 out of sequence — or without that prerequisite — leaves KSCHL missing. Read this narrowly: it is one specific SNOTE-sequencing error reported against one note, not evidence of a general flaw in the remap. If you hit the same KSCHL error, check the prerequisite notes in Note 3776054's own "Related Notes" section before raising a fresh incident.KBA 3737702 — the one that names the 194Q-successor row — is covered on its own below, because the row it points at is now confirmed independently of the login-gated KBA.
The 194Q row: confirmed, not folklore
Old Section 194Q — income-tax TDS on purchase of goods — doesn't map onto a single new section by mere renumbering; under the consolidation it becomes one row inside Section 393(1)'s own Table, and the bare Act itself settles which row. s.393(1), Table, Sl. No. 8(ii) of the Income-tax Act, 2025 (Act 30 of 2025, pp. 403 and 425) covers "any sum exceeding fifty lakh rupees for purchase of any goods", payer described as "any person, being a buyer", rate 0.1%. Note 1(b) under the same table makes clear the ₹50 lakh figure is a threshold on the purchase amount, not on the buyer's turnover: tax is deducted "on the sum exceeding fifty lakh rupees" — so on ₹1 crore of purchases from one seller in the tax year, the deduction runs on ₹50 lakh of it, not the full ₹1 crore. Note 1(a) disapplies the row for any transaction on which tax is deductible or collectible under any of the provisions of the Act.
The Act separately defines who counts as a "buyer" for that row. s.402(6), Table Sl. No. 1, ties the obligation to a person whose total sales, gross receipts or turnover exceeded ₹10 crore in the tax year immediately preceding the one in which the purchase is made — the ₹10 crore figure is a turnover test on the buyer, separate from the ₹50 lakh purchase threshold in 393(1) Sl. No. 8(ii) itself. s.402(6) cross-refers back to "393(1) [Table: Sl. No. 8(ii)]", which is independent, internal confirmation that this is the right row — not an inference from a vendor dropdown or a blog's reading of the Act.
SAP's own KBA 3737702, "Exemption details handling for section 194Q after Income tax Act 2025 amendment", gives the same row in its symptom and keywords: "Concern on how exemption details should be used for section 194Q, (393(1)(8)(ii)) under the new changes" — SAP's own shorthand, in its symptom/keyword fields rather than necessarily verbatim in its title. The row number here is confirmed independently from the bare Act above, not from this KBA. What the KBA still gates behind an S-user login is the actual exemption-handling configuration — the 194Q exemption details (the KBA's keywords list exemption number, vendor data and thresholds) — and this article has not read that resolution text; confirm the configuration steps against your own SAP for Me access before relying on them.
A small, separate corroboration that Section 393(1)'s Table carries a numbered Sl. No. 8 with sub-clauses: Rule 219(1)'s own Table in the Income-tax Rules, 2026 prescribes Form 143 directly at Sl. No. 4 — the quarterly TCS statement, unrelated to 194Q — alongside Forms 138, 140 and 144 for the income-tax TDS statements, all in the same rule. Separately, that same Rule 219(1) Table routes "s.393(1) [Table: Sl. No. 8(iii)]" to Form 138 (the salary-statement ground), and routes the rest of s.393(1) — explicitly "other than Sl. No. 8(iii)" — to Form 140. That confirms Sl. No. 8 has at least a sub-clause (iii) distinct from (ii); it isn't, on its own, how this article knows (ii) is the 194Q-successor row — that comes directly from the Table text quoted above.
Don't conflate this with the separate manpower reclassification
KBA 3717443, for S/4HANA Cloud Public Edition, is a genuinely different fix that happens to land in the same tax year. The legal basis is Finance Act, 2026 (No. 4 of 2026), s.90(b) — not the Union Budget announcement, which isn't law by itself — inserting s.402(47)(f) into the Income-tax Act, 2025: "supply of manpower to a person to work under his supervision, control or direction" is added to the statutory definition of "work", in force from 1 April 2026 (Gazette of India, Extraordinary, Part II—Section 1, No. 9, dated 30 March 2026, CG-DL-E-31032026-271439, p. 58).
From 1 April 2026 this sits at s.393(1), Table, Sl. No. 6(i) of the Income-tax Act, 2025 — not "194C". That 1961-Act number governs only deductions on or before 31 March 2026; the manpower-supply reclassification only exists in the 2025 Act — in the definition of "work" at s.402(47)(f), which Sl. No. 6(i) picks up — so it doesn't reach anything still governed by 1961-Act numbering. The rates at Sl. No. 6(i) are 1% where the payee is an individual or HUF and 2% for any other payee, with thresholds of ₹30,000 per single sum or ₹1,00,000 aggregate in the tax year (Act 30 of 2025, p. 401).
A second, easy-to-blur distinction sits one sub-clause over: fees for technical services run at 2%, not 10% — Sl. No. 6(iii), column D, clause (a)(i), reported under Form 140 code 1026. Professional services are the 10% row — Form 140 code 1027. A vendor master that defaults every consultant invoice to one blended 10% "professional fee" row, including technical-services lines, is wrong before anyone even touches the Section 393 remap.
SAP's own KBA 3717443 still labels this with the 1961-Act numbers — "194C" for the manpower-supply reclassification, "194J" for the technical/professional-fee row it sits beside — because that's the shorthand SAP's documentation uses, not because 194C/194J is the numbering now in force. Read that as SAP's own wording, not as this article's framing of the operative law. If your vendor master still keys a manpower-supply line to a 194J-successor row — SAP's KBA warns specifically against "the higher 10% deduction" — or a technical-services line to the professional-fee rate, fix it under Sl. No. 6 of the Section 393(1) Table. SAP publishes this as a separate KBA, not as part of the main Section 393 remap, so don't assume the remap fixes it.
What a wrong key costs downstream
None of this is cosmetic. A wrong key is the kind of reference-data error a cash-level check cannot see: books and bank can agree to the rupee while the statement carries the wrong row. Where the Act itself bites is processing. Under s.399(1)(a)(ii) of the Income-tax Act, 2025, every TDS statement is processed after adjusting for "an incorrect claim apparent from any information in the statement", which s.402(3)(b) defines to include a claim in respect of a rate of deduction "not as per the provisions of the Act"; s.399(1)(e) then generates an intimation of the amount payable. So a row deducted at a rate the Act doesn't fix for the row reported comes back as an amount payable in the processing intimation, after the quarter has closed, not at month-end. A wrong row at the right rate need not trip that check at all, which is why the reconciliation below matters.
One more thing worth checking rather than assuming: where a withholding tax code is deleted and recreated rather than remapped in place, confirm the new code treats a separately-shown GST component the way the old one did. For services, the 1961-Act position is CBDT Circular No. 23/2017 (dated 19 July 2017): where the "GST on services" component is indicated separately in terms of the agreement or contract, tax is deducted on the amount without including it. That circular is about services; it does not speak to purchases of goods, so don't read it onto the 194Q-successor row (s.393(1), Table, Sl. No. 8(ii)). Whether it carries over unchanged under the 2025 Act depends on s.536(2)(j) of Act 30 of 2025, which deems a circular issued under the repealed Act to continue "so far as it is not inconsistent with the corresponding provisions" of the new Act. That's a judgement call for your CA to confirm against the recreated code — this article does not assert it carries over automatically.
The reconciliation none of these KBAs eliminate
Every path above — ByDesign's dropdown, the S/4HANA Cloud note chain, the on-premise/Private Edition KBAs, the 194Q row, the manpower-reclassification side-fix — changes configuration. None of it tells you, after the fact, whether every bill that should have picked up the new key actually did. That's a line-by-line reconciliation of the vendor master against the quarter's deductions, run exactly when it's most painful to do manually: right after a remap, when historical rows keyed under the old numbering and newly-keyed rows under Section 393 sit side by side in the same ledger, and a pivot table can't tell you which rows were actually touched by the config change versus which were silently skipped.
That reconciliation habit matters whichever ERP keys the deduction, SAP included. Recoup's own product reach, today, is narrower than an SAP vendor master: Payment Approvals computes the income-tax TDS section and amount at the point of approval for the 194C/194J/192 ground, per bill, and posts clean invoices straight to Zoho Books — it does not read or write an SAP vendor master, and it does not decide the new section numbers for you. If your AP flow runs through SAP, the remap above is work you do inside SAP itself; what Recoup removes is the separate, manual, per-invoice judgement at approval for whatever routes through Zoho instead — so a corrected vendor-master row stops needing to be reapplied, bill by bill, by whoever happens to process that vendor's next invoice.
Stop re-keying TDS at approval — for whatever posts through Zoho
Recoup computes the income-tax TDS section and amount at approval, per bill, from your vendor master — so a corrected master propagates automatically instead of depending on invoice-by-invoice memory. It doesn't touch an SAP vendor master or Section 393 configuration; the remap above is still SAP work.
See Payment Approvals →Related guides
TDS reconciliation after the Income Tax Act 2025
The business side of the same remap — what changed in the section numbers, forms and vendor master, ERP-agnostic.
GSTR-2B reconciliation in SAP
What SAP's inward-reconciliation module auto-matches, and what still needs a human decision.
Setting up e-invoicing (IRN) in SAP
The certificate step most SAP-GSP implementations skip.
GST reconciliation: the 2026 guide for finance teams
The other monthly reconciliation your vendor master has to stay honest for.