What Should Your Treasury Swap Settlement Rules Specify?

What should your treasury swap settlement rules specify? Set them around when each payment becomes final, who releases it, and what happens if the other leg is late or fails. A swap can expose your treasury to principal risk when one asset leaves your control before the other arrives. The rulebook should make that gap explicit and limit it.

How do you define settlement finality?

Define finality separately for each leg: a bank payment may be final under its payment system’s rules, while a token transfer depends on the chain’s settlement behavior and your custody controls. Specify the exact asset, network, receiving address or account, value date, time zone and evidence required before marking the trade settled. A transaction hash or payment instruction alone may show that a transfer was initiated, not that the recipient has control of the asset.

Where the route supports payment-versus-payment settlement, make release of one leg conditional on the other settling. If the legs settle through separate systems without that protection, define the maximum time and amount your treasury may be exposed while waiting. A thor swap route is one example of why route choice and settlement conditions belong in the same operational decision; the mechanics merit a closer look when you compare transfer paths.

Which cutoffs and exception rules should you set?

Set a submission cutoff that leaves time for screening, approval and correction before the relevant payment or network window closes. State what happens when a cutoff is missed: defer both legs to the next permitted window, or cancel under a documented process. Specify who can approve a retry, how duplicate instructions are detected, and how counterparties are notified of a delay.

• Match both legs by counterparty, asset, amount, value date and trade reference before release.
• Define permitted amount tolerances, fees and treatment of partial fills.
• Require a named approver and a separate operator for manual releases or exceptions.
• Record settlement evidence, timestamps and reconciliation status in the treasury ledger.

Netting can reduce the amounts you need to transfer when obligations are eligible and matched, but it does not by itself make the remaining payments simultaneous. Document which trades can be netted, how disputes are resolved and whether the agreement and systems support that treatment. Keep a fallback route for outages, with its own limits and approval path rather than an informal override.

How should you cap settlement exposure?

Set counterparty and route limits for unsettled principal, and make escalation automatic when a delayed leg would breach either limit. Choose the smallest practical exposure window and require reconciliation before treasury treats the swap as complete. The next thing to watch is your next scheduled treasury-policy review: confirm that its cutoff, finality test and exposure cap still fit the routes you use.