Talk:Emissions Anatomy
EU Emissions Allowance Transaction Annex to the 2005 ISDA Commodity Definitions
A Jolly Contrarian owner’s manual™ Go premium
Crosscheck:
Suspension in a Nutshell™
Original text
Comparison See our natty emissions comparison table between the IETA, EFET and ISDA versions of emissions trading docs
Resources and Navigation
|
Comparisons
The definition of Suspension Event is more or less the same in all three emissions trading documentation regimes. Compare:
ISDA: Suspension Event
IETA: Suspension Event
EFET: Suspension Event
As an extra treat, here are some deltaviews:
IETA vs EFET: comparison
ISDA vs IETA: comparison
Basics
Someone’s mind got infested by nefarious phantoms, readers: either those of the collected carbon squads, or JC’s. We are not ruling out JC, to be clear. But this is too weird.
A Suspension Event happens when the official infrastructure falls over so that the parties can’t transfer Allowances to settle a Transaction. It is the fault of neither party — therefore to be distinguished from a Failure to Deliver, which generally will be. While there is overlap between Settlement Disruption Events and Suspension Events (in that both are things beyond the parties’ control) Suspension Event, being narrower and related to the failure of official infrastructure, trumps Settlement Disruption Event where they both apply to the same event. Generalia specialibus non derogant, I suppose.
Note the Long-Stop Date concept, which references 1 June in a year following a set of seemingly arbitrary two-year spells in the Fourth Compliance Period and relates only to Suspension Events, not Settlement Disruption Events, and also appears to bear no relation at all to the Reconciliation Deadline at the end of April in each year.
We have compared Settlement Disruption Events and Suspension Events here.
A curiosity to which the JC has not yet found a plausible answer is why there is a Cost of Carry adjustment for Suspension Events that run over the scheduled Delivery Date, but not for other, ordinary Settlement Disruption Events (or for that matter, Failures to Deliver).
There is no at-market termination provision at a “long-stop”
Also, there is the “then I woke up and it was all a dream” method of resolving irreconcilable suspensions. Unlike for Settlement Disruption Event, The Carbon Squad did not provide for “Payment on Termination for Suspension Event”.
We are baffled by this, as we have mentioned elsewhere: it defaults the position to one where the person who thought they had sold forward a risk finds, for reasons entirely beyond their control, that not only was that risk transfer ineffective, but the risk has come about and the asset is, effectively worth zero. If you consider the position of someone who was, for example, financing someone else’s Allowance allocation — hardly out of the question, since that is the point of a Forward Purchase Transaction — this is transparently the wrong outcome, since the Seller — the person who is borrowing against its Allowances — gets to keep the money. Madness.
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
- ↑ We think this number is superfluous, in that there is not a (II).
- ↑ Since ISDA’s crack drafting squad™ elected to express a mathematical proposition on its own tortured prose, it is not entirely clear what is meant to be divided by 360: the stray comma suggests maybe it is meant to be a denominator for the whole sum, but we think it makes more sense to divide only the Cost of Carry Delay by 360, as that gets you an annualised day count fraction that the rest of the sum can be multiplied by. If you ignored the ambiguous comma, that is the most consistent with the paragraph layout.