When customer payments arrive but never get applied

One common failure in accounts receivable is cash that arrives but never gets matched to the invoice it pays. The bank looks right while the customer ledger stays wrong. It begins with thin remittance detail and is fixed at the point where receipts are applied.

How it starts

A payment comes in without enough information to identify it. The customer pays several invoices in one transfer and sends no breakdown. A cheque arrives with a reference that matches nothing in the system. A large customer short-pays because of a dispute nobody in finance has heard about.

The cash still has to be deposited. So the team banks it and parks it in an unapplied or suspense account, intending to come back later. Later rarely comes. The next batch of receipts takes priority, and the parked items age quietly.

Other routes lead to the same place. Someone applies a payment to the oldest open invoice by default when the customer meant a newer one. A payment lands on the wrong account because two customers share a similar name. Where collections must be split across penalties, fees, interest and the principal balance in a set order, a clerk may apply the whole amount to principal, leaving small residual charges open on the account.

Returned cheques make it worse. If a bounced payment is reversed in the bank but not on the customer account, the invoice shows as settled when it is not.

How it gets spotted

The earliest signal usually comes from outside finance. A customer complains about a reminder letter for something already paid. A sales manager hears that a good account has been put on credit hold for no reason anyone can explain.

Inside the team, the suspense balance tells the story if anyone watches it. A healthy unapplied account turns over constantly. One that only grows, or holds items nobody can describe, points to a matching problem.

The aging report is another clue. Old invoices on accounts that are otherwise current, paired with credit balances on the same or related accounts, suggest cash went to the wrong place. Collectors chasing debts that turn out to be paid is a cost, and it erodes their trust in the report they work from.

At period end the reconciliation between the receivables subledger and the general ledger may still balance. That is what makes this failure easy to miss. Total cash is right; its distribution across customers is not.

Fixing the backlog

Start by listing every unapplied and suspicious item with what is known about it: date, amount, payer name, bank reference. Sort by size, because a small number of large items often explain most of the problem.

Then go and get the missing information. Call the customer. Ask the bank for remittance images or the full payment message. Check whether a sales or service team agreed a deduction that was never recorded as a credit memo.

Once a payment is identified, apply it properly and record any genuine adjustment or credit as its own entry with a reason. Do not net differences away silently. If items cannot be identified after real effort, follow the policy for miscellaneous receipts or unclaimed funds instead of forcing a match.

Post corrections so that the subledger and the general ledger move together. A manual journal that fixes the ledger but leaves customer accounts untouched only moves the error somewhere harder to find.

Stopping it coming back

The lasting fix sits upstream. Invoices need a clear reference that customers can quote, printed where they will see it. Large customers can be asked to send remittance advice in a consistent form.

Set an owner for the suspense account and a rule that nothing sits there without a note explaining what is being done about it. Review that account as part of the regular close, not as a cleanup project once a year.

If allocation order matters, build it into the system so the clerk is not deciding it by hand.

Questions to ask the people who run it

What happens when a payment arrives and nobody can tell what it is for?

Who is allowed to move money out of suspense, and does anyone check their work?

When a customer short-pays, how does the team find out why?

How are bounced cheques reversed on the customer account, and who does it?

Are there customers whose payments are always difficult to match? What makes them hard?

Do collectors ever chase invoices that turn out to be paid? What do they do when that happens?

Is there a workaround everyone uses that is not written down anywhere?

The documented procedure usually says payments are matched on receipt. The answers to these questions show what really happens on a busy day, and that is where the change has to land.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.