Credit Event Upon Merger - ISDA Provision

From The Jolly Contrarian
Revision as of 11:18, 12 April 2020 by Amwelladmin (talk | contribs) (Replaced content with "{{manual|MI|2002|5(b)(v)|Section|5(b)(v)|medium}}")
Jump to navigation Jump to search

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

Resources and navigation

[[{{{1}}} - 1992 ISDA Provision|This provision in the 1992]]

Resources Wikitext | Nutshell wikitext | 1992 ISDA wikitext | 2002 vs 1992 Showdown | 2006 ISDA Definitions | 2008 ISDA | JC’s ISDA code project
Navigation Preamble | 1(a) (b) (c) | 2(a) (b) (c) (d) | 3(a) (b) (c) (d) (e) (f) (g) | 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) Force Majeure Event 5(b)(iii) Tax Event 5(b)(iv) Tax Event Upon Merger 5(b)(v) Credit Event Upon Merger 5(b)(vi) Additional Termination Event (c) (d) (e) | 6(a) (b) (c) (d) (e) (f) | 7 | 8(a) (b) (c) (d) | 9(a) (b) (c) (d) (e) (f) (g) (h) | 10 | 11 | 12(a) (b) | 13(a) (b) (c) (d) | 14 |

Index: Click to expand:

Section 5(b)(v) in a Nutshell

Use at your own risk, campers!
5(b)(v) Credit Event Upon Merger. If “Credit Event Upon Merger” applies and it or any of its Credit Support Providers or Specified Entities suffers a Designated Event (which is not a Merger Without Assumption) and the relevant entity’s (which will be the Affected Party) creditworthiness is materially weaker as a result.
A “Designated Event” means that the relevant entity:―
(1) merges with, or transfers substantially all of its assets into, or reorganises itself as another entity;
(2) comes under the effective voting control of another entity; or
(3) makes a substantial change in its capital structure by issuing or guaranteeing debt, equities or analogous interests, or securities convertible into them;

Full text of Section 5(b)(v)

5(b)(v) Credit Event Upon Merger. If “Credit Event Upon Merger” is specified in the Schedule as applying to the party, a Designated Event (as defined below) occurs with respect to such party, any Credit Support Provider of such party or any applicable Specified Entity of such party (in each case, “X”) and such Designated Event does not constitute a Merger Without Assumption, and the creditworthiness of X or, if applicable, the successor, surviving or transferee entity of X, after taking into account any applicable Credit Support Document, is materially weaker immediately after the occurrence of such Designated Event than that of X immediately prior to the occurrence of such Designated Event (and, in any such event, such party or its successor, surviving or transferee entity, as appropriate, will be the Affected Party).
A “Designated Event” with respect to X means that:―
(1) X consolidates or amalgamates with, or merges with or into, or transfers all or substantially all its assets (or any substantial part of the assets comprising the business conducted by X as of the date of this ISDA Master Agreement) to, or reorganises, reincorporates or reconstitutes into or as, another entity;
(2) any person, related group of persons or entity acquires directly or indirectly the beneficial ownership of (A) equity securities having the power to elect a majority of the board of directors (or its equivalent) of X or (B) any other ownership interest enabling it to exercise control of X; or
(3) X effects any substantial change in its capital structure by means of the issuance, incurrence or guarantee of debt or the issuance of (A) preferred stock or other securities convertible into or exchangeable for debt or preferred stock or (B) in the case of entities other than corporations, any other form of ownership interest; or

Related agreements and comparisons

Click here for the text of Section 5(b)(v) in the 1992 ISDA
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

Numbering Discrepancy: Note the numbering discrepancy in Section 5(b) between the 1992 ISDA and 2002 ISDA. This is caused by a new 5(b)(ii) (Force Majeure Event) in the 2002 ISDA before Tax Event, which is thus shunted from Section 5(b)(ii) (in the 1992 ISDA) to Section 5(b)(iii) (in the 2002 ISDA).

First established in the 1987 ISDA, CEUM was gently upgraded for the 1992 ISDA to include Credit Support Providers and Specified Entities, and to clarify who, upon such a merger, is the Affected Party, as per this comparison.

It then had quite the overhaul of Credit Event Upon Merger between 1992 ISDA and 2002 ISDA as this comparison illustrates.

Designated Event is part of the definition of Credit Event Upon Merger in the 2002 ISDA, and doesn’t have an equivalent in the 1992 ISDA nor, obviously enough,the 1987 ISDA.

The 2002 ISDA introduced the “Designated Event” in an attempt to define more forensically the sorts of corporate events that should be covered by CEUM. They are notoriously difficult to pin down. Even before the 2002 ISDA was published, it was common to upgrade the 1992 ISDA formulation to something resembling the glorious concoction that became Section 5(b)(v) of the 2002 ISDA. The 1992 wording is a bit lame. On the other hand, you could count the number of times an ISDA Master Agreement is closed out purely on account of Credit Event Upon Merger on the fingers of one hand, even if you had lost all the fingers on that hand to an industrial accident.

So — yeah.

Template

Summary

Known among the cognoscenti as “CEUM”, the same way Tax Event Upon Merger is a “TEUM”. No idea how you pronounce it, but since ISDA ninjas communicate only in long, appended, multicoloured emails and never actually speak to each other, it doesn’t matter.

Pay attention to the interplay between this section and Section 7(a) (Transfer). You should not need to amend Section 7(a) (for example to require equivalence of credit quality of any transferee entity etc., because that is managed by CEUM.

Note also the interrelationship between CEUM and a Ratings Downgrade Additional Termination Event, should there be one. One can be forgiven for feeling a little ambivalent about CEUM because it is either caught by Ratings Downgrade or, if there is no requirement for a general Ratings Downgrade, insisting on CEUM seems a bit arbitrary (i.e. why do you care about a downgrade as a result of a merger, but not any other ratings downgrade?)

Template

General discussion

Template:M gen 2002 ISDA 5(b)(v)

Template

See also

Template

References