Direct answer

Cash application is the process of identifying a customer receipt and matching its value to the correct open receivables, so the invoices are cleared accurately. SAP FI can use references, payer identification, remittance advice, amounts, processing rules and manual review. When evidence is insufficient, Finance should investigate or post according to an approved on-account process rather than clear an unrelated invoice simply because amounts happen to match.

Follow the money and the open item

An invoice creates a customer open item. The bank statement or incoming-payment entry brings evidence that funds arrived. Cash application connects those records to determine which receivable has been settled. This link affects aged debt, customer statements, collections decisions and financial reconciliation. A correct bank balance alone does not prove that customer invoices were matched correctly.

What evidence makes a match reliable?

Begin with payer identity and bank account, payment reference, invoice number, amount, currency, value date and any remittance advice. Verify the relevant customer account and open-item status. A remittance may cover several invoices or include a discount, deduction or credit. A matching amount without the correct customer and invoice context is not reliable evidence of settlement.

Standard SAP processing versus optional automation

SAP's bank statement process can import items and apply configured posting and reprocessing rules; unmatched items may require investigation. SAP Help also describes a separately licensed SAP Cash Application capability that can use machine learning for matching proposals. Do not assume the additional service is enabled in every SAP deployment. The controls and results depend on product edition, configuration and data quality.

Accounts Receivable and Treasury colleagues compare bank receipt information with open invoices and remittance advice.
Finance tests payer, invoice reference and amount before reducing the open balance.

Worked example: a receipt with multiple invoices

Suppose a customer transfers ₹85,000 with a remittance identifying invoices of ₹50,000 and ₹35,000. If the payer, reference, currency and posted items align, Finance may clear both invoices using the permitted processing method. Without a remittance, the same value could match other combinations or another customer. The analyst should seek evidence rather than let a plausible arithmetic total determine the clearing decision.

When a payment differs from the invoice

A short payment could reflect an agreed cash discount, deduction, bank charge, dispute or an incorrect remittance. An overpayment may require an on-account balance or a separate resolution. SAP Help documents options for posting incoming payments, clearing items and handling residual items; the treatment of differences depends on relevant posting rules, reason codes, tolerances and approved business controls.

Exception ownership and controls

Treasury or the bank reconciliation team confirms receipt evidence; Accounts Receivable owns allocation and open-item review; Sales or Customer Service may help identify deductions and disputes. Define authority to approve write-offs, discounts, reclassifications and unmatched cash handling. Track unresolved bank items and avoid silent or forced clearing. Retain traceability from bank transaction to accounting document to original invoices.

Payment matching scorecard covering customer identity, remittance references, amounts and the final clearing or exception decision.
A matching scorecard prevents one plausible amount from replacing full evidence.

Why unapplied cash matters

Unallocated receipts make collections and customer balance reporting unreliable. Customers may be chased for invoices they have paid while bank receipts remain unresolved. Repeated exceptions can indicate poor invoice references, inaccurate master data, missing remittance transmission or ineffective matching rules. Review both outstanding customer items and unprocessed bank statement items rather than optimizing only automatic match percentage.

Consultant questions to ask

Which banks and formats provide incoming-payment data? What identifies the payer? Are remittance files received? How many invoices can one payment cover? What happens to payment differences, foreign currencies and intercompany receipts? Which roles approve manual postings? What reconciliation evidence proves invoices were actually settled? Test real exception patterns before deciding whether more automation is valuable.

Related SAP FI concepts

Review incoming payment processing, automatic and manual clearing, customer invoice accounting and customer payment terms. Return to SAP FI / FICO.

Official SAP References