Merger Without Assumption - ISDA Provision: Difference between revisions
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
{{isdaanat|5(a)(viii)}} | {{isdaanat|5(a)(viii)}} | ||
This can be triggered if: | 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 | *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, | *(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?=== | ===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”. | 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}} |
Revision as of 13:46, 2 August 2019
ISDA Anatomy™
view template
view template
|
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 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 [1]
But in some cases the Transactions might not carry across. Perhaps the resulting entity has no power to transact swaps. Perhaps it is in a jurisdiction in which that cannot be enforced. Perhaps it just refuses to honour them. Merger Without Assumption addresses that contingency. This is the clause that would have been covered 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
- (in the case of a transfer of assets) a small rump of 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 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”.
See also
References
- ↑ 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.