Template:M summ EUA Annex (d)(i): Difference between revisions
Amwelladmin (talk | contribs) No edit summary Tag: Manual revert |
Amwelladmin (talk | contribs) No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
=== {{euaprov|Settlement}} === | === {{euaprov|Settlement}} === | ||
{{ | {{Emissions transfer of allowances summ|euaprov}} | ||
=== {{euaprov|Delivery}} === | === {{euaprov|Delivery}} === | ||
{{M summ EUA Annex (d)(i)(2)}} | {{M summ EUA Annex (d)(i)(2)}} | ||
Latest revision as of 13:49, 17 October 2023
Settlement
Transfer from a specified Holding Account
Curious conditionality, across all three versions, where the Delivering Party specifies a Holding Account from which Allowances must be delivered, and not just the account to which they must be delivered. Quite why it should matter whence the Allowances come we cannot say — a vague fretfulness about theft perhaps? — but ok; let’s run with it.
Note, in any case, its moderation in IETA (5.2) whereby one has an obligation to make sure there are sufficient allowances in your account to satisfy your delivery obligation. So even though you can’t be forced to deliver from anywhere else, you can be sued for losses arising from your failure to ensure there was something to deliver in your Holding Account. All rather cack-handed, but in “fundamental upshot” terms, this does get to the right place.
The transfer is done once the Allowances hit the Receiving Party’s account (I know, I know: you don’t say.) But wait: there is an interesting use of the word “whereupon” here, upon which we dwell in a bit more detail in the premium section.
Delivery
All tediously quotidian, largely-goes-without-saying stuff, until you stumble over subparagraph (B) like an inattentive trail-runner not noticing a tree-root.
So:
(A)
Transfer from a specified Holding Account
Curious conditionality, across all three versions, where the Delivering Party specifies a Holding Account from which Allowances must be delivered, and not just the account to which they must be delivered. Quite why it should matter whence the Allowances come we cannot say — a vague fretfulness about theft perhaps? — but ok; let’s run with it.
Note, in any case, its moderation in IETA (5.2) whereby one has an obligation to make sure there are sufficient allowances in your account to satisfy your delivery obligation. So even though you can’t be forced to deliver from anywhere else, you can be sued for losses arising from your failure to ensure there was something to deliver in your Holding Account. All rather cack-handed, but in “fundamental upshot” terms, this does get to the right place.
The transfer is done once the Allowances hit the Receiving Party’s account (I know, I know: you don’t say.) But wait: there is an interesting use of the word “whereupon” here, upon which we dwell in a bit more detail in the premium section.
(B)
We’ll talk about (B) in the premium content section.
(C)
If the Receiving Party has designated multiple Specified Holding Accounts — as to why it would have multiple accounts, let alone specify them for a single Transaction we can provide no answer beyond basic bloody-minded perversity — but let’s just say — Delivering Party starts at the top and, if for some reason the first-named accounts are subject to some kind of disruption and the later ones are not — again, search us what might cause that — work its way down until it has delivered all EUAs. (If it gets to the bottom unfulfilled, see Settlement Disruption Event and Suspension Event).
(D)
If you deliver outside the normal window during business hours, your delivery is deemed satisfied at the next moment where a window on business hours opens. Workaday stuff that will be familiar with anyone who deals with the settlement of securities for a living.
But (B)? That’s weird. For more discussion on that, and a compare and contrast with the corresponding IETA provision, see the premium content.