F-32 — Clear Customer Open Items
F-32 is used to manually clear customer open items such as invoices, credit memos and payments. It is most useful when customer items must be matched outside automatic incoming-payment or clearing processes. For reliable support work, start with the exact system, client, user and business context, then use the transaction's own status, document or log evidence before changing configuration or data.
This practitioner page covers F-32, Clear Customer Open Items. It explains the transaction's operational purpose, the evidence to capture, the data or configuration objects that matter, and the failure patterns that commonly mislead SAP support teams.
Reviewed by an ERPClimb SAP consultant on 19 Sept 2026· 671 words
Purpose
manually clear customer open items such as invoices, credit memos and payments. The useful way to think about F-32 is as part of an end-to-end business or technical flow, not as an isolated screen. Capture the exact organizational context, business object, user and timestamp before drawing conclusions, because those values determine which data and configuration the transaction reads.
When it is used
F-32 is typically used when customer items must be matched outside automatic incoming-payment or clearing processes. It is also valuable during test cycles because it provides a repeatable way to prove what SAP processed, selected or rejected. In production, narrow the selection to the affected population first and separate diagnostic/display actions from functions that can post, retry, clear or change system state.
How to use it in practice
- Confirm the customer and company code from the bank/remittance evidence.
- Select the relevant open items and compare amounts, references and dates.
- Choose residual, partial payment or difference handling according to accounting policy.
- Post the clearing document.
- Verify cleared items in FBL5N and customer balance after posting.
Key data objects
These are the strongest anchors for a F-32 investigation. Record the values in the incident or test evidence so another consultant can reproduce the same conclusion and distinguish master data, configuration, authorization and transaction-state problems.
- customer — verify the exact value, organizational context and relationship to the affected document or interface.
- company code — verify the exact value, organizational context and relationship to the affected document or interface.
- clearing date — verify the exact value, organizational context and relationship to the affected document or interface.
- open items — verify the exact value, organizational context and relationship to the affected document or interface.
- residual/partial payment handling — verify the exact value, organizational context and relationship to the affected document or interface.
How to prove it in the data
Use a three-part proof: first establish the source document or request and its exact keys; second show the status, accounting/interface record or runtime evidence produced by SAP; third show the corrected result using the same selection. Cross-check neighboring transactions and logs rather than relying on a single screen message. This prevents a successful retry, changed selection or unrelated master-data edit from being mistaken for the real fix.
ECC vs S/4HANA
Customer manual clearing remains standard accounting functionality on S/4HANA, with Fiori alternatives available in many deployments. Availability does not automatically mean it is the preferred design for new work. On S/4HANA, pair familiar SAP GUI diagnostics with Fiori apps, Universal Journal, ODP, RAP/CDS or released APIs where those are the strategic surface for the process.
Common pitfalls and how to diagnose them
- Clearing the wrong invoice because amounts happen to match. Recheck the exact keys and chronology before changing configuration or reposting data.
- Using residual-item handling without understanding aging and reference impact. Recheck the exact keys and chronology before changing configuration or reposting data.
- Clearing across customers through a workaround instead of fixing the payment allocation. Recheck the exact keys and chronology before changing configuration or reposting data.
Whose problem this is
Primary ownership normally sits with the FI FICO team. Bring in Basis for infrastructure/runtime issues, Security for authorization evidence, and ABAP or integration developers only when the transaction evidence points to custom logic or mapping. A useful escalation includes exact keys, timestamp, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/f-32ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.