F-29 — Post Customer Down Payment
F-29 is used to post a received customer down payment to the customer account using a special G/L transaction. It is most useful when customer advance cash has been received and must be recorded before final invoice clearing. 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-29 — Post 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· 605 words
Esta página aún no está disponible en español.
Purpose
post a received customer down payment to the customer account using a special G/L transaction. Treat F-29 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-29 is typically used when customer advance cash has been received and must be recorded before final invoice clearing. 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 received payment and customer.
- Use the special G/L indicator required by the configured process.
- Reference the relevant request or sales document where the process requires it.
- Simulate the posting and confirm bank/customer special G/L lines.
- Post and verify the customer item in FBL5N.
Key data objects
These are the fields and business objects that most often explain the result in F-29. 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.
- bank/cash posting — verify the exact value, validity/date context and relationship to the source document.
- special G/L indicator — verify the exact value, validity/date context and relationship to the source document.
- amount — verify the exact value, validity/date context and relationship to the source document.
- down-payment request/reference — 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-29 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 for S/4HANA Central Finance and payment scenarios references F-29 as the customer down-payment transaction. 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
- Posting to the normal receivables account instead of the configured special G/L flow. Reconcile the exact business document and date before applying a workaround.
- Using the wrong customer or reference. Reconcile the exact business document and date before applying a workaround.
- Ignoring tax/localization requirements for advances. 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-29ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.