FTXP — Maintain Tax Codes
FTXP is used to create or maintain country-specific tax codes and their tax percentages/accounting behavior. It is most useful when implementing tax configuration or investigating whether a tax code is valid for a legal/tax procedure. Start with the exact organizational keys and business date, then prove the result from SAP documents, balances or logs before changing configuration or reposting data.
This page explains FTXP — Maintain Tax Codes — from a consultant's point of view: what it changes or displays, when it belongs in the process, which keys matter, how to prove the result, and the mistakes that create avoidable reconciliation work.
Published 19 Sept 2026· 601 words
Esta página aún no está disponible en español.
Purpose
create or maintain country-specific tax codes and their tax percentages/accounting behavior. The transaction should be read in the context of the full accounting or logistics flow: source document, organizational assignment, posting date, configuration and resulting document all matter. A technically successful save is not enough; the output must reconcile to the intended business event.
When it is used
FTXP is typically used when implementing tax configuration or investigating whether a tax code is valid for a legal/tax procedure. In project testing it is equally useful for proving configuration and master data with a controlled example. In production, narrow the scope first and capture the before-state so any posting, clearing, settlement or master-data change can be reconciled afterward.
How to use it in practice
- Confirm the company-code country and assigned tax procedure.
- Use an approved tax code design and naming convention.
- Maintain rates/conditions and review calculated tax behavior.
- Coordinate account determination with Finance/Tax.
- Test representative AP, AR and MM/SD postings.
Key data objects
These are the fields and business objects that usually explain the result in FTXP. Capture them in test evidence and incident handovers, because a mismatch in company code, plant, fiscal period, account or reference document is often more important than the screen message itself.
- country — verify the exact value, validity/date context and source of derivation.
- tax code — verify the exact value, validity/date context and source of derivation.
- tax procedure — verify the exact value, validity/date context and source of derivation.
- tax percentage/condition — verify the exact value, validity/date context and source of derivation.
- input/output tax behavior — verify the exact value, validity/date context and source of derivation.
How to prove it in the data
Prove the result end to end: identify the source document/master record, inspect the transaction's proposal or status, then open the resulting accounting or logistics document and reconcile amounts, quantities and account assignments. Use document flow, line-item displays and master-data history with the same fiscal period and organizational scope. That distinguishes a true configuration defect from a selection, timing or historical-data difference.
ECC vs S/4HANA
Tax-code maintenance remains relevant in S/4HANA, although localization and tax engines may add external determination layers. On S/4HANA, Universal Journal, Business Partner, Material Ledger or Fiori may change the preferred analysis surface, but the business control behind the transaction still has to be understood and tested.
Common pitfalls and how to diagnose them
- Creating a tax code without tax-team approval. Reconcile the exact document and period before making a configuration change.
- Copying another country's code and assuming procedure logic is identical. Reconcile the exact document and period before making a configuration change.
- Changing a productive tax rate without effective-date and compliance analysis. Reconcile the exact document and period before making a configuration change.
Whose problem this is
Primary ownership is Finance/Controlling, with Basis or ABAP involved only when runtime, authorization or custom-code evidence points there. A useful escalation includes the business document, organizational keys, posting/valuation date, expected accounting result and the exact mismatch already proven.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ftxpERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.