FICO Tax Configuration Part 1: Tax Procedures, Tax Codes and Why They Matter
Every invoice needs correct tax. Learn how SAP calculates taxes: the tax procedure assigned to a country, tax codes that carry rates and account keys, input vs output tax, and how tax lines post to GL accounts automatically — the foundation for VAT/GST compliance.
What this complete series covers
Learn Tax Configuration in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.
- Who it is for
- Best for SAP consultants, developers, and learners who want a practical understanding of Tax Configuration.
- Prerequisites
- Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
- Final outcome
- By the end, you should be able to explain Tax Configuration clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.
- Part 1: FICO Tax Configuration Part 1: Tax Procedures, Tax Codes and Why They Matter
Understand the business and technical purpose of SAP tax configuration, the role of tax procedures and tax codes, and the master data that drives correct tax calculation on every transaction.
- Part 2: FICO Tax Configuration Part 2: Configuring Tax Codes, Conditions and Accounts End to End
Walk through the practical configuration steps to build a working tax code, assign G/L accounts through automatic account determination, and trace how tax amounts post during document entry.
- Part 3: FICO Tax Configuration Part 3: Tax Determination in Sales and Purchasing
Explains how tax codes are determined at document entry, how condition-based tax procedures calculate tax amounts, and how those amounts are automatically posted to the correct GL
System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.
Explanation
📌 KEY POINTS
✅ A tax procedure (calculation schema) is assigned to each country; it lists tax condition types and account keys.
✅ Tax codes (per country) define tax type (input/output) and rates; they are entered or determined on invoices.
✅ Account keys (e.g. VST input tax, MWS output tax) link tax lines to GL tax accounts (OB40).
✅ Input tax is usually recoverable; output tax is owed to authorities.
⚠️ Changing rates on a tax code already used can distort historical documents — create new codes with validity instead.
━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: Tax procedures and tax codes
Part 2: Configuring codes, conditions and accounts end to end
Part 3: Tax determination in SD/MM and automatic GL assignment
━━━━━━━━━━━━━━━━━━━━
▶ 1. TAX PROCEDURE
- Country-specific calculation procedure.
━━━━━━━━━━━━━━━━━━━━
▶ 2. TAX CODES
- Type (V input / A output), rate, account key.
━━━━━━━━━━━━━━━━━━━━
▶ 3. TAX ACCOUNTS
- Account key → GL account per chart of accounts.
━━━━━━━━━━━━━━━━━━━━
▶ 4. POSTING
- Invoice creates tax line automatically.
━━━━━━━━━━━━━━━━━━━━
▶ 5. REPORTING
- Tax returns from posted tax lines.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Check the tax procedure for your country.
- Display a tax code in FTXP.
- Post an invoice and check the tax line account.
✅ CHECKPOINT: you can trace tax from code → rate → account key → GL account.
Code example
===== CONFIG MAP =====Tax procedure assignment to country ... OBBGTax codes ............................. FTXP (tax type V/A, rate %)Tax accounts .......................... OB40 (account key → GL)Tax on sales/purchases settings ....... OBCN, OBYZ (per requirement) ===== POSTING EXAMPLE (input tax 18%) =====Dr Expense 1,000 | Dr Input tax 180 (VST → 154000) | Cr Supplier 1,180Real project scenario
A mid-size manufacturer changed the rate on an existing tax code during a VAT change. Reprinted old invoices showed the new rate and tax reports mixed periods. The team created new codes for the new rate and blocked old codes after the transition.
Common mistakes
- Changing rates on used codes.
- No tax code matrix.
- Wrong account keys.
- Manual tax lines.
- Ignoring tax team sign-off.
Best practices
- New codes for rate changes.
- Maintain a signed matrix.
- Validate account keys.
- Automatic tax calculation.
- Involve tax experts.
Interview angle
Questions: "What is a tax procedure?", "How does a tax code find its GL account?", "Input vs output tax?"
Strong answer: procedure per country, tax codes, account keys and OB40, posting and reporting.
Practice this lesson
Quick check
1. What links a tax line to its GL account?
2. Interviewers commonly ask candidates to explain the relationship between a tax procedure, a tax code, and a condition type, and to describe the difference between input and output tax from a posting perspective. In the Tax Configuration context, which answer shows the strongest practical judgment?
3. A team wants to change the rate on an existing tax code for a VAT change. Why is this risky?
Interview questions
1. What are the core concepts of Tax Configuration, and how would you explain them clearly in an SAP interview?
Answer it in your own words first, then compare.
2. A manufacturer's tax returns don't match expectations. Explain how SAP calculates and posts tax, and where you'd look.
Answer it in your own words first, then compare.
Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.