Resolve customer cash that has arrived without a reliable invoice allocation, and prove where every portion went before closing the exception.
A bank receipt is not proof that the right invoice has been paid. The payer may be unfamiliar, the remittance may arrive later, or one transfer may cover several invoices and an unexplained remainder. Guessing an allocation can make the unapplied-cash report look better while making the customer account wrong.
An unapplied cash resolution workflow starts with an existing receipt and ends with supported application or another authorized disposition, reconciled to the accounting record. Use the following procedure for B2B receivables exceptions—not as a replacement for the overall cash application process. The controls are recommended operating practices; your controller determines accounts, posting periods and accounting treatment.
Separate an unknown payer from an unknown allocation
Two missing facts need different investigations: who paid, and which obligations the payment settles. Identifying the customer does not by itself establish an invoice allocation.
Oracle’s receipt application guidelines distinguish unidentified receipts, which lack customer information, and describe applications covering all or part of one or several debit items. Exact statuses and permitted actions depend on your accounting system.
| Observed condition | Owner and evidence needed | Safe next state |
|---|---|---|
| Payer cannot be tied to a customer | Treasury and AR: bank reference, payer details, verified customer relationship | Investigating; do not guess a customer from the amount alone |
| Customer known, invoice allocation missing | AR: remittance from an established customer contact, invoice references and amounts | Allocation review after corroboration |
| Only part of the receipt is supported | AR reviewer: supported lines plus separately identified residual | Partial application if policy permits; residual stays open |
| Customer claims a deduction | AR and account owner: invoice, remittance, reason and dispute evidence | Deduction case linked to the receipt, not an invented discount |
| Payment belongs elsewhere or refund is proposed | Controller and treasury: entity, ownership, authority and verified destination | Separate authorized disposition; no informal transfer or refund |
Build one receipt-level investigation record
Start when a receipt fails normal matching or appears on the unapplied/unidentified report. Assign an AR case owner and a review date. Keep the bank transaction and existing ERP receipt identifiers together so two analysts do not create competing cases for the same money.
Capture receiving legal entity, bank account identifier, value date, amount, currency, bank reference, ERP receipt ID, current receipt status and unapplied amount. Record the report’s extraction time and filters. Keep customer identity evidence separate from allocation evidence; a trading name, parent company or project nickname is a lead, not automatic authority to apply across accounts.
Preserve the original remittance and later clarifications with sender and date. The Research Foundation for SUNY’s unapplied receipts procedure provides an institutional example of attaching receipt evidence and assigning identification and monitoring responsibilities. Its review cadence is its own policy, not a universal requirement.
Ask for an allocation that can be checked
Contact the customer through an established billing channel. Ask for the paying entity, receipt reference, invoice numbers, amount allocated to each invoice, and explanations for any credits or differences. Avoid sending unrelated customer balances or bank details to an unverified requester.
Compare the response with open invoices, contract/customer records and the bank receipt. If the remittance conflicts with the receiving entity, currency or customer relationship, keep the case in investigation and name the decision owner. Do not override that conflict merely because an invoice has an identical amount.
Use an allocation worksheet, not an amount-only match
For each candidate invoice, record the customer account and entity, invoice number, current open balance, proposed application, evidence reference, reviewer and eventual ERP application reference. Add a separate residual row with reason, owner, next action and review date. That row is how partially resolved cash remains visible.
| Receipt portion | Current balance | Proposed amount | Evidence and control |
|---|---|---|---|
| Invoice A-104, verified customer/entity | $7,000 | $7,000 | Customer remittance identifies this invoice; refresh balance before posting |
| Invoice A-109, same customer/entity | $4,000 | $4,000 | Same remittance supports this line; check for pending applications |
| Unexplained remainder | Not an invoice balance | $1,000 retained unapplied | AR owns customer clarification; no automatic credit or refund |
| Total receipt accounted for | Original receipt: $12,000 | $11,000 application + $1,000 residual | Reviewer confirms no portion is assigned twice |
This is a constructed example, not a prescribed accounting entry. The customer confirms the two invoice allocations but cannot yet explain the extra $1,000. If company policy permits partial application, approve only the supported $11,000. Keep the remaining $1,000 as a visible receipt exception with an owner and next action. Do not call it revenue, a discount or a refund simply to clear the queue.
Use one currency per control calculation unless accounting has explicitly approved a cross-currency method. Fees, foreign-exchange differences and adjustments require their own supported treatment; they are not unexplained plugs in the worksheet.
Revalidate before applying the existing receipt
Move the case from Investigating → Allocation reviewed only when the proposed distribution is supported and the designated reviewer has approved any required exceptions. Before execution, refresh the receipt’s remaining amount and each target invoice’s current balance, including pending applications where your system exposes them.
Suppose another operator applies $2,000 to A-104 while the worksheet is waiting. Its balance is now $5,000, not $7,000. Stop the old allocation. Determine which receipt funded that application, update the proposal and obtain renewed review. Do not silently move the extra $2,000 to A-109 or another invoice.
Apply the existing receipt through the accounting system’s supported process; do not record a second bank receipt. Record the receipt ID and application references separately so later review distinguishes the arrival of funds from their allocation. Use your ERP’s documentation for the execution sequence; the investigation worksheet is not a posting interface.
- Execution succeeds: retain the receipt/application IDs, invoice-level amounts, operator and posting date.
- Execution fails: keep the case open, capture the error and assign correction. Re-review changed amounts, entities or periods.
- Outcome is uncertain: read the receipt and application history before resubmitting. An absent confirmation is not proof that nothing posted.
Reconcile the receipt and keep the residual open
After application, compare the worksheet with the actual ERP receipt, affected invoice balances and applicable reconciliation records. Confirm the bank receipt was captured once and the intended application—not merely a batch total—was recorded. Accounting should determine the ledger reconciliation and period treatment.
Oracle’s Unapplied Receipts Register documentation describes status, currency and business-unit filters and notes report exclusions. Use that as a reminder to document what your own report includes; an item disappearing from a filtered report is not sufficient closure evidence.
In the example, the worksheet should show $11,000 applied, $1,000 still unapplied and $12,000 accounted for. The supported invoice lines can be marked reconciled while the overall receipt case remains open. Maintain a roll-forward of the unresolved balance: opening amount, newly unresolved amounts, supported applications or other authorized dispositions, and closing amount. Link each movement to its source transaction.
Hand off a decision without pretending it is completed
If the customer later establishes that the $1,000 was an advance, duplicate payment or a different obligation, route that evidence to the appropriate policy owner. A refund request needs separate authorization and execution proof. A short-payment claim belongs in deduction management. Neither a case assignment nor a promised refund resolves cash in the accounting record.
Close only after each portion has a supported final disposition, required posting is verified, and the controller’s reconciliation requirements are met. Reopen the case if an application is reversed or new evidence invalidates the allocation; retain the prior decision rather than overwriting it.
Where Workhint fits
The coordination problem sits around the accounting transaction: someone must collect clarification, review evidence, decide the next action and confirm the handoff. Workhint’s Workflow Engine supports configured work steps, role-based approval routing and required details or files before progress.
For a multi-team exception queue, the Workflow Automation Software solution describes structured forms, human decisions, owners and process stages. Those capabilities are relevant to organizing an investigation and review process. They do not establish native bank matching, an AR ledger integration or automatic receipt posting. Keep the accounting system authoritative for receipt status, applications and balances; define how its evidence will be returned to the workflow before implementation.
Frequently asked questions
Can we apply cash to the oldest invoice without remittance?
Not merely to empty the exception queue. Use the company’s authorized allocation policy and applicable customer terms, verify customer/entity and document the basis. If evidence conflicts, escalate rather than treating age or equal amounts as proof.
Does identifying the customer resolve unapplied cash?
No. It resolves one question. You still need a supported allocation or another authorized disposition, verified execution and reconciliation.
Who owns an unapplied-cash case?
Assign AR an explicit case owner, with treasury supporting receipt identification and the controller owning accounting decisions. Customer/account teams can obtain missing evidence without becoming the authority for unsupported postings.
What should a reviewer see at close?
The original receipt, allocation evidence, approved distribution, actual application references, residual disposition and reconciliation proof. A zero on one report or a completed task notification alone is not enough.
Leave a Reply