Why was a deposit held for review?

A held deposit means the system found something it could not be certain about. It would rather ask than guess, because guessing wrong credits the wrong person.

The usual reasons

The reference number was used before. Someone quoted a reference that already appears against an earlier deposit, but for a different amount. That is a common pattern in reuse, so it stops and asks.

The amount does not match. The reference is familiar, but the amount is different from what was requested. This is often a typo, but it has to be looked at.

The same reference is in two pools. The number turned up in both your Google Pay list and your bank list. It cannot be attributed to one source, so it is flagged rather than assumed.

The reference is already approved. A customer submitted a reference that was already approved earlier. Rather than approving the same money twice, the system rejects the new request with a clear reason.

What your team does

Open the request. You will see the history attached to it: when the reference was used, for what amount, and what happened. That is everything needed to decide.

The team then either approves or rejects, and the decision is recorded against a name.

What happens if nobody decides

After your timeout window, the system rejects it automatically and moves on. Nothing sits forever.