F-54 — Clear Vendor Down Payment
F-54 is used to clear a vendor down payment against the supplier's final invoice. It is most useful when the supplier invoice has been posted and an earlier vendor advance must 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-54 — Clear Vendor 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· 593 words
Esta página aún no está disponible en español.
Purpose
clear a vendor down payment against the supplier's final invoice. Treat F-54 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-54 is typically used when the supplier invoice has been posted and an earlier vendor advance must 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
- Display the final invoice and down-payment item first.
- Select the correct vendor and special G/L transaction.
- Match the down payment with the intended invoice.
- Review tax, local-currency and difference effects.
- Post and verify the vendor items and clearing document.
Key data objects
These are the fields and business objects that most often explain the result in F-54. Record them in support evidence so the next person can reproduce the same outcome.
- vendor/company code — verify the exact value, validity/date context and relationship to the source document.
- down-payment special G/L item — verify the exact value, validity/date context and relationship to the source document.
- supplier invoice — 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.
- tax/difference handling — 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-54 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 continues to reference F-54 for vendor down-payment clearing, including 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 the wrong down payment because the supplier has several advances. Reconcile the exact business document and date before applying a workaround.
- Ignoring localization-specific tax effects. Reconcile the exact business document and date before applying a workaround.
- Using the clearing to compensate for an incorrect invoice value. 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-54ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.