Template:M summ EUA Annex Settlement Disruption and Suspension: Difference between revisions
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) |
||
| Line 9: | Line 9: | ||
===Delayed performance=== | ===Delayed performance=== | ||
Once the event is overcome the parties must resume their obligations: for a {{euaprov|Settlement Disruption Event}}, within two {{euaprov|Delivery Business Days}}; for a {{euaprov|Suspension Event}}, within 10 {{euaprov|Delivery Business Days}}, but | Once the event is overcome the parties must resume their obligations: for a {{euaprov|Settlement Disruption Event}}, within two {{euaprov|Delivery Business Days}}; for a {{euaprov|Suspension Event}}, within 10 {{euaprov|Delivery Business Days}} — the fossil record does not reflect ''what'' the ’squad was thinking when it drew that distinction, but we must assume it was thinking something — for Suspension Events it underwent the exercise of crafting a tiresome waterfall of intermediate deadlines depending on whether the {{euaprov|Suspension Event}} coincides with an {{euaprov|End of Phase Reconciliation Deadline}}. You wouldn—t do ''that'' just for the giggles. Well, ''I'' wouldn’t. | ||
The {{euaprov|Suspension Event}} contemplates an additional {{euaprov|Cost of Carry Amount}} payment | The {{euaprov|Suspension Event}} also contemplates an the cash payer paying an additional {{euaprov|Cost of Carry Amount}} payment, and again the ’squad’s logic here does not leap off the page. If anyone happens to know, do write in. | ||
==={{euaprov|Continuing Settlement Disruption Event}}s=== | ==={{euaprov|Continuing Settlement Disruption Event}}s=== | ||
Now things start getting properly baroque. Settlement disruption contemplates the scenario where the disruption stretches out past the original scheduled {{euaprov|Delivery Date}}. After this time of course we must deal with the phantoms and succubi of unexpected reconciliation deadlines, end of phase reconciliation deadlines which of course we are not within the parties’ original contemplation, the original {{euaprov|Delivery Date}} scheduled to occur before any of these could happen. At the end of a period not longer than nine {{euaprov|Delivery Business Days}} after the original {{euaprov|Delivery Date}}, an “{{isdaprov|Illegality}}” {{isdaprov|Termination Event}} will be deemed to occur. | Now things start getting properly baroque. Settlement disruption contemplates the scenario where the disruption stretches out past the original scheduled {{euaprov|Delivery Date}}. After this time of course we must deal with the phantoms and succubi of unexpected reconciliation deadlines, end of phase reconciliation deadlines which of course we are not within the parties’ original contemplation, the original {{euaprov|Delivery Date}} scheduled to occur before any of these could happen. At the end of a period not longer than nine {{euaprov|Delivery Business Days}} after the original {{euaprov|Delivery Date}}, an “{{isdaprov|Illegality}}” {{isdaprov|Termination Event}} will be deemed to occur. | ||
Revision as of 15:43, 12 April 2023
Priority
The same event can be a Settlement Disruption Event and a Suspension Event: both are events beyond the control of the counterparties and for which neither is at fault (in contrast to Failure to Deliver); however as Suspension Event is narrower, relating only to the failure of formal regulatory infrastructure in which the EUAs are held and registered, has priority over the wider Settlement Disruption Event (which would take in general market settlement issues) if the same event could otherwise be both.
Notification
Either party can notify a Settlement Disruption Event; only the party affected by a Suspension Event is required to give notice. Again, we suppose this has something to do with the more general nature of settlement disruption events.
Effect of event
In each case the practical upshot of the event is that the parties’ respective obligations are suspended. The parties have to try to overcome a Settlement Disruption Event; it being realistically beyond their gift to overcome a Suspension Event, they are not required to do that.
Delayed performance
Once the event is overcome the parties must resume their obligations: for a Settlement Disruption Event, within two Delivery Business Days; for a Suspension Event, within 10 Delivery Business Days — the fossil record does not reflect what the ’squad was thinking when it drew that distinction, but we must assume it was thinking something — for Suspension Events it underwent the exercise of crafting a tiresome waterfall of intermediate deadlines depending on whether the Suspension Event coincides with an End of Phase Reconciliation Deadline. You wouldn—t do that just for the giggles. Well, I wouldn’t.
The Suspension Event also contemplates an the cash payer paying an additional Cost of Carry Amount payment, and again the ’squad’s logic here does not leap off the page. If anyone happens to know, do write in.
Continuing Settlement Disruption Events
Now things start getting properly baroque. Settlement disruption contemplates the scenario where the disruption stretches out past the original scheduled Delivery Date. After this time of course we must deal with the phantoms and succubi of unexpected reconciliation deadlines, end of phase reconciliation deadlines which of course we are not within the parties’ original contemplation, the original Delivery Date scheduled to occur before any of these could happen. At the end of a period not longer than nine Delivery Business Days after the original Delivery Date, an “Illegality” Termination Event will be deemed to occur.