Returned Payment

A returned payment is one that did not go through and is therefore routed back to the person who sent it. The receiving bank, or an intermediary along the way, was unable or unwilling to credit the intended beneficiary, so it returns the funds through the payment chain to the originating bank, which credits the payer. Common causes include a closed or nonexistent account, an incorrect account number, a name that does not match the account, a blocked account, or a compliance concern.

A return differs from a payment that never left: the funds actually moved, at least part of the way, and must travel back. That journey can take days, and in cross-border payments the amount that arrives back is often smaller than the amount sent, because of fees deducted on the outbound and return legs and differences between the exchange rates used in each direction.

Payment systems distinguish between several ways in which money can come back:

• Reject: the payment is refused before settlement, for example because the message fails validation. No funds have moved.
• Return: the payment has settled but the receiving bank cannot apply it, so it sends the funds back after settlement.
• Recall: the sender asks for the money back, for instance after a duplicate or a fraud. The receiving bank may return the funds only if they are still available and, in many cases, with the beneficiary's consent.
• Reversal or chargeback: mechanisms in card and some account-based schemes for undoing a transaction, usually initiated by the payer's side.

In the European SEPA schemes these are known collectively as R-transactions. In ISO 20022 messaging, a return is sent as a dedicated payment return message (pacs.004), carrying a reason code and a reference to the original transaction.

In the US ACH network, governed by Nacha rules, a receiving bank returns an entry using a standard return reason code, such as R01 (insufficient funds), R02 (account closed), R03 (no account or unable to locate account) or R04 (invalid account number). Most returns must be made within two banking days of settlement, but returns of consumer debits that the customer says were unauthorized can be made within 60 days. ACH debit returns are particularly important for firms that collect funds through ACH pull, because a customer's money can be treated as received and then come back days later. Nacha monitors return rates and can require originators with excessive returns to reduce them.

Wire transfers through Fedwire are final on settlement, so a wire that cannot be applied is returned by sending a new wire back rather than by unwinding the original.

An international wire may pass through several banks before it reaches the beneficiary bank. If that bank cannot credit the account, perhaps because of a beneficiary-account mismatch or a sanctions or AML concern, it sends the funds back through the chain. Each bank may deduct a handling fee, and under SHA or BEN charge codes fees may also have been taken on the way out. If the payment was converted from one currency to another, the return is converted back at the rate on the day of the return, which may differ from the original rate. The payer therefore often receives a short amount, and the shortfall can be difficult to recover. A payment trace using the UETR can show where the payment is and why it was returned.

A company in the United States sends USD 10,000 to a supplier's euro account in Germany. The payment is converted to EUR 9,200 at 0.92 euros per dollar, and an intermediary deducts a EUR 20 fee. The German bank finds the account closed and returns EUR 9,180, less its own EUR 15 return fee, so EUR 9,165 comes back. By then the dollar has strengthened and the return is converted at 0.95 euros per dollar, giving USD 9,647. The company has lost USD 353 to fees and exchange movements, plus the time spent on a payment investigation.

For payment firms, returns are a routine part of operations. They must be matched to the original transaction in reconciliation, credited to the right customer, and investigated where the reason suggests fraud, a mule account or a sanctions hit. High return rates for a sender or corridor can indicate data quality problems or account-validation failures, which tools such as account verification and confirmation of payee are designed to reduce. Firms should also set clear terms on who bears return fees and exchange losses, and explain them to customers before a payment is sent.