A customer pays you. The money lands in your bank account. But until someone links that payment to the right invoice, your books still say the customer owes you money, and your collections team may still be chasing it. Cash application is the step that closes that gap. This guide explains what it is, where it goes wrong, and how to match payments to invoices accurately.
What is cash application?
Cash application is the accounts receivable process of matching incoming payments to the open invoices they settle, then recording the result in your ledger. When it is done well, customer balances are correct, aging reports can be trusted and nobody receives a reminder for an invoice they already paid.
What is unapplied cash?
Unapplied cash is money you have received but not yet matched to any invoice. It sits on the account as a credit, often under a generic heading. Some of it is unavoidable, for example a prepayment or a deposit. Much of it is simply a payment with missing or unclear information. The goal is not zero unapplied cash at every moment, but a small balance with clear ages and owners, cleared quickly.
The matching process step by step
1. Collect payment and remittance data
Remittance data is the information that explains a payment: who paid, which invoices it covers and how much goes to each. It arrives in many forms, such as a bank reference, an emailed remittance advice, a portal download or a note on a cheque stub. Gather it into one place each day rather than hunting for it when a payment will not match.
2. Identify the customer
Payers do not always use the name on your invoice. A parent company, a shared services centre or a payment processor may send the money. Keep a list of known payer names and bank details linked to each customer account, and update it whenever a new variation appears.
3. Match to open invoices
The cleanest case is an exact match: the payment equals one invoice and the reference quotes its number. Next come one payment covering several invoices, and several payments for one invoice. Match on invoice number first, then on amount and customer, and only then on judgement.
4. Post and reconcile
Apply the payment, update the customer balance and reconcile the total to the bank statement. If the totals do not agree, find out why before moving on.
Handling short-pays and overpayments
A short-pay happens when a customer pays less than the invoice total. Do not simply leave the balance sitting there. Find the reason first, because it decides what you do next.
- Deduction taken. The customer subtracted a discount, a return or a claimed damage. Log it with a reason code and pass it to the right person to approve or dispute.
- Bank or tax withholding. The difference is a fee or a withholding. Record it correctly, and ask for the certificate if one applies.
- Dispute. The customer disagrees with part of the invoice. Apply the cash, then route the remainder through your dispute process.
- Simple error. A typo or a rounding difference. Small amounts can follow a written-off tolerance policy, such as anything under a fixed threshold.
Overpayments need the same care. Hold the excess as a credit on the account and either apply it to the next invoice with the customer's agreement or refund it.
Auto-matching rules that save time
Most payments are boring, and boring is good. Set rules so the routine ones apply themselves and people only see the exceptions:
- Exact invoice number and amount. Apply automatically.
- Known payer, one open invoice, same amount. Apply automatically.
- Known payer, amount equals the sum of several open invoices. Suggest the match for a quick human check.
- Amount within a small tolerance. Apply, and book the tiny difference to a defined account.
- Anything else. Send to an exception queue with the likely candidates listed.
Start with conservative rules and watch the results for a few weeks. A rule that wrongly applies cash is worse than a payment that waits for a person.
A daily cadence
Cash application works best as a short daily routine, not a monthly clean-up. A simple rhythm: import the bank feed each morning, run auto-matching, work the exception queue, then review any unapplied item older than a few days. Each morning, ask the sender for missing remittance details the same day, while the payment is still fresh in their mind. Once a week, review your unapplied cash by age and by payer, and look for patterns, such as one customer who never quotes invoice numbers.
Common mistakes
- Applying to the oldest invoice by default. This can pay off a disputed invoice by accident or contradict what the customer intended.
- Parking payments in a suspense account. Items left unexamined tend to stay there.
- Ignoring the cause of repeat exceptions. If one customer always causes a problem, fix the remittance process, not just each payment.
- Skipping the bank reconciliation. It is the check that catches posting errors early.
Where tools help
A spreadsheet is enough while volumes are low. As payments grow, matching by hand takes more time than it should. If you manage receivables with FulcrumGrid Collection, you can keep overdue invoices and follow-ups in one place, which makes it easier to see which accounts are really late once payments are matched. It will not replace good remittance habits, but it can reduce the chasing of invoices that are already settled.
Get the remittance data in, match the routine payments by rule, give every exception an owner and review daily. Accurate cash application is quiet, steady work, and it makes every other receivables number more trustworthy.
Frequently asked questions
What is the difference between cash application and collections?
Cash application records the payments you have received against the right invoices. Collections is the work of following up on invoices that are still unpaid. Accurate cash application keeps collections focused on the right accounts.
What should I do with unapplied cash?
Investigate it daily. Look for the payer in your records, check the bank reference, and ask the customer for remittance details. Anything you cannot match within a few days should be escalated and tracked by age.
How do I handle a customer who short-pays every invoice?
Find the pattern. It may be a recurring deduction, a withholding or a disagreement about terms. Record a reason code each time, then agree a fix with the customer so the next payment arrives in full.
Can cash application be fully automated?
Mostly, for routine payments. Auto-matching handles exact matches well, but short-pays, unclear references and prepayments still need a person. Aim to automate the easy majority and review the exceptions.
FulcrumGrid Collection
Chase only what is really overdue
FulcrumGrid Collection helps you track overdue invoices and follow up on a sensible schedule, so your team focuses on accounts that are genuinely late.