TTR II User Manual V 1.2 November 2017

Size: px
Start display at page:

Download "TTR II User Manual V 1.2 November 2017"

Transcription

1 TTR II User Manual V 1.2 November 2017

2 Document Information Contact Name Code Contact information Note Alexander Racher AR Roland Rotsejdl RR Revision History Version Status Date Editors Description 1.0 F AR Final Version 1.1 F AR Complete makeover, see marked changes in corresponding markup version document 1.2 F AR Some smaller updates Legend: WIP: Work in progress R: To be reviewed F: Approved User Manual TTR II (V1.2) Page 2 / 48

3 Table of Contents Document Information Introduction, Basics and Expected Functionalities Abbreviations and terms Asset Classes to be considered Data input Automated data input via FIX Interface Messages for Pre Trade Publishing Messages for Post Trade Transparency Messages for Portfolio Compression Cycle Manual data input via WebGUI ESMA Instrument Search Data Input Checks General Input Checks Check against ESMA DB Who-needs-to-report Check Reporting delay check Data Processing Normal processing Publication delay check Exception processing Trade flags Deferred publishing = Waiver Concept Deferrals for equity and equity-like instruments Deferrals for non-equity instruments Combinations of Trade Flags Combinations of Trade Flags Equity RTS Combinations of Trade Flags Non-Equity RTS Data correction possibilities Data Output Display of TTR II transactions on website (15 minutes delayed) Display of public information to the TTR II system on website Information to be made public Pre-Trade Reporting Post-Trade Reporting Acceptable reporting delays for equity and equity-like instruments Acceptable reporting delays for non-equity instruments Portfolio Compression Cycle Data Storage Reporting Reporting to Customers Trade Details Report Price Offer & Quote Details Report Portfolio Compression Cycle Details Report SI Status Report Means of report generation User Manual TTR II (V1.2) Page 3 / 48

4 Display of automatically generated reports within GUI Submenu Report Overview Manually generated reports within GUI Submenu Report Generation (Advanced Reporting) Reporting to National Capital Market Authority (FMA) General reporting obligations to FMA Waiver Setup, LEI Waiver Setup Legal Entity Identifier (LEI) User Manual TTR II (V1.2) Page 4 / 48

5 1. Introduction, Basics and Expected Functionalities TTR II is a MiFID II compliant transaction reporting / publication system, allowing customers of Wiener Börse AG to report OTC trades, price offers / quotes and portfolio compression cycles (PCCs). In the course of MiFID II / MIFIR (hereinafter MM ) transparency obligations for off-exchange transactions will be enhanced massively. MM now defines more financial institutions as Systematic Internalisers (SI) and at the same time defines rules, which information on their trading actions they have to publicly disclose. Besides the more rigid obligations for SIs all other financial institutions have to report their OTC activities not only in equities but all other instrument classes as well (fixed income / bonds, structured products, derivatives, ). Current WBAG solution for MiFID I is called Transparency Trade Reporting (TTR ) and focuses primarily post-trade data in equities. Future solution Transparency Transaction Reporting II (TTR II) includes post-trade publication for all equity and non-equity asset classes and pre-trade publication as well. MM furthermore defines the Approved Publication Arrangement (APA), entities, which are allowed to offer OTC publication services to financial institutions within the EU. In order to become an APA, an entity has to apply at its National Capital Market Authority (NCA, in Austria: FMA). WBAG will offer the data to all interested stake holders in FIX protocol format (hereinafter Tip/Fix Converter ). For this a FIX feed is set up and is feeded with ADH data. This allows offering the full scope of WBAG s and its partner exchange s data products also via FIX to interested customers. Legal documents used for this functional description: MiFID II_RL EU_ _CELEX-32014L0065-EN-TXT.pdf MiFIR_Regulation (EU) No _ _CELEX-32014R0600-EN-TXT.pdf RTS 1, 2, 3, 13 and 14 (parts of other RTS docs used in the text as well) Many data correctness checks are done against the ESMA reference data base (FIRDS) as currently available for MiFID I OTC reporting. ESMA will substantially extend this DB for all non-equity reference data. User Manual TTR II (V1.2) Page 5 / 48

6 The overview of the TTR II workflow of data input, data processing and data publishing is shown in the figure below: Figure. 1: TTR II data processing User Manual TTR II (V1.2) Page 6 / 48

7 Application language The language of the TTR II application is English Abbreviations and terms Abbreviation, Term FIX FMA PCC MiFID II OTC ESMA DB / FIRDS Description Financial Information exchange Protocol Finanzmarktaufsicht Portfolio Compression Cycle Markets in Financial Instruments Directive II Over the counter, financial instruments traded out of a trading venue / MTF European Security and Markets Authority Database / Financial Instruments Reference Data System 2. Asset Classes to be considered Resources: MiFIR Regulation , Article 20 and 21 The TTR II system allows the processing and publication of trades, price offers, quotes and PCCs for all asset classes. Please refer to the tables below for details. a) Equity and equity-like financial instruments (Annex III to RTS 1) Asset Class MiFIR Code ADH BasicDataType Shares SHRS BDSh ETFs ETFS BDEt Depositary Receipts DPRS BDSh Certificates (funds, no structured products as defined by WBAG) CRFT BDEt Other equity like financial instruments OTHR BDSh User Manual TTR II (V1.2) Page 7 / 48

8 b) Non-equity financial instruments (Annex IV to RTS 2) Asset Class MiFIR Code ADH BasicDataType Securitised derivatives SDRV BDUt Structured Finance Products (SFPs) SFPS BDUt Bonds BOND BDBo ETCs ETCS BDBo ETNs ETNS BDBo Emission Allowances EMAL BDSh Derivative DERV BDDe 3. Data input Two different data input sources for TTR II are available: 1) Automated data input via FIX Interface (dedicated TTR II FIX interface and CEESEG FIX) 2) Manual data input via WebGUI A defined set of fields shall be inserted by the customer via FIX and WebGUI for further publication. More information can be found in the following separate specifications: - CEESEGFIX TTR II Specification - WebGUI Specification As a further improvement it is planned to automatically populate the data of the fields available in ESMA DB within the WebGUI (the customer only has to insert the instrument identifier fields). The same applies to the FIX interface. In case it is not possible to use ESMA DB data, the sent transaction is rejected in case mandatory fields are missing Automated data input via FIX Interface The FIX communication is elaborated in detail in the CEESEG FIX TTR II specification Messages for Pre Trade Publishing For pre trade transparency the following messages are defined: New Order Single Cancel Order Request Cancel Replace Order Request Execution Report Quote Quote Status Report User Manual TTR II (V1.2) Page 8 / 48

9 Note all pre-trade messages ( orders and quotes ) are only valid for the current trading day Messages for Post Trade Transparency For post trade transparency the following messages are defined: Trade Capture Report Trade Capture Report Ack Kindly note TTR II requires customers to send the correct turnover for each trade in following cases (conditionally mandatory in FIX): 1. LRGS equity post-trade transparency waiver for deferred publication 2. Customer uses SI-threshold calculation Turnover needs to be updated in the course of trade corrections if price or volume were changed! Furthermore changes of ISIN may only be done via cancellations / send new trade, there is no trade correction of ISIN possible Messages for Portfolio Compression Cycle For PCC the following messages are defined: NewOrderList ExecutionReport 3.2. Manual data input via WebGUI For manual data reporting a WebGUI is implemented with the following functionalities: Entry of transactions (trades, price offers, quotes, PCCs) Overview of all reported / published transactions Correction of transactions Deletion of transactions Downloading of predefined reports Generation of individual reports Waiver view ESMA Instrument Search The WebGUI is implemented in HTML5, available via HTTPS and secured via TLS. The WebGUI will be available in production via the URL Kindly note TTR II requires customers to send the correct turnover for each trade in following cases (conditionally mandatory in WebGUI): 1. LRGS equity post-trade transparency waiver for deferred publication 2. Customer uses SI-threshold calculation Turnover needs to be updated in the course of trade corrections if price or volume were changed! User Manual TTR II (V1.2) Page 9 / 48

10 Furthermore changes of ISIN may only be done via cancellations / send new trade, there is no trade correction of ISIN possible. Data input via WebGUI shall be done always in local time, TTR II takes care of conversion to UTC ESMA Instrument Search Depending on the availability, functionality and detailed content of the ESMA Database (FIRDS), WBAG will provide an additional service called ESMA Instrument Search. In general, the ESMA instrument search in FIRDS shall provide an enhanced search possibility, which is offered to customers as a separate service. With the help of this search customers shall have the possibility to check, if certain instruments (derivatives) are traded on a trading venue within the EU (TOTV) and are therefore mandatory to be published. More details on the ESMA Instrument Search (TOTV) will be defined in autumn 2017, when FIRDs download data becomes available. Within the search filters (e.g. Name, Currency, ISIN,.), there are no mandatory fields. Furthermore a wildcard search within the fields is possible. The results are shown in lists, including a paging after 50 instruments. There is a headline above the result list, showing the total number of found instruments: Your search returned x.xxx instruments. Showing 1 to 50. Due to performance reasons, the result list is limited to results. In case the user would like to see further results, there is a button More, where the next results are loaded. Editing or deleting of data within WBAG s database ESMA Download DB, where all data from ESMA DB (FIRDS) is stored, is not possible any more (in comparison to the old TTR system), as there will be a possibility to skip the ESMA check when entering transactions. Please refer to the separate specifications for the WebGUI and FIX for more information on this functionality. 4. Data Input Checks Resources: DVO 2017/571 (RTS 13): Article 10 User Manual TTR II (V1.2) Page 10 / 48

11 4.1. General Input Checks Applicable to: Pre-trade Post-trade Resources: MiFID2 Directive , Article 64 RTS 13 Paragraph 14 RTS 13 Paragraph 25 RTS 13 Article 10 Paragraphs 4-8 Within FIX and the WebGUI some general checks are implemented. The subsequent fields are checked for validity. Please note: Any checks are only triggered after the customer hits the send button in the GUI respectively sends the FIX trade report. Depending of the result of the checks, the report is sent to the TTR II system or rejected (with corresponding rejection message). Excluded are of course any fields, where the customer can only select from dropdown menus in the GUI. The same applies for FIX in cases where only a predefined set of valid values is accepted. Mandatory fields All mandatory fields according to the CEESEG FIX TTR II specification respectively the WebGUI specification shall be populated by the customer. Otherwise the reporting of the transaction is not possible within the GUI and in case of FIX the message is rejected. InstrumentIdentifierType (FIX tag 22) Mandatory field. Valid value: ISIN In case of mismatch for FIX, a rejection is triggered; the WebGUI uses ISIN per default. ISIN (FIX tag 48) Mandatory field. In case the field InstrumentIdentifierType is ISIN, a check, if the inserted ISIN is valid, is implemented. The checks are done according to ISO 6166 and include: o Length of the ISIN is 12 characters o The last character (12) is the check sum Please use the standard feature of quick fix for this check (also for the GUI). In MiFID II mentioned code OTHR became obsolete as all instruments in FIRDS have to have an ISIN. User Manual TTR II (V1.2) Page 11 / 48

12 Price (FIX tag 44 in Order messages, tags 132 and 133 in Quote messages, tag 31 in Trade message) The inserted price needs to numeric according to RTS 1&2 (decimal 18, 17) and is mandatory. Explanation for the format decimal 18,17 : According to MiFID II this notation means there is a maximum of 18 digits in total, whereas up to 17 digits may be used after the decimal point. Exception: In case of a pending prices the price field may also be empty (NULL). The pending price information is then transported in a separated field. For more details see CEESEG FIX TTR II specification. This is a mandatory requirement from MiFID II. The purpose of a pending price: In case of forward pricing, a trade is done without the price being known. Therefore the price is published with NULL (not 0) and a corresponding flag PNDG (=Pending Price; only a flag, not a price!). Investment firms are obliged to publish the missing price in form of a correction of the originally reported trade as soon as possible. Date & Time of transaction (tag 60) The inserted date & time shall not be in the future. In general for publication the MiFID II compliant Date_Time shall be published: YYYY-MM-DDThh:mm:ss.ddddddZ (Z=UTC) For the customer this implies the following: o Via FIX the customer sends the format YYYYMMDD-hh:mm:ss.ddd. The timestamp is UTC as per FIX specification. Please note, the Z is redundant in FIX, but mandatory any way. As not the complete time stamp is delivered via FIX, the timestamp is filled by the APA system before publication. o Via WebGUI the customers send the format YYYY-MM-DDThh:mm:ss.ddddddZ. The separators and the letters T and Z are prefilled within the WebGUI. The dddddd are prefilled with , however, they may be changed if necessary. The date & time inserted by the customer shall be granular to at least the nearest second. It is expected, that the customers converts the time stamp to UTC time before entering it. The following MiFID II affected time stamps are necessary: - Trading Date Time (to be consistent within the system, we use the format for price offers and quotes as well, not only for trades) - Publication Date Time Side-Note: Within TTR II no timestamp according to MiFID II date_time format needs to be generated. The relevant MiFID II timestamps are either inserted by the customer (according to the definition above) or generated by ADH (publication time stamp). In case there are further User Manual TTR II (V1.2) Page 12 / 48

13 timestamps, which are generated within TTR II, the format is not necessarily the MiFID II format. Currency (tag 15 in all message types used) The inserted / selected currency is checked against the ISO 4217 standard. ID (Trade Report ID as TIC in tags 37, 20050, for Orders and Quotes, tag 880 for Trades, CLOrdID in tag 11, QuoteID) For each transaction a unique ID must be inserted / assigned by the customer. The uniqueness is checked automatically by the system. The transaction identification code, TIC, customer identification code CIC and quote identification code QuoteID shall be unique, consistent and persistent per ISO segment MIC and per trading day. InstrumentTypeMiFIR (tag 12000) Mandatory field; if missing or invalid, a rejection is triggered. Valid values: Equity financial instruments (Annex III to RTS 1): SHRS, ETFS DPRS CRFT OTHR Non-equity financial instruments (Annex IV to RTS 2): SDRV, SFPS, BOND, ETCS, ETNS, EMAL, DERV InstrumentUnderlyingTypeMiFIR (tag 12001) Conditionally mandatory field if InstrumentTypeMIFIR is SDRV or DERV. If missing or invalid, a rejection is triggered. Valid values: INTR, EQUI, COMM, CRDT, CURR, EMAL InstrumentSubTypeMiFIR (tag 12002) Conditionally mandatory field if InstrumentTypeMIFIR is DERV. If missing or invalid, a rejection is triggered. Valid values (with explanation): OPTN = Options, FUTR = Futures, FRAS = Forward Rate (FRA) Agreement, FORW = Forwards, SWAP = Swaps, PSWP = Portfolio, SWPT = Swaptions, FONS = Futures on a swap, FWOS = Forwards on a swap, FFAS = Forward Freight Agreements (FFAs), SPDB = Spread betting, CFDS = CFD, OTHR = Other Volume (tag 38 in Order messages, tags 134 and 135 in Quote messages, tag 32 in Trade messages) The inserted volume needs to be numeric according to RTS 1 and 2 (decimal 18, 17). The field volume is only mandatory for equities (in any case) and for non-equities only if InstrumentTypeMiFIR is neither DERV nor EMAL. User Manual TTR II (V1.2) Page 13 / 48

14 Explanation for the format decimal 18,17 : According to MiFID II this notation means there is a maximum of 18 digits in total, whereas up to 17 digits may be used after the decimal point. QuantityInMeasurementUnits (tag 1147) Conditionally mandatory field for instruments, for which the following combinations of classifications are applicable: InstrumentTypeMIFIR InstrumentUnderlyingTypeMiFIR DERV COMM DERV EMAL EMAL - If the field QuantityInMeasurementUnits is missing or invalid, a rejection is triggered. NotationMeasurementUnit (tag 12007) Conditionally mandatory field for instruments, for which the following combinations of classifications are applicable: InstrumentTypeMIFIR InstrumentUnderlyingTypeMiFIR DERV COMM DERV EMAL EMAL - If the field NotationMeasurementUnit is missing or invalid, a rejection is triggered. Price notation (e.g. percentage notation ) (tag 423) The field is mandatory for non-equity instruments with InstrumentTypeMIFIR = SDRV, SFPS, BOND, ETCS, ETNS, EMAL, DERV In case of mismatch, a rejection is triggered. VenueOfExecution This field is only relevant for publication via ADH and is derived from tag 448 (if NO for both fields XOFF, if at least one YES SINT).Customers do NOT have to provide this, only tag 448 to highlight if on buy or sell side an SI is involved. Reprint (tag 570) The field is mandatory. Valid values: ORGN if not reported on any other APA and customer is responsible for reporting. DUPL if other party has to report / trade was reported at another APA earlier. Note any trade reports using DUPL are not published (not forwarded to ADH for publication) but only processed for SI threshold calculation service! Note TTR II accepts DUPL for non-equity instruments for the purpuose of SI calculations although DUPL is not specified in RTS 2 / for non-equity instruments. In case of mismatch, a rejection is triggered. User Manual TTR II (V1.2) Page 14 / 48

15 NominalValue (tag 231 ContractMultiplier) The field is mandatory for non-equity instruments with InstrumentTypeMIFIR = SDRV, SFPS, BOND, ETCS, ETNS, EMAL, DERV In case of mismatch, a rejection is triggered. NominalCurrency (tag 10015) The field is mandatory for non-equity instruments with InstrumentTypeMIFIR = SDRV, SFPS, BOND, ETCS, ETNS, EMAL, DERV In case of mismatch, a rejection is triggered. Type (tag EMALSubTypeMiFIR) Conditionally mandatory field for instruments, for which the following combinations of classifications are applicable and result in following valid values: InstrumentTypeMIFIR InstrumentUnderlyingTypeMiFIR Valid values DERV EMAL EUAE, CERE, ERUE or EUAA, OTHR EMAL - EUAE, CERE, ERUE or EUAA, OTHR In case of mismatch, a rejection is triggered. TransactionToBeCleared (tag 577 ClearingInstructions) The field is mandatory for derivatives (InstrumentTypeMiFIR = DERV). In case of mismatch, a rejection is triggered. TTR II rejects any reports which do not fulfil the requirements. In case a check is unsuccessful, the reported transaction is rejected Check against ESMA DB Applicable to: Pre-trade Post-trade TTR II performs checks against the ESMA DB before accepting a new report. These checks depend on the availability of an according reference in ESMA DB. According to the national authority FMA an APA does not have to check each and every input. The checks are therefore performed with best effort. To fulfill the best effort approach, the following process is implemented within TTR II: User Manual TTR II (V1.2) Page 15 / 48

16 By default each transaction is being checked against the ESMA DB. In case of a rejection caused by a mismatch of information or by a lack of information in ESMA DB, the customer has two possibilities to proceed: The customer can double check the entries and sends a corrected report. In case the information is correct from the customer s point of view, the affected transaction shall be sent with the Skip ESMA Check flag. More details to rejection messages can be found in chapter 5.3. Fields to be checked against ESMA DB Depending on the FIRDS download files made available, the fields to be checked may be updated. The criterions for the checks are taken from a parametrization, which can be configured by WBAG. Instrument Identifier (ISIN) If ESMA check is used (check box in GUI ticked or FIX tag 22 sent with value 4 ) and the inserted instrument identifier does not match the ESMA DB, a rejection is triggered. Following FMA confirmation from Sept 21, 2017 only ISINs are applicable. Currency (tag 15) It is checked, if the inserted instrument exists in ESMA DB with the provided currency. If the instrument exists with multiple currencies, the inserted currency is considered for the rest of the ESMA checks, e.g. price, turnover. Price (FIX tag 44 in Order messages, tags 132 and 133 in Quote messages, tag 31 in Trade message) i.e. max. deviation in percent compared to the ESMA reference price Tier 1: (-30% < x <= -50% OR +80% < x <= +100%) publication with warning Tier 2: (x > -50% / x > +100%) rejection This check is skipped in case that PricePending is set to YES (no price information available) or PostTradeTransparencyWaiver is - DATF (Daily aggregated transaction flag) - VOLW (Volume omission flag) - COAF (Consecutive aggregation flag) - FWAF (Four weeks aggregation flag) - IDAF (Indefinite aggregation flag) Turnover (tag 381 GrossTradeAmt, only if sent by customer) i.e. max. deviation in percent compared to the ESMA average daily turnover Tier 1: (-30% < x <= -50% OR +80% < x <= +100%) publication with warning Tier 2: (x > -50% / x > +100%) rejection This check is skipped in case that MiFID2TradeFlag or PostTradeTransparencyWaiver is - LRGS (Large in scale) or User Manual TTR II (V1.2) Page 16 / 48

17 - SIZE (Transactions above the standard market size) or - LMTF (Limited details flag) or - DATF (Daily aggregated transaction flag) - VOLO (Volume omission flag) or - VOLW (Volume omission flag) Price notation (e.g. percentage notation ) (tag 423) If the inserted price notation does not match the ESMA DB, a rejection is triggered. InstrumentTypeMiFIR (tag 12000) If the inserted InstrumentTypeMiFIR does not match the ESMA DB, a rejection is triggered. InstrumentUnderlyingTypeMiFIR (tag 12001) If the inserted InstrumentUnderlyingTypeMiFIR does not match the ESMA DB, a rejection is triggered Who-needs-to-report Check Applicable to: Pre-trade Post-trade For this check the following mandatory input fields need to be filled by the customer (tags 453/452/448): - SI status of customer (stati: SI, Non-SI) - SI status of counterpart (stati: SI, Non-SI) - Side of the customer (stati: Buyer, Seller) - Reprint (stati: ORGN, DUPL) tag 570 Description of check: It is checked, if the customer is obliged to report or not and if the customer filled the field Reprint correctly. - In case the customer is obliged to report, he has to fill the field Reprint with ORGN - In case the customer is not obliged to report, he CAN report optionally, but only with field Reprint = DUPL o WBAG strongly recommends reporting also DUPL transactions in order to enable a correct SI status calculation in the system. o DUPL trades are not published, they are only stored in the TTR II data base. Check, who has to report: 2 non SI s seller 2 SI s seller User Manual TTR II (V1.2) Page 17 / 48

18 SI = buyer, non-si = seller buyer SI = seller, non-si = buyer seller) Buyer Non-SI SI SI Non-SI (green: obliged to report) Seller Non-SI SI Non-SI SI Process of check: 1.) Customer fills the mandatory input fields (SI status customer, SI status counterpart, Side, Reprint) 2.) Customer sends the transaction 3.) The system performs the following checks: a. If customer = SI and customer = seller => Reprint has to be populated with ORGN b. If customer = Non-SI and customer = seller and counterparty = Non-SI => Reprint has to be populated with ORGN c. If customer = Non-SI and customer = seller and counterparty = SI => Reprint has to be populated with DUPL d. If customer = Non-SI and customer = buyer => Reprint has to be populated with DUPL e. If customer = SI and customer = buyer and counterparty = SI => Reprint has to be populated with DUPL f. If customer = SI and customer = buyer and counterparty = Non-SI => Reprint has to be populated with ORGN 4.) In case everything is fine, the reported transaction is processed within TTR II. In case the field Reprint was populated wrongly by the customer, the transaction is rejected with an according error message. Please note: The SI status of the customer, which is calculated by the SI check described herein, is NOT automatically used by the system. The information about the SI status of the customer has only informational character. TTR II can only monitor SI status if all trades done (incl. DUPL) by an APA customer are actually sent to ADH. Furthermore the check on Substantial Basis / comparison with customer turnover (on- and offexchange) in one specific instrument can only be done on customer side. This APA documentation holds threshold values as specified in chapter for customer turnover. DISCLAIMER: Kindly note WBAG cannot take any legal responsibility for these SI calculations. User Manual TTR II (V1.2) Page 18 / 48

19 4.4. Reporting delay check Applicable to: Pre-trade Post-trade This check only applies for transactions, which have to be published immediately (NO deferral waivers applicable). If the time difference between the trade matching (time-stamp of trade provided by customer, tag 60) and the reporting time (time of reception in TTR II, returned to the customer in tag 60) of the trade exceeds the limits defined in and 7.2.2, the affected message is not rejected, but triggers a warning flag in the reply message of TTR II as defined in chapter 5.2. Accordingly TTR II issues a warning if an equity instrument reporting time stamp is more than 1 min later than the timestamp trade matching (time-stamp of trade provided by customer) if a non-equity instrument reporting time stamp is more than 15 min (as of Jan 1, 2020: 5 min) later than the timestamp trade matching (time-stamp of trade provided by customer) The trade is published immediately if such a warning is issued nonetheless. Equity and equity-like only: All late reporting warnings only apply from 9:00-17:45 (trading hours of WBAG). If a transaction takes place outside of trading hours, then warning is issued that the trade is published at or after 9:00 (beginning of trading) of the following trading day. Please note: This check only helps in case a customer is too late with reporting a transaction. For the limits defined in and of course also the difference between the trading time and the publication time (= reporting time + TTRII processing) is relevant, see chapter 5.2. Furthermore note that for trade corrections and cancellations no reporting delay check applies. 5. Data Processing This chapter describes the processing of transactions within the TTR successfully passed all checks as described in the previous chapter. II system, after they have 5.1. Normal processing Resources: RTS 13 Article 10 RTS 13 Recital 17 User Manual TTR II (V1.2) Page 19 / 48

20 Definition of necessary fields for normal processing: TIC Code (in tags 37, 20050, for Orders and Quotes, tag 880 for Trades): TTR II generates unique ID s. To facilitate reliable communication between an APA and the customer reporting a transaction, particularly in relation to cancellations and amendments of specific transactions, an APA should include in the confirmation messages to the reporting customer the Transaction Identification Code (TIC), which has been assigned by TTR II when making the information public. An APA shall refer to the TIC in any subsequent communication with the customer in relation to a specific trade report. This means all TTR II customers need to be able to store the TIC and provide it with any cancellation or amendment of the originally reported data. Processing Steps: 1. Customer sends trade, price offer / quote or PCC 2. TTR II generates a TIC (Transaction Identification Code) for the transaction (NOTE: Following ESMA Q&A on Transparency a TIC shall not be generated if one of the following flags for initial aggregated publication is used: DATF, VOLW, FWAF or IDAF.) a. TIC Code is generated uniquely. It is generated as suggested by the FIX trading community: The TIC code comprises up to 52 characters and it is generated as a combination of the reporting date, the reporting time stamp and a sequence number, which is unique for each reporting day. b. Besides this no amendment or further enrichment of the inserted customer data takes place 3. Performance of data input checks as defined in chapter TTR II confirms acceptance of transaction (in tag 150) as ACCEPTED = PENDING_NEW OR rejects in case of missing or wrong input data as REJECTED (both including TIC). In case of duplicate trades (flagged with DUPL ) these shall not published. Reception of correct trade in TTR II are confirmed with ACCEPTED = NEW. There is no further processing but for SI threshold calculations for trades flagged DUPL. 5. Check for deferral logic Before publishing the transaction, the TTR II system checks, if potential deferrals are applicable. For more details, please refer to chapter Enrichment with defined reference data from ESMADB. 7. Sending reported data from TTR II to ADH for publication: a. Sending & immediate publication i. Sending of reported data incl. TIC to ADH b. Queuing, deferring and sending publication i. Queuing of reported data, incl. TIC ii. After the end of the deferral time, the publication is triggered through a scheduler process, please refer to 5.4. User Manual TTR II (V1.2) Page 20 / 48

21 8. Feedback Loop As ADH is used as the publishing system for TTR II a feedback loop is set up to confirm dissemination to TTR II customers. An ADH TTR II customer (part of TTR II) constantly monitors ADH output and checks, if ADH published the received TTR II transaction. If a TTR II transaction is received from ADH a confirmation is send to the TTR II customer ( PUBLISHED = NEW ). Please note: TTR II sends a TIC Code and a sequence number (ApplSeqNum=1181) to the ADH system. Only with the help of these two fields a transaction may be marked as unique. Those two fields are sent back from ADH to the TTR II, to be able to identify the transactions of the TTR II uniquely. The sequence number is generated by the TTR II and is unique per day. If a transaction is deferred for more than one day, the same mechanism applies, as the sequence number is only added while sending to ADH. Please note: ADH data (as the data dissemination system for the TTR II) is only available one way. There is no possibility to manipulate pre- or post-trading data Publication delay check Applicable to: Pre-trade Post-trade Please note: The check described hereafter is very similar to the check described in chapter 4.4 ( reporting delay check ). The main difference is: the reporting delay check from chapter 4.4 refers to a possible late reporting by the customer. The hereafter described publication delay check refers to a potential late publishing caused by a late TTR II processing. The publication delay check only applies for transactions, which have to be published immediately (NO deferral waivers applicable). If the time difference between the trade matching (time-stamp of trade provided by customer, sent in tag 60) and the publication time (returned to customer in tag 60 in published message) of the trade exceeds the limits defined in and 7.2.2, a warning as defined in chapter 5.2 is triggered together with the final publication confirmation after the processing of the feedback loop. Accordingly TTR II issues a warning if an equity instrument publication time stamp is more than 1 min later than the timestamp trade matching (time-stamp of trade provided by customer) if a non-equity instrument publication time stamp is more than 15 min (as of Jan 1, 2020: 5 min) later than the timestamp trade matching (time-stamp of trade provided by customer) User Manual TTR II (V1.2) Page 21 / 48

22 Equity and equity-like only: All late publication warnings only apply from 9:00-17:45 If a transaction takes place outside of trading hours, then a warning is issued that the trade is published at or after 9:00 (beginning of trading) of the following trading day Exception processing Publication with warning In certain cases as e.g. used in chapter 7.2, a warning is returned to the customer, but the transaction is still published. The customer should double-check the transaction and may send a correction. Rejection with reject reason In case data in the report appears to be erroneous as used in chapter 4, the transaction is rejected with a message specifying the reason. The customer should double-check the provided data and correct erroneous fields to enable the publication Trade flags TTR II customers may refer to the separate Excel-specification All_Flags_APA_Overview for further details on the functional implications of trade flags in TTR II. Following MiFID II / MiFIR there are quite some trade flags to be used under different circumstances. In TTR II these are separated in non-functional flags (from TTR II perspective) as available in field MiFID2TradeFlags and functional flags, e.g. post-trade deferral flags. Both fields are available in the WebGUI accordingly, in the FIX interface several fields are available following the FIX standard. This chapter defines the allowed combinations of flags as published by ESMA Q&A On MiFID II and MiFIR transparency topics ESMA As a general approach, flags should only be applied in case the circumstances described in Table 1 apply. If none of the specified circumstances apply, the transaction should be published without a flag. Flag Name Description RTS 1 equity RTS 2 nonequity BENC Benchmark transaction flag RTS 1: Transactions executed in reference to a price that is calculated over multiple time instances according to a given benchmark, such as volume-weighted average price or time-weighted average price RTS 2: All kinds of volume weighted average price transactions and all other trades where the price is calculated over multiple time instances according to a given benchmark. y y User Manual TTR II (V1.2) Page 22 / 48

23 ACTX Agency cross RTS 1+2: Transactions where an investment firm has y y transactions flag brought together customers price offers with the purchase and the sale conducted as one transaction and involving the same volume and price TNCP Transactions not Transactions not contributing to the price discovery y contributing to the process MiFIR Art 23 and as set out in RTS 1 Art 2 price discovery process (MiFIR Art 23) SDIV Special dividend Transactions that are either: y flag Executed during ex-dividend period where the dividend or other form of distribution accrues to the buyer instead of the seller (or vice versa in the cum-dividend period) LRGS Post-trade large in scale transaction flag RTS 1: Transactions that are large in scale compared with normal market size for which deferred publication is permitted under RTS 1 Art 14 RTS 2: Transactions executed under the post-trade large in scale deferral. SIZE Transactions RTS 1: Transactions executed on a systematic above the internaliser where the size of the incoming price offer standard market was above the standard market size RTS 1 Art 11 size flag RTS 2: Transactions executed under the post-trade size specific to the instrument deferral. ILQD Illiquid instrument RTS 1: Transactions in illiquid instruments as transaction flag determined in accordance with Art 1-9 Commission Delegated Regulation executed on a systematic internaliser RTS 2: Transactions executed under the deferral for instruments for which there is not a liquid market. RPRI Transactions Transactions executed on a systematic internaliser with which have a price improvement MiFIR Art 15 (2) received price improvement flag TPAC Package Package transactions which are not exchange for transaction flag physicals as defined in RTS 2 Art 1 XFPH Exchange for Exchange for physicals as defined in RTS 2 Art 1 physical transaction flag CANC Cancellation flag RTS 1+2: When a previously published transaction is cancelled AMND Amendment flag RTS 1+2: When a previously published transaction is amended y y y y y y y y y y y y y User Manual TTR II (V1.2) Page 23 / 48

24 DUPL Duplicative trade When a transaction is reported to more than one APA in reports flag accordance with Art 17 (1) of Commission Delegated Regulation Table 1: MiFID II Trade Flags y, but not published not required by RTS 2 but needed for SI calculations, will not be published CANC and AMND: The flags CANC and AMND apply in the same way for equity and non-equity instruments. The flags CANC and AMND should not be used when publishing all the details of a transaction after the lapse of the supplementary deferrals for non-equity instruments Deferred publishing = Waiver Concept In the TTR II waiver solution WBAG makes available all possible deferral waivers for post trade for equity & equity-like instruments (RTS 1) and for non-equity instruments (RTS 2). Pre-trade waivers in TTR II are supported for making public transactions according to any confirmation by NCAs, but are not checked for correctness nor have they any other functional implication within the TTR II system. Note these flags may only be entered in field MiFID II Trade Flag in the WebGUI or in according fields as described in the CEESEG FIX TTR II specification and published afterwards. Post-trade deferral waivers / their flags may be entered in field Post Trade Deferral Waiver in the WebGUI or in according fields as described in the CEESEG FIX TTR II specification. The deferred publication of a record is achieved by setting a scheduled job in a scheduler to publish the record at the respective time. The publication is continued at the set time. The job data is stored in the database to ensure the functionality of deferred publication also in case of a short time outage of the application server. The timespan of the publication can t be influenced by the customer. It is preset by the MiFID II threshold table or defined by an NCA. Should a trade be amended or cancelled during the deferral period, all transactions sent by the customer are published after the deferral period. Following ESMA Q&A on MiFID II and MiFIR transparency topics (Chapter 8 Data reporting service providers), [ ] investment firms should report the transaction to the APA as soon as technically possible after the execution, regardless of the application of any deferrals. Any waiver is set up by WBAG after transmission of the according NCA confirmation. User Manual TTR II (V1.2) Page 24 / 48

25 Waivers are set up by WBAG, therefore a customer has to send the NCA confirmation for each waiver to be able to use it in the system. Waiver processing: In general all trades are disseminated immediately. Deferrals are the exemption and are only possible if a waiver is set up correctly and in time by the customer. This means, within the GUI the waiver dropdown is only active with the approved waivers. In comparison, within FIX any sent deferral flags are compared to the waivers set up. In case the waiver applies, the publication is deferred following the rules defined below. If the waiver is not set up, the transaction is rejected. Processing during data input by customer via WebGUI: a. If no waiver is applicable, the transaction is published immediately. b. If a waiver is applicable, the system automatically activates the field Post Trade Deferral Waiver. This is a multi-select dropdown, where only the approved waivers for the ISIN are listed for selection. After selection of the deferral waivers, the system automatically defers the publication according to the rules below. i. The field Average Daily Turnover (ADT) is activated in case a LRGS = Large in Scale Waiver is selected. ii. The customer needs to insert the ADT mandatorily if it is not provided by the system with FIRDS data Deferrals for equity and equity-like instruments The only possible waiver for deferrals is LIS-transaction (LRGS). LIS means Large in Scale. If a transaction with LRGS is sent via FIX or entered into the WebGUI, TTR II uses following fields inserted by the customer to determine the deferral period applicable: Average Daily Turnover (ADT) not applicable if Instrument Type MiFIR = ETFS Turnover The TTR II system determines the ADT class in the first column of the following tables (depending on the Instrument Type MiFIR) and then determines the deferral time based on the turnover of the transaction entered. for shares, depositary receipts, certificates and other similar financial instruments (SHRS, DPRS, CRFT, OTHR): ADT & turnover are processed for ETFs: only turnover is processed User Manual TTR II (V1.2) Page 25 / 48

26 Average daily turnover (ADT) in EUR > 100 m 50 m 100 m 25 m 50 m 5 m 25 m 1 m 5 m m < Minimum qualifying size of transaction for permitted delay in EUR Timing of publication after the transaction minutes minutes End of the trading day minutes minutes End of the trading day minutes minutes End of the trading day minutes minutes End of the trading day minutes minutes End of the trading day minutes minutes End of the trading day minutes minutes End of the trading day minutes minutes End of the trading day minutes minutes End of the next trading day Table 2: Deferred publication thresholds and delays for shares and depositary receipts (SHRS, DPRS) User Manual TTR II (V1.2) Page 26 / 48

27 Average daily turnover (ADT) in EUR ADT < ADT Minimum qualifying size of transaction for permitted delay in EUR Timing of publication after the transaction minutes End of the trading day minutes End of the trading day Table 3: Deferred publication thresholds and delays for certificates and other similar financial instruments (CRFT, OTHR) Minimum qualifying size of transaction for permitted delay in EUR Timing of publication after the transaction minutes End of the trading day Table 4: Deferred publication thresholds and delays for ETFs (ETFS) Deferrals for non-equity instruments TTR II uses 2 calendars, one for working days, one for trading day (confirmation from FMA ): Arbeitstag ist izm Nachhandelstransparenz relevant (zb ART 11 von RTS 2; ein Arbeitstag an dem veröffentlicht wird, muss nicht unbedingt Handelstag sein) For the identification of working days and trading days 2 calendars should be used: - Working days are all weekdays where there is no public holiday in Austria. They shall be used for deferral calculations if mentioned accordingly / depending on the used deferral flag. Trading days are all working days except Saturdays, Good Friday (Karfreitag), Dec 24 and 31. Publications are only possible on WBAG and/or partner exchange working days NOTE: Detailed deferral periods per flag can be changed (parametrization in Cockpit: per flag if FMA publishes standard deferrals and per waiver if FMA confirms individual deferral periods per confirmation ( Bescheid )), the values hereafter are to be seen as initial/default values. FMA may define different periods for all standard or supplemental deferrals (FMA on Sept 29, 2017: Vorab ist anzumerken, dass die FMA Ausnahmen zur Vorhandels- und Aufschub für Nachhandelstransparenz durch Verordnung gemäß 90 Abs 11 WAG 2018 gewähren kann. Die FMA wird davon Gebrauch machen und in einer neuen HandelstransparenzausnahmenVO (ähnlich wie bisher in der HTAusnV) entsprechende Ausnahmen und Aufschübe, nach jetzigem Stand auch für sog. Supplementary Deferral gemäß Art 11 Abs 3 MiFIR (und Art 8 bzw 11 RTS 2) vorsehen. Die Arbeiten daran werden in Q starten. Die VO wird selbstverständlich konsultiert werden.) User Manual TTR II (V1.2) Page 27 / 48

28 Following standard deferral flags (= waivers) are possible: - LRGS (Large in Scale), - SIZE (Transactions above the standard market size), - ILQD (Illiquid instrument), - TPAC (Package transaction) and - XFPH (Exchange for physical transaction). Transactions qualifying for the deferral waivers as mentioned above are made public on the second working day after the date of the transaction at 18:45 CET. In addition to that following supplementary flags / waivers are supported by TTR II, where a competent authority may grant deferred publication differing from the standard mentioned above: Flag Name Description Supplementary deferral flags (RTS 2 only) LMTF Limited details flag First report with publication of limited details in accordance with Art 11(1) (a) (i) FULF Full details flag Transaction for which limited details have been previously published with Art. 11 (1) (a) (i) DATF Daily aggregated transaction flag Publication of daily aggregated transaction in accordance with Art 11 (1) (a) (ii) FULA Full details flag Individual transactions for which aggregated details have been previously published in accordance with Art 11 (1) (a) (ii) VOLO Volume omission flag Transactions for which limited details are published in accordance with Art 11 (1) (b) FULV Full details flag Transactions for which limited details have been previously published in accordance with Art 11 (1) (b) FWAF Four weeks aggregation flag Publication of aggregated transactions in accordance with Art 11(1) (c) FULJ Full details flag Individual transaction which have previously benefited from aggregated publication in accordance with Art. 11 (1) (c) IDAF Indefinite aggregation flag Transactions for which the publication of several transactions in aggregated form for an Transactions for which the publication of several transactions in aggregated form for an indefinite period of time has been allowed in accordance with Article 11(1)(d). VOLW Volume omission flag Transaction for which limited details are published in accordance with Article 11(1)(b) and for which the publication of several transactions in aggregated form for an indefinite period of time will be consecutively allowed in accordance with Article 11(2)(c). User Manual TTR II (V1.2) Page 28 / 48

29 COAF Consecutive aggregation flag Table 5: Supplementary deferral flags (RTS 2 only) Cases, under which supplementary flags are relevant: Transactions for which limited details have been previously published in accordance with Article 11(1)(b) and for which the publication of several transactions in aggregated form for an indefinite period of time has consecutively been allowed in accordance with Article 11(2)(c). There are two general implications of supplementary flags: Flags, which trigger the TTR II deferral (done within TTR II core) (hereinafter marked with TTR II deferral ) Flags, which do not trigger a deferral in TTR II; only the handling of data input checks is modified in these cases (as described accordingly below for each case). This is because the customer has to send full details for the final publication anyway. Case 1: Art 11 (1) (a) (i) In case a customer sends the LMTF flag, the customer has to publish all details but Volume immediately. In this case, no check on volume is done, as the field is empty. In case of the final publication with flag FULF, it is sent by client no later than 19:00 local time on the second working day after the date of the transaction. In case FULF the reporting delay check does not apply. Instead an additional check applies: check, if Trade_Date = t 2 working days and if the Reporting_Date_Time is <= 19:00. If FULF is sent later, a warning is issued. A warning message is sent as a reply to LMTF trade if FULF has not yet been sent after 19:00 local time on the second working day after the date of the transaction. NOTE: In case of LMTF or FULF no automatic deferral is done in TTR II. Case 2: Art 11 (1) (a) (ii) In case a customer sends the DATF flag, the customer has to publish all details on the following working day before 9:00 local time (but volume) for at least 5 aggregated transactions with the same ISIN executed on the same trading day. Price field shall be empty, instead VolumeWeightedAverage shall be published (see Art 11 (4) below as well). In this case the reporting delay, volume and price check do not apply. Instead an additional check applies: check, if Trade_Date = t-1 and if the Reporting_Date_Time is < 9:00. If DATF is sent later, a warning is issued. In case of the final publication of individual transactions including volume the flag FULA is sent by no later than local time on the second working day after the date of the transaction.. In case FULA the reporting delay check does not apply. Instead an additional check applies: check, if Trade_Date = t 2 working days and if the Reporting_Date_Time is <= 19:00. If FULA is sent later, a warning is issued. User Manual TTR II (V1.2) Page 29 / 48

30 A warning message is sent as a reply to DATF trade if FULA has not yet been sent after 19:00 local time on the second working day after the date of the transaction. NOTE: In case of DATF or FULA no automatic deferral is done in TTR II Case 3: Art 11 (1) (b) + (2) (a) + (c) + (3) In case a customer sends the VOLO flag, the customer has to publish all details but Volume immediately. In this case, no check on volume is done, as the field is empty. The final publication including the volume and the flag FULV is made after 4 weeks have lapsed on the next working day before 9:00. In this case the reporting delay check does not apply. Instead an additional check applies: check, if Trade_Date = t- (4 weeks and 1 working day) and if Reporting_Date_Time is < 9:00. If FULV is sent later, a warning is issued. A warning message is sent as a reply to VOLO trade if FULV has not yet been sent after 4 weeks have lapsed on the next working day before 9:00 compared to the date of the transaction. NOTE: In case of VOLO or FULV no automatic deferral is done in TTR II In case the customer sends the VOLW flag, the customer has to publish all details for aggregated transactions but volume immediately. Price field shall be empty, instead VolumeWeightedAverage shall be published (see Art 11 (4) below as well). In this case, no check on price and volume is done, as the fields are empty. The final publication including volume incl. the flag COAF for aggregated transactions previously reported without volume has to be published after 4 weeks on the following Tuesday before 9:00. In this case the reporting delay and price check do not apply. Instead an additional check applies: check, if Trade_Date = t- 4 weeks on the following Tuesday and if Reporting_Date_Time is < 9:00. If COAF is sent later, a warning is issued. A warning message is sent as a reply to VOLW trade if COAF has not yet been sent after 4 weeks on the following Tuesday before 9:00 compared to the date of the transaction. NOTE: In case of VOLW or COAF no automatic deferral is done in TTR II Case 4: Art 11 (1) (c) In case the customer sends the FWAF flag, the customer has to send all details for all aggregated transactions per ISIN (no individual price but only VolumeWeightedAverage) within one calendar week. Publication is deferred one week to the following Tuesday at 8:45. In this case price and the reporting delay check do not apply. NOTE: FWAF triggers an automated deferral in TTR II In case 4 weeks have passed, a customer shall send individual transactions with the FULJ flag. User Manual TTR II (V1.2) Page 30 / 48

31 In this case the reporting delay check does not apply. Instead an additional check applies: check, if Trade_Date = t- 4 weeks and if Reporting_Date_Time is < 9:00. If FULJ is sent later, a warning is issued. Other standard checks apply. A warning message is sent as a reply to FWAF trade if FULJ has not yet been sent after 4 weeks before 9:00 compared to the date of the transaction. NOTE: In case of FULJ no automatic deferral is done in TTR II Case 5: Art 11 (1) (d) In case the customer sends the IDAF flag, the customer has to send all details for all aggregated transactions per ISIN (no individual price but only VolumeWeightedAverage) within one calendar week. Publication is deferred one week to the following Tuesday at 8:45. In this case price and the reporting delay check do not apply. See also Art 11 (4) below. NOTE: IDAF triggers an automated deferral in TTR II Individual transactions do not have to be published for an indefinitive period of time. Art 11 (4) The following is valid for all flags, which mark aggregated data (DATF (only regarding number of trades), FULA, VOLW (only regarding number of trades), COAF, FWAF, IDAF): For daily or weekly aggregated data the customer has to send the following details in respect to each day or week: Volume weighted Average Total traded volume in according measurement unit as described in the table 5 below Total number of transactions Measure of volume Type of instrument All bonds except ETCs and ETNs and structured finance products Volume Total nominal value of debt instruments traded ETCs and ETNs bond types Number of units traded (1) Securitised derivatives Number of units traded (1) Interest rate derivatives Notional amount of traded contracts Foreign Exchange Derivatives Notional amount of traded contracts Equity derivatives Notional amount of traded contracts Commodity derivatives Credit derivatives Contract for differences C10 derivatives Emission allowance derivatives Emission allowances (1) Price per unit Notional amount of traded contracts Notional amount of traded contracts Notional amount of traded contracts Notional amount of traded contracts Tons of Carbon Dioxide equivalent Tons of Carbon Dioxide equivalent User Manual TTR II (V1.2) Page 31 / 48

32 Table 6: Measure of volume for non-equities In general, if the Tuesday of COAF, FWAF or IDAF is no working day, then publishing is done on the next working day at 8:45. Full details to individual transactions are sent with the same TIC as the initial publication without volume is sent (except aggregation flags where no TIC is necessary with the initial publication). Aggregated transactions shall be sent by the customer as one consolidated technical transaction (no price but VolumeWeightedAverage). User Manual TTR II (V1.2) Page 32 / 48

33 5.6. Combinations of Trade Flags In general, any trade with DUPL is not published by TTR II. The flag is mentioned in following two chapters for the sake of completeness Combinations of Trade Flags Equity RTS 1 Valid for: Equity or equity-like financial instruments (Annex III to RTS 1): SHRS shares ETFS ETFs DPRS depositary receipts CRFT certificates (funds, no structrured products as defined by WBAG) OTHR other equity-like financial instruments All flags applicable to TTR II (BENC, ACTX, TNCP, SDIV, LRGS, SIZE, ILQD, RPRI, CANC, AMND, DUPL) can be combined with each other. For details see below: BENC ACTX TNCP SDIV LRGS SIZE ILQD RPRI CANC AMND DUPL BENC x ACTX x TNCP x SDIV x LRGS x SIZE x ILQD x RPRI x CANC x AMND x DUPL x x combination not possible... combination possible For more details to Equity flags, as specified in Table 7, please refer to the ESMA Q&A. Hereafter a short abstract, with amendments for TTR II: User Manual TTR II (V1.2) Page 33 / 48

Annex./1 Scope of Supply and Services TTR II Leistungsverzeichnis TTR II. Version 1.3

Annex./1 Scope of Supply and Services TTR II Leistungsverzeichnis TTR II. Version 1.3 Annex./1 Scope of Supply and Services TTR II Leistungsverzeichnis TTR II Version 1.3 Table of Contents 1. Introduction, Basics and Expected Functionalities... 4 1.1. Abbreviations and terms... 6 2. Asset

More information

TTR II User Manual V 1.3 March 2018

TTR II User Manual V 1.3 March 2018 TTR II User Manual V 1.3 March 2018 Document Information Contact Name Code Contact information Note Alexander Racher AR alexander.racher@wienerborse.at Roland Rotsejdl RR Roland.rotsejdl@wienerborse.at

More information

TTR II User Manual V 1.3 March 2018

TTR II User Manual V 1.3 March 2018 TTR II User Manual V 1.3 March 2018 Document Information Contact Name Code Contact information Note Alexander Racher AR alexander.racher@wienerborse.at Roland Rotsejdl RR Roland.rotsejdl@wienerborse.at

More information

Questions and Answers On MiFID II and MiFIR transparency topics

Questions and Answers On MiFID II and MiFIR transparency topics Questions and Answers On MiFID II and MiFIR transparency topics 03 October 2017 ESMA70-872942901-35 Date: 03 October 2017 ESMA70-872942901-35 ESMA CS 60747 103 rue de Grenelle 75345 Paris Cedex 07 France

More information

Questions and Answers On MiFID II and MiFIR transparency topics

Questions and Answers On MiFID II and MiFIR transparency topics Questions and Answers On MiFID II and MiFIR transparency topics 12 July 2018 ESMA70-872942901-35 Date: 12 July 2018 ESMA70-872942901-35 ESMA CS 60747 103 rue de Grenelle 75345 Paris Cedex 07 France Tel.

More information

Questions and Answers On MiFID II and MiFIR transparency topics

Questions and Answers On MiFID II and MiFIR transparency topics Questions and Answers On MiFID II and MiFIR transparency topics 5 April 2017 ESMA70-872942901-35 Date: 5 April 2017 ESMA70-872942901-35 ESMA CS 60747 103 rue de Grenelle 75345 Paris Cedex 07 France Tel.

More information

Questions and Answers On MiFID II and MiFIR transparency topics

Questions and Answers On MiFID II and MiFIR transparency topics Questions and Answers On MiFID II and MiFIR transparency topics 18 December 2017 ESMA70-872942901-35 Date: 18 December 2017 ESMA70-872942901-35 ESMA CS 60747 103 rue de Grenelle 75345 Paris Cedex 07 France

More information

Release Notes for ADH Release Plan 2017 Version 1.9a

Release Notes for ADH Release Plan 2017 Version 1.9a Release Notes for ADH Release Plan 2017 Version 1.9a November 2017 Document Information Contact Name Code Contact information Note Alexander Racher AR alexander.racher@wienerborse.at Revision Histor Version

More information

APPENDIX 1: NASDAQ APA SERVICE DESCRIPTION

APPENDIX 1: NASDAQ APA SERVICE DESCRIPTION APPENDIX 1: NASDAQ APA SERVICE DESCRIPTION About APA MiFID II introduces a requirement for all investment firms to publish OTC trades executed outside the rules of a trading venue. This requirement was

More information

Cboe Europe Last Sale Specification

Cboe Europe Last Sale Specification Cboe Europe Last Sale Specification Version 1.3 19 July 2017 Cboe Europe Limited is a Recognised Investment Exchange regulated by the Financial Conduct Authority. Cboe Europe Limited is an indirect wholly-owned

More information

ISE OBOE Release 1.2. OBOE Market Model. Publication Date 8 th May 2018 Release Date 1 st March Version: 1.4

ISE OBOE Release 1.2. OBOE Market Model. Publication Date 8 th May 2018 Release Date 1 st March Version: 1.4 ISE OBOE Release 1.2 OBOE Market Model Version: 1.4 Publication Date 8 th May 2018 Release Date 1 st March 2018 ISE OBOE powered by Deutsche Börse 7 Market Technology Contents 1 Introduction 4 2 Overview

More information

MiFID II Challenges and MTS Solutions

MiFID II Challenges and MTS Solutions MiFID II Challenges and MTS Solutions Contents 1. Transparency 2 2. Reporting 11 3. Data 15 4. Glossary 17 Transparency MiFID II transparency Client questions: When does transparency apply? How am I affected??

More information

MiFID II PRE AND POST TRADE REPORTING SERVICE DESCRIPTION

MiFID II PRE AND POST TRADE REPORTING SERVICE DESCRIPTION MiFID II PRE AND POST TRADE REPORTING SERVICE DESCRIPTION 14 February 2018 VERSION 1.3 Status: Published 2018 Cboe Global Markets 1 2 Contents 1. INTRODUCTION... 5 2. HOW CBOE WORKS... 5 3. THE SERVICES...

More information

MiFID II PRE AND POST TRADE REPORTING SERVICE DESCRIPTION

MiFID II PRE AND POST TRADE REPORTING SERVICE DESCRIPTION MiFID II PRE AND POST TRADE REPORTING SERVICE DESCRIPTION 30 August 2017 VERSION 1.2 Status: Published 2017 Bats Global Markets 1 2 Contents 1. INTRODUCTION... 4 2. HOW BATS WORKS... 4 3. THE SERVICES...

More information

Trading Manual. Zagreb, December 2018

Trading Manual. Zagreb, December 2018 Zagreb, December 2018 DISCLAIMER: Please note that this is a convenience translation of the which serves for information purposes only. The original Croatian text is binding in all respects. Contents:

More information

Appendix n: Manual Trades

Appendix n: Manual Trades Early draft proposal for INET Nordic Market Model version effective as of January 3, 2017 Appendix n: Manual Trades For trading on-exchange, the Member can either make Trades in the Order Book or outside

More information

Information handbook for audit trail, transaction and other regulatory reportings under the MiFID II/ MiFIR regime. Frankfurt Stock Exchange and Eurex

Information handbook for audit trail, transaction and other regulatory reportings under the MiFID II/ MiFIR regime. Frankfurt Stock Exchange and Eurex Information handbook for audit trail, transaction and other regulatory reportings under Frankfurt Stock Exchange and Eurex Release Date September 2017 Page 2 of 41 Abstract This document outlines the new

More information

TRADE REPORTING SERVICES SERVICE DESCRIPTION

TRADE REPORTING SERVICES SERVICE DESCRIPTION TRADE REPORTING SERVICES SERVICE DESCRIPTION 10 May 2016 VERSION 2.0 2016 Bats Global Markets 1 2 Contents 1. INTRODUCTION... 4 2. HOW BATS WORKS... 4 3. THE SERVICES... 4 3.1 TDM Service... 4 3.2 SI Quoting

More information

Trading Manual. Zagreb, 27 December 2017

Trading Manual. Zagreb, 27 December 2017 Zagreb, 27 December 2017 DISCLAIMER: Please note that this is a convenience translation of the which serves for information purposes only. The original Croatian text is binding in all respects. Contents:

More information

Outstanding uncertainties in the MiFIR post trade transparency framework

Outstanding uncertainties in the MiFIR post trade transparency framework 13 November 2017 Verena Ross European Securities and Markets Authority 103 Rue de Grenelle 75007 Paris France Outstanding uncertainties in the MiFIR post trade transparency framework Dear Verena, One of

More information

London Stock Exchange. Millennium Exchange MiFID II Deployment Guide

London Stock Exchange. Millennium Exchange MiFID II Deployment Guide London Stock Exchange Millennium Exchange MiFID II Deployment Guide Issue 3.0 28 December 2017 Contents 1.0 Purpose 5 2.0 Document History 6 3.0 References to MiFIR / MiFID II documentation published

More information

Client FIX Specification Modifications for MiFID II/R Equity/Equity-Like & FFO Instruments

Client FIX Specification Modifications for MiFID II/R Equity/Equity-Like & FFO Instruments Introduction This document outlines the changes to our FIX messaging specifications being implemented to support MiFID II/R for equity (and equity-like) and FFO instruments. Much of the material here is

More information

Turquoise. Millennium Exchange MiFID II Deployment Guide Proposal

Turquoise. Millennium Exchange MiFID II Deployment Guide Proposal Turquoise Millennium Exchange MiFID II Deployment Guide Proposal Issue 1.2 29 December 2017 Contents 1.0 Purpose 4 2.0 Document History 5 3.0 References to MiFIR / MiFID II documentation published by

More information

Questions and Answers On MiFIR data reporting

Questions and Answers On MiFIR data reporting Questions and Answers On MiFIR data reporting 26 September 2018 ESMA70-1861941480-56 Date: 25 May 2018 ESMA70-1861941480-56 ESMA CS 60747 103 rue de Grenelle 75345 Paris Cedex 07 France Tel. +33 (0) 1

More information

MiFID II / MiFIR Transaction Reporting and Transparency

MiFID II / MiFIR Transaction Reporting and Transparency MiFID II / MiFIR Transaction Reporting and Transparency Speakers: Simon Sloan, Head of Function, Asset Management Supervision, Central Bank of Ireland Anne Marie Pidgeon, Securities and Markets Supervision,

More information

Genium INET Market Model

Genium INET Market Model Fixed Income Derivatives Nasdaq Derivatives Markets Revision [1.0] 24 Nov 2017 2017 Nasdaq, Inc. All Rights Reserved. Document History Revision Published Author(s) Summary of Changes 1.0 [24 11 2017] Fixed

More information

MiFID II: The Unbundling ISITC Meeting

MiFID II: The Unbundling ISITC Meeting MiFID II: The Unbundling ISITC Meeting Nick Philpott 18 September 2017 0 Salmon is illiquid ESMA December 2014 Consultation Paper on MiFID II / MiFIR, p. 141 https://www.esma.europa.eu/press-news/consultations/consultation-mifid-iimifir

More information

MiFID II Meeting

MiFID II Meeting MiFID II Meeting 07.02.2017 Presentation and Review of the proposed new VDF Structures Manuel Alonso Agenda Introduction Proposed new structure technical explanation and examples Specific topics and discussion

More information

ATHEX & its Members in the process of bridging MiFID II

ATHEX & its Members in the process of bridging MiFID II ATHEX & its Members in the process of bridging MiFID II Market Operation & Member Support Division Members Support Dpt General Scope of presentation: To provide the status of ATHEX s services & systems

More information

ESMA DISCUSSION PAPER MiFID II/MiFIR

ESMA DISCUSSION PAPER MiFID II/MiFIR ESMA DISCUSSION PAPER MiFID II/MiFIR Summary of ESMA s Market Data Reporting Proposals June 2014 1 Contents Transaction reporting (slides 3-18) Instrument reference data (slides 19-21) Maintaining records

More information

Fixed Income Cash Markets Genium INET Functional Changes. Document Updated:

Fixed Income Cash Markets Genium INET Functional Changes. Document Updated: Fixed Income Cash Markets Genium INET 5.0.0201 Functional Changes Document Updated: 2017-09-14 Contents 1 Introduction 3 2 Manual trade reports on exchange 3 2.1 Manual trade reports 3 2.2 Deferred Trade-Publication

More information

MiFID II / MiFIR post-trade reporting requirements

MiFID II / MiFIR post-trade reporting requirements MiFID II / MiFIR post-trade reporting requirements Understanding bank and investor obligations September 2017 Association for Financial Markets in Europe www.afme.eu Disclaimer The AFME : Understanding

More information

Release Notes 23 February 2018

Release Notes 23 February 2018 Release Notes 23 February 2018 London Stock Exchange Derivatives Market SOLA Trading System - Version 12 Release notes Guidelines 23 February 2018 Version 1.0 1 1.0 Document history This document has been

More information

Reporting Guideline, version 2.1. Members On Exchange trade and Members and Non-Members OTC trade Reporting. November 20, 2017 INET NORDIC

Reporting Guideline, version 2.1. Members On Exchange trade and Members and Non-Members OTC trade Reporting. November 20, 2017 INET NORDIC Reporting Guideline, version 2.1 Members On Exchange trade and Members and Non-Members OTC trade Reporting November 20, 2017 INET NORDIC 1/21 1. General information on reporting 1.1 The Nasdaq Nordic Reporting

More information

10 November InfoNet. MiFID II/R Seminar. Transparency. Sponsored by

10 November InfoNet. MiFID II/R Seminar. Transparency. Sponsored by 10 November 2015 InfoNet MiFID II/R Seminar Transparency Sponsored by PRESENTATION Fabio Braga, Technical Specialist, Trading Venues Policy, FCA INFONET 10 November 2015 Transparency & Market Structure

More information

Use of UK data in ESMA databases and performance of MiFID II calculations in case of a no-deal Brexit

Use of UK data in ESMA databases and performance of MiFID II calculations in case of a no-deal Brexit 5 February 2019 ESMA70-155-7026 PUBLIC STATEMENT Use of UK data in ESMA databases and performance of MiFID II calculations in case of a no-deal Brexit The European Securities and Markets Authority (ESMA)

More information

(Text with EEA relevance)

(Text with EEA relevance) L 87/174 COMMISSION DELEGATED REGULATION (EU) 2017/577 of 13 June 2016 supplementing Regulation (EU) No 600/2014 of the European Parliament and of the Council on markets in financial instruments with regard

More information

COMMISSION DELEGATED REGULATION (EU) /... of

COMMISSION DELEGATED REGULATION (EU) /... of EUROPEAN COMMISSION Brussels, 14.7.2016 C(2016) 4390 final COMMISSION DELEGATED REGULATION (EU) /... of 14.7.2016 supplementing Regulation (EU) No 600/2014 of the European Parliament and of the Council

More information

Producing RTS 27 & 28 Reports

Producing RTS 27 & 28 Reports #FIXEMEA2018 Producing RTS 27 & 28 Reports Alex Wolcough Director, Appsbroker Hanno Klein Co-Chair Global Technical Committee and Co-Chair High Performance Working Group, FIX Trading Community, Senior

More information

Tick Size Regime at WBAG RTS 11: Tick size regime for shares, depositary receipts and exchange traded funds

Tick Size Regime at WBAG RTS 11: Tick size regime for shares, depositary receipts and exchange traded funds Tick Size Regime at WBAG RTS 11: Tick size regime for shares, depositary receipts and exchange traded funds Current WBAG Tick Size Regime for different Asset Classes Instrument Type Equities ETFs (Investment

More information

FIRDS Transparency System

FIRDS Transparency System FIRDS Transparency System Instructions on download and use of full and delta transparency results 18 December 2017 ESMA65-8-5240 Date: 18 December 2017 ESMA65-8-5240 Document control: Version Date Author

More information

Consultation Paper Draft implementing technical standards under MiFID II

Consultation Paper Draft implementing technical standards under MiFID II Consultation Paper Draft implementing technical standards under MiFID II 31/08/2015 ESMA/2015/1301 Date: 31 August 2015 ESMA/2015/1301 Responding to this paper The European Securities and Markets Authority

More information

CBOE EUROPE EQUITIES GUIDANCE NOTE 2017 Q2 EXCHANGE RELEASE

CBOE EUROPE EQUITIES GUIDANCE NOTE 2017 Q2 EXCHANGE RELEASE CBOE EUROPE EQUITIES GUIDANCE NOTE 2017 Q2 EXCHANGE RELEASE EFFECTIVE 14TH JULY 2017 VERSION 1.1 Cboe Europe Limited is a Recognised Investment Exchange regulated by the Financial Conduct Authority. Cboe

More information

(Text with EEA relevance) (OJ L 173, , p. 84)

(Text with EEA relevance) (OJ L 173, , p. 84) 02014R0600 EN 01.07.2016 001.002 1 This text is meant purely as a documentation tool and has no legal effect. The Union's institutions do not assume any liability for its contents. The authentic versions

More information

Fixed Income Cash Markets Genium INET Functional Changes. Document Updated:

Fixed Income Cash Markets Genium INET Functional Changes. Document Updated: Fixed Income Cash Markets Genium INET 5.0.0201 Functional Changes Document Updated: 2017-10-12 Revision History 2017-09-14 1.0 Initial description 2017-10-12 1.1 Updates to implementation dates for Circuit

More information

Post-Trade Transparency Interface Specification

Post-Trade Transparency Interface Specification Please respond to: LME IT Solutions Delivery THE LONDON METAL EXCHANGE 10 Finsbury Square, London EC2A 1AJ Tel +44 (0)20 7113 8888 Registered in England no 2128666. Registered LME.COM Change History Revision

More information

(hereinafter: WBAG) and and (hereinafter: Contractual Partner)

(hereinafter: WBAG) and and (hereinafter: Contractual Partner) agreed by Wiener Börse AG Wallnerstraße 8 A - 1010 Vienna (hereinafter: WBAG) and and (hereinafter: Contractual Partner) I. Preamble By notification of 3 April 1998, the Ministry of Finance in agreement

More information

ICE Futures Europe and ICE Endex

ICE Futures Europe and ICE Endex ICE Futures Europe and ICE Endex MiFID II Position Reporting August 2017 Version 1.0. Contents 1 External... 4 2 Overview... 5 2.1 Document Purpose... 5 2.2 ICE MFT... 6 2.3 ICE Market Oversight... 6 3

More information

FAQs on MiFID II - Transitional Transparency Calculations

FAQs on MiFID II - Transitional Transparency Calculations ESMA50-164-677 15 May 2018 FAQs on MiFID II - Transitional Transparency Calculations Scope: This document aims at gathering Frequently Asked Questions (FAQs) and answers regarding the publication of the

More information

Market making agreements and schemes at WBAG RTS 8: Specifying the requirements on market making agreements and schemes

Market making agreements and schemes at WBAG RTS 8: Specifying the requirements on market making agreements and schemes Market making agreements and schemes at WBAG RTS 8: Specifying the requirements on market making agreements and schemes Existing Market Maker regimes and MiFID II Today, market making programs are already

More information

ESMA Consultation Paper on Review of the technical standards on reporting under Article 9 of EMIR (10 November 2014 ESMA/2014/1352)

ESMA Consultation Paper on Review of the technical standards on reporting under Article 9 of EMIR (10 November 2014 ESMA/2014/1352) E u r e x C l e a r i n g R e s p o n s e t o ESMA Consultation Paper on Review of the technical standards on reporting under Article 9 of EMIR (10 ) Frankfurt am Main, 09 February 2015 Acronyms Used CM

More information

London Stock Exchange Derivatives Market

London Stock Exchange Derivatives Market London Stock Exchange Derivatives Market LSEDM 401 HSVF Market Data Technical Specification (SOLA 11) Issue 5.1 31 March 2017 Contents 1.0 Introduction 6 6.4 Message Type ES: Instrument Schedule Notice

More information

London Stock Exchange. TRADEcho MiFID II Deployment Guide

London Stock Exchange. TRADEcho MiFID II Deployment Guide London Stock Exchange TRADEcho MiFID II Deployment Guide Issue 2.0 19 October 2017 Contents 1.0 Purpose 5 2.0 Document History 6 3.0 References to MiFIR / MiFID II documentation published by London Stock

More information

Trax Transparency Solution

Trax Transparency Solution Trax Transparency Solution Your Fast Track to European Regulatory Change Comply with Confidence European Markets are Experiencing Unprecedented Change Impact of MiFID II Transparency The EU Markets in

More information

CBOE EUROPE MMTV3.04 GUIDANCE

CBOE EUROPE MMTV3.04 GUIDANCE CBOE EUROPE MMTV3.04 GUIDANCE VERSION 1.0 Cboe Trading Limited is a Recognised Investment Exchange regulated by the Financial Conduct Authority. Cboe Trading Limited is an indirect wholly-owned subsidiary

More information

Bloomberg MiFID II solutions guide.

Bloomberg MiFID II solutions guide. Bloomberg MiFID II solutions guide. MiFID II: Welcome to the new regime. A full calendar year is a long time or is it? On 3 January 2018, Europe will see the update to the Markets in Financial Instrument

More information

Final Report Draft technical standards on data to be made publicly available by TRs under Article 81 of EMIR

Final Report Draft technical standards on data to be made publicly available by TRs under Article 81 of EMIR Final Report Draft technical standards on data to be made publicly available by TRs under Article 81 of EMIR 10 July 2017 ESMA70-151-370 10 July 2017 ESMA70-151-370 1 Table of Contents 1 Executive Summary...

More information

Reply form for the Consultation Paper on MiFID II / MiFIR

Reply form for the Consultation Paper on MiFID II / MiFIR Reply form for the Consultation Paper on MiFID II / MiFIR 19 December 2014 Responding to this paper The European Securities and Markets Authority (ESMA) invites responses to the specific questions listed

More information

As our brand migration will be gradual, you will see traces of our past through documentation, videos, and digital platforms.

As our brand migration will be gradual, you will see traces of our past through documentation, videos, and digital platforms. We are now Refinitiv, formerly the Financial and Risk business of Thomson Reuters. We ve set a bold course for the future both ours and yours and are introducing our new brand to the world. As our brand

More information

FREQUENTLY ASKED QUESTIONS

FREQUENTLY ASKED QUESTIONS NOV 2017 MARKETS IN FINANCIAL INSTRUMENTS DIRECTIVE II (MIFID II) FREQUENTLY ASKED QUESTIONS Table of Contents Background...4 What is MiFID?... 4 The general objectives of MiFID II are to:... 4 How was

More information

Consultation Paper Review of the technical standards on reporting under Article 9 of EMIR

Consultation Paper Review of the technical standards on reporting under Article 9 of EMIR Consultation Paper Review of the technical standards on reporting under Article 9 of EMIR 10 November 2014 ESMA/2014/1352 Date: 10 November 2014 ESMA/2014/1352 Annex 1 Responding to this paper ESMA invites

More information

Bloomberg SSEOMS MiFID II - FIX Orders and Executions Flat Tags

Bloomberg SSEOMS MiFID II - FIX Orders and Executions Flat Tags Bloomberg SSEOMS MiFID II - FIX Orders and Executions Flat s Bloomberg s Sell Side Execution and Order Management Solution (SSEOMS) is updating the electronic FIX interface to support the latest tag extensions

More information

FIA MiFID II Exchange Readiness Questionnaire

FIA MiFID II Exchange Readiness Questionnaire Communication and Collaboration FIA MiFID II Readiness Questionnaire A.1 What are your plans for communicating MiFID II updates to your members and participants during 2017? The consultation period for

More information

London Stock Exchange Derivatives Market. MiFID II Deployment Guide Proposal

London Stock Exchange Derivatives Market. MiFID II Deployment Guide Proposal London Stock Exchange Derivatives Market MiFID II Deployment Guide Proposal Issue 1.1 28 August 2017 Contents 1.0 Purpose 5 2.0 Document History 6 3.0 References to MiFIR / MiFID II documentation published

More information

Reporting Guideline, version 2.0. Members On Exchange trade and Members and Non-Members OTC trade Reporting. September 18, 2017 INET NORDIC

Reporting Guideline, version 2.0. Members On Exchange trade and Members and Non-Members OTC trade Reporting. September 18, 2017 INET NORDIC Reporting Guideline, version 2.0 Members On Exchange trade and Members and Non-Members OTC trade Reporting September 18, 2017 INET NORDIC 1/21 1. General information on reporting 1.1 The Nasdaq Nordic

More information

Questions and Answers On MiFID II and MiFIR transparency topics

Questions and Answers On MiFID II and MiFIR transparency topics Questions and Answers On MiFID II and MiFIR transparency topics 19 December 2016 ESMA/2016/1424 Date: 19 December 2016 ESMA/2016/1424 ESMA CS 60747 103 rue de Grenelle 75345 Paris Cedex 07 France Tel.

More information

lucht probst associates gmbh MiFID II Index Contents

lucht probst associates gmbh MiFID II Index   Contents Contents Markets in Financial Instruments Directive (MiFID II) Directive No. 2014/65/EU... 2 Markets in Financial Instruments Regulation (MiFIR) Regulation (EU) No. 600/2014... 10 Overview of Level I,

More information

Questions and Answers On MiFID II and MiFIR transparency topics

Questions and Answers On MiFID II and MiFIR transparency topics Questions and Answers On MiFID II and MiFIR transparency topics 18 November 2016 ESMA/2016/1424 Date: 18 November 2016 ESMA/2016/1424 ESMA CS 60747 103 rue de Grenelle 75345 Paris Cedex 07 France Tel.

More information

BME markets Transaction Reporting Service. TRS v 2.1

BME markets Transaction Reporting Service. TRS v 2.1 BME markets Transaction Reporting Service TRS v 2.1 8 Jun 2018 Contents 1. BME markets transaction reporting service... 4 Introduction... 4 Notification of transaction reporting records to the competent

More information

Fixed Income New Market Model. October 2017

Fixed Income New Market Model. October 2017 Fixed Income October 2017 Main Implications for Fixed Income The Directive imposes new obligations and requirements on all market participants Aims to move OTC trades onto Trading Venues MiFID II Greater

More information

LSE Equity Trade and Quote Data File Format Document Version 3.1

LSE Equity Trade and Quote Data File Format Document Version 3.1 LSE Equity Trade and Quote Data File Format Document Version 3.1 LSE Equity Trade and Quote Dataset, v3.1 Page 1 of 17 Overview Tick Data provides three types of market data for issues traded on the London

More information

Introduction to Client Online

Introduction to Client Online Introduction to Client Online Trade Finance Guide TradeFinanceNewClientsV2Sept15 Contents Introduction 3 Welcome to your introduction to Client Online 3 If you have any questions 3 Logging In 4 Welcome

More information

Nasdaq Implementation Guide. Transaction Reporting Version 1.0. Oct 2, 2017

Nasdaq Implementation Guide. Transaction Reporting Version 1.0. Oct 2, 2017 Nasdaq Implementation Guide Transaction Reporting Version 1.0 Oct 2, 2017 Date Version Description of change 2017-10-02 1.0 Initial version LEGAL DISCLAIMER The content of this document is subject to change

More information

Commentary of Wiener Börse AG on CESR s Advice on Possible Implementing Measures of the Directive 2004/39/EC on Markets in Financial Instruments

Commentary of Wiener Börse AG on CESR s Advice on Possible Implementing Measures of the Directive 2004/39/EC on Markets in Financial Instruments Commentary of Wiener Börse AG on CESR s Advice on Possible Implementing Measures of the Directive 2004/39/EC on Markets in Financial Instruments Wiener Börse AG welcomes the possibility to comment on the

More information

SIX Corporate Bonds AG. Directive 3: Trading. Dated 16 March 2018 Entry into force: 27 March 2018

SIX Corporate Bonds AG. Directive 3: Trading. Dated 16 March 2018 Entry into force: 27 March 2018 SIX Corporate Bonds AG Directive : Trading Dated 6 March 08 Entry into force: 7 March 08 Content Purpose and principle... General.... Trading day and trading period.... Trading hours... Definitions....

More information

Business Requirements Document FIRDS Reference Data

Business Requirements Document FIRDS Reference Data Business Requirements Document FIRDS Reference Data 30 October 2015 ESMA/2015/MDSC/1 Date: 30 October 2015 ESMA/2015/MDSC/1 Document control: Version Date Author Comments 0.1 11/11/2014 Jerry Nason First

More information

T7 Release 6.1. Functional Reference

T7 Release 6.1. Functional Reference T7 Release 6.1 Functional Reference Date 30 th April 2018 Content 1. Introduction... 6 1.1 Content of this document... 6 1.2 Usage Notes... 7 1.3 Further reading... 7 1.4 Abbreviations and Definitions...

More information

Final Report Amendments to Commission Delegated Regulation (EU) 2017/587 (RTS 1)

Final Report Amendments to Commission Delegated Regulation (EU) 2017/587 (RTS 1) Final Report Amendments to Commission Delegated Regulation (EU) 2017/587 (RTS 1) 26 March 2018 ESMA70-156-354 Table of Contents 1 Executive Summary... 3 2 Prices reflecting prevailing market conditions...

More information

Summary Member Impact - OMnet Genium INET (November 2017)

Summary Member Impact - OMnet Genium INET (November 2017) Summary Member Impact - OMnet Genium INET 5.0.0210 (November 2017) Contents 1. Purpose of the Document... 5 2. Reference Data... 5 2.1 Trade Report Type... 5 2.1.1 Description... 5 2.1.2 Messages... 5

More information

Cboe Europe Regulatory Transaction Reporting Service Description

Cboe Europe Regulatory Transaction Reporting Service Description Cboe Europe Regulatory Transaction Reporting Service Description Version 1.4 23rd November, 2017 Cboe Europe Limited is a Recognised Investment Exchange regulated by the Financial Conduct Authority. Cboe

More information

Shared: Budget Adjustments Import

Shared: Budget Adjustments Import Shared: Budget Adjustments Import User Guide Applies to these SAP Concur solutions: Expense Professional/Premium edition Standard edition Travel Professional/Premium edition Standard edition Invoice Professional/Premium

More information

CLEARING OF OTC TRADES IN LISTED EQUITY DERIVATIVES SERVICE DESCRIPTION

CLEARING OF OTC TRADES IN LISTED EQUITY DERIVATIVES SERVICE DESCRIPTION CLEARING OF OTC TRADES IN LISTED EQUITY DERIVATIVES SERVICE DESCRIPTION INTRODUCTION As a response to the changes in market structure brought about by the MiFID2/R Nasdaq is extending the current OTC clearing

More information

Market Model for the Trading Venue Xetra

Market Model for the Trading Venue Xetra Market Model for the Trading Venue Xetra Deutsche Börse AG All proprietary rights and rights of use of this Xetra publication shall be vested in Deutsche Börse AG and all other rights associated with this

More information

Nasdaq Commodities Europe

Nasdaq Commodities Europe Upcoming Functional Changes Genium INET 5.0.0201 Revision 1.2 17 Oct 2017 2017 Nasdaq, Inc. All Rights Reserved. Copyright 2017, Nasdaq, Inc. All rights reserved. All content in this document is owned,

More information

ANNA-DSB Product Committee Final ISIN Principles 28 th March 2017

ANNA-DSB Product Committee Final ISIN Principles 28 th March 2017 ANNA-DSB Product Committee Final ISIN Principles 28 th March 2017 1 Executive Summary European legislation MiFID II/MiFIR & MAR have specified the use of ISIN for all the instruments in-scope, including

More information

Introduction to Client Online

Introduction to Client Online Introduction to Client Online Bibby Factors International Guide 1 InternationalFactoringNewClientBibbyUKopsSept15 Introduction 3 Logging In 5 Welcome Screen 6 Navigation 7 Viewing Your Account 9 Invoice

More information

ANNEXES. to the. COMMISSION DELEGATED REGULATION (EU) /... of XXX

ANNEXES. to the. COMMISSION DELEGATED REGULATION (EU) /... of XXX EUROPEAN COMMISSION Brussels, 28.7.2016 C(2016) 4733 final ANNEXES 1 to 2 ANNEXES to the COMMISSION DELEGATED REGULATION (EU) /... of XXX supplementing Regulation (EU) No 600/2014 of the European Parliament

More information

Technical Specifications 01 November January SOLA Derivatives HSVF Market Data. SOLA 12 Drop 4: V November 2018

Technical Specifications 01 November January SOLA Derivatives HSVF Market Data. SOLA 12 Drop 4: V November 2018 Technical Specifications 01 November 201827 January 2014 SOLA Derivatives HSVF Market Data SOLA 12 Drop 4: V9.0 01 November 2018 1 1 Introduction 7 1.1 Purpose 7 1.2 Readership 7 1.3 Revision History 7

More information

SOCIÉTÉ GÉNÉRALE CORPORATE AND INVESTMENT BANKING SYSTEMATIC INTERNALISER PRE-TRADE COMMERCIAL POLICY UNDER MIFID II / MIFIR 3 JANUARY 2018

SOCIÉTÉ GÉNÉRALE CORPORATE AND INVESTMENT BANKING SYSTEMATIC INTERNALISER PRE-TRADE COMMERCIAL POLICY UNDER MIFID II / MIFIR 3 JANUARY 2018 SOCIÉTÉ GÉNÉRALE CORPORATE AND INVESTMENT BANKING SYSTEMATIC INTERNALISER PRE-TRADE COMMERCIAL POLICY UNDER MIFID II / MIFIR 3 JANUARY 2018 Société Générale is a French credit institution (Bank - Investment

More information

EN 422 EN CHAPTER 7: MARKET DATA REPORTING. RTS 22: Draft regulatory technical standards on reporting obligations under Article 26 of MiFIR

EN 422 EN CHAPTER 7: MARKET DATA REPORTING. RTS 22: Draft regulatory technical standards on reporting obligations under Article 26 of MiFIR CHAPTER 7: MARKET DATA REPORTING RTS 22: Draft regulatory technical standards on reporting obligations under Article 26 of MiFIR EUROPEAN COMMISSION Brussels, XXX [ ](2012) XXX draft COMMISSION DELEGATED

More information

MiFID II pre and post trade transparency. Damian Carolan and Sidika Ulker 12 October 2017

MiFID II pre and post trade transparency. Damian Carolan and Sidika Ulker 12 October 2017 MiFID II pre and post trade transparency Damian Carolan and Sidika Ulker 12 October 2017 Allen & Overy 2017 Agenda 1 Overview of the MiFID II transparency regime 2 Extraterritorial considerations in respect

More information

Manual of Transaction Reporting of Borsa Italiana

Manual of Transaction Reporting of Borsa Italiana Manual of Transaction Reporting of Borsa Italiana Guidelines for Transaction Reporting by Non-MiFID member firms This document is relevant for members of the trading venues operated and managed by Borsa

More information

TABLE OF CONTENTS General Admission Criteria Ongoing Obligations

TABLE OF CONTENTS General Admission Criteria Ongoing Obligations Rules prime market TABLE OF CONTENTS General 4 1. Scope of Application 4 2. Participation Bid and Decision on Participation 4 Participation Bid 4 Competence for Stating the Grounds for Acceptance or Rejection

More information

Nasdaq Nordics Introduction to the main MiFID II requirements.

Nasdaq Nordics Introduction to the main MiFID II requirements. Nasdaq Nordics Introduction to the main MiFID II requirements. 13 November 2017 Table of Contents Background...3 Market structure...4 Trading obligation...5 Pre and post Trade Transparency...5 Organizational

More information

ANNEX. to the COMMISSION DELEGATED REGULATION (EU).../...

ANNEX. to the COMMISSION DELEGATED REGULATION (EU).../... EUROPEAN COMMISSION Brussels, 19.10.2016 C(2016) 6624 final ANNEX 1 ANNEX to the COMMISSION DELEGATED REGULATION (EU).../... amending Commission Delegated Regulation (EU) No 148/2013 supplementing Regulation

More information

Reply form for the ESMA MiFID II/MiFIR Discussion Paper

Reply form for the ESMA MiFID II/MiFIR Discussion Paper Reply form for the ESMA MiFID II/MiFIR Discussion Paper 22 May 2014 Date: 22 May 2014 Responding to this paper The European Securities and Markets Authority (ESMA) invites responses to the specific questions

More information

MiFID II Transaction reporting: Detecting and investigating potential market abuse

MiFID II Transaction reporting: Detecting and investigating potential market abuse www.pwc.com Transaction reporting: Detecting and investigating potential market abuse July 2017 Transaction reporting Executive summary In 2007 MiFID I introduced the concept of a harmomised transaction

More information

UniCredit Bank AG Systematic Internaliser Service Description September 2018

UniCredit Bank AG Systematic Internaliser Service Description September 2018 UniCredit Bank AG Systematic Internaliser Service Description September 2018 1. INTRODUCTION Under the Directive (EU) No. 65 / 2014 on markets in financial instruments and Regulation (EU) No. 600 / 2014

More information

AFME, CBOE and LSE Paper on the application of the tick size regime

AFME, CBOE and LSE Paper on the application of the tick size regime AFME, CBOE and LSE Paper on the application of the tick size regime 7 September 2018 AFME, CBOE and the London Stock Exchange Group (the Organisations) believe that tick sizes have an important role to

More information

Introduction to Client Online

Introduction to Client Online Introduction to Client Online Construction Finance Guide ConstructionFinanceNewClientsV2Sept15 Contents Introduction 3 Welcome to your introduction to Client Online 3 If you have any questions 3 Logging

More information