Returns and recalls are different
A return is initiated by a bank in the payment chain, usually the beneficiary's bank. It sends the funds back because it cannot or will not complete the payment. You did not ask for it. It happens to you.
A recall is initiated by the payer. You ask your provider to try to retrieve a payment you have already sent, perhaps because it went to the wrong account, was a duplicate, or was the result of fraud. Your provider sends a request down the chain. Whether the money comes back depends on where it is and, often, on the consent of the beneficiary.
The distinction matters because the likely outcomes are very different. Returned funds almost always come back, although sometimes reduced by charges or exchange differences. Recalled funds come back only if the request reaches them in time or the beneficiary agrees.
Why payments are returned
The most common reasons a bank returns an international payment are:
- Account does not exist or is closed. The account number or IBAN is wrong, or the beneficiary has moved banks.
- Name does not match. The beneficiary bank is not satisfied that the named beneficiary holds the account.
- Account cannot receive the payment. It may be blocked, dormant, restricted to certain currencies or not permitted to receive international payments.
- Missing or incorrect information. No purpose code where one is required, an incomplete address or a missing local identifier.
- Unanswered query. A bank asked for information and did not receive a satisfactory reply in time.
- Compliance decision. A bank decided, under its own policy, not to process the payment. It may not explain why.
- Beneficiary refusal. Occasionally the beneficiary asks its bank to send a payment back, for example if it was not expected.
Some of these can be fixed and the payment resent with correct details. A compliance refusal usually cannot be overturned by resending to the same bank.
What comes back on a return
Returned funds travel back through the chain, and each bank may take a fee on the way, just as on the outward journey. The amount you receive can therefore be lower than what you sent.
Currency can also cause a difference. If you converted Canadian dollars to euros and sent euros, the returned euros may be converted back to Canadian dollars at the rate on the day they arrive. If rates have moved, you may gain or lose. You could also choose to hold the returned euros and resend them once details are corrected, which avoids converting twice.
An illustrative example: a company sends 10,000 euros to a supplier, but the IBAN has a typo that still passes validation and does not match any account. The beneficiary bank returns the funds. Intermediaries deduct charges on the way back and the company's provider receives 9,960 euros. The company corrects the IBAN with the supplier and resends. Those figures are made up, but the pattern of a small loss on a return is typical.
How a recall works
When you ask for a recall, your provider sends a formal request through the same chain the payment took, quoting the original payment and its UETR. Each bank checks whether it still holds the funds.
- If the payment has not yet left your provider or its bank, it can often be stopped outright.
- If it is held at an intermediary, that bank can usually return it to the sender.
- If it has reached the beneficiary bank but has not been credited, that bank may return it.
- If it has been credited to the beneficiary's account, the money now belongs to the beneficiary in the eyes of the bank. The bank will normally ask its customer for permission to debit the account and return the funds. If the beneficiary refuses or does not respond, the bank generally cannot return the money without legal authority.
That last point is the hard truth of recalls. Once funds are credited, recovery is not guaranteed, and in many cases it depends on the goodwill of someone you have just paid by mistake.
Timelines in general terms
Banks do not commit to a fixed time for recalls. The response depends on how many banks are involved, how fast each answers, and whether the beneficiary has to be contacted. A recall of a payment that has not yet left can be quick. A recall that needs beneficiary consent can take weeks, and some never receive a final answer.
For SEPA credit transfers there is a defined recall process within the scheme rules, with time limits for the payer's bank to send a request and for the beneficiary's bank to respond. Even then, once the funds are credited, the beneficiary's consent is usually needed.
What makes the biggest difference is speed. The sooner you act, the more likely the payment is still somewhere a bank can stop it. Raise a recall as soon as you know there is a problem, and do not wait to see whether the beneficiary returns the money voluntarily.
What you can and cannot get back
| Situation | Likely outcome |
|---|---|
| Payment not yet released by your provider | Can usually be cancelled |
| Payment held at an intermediary for a query | Can usually be returned, possibly less charges |
| Payment at beneficiary bank, not credited | May be returned, depending on that bank |
| Credited to the correct beneficiary, duplicate payment | Depends on beneficiary agreeing to return or credit it |
| Credited to the wrong account through a keying error | Depends on the account holder's consent or legal action |
| Credited to a fraudster's account | Often difficult; funds may have moved on quickly |
For a duplicate payment to a regular supplier, the simplest route is often to ask the supplier to hold the surplus as credit against the next invoice. That avoids the cost and delay of a formal recall.
When fraud is involved
Recalls connected to fraud, such as payments to a fraudster after a fake change of bank details, need fast and coordinated action.
- Tell your payment provider immediately and ask for an urgent recall marked as fraud.
- Report the fraud to the police and to the relevant national fraud reporting body.
- Gather the evidence: the fraudulent emails or messages, the original genuine bank details and the payment confirmation with its UETR.
- Warn the genuine supplier, whose systems or email may have been compromised.
A recall marked as fraud may prompt the beneficiary bank to freeze the account if funds remain, but rules differ between countries. Fraudsters often move money out within hours, so recovery is uncertain. Prevention through verification and dual authorisation is far more effective than recovery after the fact.
Avoiding the need for recalls
Most recalls are avoidable. The habits that prevent them are simple.
- Collect bank details from a document and confirm them with a known contact.
- Verify every change of bank details by phone to a number you already hold, never one in the change request.
- Check for duplicates before releasing payments, especially when re-sending after a query.
- Use a second approver for new beneficiaries and for changes.
- Keep confirmations and UETRs, so if something does go wrong you can act within minutes.
The guide to IBANs and account numbers covers the detail errors that cause most returns.
Talking to the beneficiary
When a payment has been credited to the wrong place or paid twice, the person holding the money is often the key to getting it back. How you approach them matters.
For a duplicate or overpayment to a genuine supplier, contact them directly and early. Explain what happened, give the payment details and UETR, and propose a solution: a refund to the original account or a credit against the next invoice. Most established businesses will agree, because they want to keep the relationship. Put the agreement in writing.
For a payment credited to an unknown third party through a keying error, you usually cannot contact them yourself, because their bank will not disclose who they are. The recall request is the channel. The beneficiary bank will contact its customer and ask for consent. If the account holder refuses, the remaining options are legal ones, which vary by country and can be costly relative to the sum involved.
Whatever the situation, keep a written record of every contact and every request made through your provider, with dates. If the matter becomes a legal claim or an insurance claim, that record will be needed.
Internal follow-up after a return or recall
Every return or recall is a chance to find a weakness in your process. After the funds are resolved, work through a few practical points inside the team. Establish where the wrong detail came from: keyed by hand, copied from an email or taken from an old record. Check whether the approval step had the information needed to spot it. Decide whether the beneficiary record should be updated, deactivated or flagged for re-verification.
Record the outcome, including any charges lost and exchange differences, and book them correctly. Over a year, a log of returns and recalls shows where the process needs tightening and which beneficiaries or corridors cause repeated trouble.
General information
This article is general information and is not legal advice. Recovery of funds depends on the banks involved, the laws of the countries concerned and the facts of each case. If you need to recover funds from a third party, take legal advice. For how payment confirmations and tracking support investigations, see the CCYFX platform page.
