What is unapplied cash in AR and how do I clear it?
Unapplied cash is a customer payment that's been received and recorded, but not yet matched to a specific open invoice — it sits in a clearing or unapplied-payments balance instead of reducing a receivable. It's cleared by identifying which invoice(s) the payment is actually for and applying it; until that happens, it inflates cash while AR aging still shows the invoice as fully open.
By Zuny Fester, Head of Operations and MarketingPart of the accounts receivable and collections guide.
| What it is | A recorded payment not yet matched to a specific open invoice |
|---|---|
| Where it lives | A clearing or unapplied-payments account, separate from the customer's invoice-level detail |
| Why it happens | Missing or ambiguous remittance detail, a payment that doesn't match any open invoice amount, or a payment received before the invoice was issued |
| What it distorts | AR aging (the invoice still shows as fully open) and cash forecasting (cash looks collected but isn't tied to what it satisfies) |
| How it clears | Identifying the correct invoice(s) via remittance detail, customer confirmation, or amount-matching, then applying the payment |
Why a received payment can still be "open"
Recording a payment and applying it to a receivable are two different steps. NetSuite's own documentation on the customer payment process distinguishes exactly this: a payment can be received and recorded in the system while remaining unapplied — the money exists, but it isn't yet tied to any specific invoice. Until it's applied, the invoice it's actually meant to satisfy still shows as fully open on an aging report, even though the cash has already arrived.
Why payments end up unapplied in the first place
The most common cause is missing or ambiguous remittance information — a wire or check arrives with no invoice number, or a payment amount that doesn't cleanly match any single open invoice (a lump sum, a partial payment, or an amount that's the sum of two invoices minus a small deduction). A payment can also arrive before the corresponding invoice is even issued, common with deposits or prepayments, which has nothing to apply against yet by definition.
What unapplied cash actually distorts
Two things go wrong simultaneously. AR aging overstates how much is genuinely outstanding, because an invoice that's actually been paid still reads as open until the match happens — a stale aging report full of unapplied-but-collected invoices makes collections effort look worse than it is and can trigger unnecessary dunning on an account that's already paid. Cash forecasting has the opposite problem: cash that's arrived looks available, but until it's matched, nobody can confirm with certainty which specific obligation it actually discharges, which matters when reconciling against what was expected to be collected in a given period.
How to actually clear it
Clearing unapplied cash means identifying the invoice or invoices the payment is genuinely for and applying it — via remittance detail attached to the payment, matching the payment amount against open invoice amounts (including combinations that sum to the payment), or contacting the customer directly when neither produces a confident match. Left unresolved, unapplied cash doesn't self-correct; it accumulates, and the longer it sits, the harder it gets to trace back to the right invoice as remittance records age out or go missing.
Next step
Map the finance workflow with the most exposure and prove the automation path.
Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.
Worked example
$9,400 sitting unapplied for three weeks while its invoice ages
A wire for $9,400 arrives on the 3rd of the month with no remittance advice attached — just a bank reference number. It's recorded as a customer payment but held unapplied because no invoice number is provided. Meanwhile, invoice #4471 for exactly $9,400 continues aging on the AR report: 7 days past due on the 3rd, 14 days by the 10th, 21 days by the 17th — triggering a dunning reminder at the 14-day mark for an invoice the customer has, in fact, already paid.
On the 24th, a follow-up call to the customer's AP contact confirms the wire was for invoice #4471. The payment is applied, closing the invoice and correcting the aging report retroactively for reporting purposes — but the three weeks of unnecessary dunning, and the three weeks the aging report overstated genuinely open AR by $9,400, already happened and can't be undone. Matching on amount alone (a $9,400 payment against a $9,400 open invoice) would have closed this the same day the wire landed, without needing the customer call three weeks later.
Frequently Asked Questions
Sources
Related
Topic
AR & Collections
Accounts receivable is the money customers owe a business for goods or services already delivered on credit — a current asset on the balance sheet until it's collected. AR and collections, as a practi…
Read moreDiagnostic
How do I handle partial payments and split invoices in cash application?
Apply a partial payment against the specific invoice the customer intended, leaving the remainder open rather than closing the invoice or creating an unexplained credit. When one payment is meant to cover multiple invoices (a split payment), allocate it line by line using the remittance detail; if no allocation is specified, apply oldest-invoice-first is the most common default rule.
Read moreDiagnostic
How do I handle a customer short-payment, deduction, or chargeback on an invoice?
First classify the deduction — valid claim (damaged goods, pricing error, an agreed promotion) versus unauthorized short-pay. Valid claims get coded to the right expense/contra-revenue account and closed out; unauthorized ones get disputed and either recovered or written off. Applying the payment before classifying the gap creates unapplied-cash and aging problems downstream.
Read moreDiagnostic
How do I match a lump-sum remittance to many open invoices?
Match against the remittance detail that comes with the payment — a BAI2 lockbox record, an EDI 820 advice, or a remittance email listing invoice numbers — rather than guessing how a lump sum splits. When that detail is missing, fall back to amount-combination matching, and treat any leftover as its own item to resolve, not force-fit into an invoice it doesn't match.
Read more