How to clear unapplied cash with an AI agent

Work the backlog oldest first, one receipt at a time. For each unapplied amount the agent establishes who paid, what they meant to pay, and why it was not applied. It asks the customer for a remittance where needed, applies the receipt once the evidence matches, and prepares refunds and transfers between entities for a person. It never returns money itself.

What is unapplied cash, and who owns clearing it?

Unapplied cash is money you have received but not matched to an invoice. Some of it is identified to a customer but sits "on account" because the customer did not say which invoices it paid. Some is not identified at all. While it sits there, the same customer's invoices look overdue, they get chased for money they have paid, and your receivables overstate what is owed. Over time, old balances become hard to explain and, in some places, may have to be handled under rules about unclaimed funds.

The accounts receivable lead owns the unapplied balance and the clearance process. Credit control owns customer contact. The financial controller approves refunds and any transfer between entities. Day-to-day matching of new receipts is a separate process, described in applying cash receipts to open invoices; this playbook is about what that process could not place. The wider finance position is in AI agents for finance: books you can audit.

How does the agent clear the backlog, step by step?

1. Agent, depth 1: lists unapplied items by age. Receipt, date, amount, payer, reference, and whether a customer is identified. Evidence: the list reconciled to the unapplied balance.
2. Agent, depth 1: re-runs identification on unidentified items. New customer records, new bank details on file and newly raised invoices may now explain an old receipt. Evidence: what was checked and found.
3. Agent, depth 1: looks for the reason. Paid before the invoice was raised; paid the wrong entity; paid twice; overpaid; paid a total that matches no combination of invoices. Evidence: the reason and the records that support it.
4. Agent, depth 3: requests a remittance from the customer's billing contact on an approved template, listing the receipt and the open invoices. Evidence: the request sent.
5. Agent, depth 3: applies the receipt when the remittance or a newly raised invoice gives an exact match, under the same rules as daily cash application. Evidence: the application verdict and the rule.
6. Agent, depth 2: prepares the rest. Duplicates and overpayments as proposed refunds or credits on account; wrong-entity payments as proposed intercompany transfers; untraceable items as a residue. Evidence: each proposal with its support.
7. Person, accounts receivable lead or controller: decides. Refunds, transfers, holding on account, or escalation of the residue. Evidence: the decision and its authority.

Why are refunds always with a person?

Because a refund moves money out, and money sent to the wrong place is hard to recover. Overpayments and duplicates are a known route for fraud: a payment is made in error, or apparently in error, and a request follows asking for the refund to go to a different account. The agent proposes refunds to the original payer's account only, and a person releases them under your payment controls. An emailed request to refund elsewhere is external information and cannot authorise a payment.

The same caution applies to transfers between entities. A payment received by the wrong company in a group must be moved with entries on both sides, approved by accountants who know both sets of books.

What makes this different from suspense clearing?

Suspense holds anything that could not be posted, from any source. Unapplied cash is narrower: money received from customers. The tools overlap, and unidentified receipts sometimes sit in suspense rather than in receivables; the general method is in clearing suspense account balances. The difference that matters is the customer. Unapplied cash always has someone on the other side who may be chased, credited or refunded, so every decision has a customer consequence. The underlying process is explained in what is cash application, and the question of how far to trust an agent with it in can an AI agent apply cash receipts to invoices.

Which controls matter, and what evidence do they leave?

Balance reconciles to items. Evidence: the item list and its total.

The bank line is the authority on amount. Evidence: bank reference on every application.

Chasing paused for customers with unapplied cash. Before any reminder, credit control sees the unapplied amount. Evidence: the check in each dunning verdict.

Refunds only to the original payer. Evidence: payer account on each refund proposal, matched to the receipt.

Age escalation. Items past the controller's limit go to the controller automatically. Evidence: escalation records.

What should you measure?

• Unapplied balance by age band, at each month-end.
• Items cleared per week from the backlog.
• Remittance requests answered, and how quickly.
• Customers chased while holding unapplied cash. Should be zero.
• Refunds proposed, approved and later disputed.

Where does it usually go wrong?

Everything is applied oldest-first to clear the backlog. The balance falls but the applications are guesses. Apply only on evidence; leave the rest on account and visible.

Remittance requests go to the wrong person. Sales contacts do not know what accounts payable paid. Use the billing contact.

On-account balances are treated as unapplied for ever. Some customers pay in advance on purpose. Mark known prepayments so they leave the backlog.

The backlog grows back. Clearing is wasted if daily application keeps failing for the same reason. Feed the reasons back to the cash application rules.

Where Pryme fits

In Pryme, applying a receipt on matching evidence, proposing a refund and proposing an intercompany transfer are separate capabilities. The first can be certified at depth 3; the other two are held, because moving money is depth 4 and refunds go only to the original payer on file.