Rejection and return answer different questions
A rejection reports that an instruction was not accepted for further processing at the relevant stage. A return of funds concerns money being sent back after settlement at a relevant point in the chain. These are simplified distinctions: a customer portal may use “rejected” loosely for several internal outcomes.
Ask the bank which event the label describes. A failed instruction, a debit reversal on your account and an interbank return are related possibilities, but they are not interchangeable evidence.
How the message types help
In relevant ISO 20022 flows, a pacs.002 reports payment status and can carry a rejection; a pacs.004 is a Payment Return message. The correct message depends on the settlement context. Neither a copied code nor a document heading alone establishes that a refund is already available to the sender.
Swift’s PMPG guidance on returns and rejects explains the distinction and cautions against using a return where a rejection is appropriate merely to deduct charges. Our status decoder explains terminology without investigating a payment.
Get the actual reason before trying again
Account details, routing instructions, supported services or a bank’s compliance review may prevent processing. Request the original reason code and its bank explanation. Do not infer a specific cause from a generic “failed” label.
Before resending, ask which detail must change, whether the original can still proceed and what happened to its debit. Correcting the beneficiary name in an email does not amend an instruction already held by the banks.
Follow the return as its own event
- Which institution initiated the return, and on what date?
- What return or investigation reference should your bank use?
- What amount and currency are being returned, and are any deductions explained?
- Has the sending bank received the return, or is it still awaiting it?
- When does the bank expect to post the account adjustment?
Keep the original UETR alongside any return reference the bank supplies. Do not assume that the return uses the same customer-facing identifier or retraces every intermediary in precisely the same way.
Check the amount and the account entry
There is no universal refund countdown that follows from the word “rejected.” Handling depends on the banks, route, currency and unresolved checks. Ask for a case-specific expectation and a follow-up date.
The account credit can differ from the original debit because of explained charges or currency conversion. Ask for the calculation rather than treating every difference as an unexplained loss. See OUR, SHA and BEN charges for the allocation of transfer fees.
If the refund is still missing
Ask the sending bank to connect the original payment, the reported rejection or return and your account entry in one response. Use the bank-trace template if an investigation is needed. A UETR.io event cannot independently confirm the return or recredit.