What is cash application?
Cash application is the process of matching an incoming customer payment to the specific open invoice (or invoices) it settles, then posting that match in accounts receivable so the invoice's balance is reduced or closed. It depends on remittance data — an invoice number, a customer reference, or a payment portal that already links the payment to an invoice.
Part of the payment reconciliation and cash application guide.
| What it matches | An incoming payment to the open invoice it settles |
|---|---|
| What it depends on | Remittance data — an invoice number, reference, or portal link |
| Where it's applied | The accounts receivable subledger |
| What happens without a match | The payment sits as unapplied cash until resolved |
Why this step exists
Receiving money is only half the job — accounts receivable needs to know which specific invoice that money paid off, so the customer's account and the company's aging report both reflect reality. Without cash application, a company would know it has cash but not know which customers still owe money and which are paid up, which makes collections, forecasting, and the aging report all unreliable.
What good remittance data looks like
A payment carries an invoice number in its memo or ACH addenda record, arrives with a separate remittance advice, or is made through a payment portal that already ties it to an invoice. When none of these are present, matching falls back to amount and customer name — reliable until two invoices share an amount, which is where most cash application exceptions come from.
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
A payment with and without remittance data
A $1,200 ACH payment arrives with the memo "INV-4021". Cash application matches it instantly to invoice 4021, closes it, and the aging report updates automatically. A second $1,200 payment arrives the same day from a different customer with no memo at all, and that customer happens to have two open invoices, one for $1,200 and one for $800. This one can't be auto-matched with confidence — it goes into the exception queue for a person to confirm with the customer which invoice was intended, exactly the kind of gap that reliable remittance data prevents.
Frequently Asked Questions
Sources
Related
Topic
Payment Reconciliation & Cash Application
Payment reconciliation is the process of proving that every dollar that hit your bank account is accounted for somewhere in your books — matched to a deposit, a payout, an invoice, or an explained var…
Read moreDefinition
What is payment reconciliation?
Payment reconciliation is the process of proving that every payment that hit your bank account is accounted for in your books — matched to a deposit, a payout, an invoice, or an explained variance. It has two layers: bank reconciliation, which ties the bank statement to the general ledger, and cash application, which ties each individual payment to the invoice it settles.
Read moreHow-to
How does automated cash application work?
Automated cash application matches incoming payments to open invoices using deterministic rules first (exact amount plus invoice number or customer ID), then fuzzy or confidence-scored matching for near-misses, routing anything unresolved to an exception queue for a person to confirm. The result is applied straight to the AR subledger without manual lookup for the majority of payments.
Read more