Template:M comp disc EFET Allowance Annex 7.1: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
(Created page with "Functionally, the definition of Force Majeure is the same in the EFET and IETA versions. Here is a {{diff|77069|77068}}: the differences are to account for the architecture and nomenclature of the different master agreements, though the IETA has a conflict clause favouring Suspension Event over Force Majeure/Settlement Disruption Event, which the EFET does not.")
 
No edit summary
Line 1: Line 1:
Functionally, the definition of Force Majeure is the same in the EFET and IETA versions. Here is a {{diff|77069|77068}}: the differences are to account for the architecture and nomenclature of the different master agreements, though the IETA has a conflict clause favouring Suspension Event over Force Majeure/Settlement Disruption Event, which the EFET does not.
Functionally, the definition of {{efetaprov|Force Majeure}} is the same in the EFET and IETA versions. Here is a {{diff|77069|77068}}: the differences are to account for the architecture and nomenclature of the different master agreements, though the IETA has a conflict clause favouring Suspension Event over Force Majeure/Settlement Disruption Event, which the EFET does not.
 
The equivalent under the {{emissionsannex}} is the {{euaprov|Settlement Disruption Event}} — so called because there is already a Force Majeure under the {{isdama}} so the ’squad had to call their version something else.

Revision as of 15:23, 28 July 2023

Functionally, the definition of Force Majeure is the same in the EFET and IETA versions. Here is a comparison: the differences are to account for the architecture and nomenclature of the different master agreements, though the IETA has a conflict clause favouring Suspension Event over Force Majeure/Settlement Disruption Event, which the EFET does not.

The equivalent under the ISDA EU Emissions Annex is the Settlement Disruption Event — so called because there is already a Force Majeure under the ISDA Master Agreement so the ’squad had to call their version something else.