How to trace missing incoming payments with an AI agent

Most missing payments are in one of five places: already credited, sitting in suspense, returned to the sender, held for review, or never sent. The agent searches each in turn and drafts an answer. Applying funds from suspense to an account is held for a named person, and holds for financial crime review are never explained to the customer.

What is a missing payment trace, and who owns it?

A customer says money should have reached them and has not. Their employer says salary went out on Friday; a buyer says they paid the invoice. The bank's job is to find out whether the payment arrived, and if it did, why the customer cannot see it. Payment operations or customer service owns the case, with financial crime involved if the payment is held for a check.

It is a common request and an easy one to answer badly. "It's on its way" may be untrue, and "we have no record" may be wrong if the payment sits in a suspense account under a misspelt name. Whether an agent can trace a missing or failed payment is a yes for the search; the care is in what it does with the result.

What does the agent prepare?

1. Agent, depth 1: collects the details. Sender, amount, date sent, reference, the sending bank, the account details the sender used.
2. Agent, depth 1: searches credits to the account. Including credits under a different reference or a combined amount.
3. Agent, depth 1: searches suspense and unapplied items. Payments that arrived but could not be applied: wrong account number, name mismatch, closed account, missing reference.
4. Agent, depth 1: searches returns. Payments received and sent back, with the reason.
5. Agent, depth 1: checks for holds. If the payment is held for a financial crime or fraud check, it stops and routes the case to a person.
6. Agent, depth 2: drafts the answer. What was found and what happens next. Standard answers, such as "credited on this date with this reference", can go at depth 3 once certified.
7. Agent, depth 2: drafts the application from suspense. With the evidence linking the payment to the customer. A person approves; moving funds from suspense to an account is depth 4.
8. Agent, depth 2: drafts the trace request to the sending bank if the payment has not arrived, or advises the customer to ask the sender to raise a trace with their own bank.

What does a named person approve, and why?

Applying funds from suspense. A payment in suspense belongs to someone, and the customer saying it is theirs is a declared claim. The agent gathers evidence that ties the payment to this customer, such as the sender's name, the amount, the date and a near-match on the account number, and a person decides. Getting this wrong credits one customer with another person's money.

Anything involving a hold. If a payment is held for a sanctions or fraud check, the customer may not be told why, and in some cases may not be told it is being checked at all. A person decides what to say.

Trace requests to other banks. These go out under the bank's name and a person sends them.

Matching incoming payments to customer accounts covers the routine matching that should keep most payments out of suspense in the first place.

Which controls apply, and what evidence do they leave?

Search record. Each search and its result is filed, so a person picking up the case sees what has already been checked.

Evidence for suspense applications. The fields compared, the result for each, and the person who approved. If two customers claim the same payment, the record shows why it went to one of them.

No disclosure of holds. The agent has no capability to discuss screening or fraud holds. The verdict on any attempt is refused, naming the role scope.

Duplicate watch. If the sender is about to resend, the agent notes the original so that a second payment is not credited twice, or so the first can be returned.

Where does it usually go wrong?

Promises. "It will arrive today" is a guess. The agent should say only what it found and what the next step is.

Wrong account, right name. The sender used an old account number for a closed account, and the payment was returned days ago. The customer was never told. Check returns before suggesting the sender try again.

Account restrictions. A payment arrives at an account restricted because identity documents are outstanding, and it is held. The fix is to get the documents in, as in collecting missing KYC documents from customers, not to release the payment.

Asking the customer to chase the wrong bank. If the payment was never received, the sender's bank holds the answer. Telling the customer clearly saves a week.

What should you measure?

• Traces resolved at first contact.
• Payments found in suspense, and time from arrival to application.
• Suspense applications reversed because the money belonged to someone else. Should be none.
• Cases routed for holds, and complaints about how they were handled.
• Repeat traces for the same payment.

The general bounds for bank agents are in AI agents in banking.