Operational Risk in a Forward Settlement Fails Scenario
A corporate client has a USD 20,000,000 outright forward to buy EUR and sell USD, settling T+2 with Bank X. On settlement day, the client's operations team discovers that Bank X has not received the USD leg because the client's payment was sent to an incorrect SWIFT BIC and is being returned. Bank X has already paid EUR to the client's account. The client's treasury must decide how to respond, manage the resulting exposure, and document the incident. The client's FX policy requires settlement risk monitoring, counterparty limits, and incident reporting within 24 hours. The EUR/USD rate has moved 0.8% against the client since the trade. The client's credit line with Bank X is USD 30,000,000.
1. Analyze the settlement risk and exposure created by the failed USD payment, and recommend immediate actions.
Read the worked answer
The client has received EUR but has not delivered USD, so it holds an unintended USD 20,000,000 obligation to Bank X and a EUR position it did not plan to hold. This is a settlement fail that creates: (1) counterparty credit exposure to Bank X for the EUR received (Bank X may demand return or payment); (2) funding risk, because the client must still fund USD 20,000,000, possibly at a higher cost; (3) market risk on the EUR received, since the client did not intend to hold EUR and the rate has moved 0.8% against it; (4) operational and reputational risk. Immediate actions: (1) contact Bank X immediately to explain the failed payment and confirm the EUR receipt; (2) instruct the bank to recall or reverse the returned USD payment and re-send to the correct BIC with same-day value if possible; (3) confirm whether Bank X will treat the payment as late and whether any compensation is due; (4) hedge or convert the EUR received to USD at current market to close the unintended position, documenting the cost; (5) check the credit line: USD 20,000,000 is within the USD 30,000,000 limit, but the exposure plus any other trades must be monitored; (6) report the incident under the 24-hour policy. The client should also verify whether the incorrect BIC was caused by an internal control failure (e.g., manual entry without dual verification).
2. Recommend the control improvements and the incident documentation the client should complete.
Read the worked answer
Control improvements: (1) implement dual verification of SWIFT BICs and account numbers against a static standing data file, with maker-checker; (2) use pre-validated settlement instructions and require confirmation with the counterparty before first payment; (3) automate payment matching and reconciliation between trade blotter and settlement system; (4) set settlement risk limits by counterparty and monitor intraday exposure, including Herstatt risk (paying out before receiving); (5) establish a fail-management procedure with escalation, contact lists, and cutoff times; (6) train operations staff on BIC validation and sanctions screening. Incident documentation: (1) timeline of the trade, payment instruction, error, discovery, and resolution; (2) root cause analysis (e.g., manual entry error, missing dual control); (3) financial impact, including any conversion loss, compensation, and funding cost; (4) counterparty communications and confirmations; (5) remediation actions with owners and deadlines; (6) sign-off by compliance and treasury. The documentation should be completed within the 24-hour policy and retained for audit. The client should also review whether the incident triggers regulatory reporting (e.g., operational risk event) and whether the counterparty relationship requires a formal apology or service credit. Finally, the client should test the new controls and update the FX policy to reflect lessons learned.