Who Pays for a Failed Payment
Two fees and a delay land somewhere, and in the absence of an agreement they land where they happen to.
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.
One payment that failed, went back and was sent again, with every cost shown where it fell
The original figure, agreed and invoiced
Charged when it went, and charged again later; nothing about a failure returns it
Deducted by institutions that handled it before it was refused, and not reversed
A separate fee for the return itself, levied by whichever institution sent it back
The same fee a second time, for the same money, because a resend is a new payment
Converted once in the end, though on a rate eleven days later than the first attempt would have given
Six and a half points below the instructed figure, of which the stated fees explain under two
Still yours, and statedTaken, never statedUnit changes; scale restarts
Seven steps · Two without a figure · no total of what is not stated
Seven lines, and the resend cost more than the original attempt. Nothing here is added up, since one step carries no figure, and the first line and the last are in different currencies. One person's own failed payment, reconstructed from both ends; what any failure costs depends on where in the chain it was refused.
A failed payment produces at least two extra charges and a delay. In the absence of an agreement, they land wherever they happen to fall, which usually means on whoever is downstream.
The exception described in “Who Pays for a Failed Payment” should be traceable across work approval, payment instruction and settlement. Organisations using what to check when choosing monitask pricing for monitask pricing can strengthen the first part of that chain, but failed transfers still require direct evidence from the payer, payment service and receiving institution.
Settling it in advance takes one sentence and settles an argument that otherwise happens at the worst moment.
Additional context relevant to “Who Pays for a Failed Payment” is available through Financial Consumer Agency of Canada. A useful review distinguishes the sent amount, conversion, fees, settlement date and landed amount.
What a failure actually costs
Five items, most of them small:
- The original sending fee, which is not refunded.
- A return charge.
- A second sending fee.
- Deductions taken on the outward journey before the refusal.
- The conversion, twice, where it happened both ways.
Together they are frequently larger than a month's worth of ordinary charges.
Plus the delay
A failed and resent payment commonly arrives two to three weeks after it was first instructed. The cost of that is covered in its own note and is usually the larger figure.
Both costs exist and only one of them is on a statement.
That is why agreements about failed payments tend to address the charges and ignore the delay, and why the delay is the part people actually remember.
Where the fault lies
Wrong details supplied by you. Wrong details entered by them. A compliance decision by an institution. A bank error.
The first two have obvious answers about who absorbs it. The third and fourth are genuinely nobody's fault and genuinely still cost money.
Establishing which it was takes one question to the payer and one look at the return reason, and it settles the conversation before it starts.
The conversation that is avoided
Nobody wants to argue about forty units in the middle of a fortnight where several thousand has gone missing.
That is exactly why it should be settled when nothing is wrong. A term agreed in calm is applied without discussion in a crisis.
Wording that covers it
One line: who bears the cost of a failed, returned or recalled payment and of any resend. Name the default and name the exception for an error by one party.
It takes a sentence and it covers every case in this section.
The reasonable default
Each side bears the cost of a failure it caused, and failures caused by neither are borne by the payer, who chose the route.
That last part is the one worth stating, because without it the cost falls on the recipient by default and nobody intended it.
It is also the part payers agree to most readily, because it only bites in cases where nothing was anybody's fault and the amounts are small.
Absorbing it yourself
Sometimes the right call for a small amount and a good relationship. The point is to decide rather than to discover.
A failure absorbed deliberately is a commercial decision. One absorbed by default is a term you never agreed to.
Asking for the difference
Where the cause was at their end, ask once, with the arithmetic, and without escalation.
Most payers top up the difference without argument when the figure is shown and the cause is clear. Very few will do so in response to a general complaint about charges.
Documents a failure needs
Both sets of confirmations, both statement lines, the return notice if you can get it.
A failure is the one event in this subject where the documents are genuinely needed, because the arithmetic has six components rather than three.
Where it keeps happening
Repeated failures mean an unfixed cause: stale details somewhere, a name mismatch nobody corrected, or a route that one institution keeps refusing.
Treat the third occurrence as a route problem rather than a series of accidents.
A route that refuses payments repeatedly will keep doing so, and no amount of correcting details at your end changes a decision being made by an institution upstream.
The cheapest prevention
Confirmed details, a small test payment, and a route that does not pass through institutions known to refuse.
The first two cost minutes. Everything in this note costs more than that.
What no clause can allocate
The disruption. A clause can say who pays forty units of charges and cannot say who carries a fortnight without the money, the hours spent chasing it, or the obligations missed in the meantime.
Those land on whoever was relying on the payment, which is always the recipient, and no agreement redistributes them. That asymmetry is why prevention is worth more here than any term, and why the earlier notes in this section are the ones that actually help.
A clause is still worth having. It settles the small argument quickly so that the fortnight can be spent on the large problem.