29.10.2012 Views

Scope - Clearstream

Scope - Clearstream

Scope - Clearstream

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

MARKET PRACTICE BOOK - CORPORATE ACTIONS<br />

38<br />

- Annex 6A: per event, the required details in the security T&C, to allow the PPA/<br />

CD/CSP to diarise the events.<br />

- Annex 6B: per event, the deadlines and details to be confirmed during the life of<br />

the event, e.g. for updates, amendments, valuations, etc. For predictable events<br />

occurring upon a triggering event or at the option of the issuer (refer to flow 2.2.2.2),<br />

these should be notified once the triggering/external event occurs and/or the option is<br />

‘exercised’ by the Issuer. As these events could occur at any time, they are ‘flagged’<br />

by the PPA/CD/CSP as potential occurrences rather than being diarised.<br />

Example Predictable event<br />

For a Convertible bond, the T&C of the security will indicate that it is<br />

convertible during a specific period, e.g. from 01/01/2011 to 01/01/2013.<br />

Before the period of action starts, a notification will contain a summary of the<br />

event, and confirm the relevant applicable deadlines. A second notification<br />

may announce a suspension period, during which the bond is not convertible<br />

(e.g. from 01/03/2012 to 20/03/2012, because underlying shares may be<br />

blocked). Such notification will then indicate the last deadline to instruct a<br />

conversion before the suspension period starts, e.g. 25/02/2012.<br />

• Unpredictable events: ( Consent Solicitation, General Meeting, Extraordinary<br />

Meeting, Repurchase / Tender Offer, Exchange Offer, Credit Event, Change to T&C of<br />

securities)<br />

- Annex 6C: per event, details requirements to be described in the event<br />

documentation, within the scope of the security T&C.<br />

The event documentation can be considered the first announcement, and can be<br />

provided as preliminary information, or as complete information. Any events defined<br />

within specific event documentation remains governed by such document and not by<br />

any covering notification, usually only a précis. All affected parties will make<br />

documentation available to investors, except if restricted from doing so<br />

(see Special note).<br />

Example Unpredictable event<br />

For an exchange offer on a bond, the offering documentation should indicate<br />

the start and end date of the offer, as well as the proceeds ratio and deadlines<br />

to be respected.<br />

Subsequent post-launch notifications may advise of an extended offer period<br />

or announce the result of the offer.<br />

Special note: documentation for Restricted (Targeted) Events<br />

Issuers may launch events with a specific, restricted target investor base, e.g. due to<br />

holding size, residents’ legal jurisdictions, etc., for which the event documentation may not<br />

be made publicly available, and therefore not obtainable from the ICSDs in their normal<br />

course of business. In such cases, the ICSDs will advise their customers in the event<br />

notifications how to obtain the event documentation. It is therefore recommended to<br />

confirm whether Event Documentation may be published online by the ICSDs, by using the<br />

Public/Restricted indicator in the applicable templates.<br />

All parties will ensure an efficient and timely flow of information from the Issuer through to<br />

the account holders as per the agreed and defined flows, following.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!