FAQ

Technical interface changes

What MICs will be supported by the two venues?

Please refer to our Market Identifier Codes page.

Will there be any reference data file format changes?

  • Symbol reference data file:

    The mic column shall be populated with the value of CEUX for symbols uniquely listed on the NL regulated market.

    The bloomberg_bats and reuters_ric_bats columns present in the symbol reference file for each environment will be as described in Table 2 below. Use of these exchange codes is subject to agreement with Bloomberg and Refinitiv.

    Venue Bloomberg Exchange Code
    (bloomberg_bats)
    Refinitiv (Reuters) Exchange Code
    (reuters_ric_bats)
    BXE EB .BS
    CXE IX .CHI
    DXE I2 .DXE
    Table 2: Exchange Codes
  • Trade data file:
    The contra column in the Trade Data File will be populated with the value of CEUX for DXE for all order book executions.
Back to top

Pricing

What will the pricing be for UK and NL venues?

The fee schedules that apply for Cboe UK and Cboe NL can be found here.

Back to top

Regulatory Data and Transaction Reporting

Do I need to supply an additional long code mapping file via the Identifier Management application for any order activity on the NL venue?

No. Long to short code mappings shall apply to both the UK and NL venues; Participants will therefore only be required to upload their mappings once for them to apply to both venues. As a consequence of this participants will not be able to use a different mapping per short code for each venue.

Will I need to provide transaction reporting information if the current transition period is extended?

If the transition period is extended then the current requirements will continue, whereby only Non-UK or EEA Participants (current third country firms such as Swiss or Cayman regulated firms) on each venue respectively will be required to submit transaction reports to Cboe UK and NL separately, in order for Cboe to meet its obligation to the FCA and AFM respectively.

Will I need to provide transaction reporting information if the transition period ends on 31 December as scheduled?

Cboe UK will be required to transaction report for transactions conducted on the RIE by members who are not UK regulated, except for EEA firms operating through a branch and who are subject to FCA transaction reporting requirements under the temporary permissions regime. Cboe NL will be required to transaction report on behalf of any non-EEA members trading on its markets (which includes UK domiciled firms).

What trading activity is in scope if I do need to transaction report?

The only on-exchange activity that is potentially exempt from transaction reporting is exchange trade reports (ETRs) that are used for settlement purposes (sometimes referred to as End of Day ETRs).

What solutions are on offer in the event I need to transaction report?

  • Cboe Regulatory Transaction Reporting Gateway:
    Participants should use the Cboe Regulatory Transaction Reporting Gateway (RTRG) service to submit transaction reports to Cboe Europe who will then forward them onto the required regulator. The specification for this service can be found here and Participants who need to begin using this service should contact Trade Desk to begin on-boarding.
  • Cboe Deal Capacity Offering:

    The introduction of participant short code information on orders through MIFID II means that (if used correctly) Cboe Europe have the information required to generate transaction reports for clients conducting trading activity in a Deal (Principal) capacity. Participants opting in to this offering will have transactions for their order book executions generated and sent to the required regulator by Cboe. Please note that at this time, ETRs are excluded from this service and therefore any non EOD ETR transactions will need to be submitted to Cboe Europe via the RTRG. Participants wishing to use this offering should contact their Account Manager who can provide the next steps.

    Participants can opt in to this offering at a bank code (clearing firm) level. Any bank codes that have opted in, which submit orders matching the below, along with any non EOD ETRs, will be rejected:
    • AOTC (Agency) orders
    • MTCH (Riskless) orders
    • Orders submitted without both an execution and investment short code
    • Orders submitted with non-registered short codes. For a registration to be considered valid, it must be uploaded by 5am UK time on the day it is to be used. Any registrations after this time will not take effect until the next trading day.
    In addition, Participants must:
  • Unavista:

    Participants that use Unavista to transaction report to competent authorities may also be able to use it to report details of Cboe transactions to Cboe UK and Cboe NL.

Back to top

Cboe LIS

What are the plans regarding Cboe LIS in the event of a transition deal being established with no share trading obligation?

Cboe NL will prepare to offer the LIS service and will prepare its participants to be ready for an end of year launch, however in the event of a transition and no EU STO, then it may take the decision not to launch. Therefore EU participants should retain their Cboe UK membership and connectivity.

In the event of an EU Share Trading Obligation (STO) do the above plans changes?

In the event of an EU STO being implemented Cboe NL will launch with the LIS product, supporting EEA stocks in 16 markets with the execution MIC of LISZ.

Post January 2021, Cboe UK will continue to offer the LIS product on all 18 markets under the LISX MIC, as it does today.

For further information please refer to Cboe LIS.

Are there different LIS thresholds for LISX vs LISZ?

No. Trading on both the UK LIS (LISX) and NL LIS (LISZ) for EU symbols will only be supported using the higher LIS ‘lis_local’ value in the DXE Reference Data file. IOIs (Indications of Interest) sent with lower values will be rejected.

  • The CXE Reference Data file contains LIS ‘lis_local’ values which will be lower for trading EU symbols as these values have now been sourced from FCA FITRS
  • The DXE Reference Data file contains LIS ‘lis_local’ values which will be higher for trading EU symbols as these values remain sourced from ESMA FITRS
Back to top

Approved Publication Arrangement (APA) and Systematic Internaliser (SI) quoting services

Have Cboe launched the NL based APA and SI quoting services?

Yes. The NL based services launched on Monday 2nd September 2019.

Has Cboe’s previously announced technical implementation for controlling which APA a firm trade reports to changed?

No. As previously announced, the venue (UK or NL) associated with the bank code used for trade reporting into the Cboe APA is used to denote whether the trade report is targeting the UK or NL APA. Depending on the post Brexit plans of each firm using the APA, firms may need to request new bank codes (associated with the appropriate APA) and then populate the relevant bank code in the PartyID (FIX tag 448) field of the Trade Capture Report message on FIX and BOE interfaces.

On Multicast and TCP PITCH the Cboe Trade Flags field in the “Trade Message — Extended Form” and “Trade Message — Unknown Symbol” messages types is used to convey the Cboe Regulated Entity to which the trade was reported. As such, the Cboe Trade Flags field supports the following values:

Regulated Entity Description
UK EU
‘-‘ ‘4‘ The trade was reported to Cboe on time and in the Main Session
‘1‘ ‘5‘ The trade was reported to Cboe ‘late’
‘2‘ ‘6‘ The trade was reported to Cboe out of the Main Session
‘3‘ ‘7‘ The trade was reported to Cboe late and out of the Main Session

Can I test my firm’s current and/or future Brexit APA and SI implementation in UAT?

The APA UAT (Certification) environment can be set up for either scenario by Cboe Trade Desk based on the bank code’s venue configuration described above.

What do I need to do to ensure my entity is reporting to the correct APA?

You should previously have informed Cboe of whether your firm would like to report through the UK or NL APA. If your plans have changed since you informed Cboe of the APA that you wished to use, you will need to inform us of your revised plans. Any new on-boarding firms will be required to specify which APA they wish to report through.

Back to top

ROIE

My firm is UK domiciled and regulated by the FCA, can we trade on EU domiciled venues, such as Cboe NL?

Yes, Cboe NL (Cboe Europe B.V.) is on the FCA register as a UK Recognised Overseas Investment Exchange (ROIE) which permits UK domiciled, FCA regulated firms to trade on our Dutch venue. https://register.fca.org.uk/s/search?predefined=ROIE

Does ROIE status apply only to the securities that are listed on your Regulated Market? Can you confirm that we can access the full services of Cboe NL on all securities?

UK firms will be able to enjoy access to all services and trade all instruments under ROIE status. There is some misplaced confusion relating to legal entity, or Operator of a market where the ROIE status is applied, versus the operation of markets (MTFs and RMs). The venue Operator Cboe Europe B.V. is approved as an ROIE so all of its services and markets are available to UK domiciled, FCA regulated firms.

Back to top

RTS24 Identifier Management and Order Record Keeping

Why are there changes being made to the MiFID II Identifier Management Application?

As per the previous notice, prior to the Brexit transition period ending, UK nationals were required to use a National Insurance Number (first priority) or CONCAT (second priority) as a long code to identify natural persons on both the UK and NL equities venues. Given the late nature of this change, we have confirmed with the AFM that, whilst we expect Participants to do all reasonable efforts to comply from day 1, if they are not able to they will be permitted to continue to use national insurance numbers for UK nationals for a limited period of time as from 4th January 2021. Currently, it is not possible for Participants to use the same short codes for a given natural person on each venue, as each short code can only be mapped to a single long code, though this changes from 16th April 2021 in Production and 22nd March 2021 in Certification through this change.

What are valid long codes for a UK national natural person on each Cboe venue?

Until now, natural persons from the UK have been identified by means of their National Insurance Number (first priority) or by "CONCAT" (second priority). As from 4th January 2021 UK nationals should be identified in accordance with the following format:

Venue 1st Priority 2nd Priority
Cboe UK (BXE, CXE) UK National Insurance number CONCAT
Cboe NL (DXE) Passport number CONCAT

Are there any scenarios where long code registrations will be rejected where they won't have been before?

Yes.

  1. Files over 3MB will be be rejected. Participants that use files that exceed this size will need to split their uploads into more than one file.
  2. Full validation rules are listed in Section 2.3 - Validation Messages of the Cboe Europe MiFID II Identifier Management Application Spec. Validation errors will result in an error message in the Message column described below and can result in either:
    • the row not being processed correctly, in which case there will be ‘N’ in the Processed column
    • or a warning associated with the uploaded long code that does not prevent it from being processed, in which case there will be ‘Y’ in the Processed column.

When will the changes be made in CERT and PROD?

Date CERT or PROD Functionality Action Required Additional Notes
Monday 22 March 2021 CERT

New Identifier Management app and API endpoints available per UK and NL venue.

The new Identifier Management web app replaces the existing web app within the Cboe Participant Portal

Participants should ensure their processes switch to maintain identifiers through the new Identifier Management app and API endpoints. Participants should stop using the existing API endpoints to prevent data being overwritten.

Participants should test their registration uploads meet the newly introduced validation rules prior to the upcoming Production release

Cboe Participant Portal users with the ‘MiFID II Short Code Registration’ privilege will automatically be given access to the new Identifier Management app and API. If you require access to the tool you should contact your firm's Account Admin who will provide this.
Friday 16 April 2021 PROD

New Identifier Management app and API endpoints available per UK and NL venue.

The new Identifier Management web app replaces the existing web app within the Cboe Participant Portal

Participants should ensure their processes switch to maintain identifiers through the new Identifier Management app and API endpoints. Participants should stop using the existing API endpoints to prevent data being overwritten.

Participants should test their registration uploads meet the newly introduced validation rules prior to the upcoming Production release

Cboe Participant Portal users with the ‘MiFID II Short Code Registration’ privilege will automatically be given access to the new Identifier Management app and API. If you require access to the tool you should contact your firm's Account Admin who will provide this.
Monday 03 May 2021 CERT Existing Identifier Management API endpoints are sunset. Participants should ensure their processes switch to maintain identifiers through the new API endpoints. Participants will no longer be able to use the existing Identifier Management API endpoints.
Friday 07 May 2021 PROD Existing Identifier Management API endpoints are sunset. Participants should ensure their processes switch to maintain identifiers through the new API endpoints. Participants will no longer be able to use the existing Identifier Management API endpoints.

I only trade on one venue, does this change impact me?

Yes. This impacts all users of the Identifier Management Application via web GUI or the API. In addition to the changes made to the web GUI and API endpoints, Cboe will also introduce validations at registration time as described above.

Can I still submit corrections after the changes go live?

Yes. Corrections can still be submitted after the web GUI and API endpoint changes are introduced. However, participants should ensure they are aware of the validation rules for the supplied long codes.

Can I use the same identifier mappings across both venues, i.e. the same file?

Yes. Effective 16th April 2021 in Production and 22nd March 2021 in Certification, participants will be able to register the same short code to long code mappings per venue, provided the files meet the required validation rules of each venue at the point of registration as described above.

Once the new per venue API endpoints are live can I still use the existing endpoints?

Yes. The existing endpoints will be available until 7th May 2021 in Production and 3rd May 2021 in Certification, at which point they will be sunset. Participants should note, it is not advisable to upload identifiers to both the existing and new API endpoints as this risks the per venue data registration being overwritten.

Once the new web GUI is live is it possible to use the old one?

No. The new web GUI will replace the existing application. Participants who use the web GUI only to register Identifiers should utilise the Certification environment to ensure they are prepared for the changes.

Will I need a new Participant Portal privilege to access the new web GUI or API endpoints?

No. Participants with existing user privileges and API keys will be able to access the new web GUI URLs and API endpoints. If you require access to the tool you should contact your firm's Account Admin who will provide the 'MiFID II Short Code Registration' privilege.

Will any network changes be required to access the new web GUI or API endpoints?

No. If you are still accessing the web GUI and API endpoints from the same source there are no network changes required.

Back to top