Template:M gen 2002 ISDA 6(f)

Red letter day for ISDA’s crack drafting squad™

Whatever else you might have to say about ISDA’s set off provision — and as this page demonstrates, there’s quite a bit to say — one thing that stands out is how appallingly drafted it is.

The expression, “in circumstances where there is a Defaulting Party or where there is one Affected Party in the case where either a Credit Event Upon Merger has occurred or any other Termination Event in respect of which all outstanding Transactions are Affected Transactions has occurred” will make your head spin, but it is meant to strike two contingencies: All Transactions are being terminated, and one Party is at fault.

The ’squad’s own pedantic approach to drafting, which separates Events of Default from Termination Events, and describes the perpetrators differently (“Defaulting Party” for the former; “Affected Party” for the latter, is to blame here.

In any case one would only impose Section 6(f) set off where your counterparty has gone tetas arriba and you have terminated all Transactions.

Cross-affiliate set-off

The 2002 ISDA’s Set-off provision refers to a “Payer” and “Payee”. Since either the “Payer” or the “Payee” could be the Innocent Party, including Affiliates into the 2002 definition becomes problematic and cumbersome.

Generally, market practice is therefore to do the following:

• Where Affiliates are required: to use bespoke wording.
• Where Affiliates are not required: use the 2002 ISDA standard set-off wording above.

But cross affiliate set-off is a pretty rum affair in any case. Generally, set-off requires mutuality of payment, currency, time and counterparty, so setting off between affiliates is liable to challenge anyway (unless you have cross-guarantee arrangements). And in these modern days of bank recovery and resolution, conjoining claims between entities which are supposed to be siloed and independent isn’t really the thing.

Scope of Set-off

The 2002 ISDA set-off wording allows set-off following an Event of Default, CEUM, or any other Termination Event where there is one Affected Party and all outstanding transactions are Affected Transactions.

Often brokers will also want to set-off where there is an Illegality or ATE. There is no specific reference to all Transactions being Affected Transactions but this is implied in any set-off provision by its nature:

• If only some transactions are Affected Transactions and so only a portion of outstanding Transactions are being terminated then there is an on-going relationship and unilateral set-off is not appropriate.
• i.e., if you weren’t terminating all Transactions, it would be drastic and counterproductive to a relationship to use a set-off.
• As such, the Tax Event and Tax Event Upon Merger provisions (those not caught by your wording) are more likely to only affect certain transactions and not all Transactions and therefore set-off is not likely to be relevant in such instances.
• Force Majeure: The 1992 ISDA contains no Force Majeure provision. Commercially, it is not likely that an ISDA Master Agreement would be closed-out as a result of a Termination Event as these are generally viewed as non-fault and set-off would generally not be relevant.

• Illegality does allow either party to terminate but this is limited to all Affected Transactions which may not result in a close-out of the entire ISDA Master Agreement. In fact, the definition used of Affected Transactions makes it clear that in the cases of Illegality, Tax Event Upon Merger or Tax Event then it will only be transactions affected by the Termination Event that are closed-out. In relation to ATEs and CEUM this will be all Transactions and so set-off is relevant.