unapplied cash in AR keeps growing while customers show open invoices that were already paid by check
Fixes unapplied cash in AR that keeps growing while customers show open invoices already paid by check: match the cheque payments sitting in unapplied cash to the invoices they settled, repair the remittance matching process, and clear the backlog. Use for AR cash application. Not for genuinely disputed invoices under active resolution.
TL;DR
The money arrived and the invoices are still open, so the payments are almost certainly sitting in the unapplied cash balance, parked there because the cheque remittance did not match cleanly at entry: no invoice number on the cheque stub, a customer name variant, or a payment keyed to the parent account. Pull the unapplied cash detail and the open invoice list for the same customers and match them in bulk - amounts, cheque numbers in the bank deposit detail and dates usually resolve most pairs in minutes. Apply each payment properly, then fix the intake: require remittance references on the deposit record, and run an unapplied cash review weekly so the balance cannot quietly rebuild behind the AR team's back.
unapplied cash in AR keeps growing while customers show open invoices that were already paid by checkUse this when
- The AR unapplied or suspense cash balance grows month over month.
- Customers complain or statements show invoices open that the customer insists were paid by cheque.
- Cheque payments are entered before remittance advice is matched, as a two-step process.
Not for this skill when
- Invoices are open because the customer disputes them. Those belong in dispute management, not cash application.
- Payments cannot be found anywhere in the ledger. That is a bank deposit recording problem upstream of AR.
Steps
- Age and detail the unapplied cash balance by customer and receipt date, and pull open invoices for the same customers. Verify: both populations are listed side by side with amounts and dates
- Match payments to invoices using amount, cheque number from bank deposit detail, and payment date proximity, starting with exact amount pairs. Verify: the clear pairs are identified and the ambiguous residue is separated
- Apply each confirmed payment to its invoices and confirm the customer balance afterwards reflects reality. Verify: invoices close and the unapplied balance falls by the applied amounts
- For the ambiguous residue, contact customers with a specific list: cheque number, date and amount, asking which invoices they intended. Verify: each residual payment gets a documented allocation or a genuine dispute flag
- Change the process: capture remittance references at deposit entry and review unapplied cash weekly with an ageing threshold. Verify: the new review exists and the balance trend reverses in the following month
Variant phrasings
unapplied cash growing customers invoices already paid by check
The paired symptom in one search.
AR unapplied cash reconciliation match payments to open invoices
The backlog-clearing phrasing.
cheque payment not applied invoice still open remittance missing
The intake-cause variant.
Compatibility: Accounts receivable cash application in SAP, Oracle, NetSuite, Dynamics and QuickBooks, including lockbox, cheque and manual receipt entry.
Why it happens
Cash application has two halves: recording that money arrived, and deciding what it settles. Under time pressure, teams record the deposit to keep the bank rec moving and defer the allocation, parking the receipt as unapplied. Cheques make deferral easy because their remittance information lives on paper stubs outside the system. Each deferral is individually reasonable; collectively they build a growing liability balance while the AR ledger accuses good customers of not paying, damaging both the balance sheet and customer relationships.
Edge cases / pitfalls
- Unapplied cash can conceal misdirected payments meant for another entity; confirm the paying company before applying across group customers.
- Old unapplied balances sometimes must be recognised under unclaimed property rules; involve the controller before writing anything off.
- Customer statements should exclude invoices under confirmed payment matching, or dunning will chase paid bills.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_sBzNwkQpOmtaSN1i3q5XbA