F-39 — Clear Customer Down Payment
F-39 is used to clear customer down-payment special G/L items against the final customer receivable. It is most useful when the final invoice exists and the customer advance should be applied to it. Start with the exact organizational keys, business document and date, then reconcile the resulting SAP document or status before changing master data or configuration.
Verified practitioner reference for F-39 — Clear Customer Down Payment. The page covers purpose, when to use it, practical execution, the key business data to capture, how to prove the result, S/4HANA context, common mistakes, ownership and related SAP objects.
Published 19 Sept 2026· 587 words
Esta página ainda não está disponível em português.
Purpose
clear customer down-payment special G/L items against the final customer receivable. Treat F-39 as one step in an end-to-end process. Values shown or posted here are usually driven by master data, organization, dates and preceding documents, so an accurate diagnosis starts by preserving those inputs rather than changing the symptom screen first.
When it is used
F-39 is typically used when the final invoice exists and the customer advance should be applied to it. It is also valuable in project and regression testing because it provides a repeatable business state. In production, use the narrowest document or organizational selection that answers the question and capture the before-state before any posting, clearing or configuration change.
How to use it in practice
- Confirm the final customer invoice and down payment belong together.
- Select the correct special G/L down-payment item.
- Select the target invoice/open item.
- Review clearing amount, tax and residual difference.
- Post and verify both items are cleared correctly.
Key data objects
These are the fields and business objects that most often explain the result in F-39. Record them in support evidence so the next person can reproduce the same outcome.
- customer/company code — verify the exact value, validity/date context and relationship to the source document.
- down-payment item — verify the exact value, validity/date context and relationship to the source document.
- invoice/open item — verify the exact value, validity/date context and relationship to the source document.
- clearing date — verify the exact value, validity/date context and relationship to the source document.
- difference/tax effects — verify the exact value, validity/date context and relationship to the source document.
How to prove it in the data
Use document flow and chronology. Start from the source business event, inspect the F-39 document or master data, then follow the resulting accounting, purchasing or asset document and reconcile amount, quantity, account assignment and status. A correct proof uses the same company code or plant, business date, document keys and currency/unit context at every step.
ECC vs S/4HANA
SAP documentation recommends F-39 for customer down-payment clearing in relevant S/4HANA scenarios. Where S/4HANA offers a Fiori successor or a changed data model, the classic transaction can still be valuable for support, but the strategic process and clean-core guidance should govern new implementations.
Common pitfalls and how to diagnose them
- Clearing a down payment against the wrong invoice because amounts match. Reconcile the exact business document and date before applying a workaround.
- Using F-32 when the process specifically requires down-payment clearing behavior. Reconcile the exact business document and date before applying a workaround.
- Ignoring posting-period/tax consequences of the clearing date. Reconcile the exact business document and date before applying a workaround.
Whose problem this is
Primary ownership is the Finance/Controlling team, with adjacent teams involved when the evidence crosses into Asset Accounting, Project System, tax, Basis, Security or integration. Escalate with document numbers, organization, dates, 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-39ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.