Tag: Brexit

Discover all of Kaizen Reporting’s brexit resources. Learn more about global regulatory reporting from our team of specialists, covering FCA, ESMA and SEC.

  • REGISTER: Finance Magnates London Summit 2021

    REGISTER: Finance Magnates London Summit 2021

    We’re delighted to be taking part in the Finance Magnates London Summit 2021.

    Join Kaizen’s Ian Rennie for ‘Regulatory Catch Up: Understanding Changing Regimes‘ alongside a panel of experts to discuss the impact of Brexit on the way regulators monitor businesses in financial services. The speakers will lay out the most important revisions that brokers in the UK and the EU (and more often both) need to take into account.

     

    When: 17 November 2021
    Time: 12:30 – 13:10 GMT

     

    • Find out more and register here.
  • New iteration of the ESMA EMIR Q&A

    New iteration of the ESMA EMIR Q&A

    The latest EMIR Q&A contains two elements impacting trade reporting. Firstly, there’s clear advice on how to populate the buy/sell indicator in position level reports and then there is altogether more confusing text defining how to delete trades where a counterparty “ceases to exist”.

    Populating the buy/sell indicator at position level

    There is a small amendment in TR Q&A 3b which provides a clarification on the population of the buy/sell indicator on a position level report when the position is reduced to zero.  If a firm reported a ‘sell’ at a trade level which resulted in the position being reduced to zero, then the firm would populate the buy/sell indicator on the position level report with ‘S’ for sell. As this appears entirely logical, I hope that this doesn’t constitute a change for many firms.

    Procedure for terminating ‘dead trades’ by Trade Repositories (TRs)

    ESMA has included an entirely new question, TR Q&A 57, defining a procedure for the termination of ‘dead’ trades by TRs. Whilst this requirement is largely aimed at the TRs, there is some responsibility on firms as well.

    By ‘dead trades’, ESMA means trades that have been reported to a TR, but where one of the counterparties has subsequently “ceased to exist”. Unfortunately, the wording of this new question renders the procedure incomprehensible. It is not helped by an apparent requirement to submit reports with action types (sic) of “ETRM”, which doesn’t actually exist for EMIR. 

    FCA and the Q&A

    UK firms must be wondering how much longer the FCA will continue to support a Q&A that it no longer has the ability to influence. Obviously, it is a massive issue as there is strong pressure to minimise any divergence in the respective reporting regimes even if it only stems from the Q&A. Whilst there is a huge amount of valuable information in the Q&A, there is room for improvement. Anybody doubting this should look at TR Q&A 9 a little closer and see how elements of this actually contradict the RTS. As evidenced by the joint trade associations’ best practices, the industry has highlighted some areas of trade reporting where more clarification is required so that it can submit better quality reports.

    Problems following Brexit

    EMIR was already a very complex reporting regime, but the impact of Brexit has added to this complexity – particularly for those firms with dual-reporting obligations. Our ReportShield quality assurance testing takes into account the different nuances of reporting to an EU TR or to a UK TR (or both!). If the two regimes continue to diverge, Kaizen’s testing will continue to be updated in line with the latest guidance and we can also provide advice on ensuring your reporting has been updated for both EU and UK obligations.

  • WATCH: Kaizen CEO Dario Crispini on regulatory reporting in 2021

    WATCH: Kaizen CEO Dario Crispini on regulatory reporting in 2021

    Following Kaizen Reporting’s win for ‘Regulatory Reporting Solution of the Year’ at the FOW International Awards 2020, our CEO Dario Crispini talks to Luke Jeffs, Managing Editor of Global Investor Group on the upcoming regulatory reporting changes in 2021, what firms should be doing now that the UK has left the EU and the main trends in the RegTech space.

    The subsequent videos below are smaller snippets from the same video; broken up into bitesize videos if you don’t have time to watch the whole recording.

  • EMIR Q&A –UK derivatives to be considered OTC

    EMIR Q&A –UK derivatives to be considered OTC

    ESMA thoughtfully delivered a new Christmas edition of its EMIR Q&A on 21 December. It may not have been at the top of everyone’s Christmas list, but at least it hasn’t brought any unexpected pain. So, let’s unwrap it and see how it’s impacted EU EMIR trade reporting.

    UK trading venues confirmed as OTC

    As the UK has left the EU and its derivative markets haven’t been granted equivalency, it should be no surprise that any new derivative contracts traded on UK derivative markets will be considered OTC for EU EMIR reporting purposes. This will have the following implications for trade reporting to an EU trade repository:

    • ‘Venue’ (2.15) – for trades in UK derivatives concluded OTC, the code ‘XXXX’ shall be used (as opposed to ‘XOFF’)
    • ‘Clearing obligation’ (2.34) – this field will now need to be populated for trades executed on UK derivative markets
    • ‘Intragroup’ (2.38) – this field will now need to be populated for trades executed on UK derivative markets.

    This is exactly as we expected and consistent with previous post-Brexit transition communications.

    There is no change to current practices when reporting to UK trade repositories. The UK FCA has taken a pragmatic approach and doesn’t treat EEA derivatives as OTC for EMIR trade reporting purposes.

    What else is in the new Q&A for trade reporting?

    ESMA provides wording to clarify the reporting technique for derivatives executed on a third country venue and cleared on the same day. So long as certain criteria are met, the reporting scenario for third country ‘ETDs’ is the same as EEA ETDs.

    In practice, this is what the industry has already been doing – there is no real change.

    Changes to Kaizen testing post transition period

    Clearly, there are some changes to both the UK EMIR and EU EMIR reporting regimes after the Brexit transition period. Whether you are reporting to an EU trade repository, a UK trade repository or if you are unfortunate enough to have a dual reporting obligation, you can be rest assured that our quality assurance testing will continue to adapt to the changing regulatory requirements.

    • If you would like more information on this, or to speak to one of our specialists, please contact us. 
    • To read the new EMIR Q&A, visit the ESMA website.
     
  • Brexit and SFTR – Your questions answered

    Brexit and SFTR – Your questions answered

    We’ve had a great response to our Brexit webinar on EMIR and MiFIR, but it’s left some of our clients asking “what about SFTR?” We asked our Senior Regulatory Reporting Specialist for SFTR, Jonathan Lee, about what firms need to know.

    This Q&A looks specifically at the SFTR reporting obligations (as distinct from any other disclosure requirements) and the period following the end of the transition period from 1 January 2021. 

    What are the reporting differences?

    The key difference between EU SFTR and UK SFTR is that under UK SFTR, non-financial counterparties (NFCs) established in the UK will not be required to report under SFTR, either directly (if large in size) or via mandatory delegated reporting (if small or medium-sized).

    As a further point of clarification, if a financial counterparty established in the UK has traded with an NFC, then they will only be required to provide a single transaction report with the FC as reporting counterparty. In the EU, transactions executed by NFCs will be required to be reported from 11 January 2021.

    Which regimes do I need to report under?

    • Financial counterparties established in the UK will need to report under UK SFTR.
    • Financial and non-financial (from 11 January 2021) counterparties established in the EU will need to report under EU SFTR.
    • UK established firms trading through EU branches will need to submit reports under both UK SFTR and EU SFTR.
    • EU established firms trading through UK branches will need to report under both EU SFTR and UK SFTR.
    • Third country established firms trading through UK branches will need to report under UK SFTR.
    • Third country established firms trading through EU branches will need to report under EU SFTR.

    Which trade repository should I register with?

    • Financial counterparties established in the UK will need to sign up to a UK SFTR trade repository (TR) if they have not already done so.
    • Financial counterparties established in the EU or any third country, trading through UK branches will also need to sign up to a UK SFTR TR.

    What about reconciliations?

    Reconciliations going forward will only take place between intra-jurisdiction (EU vs EU or UK vs UK). Simply, you will only be subject to trade reconciliations when both parties have an obligation to report under that jurisdiction (whether UK or EU). This applies to both pairing and matching of transactions and lifecycle events.

    Anything else for firms to consider? UTI creation, sharing, pairing and matching…

    At present, the unique trade identifier (UTI) creator is determined by either bilateral agreement with the counterparty or a mechanism determined by the ESMA defined waterfall. In essence, this will not change, the issue is that it will only continue to formally apply across a single jurisdiction. Therefore, if you currently have a bilateral agreement to receive UTIs from an EU counterparty, while you will be required to report under UK SFTR, then they will no longer be bound to provide it, nor will it be subject to pairing and matching and vice versa. There is no reason why you cannot continue to supply and receive UTIs in the same way as pre-Brexit, but you may meet reluctance from some counterparties and without dialogue with your counterparties, it should not be assumed, if crossing jurisdictions.

    Since these cross jurisdictions become single-sided transaction reports, some dealers have expressed a desire to simplify processes by unilaterally assigning UTIs to cross jurisdictional transactions, thereby no longer offering UTI sharing and pairing for these reports.

     

    • For a conversation with Jonathan or one of our regulatory experts about reporting under SFTR after Brexit, please contact us.
  • How to report UK nationals if there is a no-deal Brexit

    How to report UK nationals if there is a no-deal Brexit

    We were hoping for a different outcome but unfortunately for firms reporting to EU National Competent Authorities (NCAs), the approach to reporting UK nationals will change if there is a no-deal Brexit.

    Happily there is no change for firms reporting to the FCA. 

    Wouter van Bronswijk who leads reporting at the AFM, the Dutch regulator, confirmed at a recent Infoline Trade and Transaction Reporting Conference that based on the regulations, the UK would become a third country. This means that firms reporting to EU NCAs will have to change the way in which:

    1. They prioritise the nationality to use for individuals who have more than one nationality of which the UK is one;
    2. They change the preferred identifier to use for UK nationals.

    Determining the nationality to report

    Where an individual has multiple nationalities there is a waterfall approach to determine what nationality to include in the transaction reports. This will apply to traders and clients that are natural persons. 

    The steps are:

    • Use the first EEA country based on the country code when sorted alphabetically
    • If there are no EEA nationalities then it is the first non-EEA nationality based on a sorted country code
    • If the UK is the nationality, then the passport number is the preferred identifier and if that does not exist the CONCAT should be used.

    All those UK National Insurance numbers that firms had been diligently collecting cannot be reported to EEA NCAs post-Brexit. 

  • FCA: The five key reporting challenges for firms preparing for Brexit

    FCA: The five key reporting challenges for firms preparing for Brexit

    The FCA has outlined what it sees as the key challenges for firms reporting to the FCA in respect of Brexit. 

    Speaking at the Infoline Trade and Transaction Reporting Conference last week, Ana Fernandes, who leads the Markets Reporting Team at the FCA, gave her views alongside Wouter van Bronswijk from the Netherlands’ AFM, Rob Knight (Chair) and myself. 

    It was great to get an opportunity to hear the thoughts of both EU and UK regulators as a possible no-deal Brexit lurks around the corner.

    Here is a summary of the key takeaways for firms reporting to the FCA.

    • Pre and post Brexit reporting consistency:  The FCA has been working to keep disruption to a minimum.  Hence there is broadly full consistency between pre and post Brexit reporting to the FCA. The regulator is in the process of drafting the Statutory Instrument text, which will be published next year. This will look to address some current deficiencies encountered since MiFID II go live and there will be a consultation undertaken with the industry on the proposals to seek their views. 
    • No Transitional relief: “Market Abuse does not go on holiday” so transaction reports are required from Day 1 post-Brexit.  There will be “no excuses”. The current transition period is operating up to 31 December. 

    • UK firms must use UK FIRDS: The scope of instruments within the regime is being maintained to include all of the EU FIRDS instruments but will also include UK-only instruments. Further, the UK version of an instrument will take precedence over any EU version instruments which may cause differences between the two data sets.

    • Loss of Article 4 Transmission: UK firms and EU firms transmitting to each other can no longer make use of the Article 4 transmission process as the UK will become a third country. Firms have to make sure they are connected to FCA FIRDs by the cutover date. UK FIRDS has been live and operational since March 2019 to support this.

    • Final point: Firms have to be ready on Day 1, there is no transitional period or holiday.  The FCA’s expectation is that all firms should be compliant.

    Many thanks to Richard Horsler and the team at Infoline for organising the conference.

    If you’d like guidance or advice on preparing for Brexit from one of our regulatory specialists, please contact us. 

  • Our response to the Chancellor’s statement on financial services after Brexit

    Our response to the Chancellor’s statement on financial services after Brexit

    The Chancellor of the Exchequer, Rishi Sunak, this week outlined in a statement that the UK will “exercise its discretion” when implementing EU regulations that will not have come into force by the time the Brexit transition period ends on 31 December.

    The statement says that the UK will not incorporate into law the fourth phase of reporting obligations of SFTR, which applies to Non-Financial Counterparties (NFCs) and is due to apply in the EU from January 2021.

    In response, our Senior Regulatory Reporting Specialist, Jonathan Lee, said: 

    “We welcome the Chancellor starting to provide some clarity on the rules which will govern the UK’s financial services sector following our departure from the EU.  Firms will welcome changes to regulation that will reduce the compliance burden whilst remaining equivalent to the ESMA regulations.

    “The Chancellor’s announcement indicates that the first sets of rules to diverge will be in the application of SFTR for non-financial counterparties (where only single-sided financial counterparty reporting will be required) and in the UK’s refusal to adopt buy-in rules under CSDR. This divergence might be an issue for multinational institutions operating in the UK and EU where they will increasingly need to manage two distinct sets of reporting rules and have systems, controls and personnel able to ensure ongoing compliance with both regimes.

    “However, there appears to be plenty of scope to additionally tailor the EMIR and MiFIR reporting regimes to the benefit of the UK firms without losing equivalence.” 

    (ends)

    Read our Brexit White Paper:  Warning: Brexit can damage your MiFIR Transaction Reporting and EMIR Trade Reporting. 

    Further reading:

     

     

     

  • Post-Brexit regulatory reporting wish list: EMIR trade reporting

    Post-Brexit regulatory reporting wish list: EMIR trade reporting

    We recently speculated that now might be a good time to think about what changes you might want to see in the UK reporting regimes at the end of the transition period. The UK Chancellor’s assertion that he is seeking “outcomes based” equivalence rather than complete alignment appears to have left the door ajar for some sensible changes to the reporting regimes.

    Previously I shared my top ten suggestions for changes to the MiFIR transaction reporting regime. Now it’s time for my top ten changes for EMIR trade reporting which I believe will make reporting more proportionate for firms without degrading regulator’s ability to use the data for the intended purposes. In fact, some of them may help increase the quality of the data for the regulators:

    1. Eliminating trade reporting for ETDs

    Since the main purpose of EMIR trade reporting is to monitor for systemic risk, there appears to be little value in collecting reports of ETD trades when they are immediately netted into an end of day position report. Additionally, key elements of EMIR trade reporting like lifecycle events and collateral reporting can only really be sensibly applied to the end of day positions for ETDs. Perhaps the only value of ETD trade reports is for the detection of market abuse – but this is the driver behind MiFIR transaction reporting and their inclusion in EMIR is an expensive duplication.

    1. Review some of the roles of the trade repositories (TRs)

    The trade repository ‘layer’ between firms and the FCA appears to be a potential hindrance for the regulator as it needs to access multiple databases which may have their own systems and fields. It would also help the production of useful public data aggregations from a single source and reduce problems in performing the pairing and matching reconciliations. Having multiple TRs appears to increase risks, so given that the regulators have the ability to act as the single repository themselves as the FCA has demonstrated with MiFIR transaction reporting, it should now be reviewed.

    The entities behind the TRs can still have an extremely important role to play, but this would be more akin to the role that ARMs have in helping firms report to the NCAs.

    1. ‘Beneficiary’

    “The party subject to the rights and obligations arising from the contract…” Is there a situation when this party is not going to be the reporting counterparty! OK, there is a small case where it could be argued that a sub-fund could be the beneficiary rather than the reporting fund counterparty, but does this really justify the confusion this seemingly superfluous field causes?

    1. Reporting Timestamp

    “Date and time of reporting to a trade repository”. This used to be populated by the trade repositories as it is the same as the time they receive it. Asking firms to report this field is duplication and leaves firms exposed to making errors.

    1. Trading Capacity

    For EMIR, we have ‘principal’ and ‘agent’ as possible values. However, we are told that only principals to a trade need to report; not any party acting as agent. This field has no value other than to cause confusion in interpretation and should be removed.

    1. Don’t ask for data you’ve already got

    It sounds obvious, but there’s no justification for regulators to ask firms for data that they already have. It creates the potential for firms to supply different data to the ‘golden source’ – do the regulators think it would be a good idea to use this sub-optimal data rather than the pristine data they have? For example, the regulators will already have reference data collected from EEA trading venues (even post-Brexit) for ‘product classification’, ‘underlying identification’, ‘notional currency 1’, notional currency 2’ ‘delivery type’, ‘price multiplier’ and ‘maturity date’ where the instruments is tradeable on an EEA trading venue. If the instrument is an OTC derivative and has an ISIN, a golden source of this data is also available on the ANNA DSB.

    1. Country of the other counterparty

    “The code of the country where the registered office of the other counterparty is located or country of residence in case that other party is a natural person” So, similar to the argument in point six, this information is contained in the GLEIF database for organisations. Asking firms to populate this field for organisations is again unnecessary (firms cannot deal with an organisation unless they have an LEI).

    If the counterparty is an individual, why ask for the country of residence? For a start, it is different from the equivalent field for MiFIR. Additionally, natural persons often have multiple residences and move around. It is difficult to understand how collecting the country of residence for natural person counterparties can be of any use for monitoring systemic risk.

    1. Basket derivatives

    Firms executing transactions in OTC basket derivatives have to populate the underlying ISIN field with all the ISINs that comprise that basket (similar to, but not the same as MiFIR). For example, if they trade a pharmaceutical basket comprising 421 stocks, they have to populate the ISINs of all 421 stocks. Since there is no information of the individual stock weightings, it is extremely difficult to see how any regulatory authority can use the data to help monitor systemic risk. This is very onerous for firms and can be of very little value to the regulators.

    1. Duplicate fields

    There are a number of required fields that can be derived from other fields. For example, the information provided in a CFI code (Classification of the financial instrument) renders the following mandatory fields obsolete:

    • Contract type
    • Asset class
    • Delivery type
    • Option type
    • Option exercise style
    1. Report tracking number (RTN)

    “A unique number for the group of reports which relate to the same execution of a derivative contract”. At Kaizen, we can find very little evidence of this field being populated for the scenarios described in the ESMA Q&A. Where it is mandatory, for the action type of ‘position component’ at a trade level, our findings show that there is a common failing to assign the same code to all the trades that comprise a particular position report. If the field is only mandatory for trades that are going to be netted into a position report, it is questionable whether this troublesome field offers any real value to the regulators.

     

    So these are my top ten and again I have to add the caveat that there may be perfectly valid reasons why the regulators need this information. However, there is a view in the industry that the EMIR trade reporting regime needs a fundamental review rather than simply tinkering round the edges. Nobody can deny the importance of a reporting regime to monitor for systemic risk, but the poor quality of much of the data reported and the lack of appetite amongst certain NCAs to address these deficiencies six years after go-live, suggests that the current reporting regime doesn’t achieve its objectives. 

    Check out the first blog in this series on MiFIR transaction reporting. Forthcoming blogs will detail our wish lists for SFTR reporting and Post-Trade Transparency reporting.

    For help with your EMIR trade reporting accuracy or to discuss your own post-Brexit EMIR trade reporting wish list with one of our regulatory specialists, please contact us.

  • Post-Brexit regulatory reporting wish list: MiFIR transaction reporting

    Post-Brexit regulatory reporting wish list: MiFIR transaction reporting

    Wouldn’t you know it; you spend over three years planning and worrying about a hard Brexit, and in the end, right at the last moment, after all the sleepless nights, it doesn’t actually happen! Instead, we now have a nice 11-month transition period. While there may be no changes to the MiFIR, EMIR and, SFTR reporting regimes until 2021, now is a good time to think about what changes you would like to see in the UK reporting regimes at the end of the transition period. While it was assumed that there might be little change in an attempt to assure equivalence, the UK Chancellor’s assertion that he is seeking “outcomes based” equivalence rather than complete alignment appears to have left the door ajar for some sensible changes to the reporting regimes. Starting with MiFIR, here are my top ten suggestions for changes to the transaction reporting regime which we believe will make reporting more proportionate for firms without degrading regulator’s ability to use the data for the intended purposes:

    1. “Country of Branch ” fields

    Perhaps one of the forgotten drivers behind MiFIR transaction reporting is the monitoring of conduct of business. There are five MiFIR “country of branch” fields which the NCAs use to share data amongst each other to help ensure that they can monitor branch activities. At Kaizen, we have discovered that firms frequently have issues populating these fields correctly. Since there will be no systematic sharing of data between the UK and the EEA, there appears to be no regulatory requirement to persist these fields.

    1. “ToTV Opinion Paper”

    ESMA has used this paper to expand the reportable instrument set to include “OTC derivatives sharing the same reference data details as the derivatives traded on a trading venue” Understanding the reportable instrument set has caused firms enough problems without adding to the burden. This is a considerable addition involving the matching of attributes against the ANNA DSB to find potential ISINs and then comparing the attributes associated with these ISINs against FIRDS to see if the instruments are reportable. I do not believe this is proportionate and it can be argued that it is not consistent with the Level 1 regulation. It has to go.

    1. Basket and Index Derivatives

    Firms executing transactions in OTC basket derivatives have to populate the underlying ISIN field with all the ISINs that are traded on an EEA trading venue. For example, if they trade a pharmaceutical basket comprising 421 stocks of which 352 are ToTV, they first need to discover which are ToTV and then populate all of them in the underlying ISIN field. If they make a mistake with any of those ISINs, it will be rejected by the regulator. This is very onerous for firms and can be of very little value to the regulators. There is no information on the weighting, so the information cannot possibly be used by the regulators on a systematic basis.

    Additionally, any changes in the basket composition are not reportable. It is also questionable whether the reporting of an index is of any real value to the regulators as it is doubtful whether they hold the constituent and weighting data. Of course, it is possible to manipulate the index markets (see Flaming Ferraris) but this is likely to stand out like a sore thumb to the participants and should be reported through a STOR. It is very difficult for firms to know whether the OTC index derivatives are reportable as it only takes one of the index constituents to be ToTV and this information is difficult to source – it certainly isn’t on FIRDS.

    1. IPOs

    Under MiFID, we used to say that everything that was knowable about an IPO was contained in the prospectus, so it would not be proportionate to require the resultant transactions to be reported. I’m not sure what’s changed to justify their inclusion for MiFIR. The task has been made more difficult as it is possible that some of the ‘counterparties’ don’t have LEIs as they are not necessarily normal market counterparties. Of course, trades cannot be reported if the counterparty doesn’t have an LEI. To make things worse, reporting firms have often discovered that the ISIN of the IPO is not on FIRDS at the time of the IPO. As some trading venues have not reported dates when an application for trading was made, some IPO trades have been continually rejected.

    1. Trading Capacity

    In the UK, we understand ‘principal’ and ‘agency’; but we don’t always understand the distinction between the new MiFIR values of ‘dealing on own account’ and ‘matched principal’. However, many firms, particularly the buy-side, have discovered that brokers confirming transactions back to them as ‘matched principal’, causes immense difficulties. Additionally, you can describe the same back-to-back principal scenario to a number of firms and I believe 70% of them will report it as two ‘DEAL’ transactions and 30% will report it as a single “MTCH” transaction. If it doesn’t matter which method is observed, why have the element of grey in the first place? Let’s get back to trading capacity we understand (and that are used in other reporting regimes).

    1. Crazy Chains – transmission of order, INTC and individual funds

    I love the Guidelines document, I really do. However, there are times when I’m reading sections 5.26 (Chains and Transmission) and 5.27 (Investment firm acting under a discretionary mandate for multiple clients) that I find it extremely difficult to carry on reading. There are a couple of inconsistencies within these Guidelines which suggests they may not work quite as the regulators envisage. It is just too convoluted and transaction reporting shouldn’t be this difficult. Again, I think it is the buy-side that may suffer most from this and maybe it is an area where the FCA may want to simplify the requirements. For example, are allocations to funds really required when the fund manager reports with the identifier of the individual decision maker within the fund management company? Does the transmission of order indicator actually add any value for the regulator?

    1. Repos & Securities financing indicator

    Exactly what is the logic for requiring a securities financing transaction, such as a repo, to be reportable under MiFIR simply because it has been excluded under SFTR? How was that leap made? If RTS 22, Article 2 sets the precedent that SFTs aren’t reportable under MiFIR (because they cannot be deemed to be abusive) why was it felt necessary to add the proviso that they should be reported if the counterparty is a member of the European System of Central Banks. Simplify the regulation and remove SFTs from MiFIR transaction reporting completely.   

    1. Swaps

    Completing the technical standards and Guidelines was clearly a mammoth task for ESMA and it is inevitable that there would be time constraints. I believe this is particularly evident when it comes to the reporting of swaps. For example, it is questionable whether requiring the price of an equity swap to reflect the interest rate is sensible, as the price of the underlying reference security would appear far more valuable to the regulators in pursuing market abuse. In fact, why require the interest rate side at all – it is not required for CFDs or spread bets, which are essentially swaps anyway. As for the “swap-in” and “swap-out” indicator – does this really bring any value when rules for determining the ‘buyer’ and ‘seller’ are already set out in the regulatory text?

    1. Reference Data Requirements

    Where a reported instrument is not ToTV and is only being reported because the underlying instrument is ToTV, up to 15 additional reference data fields need to be populated to describe the instrument to the regulator. This has proved to be particularly difficult for firms. A lot of these fields are essential for the regulator to detect market abuse – the underlying instrument ISIN is a prime example. However, it is questionable whether some of the others deliver any value. For example, does the ‘instrument full name’ add value when all the details are contained in other fields. Are some of the fields duplicated in the CFI code (e.g. ‘option type’). Does ‘notional currency’ have any relevance for non-FX derivatives?

    1. Short Sell indicator

    This is very onerous for firms to populate correctly and maybe the cost benefit analysis of this field should be reviewed. If there is a permissible value for ‘information not available’ (for clients after acting on a ‘best efforts’ basis) then you have to assume that the overall quality of this information is questionable.

     

    These are my ‘just for fun’ top ten as there may be perfectly valid reasons why the regulators need this information. To be honest, they’re my initial thoughts and I haven’t even mentioned other contenders such as ‘net amount’, ‘waiver indicator’ and ‘OTC post trade indicator’.

    However, there is a serious element here. If there is an opportunity for the UK FCA to tweak its reporting regimes on the basis of ‘outcomes-based equivalence’ rather than alignment, the process needs to start immediately and firms need to feed into that process. Eleven months is not a long time.

    Forthcoming blogs will detail our wish lists for the EMIR trade reporting and SFTR regimes.

    For help with your transaction reporting accuracy or to discuss your own post-Brexit transaction reporting wish list with one of our regulatory specialists, please contact us.

  • Video: Dario Crispini’s regulatory reporting predictions for 2020

    Video: Dario Crispini’s regulatory reporting predictions for 2020

    • Will data quality continue to be the theme for regulatory reporting in 2020? 
    • What are the big regulatory reporting regimes coming up?
    • What issues should firms be looking out for?
    • Will we see penalties for MiFID or EMIR reporting?
    • What are the key challenges for the RegTech industry in 2020?
    • And what on earth is ‘BRiFID’?

    The answers to these questions and more in this and more in the above video from our CEO Dario Crispini.

    With thanks to the Wealth Mosaic for collaborating with us on this video. 

  • The scariest regulatory reporting changes facing you this Halloween

    The scariest regulatory reporting changes facing you this Halloween

    It’s Halloween! And what better time to cover off some of the scariest regulatory reporting changes that you need to keep very very close to, following the full-moon…

    Quoting Macbeth’s three witches, “By the pricking of my thumbs, something wicked this way comes”, here are three key regulations affecting everyone in the coming months:

    In Thunder comes Brexit

    31 October was always going to be a horror Halloween show but the EU have prolonged the agony for another three months to 31 January. The good news is that most firms have prepared for the October exit but do keep an eye on any unknown regulatory changes in the coming months – or read our Brexit White Paper to help with your preparations.  

    In Lightning comes SMCR

    Ghosting quietly in, don’t forget if you’re an Core or Enhanced Firm, as categorised by the FCA, your CF Approved Persons change to SMFs under the Senior Managers and Certification Regime (SMCR) on 9 December. Encouraging a culture of taking responsibility for actions and demonstrating a clear understanding of where that responsibility lies, are the key messages. You can’t use a magic wand to sign-off on the accuracy of your regulatory reporting, a key task for your SMFs.

    In Rain comes SFTR

    As we speak on the day of the devil, SFTR is only 166 days away.  This is frighteningly close.  Are you prepared and testing in UAT for this new reporting regime coming into effect on 14 April 2020? Contacting our very own SFTR expert Jonathan Lee is much less scary than a letter from the regulator.

    When the hurly-burly’s done, when the battle’s lost and won, Kaizen is here to help with the most scary of regulatory reporting challenges. Please contact us if you’re worried about any of the above and we can turn your regulatory reporting obligations from a trick to a treat!

    Author: Chris Machinbeth

  • Brexit – FCA Statement on EMIR Trade Reporting

    Brexit – FCA Statement on EMIR Trade Reporting

    The FCA has published a statement that will hopefully provide some comfort to firms worried about the impact a hard Brexit will have on their EMIR trade reporting – should there actually be a hard Brexit on 31 October. Although it stresses the need for accurate data, the FCA acknowledges that mid-week changes of this magnitude will be challenging and it promises to adopt a “proportionate and pragmatic” approach – particularly where firms have robust systems and the data reported is accurate. (If you’re not sure the data you have reported under EMIR is accurate, perhaps this is a good time to contact us for a quality assurance check.)

    FCA-registered Trade Repositories (TRs) are required to ensure the migration of all outstanding trades (and historic data) for UK counterparties, so, in theory, it should be a seamless process for firms to transfer reporting to an FCA registered TR. However, because it’s a mid-week change, the chances are that it won’t be an entirely seamless! The FCA has therefore made some sensible concessions to the T+1 reporting requirement and has stated:

    • We expect all UK reporting counterparties to have reported the details of all derivative transactions concluded, terminated and/or modified on 1, 2 and 3 November 2019 to an FCA registered TR by no later than 4 November 2019
    • UK reporting counterparties must also ensure that any details of their derivative transactions concluded, terminated or modified on 30 and 31 October 2019 that cannot be reported by the point of exit are back-reported to an FCA registered TR by no later than 4 November 2019.

    Counterparties within scope of ‘UK EMIR’

    The FCA has also stated that: “UK branches of third-country firms (including branches of firms from EU27 countries after Brexit) are not in scope of the UK EMIR reporting regime and so do not have to report under the onshored UK regime” Whilst this removes one element of potential branch level dual reporting, the FCA also states that branches of UK established firms outside the UK are within scope of the UK EMIR reporting regime.

    The reporting of new and outstanding trades under ‘UK EMIR’

    The FCA states that all new derivative trades entered into by UK counterparties on or after 11.00pm on exit day are in scope of the UK EMIR reporting regime and are required to be reported to an FCA-registered, or recognised, TR. In addition, all outstanding derivative trades entered into by UK counterparties on or after 16 August 2012, need to be held in an FCA-registered, or recognised, TR on exit day. So any firm believing that they no longer need to worry about the completeness and accuracy of their previous reporting are sadly mistaken. The UK authorities will have access to this data and they will expect it to be correct.

    Inter TR Reconciliation

    At least in the short term there will be no inter-TR reconciliation in the UK regime! However, the FCA recognises the role this reconciliation plays in ensuring the quality of the data and will reconsider this issue with UK TRs at a future date.

    Will this all work?

    Yes, but probably not perfectly. Of course, we are still unsure whether there will be a hard Brexit and, if there is one, whether it will be on 31 October 2019. So there are still plenty of ‘unknowns’.

    Of course there shouldn’t be any ‘unknowns’ about the quality of your EMIR trade reports. We expect the FCA to become far more intrusive in ensuring the quality of reports under UK EMIR. If you’re not sure your EMIR reports will meet this scrutiny, please contact us as this is why we here at Kaizen exist – our assurance services can tell you how good or bad your reporting is, identify your issues and get you quickly on a path to good quality reporting. 

    Read the statement on the FCA website.

    ***

    If you need more information about reporting after Brexit, please read David’s Brexit White Paper. 

  • The effects of Brexit on MiFID II post-trade transparency reporting

    The effects of Brexit on MiFID II post-trade transparency reporting

    “There are known knowns. These are things we know that we know. There are known unknowns. That is to say, there are things that we know we don’t know. But there are also unknown unknowns. There are things we don’t know we don’t know.” – Donald Rumsfeld (Feb, 2002).

    Brexit…the ‘known unknown’ of everyone’s lives (at least for those of us in the UK) and not just in financial services but across all sectors of life.

    MiFID II has not escaped Brexit either.  Let’s call it BRiFID!  My colleague David Nowell has covered in detail the effects of Brexit on EMIR trade reporting & MiFIR transaction reporting but in this blog, I want to delve into the effects on post-trade transparency reporting. 

    Kaizen announced at the beginning of December 2018 that we were to offer post-trade transparency reporting testing following on from our established MiFID II transaction reporting testing service. The need and demand for MiFIR completeness and accuracy across regimes has become very relevant, highlighted even further by the recent penalty announcements from the UK regulator, the FCA:

    The FCA’s Final Notice on 19 March for the first of this year’s transaction reporting fines, stated:

    “Firms must take reasonable steps to ensure the accuracy and completeness of the transaction reports that they submit to the Authority. One way that firms can help to achieve this is by having controls in place to reconcile the completeness and accuracy of their transaction reporting process.”

    The most recent fines were admittedly for transaction reporting inaccuracies under MiFID I, and MiFID II sanctions are not yet known or been broadcast. But it is only a matter of time before the next firm is penalised and this could well be for post-trade reporting inaccuracies (known unknowns). Stephen Hanks, Head of Markets Policy at the FCA, mentioned at an conference on 16th April that, “poor data quality is still being sent to APAs and that the FCA will continue to work with investment firms to improve quality as a priority”.

    What Now?

    MiFID II transaction reporting has clearly taken a regulatory priority since go-live but post-trade transparency reporting, its just-as-important sibling, is just as key. The past year’s Level 3 Q&As have brought clarity to previous ambiguous regulatory text so firms should now have a greater understanding of their reporting obligation but do they have the testing and controls in place?

    Stephen Hanks stated; “There are still issues we see in reports and we are particularly disappointed to still be seeing errors in reports which would have been errors under MiFID I, never mind MiFID II.”

    Really! Why? When??

    Yes, in amongst the turmoil of BRiFID, investment firms and regulated markets have a near to real-time responsibility to make sure their RTS 1 equity-like and RTS 2 non-equity trades are reported within one minute and 15 minutes respectively (reducing to five minutes by 2021). The responsibility wording is key. Firms may think they do not have a reporting responsibility or they may have asked their brokers to report on their behalf but have firms put in place the correct control framework to prove this if the regulators come calling?  Could this highlight a firm’s unknown unknowns?

    MiFID II has now been live for almost 15 months. With Brexit there is the very real situation that post-trade transparency reporting will need to be directed to either the EU or UK APA as well as liquidity shifting away from the main markets and the impact of ESMA’s Trading Obligation views.  This is a good time to make sure you’re also compliant with post-trade transparency reporting as well as transaction reporting. 

    What next?

    If you have any doubts about whether your post-trade transparency reporting and controls are up to the required standard, we can help. We have a proven track record in helping firms tackle their regulatory reporting issues and risks head on – and helping them to avoid censure. Our ReportShield™ quality assurance services provide everything you need for reporting assurance including a bespoke control framework, quality assurance testing of all fields on all reports, reference data testing, reconciliation and completeness checks and training. Contact us to find out more. 

  • Swiss Derivatives Regulator FINMA Recognises UK Derivative Regulations Ahead of Brexit

    In a move aimed at safeguarding regulatory compliance for Swiss derivative market participants trading under foreign law, the Swiss regulator, FINMA has provisionally recognised the derivative regulations of the UK with respect to reporting, clearing and risk mitigation obligations.

    At present, the UK falls under the territorial scope of EMIR and the clearing obligation (Art. 14 EMIR transposition act), reporting obligation (Art. 19 EMIR transposition act) and risk mitigation obligation (Art. 21 EMIR transposition act) offer equivalence with the relevant Swiss legislation (cf. Art. 97 (1) FMIA; Art. 104 (1) FMIA; Art. 107 (1) FMIA). The post-Brexit recognition of equivalence will enter into force when the EMIR transposition act passes into UK law.

    This announcement was made in FINMA Guidance 01/2019 BREXIT: Recognition of UK derivatives regulations. It should mean that firms subject to Swiss obligations to report can continue to use the UK’s ‘Recognition of Equivalence’ in order to report via a UK trade repository using a continuation of the ‘EMIR’ format.

    We are currently developing regulatory testing to meet quality assurance requirements for Swiss FINMA Finfrag and Sesta derivative and securities transaction reporting obligations. Please get in touch to discuss your requirements.  

    We’ve also published a Brexit White Paper which looks at the implications for reporting. Download it here to find out what you need to do to get ready by 29 March. 

  • White Paper – Brexit can damage your MiFIR transaction reporting and EMIR trade reporting

    White Paper – Brexit can damage your MiFIR transaction reporting and EMIR trade reporting

    UPDATED – 19 February 2019

    As we get closer to the withdrawal date, we have seen a flurry of statements from ESMA and the FCA on the impact of a hard Brexit on MiFIR and EMIR reporting obligations. As a result, we have revised our Brexit White Paper to take account of the recent statements.

    One of the most interesting developments was the statement from ESMA that EMIR trades and positions submitted to an EU trade repository by a UK counterparty would not need to be modified or updated post 29 March. The onus will be on the trade repositories to terminate these reports in the event of a hard Brexit. Before UK firms start celebrating, it should also be noted that these trades and positions could be ported to the newly established UK trade repositories and it is expected that firms will have to update and modify these trades as per usual. In effect, it is quite a seamless solution for firms and regulators alike. 

    As we’ve all discovered, Brexit is a fantastic opportunity to upset friends and family by sharing our expert views on the subject.

    Unfortunately, it will also have a profound effect on MiFIR transaction reporting and EMIR trade reporting.

    If there weren’t enough things to consider, we need to assess the impact it could have on branches, delegated reporting, outstanding trades, reportable instruments and personal data standards, just to name a few.

    Whilst it is tempting to bury our heads and wait for it all to blow over, the sad fact is that the impact on reporting could be brutal.

    We recommend that you put on your tin hats, batten down the hatches and prepare for a bumpy ride. What better way to start than reading our revised White Paper on the potential impact Brexit could have on your reporting? 

  • Will Brexit lead to a TRexit?

    Will Brexit lead to a TRexit?

    I spent some time last weekend catching up on the arguments for and against a Brexit. It got me thinking about the implications for reporting for firms in the UK. Now that the UK has voted to leave, will it have a major impact reporting-wise? Will obligations significantly reduce? I’ve come to the conclusion that in the main, I think Brexit will have very little impact on regulatory reporting. Here’s why:

    A transparent market is the ultimate aim

    Having seen the regulatory process and the development of transaction reporting legislation from inside the (then) FSA, my thinking is this: the UK needs clean markets to attract capital. To that end, the FCA has been at the forefront in establishing the transaction reporting regime in Europe as well as its shape under MiFID II. Clean capital markets will be even more important to the UK under a Brexit scenario so I fully expect that the UK would maintain a near identical transaction reporting regime. This could even include negotiating the ongoing exchange of transaction reports with our European neighbours under the existing MiFID model assuming that MiFID II is not adopted in full as a member of the EEA.

    Passporting

    Where an impact is more likely is for firms passporting into Europe today and they will be anxious about the future of their licence. Dependent on the outcome of negotiations on transaction reporting exchange, passported firms may have to report to their local competent authority (as today under MiFID I) and may lose the benefits of centralised reporting set out under MiFID II.

    Similarly, incoming branches to the UK may end up with a double reporting obligation to the UK and to their home competent authority. This would be more of a challenge were reporting obligations to differ between the UK and Europe but if they remain harmonised it reduces to a routing rather than a reporting problem. These risks I feel, will be addressed with a practical solution. After all, transaction reporting exchange is in place to provide that holistic view of activity on our markets. Without an agreed exchange, the FCA is likely to require market operators to report for members who do not have a UK transaction reporting obligation and similarly from the EU’s perspective.

    What about EMIR?

    For EMIR it is a similar story. EMIR needs to be global, not just European, if the data is to be useful for identifying emergent risks to the financial system: its primary aim. ESMA is currently working with Trade Repositories to standardise how information is made available to the array of regulators that have access rights to this information. Creating a UK specific regime, however well designed, would be an unwelcome complication for firms and Trade Repositories.

    Dual-sided vs single-sided

    Recent EMIR discussions have been around dual-sided vs single-sided reporting. My view is very pro dual-sided between financial counterparties as this goes a long way to promoting reporting quality. That said, for those non-financial counterparties delegating reporting to their broker, there is very little benefit for reporting quality of dual-sided reporting so this could easily be dropped. Similarly, many of the larger firms have created centralised reporting solutions and would not welcome divergence from the EU requirements, creating yet another distinct reporting obligation.

    So all in all, due to the added complications, and the UK having been a chief instigator in tougher reporting measures, I expect that the reporting world will continue very much in the same vein despite the UK voting to leave the EU.