Merger Without Assumption - ISDA Provision: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{isdaanat|5(a)(viii)}}
{{nman|isda|2002|5(a)(viii)}}
When a firm merges into, or is taken over by, another, some magical — or unexpected — things can happen. Not for nothing does the {{isdama}} labour over the very description: that this might be a “[[consolidation]], [[amalgamation]], [[merger]], [[transfer]], [[reorganisation]], [[reincorporation]] or [[reconstitution]]” — prolix even by ISDA’s lofty standards — should tell you something. Generations of lawyers have forged whole careers out of the manifold ways one can put companies together and take them apart again. Your correspondent is not one of them, and has little more to say about it, except that what happens to live contracts at the time of such chicanery will depend alot on just how the companies or their assets are being joined or torn assunder. If the contracts carry across — which in a plain merger, they ought to — all well and good <ref>Though watch out for traps: what if ''both'' merging companies have {{isda}}s with the same counterparty, but on markedly different terms? Which prevails? Do they both? Which one do you use for new {{isdaprov|Transaction}}s? This you will have to hammer out across the negotiating table.</ref>
 
But in some cases the Transactions might not carry across. Perhaps the resulting entity has no [[Ultra vires|power]] to transact swaps. Perhaps it is in a jurisdiction in which that cannot be enforced. Perhaps it just refuses to honour them. {{isdaprov|Merger Without Assumption}} addresses that contingency.
This is the clause that would have been covered Section {{isdaprov|5(a(ii)}}(2) {{isdaprov|repudiation}}, ''had the resulting entity accepted the contract at all in the first place''. It can be triggered if:
*The resulting party repudiates ''any'' outstanding {{isdaprov|Transactions}} under the {{isdama}}; or
*(in the case of a transfer of assets) a small rump of {{isdaprov|Transactions}} are left in the original entity, and not transferred at to the new entity. Now you would think this ought to be covered by {{isdaprov|Credit Event Upon Merger}}, wouldn't you, because if there were no deterioration in credit and the transferring entity was still around and hadn’t winked out of existence then,
===And “[[all or substantially all]]” means?===
There's not a lot of [[case law]] on it. Some say 90%. Some say 75%. Some people — your correspondent included — say “shoot me”.
{{sa}}
{{ref}}

Latest revision as of 16:55, 14 August 2024

2002 ISDA Master Agreement

A Jolly Contrarian owner’s manual™

5(a)(viii) in a Nutshell

The JC’s Nutshell summary of this term has moved uptown to the subscription-only ninja tier. For the cost of ½ a weekly 🍺 you can get it here. Sign up at Substack. You can even ask questions! Ask about it here.

Original text

5(a)(viii) Merger Without Assumption. The party or any Credit Support Provider of such party consolidates or amalgamates with, or merges with or into, or transfers all or substantially all its assets to, or reorganises, reincorporates or reconstitutes into or as, another entity and, at the time of such consolidation, amalgamation, merger, transfer, reorganisation, reincorporation or reconstitution:―
5(a)(viii)(1) the resulting, surviving or transferee entity fails to assume all the obligations of such party or such Credit Support Provider under this Agreement or any Credit Support Document to which it or its predecessor was a party; or
5(a)(viii)(2) the benefits of any Credit Support Document fail to extend (without the consent of the other party) to the performance by such resulting, surviving or transferee entity of its obligations under this Agreement.
See ISDA Comparison for a comparison between the 1992 ISDA and the 2002 ISDA.
The Varieties of ISDA Experience
Subject 2002 (wikitext) 1992 (wikitext) 1987 (wikitext)
Preamble Pre Pre Pre
Interpretation 1 1 1
Obligns/Payment 2 2 2
Representations 3 3 3
Agreements 4 4 4
EODs & Term Events 5 Events of Default: FTPDBreachCSDMisrepDUSTCross DefaultBankruptcyMWA Termination Events: IllegalityFMTax EventTEUMCEUMATE 5 Events of Default: FTPDBreachCSDMisrepDUSTCross DefaultBankruptcyMWA Termination Events: IllegalityTax EventTEUMCEUMATE 5 Events of Default: FTPDBreachCSDMisrepDUSSCross DefaultBankruptcyMWA Termination Events: IllegalityTax EventTEUMCEUM
Early Termination 6 Early Termination: ET right on EODET right on TEEffect of DesignationCalculations; Payment DatePayments on ETSet-off 6 Early Termination: ET right on EODET right on TEEffect of DesignationCalculationsPayments on ETSet-off 6 Early Termination: ET right on EODET right on TEEffect of DesignationCalculationsPayments on ET
Transfer 7 7 7
Contractual Currency 8 8 8
Miscellaneous 9 9 9
Offices; Multibranch Parties 10 10 10
Expenses 11 11 11
Notices 12 12 12
Governing Law 13 13 13
Definitions 14 14 14
Schedule Schedule Schedule Schedule
Termination Provisions Part 1 Part 1 Part 1
Tax Representations Part 2 Part 2 Part 2
Documents for Delivery Part 3 Part 3 Part 3
Miscellaneous Part 4 Part 4 Part 4
Other Provisions Part 5 Part 5 Part 5

Resources and Navigation

Index: Click to expand:

Comparisons

Redlines


Discussion

ISDA’s crack drafting squad™ giveth and ISDA’s crack drafting squad™ taketh away.

In 1992, ISDA’s crack drafting squad™ added references to a party’s Credit Support Providers and Credit Support Documents — the 1987 ISDA did not have a concept of a Credit Support Provider at all (though it does contemplate Credit Support Documents).

In 2002 some further enhancements: ISDA’s crack drafting squad™ had contrived some different ways of describing how a company might reorganise itself (specifically, “reorganisation, reincorporation or reconstitution”). It also, uncharacteristically, deletes the text “by operation of law or pursuant to an agreement reasonably satisfactory to the other party to this Agreement”. This removes an unnecessary restriction on the foregoing event (the surviving entity failing to assume all the obligations under the ISDA) so makes sense: the squad here is just correcting its own verbal profligacy.

Basics

When a firm merges into, or is taken over by, another, some magical — or unexpected — things can happen. Not for nothing does the ISDA Master Agreement labour over the very description: that this might be a “consolidation, amalgamation, merger, transfer, reorganisation, reincorporation or reconstitution” — prolix even by the lofty standards of ISDA’s crack drafting squad™ — should tell you something. Generations of corporate lawyers have forged whole careers — some never leaving the confines of their law practices for forty or more years — out of the manifold ways one can put companies together and take them apart again.

Your correspondent is not one of those people and has little more to say about mergers, except that what happens to live contracts at the time of such chicanery will depend a lot on just how the companies and their assets are being joined together or torn assunder.

If the ISDA Master Agreement and its extant Transactions carry across — which, in a plain merger, they ought to — all well and good - though watch out for traps: what if both merging companies have ISDAs with the same counterparty, but on markedly different terms? Which prevails? Do they both? Which one do you use for new Transactions? This you will have to hammer out across the negotiating table.

But in some cases, Transactions might not carry across. Perhaps the resulting entity has no power to transact swaps. Perhaps it is in a jurisdiction in which they — or ISDA’s sainted close-out netting provisions, about which so many tears and so much blood is annually spilled — cannot be enforced. Perhaps the new entity just refuses to honour them.

Merger Without Assumption addresses all of these contingencies.

This is the clause that would have been covered by Section 5(a)(ii)(2) repudiation, had the resulting entity accepted the contract at all in the first place. It can be triggered if the resulting party repudiates any outstanding Transactions under the ISDA Master Agreement (or otherwise they are not binding on it); or any Credit Support Document stops working as a result of the merger.

Premium content
Here the free bit runs out. Subscribers click 👉 here. New readers sign up 👉 here and, for ½ a weekly 🍺 go full ninja about all these juicy topics👇

See also

References