FI Global Settings Withholding Tax: Classic vs EWT and the Changeover Process

Book: Financial Accounting in SAP S/4HANA Finance Simplified: Questions & Answers
Author: Narayanan Veeriah
ISBN: 978-93-65898-675

Chapter 13 is all about withholding tax. The tax your customer deducts from your invoice before paying you. Or the tax you deduct from a vendor before paying them. Veeriah spends most of the chapter on Extended Withholding Tax (EWT) because classic withholding tax is basically legacy at this point.

The withholding tax framework

In countries like the US, UK, India, Argentina, and Brazil, the customer (invoice recipient) withholds tax from the vendor (service provider) and remits it to tax authorities. The vendor is liable, but collection happens at source.

Example: $1,000 tax due, customer withholds 20% ($200), vendor pays the remaining $800. Overpayment gets refunded.

Self-withholding tax flips it: the vendor deducts and pays directly. India’s self-assessment tax works this way.

Names vary: “withholding tax” in the US, TDS in India. US companies file 1099 and 1042-S forms with the IRS.

Classic vs extended withholding tax

Classic withholding tax (pre-R/3 4.0) only handles AP-side calculation per invoice line. Limited.

Extended withholding tax (EWT) handles both AP and AR views, multiple withholding types per line, accumulation, min/max amounts, certificate numbering, rounding rules, and posting at invoice or payment time (including partial payments).

Countries that legally require EWT: USA, Argentina, Brazil, Colombia, Mexico, Peru, Venezuela, EU countries, UK, India, Philippines, South Korea, Thailand, and more.

If you need federal and state reporting in the US, EWT is not optional.

Per company code, you pick classic or EWT. SAP recommends EWT everywhere.

EWT configuration groups

Five IMG groups:

1. Basic settings - country/region IDs, withholding tax keys
2. Calculation - types for invoice/payment posting, formulas, min/max amounts
3. Company code - assign types to company codes, activate EWT
4. Posting - tax G/L accounts
5. Reports - certificate numbering

Key customizing tasks:

• Withholding tax country/region ID - may differ from political ISO codes, used for form printing
• Withholding tax keys - official names per tax authority (India has keys per Income Tax Act section; US has 50+ keys for 1099/1042-S reporting)
• Withholding tax types - control calculation logic (separate definitions for invoice posting S_ALR_87003264 and payment posting S_ALR_87003266)
• Withholding tax codes - percentage rates, posting type (standard or offsetting entry), reporting info
• Formulas - base amount, rate, currency, validity date per header
• Certificate numbering - four concept options for assigning number ranges

EWT process flow (AP view)

1. Enter invoice with withholding tax data per line
2. If invoice-time posting is configured, system calculates and posts WHT per type/code
3. If payment-time only, system calculates base but waits for payment
4. On payment, system reduces invoice by WHT and posts
5. Automatic payment proposals recalculate WHT if you change open item selection
6. Display WHT data on clearing line items after posting

AR view works in reverse: your customers withhold from payments to you.

Country quirks: Brazil, Spain, Philippines post WHT at invoice. Italy and Argentina post WHT as offsetting expense without reducing the invoice amount.

Master data and document entry

Three key document fields: withholding tax code, base amount, and exempted amount.

Maintain WHT type and code on the business partner master (vendor/customer, company code area). System defaults the code during entry. Field visibility comes from posting key and reconciliation account field status.

Exemption reasons (2-digit IDs) handle temporary or permanent WHT exemptions. US examples: 03 (income not from US source), 04 (tax treaty exempt), 12 (chapter 4 withholding). Enter on the vendor master with certificate number, exemption percentage, and validity dates.

Recipient types group vendors by occupation for different rates under the same WHT type. Used for US 1042-S reporting.

Certificate numbering

Four EWT numbering concepts:

1. Numbering class per company code
2. Per company code + withholding tax type
3. Per company code + branch + withholding tax type
4. Per company code + account type + place of business + recipient type

Define numbering class, numbering groups, and assign to company code/country.

Changing from classic to EWT

Withholding tax changeover is a one-way street. Once EWT is active, you cannot go back.

Prerequisites:

• Upgrade to R/3 4.0+ (or ECC/S/4HANA) if still on older versions
• Switch to Logistics Invoice Verification (LIV), not classic invoice verification
• Test conversion in a non-production system first
• Block user access during conversion (weekend project)
• Activate EWT only when the system prompts

Process in three phases:

Preparation: financial accounting comparative analysis, archive cleared items (saves massive processing time), complete EWT customizing matching classic settings, set up F_WTMG authorizations, block users.

Data conversion: create conversion run, select company codes, map classic codes to EWT types/codes, run analysis, convert customizing (test run first), convert master data and documents, activate EWT.

Postprocessing: manually transfer exemption data to vendor masters, define reunification tax as separate WHT type, re-enter recurring entry docs, sample docs, and noted items that did not convert, release system for users.

Traffic lights on the conversion run screen track progress. Green = done. Yellow = warnings. You cannot redo a completed step.

Previous: FI Global Settings Tax on Sales and Purchase Chapter 12 | Next: FI Global Settings Inflation Accounting Chapter 14