SAP transaction codeObjectF-53ModuleFI_FICO

F-53 — Post Outgoing Payment with Clearing

F-53 posts a manual outgoing payment (bank to vendor or bank to GL account) and clears the selected open items in one step. It is a two-screen transaction: the bank line entry, then the open item selection screen where the assigned amount must net to zero against chosen invoices before the document can be saved.

This page covers F-53, the classic transaction for manually posting an outgoing payment and clearing vendor (or GL) open items in the same document. It focuses on the header-plus-open-item-selection mechanics, the tables the posting writes to, and the recurring reasons a clearing attempt fails to balance.

Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,137 words

What it does

F-53 records a payment leaving the company (bank credit) and simultaneously clears the vendor or GL open items that payment settles, producing a single accounting document with the offsetting bank and clearing lines already reconciled. The structural fact that drives most confusion: the transaction is really two screens glued together. The first screen captures the bank/GL posting line (account, amount, value date). The second, 'Process open items', is where the actual clearing happens - the system proposes open items for the account entered, and the document will not post until the sum of selected items, minus any cash discount, equals the amount entered on the first screen exactly. Anyone treating it as a single-screen entry transaction like FB60 will be confused by the difference field that refuses to hit zero.

When it is used

Used for one-off manual outgoing payments that do not go through the automatic payment program: petty cash disbursements, wire transfers confirmed after the fact by the bank, correcting a payment run's omission, or clearing a vendor debit balance manually. It sits at the bank reconciliation step of the AP process - after an invoice has been posted (FB60/FB70/MIRO) and before or alongside bank statement processing. Consultants reach for F-53 instead of F110 when there is a single payment to record rather than a batch run, and instead of FB60/FB50 when the goal is specifically to clear existing open items rather than just post a new document. It is also the fallback when electronic bank statement auto-clearing fails to match a payment and someone has to clear it by hand.

How to use it

  • Enter document date, posting date, company code, currency and the bank G/L account as the header/first line (posting key 50 for outgoing payment).
  • Enter the payment amount and value date for the bank line.
  • In the open item selection area, enter the vendor (or GL) account and account type, then trigger 'process open items'.
  • On the open item screen, select the invoices to clear; use partial or residual payment functions if the amount does not match the full invoice value.
  • Confirm the difference field shows zero, adjusting for cash discount or manual write-off lines if needed.
  • Simulate the document to check the debit/credit lines balance and the correct GL accounts are hit.
  • Post the document and note the clearing document number for reconciliation.

Key fields

  • BKPF - accounting document header for the payment posting (company code, document number, fiscal year).
  • BSEG - all line items of the payment document, including the bank line and the clearing lines.
  • BSIK - vendor open items; entries here move out once cleared by this posting.
  • BSAK - vendor cleared items; the invoice and the payment both appear here after clearing, linked by the clearing document number.
  • BSIS / BSAS - equivalent open/cleared item tables when the offsetting side is a GL account rather than a vendor.

How to prove it in the data

To confirm a payment cleared a specific invoice, check BSAK for the vendor account: the invoice line and the payment line should share the same AUGBL (clearing document number) and AUGDT (clearing date). Before clearing, the same invoice sits in BSIK with AUGBL blank. Cross-check BKPF for the payment document to confirm posting date and company code match what was reported, and pull BSEG for that document number to see the bank line and clearing line amounts split correctly.

ECC vs S/4HANA

F-53 still works unchanged on S/4HANA as a classic GUI transaction. BSIK and BSAK remain populated as compatibility views over the universal journal table, so the same selection logic and clearing behavior apply. There is no direct one-to-one Fiori replacement for manual ad hoc clearing of this kind; the newer clearing apps are oriented around bank statement matching rather than free-form manual payment entry, so F-53 remains the practical route for a genuinely manual, one-off payment.

Common pitfalls

  • Difference not zero: the most common stall. Usually caused by cash discount not calculating because the vendor terms of payment or tolerance group is missing, or because the user selected items whose total does not match the entered payment amount. Check the terms of payment on the invoice and the tolerance settings before assuming a fat-finger entry error.
  • Wrong or missing open items on the selection screen: selection is driven by account type and special G/L indicator; withholding tax or down payment items on special G/L indicators will not appear unless explicitly included, leading users to think the invoice is missing.
  • Partial versus residual confusion: partial payment leaves the original invoice open and creates a separate open item for the payment; residual clears the original invoice and opens a new item for the remaining balance. Picking the wrong one distorts vendor aging and duplicate-payment checks later.
  • Exchange rate handling: for foreign currency vendors, realized gain or loss lines depend on the exchange rate type and the rate as of posting date; a stale or missing rate produces an unexpected gain/loss line that throws off the difference field.
  • Bank clearing account configuration missing for the house bank used, which throws an error at the header screen before open items are even reached - a Basis/config issue, not a data one.
  • Reflex reversal: once a document is posted and cleared, fixing a wrong selection means reversing with FB08 rather than trying to repost over it; reversal re-opens the original items but can leave a residual cash-discount line that needs separate cleanup.

Whose problem this is

Functional AP or treasury accounting issue in almost all cases. ABAP involvement is rare and limited to custom open item selection logic via enhancement. Basis is only involved if a missing bank clearing account configuration or authorization object blocks the posting. A good handover includes company code, vendor or GL account, the invoice document number expected to clear, and the clearing document number if the posting already happened.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Source: ERPClimb — https://erpclimb.com/sap-tcodes/f-53ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.