Tag: RTS 22

  • FCA publish Market Watch 59

    FCA publish Market Watch 59

    Market Watch 59 is ‘almost totally dominated by Transaction Reporting Observations’ and marks yet another strongly worded message from the Financial Conduct Authority on the importance of complete and accurate transaction reporting and how it is critical to the FCA’s work to ensure that markets function well.

    As ever, the FCA stress the importance of adequate systems and controls over transaction reporting and highlights how these requirements are clearly defined in Article 15 of RTS22. In particular, the FCA stresses the importance of reconciliation of front office trading records against data samples from the NCA. It also notes that some market participants don’t appear to be aware of the FCA’s facility to provide this data and the need for regular and thorough reconciliation.

    Valid but incorrect reports

    One of the more important messages from the FCA’s Market Watch is that:

    “Firms should not assume that a report was accurate because it was accepted by the Market Data Processor, as business validation rules are not intended to identify all errors and omissions”

    As we already know at Kaizen, there are too many ‘valid but incorrect’ transaction reports. In amongst the errors highlighted by the FCA are a number of old favourites, including the transposing of the buyer and sell:

    • Incorrect time (especially after the transition to British Summer Time!!!)
    • Price not reported in the major currency
    • Venue populated with the operating MIC where a segment level MIC is available
    • Misreporting the buyer as the seller and vice versa (oh come on!)
    • Re-use of identifiers for multiple clients
    • Incorrect client type code
    • Inconsistency between trading capacity and buyer/seller IDs

    Instrument Reference Data

    There is slightly conciliatory tone on the rejections where the instrument ID, or underlying instrument ID, is not present on FIRDS. Whilst the FCA is still keen to point out this is sometimes the firms’ fault, using the wrong Venue code for example, quite often it results from incorrect reference data submitted by the trading venues. The FCA is clearly sending a message to the trading venues and systematic internaliser that greater control is required over their RTS23 reference data submissions.

    Errors and omissions notifications forms

     The FCA’s observations end on a particularly worrying note for many firms. It reminds firms that where errors or omissions are identified in transaction reports, participants must submit a corrected report to the NCA. Alas, the FCA has noted that some firms are submitting an errors and omissions form, but not subsequently correcting the errors or correcting errors without submitting an errors and omissions form. The FCA does not appear to be happy about this!

    How Kaizen can help

    This is exactly what we here at Kaizen exist to do.  We have a proven track record in helping firms tackle their trade and transaction reporting issues and risks head on – and helping them to avoid censure whether it is for RTS23, MiFIR, EMIR, Dodd-Frank or another G20 regulation. Please contact us for a discussion with one of our regulatory experts to find out more.

  • MiFID II reporting: what we’re seeing six months in

    MiFID II reporting: what we’re seeing six months in

    Six months in, MiFID II is still leaving practitioners and regulators alike scratching their heads with a number of seemingly intractable problems. The reporting of derivatives in particular is causing difficulty as firms continue to struggle with reporting eligibility concerns, the misreporting of certain fields and validation issues. Firms have sometimes been unable to get a copy of what they reported to their regulator or approved reporting mechanism (ARM). Taken together, this reduces the efficacy of transaction reporting, says our managing director Ian Rennie.

    Reporting eligibility

    The trials of applying the concept of “traded on a trading venue” (TOTV) are well documented. Although ESMA’s opinion (issued on 17 May 2017) sought to establish a clear meaning of TOTV, concerns persist. There are still teething problems with the infant Derivatives Service Bureau (DSB) service particularly with the interaction of the DSB’s instrument normalisation and the reporting requirements.

    Aside from TOTV there are problems with applying the reportability criteria to transactions involving indices. Identifying accurately which indices contain MiFID instruments is problematic. One obvious example is Boeing which is dual listed as LON: BOE and NYSE: BA. There is, however, no regulatory requirement on index providers to make public the constituents of any index, which are dynamic in nature; moving in and out on a regular basis.  As a result, smaller firms may find it prohibitive to source the appropriate and relevant data to identify reportable index derivatives.

    Incorrect fields being reported and risk of detection

    There have also been instances of inaccurate or superfluous fields being reported. The commodity indicator flag is being populated on non-commodity instruments. Similarly, instrument fields are being populated unnecessarily when the transaction in question is reported with a valid Financial Instruments Reference Data System (FIRDs) International Securities Identification Number (ISIN). Volatile attributes were a late addition to the reporting obligations and overall the industry is still looking to implement this change.

    The UK Financial Conduct Authority (FCA)’s investment in its Market Data Processor (MDP) platform has been significant and gives the regulator a greater capacity to detect circumstances where two parties to a transaction have reported divergent values for the same transaction. This is particularly the case in instances where transactions are traded on a venue and now, as mandated, firms must persist the trading venue ID for the transaction. The FCA can use that ID to pair transactions and then match fields to highlight any discrepancies, which it can then automatically fire out to both firms.

    Obtaining data from competent authorities and ARMs

    Regulatory Technical Standard 22, Article 15, obliges firms to reconcile and test between their internal systems and data provided by competent authorities. Failing the provision of the data by the relevant national competent authority (NCA), firms should use data from their ARM or, as a last resort, use the transaction reports submitted by the firm to their NCA.

    The FCA appears to be a frontrunner, through its MDP system, in providing data back to the firms it regulates. Commitment by other NCAs to provide back to firms their data is not clear and should be closely monitored. That said, the current FCA extract service is not fit-for-purpose; even where firms obtain FCA data through the MDP portal they are unable to reconcile back safely to their own source systems.

    As mentioned above, RTS 22, article 15 points firms to obtain data extracts from their ARMs if not available from the competent authorities. Approved reporting mechanisms have had teething problems as well in their ability to provide data back to firms. In some instances, firms have been limited by the number of transactions they can obtain and there have been problems with the methods available for the data transfer. All ARMs have made significant progress in the area, which is most welcome.

    Efficacy of reporting and communication from the NCAs

    The primary objective of MiFID II reporting is to aid NCAs in the detection of market abuse. Any issues that prevent the correct application of the reporting criteria, reporting inaccuracies or unneeded fields or roadblocks facing firms’ efforts to conduct assurance activities, therefore, will reduce the efficacy of the reporting regime, as will inappropriate requirements.

    One simple example that illustrates this is the reporting of pricing of equity swaps when compared with contracts for difference (CFDs). For equity swaps ESMA’s guidelines require the financing charge to be reported — a piece of information that appears wholly irrelevant to market abuse — while for CFDs, which are economically the same instrument, the price of the underlying is reported.

    In summary, both firms and the regulator still need to do plenty of work to get MiFID II reporting into shape. This is likely to be a long and difficult road.

    Our ReportShield™ quality assurance service gives financial firms peace of mind in the accuracy, completeness and overall quality of MiFID II reporting data. If you would like an assessment of the quality of your MiFID reporting six months in, please contact us.

    A variation of this article was published by Thomson Reuters Accelus, a subscription-only site, on 12 July 2018.

  • Listen: Ian Rennie speaks on MiFID II and Senior Managers Regime

    Listen: Ian Rennie speaks on MiFID II and Senior Managers Regime

    Ian Rennie spoke at City & Financial’s Implementation of the Extension of The Senior Managers and Certification Regime conference. He spoke about the new Senior Managers Regime (SMR) requirements under MiFID II, where that fits into the regulatory landscape and the steps that can be taken to be compliant with MiFID II and SMR. 

    Have a listen below.

     

     

  • The good, the bad and the new: Final MiFID II transaction reporting guidelines

    The good, the bad and the new: Final MiFID II transaction reporting guidelines

    It was a big day in the world of regulatory reporting on Monday (10 October) with the publication of what is expected to be the final version of ESMA Guidelines for MiFID II transaction reporting.

    These guidelines are very important because they establish an obligation on financial market participants who “shall make every effort to comply with those guidelines and recommendations.”[ref]Article 16(3)of Regulation (EU) no 1095/2010 of the European Parliament and of the Council[/ref] Failure to comply with the guidelines will be considered a breach of the transaction reporting requirements.

    The guidelines are extensive so we’ve carried out an initial review of the 280-odd pages and a quick comparison to the previous version focusing on the transaction reporting requirements.

    Our take? Well, the good news is that ESMA has answered a lot of questions. The not-so-good news is that many questions still remain unanswered.  The bad news is that the guidelines have thrown up some new questions.

    Here are our immediate observations (there will be more to come once we’ve had more time to plough through and analyse all the changes).

    Identifying natural persons

    There have been some changes to identifiers for individuals which we think will be welcomed by the industry:

    1. Person identifiers: no longer requires firms to monitor for the expiry of identification documents such as passports.
    2. Clarification of how to determine nationality of individuals with multiple non EEA nationalities is by the first country code when sorted alphabetically.
    3. Introduction of an exhaustive list of name prefixes where these are to be removed when constructing the CONCAT identifier.
    4. Name and surname fields are now to allow the original country spelling so transliteration is not required for these fields.

    Who is the decision maker?

    This is the key question that competent authorities need to answer when undertaking surveillance for market abuse. As such, this is key information in the transaction report and ESMA has provided further clarifications and examples in the scenarios for the various decision maker fields including reporting chains which will prove very useful when mapping out the reporting logic.

    Reporting trades against fund managers has been clarified

    ESMA clarifies that they are looking for the decision maker. Therefore, where there is a transaction on the instruction of the fund manager, the fund manager will be the buyer and the decision maker field is left blank as it is one and the same party.

    Where execution is determined outside of the reporting firm then the “execution within firm” field should be populated with “CLIENT”. Similarly, where executions are filled by an order management system then this should be identified with an Algo identifier.

    Venue identifier

    The original guidance and RTS 22 indicated that all trading that was not directly on venue activity would be reported as XOFF. Unfortunately, the latest guidance suggests a move back to the MiFID I approach where the venue MIC code must be used when a trade is executed under the rules of a venue.

    “The buying and selling interest of two parties is not brought together by the Trading Venue either on a discretionary or non-discretionary basis, but the transaction is nonetheless subject to the rules of that Trading Venue and is executed in compliance with those rules.”

    ESMA confusingly goes on to say,

    “Where an Investment Firm is not the direct market facing entity the Investment Firm is not regarded as executing on the Trading Venue for the purposes of transaction reporting.”

    This seems to contradict the prior statement. The examples provided, however, do make clear that where the parties to a transaction agree that it is executed under the rules of an exchange or trading venue then the venue field should be populated with the MIC code of that exchange or trading venue.

    Short-selling flag

    Only real change here is that aggregated client orders do not require a short-selling flag to be populated as it relates to multiple clients. Transaction reports that show individual client-side activity will need to be populated based on the each client’s overall position in the traded security.

    ESMA has also clarified in the examples that the short-selling flag is only required for uncovered short sales of shares and sovereign debt instruments per articles 12, 13 and 17 of the short selling regulations.

    Cancellation of transaction reports

    ESMA has clarified that only the “key” fields 1, 2, 4 and 6 are to be submitted in the cancellation report. Inclusion of additional field information will result in a rejection of the cancellation report.

    Identification of the underlying instrument

    Surprisingly, ESMA has asked that where there is a derivative on a derivative (an option on a future on an equity, for example) the direct underlying should be identified i.e. the future rather than the equity.

    This raises the question of reportability. Are they suggesting that underlying refers to only one level down and when assessing reportability, there is no longer a look through to the ultimate underlying? For example, an option on an ADR on BT shares would not be reportable because the look through only goes down one level to the ADR? While when assessing the ADR you would look through one level to find BT shares and conclude the ADR itself is reportable? In the case where the immediate underlying is a future on a third country exchange that doesn’t use ISIN to identify its products means that the underlier field cannot be populated again – does this suggest that ESMA now considers such instruments as not reportable?

    Equity swaps and instruments reported with two separate transactions reports

    There has been an amendment to the approach ESMA wants to see for instruments which have multiple legs such as equity swaps. ESMA has compressed the two legs of an equity swap into a single transaction report using + and – to flag the buyer and seller of the legs. Previously in the consultation paper ESMA expected two transaction reports which were to be linked using the complex trade ID field.

    Similarly, for equity swaps the ISIN code for each equity leg is included in underlying instrument field with a + for the buyer (receives the performance) and – for the seller (on the equity leg that where they pay the performance).

    Similarly, where a benchmark is exchanged for equity performance the benchmark is identified in the “Underlying index name” field with a + or -.

    Other things of note:

    • Transfers are further defined in the text.
    • Changes in ownership structure are reportable.
    • Units of funds are not financial instruments and therefore not reportable.
    • Transactions for the creation and redemption of funds are only excluded where they are directly with the fund administrator. This was in the prior version of the guidance but it is now much clearer.
    • Identifying buyer or seller for trusts has been amended to be consistent with the approach taken for firms.

    What’s not addressed
    Outsourcing – do you need to be an ARM?

    There is an open question being debated by lots of different interested parties. The suggestion by ESMA had been that where a firm uses a central reporting hub to generate the transaction reports for all the reporting entities in its group that firm would have to register as an Approved Reporting Mechanism or ARM. Similarly, parties that stood between the reporting firm and the ARM providing reporting services would also be required to become an ARM.

    The guidelines clarify that

    “No requirement for a receiving firm to become an ARM. There was request for confirmation that a receiving firm reporting details transmitted by a transmitting firm did not need to become an ARM. ESMA confirms that that is not an outsourcing arrangement as the receiving firm is making its own report and it is not required to become an ARM. A statement on this has been included in the relevant section of the Guidelines.”

    From this it does imply that any form of outsourcing type arrangement involving your transaction reporting activity may require the supplier of the service seeks ARM status. This is not black and white and my suspicion is that this issue is still under discussion behind the closed doors at ESMA. What they have been able to do is rule out a scenario for receiving firms in the reporting chain to be ARMs.

    My view is that extension of the ARM regime beyond entities seeking to submit transaction reports directly to a competent authority on behalf of third parties will be unworkable.

    To conclude

    The above is by no means an exhaustive list – as always, the devil will be in the detail. Firms should be looking to see if their request for additional scenarios (as requested in the consultation paper) has been appropriately addressed.

    Do share with us here at Kaizen your initial reaction to the guidelines and anything further you’ve discovered so far. As mentioned, we will post a more thorough analysis once we’ve had more time to digest.

    Happy reading!

  • FCA provides timeline for MiFID II testing services

    FCA provides timeline for MiFID II testing services

    The FCA has published details of how interested parties can register to connect to their MiFID II data submission service and has also announced that they will provide testing facilities six months ahead of MiFID II go-live.

    The Market Data Processor (MDP) service replaces the current transaction reporting system Zen and will be operated and supported by a third party, Sopra Steria. The MDP also provides the mechanism for other Data Reporting Service Providers (ARMs, APAs and CTPs), trading venues and systematic internalisers to submit the instrument reference data required under RTS 23 and trade data required by ESMA to calculate the double volume cap as per RTS 3.

    Some parties such as our partner UnaVista are developing services to support MiFID II including an instrument static submission service so parties won’t have to register and pay the connection and annual fees to use the MDP service directly. In addition to a substantial cost saving, it has the benefit of validating the data before submitting it to the FCA.

    The MDP service specifications will be available to registering parties from the end of September and from Q4 for commodity position reports. A test environment will be available from 1 July 2017 allowing connecting entities and those further down the chain a good deal of time to undertake comprehensive testing prior to the MiFID II go-live date of 3 January 2018.

    Sopra Steria will also be managing the data extract service. This is the mechanism by which samples of submitted transaction reports can obtained for testing the veracity and completeness of the submissions. This process is expected to be conducted by all reporting firms as part the controls required to comply with RTS 22 Article 15 paragraph 3.

    Useful link: MiFID II Regulatory Technical Standards.

  • Collateral transfers are to be explicitly excluded from MiFID II transaction reporting

    Collateral transfers are to be explicitly excluded from MiFID II transaction reporting

    ESMA has published a final report on RTS 22 which seeks to amend the original drafting to explicitly exclude collateral transfers.

    The potential introduction of collateral transfers as reportable transactions was of significant concern to the industry so this development will be warmly welcomed.

  • ESMA gets in just before Santa to consult on clocks, data, records and reporting under MIFID II

    ESMA gets in just before Santa to consult on clocks, data, records and reporting under MIFID II

    ESMA’s consultation paper on some MIFIR/MIFID II guidelines were delivered, as promised, before Rudolph had his harness fitted. Well… just about.

    Those still at their desks on 23 December were left scratching the heads on whether they had been naughty or nice as they began to pore over 269 pages of guidelines on transaction reporting, reference data, order keeping and clock synchronization. 

    You may be relieved to hear that we will not be going through all 269 pages in detail in this blog (and there’ll be no more Santa related puns). Instead we look to set this document in context, explore its usefulness, its purpose, and briefly summarise the structure and content.

    Context

    The publication of the consultation paper continues the exercise of adding further granularity to the obligations required under MIFID II/MIFIR and then built upon under ESMA Regulatory Technical Standards (RTS) 22, 23, 24 and 25.  On page 7 of the consultation paper ESMA explains that:

    “…this guidance complements the technical standards and will be essential for the consistent implementation of the new MiFIR rules.”

    Are they useful?

    Considering the already published details under the directive, regulation, and RTS, it is valid to ask whether further granularity and detail is required. It’s worth considering the guidance provided by ESMA to market participants who have to meet EMIR reporting obligations. Under EMIR, guidance was provided in a piecemeal ad-hoc fashion. Guidelines were not drafted and published for consultation, clarifications were instead conveyed via a ‘Question and Answers’ document. For those who have Dodd Frank Reporting (DFA) obligations (under Chapter 17 part 43, 45 and 46) no further guidance other than the regulation was provided. So seen in this light – having well thought out, structured, and consulted upon guidelines should give firms a greater chance of delivering increased quality and consistency of reporting.

    Regulators’ expectations

    The regulators who drafted this consultation document have the experience of reporting under MIFID and as a result, the standards of the RTS and now these guidelines are more informed, detailed, and consistent than compared to EMIR.  Therefore there will be a greater expectation that the quality of MiFIR reporting will be high from the beginning. To increase the likelihood of the guidelines being successful ESMA will consider all comments received by 23 March 2016. Having guidelines that have been written by regulators with previous experience and consulted upon with market participants – combined with a potential year’s delay to MIFID II – gives the best chance of correct reporting than any of the recently introduced reporting obligations such as EMIR and DFA.

    Structure and content

    The guidelines’ length of 269 pages may make it feel impenetrable and inaccessible but on close inspection this is not the case. While there are four issues covered in this document – transaction reporting, reference data, order record keeping and clock synchronization – here we just review the transaction reporting section, which takes up 193 of the 264 pages and is made up of four parts.

    • Part I: General Principles
      Includes guidance on the how, what, when, where to send reports and exclusions.
    • Part II: Blocks (not to be confused with block trades!)
      A block is a collection of fields, which relate to a particular topic and there are 12 blocks in total. For example, block 1 deals with buyer/seller identification, block 4 deals with execution time within the firm and block 10 branches.
    • Part III: Scenarios
      Outlines different trading scenarios that a reporting party may encounter. For example, transmissions of orders, grouped orders, provision of direct electronic access.
    • Part IV: Instruments
      Offers clarity on what instrument data is required to be populated on reports. Focusing primarily on derivatives, this section prescribes when an ISIN is applicable versus when characteristics of the instrument are required.

    In each of the four sections ESMA attempts to provide clear notes on guidance backed up by an example and then an outline of what is expected to be included in the report. It is worth noting that two thirds of the nearly 200 pages on transaction reporting are made up of examples of how the report should be reported.

    Welcome step, but…

    The guidelines and the opportunity for the industry to provide feedback is a very welcome step. Taken together with the MiFID II/R RTS and the now likely year delay, the industry has the materials at its disposal for introducing high quality reporting on go-live. Though I do have a note of caution for firms: ESMA and the competent authorities’ expectations will be high and individuals under the senior managers regime (coming into effect in quarter 1 next year) will be held to account for any failings.

    Over the coming weeks and months we will explore in more detail the effects and implications of guidelines so keep an eye out and feel free to raise questions or comments either to me (dario.crispini@kaizenreporting.com)or via Linkedin or Twitter. Happy New Year from all of us at Kaizen!

  • Good and bad news for transaction reporting under RTS 22

    Good and bad news for transaction reporting under RTS 22

    Fewer reportable fields doesn’t necessarily mean less work.  In this blog, we look at the key changes in RTS 22 from the original  MIFID II consultation proposals and provide some conclusions on the overall impact.

    We carried out a detailed analysis of the reporting fields in the revised draft regulatory technical standards (RTS) released by ESMA.  RTS 22 is the section which sets out the transaction reporting obligations and reportable fields.  The analysis takes the fields in the original consultation paper and compares them to the equivalent versions of the fields in the final report.  In many cases this is a one to one mapping after accounting for some changes in the terminology used.  If you want to take a look or to use the table of fields for your own analysis we have published this as an excel document.

    So what did we find? Taken at face value the number of fields have been reduced from 81 to 65 fields.  A reduction of 16 fields, which is seemingly good news.  However this apparent reduction masks an increase in the information that reporting firms will have to capture and submit – not such good news.

    New fields: Our analysis shows there are 10 new fields which have been added.  The overall reduction in the number of fields results from 13 control fields (code type e.g. LEI vs national identifier) being removed.  We expect that seven of these will be included within the ISO 20022 reporting schema and therefore firms will have to continue to report them.  The remainder are no longer necessary for fields where only one code type is permitted for reporting which again will be enforced through the reporting schema.

    Fully removed fields: Nine fields in total were removed.  “Postcode” and “country of residence” fields have been removed for several identifier fields as has the “consideration” field and the “option exercise” field  is no longer a reportable activity.

    Compressed into another field: Three fields have been compressed into other existing fields, so in essence the information is still to be reported.  The three counterpart fields remain.

    Unchanged: A total of 52 fields remain unchanged in terms of field name.  There are some wording changes embedded which will need further analysis as these will have implications for reporting.

    You can also find our full analysis of the tables below which have the original data fields and revised data fields side by side so you can conduct your own analysis.

    [supsystic-tables id=’6′]

    The 10 new reporting fields:

    Providing these additional fields will in some cases be easy, such as field 5 stating whether you are a MiFID firm or not, whilst others will be very challenging, such as field 40 “complex trade ID” and “instrument full name”.  This latter field is likely to be supported by further guidance given it will be used to identify all derivatives which are not allocated an ISIN code.

    [supsystic-tables id=’5′]