Same-Day FX Settlement Does Not Protect Both Currency Legs

An afternoon customer payout run needs dollars. Treasury has booked a euro-to-dollar conversion for settlement that morning. Both currency payments are due today. That sounds like a funding plan—but it says little about what happens if the euro payment becomes irrevocable and the dollars never arrive.

Same-day settlement is a timing commitment, not a description of how the two currency legs are protected. For a payments lead, the decisive question is whether the business can finally pay away one currency without finally receiving the other. A second question follows: even if that exchange is protected, what funds the payout run if the trade fails to settle?

A shared settlement date can hide an exposure window

Consider a hypothetical payment provider selling €1 million for $1.1 million, with no fees. Its euro payment can no longer reliably be cancelled at 10:00. Final receipt of the dollars is expected at 11:00, ahead of a 15:00 customer payout run.

If these are independent payments, the provider has principal exposure from 10:00 until the dollars are finally received. If the counterparty fails to deliver them after the euros have been paid, the provider could lose the €1 million it sold—not merely the cost of an adverse exchange-rate movement.

The starting point matters. The Basel Committee, in its bank-focused guidance, explains that exposure begins when cancellation is no longer certain. That can precede the visible account debit and can even fall before the FX settlement date.

If both payments complete as expected, the exposure in this example lasts an hour. Successful completion does not mean the exposure never existed. If the dollars arrive late, the window extends—and the payout schedule may also be threatened.

Payment settlement time answers a scheduling question; it does not, by itself, answer the principal-protection question. T+0 tells treasury that settlement is scheduled for the trade date. It does not establish what prevents one currency from being delivered without the other.

The protection comes from linked finality

Payment versus payment, or PvP, changes the relationship between the two legs. As described by the BIS, final transfer of one currency occurs if and only if final transfer of the other occurs.

“Final” means irrevocable and unconditional. A payment instruction, a confirmation or a scheduled receipt is not the same thing. In the hypothetical trade, genuine PvP protection means the provider’s final euro transfer is conditional on the final dollar transfer. Two independent payments scheduled for 11:00 do not provide that safeguard, however confidently their completion times are quoted.

This is why speed and protection need separate specifications. A later exchange settled through PvP can have principal protection that a same-day exchange of independent payments lacks. That is not an argument for slower funding; it is an argument against treating a faster timetable as a substitute for a protected exchange.

The protection must also cover the payment provider’s own exchange. A settlement partner’s participation in a PvP arrangement does not automatically establish that every customer transaction has the same protection. Basel’s guidance identifies possible principal exposure through indirect access, including where internal currency entries are not conditional on their corresponding entries. Moving both currencies across one institution’s books is not sufficient evidence either.

The useful question for a settlement partner is therefore specific: where does our sold-currency payment become irrevocable, where does our bought-currency receipt become final, and what makes those events conditional on each other?

Protected principal is not the same as funded payouts

PvP addresses the risk of losing the currency paid away in the exchange it covers. It does not guarantee that the trade will settle—or that treasury will have the currency required for its next obligation.

In the basic PvP arrangement described by Basel, if the counterparty fails to pay in, the selling party receives its original currency back. That is a materially better outcome than losing the principal. But our payment provider needs $1.1 million for its customers, not the return of €1 million. Until it borrows dollars or replaces the trade, it is short the full dollar requirement.

Assume the euros are returned early enough to arrange another conversion. If the replacement rate has moved from $1.10 to $1.09 per euro, the same €1 million now buys $1.09 million—$10,000 less than the payout run requires, still ignoring fees. The original principal has been preserved, but replacing the trade now leaves an additional funding requirement.

That example separates two problems. Liquidity risk concerns obtaining the required dollars in time; replacement-cost risk concerns an adverse price for obtaining them. Even with no exchange-rate movement, a failed trade can leave treasury unable to meet the payout deadline. Conversely, an available replacement trade may solve the timing problem at a cost.

There is also a distinction between settlement time and payout time. Final receipt at the FX settlement point is not automatically beneficiary credit and funds availability. Depending on the payment flow, the dollars may still need to reach the account or route used for customer payouts.

A useful funding plan therefore identifies the latest point at which the dollars must be usable for the run, not just the promised FX completion time. It also establishes whether fallback dollar funding can be accessed before that point. Recovering euros is not itself a dollar contingency plan.

Netting reduces the amount, not the need for protection

Pre-settlement obligation netting can reduce how much currency counterparties must exchange by offsetting obligations before payment. Where the netting is legally sound and enforceable, it can reduce the size of principal exposure.

But the remaining payments still need their own settlement protection. If a net euro payment becomes irrevocable before the net dollar receipt is final, the provider can still be exposed on that residual exchange. The amount at risk may be smaller; the reason it is at risk has not changed.

Netting changes how much needs to move. PvP changes the conditions under which it moves. A settlement proposal that emphasises reduced funding requirements has answered a useful question, but not the whole question. Treasury still needs to know whether the remaining currency legs are conditional on each other.

Conclusion

For FX that funds customer payouts, treat the completion deadline, principal protection and fallback liquidity as separate requirements. Same-day settlement supplies a timetable. PvP protects the covered exchange against paying one currency without receiving the other. Neither alone ensures the required currency will be available for the payout run when customers need it.

For requesting more information about how we can help reach out to us. We're here to help and answer any questions you may have.

Contact us!