Cash Application

Cash application is the accounting process of matching each payment a company receives to the specific customer invoices it settles, and then recording that match in the books so the invoices are closed and the customer's balance is reduced. It turns a bank credit such as "$48,500 received from Customer X" into precise entries against the right open items in accounts receivable.

Cash application sits between treasury and accounting. Treasury sees the money arrive through balance reporting; the receivables team decides what it pays for. It is a form of payment reconciliation on the incoming side, and it is distinct from bank reconciliation, which checks that the cash balance in the ledger agrees with the bank statement as a whole.

Imagine a landlord with twenty tenants. Money lands in the bank all month, some tenants pay two months at once, some pay a bit short because of a repair they arranged themselves, and one pays from a relative's account. At the end of each week the landlord has to tick off which rent each payment covers, so that nobody is chased for money they already paid.

A business does the same, but with thousands of customers, invoices and payments. Without that ticking-off, the books show customers owing money they have paid, collectors chase the wrong people, and the company cannot tell how much cash is really outstanding.

A typical cash application cycle follows these steps:

1. The payment arrives by ACH, wire, card, direct debit, cheque or a lockbox service in which a bank collects and scans customer cheques.
2. The remittance information is gathered. This is the customer's note of which invoices are being paid. It may travel with the payment, arrive separately by email or a supplier portal, or be missing altogether.
3. The payment is matched to open invoices by amount, invoice number, customer reference or account.
4. Differences are resolved: short payments, deductions, disputed items, early-payment discounts taken, or unidentified receipts.
5. The match is posted to the receivables subledger, which updates the general ledger.

The basic journal entry for a fully matched $10,000 receipt is simple:

If the payment cannot be identified, it is usually posted to a suspense or "unapplied cash" account until someone works out who sent it. If a customer pays $9,800 against a $10,000 invoice and claims a 2% discount, the $200 difference is posted to discounts allowed if the claim is valid, or left open as a deduction to be disputed.

Most of the difficulty lies in remittance data. In the United States, Nacha's corporate ACH formats carry it in addenda records: a CCD+ entry carries one addenda record with an 80-character field, while a CTX entry can carry up to 9,999 addenda records formatted in the ASC X12 820 standard. Wires and international transfers carry structured or free-text remittance fields, and ISO 20022 messages provide dedicated structured remittance fields that make automatic matching easier when both sides use them.

Companies use several tools to raise their automatic match rate:

• Virtual accounts. Giving each customer its own virtual account number identifies the payer from the receiving account alone.
• Matching rules. Software in the ERP system or a specialist tool matches on exact amounts, invoice numbers found in free text and combinations of invoices that add up to the payment.
• Machine learning. Some tools learn from past manual matches, for example that one customer always quotes purchase-order numbers rather than invoice numbers.

Performance is commonly measured as:

If 8,500 out of 10,000 payments in a month are matched without human work, the rate is $\frac{8{,}500}{10{,}000} \times 100\% = 85\%$; the remaining 1,500 go to an exceptions queue.

Slow or inaccurate cash application has knock-on effects across the business:

• Collections. Customers who have paid may be chased or put on credit hold, while those who have not paid are missed.
• Cash conversion. Days sales outstanding and the cash conversion cycle look worse than they are, and working capital reports are wrong.
• Forecasting. Treasury's cash forecasting depends on knowing which invoices remain open.
• Close. Unapplied cash must be cleared or explained at each financial close, and large suspense balances draw auditors' attention.

Cash application also has a control role. Payments received from unexpected accounts, overpayments followed by refund requests, and frequent changes in payer details can be signs of payment fraud or money laundering, so receivables teams usually have rules on how refunds of overpayments are approved and to which account they may be sent.

• Nacha
• ISO 20022