Template:Failure to pay procedure: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
No edit summary
Line 5: Line 5:


So, you will need:
So, you will need:
*'''A failure''': A {{{{{1}}}|Failure to Pay or Deliver}}, on day '''T'''. This is an {{{{{1}}}|Event of Default}} under Section {{{{{1}}}|5(a)(i)}}. You must have:
====A failure====
::(i) a Failure by the {{{{{1}}}|Defaulting Party}} to make a payment or delivery when due;
A {{{{{1}}}|Failure to Pay or Deliver}}, by the {{{{{1}}}|Defaulting Party}} to make a payment or delivery when dueon day '''T'''. This is an {{{{{1}}}|Event of Default}} under Section {{{{{1}}}|5(a)(i)}}.  
::(ii) a notice by the {{{{{1}}}|Non-Defaulting Party}} under Section {{{{{1}}}|6(a)}} to the {{{{{1}}}|Defaulting Party}} that the failure ''has happened'' and designating an {{isdaprov|Early Termination Date}}, no more than twenty days in the future.
 
*'''Notice of failure''': The {{{{{1}}}|Non-defaulting Party}} must give notice of the {{{{{1}}}|Failure to Pay or Deliver}} (which since it is not due until the close of business on a given day, [[Q.E.D.]], can be validly given ''only after'' [[close of business]] on the due date for payment or delivery) and, by dint of Section {{{{{1}}}|12(a)}} ({{{{{1}}}|Notices}}), will only be deemed effective on the following {{{{{1}}}|Local Business Day}}: ie '''T+1'''. <ref>'''Spod’s note''': This notice requirement is key from a cross default perspective (if you have been indelicate enough to widen the scope of your [[cross default]] to include [[derivatives]], that is): if you don’t have it, ''any'' failure to pay under your {{isdama}}, however innocuous — even an operational oversight — automatically counts as an Event of Default, and gives a different person to the right to close ''their'' {{isdama}} with your Defaulting Party because of it defaulted to ''you'', even though (a) the Defaulting Party ''hasn’t'' defaulted to ''them'', and (b) you have decided not to take any action against the Defaulting Party yourself.</ref> Note also: you cannot send a close-out notice by [[email]], [[electronic messaging system]], or (if you have a {{1992ma}}, at any rate), by [[fax]]. The proper form is to have it hand-delivered by someone prepared to swear an affidavit as to when and where they delivered it to the {{isdaprov|Defaulting Party}}.
====Notice of failure====
*'''[[Grace Period]]''': Once the notice is effective, the {{{{{1}}}|Defaulting Party}} has a window (the [[grace period]]) in which it can remedy the failure to pay or deliver.  
The {{{{{1}}}|Non-defaulting Party}} must give the {{{{{1}}}|Defaulting Party}} notice under Section {{{{{1}}}|6(a)}} of the {{{{{1}}}|Failure to Pay or Deliver}} no more than twenty days in the future. The [[twenty Business Days]] restriction is a fun one that no-one has been able satisfactorily to explain to me.
 
Since payments and deliveries are generally due at [[close of business]] on a given day, [[Q.E.D.]], a Section {{{{{1}}}|6(a)}} notice of Failure to Pay or Deliver can usually only be given ''after'' [[close of business]] on the due date.
 
Thanks to Section {{{{{1}}}|12(a)}} ({{{{{1}}}|Notices}}), the Section {{{{{1}}}|6(a)}} notice will only be effective on the following {{{{{1}}}|Local Business Day}}: i.e., '''T+1'''. <ref>'''Spod’s note''': This notice requirement is key from a [[cross default]] perspective (if you have been indelicate enough to widen the scope of your [[cross default]] to include [[derivatives]], that is): if you don’t have it, ''any'' failure to pay under your {{isdama}}, however innocuous — even an operational oversight — automatically counts as an Event of Default, and gives a different person to the right to close ''their'' {{isdama}} with your Defaulting Party because of it defaulted to ''you'', even though (a) the Defaulting Party ''hasn’t'' defaulted to ''them'', and (b) you have decided not to take any action against the Defaulting Party yourself.</ref> Note also: you cannot send a close-out notice by [[email]], [[electronic messaging system]], or (if you have a {{1992ma}}, at any rate), by [[fax]]. The proper form is to have it hand-delivered by someone prepared to swear an affidavit as to when and where they delivered it to the {{isdaprov|Defaulting Party}}.
 
====[[Grace period]]====
Once your Section {{{{{1}}}|6(a)}} notice is effective, the {{{{{1}}}|Defaulting Party}} has a window (the [[grace period]]) in which it can remedy the failure to pay or deliver.  
:(i) The standard [[grace period]]s are set out in Section {{{{{1}}}|5(a)(i)}}. Be careful here: under a {{2002ma}} the standard is '''''one''''' {{isdaprov|Local Business Day}}. Under the {{1992ma}} the standard is '''''three''''' {{isda92prov|Local Business Day}}s. ''But check the {{{{{1}}}|Schedule}}'' because in either case this is the sort of thing that counterparties adjust: {{2002ma}}s are often adjusted to conform to the {{1992ma}} standard of three {{{{{1}}}|LBD}}s, for example.  
:(i) The standard [[grace period]]s are set out in Section {{{{{1}}}|5(a)(i)}}. Be careful here: under a {{2002ma}} the standard is '''''one''''' {{isdaprov|Local Business Day}}. Under the {{1992ma}} the standard is '''''three''''' {{isda92prov|Local Business Day}}s. ''But check the {{{{{1}}}|Schedule}}'' because in either case this is the sort of thing that counterparties adjust: {{2002ma}}s are often adjusted to conform to the {{1992ma}} standard of three {{{{{1}}}|LBD}}s, for example.  
:(ii) So: once you have a clear, notified {{{{{1}}}|Failure to Pay or Deliver}}, you have to wait ''at least'' one and possibly three or more {{{{{1}}}|Local Business Day}}s before doing anything about it. Therefore you are on tenterhooks until the [[close of business]] '''T+2''' {{{{{1}}}|LBD}}s (standard {{2002ma}}), or '''T+4''' {{isda92prov|LBD}}s (standard {{1992ma}}).  
:(ii) So: once you have a clear, notified {{{{{1}}}|Failure to Pay or Deliver}}, you have to wait ''at least'' one and possibly three or more {{{{{1}}}|Local Business Day}}s before doing anything about it. Therefore you are on tenterhooks until the [[close of business]] '''T+2''' {{{{{1}}}|LBD}}s (standard {{2002ma}}), or '''T+4''' {{isda92prov|LBD}}s (standard {{1992ma}}).  

Revision as of 16:25, 26 July 2021

Closing out an ISDA Master Agreement following an Event of Default

Here is the JC’s handy guide to closing out an ISDA Master Agreement. We have assumed you are closing out as a result of a {{{{{1}}}|Failure to Pay or Deliver}} under Section {{{{{1}}}|5(a)(i)}}, because — unless you have inadvertently crossed some portal, wormhole into a parallel but stupider universe — if an ISDA Master Agreement had gone toes-up, that’s almost certainly why. That, or at a pinch {{{{{1}}}|Bankruptcy}}. Don’t try telling your credit officers this, by the way: they won’t believe you — and they tend to get a bit wounded at the suggestion that their beloved NAV triggers are a waste of space.

In what follows “Close-out Amount” means, well, “Close-out Amount” (if under a 2002 ISDA) or “Loss” or “Market Quotation” amount (if under a 1992 ISDA), and “{{{{{1}}}|Early Termination Amount}}” means, for the 1992 ISDA, which neglected to give this key value a memorable name, “the amount, if any, payable in respect of an {{{{{1}}}|Early Termination Date}} and determined pursuant to Section 6(e)”.

So, you will need:

A failure

A {{{{{1}}}|Failure to Pay or Deliver}}, by the {{{{{1}}}|Defaulting Party}} to make a payment or delivery when dueon day T. This is an {{{{{1}}}|Event of Default}} under Section {{{{{1}}}|5(a)(i)}}.

Notice of failure

The {{{{{1}}}|Non-defaulting Party}} must give the {{{{{1}}}|Defaulting Party}} notice under Section {{{{{1}}}|6(a)}} of the {{{{{1}}}|Failure to Pay or Deliver}} no more than twenty days in the future. The twenty Business Days restriction is a fun one that no-one has been able satisfactorily to explain to me.

Since payments and deliveries are generally due at close of business on a given day, Q.E.D., a Section {{{{{1}}}|6(a)}} notice of Failure to Pay or Deliver can usually only be given after close of business on the due date.

Thanks to Section {{{{{1}}}|12(a)}} ({{{{{1}}}|Notices}}), the Section {{{{{1}}}|6(a)}} notice will only be effective on the following {{{{{1}}}|Local Business Day}}: i.e., T+1. [1] Note also: you cannot send a close-out notice by email, electronic messaging system, or (if you have a 1992 ISDA, at any rate), by fax. The proper form is to have it hand-delivered by someone prepared to swear an affidavit as to when and where they delivered it to the Defaulting Party.

Grace period

Once your Section {{{{{1}}}|6(a)}} notice is effective, the {{{{{1}}}|Defaulting Party}} has a window (the “grace period”) in which it can remedy the failure to pay or deliver.

(i) The standard grace periods are set out in Section {{{{{1}}}|5(a)(i)}}. Be careful here: under a 2002 ISDA the standard is one Local Business Day. Under the 1992 ISDA the standard is three Local Business Days. But check the {{{{{1}}}|Schedule}} because in either case this is the sort of thing that counterparties adjust: 2002 ISDAs are often adjusted to conform to the 1992 ISDA standard of three {{{{{1}}}|LBD}}s, for example.
(ii) So: once you have a clear, notified {{{{{1}}}|Failure to Pay or Deliver}}, you have to wait at least one and possibly three or more {{{{{1}}}|Local Business Day}}s before doing anything about it. Therefore you are on tenterhooks until the close of business T+2 {{{{{1}}}|LBD}}s (standard 2002 ISDA), or T+4 LBDs (standard 1992 ISDA).
(iii) At the expiry of this grace period, you finally have a fully operational {{{{{1}}}|Event of Default}}. Now Section {{{{{1}}}|6(a)}} gives you the right, by not more than 20 days’ notice[2] to designate an {{{{{1}}}|Early Termination Date}} for all outstanding Transactions. So, at some point in the next twenty days.
(iv) For this we go to Section {{{{{1}}}|6(e)}}, noting as we fly over it, that Section {{{{{1}}}|6(c)}} reminds us for the avoidance of doubt that even if the {{{{{1}}}|Event of Default}} which triggers the {{{{{1}}}|Early Termination Date}} evaporates in the meantime — these things happen, okay? — yon {{{{{1}}}|Defaulting Party}}’s goose is still irretrievably cooked. For it not to be (i.e., if Credit suddenly gets executioner’s remorse and wants to let the {{{{{1}}}|Defaulting Party}} off), the {{{{{1}}}|Non-defaulting Party}} will have to expressly terminate the close-out process, preferably by written notice. There’s an argument — though it is hard to picture the time or place on God’s green earth where a {{{{{1}}}|Defaulting Party}} would make it — that cancelling an in-flight close out is no longer exclusively in the {{{{{1}}}|Defaulting Party}}’s gift, and requires the {{{{{1}}}|NDP}}’s consent. It would be an odd, self-harming kind of {{{{{1}}}|Defaulting Party}} that would run that argument unless the market was properly gyrating.
  • Determining Close-out Amounts[3]: There is a bit of a chicken licken-and-egg situation here as you must now ascertain termination values for the {{{{{1}}}|Terminated Transaction}}s as of the Early Termination Date per the methodology set out in Section {{{{{1}}}|6(e)(i)}}, but you can’t really work out their mark-to-market values for that date at any time before that date, unless you are able to see into the future or something. Anyway, that’s a conundrum for your trading people (and in-house metaphysicians) to deal with and it need not trouble we eagles of the law. For our purposes, the trading and risk people need to come up with Close-out Amounts[4] for all outstanding {{{{{1}}}|Transaction}}s. Once they have done that you are ready for your Section {{{{{1}}}|6(e)}} notice.
  • {{{{{1}}}|Early Termination Amount}}: Your inhouse metaphysicians having calculated your Close-out Amounts, you must assemble all the values into an {{{{{1}}}|Early Termination Amount}}.[5]
  1. Spod’s note: This notice requirement is key from a cross default perspective (if you have been indelicate enough to widen the scope of your cross default to include derivatives, that is): if you don’t have it, any failure to pay under your ISDA Master Agreement, however innocuous — even an operational oversight — automatically counts as an Event of Default, and gives a different person to the right to close their ISDA Master Agreement with your Defaulting Party because of it defaulted to you, even though (a) the Defaulting Party hasn’t defaulted to them, and (b) you have decided not to take any action against the Defaulting Party yourself.
  2. See discussion on at Section 6(a) about the silliness of that time limit.
  3. Or their equivalents under the 1992 ISDA, of course.
  4. See previous footnote.
  5. Or, in the 1992 ISDA’s estimable prose, “the amount, if any, payable in respect of an Early Termination Date and determined pursuant to this Section”.