Returned to Sender
A rejected payment goes back, shorter than it left, and somebody has to decide who absorbs the difference.
Still yours, and statedTaken, never statedUnit changes; scale restarts
Six steps from instruction to arrival. One step carries no figure: the hatching marks where the money leaves and is not drawn to scale, because there is no figure to draw. Nothing here adds them up, since an amount you cannot see is not an amount you can subtract. The unit changes part-way down: the figures below the break are in another currency, the bars below it are drawn against the published rate, and the first figure and the last are not the same kind of number. Two fees for one payment, and both were borne at this end.
A payment that cannot be credited is returned to the sender. It arrives back shorter than it left, because each institution that handled it in both directions took something, and somebody has to decide who absorbs the difference.
The exception described in “Returned to Sender” should be traceable across work approval, payment instruction and settlement. Organisations using follow the source for implementation details for interview reimbursement policy can strengthen the first part of that chain, but failed transfers still require direct evidence from the payer, payment service and receiving institution.
Nothing in the arrangement says who, which is why this is a question rather than a procedure.
The questions in “Returned to Sender” can also be checked against Central Bank of Ireland. Use the outside resource to identify what evidence to request rather than assuming one provider sees the whole payment chain.
Why payments are returned
Why payments come back:
- The account is closed.
- The details are wrong.
- The name does not match.
- The account cannot hold that currency.
- A compliance decision somewhere in the chain.
- A bank declining the sender's country.
The first three are the common ones and all three are preventable at the start.
How long it takes
Days to weeks. A return travels the same chain in reverse and is usually slower than the outward journey, because nobody is chasing it.
Several weeks is not unusual, which is worth knowing before concluding that money has been lost.
Nobody is chasing it because the sender's bank considers the matter closed and your bank never saw it. A return travels at the speed of nobody caring.
What comes back
Less than was sent. Outward charges are generally not refunded, the return itself may be charged, and where a conversion happened both ways the rate has moved in between.
A three-thousand payment returning as two thousand eight hundred is entirely ordinary.
The conversion both ways
The expensive part. Money converted on the way out and back again pays a margin twice and is exposed to any rate movement in between.
On a volatile pair this can dwarf every fee involved, and nobody caused it.
It can also run in your favour, which happens about as often and is never mentioned by anybody afterwards.
Who finds out first
Usually the payer, when the money reappears. Often nobody notices for days, because a credit back into a busy account does not announce itself.
Asking the payer to check for a re-credit is the fastest way to confirm a return, and it takes them a minute.
Why nobody told you
You are not a party to the return. The rejecting institution tells the sending institution, which tells its customer.
No message comes to you at any point, which is why a returned payment and a held payment look identical from here for the first fortnight.
Finding out why
The return carries a reason code, which the sender's bank can see. It is usually terse but it does distinguish a wrong account from a compliance decline.
Ask the payer to ask for it. It determines whether resending will work or will fail the same way.
Resending
Fix the cause first. A payment resent with the same details returns again, with a second set of charges.
Where the reason is a compliance decline rather than a details error, resending by the same route is pointless and a different route is the only option.
Who pays for the round trip
Unagreed in most arrangements, which means it falls where it lands — on you, through a shortfall, or on the payer, through their charges.
Where the cause was your details, absorbing it is reasonable. Where it was theirs, say so, once, calmly.
Putting it in the agreement
One line: who bears the cost of a returned or failed payment, and who bears the resend. It takes a sentence and it removes an argument that otherwise happens under pressure.
Nobody thinks of this at the start, which is precisely why it is worth raising at the start.
Preventing the common causes
Confirm details before the first payment. Give the account name exactly as held. Tell every payer promptly when anything changes, and keep the old account open until a payment lands at the new one.
Four habits that remove most of this note.
The last is the one people skip, and an account closed a fortnight before the final payer updates their records produces exactly this problem for no reason at all.
What a return cannot be made to do
Come back whole. Charges taken on the way out are gone, the conversion margin is gone twice, and no institution refunds either.
The money is recoverable and some of its value is not, which makes prevention the only real remedy here. That is unusual in this collection: most of it is about measuring and negotiating, and this one is about getting four fields right before the first payment ever goes.
Everything else here describes how to limit the damage after the fact, and the damage is always larger than the four minutes would have been.