Incoming payment processing records money received and determines which customer receivable it settles. Where a trustworthy match exists, cash posting and invoice clearing may happen together. Where the payer or invoice is unclear, the receipt needs an identified exception path rather than an arbitrary match.
Two separate facts: cash and settlement
A bank credit proves funds arrived; it does not by itself prove which customer invoice has been settled. The accounting process must recognize the receipt in the correct bank or clearing account and handle the customer open item according to the remittance evidence. A payment reference, amount, currency and value date are useful, but not always sufficient to identify a transaction.
Manual entry and statement-supported processing
SAP S/4HANA offers incoming-payment processing with and without electronic bank statements, depending on the business setup. Users can post a payment and search for candidate open items. Electronic statement processing can automate routine matching while routing exceptions to review. The exact screens and automation available vary by deployment and configuration.
Decide whether an invoice can be cleared
A clean match uses payer identity, invoice number or structured reference, amount and valid clearing criteria. Where the document is not certain, an accountant may need to post on account or use an approved interim treatment, then apply the money later. An incorrect clearance can make collections reports look healthy while leaving the real unpaid invoice open.
An illustrative accounting entry
For a customer who pays an open 11,800 invoice in full, a simplified illustration debits the appropriate bank or bank-clearing account by 11,800 and credits the customer by 11,800, with the open invoice and payment cleared under the applicable process. A bank statement might later reconcile the interim bank clearing balance. Cash discounts, exchange differences and fees require separate treatment.
What to do with differences
A short payment can represent a legitimate discount, a disputed charge, a partial payment, or an unidentified deduction. SAP functions may support partial and residual items, reason codes, and assignment to open items. Treat those choices as controlled accounting decisions: collect evidence, apply company policy, and avoid silently writing off a balance merely to force a match.
Design a better exception queue
Group exceptions by unknown payer, missing invoice reference, duplicate receipt, mismatched currency, potential discount or wrong-bank booking. Assign an owner and aging threshold to each. Operations should monitor unapplied receipts, customer reconciliations and bank clearing accounts at a consistent cutoff; unresolved amounts need escalation before period close.
Consultant questions worth asking
Which file or banking channel delivers remittance data? What identifiers do customers actually provide? Who owns unmatched cash, and what is the approved write-off limit? Is auto-clearing accurate enough to trust? Those practical questions reveal whether master data, payment formats, integration or process ownership is the real bottleneck.
Read next
Customer Invoice Accounting; Customer Credit Memo Accounting; Automatic and Manual Clearing; Open-Item Management. Return to the SAP FI / FICO hub.