Netting - 1992 ISDA Provision

From The Jolly Contrarian
Revision as of 22:33, 27 March 2020 by Amwelladmin (talk | contribs)
Jump to navigation Jump to search

1992 ISDA Master Agreement
A Jolly Contrarian owner’s manual™

Resources and navigation

Resources Wikitext | Nutshell wikitext | 2002 ISDA wikitext | 2002 vs 1992 Showdown | 2006 ISDA Definitions | 2008 ISDA
Navigation Preamble |

1(a) (b) (c) | 2(a) (b) (c) (d) (e) | 3(a) (b) (c) (d) (e) (f) | 4(a) (b) (c) (d) (e) | 55(a) Events of Default: 5(a)(i) Failure to Pay or Deliver 5(a)(ii) Breach of Agreement 5(a)(iii) Credit Support Default 5(a)(iv) Misrepresentation 5(a)(v) Default Under Specified Transaction 5(a)(vi) Cross Default 5(a)(vii) Bankruptcy 5(a)(viii) Merger Without Assumption 5(b) Termination Events: 5(b)(i) Illegality 5(b)(ii) Tax Event 5(b)(iii) Tax Event Upon Merger 5(b)(iv) Credit Event Upon Merger 5(b)(v) Additional Termination Event (c) | 6(a) (b) (c) (d) (e) | 7 | 8(a) (b) (c) (d) | 9(a) (b) (c) (d) (e) (f) (g) | 10 | 11 | 12(a) (b) | 13(a) (b) (c) (d) | 14 |

Index: Click to expand:

Section 2(c) in a Nutshell

Use at your own risk, campers!
2(c) Netting. If on any date amounts would otherwise be payable by each party to the other
(i) in the same currency; and
(ii) under the same Transaction,
then those obligations will be satisfied and replaced by an obligation on the party owing the larger amount to pay the difference. The parties may net payments across multiple specified Transactions by saying clause 2(c)(ii) will therefore not apply. This election may apply to different groups of Transactions, will apply separately to each pairing of specified Offices and will take effect as agreed between the parties.

Full text of Section 2(c)

2(c) Netting. If on any date amounts would otherwise be payable:—
(i) in the same currency; and
(ii) in respect of the same Transaction,
by each party to the other, then, on such date, each party’s obligation to make payment of any such amount will be automatically satisfied and discharged and, if the aggregate amount that would otherwise have been payable by one party exceeds the aggregate amount that would otherwise have been payable by the other party, replaced by an obligation upon the party by whom the larger aggregate amount would have been payable to pay to the other party the excess of the larger aggregate amount over the smaller aggregate amount. The parties may elect in respect of two or more Transactions that a net amount will be determined in respect of all amounts payable on the same date in the same currency in respect of such Transactions, regardless of whether such amounts are payable in respect of the same Transaction. The election may be made in the Schedule or a Confirmation by specifying that subparagraph (ii) above will not apply to the Transactions identified as being subject to the election, together with the starting date (in which case subparagraph 2(c)(ii) above will not, or will cease to, apply to such Transactions from such date). This election may be made separately for different groups of Transactions and will apply separately to each pairing of Offices through which the parties make and receive payments or deliveries.

Related agreements and comparisons

Related Agreements
Click here for the text of Section 2(c) in the 2002 ISDA
Comparisons
Click to compare this section in the 1992 ISDA and 2002 ISDA.

Tell me more
Sign up for our newsletter — or just get in touch: for ½ a weekly 🍺 you get to consult JC. Ask about it here.

Content and comparisons

Section 2(c) is about “settlement” or “payment” netting — that is, the operational settlement of offsetting payments due on any day under the normal operation of the Agreement — and not the more drastic close-out netting, which is the Early Termination of all Transactions under Section 6.

If you want to know more about close-out netting, see Single Agreement and Early Termination Amount.

We wonder what the point of this section is, since settlement netting is a factual operational process for performing existing legal obligations, rather than any kind of variation of the parties’ rights and obligations. If you owe me ten pounds and I owe you ten pounds, and we agree to both keep our tenners, what cause of action arises? What loss is there? We have settled our existing obligations differently.

To be sure, if I pay you your tenner and you don’t pay me mine, that’s a different story — but then there is no settlement netting at all. The only time one would wish to enforce settlement netting it must, ipso facto, have happened, so what do you think you’re going to court to enforce?

Template

Summary

Section 2(c) is about “settlement” or “payment” netting — that is, the operational settlement of offsetting payments due on any day under the normal operation of the Agreement — and not the more drastic close-out netting, which is the Early Termination of all Transactions under Section 6.

If you want to know more about close-out netting, see Single Agreement and Early Termination Amount.

We wonder what the point of this section is, since settlement netting is a factual operational process for performing existing legal obligations, rather than any kind of variation of the parties’ rights and obligations. If you owe me ten pounds and I owe you ten pounds, and we agree to both keep our tenners, what cause of action arises? What loss is there? We have settled our existing obligations differently.

To be sure, if I pay you your tenner and you don’t pay me mine, that’s a different story — but then there is no settlement netting at all. The only time one would wish to enforce settlement netting it must, ipso facto, have happened, so what do you think you’re going to court to enforce?

Template

General discussion

Transaction flows and collateral flows

In a fully margined ISDA Master Agreement, all other things being equal, the termination of a Transaction will lead to two equal and opposite effects:

The strict sequence of these payments ought to be that the Transaction termination payment goes first, and the collateral return follows, since it can only really be calculated and called once the termination payment has been made.

I know what you’re thinking. Hang on! that means the termination payer pays knowing this will increase its Exposure for the couple of days it will take for that collateral return to find its way back. That’s stupid!

What with the regulators’ obsession minimise systemic counterparty credit risk, wouldn’t it be better to apply some kind of settlement netting in anticipation, to keep the credit exposure down?

Now, dear reader, have you learned nothing? It might be better, but “better” is not how ISDA documentation rolls. The theory of the ISDA and CSA settlement flows puts the Transaction payment egg before the variation margin chicken so, at the moment, Transaction flows and collateral flows tend to be handled by different operations teams, and their systems don’t talk. Currently, the payer of a terminating transaction has its heart in its mouth for a day or so.

Industry efforts to date have been targeting at shortening the period between the Exposure calculation and the final payment of the collateral transfer.

Template

See also

Template

References