Standing settlement instructions for FX: protect the bank details that move currency principal

Standing settlement instructions, or SSIs, are the pre-agreed bank-account details used to settle recurring FX and other financial-market transactions with a counterparty. This guide explains the mechanics, evidence, risks and controls a UK business should understand before relying on the process.

What this means in practice

Standing settlement instructions, or SSIs, are the pre-agreed bank-account details used to settle recurring FX and other financial-market transactions with a counterparty. A useful control framework treats the topic as part of the transaction lifecycle rather than as technical terminology owned by one specialist.

Treasury and counterparties rely on SSIs to avoid re-entering bank details on every trade, which makes controlled maintenance and authenticated change procedures especially important. The working procedure should identify when the rule is tested, who owns the check and what happens if one condition is uncertain or fails.

How the process works

The operating sequence should start with the trigger, move through validation and approval, and end only when the external result is confirmed. For this topic, the critical mechanics are: Treasury and counterparties rely on SSIs to avoid re-entering bank details on every trade, which makes controlled maintenance and authenticated change procedures especially important.

Planning should work backwards from the required result rather than from the internal submission date. A correct instruction can still fail operationally if the company misses a notice period, scheme window, bank cut-off or response deadline.

The data and evidence that matter

The decision pack should bring together counterparty, currency, beneficiary bank, account or IBAN, intermediary details, effective date, source of instruction, independent verification and system update history. Keeping those facts in one place prevents treasury, legal, operations and accounting from reaching different conclusions from different versions of the same event.

Evidence should survive staff turnover. Material decisions should sit in the treasury, finance or workflow record rather than depend on one employee's private mailbox or memory of how a bank normally behaves.

Where the process can fail

A fraudulent or mistaken SSI change can redirect the full principal of an FX settlement even though the trade rate, amount and confirmation are otherwise correct. The exposure usually becomes more expensive to fix as the company gets closer to payment, settlement, testing or maturity.

Another weakness is assumption drift. A control that was correct for one bank, currency, subsidiary or document can become wrong after a migration or amendment, so the operating rule should be revalidated whenever the underlying service changes.

Worked example: test the mechanics

A company buys US$5 million for value Friday. On Wednesday an email appears to change the counterparty's dollar settlement account. Treasury should verify the SSI change through the agreed authenticated route before altering the master record, because the exposure is the settlement principal, not merely the FX margin.

The figures are illustrative, not universal terms. In a live case the company should replace every amount, date and threshold with the current bank, scheme or contractual evidence, then rerun the decision before cash is committed.

Governance and control design

Maintain SSIs as protected master data, segregate change approval from dealing and confirm unusual amendments through trusted counterparty contacts. Where systems allow, the rule should be enforced in workflow rather than left as a warning that a user can simply acknowledge and continue past.

Reporting should focus on SSI changes, independently verified changes, aged instructions and settlements using manual one-off bank details. That measure is more useful than raw transaction volume because it highlights the part of the process that can change liquidity, control or contractual compliance.

Senior review is most valuable where judgement remains. Automated validation can test formats and thresholds, but unusual legal, liquidity or counterparty facts still need an accountable person to decide whether proceeding is reasonable.

Ownership should also survive absence and staff turnover. The procedure should say who acts, who reviews, where evidence is stored and what happens if the normal owner cannot complete the step. For standing settlement instructions for fx, undocumented expert knowledge is itself an operational dependency.

Controls should be calibrated to materiality without creating blind spots. Low-value routine items may be handled automatically, but the system should still surface unusual patterns in SSI changes, independently verified changes, aged instructions and settlements using manual one-off bank details that justify human review before a larger exposure develops.

Documentation should be usable under deadline pressure. The operating checklist should point directly to counterparty, currency, beneficiary bank, account or IBAN, intermediary details, effective date, source of instruction, independent verification and system update history and state the stop condition in plain language, while the fuller policy can retain the legal, technical or scheme background.