FB05 — Post with Clearing
FB05 is used to post a Financial Accounting document and clear selected open items in the same transaction. It is most useful when a payment, adjustment or other posting must be linked immediately to customer, vendor or G/L open items. 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 FB05 — Post with Clearing. 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· 622 words
Purpose
post a Financial Accounting document and clear selected open items in the same transaction. Treat FB05 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
FB05 is typically used when a payment, adjustment or other posting must be linked immediately to customer, vendor or G/L open items. 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
- Enter document header data and the new posting line.
- Choose the account type and account whose open items should be processed.
- Use additional selections such as document or reference number to narrow the open items.
- Match items and resolve any permitted difference according to policy.
- Post and verify the clearing document and cleared-item references.
Key data objects
These are the fields and business objects that most often explain the result in FB05. Record them in support evidence so the next person can reproduce the same outcome.
- company code — verify the exact value, validity/date context and relationship to the source document.
- document/posting date — verify the exact value, validity/date context and relationship to the source document.
- clearing account — verify the exact value, validity/date context and relationship to the source document.
- open-item selection — verify the exact value, validity/date context and relationship to the source document.
- difference and clearing document — 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 FB05 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 documents FB05 as a standard posting-with-clearing transaction in S/4HANA as well as classic FI. 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 items only because their amounts net to zero. Reconcile the exact business document and date before applying a workaround.
- Selecting open items from the wrong account or company code. Reconcile the exact business document and date before applying a workaround.
- Using clearing to hide an unresolved upstream allocation problem. 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/fb05ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.