82,903
edits
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
(22 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
=== | ====The problem with bilateral agreements==== | ||
As we have remarked before, most financing contracts are decidedly one-sided. One party — the dealer, broker, bank: we lump these various financial service providers together as ''The Man'' — provides services, lends money, creates risk outcomes; the other — the customer — consumes them. Generally, the customer presents risks to The Man and not vice versa. All the weaponry is therefore pointed in one direction: the customer’s. It almost goes without saying that should the customer “run out of road”, the Man stands to ''lose'' something. | |||
Even though the ISDA is also, in practice, a “risk creation contract” having these same characteristics, it is not, in theory, designed like one. Seeing the dealer and the customer for what they are involves seeing a rather bigger picture. In the small picture — the ISDA agreement proper — either party can be out of the money, and either party can blow up. The weaponry points both ways. | |||
This presented the First Men with an unusual scenario when they were designing the {{isdama}}: what happens if ''you'' blow up when ''I'' owe money to you? Here I might not want to crystalise my contract: since it will involve me paying you a mark-to-market amount I hadn’t budgeted for I might not even be able to. (This is less of a concern in these days of mandatory bilateral variation margin, but the {{isdama}} was forged well before this modern era). | |||
This | The answer the [[First Men]] came up with was the “flawed asset” provision of Section {{{{{1}}}|2(a)(iii)}}. This allows an innocent, but out-of-the-money, party faced with its counterparty’s default not to close out the ISDA, but to just freeze its obligations, and do nothing until the situation is resolved. | ||
There is an argument it wasn’t a good idea then; there is a better argument it isn’t a good idea now, but like so many parts of this sacred form it is there and, for hundreds and thousands of ISDA trading arrangements, we are stuck with it. | |||
====Flawed assets generally==== | |||
{{Flawed asset capsule|{{{1}}}}} | |||
====Does not apply to {{{{{1}}}|Termination Events}}==== | |||
Since most {{isdama}}s that reach the life support machine in an ICU get there by dint of a {{{{{1}}}|Failure to Pay}} or {{{{{1}}}|Bankruptcy}} this does not, in point of fact, amount to much, but it is worth noting that while {{{{{1}}}|Event of Default}}s — and even events that are not yet but with the passing of time might ''become'' {{{{{1}}}|Events of Default}} — can, without formal action by the {{{{{1}}}|non-Defaulting Party}} trigger a {{{{{1}}}|2(a)(iii)}} suspension, a mere Section {{{{{1}}}|5(b)}} {{{{{1}}}|Termination Event}} — even a catastrophic one like an {{{{{1}}}|Additional Termination Event}} (such as a [[NAV trigger]], [[Key person clause|key person event]] or some such) — cannot, until the {{{{{1}}}|Transaction}} has been formally terminated, at which point it really ought to go without saying. | |||
This might rile and unnerve [[credit officer]]s — by nature an easily perturbed lot — but given our arguments below for what a train wreck the whole {{{{{1}}}|2(a)(iii)}} thing is, those of stabler personalities will consider this in the round a good thing. | |||
Nevertheless the [[JC]] has seen valiant efforts to insert {{{{{1}}}|Additional Termination Events}} to section {{{{{1}}}|2(a)(iii)}}, and — ''quel horreur'' — ''Potential'' {{{{{1}}}|Additional Termination Event}}s, a class of things that does not exist outside the laboratory, and must therefore be defined. All this for the joy of invoking a clause that doesn’t make any sense in the first place. | |||
=== | |||
{{ | “Some things are better left unsaid,” said no [[ISDA ninja]] ever. | ||
====“No Early Termination Date ... has occurred”...==== | |||
New in the {{1992ma}} was the second condition precedent, that “...no Early Termination Date in respect of the relevant Transaction has occurred or been effectively designated”. | |||
This is tidy-up material to bring ''triggered'' {{{{{1}}}|Termination Event}}s into scope. There is a period between notice of termination and when the {{{{{1}}}|Early Termination Date}} is actually designated to happen — and in a busy ISDA it could be a pretty long period — during which time the {{{{{1}}}|Transaction}} is still on foot and going, albeit headed inexorably at a brick wall. |