Records · procedure · next step
Corporate actions: issuer-to-venue notice records
A corporate-action notification record connects an already approved event with security identifiers, its timetable and actual venue messages. Euronext’s advance-information framework and SIX’s instrument-specific reporting annexes require separate handling. Preserve submitted, received, processed and published versions rather than treating them as one completed step. This preparation does not approve a dividend, replace corporate decisions or a prospectus, or establish that holders received a payment.
General information and document preparation. The facts, actual procedural acts and applicable versions must be checked.
Julie’s legal research currently covers French law. The Swiss sections prepare documents; they do not establish Swiss-law product capability.
Julie by AlphaDeep
Julie currently assists with French law. Which approved French corporate action and venue-notification records would you like to organise?
3 free questions at signup. Avoid names and sensitive information.
Which already decided corporate action is being reported?
Identify the actual distribution, split or restructuring. Both venue frameworks concern operational event reporting; the message does not itself authorise the corporate action or replace the underlying decision.
Which security identifiers and listing branch apply?
Connect issuer, instrument/category and old/new identifiers where relevant. SIX primary and secondary equity listings use different annex branches; one event row cannot be applied to every security.
Which dates must remain separate?
Retain announcement, market-effect and payment dates where applicable. Euronext uses an earlier-event advance-information rule; SIX’s primary-equity dividend row separately names ex-date and pay-date. Do not invent a universal record date.
Prepare the records
Julie’s legal research currently covers French law. The Swiss sections prepare documents; they do not establish Swiss-law product capability.
Synthetic example
Corporate-action, security, timetable, message, receipt and notice version matrix
- Approved event
- Cash dividend, decision D1 supplied
- Security identifiers
- T1 shares, synthetic ISIN reference in S1
- Approved timetable
- Announcement A1, market effect E1 and payment P1 separately documented
- Event rule
- Venue Notice N1 or applicable SIX annex row to provide
- Underlying acts
- Decision D1, terms V1
- Channel and contact
- Authorised contact C1, event-specific channel to confirm
- Submission
- Message M1 retained; venue receipt unknown
- Published notice
- Draft U1, no publication assumed
- Changes
- V2 changes payment; approval and resubmission to link
This record organises supplied documents and values; it certifies no entitlement, permission or safety.
Which event-specific rule defines the submission?
Preserve the actual venue Notice or SIX annex row. Requirements vary by instrument and event; an old template or a secondary-listing split row is not a universal specification.
Which underlying corporate records support the data?
Link approved terms and legal acts to the message version. Euronext may request underlying documents; technical market processing does not certify the legal validity of the corporate decision.
Which recipient and channel received the report?
Record the real submission and responsible contact. SIX uses Connexor Reporting for the relevant primary-equity annex, with other channels for other branches; a message to an intermediary alone proves no venue receipt.
What establishes processing and official publication?
Retain the actual acknowledgment and published notice separately. SIX Official Notice rules distinguish transmission and publication; a file receipt does not prove final dissemination or payment.
How are timetable and identifier changes traced?
Connect the previous version, authorised change, replacement message and actual notice. Keep missing receipts visible; do not overwrite an earlier identifier or date without a correction trail.
Frequently asked questions
Which already decided corporate action is being reported?
Identify the actual distribution, split or restructuring. Both venue frameworks concern operational event reporting; the message does not itself authorise the corporate action or replace the underlying decision.
Which dates must remain separate?
Retain announcement, market-effect and payment dates where applicable. Euronext uses an earlier-event advance-information rule; SIX’s primary-equity dividend row separately names ex-date and pay-date. Do not invent a universal record date.
Which underlying corporate records support the data?
Link approved terms and legal acts to the message version. Euronext may request underlying documents; technical market processing does not certify the legal validity of the corporate decision.
How are timetable and identifier changes traced?
Connect the previous version, authorised change, replacement message and actual notice. Keep missing receipts visible; do not overwrite an earlier identifier or date without a correction trail.
Sources and versions
- Euronext — Rule Book I, corporate and securities events
Issue of 25 June 2026, rule 61004
- SIX — Directive Devoirs d’annonce réguliers (DDAR)
DDAR du 2 décembre 2025, en vigueur le 1er janvier 2026
- SIX — Directive Devoirs d’annonce réguliers (DDAR)
DDAR du 2 décembre 2025, en vigueur le 1er janvier 2026
- SIX — Directive Devoirs d’annonce réguliers (DDAR)
DDAR du 2 décembre 2025, en vigueur le 1er janvier 2026
- SIX — Directive Devoirs d’annonce réguliers (DDAR)
DDAR du 2 décembre 2025, en vigueur le 1er janvier 2026
- SIX — Directive Devoirs d’annonce réguliers (DDAR)
DDAR du 2 décembre 2025, en vigueur le 1er janvier 2026
- SIX — Directive Devoirs d’annonce réguliers (DDAR)
DDAR du 2 décembre 2025, en vigueur le 1er janvier 2026