A business customer says an overdue invoice was paid last week. The collector still sees it open. Cash application has a receipt for a similar amount, but the payment arrived without usable remittance details. Until someone connects those records, the customer may receive another reminder while your team investigates the same payment twice.
This is a cash application problem with consequences for collections. A practical response connects receipt evidence, invoice allocation, accounting ownership, and the collector’s next action. The objective is to establish what has been received and what remains collectible without guessing where a payment belongs.
Separate three different receipt questions
Start by distinguishing the exceptions your team needs to resolve. Use your accounting system’s definitions, and document any differences from these working descriptions:
- Unidentified receipt: money has been recorded, but the customer has not been established.
- Unapplied amount: a receipt, or part of it, has not been allocated to invoices or otherwise resolved through an approved treatment.
- On-account payment: money is associated with a customer account without settling specific invoices, for example an agreed advance.
Oracle’s receipt application guidance distinguishes unidentified receipts from receipts available for application and explains that one payment can cover multiple invoices. These are useful operational distinctions, although system terminology and configuration vary.
Do not treat every on-account payment as an error. Equally, moving an unexplained receipt into an on-account category should not end the investigation. Record why that treatment is appropriate and whether further allocation is expected.
Build one investigation record
Give each exception a unique receipt reference and one accountable owner. Capture the receiving business unit, receipt date, amount, currency, bank reference, payer description, suspected customer, remittance evidence, unapplied amount, and next action date. Link supporting records rather than copying sensitive bank information into broadly visible collection notes.
Keep bank receipt, accounting posting, and invoice application dates separate. They describe different events. A payment can be visible at the bank before its allocation reaches the collector’s account view.
Where a customer reports payment that cannot yet be located, record it as reported payment awaiting verification. A remittance advice describes the customer’s intended allocation; verify receipt separately before treating the invoices as paid.
Investigate in a consistent order
First check whether the receipt already exists. Search the bank reference, amount, currency, date range, and payer description before creating another receipt or exception. Duplicate entry can make a reconciliation problem harder to detect.
Next identify the paying business. A trading name, parent company, or payment service may differ from the invoiced legal entity. Confirm the connection using established account information and supporting evidence. A similar name alone is insufficient.
Then obtain the allocation detail. Ask the customer’s accounts payable contact for invoice numbers, amounts allocated to each invoice, deductions, and the payment reference. Compare those instructions with open invoices, existing credits, and earlier applications. Resolve ambiguous references before posting.
Finally, have the authorized accounting owner apply the receipt or approve another appropriate treatment. Retain the evidence and application reference so the collector can see how the exception was resolved.
A hypothetical payment that looks overdue
Assume a distributor has three overdue invoices from one commercial customer: $12,000, $9,000, and $4,000, totaling $25,000. A $21,000 receipt is recorded against the customer but remains unapplied because the remittance attachment was missing. Assume all amounts are in U.S. dollars, with no credits, fees, or other adjustments.
| Item | Before allocation | Confirmed action |
|---|---|---|
| Invoice A | $12,000 open | Apply $12,000 |
| Invoice B | $9,000 open | Apply $9,000 |
| Invoice C | $4,000 open | Remain open for collection |
| Receipt | $21,000 unapplied | Fully allocated to A and B |
The customer supplies remittance confirming payment of A and B. After authorized application, the remaining invoice balance is $25,000 minus $21,000, or $4,000. The collector follows up on C rather than requesting another $25,000.
This allocation does not generate another $21,000 of cash: the money was already received. Depending on report design, the account’s net position may already reflect the receipt even while individual invoices remain open. Check both views before describing the effect on overdue balances or performance.
Give exceptions an owner and a deadline
Use a small set of reasons that identify the next action: missing remittance, unknown payer, invalid invoice reference, allocation disagreement, or posting correction. Cash application should own allocation research; collectors can obtain customer clarification; treasury can help trace bank details. Your organization may divide those responsibilities differently, but each case needs one coordinator.
Review large and aging exceptions together. Set internal response targets based on payment volume, staffing, and risk rather than adopting an unsupported universal benchmark.
Never force a match merely to clear a queue. Route short payments, exchange differences, refunds, and adjustments through the relevant approval process. Keep unresolved amounts visible until the supporting treatment is authorized.
Return a verified result to collections
Before sending a reminder, check recent receipts and unresolved payment investigations for that account. If a reported payment is being researched, use a time-limited follow-up task for the affected invoices, with an owner and review date. Continue appropriate collection work on unrelated unpaid invoices.
After posting, confirm that the collection system has received the updated balances. Check the interface’s last successful update and any rejected records. Closing the investigation in an email does not establish that the collector’s work list is accurate.
Oracle’s Unapplied Receipts Register documentation illustrates reviewing unidentified, on-account, and unapplied payments separately and using receipt reporting to support reconciliation. Apply that principle within your own accounting environment.
Use a weekly control checklist
- Reconcile receipt records to bank activity and accounting records.
- Review outstanding exceptions by amount, age, reason, and owner.
- Confirm that resolved applications reached collection work lists.
- Check recently corrected applications for reversals or repeat errors.
- Identify customers whose recurring remittance gaps need a process change.
Track time from receipt recording to verified application alongside correction frequency. Define whether elapsed time uses calendar or business days. Separate agreed advances from unexplained backlog so the measures lead to useful action.
CMS Credit Suite provides rules-based collection work lists, recorded contact outcomes, and follow-up reminders. Discuss the accounting data and integration needed for your workflow rather than assuming those features include automated cash application. Contact Credit & Management Systems, Inc. to discuss connecting verified payment information with more accurate B2B collection follow-up.