Tag: ESMA

  • ESMA’s SFTR Data Quality Indicators: Progress with Limitations

    ESMA’s SFTR Data Quality Indicators: Progress with Limitations

    The New Framework 

    ESMA finalised its 23 SFTR Data Quality Indicators (DQIs) during 2024 and published them last month together with a “Framework for provision of data and follow-up on SFTR data quality issues“. The framework laid out how results of the DQIs are identified and expressed at the EU level, discussed at the Repositories Task Force (RTF) and shared with National Competent Authorities (NCAs) at the entity level.

    NCAs are now expected to follow up with the entities and provide feedback to ESMA. ESMA then reviews the feedback and performs a rerun to confirm the issue has been resolved, this is then shared with the RTF with any follow-ups deemed necessary. Given how variable and sporadic SFTR supervision has been across Europe, these are very positive developments. 

    Understanding the 23 DQIs: Not All Created Equal 

    Ask an ESMA official and all 155 SFTR reporting fields were created equal, however, I suspect that there is a very different view on the ground in the regulatory reporting oversight offices of the 30 NCAs and two European Supervisory Authorities (ESAs). Under SFTR, predominantly but not exclusively a systemic risk monitoring regulation, trade economics are king.  

    In summary, while the DQIs will provide the less sophisticated NCAs with a means of challenge their regulated entities in at least a minimal way, for others unfortunately at this stage, they may be little more than a distraction in performing their valuable work in keeping their domestic economies from harm. ie. time spent reviewing ESMA findings and coordinating responses may actually be better placed analysing genuinely systemic issues in that jurisdiction. 

    Two-Sided Reconciliation Tests (8 DQIs): Eight of the 22 DQIs rely on a fundamental assumption: that SFTR reports are genuinely two-sided. This means both parties have reporting obligations, are in the same jurisdiction, haven’t delegated their reporting, and their data comes from independent sources rather than shared systems. In theory, this creates a true representation of each firm’s books and records. However the reality is very different. These DQIs are flawed because so few reports are genuinely, independently two-sided. Most data ultimately comes from a single source – whether through shared systems, data vendors, or reporting delegation. In our experience, time and time again, two wrongs really do make a wrong when you’re trying to reconcile reports that originated from the same place.

    Reporting Discipline Issues (10 DQIs): A further 10 of the DQIs cover essentially SFTR reporting discipline issues rather than material economics. These include the number of rejected reports (NACKs), late reporting, missing variation margin reports on CCP cleared trades, client codes used in place of LEIs, missing issuer LEIs, incorrect reporting counterparty classification x 3, duplicate reports and not updated event dates. 

    The One with Potential: DQI 11A Anomalies 

    There is just one SFTR DQI that appears to have the potential to be truly powerful. Unfortunately like many things SFTR, it is rather loosely defined. DQI 11A Anomalies uses statistical approaches to identify abnormal/anomalous values in listed fields but encouragingly, in ratios between relevant fields too. This DQI spans 20 SFTR fields covering repo, securities lending and margin lending across loan values, collateral values, market values, lending fees, haircuts, CCP margins, collateral reuse and cash reinvestment (for securities lending). Arguably this should really be broken down into hundreds of sub and specific DQIs per type of SFT and nature of the test, such that there is a thorough understanding of the parameters and expectations. It would also enable firms to implement these indicators in their own controls frameworks. Unfortunately there are no further details or definition, such that both NCAs and reporting counterparties are left to guess the precise nature of the tests. 

    The Bigger Picture Problems 

    Aside from the limited instances of true independent two-sided reporting and an over-emphasis on reporting discipline, many of the tests also focus on the number of reports or instances, not their economic value. Also considering that in terms of market size and risk exposure, in excess of 75% of the SFT market in the EU is repo and the closely related buy-sellback market, it is something of a concern that the lion’s share of DQIs are focused on the securities lending. As primarily macro-systemic regulation, this is disappointing. 

    Looking Forward 

    It’s easy to pick holes in the new SFTR DQIs but for the forgotten stepchild of EMIR, they are certainly a move in the right direction. While at this stage it appears to be something of an opportunity squandered, firms should be painfully aware that they are on notice to up their game in terms of SFTR data quality. Those NCAs that have kept quiet and have been lurking in the shadows are highly likely to let their presence be felt once they start receiving DQI queries from ESMA that require their attention. 

    Kaizen’s quality assurance testing includes checking for all issues included in ESMA’s DQIs and many more. For a conversation with Jonathan or one of our regulatory experts about your SFTR data quality, please get in touch.

  • ESMA’s Data Quality Report 2024: MiFiR transaction reporting remains a key focus

    ESMA’s Data Quality Report 2024: MiFiR transaction reporting remains a key focus

    ESMA’s fifth report on data quality (published 30th April) – like last year’s – seemed light on a first read for MiFIR. But a second read alongside another ESMA document, the “Data Quality Engagement Framework (DQEF) for MiFIR’ published a week after the report, reminds us that MiFIR transaction reports and their data quality remain a key focus for ESMA and EU National Competent Authorities (NCAs).

    The purpose of MiFIR transaction reporting

    In the data quality report (DQR) ESMA reinforces, should we have forgotten, that data supports the day-to-day activities of financial regulators and remains essential for them to achieve their primary mandates of financial stability, orderly markets and market integrity.

    “Reduce the reporting obligations on firms”

    The DQR provides a number of use cases, introduces the DQEF and gives a significant mention to the role of transaction reports in the transparency and volume cap calculations that will reduce the reporting obligations on firms.  In case you missed it – “reduce the reporting obligations on firms”. The proof of concept (PoC) to prove the role of reports in these calculations determined that data quality is good but the DQEF being introduced is designed to address the critical data quality issues that became apparent during the exercise. 

    Improved tooling for increased scrutiny

    Furthermore, the DQR mentions that ESMA and NCAs now have improved tooling for monitoring markets. This includes details on the ESMA Data Platform (EDP) where regulators can share reported data and access predefined analytics to support them in their work.  As we highlighted last year – firms contributing reports to these calculations that are lacking data quality can expect their NCA to give them an opportunity to discuss the issues found.

    Delving into the details

    At a macro level, reported data under MiFIR is used to monitor overall trends and key market-level developments.  NCAs use the data in national financial stability reporting and sectoral updates whilst some have established systems to monitor trading venue activity or to rank firms based on their risk profiles.

    For the detection of market abuse, NCAs have developed a variety of automated alerting tools to highlight behaviours that could threaten market integrity for follow up by surveillance staff.  Data from different regimes is combined to identify cases of potential market abuse. 

    New tests to enhance data quality

    The PoC to test the potential for using MiFIR data for transparency and volume cap calculations achieved > 95% accuracy and hence will replace the existing systems (FITRS and DVCAP) and reduce the reporting burden for firms.  The discrepancies found will be addressed via the newly established DQEF based on ESMA’s existing transaction data validation rules and the TREM (Transaction Reporting Exchange Mechanism) DQEF tests, with new completeness, accuracy and consistency tests introduced to enhance data quality.

    The aim is to launch the DQEF in the first half of 2025 to allow NCAs and firms to address the quality issues found – ahead of the go live of the new transparency and volume cap system.   

    Conclusion

    We are often asked, ‘do regulators actually use the data?’ and the DQR provides clear evidence that they do. ESMA’s reuse of MiFIR transaction data for transparency and volume cap calculations demonstrates its commitment to reducing duplicative reporting – something the industry has long requested. However, increased data usage means increased scrutiny. Firms submitting poor quality data can expect to be contacted, remediation expected, warnings given and potential enforcement action.

    Firms often approach us for quality assessments after the regulator has challenged their data. This puts them in damage control mode.  The better approach is proactive quality assurance that identifies problems before regulators do. Please don’t hesitate to reach out to us at Kaizen to see how we can help.

  • ESMA’s 2024 Data Quality Report: EMIR Refit under the Microscope

    ESMA’s 2024 Data Quality Report: EMIR Refit under the Microscope

    ESMA released the fifth iteration of its Report on Quality and Use of Data (DQR) late last month, which highlights the use of reported data across multiple regimes, critiques submission quality, and references some of the enforcement actions carried out in 2024. This analysis focuses on the DQR’s EMIR data quality findings and their implications for firms. We have also published our SFTR analysis of the report.

    Focus on EMIR Refit

    Last year’s DQR placed a heavy emphasis on the potential for the EMIR Refit reporting changes to improve data quality. 12 months later, ESMA provides a mixed assessment:

    • ‘Positive assessment of go live’ in April 2024
    • Concerns regarding preparedness of Trade Repositories and reporting entities
    • Ongoing ‘need for further engagement for corrective actions’.

    EMIR Reporting was described by ESMA in last year’s DQR webinar as being ‘much more complicated’ under EMIR Refit. From Kaizen’s view of post-Refit reporting, many firms still have significant work to do to uncover hidden reporting issues and apply successful remediation procedures. This report may still be too early to provide a true reflection of data quality under the EMIR Refit regime.

    Limited Data Quality Indicators (DQIs)

    The EMIR metrics provided in the report give a limited and somewhat lacklustre view on where EMIR data quality currently rests.  Of the seven DQI metrics displayed:

    • Six show a mild improvement in data quality metrics (such as the Number of Outstanding Trades in Chart 3)
    • One indicates declining quality – percentage of missing valuations (Chart 7).

    A more comprehensive analysis of all the EMIR DQIs would be extremely useful for the industry and help us to gain a more accurate evaluation of data quality. ESMA’s Data Quality Dashboard for EMIR Refit document details (approximately) an additional 18 DQIs (c.25 in total) that are being actively monitored and discussed between supervisory authorities. The DQIs are a key tool within their regulatory arsenal and it is disappointing only a small number appear in the public report.

    Key DQI findings

    Rejection rates

    ESMA highlights the rejection rate of derivatives, which sits at approximately 1-2.5% across EU submitters. The rejection rate is described as ‘critical for authorities’ to ensure data is complete and accurate. ESMA’s expectation is for a ‘close to zero’ rejection rate.

    For me, the late report statistic is far more important, as firms are required to report trades in a timely and accurate fashion. Late submissions by some counterparties can lead to the view of unpaired submissions that distort the visibility of derivative exposure. Firms are required to report by end of day T+1, and are not in breach of any regulatory requirements if they resubmit a rejected derivative within that timeframe. In the absence of any material increases in this statistic, I question the value of emphasising it.

    Legacy format upgrades

    The DQR states that ‘36 million’ submissions needed upgrading to the new EMIR Refit format within 180 days from April 2024. At the end of February 2025, 2% of those submissions had not been converted. Firms with a UK EMIR reporting obligation should take note of the focus on updating old submissions and enforcing the strict schemas under EMIR. ESMA states firms should ensure ‘swift upgrading’ of any old format derivatives.

    Maturity date issues

    Abnormal or blank maturity dates continue to cause confusion (as shown in Chart 6), despite a small reduction to approximately 10% of submissions. Due to products such as CFDs, the maturity date fields have not been mandatory under EMIR Reporting’s validation rules, long prior to EMIR Refit. Regulators fully expect these ‘optional’ fields to be populated where applicable to the derivative. It is worth repeating:

    Optional fields do not mean the entity has a choice as to whether they are populated or not.

    Abnormal or blank maturity dates is a relatively high figure at 10% and ESMA explicitly expects a ‘lower percentage going forward’. Firms must ensure that this data point, and all further ‘optional’ fields are fully reviewed and are being reported for all submissions in a timely and consistent manner.

    Missing valuations

    Chart 7 shows that missing valuations are increasing (currently at 12.36%), even though daily valuations are required for a large majority of EMIR reporters and have been since August 2014. 

    Entity Responsible for Reporting (ERR)

    The DQR also places emphasis on a new field from EMIR Refit, the Entity Responsible for Reporting (ERR). This OTC field is described as a ‘crucial addition under EMIR Refit’ and ESMA appears dissatisfied with the volume of misreporting of this field (as shown in Chart 6).

    Trade Repositories’ (TRs) challenges

    ESMA gives mention to the reporting difficulties of TRs as well as entities, including issues such as:

    • Difficulty with reporting portability
    • LEI updates from M&A activity
    • Inter-TR reconciliation delays
    • Challenges providing complete reports to the NCAs.

    In my opinion, this highlights the complexity of EMIR Refit for firms and TRs alike, notably given the vast range of reportable products and lifecycle events, under a complicated reporting regime.

    The simplification paradox

    ESMA makes efforts to explain its desire to simplify reports and reduce the regulatory burden for firms. Very few firms will agree that this objective has been achieved in practice or in the spirit of the regulation. While many aspects of reporting have received welcome clarification, additional reporting requirements have been introduced and made the overall regulatory regime much more complex.

    What does this mean for firms?

    Based on the DQR findings, firms should focus on:

    1. Ensuring proper population (where applicable) of maturity data fields
    2. Valuation reporting – review processes to stop the increasing trend of missing valuations
    3. ERR field accuracy – verify the correct implementation of this ‘crucial’ addition
    4. Legacy migrations – complete any remaining pre-Refit format submission upgrades
    5. Rejection rates vs late reporting – while ESMA focuses on rejection rates, firms should also prioritise timeliness.

    Assessment

    Overall, I welcome the DQR’s attention to data quality critique and its motivation to help firms achieve regulatory compliance through complete, accurate and timely reporting. The justification of how data is used is particularly valuable, as this large operational burden is often questioned by firms.

    Going forward, the DQR would benefit from further transparency and metrics across the full suite of DQIs. This would help firms understand how their reporting is being reviewed by supervisory authorities and allow them to focus their limited remediation resources on improving the most material parts of EMIR Reporting.

    Better guidance and clarity would also ensure firms are better equipped to ensure reporting is complete and accurate at point of submission, negating the need for costly remedial action for firms and regulators alike.

    Concerned about the quality of your EMIR Reporting data? More than 200 firms from tier 1 banks to small fund managers rely on Kaizen’s quality assurance to meet – and exceed – their regulatory obligations. Contact us to request a demo or for a conversation with one of our regulatory experts. 

  • UK SFTR – Desynchronised Harmony

    UK SFTR – Desynchronised Harmony

    UK announces SFTR validation rule changes

    On 14 October 2021, the FCA published updated validation rules for SFTR in the UK. These amended rules are due to take effect on 11 April 2022*.

    In terms of the validation rules themselves, this move will bring them entirely into line with the new EU SFTR validation rules due to take effect from 31 January 2022. The current rules differ slightly in the treatment of price currency loan and collateral fields.

    We think this is the right approach – UK/EU rules should either be harmonised (as is the case here) or fully diverged (as part of a more aggressive regulatory arbitrage) but not somewhere in no-mans-land in the middle.

    The timing (April rather than January) arguably gives firms a little more time to implement the changes (something the industry has been very vocal about). The fact that these were announced in mid-October rather than the end of July (when ESMA made its announcement) negates this benefit somewhat, particularly for firms that only have a UK reporting obligation. The current two-speed timing (EU implementing in January and UK in April) also complicates things for dual reporting firms as it means two and a half months of validation rule divergence.

    The FCA is dangling a carrot as firms will have until 11 April 2022 to make the changes. We hope ESMA will take the bait and offer a matching extension to its original implementation date!

    *Please note this date was updated from 14 April.

    • If you have concerns about your firm’s SFTR data quality and regulatory compliance, working through the changes to the validation rules or undergoing trade repository migrations, we can help.  Please contact us for a conversation with Jonathan or one of our regulatory specialists to discuss your challenges.  
  • ESMA and the European Commission clarify treatment of Alternative Investment Funds (AIFs) under SFTR

    ESMA and the European Commission clarify treatment of Alternative Investment Funds (AIFs) under SFTR

    The European Commission and ESMA have both dispelled any concerns that non-EU AIFs were being brought into scope for SFTR reporting if their AIFMs were EU-based.

    A paragraph in the Final Report that accompanied the Level 3 Guidelines on SFTR reporting on 6 January, raised concerns as it appeared to bring non-EU AIFs into scope for SFTR reporting if their Alternative Investment Fund Manager (AIFM) was based in the EU. This statement, while apparently contradicting elements of SFTR Level 1 (the regulation itself), Level 2 (the regulatory and implementation technical standards (RTS & ITS)) and other elements of the guidelines, nevertheless raised fears that extra territoriality was sought by EU regulators.

    In response to trade association concerns, both ESMA and the Commission have responded in letters stating that non-EU AIFs will not come into scope for SFTR reporting regardless of where their AIFM is based.

    Furthermore, ESMA provides further clarification about the nature of the Final Report and how to distinguish it from the Guidelines themselves. The Final Report provides feedback on the consultation responses, a summary of proposals in the consultation paper and an assessment of the feedback. They hasten to add that while some of the feedback resulted in amendments to the guidelines, other elements were discarded. They further emphasise that reporting parties should focus on the Guidelines and not the Final Report as it is the Guidelines that contain all the clarifications and examples to enable reporters to be compliant with the Level 1 SFTR regulation.

    The Commission in its response, re-states that SFTR Article 2(1) limits the application of the regulation to “(a) a counterparty to an SFT that is established (i) in the Union, including all its branches irrespective of where they are located; (ii) in a third country, if the SFT is concluded in the course of the operations of a branch in the Union of that counterparty.” Therefore, an AIF not established in the Union is not subject to the obligations set out in Article 4(1) SFTR.    

    Now we can only hope for such definitive feedback from the Commission and ESMA in relation to settlement finality and the reporting of bilateral variation margins…to be continued!

    You can read the letters here.

    We are helping a number of investment firms prepare to report accurately for SFTR.  Please contact us for a complementary consultation with one of our regulatory experts. 

  • FIRDS: Are trading venues contributing to poor quality transaction reporting?

    FIRDS: Are trading venues contributing to poor quality transaction reporting?

    Perhaps the biggest irony about MiFIR transaction reporting is that reports submitted by investment firms need to be complete and accurate, but ESMA states it cannot provide any guarantee that one of the key tools firms need to do this, the ESMA FIRDS reference database, is “complete, accurate or up-to-date”. This is particularly harsh on firms as they can report with the correct ISIN to identify the financial instrument, but if that ISIN (or underlying ISIN) is not on the FIRDS database within seven calendar days, then the report will be rejected by the competent authority. The onus is then on the firm to investigate whether they should re-submit the report.

    This is unfair on firms as most of them are trying to do the right thing by only reporting transactions in instruments that are reportable, but they are frustrated with limitations of ESMA’s FIRDS database. It would be easy to blame ESMA for this, but I believe that also is unfair. The quality of FIRDS can only ever be as good as the information submitted to it and it is the EEA trading venues that are obliged to submit this data through the requirements detailed in RTS 23. The quality of FIRDS data has improved dramatically since go-live, as you would expect over the course of two years, and many trading venues may be reporting perfectly. However, other trading venues are not, and deficiencies in this reference data was highlighted in Germany’s Ministry of Finance’s position paper on MiFID and MiFIR.

    Germany’s Ministry of Finance concludes that “ further analysis is needed on the question of how to ensure the provision of accurate, reliable and timely reference data. The analysis should also explore ways to make FIRDS the golden source for reference data.” Well I’m sure we all know the obvious answer to this one – there is nothing quite like a sanction, perhaps in the form of a fine and public censure, to ensure data quality is taken more seriously. We have seen sanctions used for firms’ poor transaction reporting and how this can focus attention, so maybe trading venues need to be wary of the possibility of sanctions if they don’t improve the quality of their reference data. If you are a trading venue that has doubts about the quality of its reference data, now might be a good time to look at quality assurance solutions.

    The quality of FIRDS data also impacts the thorny issue of the ESMA opinion paper on OTC derivatives traded on a trading venue. In this paper, ESMA expands the reportable instrument set to include “OTC derivatives sharing the same reference data details as the derivatives traded on a trading venue”. This paper has caused much consternation in the industry. Whilst some firms have paid as much attention to the opinion paper as a London cyclist does to a red light, many other firms are desperately trying to do the right thing in trying to match the reference data attributes of their OTC derivatives against the attributes of derivatives on the FIRDS database to see if they are reportable. The quality of the FIRDS data, and the flexibility of FIRDS itself, often makes this a frustrating and imprecise task. This appears particularly true for FX and interest rate derivatives and prompts the question (also asked by Germany’s Ministry of Finance) of whether the concept of ‘traded on a trading venue’ should be applied to OTC derivatives. Anybody who thinks it should, needs to try assessing whether some OTC FX swaps are reportable or not. They would probably find that they first need to match attributes against the ANNA Derivatives Service Bureau to find potential ISINs and then compare the attributes associated with these ISINs against FIRDS to see if the instruments are reportable (not forgetting to check if the underlying forwards have reportable ISINs). They may well struggle with the flexibility of FIRDS in this task and may possibly be perplexed by the quality of much of the data – for example, the lack of consistency between the financial instrument long name and the attributes, particularly the expiry date. 

    Whilst the MiFIR definition of reportable instruments appears easy on paper (MiFIR Article 26(2)), there is plenty of devil in the detail and many firms struggle to fully understand them. These firms are unlikely to understand the implications of the ESMA ToTV opinion paper and it does appear to be too complex a requirement for the associated regulatory benefit. The current data quality and flexibility of FIRDS does not seem fully adequate to support this requirement. More importantly, it appears that the quality of FIRDS reference data may be causing issues with the overall quality of transaction reporting. Whilst many trading venues are on top of the task of their RTS 23 reporting, it appears that some trading venues need to up their game to avoid regulatory attention.

    If you’re worried about the quality of your reported data, this is why we here at Kaizen exist. Our accuracy testing and reference data testing services check all data fields in every trade or transaction report submitted to the regulator so you have a full picture of the quality of your reporting.  Contact us for a discussion on how we can help. Join in the conversation over on our LinkedIn.

  • Video: David Nowell on what is happening with EMIR Trade Reporting

    Video: David Nowell on what is happening with EMIR Trade Reporting

    In this video, David Nowell answers the below questions:

    • Why is EMIR important?
    • Following recent comments from ESMA about the FCA and other NCAs, what changes are we likely to see?
    • What do the changes mean for financial firms?
    • What are the key changes from the recent EMIR re-fit?

    If you need help with your EMIR Trade Reporting data quality, get in touch.

  • SFTR reporting final guidelines – ready, steady….go!

    SFTR reporting final guidelines – ready, steady….go!

    In this blog, we explain the securities financing transactions reporting final guidelines

    It was good news last week for those of us who’ve been waiting for ESMA to publish the final guidelines for SFTR reporting. The overriding principle of the regulation which these new guidelines reinforce, is that reporting firms are expected to populate the database in as comprehensive, timely and accurate basis as possible. These guidelines, the final report (responding to consultation feedback), updated validation rules and a statement on non-EU issuer LEIs offer some contradictions and will not please all market participants but do provide much of this framework.

    Of course this blog is no substitute for reading the guidelines but here are some of the highlights:

    Timeline

    ESMA confirmed reporting obligations for credit institutions and investment firms (banks) go-live on Monday 13 April (for EU jurisdictions that do not observe Easter Monday as a public holiday) or Tuesday 14 April for those that do. In either case, reporting firms are required to send reports for any SFTs executed on or after Saturday 11 April. Market infrastructures will follow accordingly on 13 July, buy-side on 12 October and non-financial counterparties on 11 January 2021.

    Non-EU issuer LEIs

    ESMA acknowledged that only 30% of non-EU issued securities currently have an issuer LEI and therefore have removed the need to populate these security loan and security collateral issuer LEI fields for non-EU issued securities until 13 April 2021.

    Third party executed reportable trades

    ESMA have provided clarity on which SFTs executed on behalf of the reporting counterparty through powers of attorney are reportable under SFTR. The following are reportable:

    • CSD fails curing transactions in which securities are automatically borrowed. Credit or securities provided to avoid settlement fails are collateralised with the securities account of the borrowing CSD participant
    • Auto-collateralisation transactions where payment banks or their clients are counterparties.
    • CREST client auto-collateralisation trades.

    However, CCP “daylight lending facilities”, auto-collateralisation trades with an ESCB counterparty and intraday credit/overdrafts resulting from fails-curing transactions are all out of scope.

    Third country reporting obligations

    ESMA has advised that in bringing SFTR into line with EMIR, for a transaction to be in-scope for reporting by an EU branch of a 3rd country entity, the term ‘conclusion’ relates only to instances in where they are a counterparty to the trade. i.e. the counterparty where the SFT is booked. References to the EU branch merely supervising trading in a third country entity have been removed.

    Settlement fails reporting

    The guidelines require reporting parties to modify the maturity date (roll it forward to the next day or an expected settlement date) in the reports they send on settlement date +1 if a transaction is failing. It must be modified on this day because going forwards without modification it will be closed and not possible to re-open it. Providing this feedback loop on settlement status is going to be tricky.

    However, the treatment of partial returns is different where “a delayed settlement that does not result in a cancellation of the partial return, should not be reported.” 

    UTI failure

    There is no prescribed approach in the guidelines about what to do if your counterparty – responsible for creating and sharing the UTI – fails to provide it ahead of the COB T+1 reporting deadline. It simply states that “counterparties should ensure a timely solution.” Essentially reporting parties must chase and not report anything until the UTI has been shared, and document all of the steps taken to obtain the UTI.

    Valuation considerations / market values

    Market values should be reported as of close of business each working day. The values used for collateral and exposure management purposes should use most recent market prices or bilaterally agree valuations with counterparties if none are readily available. This requirement to agree values contradicts with a further statement about the unavailability of price information. This relates to some suspended shares and illiquid fixed income securities where counterparties should report the valuation contractually agreed upon conclusion of an SFT. Only then should the market value be updated with a valuation, when new price information becomes available.

    ECB FX rates should be used for valuations or bilaterally agreed rates if none exists. The need to align FX rates is a concern for the industry, given many reporting parties use an enterprise rate, not only for SFTs but across their businesses.

    Re-use reporting with delegated reports

    If reporting has been delegated, the counterparty to which reporting has been delegated is not responsible for the reporting of the estimated re-use of the collateral. NFCs are responsible for calculating the estimated re-use themselves and in providing the estimate to the counterparty in charge of reporting in a timely manner.

    CFI sourcing

    The guidelines state that counterparties should retrieve CFIs from ANNA, National Numbering Agency (NNA) or, if not available, request it at the relevant NNA of the instrument. Unfortunately by acknowledging that it is reconcilable, they contradict themselves by saying that if it doesn’t exist in the official sources then it should be agreed between counterparties. It certainly seems that official sources should be exhausted and CFIs should be requested from the NNA before attempting to derive CFIs.

    Security / collateral quality

    Ratings should be instrument-based and use internal assessments of credit quality rather than mechanistic reliance on credit rating agencies, who use measurements such as local vs foreign currency, short vs long term investment to reflect security specifics. ESMA acknowledge the resultant higher rate of reconciliation breaks. However, they fail to acknowledge sensitivity around sharing any aspect of internal ratings and the fact that many counterparties will not have fully on-boarded many securities that appear on settlement date in collateral baskets. This is likely to require some industry driven solutions.

    Variation margining 

    There is fresh guidance on how to report the collateral given or taken on a net exposure basis through post on-leg, value date, variation margin calls to complement the original trade level collateral. Counterparties should send single collateral update messages to reflect these bilateral variation margin calls. The direction of the collateral should be expressed with a sign against its market value i.e. negative for rows of collateral given and positive for collateral taken.

    Floating rate transactions

    When reporting floating rates, counterparties should indicate the relevant rate and the applicable spread. They should only provide updates when they agree to change the rate or the spread but not on a daily basis.

    Report tracking numbers (RTN) and open offer trades

    In reporting trades executed on venues where execution is contingent on central clearing (open offer basis), including DBV trades, reporting firms are not required to populate the report tracking number (RTN).  It is important to note that the clearing time and execution time would be expected to match.

    In instances in which a trade is bilaterally executed and subsequently subject to clearing (even same day), it requires the prior UTI to be reported as the RTN.

    Our view of the guidelines is that they do provide some clarity and are a step forward from where we were. However they do not provide all the answers and contradict in some places. Because of the diverse scope of the regulation, one size doesn’t fit all and it’s now for the market to interpret as best we can. Good luck and let us know how you’re getting on. 

    Kaizen’s ReportShield™ accuracy testing, advanced regulatory reconcilation and reference data testing services will help ensure your reporting is accurate from day 1 of go-live.  

    Contact us to find out more about how you can make a smooth transition to SFTR reporting.

  • €STR versus SONIA

    €STR versus SONIA

    The introduction of the new euro short-term rate (“€STR”) by the European Central Bank (ECB) in October caused potential issues for MiFIR transaction reporting and RTS 23 instrument reporting as there was no standardised four character code in RTS 22 or RTS 23 for the new benchmark rate. Fortunately, ESMA has addressed problem by creating a new four character code of ESTR for the index name and stipulating that the ISIN EU000A2X2A25 should be used to identify the index. Clearly this will be transformative in the number of successful market abuse cases brought by the regulators. ESMA details how these codes should be used for both RTS 23 and RTS 22 reporting in its December MiFIR Data Reporting Q&A.

    However, the ESMA guidance on €STR does highlight certain anomalies with the treatment of other interest rate benchmarks. For example, it’s the only interest rate where the ISIN also needs to be populated in the ‘Underlying Instrument’ code field. But perhaps the strangest anomaly is that there appears to be no equivalent treatment for the Sterling Overnight Index Average (SONIA). This was introduced in March 1997 and is used to value around £30 trillion of assets each year. SONIA derivatives are also traded on regulated markets, but there is no standardised four character code for this sterling interest rate benchmark and ESMA has not addressed this issue in the same way it has for the euro interest rate benchmark. It’s a similar story for EMIR, where the ‘ESTR’ code was added to the list of four character codes to identify floating rates, but no similar additional was made for SONIA. Why is this, I wonder? Answers on a postcard please…

  • No market abuse sanctions by FCA in 2018

    No market abuse sanctions by FCA in 2018

    ESMA has published its peer review on how national competent authorities handle suspicious transactions and orders reports (STORs) under the Market Abuse Regulation. It is fully compliant in four of the ESMA metrics and broadly compliant in the other two.  So congratulations FCA – pretty much top of the league in this review.

    However, what is interesting is that despite this near-perfect report card, the FCA has not imposed any measures and sanctions on firms.  Surely the true measurement has to be the number of successful market abuse cases the regulator has brought? The ESMA report has a handy table showing the number of measures and sanctions imposed for market abuse infringements and the UK figures for 2018 show no sanctions.

    Without wanting to appear like the Christmas Grinch, in our view this is a very disappointing figure. Bearing in mind that 2018 marked the introduction of a dramatically more complex transaction reporting regime which offers regulators a far richer data set to monitor market abuse more effectively, this failure to sanction would indicate to us that something isn’t right.

    Whilst many firms are making great efforts to report STORs and to submit transaction reports, the FCA can only do its job effectively if those transaction reports are complete and accurate. If you are not completely confident that your transaction reports meet this requirement, talk to us about our ReportShield™ data quality, reconciliation and training services.

    What do you think about this peer review from ESMA? Join in the conversation over on our LinkedIn.

  • SFTR validation rules and schemas from the ESMA cauldron…

    SFTR validation rules and schemas from the ESMA cauldron…

    Halloween saw some new ghoulish delights appear from the ESMA cauldron with the publication of SFTR validation rules (revised following the summer consultation) and XML schemas for reporting. ESMA has released four documents covering:

    1. SFTR report validation rules
    2. Counterparty and Trade Repository (TR) data exchange XML schema
    3. Intra-TR data exchange XML schema
    4. TR to authority data exchange XML schema.

    We have created a marked changes version of the latest validation rules to highlight the differences.

    Tighter but more logical 

    The validation rules have been tightened up to reflect instances in which fields that business logic dictates should be mandatory or conditional are no longer optional. For example, the loan field ‘security quality’ is now conditional rather than optional for new securities lending transactions. In other instances, fields that were not rationally mandatory (e.g. ‘maturity {date} of the security’ fields for both loan and collateral) are now conditional. The rules generally make more sense, particularly in relation to the two changes noted below.

    Full reporting – not delta reporting

    Modifications and corrections at both trade and position level now require all of the original counterparty table fields to be populated. In most cases, they also require the same fields to be populated in the loan and collateral table as in the original NEWT report in accordance with the same mandatory and conditional rules as the original report. This requirement for full reporting of modifications and corrections should be clarified in the level three guidelines when published by ESMA later this quarter.

    Bilateral Margining Simplified

    The ‘counterparty side’ is no longer required for collateral updates, making bilateral margin reporting simpler. Since stating whether the reporting party is a collateral giver or collateral taker is no longer a pre-requisite of providing a bilateral margining collateral update (COLU) or any other COLU report, it is much more straightforward to report instances of collateral flowing in both directions with the same other counterparty.

    The references to negative values of securities in the ‘counterparty side’ validation field notes on format and content have also been removed (in addition to this field being no longer required for COLU reports). Instead, the ‘collateral quantity or nominal amount’ is now permitted to be negative, enabling you to report collateral moves in either direction – as a margin giver or taker for example. You are also now permitted to use negative values in the ‘price per unit’ field. Again, we hope for further clarification when the reporting guidelines are released.

    The publication of schemas, the cementing of validation rules and a number of key clarifications (as highlighted) puts the industry in a much greater state of readiness for reporting – now only five months away.  Our advice?  Don’t now wait for final reporting guidelines (due later in Q4) but focus full steam ahead on implementation, testing and establishing your controls environment.  And if you’d like to discuss how we can ensure you are compliant with SFTR reporting rules, please don’t hesitate to contact us.

    The new validation rules and schemas are available on the SFTR section of our website.

     

  • Join us at Infoline’s Trade and Transaction Reporting Conference in Stockholm

    Join us at Infoline’s Trade and Transaction Reporting Conference in Stockholm

    We are delighted to be able to offer 30% off tickets. Use code FKM63769KAIZEN.

    Register

     

    Calling all investment firms, securities firms, banks and trading venues impacted by the reporting and disclosure obligations of SFTR, MiFIR and EMIR! Please join us at this one day conference in Stockholm. Don’t miss our Senior Regulatory Reporting Specialist, Jonathan Lee, discussing SFTR Reporting best practice and how to prepare for the April 2020 go-live at 10:30am. Followed by Senior Regulatory Reporting Specialist, David Nowell, on a panel to discuss the ongoing challenges with MiFID II Transaction Reporting and EMIR Trade Reporting. 

  • EMIR – Pairing and Matching at Position Level to be implemented in December 2019

    EMIR – Pairing and Matching at Position Level to be implemented in December 2019

    In what will undoubtedly be a surprise to the majority of the industry, ESMA has asked the trade repositories (TRs) to implement pairing and matching at position level. Previously, the pairing and matching had only taken place at the trade level reports. Whilst this undoubtedly makes sense, it could cause massive issues for investment firms as there appears to be no current mechanism or infrastructure to ensure the two counterparties use the same UTI at the position level.

    It also appears unclear which position level reports will be subject to the reconciliation process. Originally, position level reporting was optional, but the requirement for cleared trade reports to use the CCP’s valuation implies that ETDs have to be reported at a position level where the CCP only provides position level valuation. However, there are a number of other derivative types that are not subject to clearing but can be reported at a position level such as spread bets and CFDs. If these are also to be subject to position level reconciliation, it could result in confusion as there appears to be no legal basis requiring both sides to report these instruments at a position level.

    We understand that the position level reconciliation will be deployed by the TRs on 9 December this year. This gives firms precious little time to determine how they will agree on the UTI to be used at a position level and a process for the dissemination of this information to meet the T+1 reporting requirement. It is unfortunate that neither ESMA nor the FCA appears to have widely publicised this imminent requirement. As a new iteration of the ESMA Q&A on EMIR was only published earlier this month, it is surprising that ESMA did not take this opportunity to inform firms of the change.

    At Kaizen, we always update our services to reflect regulatory changes. If pairing and matching is something you’re struggling with, our quality assurance services include checking that your EMIR position level reports truly reflect the corresponding trade reports submitted. For further details of our services please contact us to get your reporting complete and accurate.  

  • ESMA clarifies FX forwards transaction reporting in new MiFIR Q&A

    ESMA clarifies FX forwards transaction reporting in new MiFIR Q&A

    ESMA has provided a very useful example of how to report FX forwards in its latest Q&A on MiFIR data reporting. In particular, we would urge firms to take note on the practice of populating the ‘quantity’ and ‘price’ fields:

    • The ‘quantity’ (and ‘quantity currency’) should reflect the amount of the FX forwards in the base currency
    • The ‘price’ (and ‘price currency) should show the forward rate expressed as a price of base currency in the quoted The monetary value XML tag should be used (if reporting to an ARM in flat file, ‘price type’ is monetary value.

    The only additional changes appear to be in the table of national identifier formats. This details a change in the format of Portuguese passports issued after April 2018 and corrections to the Romanian National Identification Number and national passport formats.

    Whilst the new MiFIR Q&A signals only relatively minor changes, it clearly demonstrates the need for firms to remain on top of regulatory developments. Our regulatory reporting training courses help firms stay abreast of the reporting requirements and help identify any interpretational errors. For further details, please see our training courses.

     
  • In the news: David Nowell and Chris Machin speak to FOW

    In the news: David Nowell and Chris Machin speak to FOW

    Our Senior Regulatory Reporting Specialists David Nowell and Chris Machin recently sat down with James Thursfield from FOW to discuss the results of the German Ministry of Finance industry consultation. The article highlights the need for a golden source for reference data and the role of the FIRDS database.

    “The regulators are well aware of deficiencies with the FIRDS reference data and already state that it cannot be relied to be complete, accurate and up-to-date,” Nowell told FOW. 

    “Esma has always, even before go-live, stated that they would not be the Golden Source (even if de-facto they actually are) and no solution has been suggested,” Machin said.

    Read the full interview.

  • 10 Lessons from industry responses to the ESMA Guidelines Consultation

    While not an exhaustive list, here are our key takeaways from reading the ESMA SFTR Guidelines consultation responses. The overall level of engagement in relation to the consultation was substantial, with 49 files published by ESMA following the consultation period.

    1. Reporting certainty

    A few fundamental questions are key to providing clarity to support a timely build for SFTR reporting. Banks and credit institutions (due to report from April 2020) need answers to some of the these questions well in advance of the self-imposed Q4 2019 deadline set by ESMA.

    In particular, question 25, whether to provide full reports or the delta of changes for modifications and corrections – respondents overwhelming voted for full reporting.

    2. Reportability of intraday market infrastructures executed SFTs

    Which intraday transactions executed on behalf of firms by CSDs and CCPs remain in-scope for reporting? While T2S Auto-collateralisation transactions are explicitly excluded from reporting, does this also cover UK Crest Auto-collateralised repos? Extracting and reporting this data presents unique challenges.

    3. Scope and third country considerations

    The approach to determining the ‘conclusion’ of a transaction by a branch is far reaching and strays from the EMIR definition. It appears to focus on the activities of individuals rather than risk held in the EU. The practical challenges of reporting SFT activities of non-EU entities where traders are supervised by EU branches are immense and likely to lead to significant confusion in relation to areas such as bilateral margining and reuse.

    Concerns were raised where SFTR does not require non-EU AIFs managed by EU AIFMs to be reported (unlike EMIR), while EU AIFs must be reported regardless of whether the AIFM is based in the EU (again unlike EMIR).

    4. Why are buy-sell backs still treated differently?

    ESMA have specified that documented buy-sell backs should be reported as buy-sell backs listing the master agreement, but it is still unclear why the reporting requirements differ from repo. The inability to apply a repo rate, forward breakeven yield or forward price on a buy-sell back is a particular issue.

    5. Is fails reporting really required?

    There has been some confusion about the reporting of settlement fails (general consensus was that perfect settlement would be assumed unless both parties chose to modify a transaction to reflect a default or extended fail).

    6. How to report bilateral variation margining

    Concerns continue to surround the reporting of bilateral variation margins for repo. Given these margin calls at the counterparty portfolio level are entirely separate from the trade level collateral, there should be a separate end of day collateral update report to reflect bilateral margining. They cannot, as ESMA examples suggest, be incorporated with trade level collateral updates.

    7. Failure to transmit Unique Trade Identifiers (UTI)

    The issue of what to do if a counterparty is responsible for providing the UTI fails to provide it in a timely manner for reporting, remains an open question. The real question is how the party subject to late notification of the UTI by their counterparty can be excused from their obligation to submit timely reports.

    8. Availability & consistency of reportable data

    There are many concerns about the availability of data for reporting. The FSB themselves highlighted in their May 2019 document Thematic Review on Implementation of the Legal Entity Identifier that on aggregate only 55% of all financial instruments in scope have an LEI code (representing 78% of outstanding amounts) and that only 11% of all firms that are issuing securities have so far obtained an LEI. Mandating usage of issuer LEIs when firms that use securities as collateral have no contractual relationship with the issuer of the securities, appears a step too far. Solutions are to make the field conditional or apply a standard dummy issuer LEI.

    Other concerns persist around missing official CFI codes, ISIN codes, differences in credit rating assessments between firms and the collateral type field.

    9. The removal of ESCB transactions from the calculation

    Trade associations reiterated that removing ESCB transactions from both sides of estimated re-use calculations will be both difficult and misleading. Nonetheless, this is understood to be an FSB requirement rather than ESMA specific.

    10. Uncertainly around in-scope commodities financing transactions

    A number of trade associations and other respondents commented on the significant uncertainty felt by the commodities trading industry around the SFTR reporting scope of any of their transactions. Concerns were raised that while commodities financing transactions share attributes with SFTs, they are not executed for financing purposes. Disagreement exists as to which transactions constitute repos and which buy-sell backs, in general they were deemed hard to define under existing SFT definitions. There are also concerns that certain commodity transactions, believed to best fit the repo definition use pledge arrangements and not title transfer. Some power and gas contracts may also be reportable under SFTR as well as REMIT. While exclusions are in place for EMIR, they are not in place for REMIT.

    Did you know Jonathan provides CPD-accredited, CISI-endorsed training on the SFTR reporting requirements? Book your place on one of our upcoming courses here or get in touch for bespoke, in-house training.   

  • A tsunami of EMIR Q&As

    A tsunami of EMIR Q&As

    Just when you thought it was safe to go back into the water, ESMA has hit us with a third EMIR Q&A in as many months. The impact on trade reporting can be summarised as follows:

    Funds and counterparties (General Question 1)

    The text now states that the fund manager must (rather than can) report on behalf of the funds and that the ID of the fund manager shall be provided as the report submitting entity. Please take care with this statement – we do not think it should be taken at face value. Whilst the amended EMIR Article 9 makes the fund management companies ‘responsible and legally liable’ for the reporting, we do not believe this is intended to prohibit delegated reporting by the broker (or another third party) on behalf of the fund manager (where the third party would be the ‘submitting entity’). It is another example where ESMA needs to be more precise in its use of language and advice to the industry.

    Reporting of outstanding positions following entry into force of EMIR (backloading)

    TR Question 4 has been completely deleted reflecting the removal of the backloading obligation following Refit.

    Intragroup transactions (TR Question 13)

    Again, synchronising with Refit, the text clarifies that intragroup trades are not reportable if certain conditions are met. These conditions are outlined in TR Question 51.

    Blocks and allocations (TR Question 39)

    Similar to General Question 1, we have further imprecise text from ESMA. ESMA states that the fund manager must report to the trade repository on behalf of the individual fund where the fund is identified as the counterparty to the trade. While the fund manager is responsible and legally liable for making the report, it can still delegate the reporting obligation. This ‘change’ applies from 18 June 2020.

    Notional amount field for credit index derivatives

    Where there is a change in index factor due to credit events, counterparties should not modify the notional (field 2.20); they should only change the index faction (field 2.89).

    Conclusion

    Not a huge amount of change in the latest Q&A, but it does demonstrate some of the pitfalls in interpreting the ESMA text and the importance of keeping in touch with the regulatory changes. If you’d like some help interpreting the changes or would like transparency of the quality of your EMIR trade reporting, please contact us to find out more about how our quality assurance and controls can get your reporting accurate.

  • ESMA fines trade repository for data delivery breaches

    ESMA has announced it has fined a trade repository for failing to provide regulators direct and immediate access to details of derivative contracts. The failures relate to trade terminations and valuations and collateral updates for the period from the start of EMIR trade reporting go live in February 2016 through to October of the same year. According to the public notice, ESMA remained unaware of the error until it was informed by the Dutch national competent authority (NCA) in July 2016.

    The fine should be a reminder to all industry participants that ESMA takes EMIR trade reporting very seriously. ESMA and the NCAs also have a ‘Data Quality Action Plan’ to address quality issues in EMIR trade reports submitted by firms.

    If you are in any doubt whether your reports meet the standards required by the regulators, please get in contact with us to discuss your EMIR data quality. The FCA has already issued a £34.5m fine for EMIR reporting breaches – we can help you put the right controls in place to make sure that you are not at risk too.

  • MiFIR transaction reporting goalposts set to shift again

    MiFIR transaction reporting goalposts set to shift again

    Whilst it may be a bit more of a tweak than a wholesale change, firms need to be aware and plan for changes to the ESMA validations that are targeted to come into effect on 23 September this year. 

    The changes were agreed back in July 2018 but delayed by the Brexit postponement and are mainly amendments to cover mistakes in the validation previously introduced. The changes, cut and pasted from the ESMA version history, are as follows:

    • rule id 010: field 3 must not be populated. This also pertains to SIs;
    • rule id 014: add provision for the case when an LEI is in the “Lapsed” status for a certain period;
    • rule id 096: validation of field 28 against the reception timestamp;
    • rule id 117: field 37 not mandatory for SIs;
    • rule id 136: check against additional CFI codes;
    • rule id 154: check against additional CFI codes;
    • rule id 227: correction of a typo in one of the CFI codes.
    • Clarified description of rules 228 and 267.

    For me, the most important of these changes is the change to Rule 117.  From the implementation of this change, firms should no longer populate ‘Country of branch membership’ for trades against systematic internalisers. Of course, this field should never have been populated for trades against systematic internalisers in the first place as this contravenes the Regulatory Technical Standards (“This field shall only be populated for the market side of a transaction executed on a trading venue or on an organised trading platform outside of the Union.”). I think it is important to highlight that this oversight has forced firms to make an error in their transaction reports in order for them to be accepted by the NCAs.

    I don’t wish to criticise the regulators for making errors, as I believe it is inevitable that there will be some initial errors in the implementation of such a complex regulatory reporting regime – for both regulators and firms. However this issue clearly raises the question about whether the NCA would expect every firm to submit a form when they are forced to report incorrectly in order for the NCA to accept the report. There has to be a degree of common sense and this is not reflected in the wording of Market Watch 59.

    It is also fair to say the changes have not been widely publicised. ESMA has made a notification of changes but I’m sure most people, like me, will find this notification extremely difficult to understand. I’m sure people will also be confused by the validation version history that still states that the changes were “applicable from the end of 2018”. Perhaps the FCA is waiting for more confidence in the 23 September implementation date before it makes an announcement. However, whilst these changes aren’t major, firms need time to assess the changes, code and test any required system changes. September 23 already appears very close.

    Kaizen will of course be updating our ReportShield testing to include the latest validation changes in time for September 23. We provide validations as part of our accuracy testing service at no extra charge to clients – saving significant costs in avoiding outsourcing an additional validations service. Please contact us for a discussion with one of our regulatory experts to find out more.

  • Sunny ESMA provides some SFTR relief

    Sunny ESMA provides some SFTR relief

    ESMA published a Consultation paper “Guidelines for reporting under Articles 4 and 12 SFTR,” together with the latest consolidated SFTR validation rules. The deadline for responses is 29 July 2019. ESMA plan to consider feedback during Q3 2019 and the final report is scheduled to be published in Q4 2019. This does not give a lot of time, particularly for the 1st phase of reporting counterparties (Banks), due to go-live in April 2020.

    Nevertheless, ESMA provided clarity on many issues and gave reason to be cheerful as many SFTs executed on behalf of financial institutions through powers of attorney during the course of daily clearing, custody and settlement activities at CCPs, CSDs and ICSDs were ruled out of scope. This has undoubtedly removed a major operational headache from the SFTR reporting requirements and will assist regulatory authorities in gaining a better understanding of the data (as they will be significantly less overwhelmed with noise).

    • In particular, Chapter 5 (General Principles), paragraphs 25-27 rule out any reporting of short term credit lines for custody or CCP clearing.
    • Paragraphs 36-41 rule out reporting of any transactions relating to “fails-curing” services offered by CSDs.
    • Paragraph 43 rules out the need to report any transactions associated with Target 2 Securities Auto-Collateralisation.

    The guidelines also clarify the exclusion of the need to report under SFTR in relation to: Retail client lending (except when it is against an irrevocable trust), private banking & Lombard loans, syndicated lending and other corporate lending for commercial purposes, intermediate give-ups and take-ups (in the execution & clearing chain) and transactions involving emission allowances.

    In further points of clarification:

    • Buy-sellbacks and Sell-buybacks should be reported as such with the appropriate master agreement detail where applicable (overruling the original SFTR regulation) (paragraph 61).
    • Margin Loan reporting only applies to Prime Brokerage business (paragraph 11).
    • Modifications that are agreed but have not taken place should not be reported until the actual modification takes place (paragraph 117).
    • Margin loans – where the value of an existing margin loan hits zero, the transaction should be modified (MODI action type) rather than terminated (ETRM action type) (paragraph 83).
    • Securities lending and borrowing transactions can only involve a single ISIN being transferred between a given pair of counterparties (paragraph 65).
    • Backloading: ESMA advises that they like the idea of reporting all open and term transactions executed prior to the date of application whether they meet the requirements for backloading or not. This approach is seen as operationally simpler for many reporting parties and provides authorities with greater information in relation to variation margining (paragraphs 167-170).
    • When trading with sub-funds, each sub-fund should be treated as a counterparty if they have their own LEI (paragraph 52)
    • For cleared SFTs, each SFT between the CCP, its clearing members and the clients of those clearing members should be treated as separate SFTs with different UTIs (paragraph 53).
    • In relation to Repos, collateralised loans in more than one currency constitute separate SFTs. This doesn’t preclude a single SFT having collateral denominated in multiple currencies though
    • Small & medium sized non-financial counterparties trading with a non EU third country entity must either trade with an entity that has been granted equivalence (in which case there is no reporting obligation under SFTR), else they will need to delegate or self-report the transaction/s (paragraph 93).
    • Execution by a branch was clarified to cover the following: a) for a client in accordance with a discretionary mandate given to it by the client; b) where the branch has supervisory responsibility for the person responsible for the investment decision concerned; c) where the branch has supervisory responsibility for the person responsible for execution of the transaction; d) where the transaction was executed on a trading venue or an organised trading platform located outside the Union using the branch’s membership of that trading venue or an organised trading platform (paragraph 102).
    • Counterparties should not report the LEI of the CSD in which they are either a direct or indirect participant (paragraph 122) in the CSD participant field.
    • ESMA acknowledged that updating valuations of securities on loan or used as collateral may not be possible where pricing becomes stale. This can affect suspended shares and some illiquid fixed income securities. In these instances, reporting parties should use contractually agreed values and only update them if new price information becomes available (paragraph 155).
    • ESMA advises counterparties should always use official sources for CFI codes. Those who felt that it would be sufficient to just populate the first 2 characters are likely to be disappointed as ESMA states that X should only be used when a character is not applicable (paragraph 163).
    • Non-bank entities are permitted to start reporting earlier than their date of application if they find it easier (paragraph 188).   

    The consultation also contains an extensive set of sample reports for many different scenarios, detailing how each of the 4 reporting tables should be populated. Once we’ve had the opportunity to review these samples and the latest trade repository validation rules, we will produce a follow-up blog.

  • In the news: Jonathan Lee speaks to BobsGuide

    In the news: Jonathan Lee speaks to BobsGuide

    Our Securities Financing Transaction Regulation (SFTR) reporting specialist Jonathan Lee recently spoke with Rebekah Tunstead at Bobs Guide to highlight the pressure that tier one banks are putting on trading venues to provide a much more compliant SFTR confirmation file from the beginning. 

    “Pretty much everyone in the chain is looking for ways in which to cut costs and to some extent pass on the onus and responsibility to others. Even among the tier one banks, they are looking to trading venues that will provide more of the reportable field in the appropriate format such that they don’t need to collate and process that data themselves,”  Lee says.

    Read the full interview.

  • ESMA updates Q&A on MiFIR and EMIR reporting

    ESMA seemingly delivered a double whammy on 4 February with the publication of Q&As for both MiFIR and EMIR data reporting. However, there’s nothing to get too excited about, although firms do need to understand the ‘clarification’ and adjust their reporting accordingly.

    Impact on MiFIR data reporting

    Bit of a damp squib. There is only one question that relates to transaction reporting (TVTIC on complex trades); the others all relate to RTS 23/MAR reference data reporting. The clarifications can be summarised as follows (italics indicate direct quote from the Q&A):

    How should the TVTIC (field 3 of RTS 22) be populated in transaction reports of a complex trade?

    Bit of a change here. Previously, firms were required to put the same TVTIC on each leg of the reported trades (if they were traded on a trading venue). New instruction is to use the TVTIC provided by trading venue for each leg of the complex trade (where the trading venue uses multiple TVTICs)

    How should Field 15 (Maturity date) of Table 3 of the Annex to RTS 23 and related MAR RTS and ITS be populated in case of trading in bonds after their originally intended maturity date?

    “For bonds that were not paid out on the originally intended maturity date (and therefore have not expired, because, for example, they defaulted), the maturity date should be set to 9999- 12-31 …until they are finally paid out, in which case the maturity date should be updated with the actual date of redemption”.

    How should field 15 (maturity date) and field 24 (expiry date) of Table 3 of the Annex to RTS 23 and related MAR RTS and ITS be populated, if these dates are non-trading dates, e.g. a weekend or a bank holiday?

    “The maturity date/expiry date defined by the issuer or the prospectus of the financial instrument should be used. No adjustment should be made to the next or previous working day for the purpose of instrument reference data reporting.”

    When should an instrument be terminated in FIRDS?

    “When field 12 (termination date) of Table 3 of the Annex to RTS 23 and related MAR RTS and ITS is initially left empty, the reporting entity is expected to fill it in when the instrument is going to be terminated. This also includes the cases when the given instrument has matured/expired, i.e. where fields 15 (maturity date) or 24 (expiry date) are applicable to the given instrument and are populated in the report.

    The termination date should be earlier than or equal to the maturity/expiry date in the cases where the maturity/expiry date is populated.”

    (RTS 23)What action should be taken by the operator of the trading venue or the systematic internaliser in the cases where the LEI of the issuer cannot be obtained?

    Tell the issuer that they should get an LEI (!!!).


    Impact on EMIR Data Reporting

    There are only three clarifications in the EMIR data reporting Q&A – the first two are amendments to previous trade reporting questions whilst the third is a brand new question:

    Q34 – Reporting of contracts with no maturity date (e.g. CFDs);

    ESMA simply reminds firms that they can also report new trades for instruments with no maturity date with an ‘Action Type’ of ‘P’ (“position component”) if it is to be included in a position level report on the same day. This is in line with previous comments from ESMA.

    Q38 – Trades terminated before the reporting deadline

    All trades must be reported even if they are terminated before the reporting deadline and ESMA is simply clarifying that these reports could also be made with an Action Type of ‘P’ if the trade is to be included in a position level report, on the same day.

    Q50 – Reporting of Confirmation Means

    ESMA states:

    The value ‘N’ (not confirmed) should be used either when:

    • The derivative has to be confirmed by the counterparties but has not been confirmed yet;
    • The derivative does not have to be confirmed by the counterparties because it has been traded on a trading venue and once traded all the terms of the contracts are known and agreed by the parties.

     In other cases, the counterparties should report the ‘E’ or ‘Y’ value for this field depending on the confirmation means used (electronic or non-electronic).

    I think this is the one element in the new Q&As that may surprise some firms as it clearly states that trades on a trading venue should have a value of ‘N’.

    So, not a lot really going on with the new Q&As. It is tempting to think that little news is good news. Personally, I don’t subscribe to this point of view; I think there is still plenty of grey in there that would benefit from further clarification, which is natural given the fundamental changes brought in by MiFIR. I also think there are a few elements in the Guidelines that, with hindsight, could have been better – (equity swaps is my favourite bugbear today).

    If you have a burning MiFIR or EMIR reporting question keeping you awake at night, why not contact us at Kaizen.

  • Santa’s SFTR gift extends to EMIR

    Santa’s SFTR gift extends to EMIR

    Santa delivered the long-awaited SFTR technical standards just in time for Christmas to delight SFTR specialists everywhere. But there also appeared to be something at the bottom of Santa’s sack for EMIR trade reporting specialists because the SFTR implementing technical standards also amended the EMIR trade reporting ITS. However, now we’ve taken the wrapping paper off this present, there doesn’t seem to be anything of value inside…

    No real change

    The reference to “Implementing Regulation (EU) No 1247/2012” seems curious as this is the old ITS that has already been amended by the shiny new Implementing Regulation (EU) 2017/105. Putting that aside, the changes appear meaningless. In a nutshell, the only taxonomy that can be used to classify an instrument is the CFI (as the ‘UPI’ alternative doesn’t exist and wouldn’t be a classification taxonomy if it did exist). This is not a real change as ESMA’s validation scheme already ensured only the CFI could be used – NB: the validation scheme is a really (under)handy mechanism to tweak the technical standards without having to bother with tiresome process.

    Annoyingly, Annex II of the SFTR ITS replaces Annex to the EMIR trade reporting ITS (Regulation (EU) 2017/105 rather than the stated (EU) 1247/2012). This is a tricky case of spot the difference – even the amusing typos in the formats of the ‘Collateral portfolio code’ and the ‘Trade ID’ have been persisted. The only changes I could find were on ‘Product classification type’ (only ‘C’ for CFI allowed), ‘Product classification’ (has to be a CFI) and the UPI is no longer referenced as a possible ‘Underlying identification type’ or ‘underlying identification’.

    SONIA

    At a micro detail level, I was disappointed that SONIA wasn’t allowed to join the floating rate index club, despite being set to become a key benchmark. The publication of the ‘new’ ITS annex might have been an ideal time to add it to the list of permitted codes for floating rate indices alongside other key benchmarks such as JIBAR and BUBOR. As a paranoid Briton, I like to think of it as a slight against UK standards, but maybe we were nebulous in just not asking for it. Still, it might be a good one for firms to remember if they ever get lectured by the regulators on the importance of putting “EONA” in their floating rate fields instead of “EONIA”.

    We will be providing EMIR trade reporting half-day training courses from early next year.  Please contact us to register your interest and for further details. 

  • SFTR: The final countdown

    SFTR: The final countdown

    UPDATED 18 December with additional links and further details on timelines for trade repository reconciliations for certain fields.

    Now that the ITS and RTS have been released, we have greater clarity on the nature of the European Commission standards for SFTR as well as the timelines. Our SFTR specialist Jonathan Lee highlights the key changes and the timeline for implementation. 

    On Thursday 13 December 2018, the European Commission (EC) adopted Regulatory Technical Standards (RTS) and Implementation Technical Standards (ITS) covering Article 4 ‘Transparency of SFTs’ reporting requirements under Securities Financing Transaction Reporting (SFTR). This critical step puts the wheels in motion for SFTR to become a live reporting obligation and sets an increasingly clear timeframe for the reporting to start from April 2020.

    Official links: EC RTS, RTS Annex 1, and EC ITS and ITS Annex 1 and RTS for Trade Repositories (TR), RTS for TR Annexes and RTS for Access to details of SFTs held in TRs.

    SFTR go-live timeline 

    The RTS and ITS have been subject to some minor revisions since the ESMA publication, therefore we can confirm that it will be subject to a three month scrutiny period by the European Parliament & Council (not the one- month period for an unchanged RTS, nor the six-month period for an RTS subject to significant, material change). Following this scrutiny, it will be published in the Official Journal of the European Union.

    The timeline from here is as follows in the graphic below, although experience tells us to leave approximately one month leeway around these dates:

    SFTR reporting timeline infographic
    Click image to enlarge

    Changes to the RTS

    While this announcement was much more about certainty of timing (after an extended delay), enabling European SFT counterparties to plan and budget for implementation, nonetheless there are some changes of note relative to the 31st March 2017 ESMA text. We can confirm that:

    1. It will be possible to include agent lenders on repo trades.
    2. There is a not-applicable option on termination optionality for repo and securities lending trades.
    3. There is more substantive guidance on the Unique Trade Identifier (UTI) creation waterfall (see Article 3, page 4 of the ITS).
    4. Timelines for Trade Repository reconciliations for certain fields have changed. The following fields in the Transaction Data table Loan section: Security quality, Maturity of the security, Jurisdiction of the issuer, LEI of the issuer and Security type  – have been brought forward to Day 1. They were previously Day 1 +24 months in the 2017 ESMA text. This will present a more pressing data quality challenge. As a small concession in Transaction Data Collateral section: Collateral unit of measure, Price currency, Price per unit and Collateral market value have been pushed back from Day 1 to Day 1 +24 months. This brings the importance of independent reference data testing to the fore. 
    5. Finally and perhaps most significantly, any bad blood between the EC and ESMA over the adoption of UTIs and branch LEIs appears to have ended. The EC has stated that that once standards are finalised and considered suitable for the purposes of reporting SFTs, the regulation will be amended accordingly. In the interim, ISO codes should be used to identify branches and bilaterally agreed UTIs should be used to identify SFTs.    

    We can help you put the right controls in place

    As we look forward to the festive season and find time to step away from all this talk of SFTR, we would encourage you to ensure that projects are now underway. Now is the time to start SFTR budgeting, hiring, planning, building and thinking about testing, controls and governance if your project has not already begun. 

    Need some help with your SFTR reporting implementation? Contact us for a consultation to find out how you can put the right controls in place to ensure accurate and effective reporting from day one. We are also rolling out an SFTR training course early in 2019 so again, please get in touch to register your interest or find out more.

  • Deep into the soul of regulatory reporting in 2018

    Deep into the soul of regulatory reporting in 2018

    We look back at the regulatory reporting year that was through the songs of Aretha Franklin (sorry Aretha).

    We saw yet another true legend sing her last note this year as the world stood United Together and said a fond farewell to the awe-inspiring Aretha Franklin. We apologise to any fan and most importantly to the great lady herself as we look back at the key regulatory reporting developments of 2018 through her songs and lyrics. I am afraid we have not learnt from our 2016 Bowie travesty….

    MiFIR transaction reporting go-live

    This time last year many of us were running through go-live lists rather than Santa lists and thinking, “I’m going to Drown in my own Tears“. However all that hard work did pay off and all involved deserve their very own Dr Feelgood feeling for their efforts. On the whole, firms got across the line despite the headwinds that presented themselves in the form of instrument data issues (FIRDs / DSB teething issues, understanding TOTV implications, identifying reportable indices), missing LEIs, rogue validation rules at ARMs and the regulator (to mention just a few).

    Though what January really signaled was the beginning of the journey and not the end. Firms’ efforts in the first months of the year were focused on reporting as much of their business as possible and dealing with the inevitable spike in validation breaks from the ARMs and competent authorities. Now the equally hard part of putting in controls to comply with RTS 22 Article 15, to check that what is reported is accurate and complete, before the regulator does, is the new priority.

    ESMA has been very busy

    We always say that regulatory reporting is the gift that keeps on giving, but ESMA can be a little like your eccentric Aunt Vera in delivering something you didn’t ask for and didn’t really want. Well, Vera has certainly been busy this year.  We had new iterations of the EMIR Q&A from ESMA on 12 July and 26 July. And since MiFIR reporting went live on 3 January, we had updates to the Q&A on 25 May and 26 September and some tweaks to the validation schemes as well.

    To be fair to ESMA, we haven’t had the avalanche of information overload we experienced in 2017 and the Q&A mechanism is an essential tool to help bed-down the new reporting regimes so we are Willing to Forgive. Whilst change can often be painful, you can always rely on Kaizen to ensure our ReportShield™ testing reflects the very latest gift from ESMA to keep you One Step Ahead.

    The FCA and SMCR

    When it comes to the Senior Managers and Certification Regime (SMCR) regime it is plain for all to see that the FCA is expecting firms to demonstrate some Respect. In the coming year, the regime will be extended to the core SMCR firms under which an individual within a firm will be ultimately responsible for ensuring that a firm complies with the conduct rules and expectations. Being able to evidence their firm’s reporting is accurate and complete will be a key demand from those who hold this responsibility.

    SFTR

    Having published its Final Report: Technical Standards under SFTR and certain amendments to EMIR back in March 2017, ESMA and the market anticipated that by December 2018 this would be a live reporting regime for investment firms and credit institutions (banks). All that was needed was European Commission endorsement and the legislative steps that follow….

    The European Commission had a Think and after 15 long months eventually piped up I Knew You Were Waiting in late July 2018, albeit with a long list of proposed amendments; largely semantics. Unfortunately, the Commission also decided that A Change is Gonna Come in reference to the rights that ESMA claimed to govern UTI and branch LEI standards endorsement. They left it with ESMA, Call Me.

    ESMA responded to the proposed amendments in September 2018, but unfortunately, it was not with Amazing Grace but rather a dismissive ‘Non,’ rejecting all the changes. The ball is now firmly in the European Commission’s court and as for the bickering, we’re sure It Hurts like Hell but to date, they have not yet found a Bridge Over Troubled Water and endorsed a final RTS for European Parliamentary and Council scrutiny. May the market sing Oh Happy Day when ESMA and the EC stand United Together and we get some certainty over the timing of SFTR go-live.

    Trade reporting and Jumpin’ Jack Flash

    So quite like Jumpin’ Jack Flash, trade reporting for MiFIR started on 3 January 2018 like a cross-fire hurricane with levels of uncertainty and clarity over different aspects of the regulation and the whole market frowned at the crumbs of a crust of bread at the quality of data.

    Firms howled at the morning driving rain with the barrage of Q&A updates throughout the year but as mentioned previously, this has certainly helped bring clarity to many grey areas within the regulation.  DVC, LEI and SI regime delays helped investment firms that felt drowned, washed up and left for dead by the various regulatory demands placed on them.

    What does 2019 hold for us?  The derivatives systematic internaliser regime. Could we start to see a penalty or sanction regime set out by ESMA and the NCAs which could leave investment firms crowned with a spike right through my head?  Questions still do remain though as to whether transparency and a level playing field has really been achieved…

    A view from across the Atlantic

    The CFTC has also been busy in 2018. Two White Papers published suggest that in these Ever Changing Times it is necessary to refresh the Dodd Frank(Iin) Act.

    The first paper, ‘Swaps Regulation Version 2.0’ sets out new proposals to change reporting to a T+1 model and bring in more detail to collateral data requirements. The second paper, which had us singing Border Song, sees The Weight of regulatory burden somewhat lifted for non-US entities where risk is sufficiently monitored by their home regulations.

    No official new rules or timeline has been given yet but we hope the CFTC will Get It Right when legislation is published. We’ll work with our clients to Jump To It and make the necessary preparations when the time comes.

    Brexit – I say a little prayer

    As we approach the end of the year the shadow of Brexit looms large for everyone.  We will share our thoughts on the impact on reporting early in the New Year but in the meantime, season’s greetings from all of us at Kaizen and we wish you a restful break with your family and friends. We thank you for your continued support and we look forward to helping you feel Rock Steady about your reporting quality in the New Year and beyond.

    If nothing else, we hope you have enjoyed listening to some fantastic and enduring classics…you can listen to our Spotify playlist here.

    With thanks to Kaizen Reporting’s industry leading reporting experts for their contributions. Dario Crispini, David Nowell, James Mooney, Jonathan Lee and Chris Machin.

  • How was it for you? Take our survey on the EMIR RTS changes

    How was it for you? Take our survey on the EMIR RTS changes

    Share your views 

    It’s a year since the revision to the EMIR Reporting Technical Standards (RTS) went live*. The resulting changes were fundamental including a significant increase in the number of reportable fields (from 85 to 129), significant changes to taxonomies, and additional asset class specific fields. Many participants struggled with implementation, particularly as there were competing compliance projects, including preparation for MiFID II transaction reporting, on-going at the same time.

    We’re a nosy bunch at Kaizen and we would love to hear your views on last year’s EMIR RTS changes and how valuable you feel the data is to the regulators.  Please head over to our short survey to have your say.  All responses are anonymous.

    *OK, the trade repositories implemented the changes on the Monday, but technically they were intended for implementation on 1 November 2017.

     

  • Swaps get swapped. Changes to reporting of FX swaps under EMIR leaves us scratching our heads

    Swaps get swapped. Changes to reporting of FX swaps under EMIR leaves us scratching our heads

    As nerdy as it sounds, updates to ESMA Q&As are usually an exciting time here at Kaizen HQ. They give us fresh ideas for new tests to code up or clarity on topics that we were scratching our heads over. The newest addition however, TR Question 49 – Reporting of FX swaps under EMIR, has left us quite baffled and asking more questions than we had before.

    Since reporting go-live it has been market practice to report the two legs of an FX swap separately. This is true for all G20 regimes, not just EMIR. In FX trading systems, it’s common to book the two forwards separately, confirm them separately and settle them separately rather than book them as an actual swap. With this, it’s understandable why it has become the industry standard to report them this way.

    A new method of reporting swaps

    TR question 49 has flipped this on its head and is requesting firms to report both legs under the same Trade ID. This will mean that for firms with multiple reporting regimes two separate processes will need to be created to report the same trades. The long term goal of regulators globally should be to work towards a harmonized way of reporting. The new guidance feels like a step away from this ideology.

    Reporting of lifecycle events also becomes far more complicated. When one leg of the swap is compressed or terminated, the remaining leg transforms itself into a forward and needs to reported as a brand new report with a separate report.

    From a revenue perspective trade repositories could find themselves feeling a bit short-changed. Many trade repositories charge per trade. If the industry does manage to become compliant with the new way of reporting it would mean significantly less data reported.It’s also important to consider what hasn’t been written in the Q&A. Nothing has been mentioned about what firms should do with the billions of swaps that have already been reported. Surely it would be impractical to expect these to be back reported?

    Timing will harm data quality

    Generally, when new Q&As are published the guidance is effective as of immediately. For this, firms have been given a year to adapt to the new method of reporting swaps. Nothing in the validation has actually changed though, this means that nothing prevents firms from making the changes earlier or not making the changes at all. As a result, different firms will change at different times and this will be harmful towards pairing and matching figures.

    At Kaizen we’re all in favour of having clear rules on how trades should be reported. This is the only way data can be consistent and of high quality. This Q&A certainly meets this criterion but the thing that is surprising is that only selective consultation appears to have taken place in producing these guidelines. Unfortunately, this is something we’ve seen ESMA do before. Surely a better way to get everybody on the same page is to make writing them a collaborative effort.  Having proper time to test and provide feedback before new rules are officially published is considered a pre-requisite by many firms to meet the reporting requirements.

    We don’t believe anyone responsible for EMIR trade reporting is deliberately trying to shirk their responsibilities, but when surprises like this keep happening it’s no wonder that firms become blinded by change and can’t report correctly. 

    If you need help in adapting your EMIR trade reporting to the latest changes or for a discussion about your EMIR reporting quality, please contact us. 

    /fx-swaps-get-swapped-emir/

  • SFTR: ESMA dismissive of proposed amendments from European Commission

    SFTR: ESMA dismissive of proposed amendments from European Commission

    ESMA have now published their opinion on proposed amendments to SFTR technical standards. This mirrors the letter that they published, sent to the commission on 4 September.

    ESMA dismiss outright the proposed changes made by the European Commission, citing the importance of the original text and the limitations of the Commission’s proposed alternatives. ESMA are adamant that they must continue to include LEIs, ISINs and UTIs in order to be consistent with EMIR and international developments in global standards (Branch LEIs and UTIs). They also state the desire to “Future Proof” SFTR.

    It is fair comment to suggest that some of the EC proposals did water down some of the ESMA proposed data standards for SFTR and that ESMA have made a number of valid points. If ESMA had decided to carry through these proposals then it was likely to introduce some confusion over the timely adoption of UTIs (without which trade repository pairing and matching would have become an even greater challenge). It was also likely to slow the international adoption of branch LEIs. 

    All in all, this would appear to be much ado about nothing. The changes (or lack of changes) from the original “Final RTS” published by ESMA on 31st March 2017 will not have any material impact on the SFTR delivery. It is just unfortunate that the pragmatic steps that the EC proposed to incorporate the option of including agent lenders on repo trades and in providing a not-applicable option for termination optionality on repo and securities lending trades will also be omitted.

    In practical terms, there is likely to be a few additional weeks of delay to the publication of the SFTR RTS into the official journal of the European Union as negotiations between ESMA and the EC continue. The EC could potentially overrule ESMA on some of these matters. This delay is likely to push out the go-live for SFTR reporting further into Q1 2020, starting with the banks & investment firms.

    For a consultation on your SFTR reporting preparation, please contact us.

  • Tales from the crypt – the great cryptocurrency derivatives EMIR reportability debate

    Tales from the crypt – the great cryptocurrency derivatives EMIR reportability debate

    Cryptocurrencies are often seen as a great way to get rich quick, or poor quicker. To be honest, if I wanted to lose a shed load of money, I’d much rather nip down the bookies and put it all on Tripod Lad to win the 3:30 at Kempton Park. Whilst it might fall at the first fence, at least I would have some idea about the mechanics preventing it reaching the winning post. However, my approach to losing money is looking increasingly old school. It appears that there’s nobody left on the planet who doesn’t know somebody holding a fraction of a bitcoin in the hope that it will miraculously increase in value enough to put their grandkids through university.

    So, how worrying is the rise of the derivatives on cryptocurrencies? Well, we’ve certainly seen extreme volatility in this asset class, commonly attributed to investor behaviours of herding and regret-aversion. Does this create systemic risk? Well, it’s tempting to believe this asset class isn’t mature enough yet to represent a risk to the entire financial system. However, the launch of exchange traded derivatives on cryptocurrencies has led to involvement of increasing numbers of systemically important financial institutions in this asset class. The CFTC Chairman J. Christopher Giancarlo has warned whilst cryptocurrency derivatives are a relatively small market in terms of systemic risk, it is one that the CFTC needs to watch carefully.

    So, we hope this is a development the EEA regulators are also watching carefully. Surely this is one of the good things about EMIR trade reporting – ESMA and other EEA regulators will have had 6 years of analysing cryptocurrency derivatives to assess whether they could have the potential to grow and become a new threat to financial stability. Or have they? Possibly not, as there is a great deal of confusion in the industry as to whether cryptocurrency derivative instruments are actually reportable at all under EMIR. Whilst some firms have decided to trade report them to trade repositories, others have not. The confusion stems from the definition of reportable derivatives. EMIR takes this definition from MiFID and the FCA has explained that whilst cryptocurrency derivatives are “capable” of being financial instruments under MiFID II, it does not consider cryptocurrencies to be currencies or commodities under MiFID II. This is unfortunate as it leaves firms with the added dilemma that if these derivatives are EMIR trade reportable, exactly how should they be reported. Those firms that have chosen to report have taken the decision to report as commodity derivatives; mainly because the ESMA validation for currency derivatives requires an official ISO currency code and cryptocurrencies do not have one.  However, it is debatable whether reporting cryptocurrencies as commodities will deliver much value to the regulators as they will not be recognisable as cryptocurrencies from the report. Maybe the perfect opportunity to address this issue would have been through the fundamental changes to the reporting technical standards implemented in October 2017.

    The reporting of cryptocurrency derivatives may be one of the “known unknowns” in EMIR reporting. However, there are many known reporting errors in EMIR trade reporting that make it through the ESMA validation scheme. Just because a trade repository has accepted a report doesn’t mean it is error free. Some firms consider EMIR trade reporting to be a “fire and forget” reporting regime apparently forgetting the obligation for “complete and accurate” reporting so long as “T+1” is achieved. However, ESMA’s 2017 Annual Report and 2018 Work Programme makes it abundantly clear that the quality of data reported to TRs is not good enough and needs to be improved.

    How good is your EMIR trade reporting? Our ReportShield™ quality assurance service delivers an independent and comprehensive analysis of the accuracy and completeness of your EMIR trade reports. For a consultation with one of our experts, please contact us.

  • ESMA updates its validation rules (again)

    ESMA updates its validation rules (again)

    Just when you thought it was safe to set out on holiday with no more reporting changes to worry about, ESMA announced some changes to its EMIR trade reporting validation rules on 9 August.

    On first glance, the changes appear fairly innocuous with only five fields impacted:

    • Reporting Timestamp; 
    • Reporting Counterparty ID;
    • ID of the Other Counterparty; 
    • Underlying Identification; and  
    • Confirmation means.

    However, no change to reporting is ever easy for firms or trade repositories (TRs). Although an implementation date of 5 November 2018 gives the industry some time to prepare, it is surprising that the changes come without any warning or consultation. They also come without any explanation of their value to the regulator. This is frustrating as good regulation should result from a robust cost benefit analysis and the industry is going to struggle to understand the benefit of some of these changes.

    Let’s take the first change – the ‘Reporting Timestamp’: “The reporting timestamp should be equal or earlier than the timestamp of the receipt of the report by the TR. The date part of the timestamp cannot be earlier than the day preceding the date of the receipt of the report by the TR. The receipt of the report should be understood as the moment the report enters a TR’s system.”

    This is probably the biggest change to the industry as many trade repositories don’t ask for firms to populate this field, as the time the firm reports should be exactly the same time the TR receives it. If the TR doesn’t auto-populate this field, it appears to introduce the possibility of error by asking the reporting firm to populate the field itself. If the TRs were to incorrectly populate the reporting timestamp, it would be challenged by the reporting firms, so the regulators would appear to be trying to fix something that isn’t broken.                 

    The validation changes to the ‘Reporting Counterparty ID’ and ‘ID of the other Counterparty’ shouldn’t present too many issues as they are both relaxations of the validations. In each case the LEI can have a status of ‘lapsed’ or ‘retired’ where the ‘Action Type’ is ‘C’ (for ‘early termination’), and the LEI no longer has any check on the ‘registration status’ where the Action Type is ‘E’.

    The validation changes to the ‘Underlying identification’ appear to be both pointless and risible. The first element allows the special characters of hyphen and full stop where the ‘Underlying identification type’ is ‘A’ for Aii. It is pointless because the Aii code can no longer be used in the ‘underlying identification’ field post MiFIR implementation and it is laughable as the hyphen has always been an integral part of the Aii (i.e. the ESMA validation would have prevented the underlying Aii being reported correctly). The additional characters are also allowed where the underlying identification type is ‘B’ (for ‘basket’) – this would cause issues as the hyphen is also used as the separator for the individual components of a basket.

    The final change impacts the ‘Confirmation means’ field which now stipulates that: If field 2.15 [Venue] is populated with a MIC code other than “XXXX” or “XOFF” and field 2.35 [‘Cleared’]is populated with “N”[Not cleared], this field shall be populated with “N”[non-confirmed]. This is sensible and is one of the tests that Kaizen already includes in our EMIR trade reporting quality assurance testing.  We apply more than 450 tests to EMIR reports to check if the data contained within them is accurate.  Our clients can also take advantage of a new Kaizen service which offer clients the opportunity to pre-test their compliance with the new validations through a tool that replicates the ESMA validation scheme.

    For further details on our pre-testing validations service and other Kaizen quality assurance services please contact us.

  • SFTR: If you can’t beat ’em, join ’em…

    SFTR: If you can’t beat ’em, join ’em…

    In the first of a two-part blog, our newly appointed SFTR reporting expert Jonathan Lee looks at the background and context of the Securities Financing and Transactions Regulation. 

    The author of this blog is about to take an “If you can’t beat ‘em, join ‘em” approach in following our European regulators into their summer recess. The European Commission publication freeze will shortly kick in and the probable timeline for publication of the final Regulatory Technical Standards (RTS) for Securities Financing Transaction Reporting will be held back until September this year at the earliest. This in turn will result in SFTR Article 4 Reporting delayed until Q1 2020 for banks and investment firms, with market infrastructures, fund managers and large non-financial counterparties to follow at subsequent three month intervals.

    Waiting a little longer…

    Many of us working closely on the new Securities Financing Transaction Reporting European regulatory regime have been on tenterhooks ever since the publication of ESMA’s Final Report on Technical Standards under SFTR in March 2017. Indeed, the initial guidance was that the European Commission would decide whether to endorse the technical standards within three months of that date and for reporting for banks and investment firms to follow approximately 15 months later (September/October 2018). We have now slipped approximately 15 months from this original target date. Nevertheless, as September approaches, we are likely to finally have some report timing finality.  

    Securities financing influence is high 

    The premise for SFTR reporting has always been a little different from the mainstream reporting regimes exemplified by MiFIR, EMIR, Dodd Frank and so forth. Securities Financing markets are less widely understood and often seen as a market utility or service offering rather than a mainstream ‘risk’ market. Nevertheless, of the four markets covered by SFTR (Repo, Buy-sellback, Securities Lending and Margin Lending); EUR 7.25 trillion contracts were recorded as outstanding within the scope of the highly respected ICMA ERCC Semi-Annual European Repo market survey (for Repo markets alone) in December 2017. The ability of securities financing markets to influence leverage, liquidity and overall global systemic market function is high.

    Financial crisis

    SFTR Regulation (November 2015) stems from the financial crisis. Repo and other securities financing markets were seen at the centre of aspects of the crisis, perhaps most notably in the collapse of Lehman Brothers (September 2008). Concerns over shadow banking, the lack of transparency, build-up of leverage, interconnectedness and pro-cyclicality inspired much debate and discussion among G20 members from 2011. This culminated in FSB reports on Shadow Banking in October 2011 and further FSB reports specific to Securities Lending and Repo from April 2012 onwards. SFTR itself sets out to enact the FSB 2015 report “Standards and Processes for Global Securities Financing Data Collection and Aggregation.”

    The greatest challenge of SFTR is the extent to which European regulators seek to ‘gold plate’ the global guidelines. The Financial Stability Board (FSB) stipulates the need for retrospective, periodic, single sided, settled position level reporting that can readily be aggregated regionally and globally. The European regulation sets out the need for very granular, daily, two-sided, trade and lifecycle event level reporting. Invariably, this is going to be very challenging to implement, manage and control by reporting parties and perhaps equally tricky for regulators to interpret, comprehend and aggregate.

    Implementation of SFTR and data quality implications will be covered in a second blog from Jonathan early next week.

  • Tell me LEIs

    Tell me LEIs

    The six-month grace period granted by ESMA for reporting firms to obtain Legal Entity Identifiers (LEIs) ended earlier this month. At her recent speech in Paris, ESMA’s executive director, Verena Ross, marked that the ‘No-LEI-no-trade’ rule now forces entities trading in EU markets to have an LEI. This allows the regulator to know exactly who is trading and enables market data to be aggregated in a more accurate manner. Verena Ross also recommended that regulators across the globe follow suit and make similar mandates.

    Someone from the HKMA must have been listening, because on the same day as the speech they announced their intention to extend regulation on the use of LEIs. From April 1st 2019, reporting entities, HKTR members, CCPs and clearing service providers must report all new trades with LEIs. Parties that do not identify themselves in the ‘Reporting for’ field and updates to existing trades will not require LEIs just yet. Similar to ESMA’s grace period, reporting entities are expected to have a process in place to request their clients obtain an LEI.

    Our research shows that of the 250 or so HKTR members, 90% of them already have LEIs. Alongside this, DTCC noted in their feedback to the proposal that some 4,200 HK based entities already have LEIs. It’s possible that MiFID II has already broken the back of the burden of obtaining LEIs in other jurisdictions.

    LEIs are becoming the industry’s gold standard for trade party identification and they are evolving too. Last year GLEIF introduced level 2 data that gave birth to LEI parent reference data being embedded in the LEI.

    In the future, we hope that LEIs will continue to evolve and that other entity static data can be hardcoded into their DNA. Features like CFTC US person status or Canadian Local Counterparty Status would do the industry a huge favour in terms of getting their reference data correct.

    Reference data errors account for 50 per cent of errors found in our testing of regulatory reports. Our ReportShield™ reference data testing checks both counterparty and instrument reference data for accuracy and completeness including real-time check of LEIs.  Contact us for a discussion on improving the quality of your reference data.

  • ESMA updates its EMIR Q&A

    ESMA updates its EMIR Q&A

    ESMA has published another iteration of its EMIR Q&A (12 July 2018). In his first blog for Kaizen, our Senior Reporting Specialist David Nowell summarises the key elements impacting trade reporting:  

    LEI changes due to mergers and acquisitions

    In TR Question 40, ESMA attempts to close some of the gaps in its previous guidance on handling LEI changes due to mergers and acquisitions. The changes bring obligations on reporting counterparties to inform their TR when their “non-EEA counterparty” has a change of LEI and to request the TR to update the LEI in the “other counterparty id” field for all outstanding derivatives. Whilst this change might initially seem attractive from a regulatory perspective, it clearly brings operational challenges for reporting firms and seems to be an imperfect solution as “non-EEA counterparty” is a poor proxy for firms with no EMIR reporting obligation.

    The new TR Question 40 also clarifies the obligations for firms when they have used an incorrect LEI, either to identify themselves as reporting counterparty or to identify their counterparty (“other counterparty id”). On these occasions, the reporting counterparty should “cancel” the incorrect reports with an action type of “E” and re-report them with a correct LEI and the previously agreed UTI. Some may question whether this guidance is consistent with the technical standards which state that an action type of “E” should only be used for the “a cancellation of a wrongly submitted entire report in case the contract never came into existence or was not subject to Regulation (EU) No 648/ 2012 reporting requirements but was reported to a Trade Repository by mistake…” It also may also be inconsistent with the validation which requires: “After a report with action type “E” is submitted, the only allowed action type to be submitted by the other counterparty, if reporting to the same TR, is “E”. No additional reports shall be allowed for that UTI”.

    New but not new

    The new Q&A marks TR Question 47 as being “new” but, in fact, it isn’t – it is the same text as the previous Q&A published on 29 May. However, some participants may have overlooked this addition and may be surprised by the instructions. We are aware that, for cross currency instruments, some participants presumed that “deliverable currency” should be populated with the code for the currency they would be delivering as reporting counterparty and the common data 61 “delivery currency 2” field should be populated with the code of the cross currency they would receive (as suggested by the technical standards). However, Q&A 47 states that “the Delivery currency 2 field should be populated for those derivatives with an FX component for which two currencies are delivered. If both Deliverable currency and Delivery currency 2 are populated, the field Deliverable currency should be populated with the first currency sorted in alphabetical order.” The industry would certainly benefit from some worked examples of derivative reporting much like the ESMA guidelines for MiFIR reporting.

    When a management company can be considered a counterparty

    ESMA also clarified that there are occasions when a fund management company can be considered to be the counterparty to a transaction. Whilst the client is still generally considered to be the counterparty when a management company enters into derivative contracts when providing a portfolio management service, the new Q&A highlights that the management company should be considered the counterparty when it “bears the risk” of the derivative contract. This principle is also borne out in a new trading scenario (“Case 4: Counterparties in the context of portfolio management) where the portfolio manager is shown to have reporting obligations against both a counterparty and a client where it is deemed to ”bear the risk” against the counterparty.

    Here’s the link to ESMA announcement here.

    Our ReportShield™ quality assurance service ensures the accuracy, completeness and quality of EMIR reporting data. If you would like an assessment of the quality of your EMIR reporting, please contact us. 

  • Measure for measure: ESMA’s assessment of EU-wide supervisory measures for EMIR

    Measure for measure: ESMA’s assessment of EU-wide supervisory measures for EMIR

    Measure for Measure is classed as a comedy yet it is also considered one of Shakespeare’s problem plays as it has aspects of a tragedy. Dealing with the concepts of justice and virtue, the play sprang to mind when reading ESMA’s recently published report on EMIR supervisory measures.

    This is because the report, which runs to some 40 pages, highlights some significant differences in approach by the national competent authorities (NCAs) on supervision and enforcement of EMIR requirements, as well as the fines and other supervisory actions that have been undertaken to date. The report has both good and bad news for financial firms.

    Let’s start with the good: There have only been three fines raised for EMIR breaches to date across Europe. Two of these fines were levied by COVIP (Italy), one for €105k and the other for €60k both in relation to article 9 reporting breaches and article 11 breaches in respect of clearing activities. Within each jurisdiction, the maximum fines that can be levied are almost consistently low.

    And the bad news: the third fine in our list is the eye-watering £35m fine raised by the FCA for the non-reporting of 68 million exchange-traded derivative contracts.  The per-record penalty applied by the FCA was increased because of prior breaches under the MiFID I transaction reporting regime. That points to the FCA treating reporting failures as a single type of breach irrespective of the reporting obligation concerned. In its final notice, the FCA also took the time to highlight that insufficient testing was carried out to ensure the accuracy and completeness of reports as well as weaknesses in oversight arrangements. And in another piece of bad news, the largest potential fine for those countries that have a cap is France’s €100m. 

    Few investigations across Europe

    Perhaps it’s unsurprising, but not all authorities have been active in conducting investigations since the inception of EMIR.  What is surprising is how few investigations have been carried out across Europe when the number of entities, both financial and non-financial, falling within the scope of EMIR is so vast.  We can’t tell the true number of investigations conducted as the “more than 20” category (as shown below) could hold a great many but we would expect ESMA to have stopped there because it was closer to 20 than 40. 

    In terms of investigations carried out, Belgium is the standout performer with more than 20 investigations being run across reporting, clearing obligation, reporting, risk mitigation techniques and Article 11 in respect of Non-Financial counterparties. On the other end of the scale, we have a number of countries that haven’t undertaken any investigations at all including Ireland, Finland, Norway and the Netherlands.

    Number of investigations carried out on the reporting obligation by country in 2017:

    None

    BU

    CZ

    FI

    HR

    IE

    LV

    MT

    NL

    NO

    SI

    1 to 5

    FR

    EL

    SK

    UK

     

     

     

     

     

     

    6 to10

    AT

    DK

    PL

    SE

     

     

     

     

     

     

    11 to 20

    CY

    ES

    PT

     

     

     

     

     

     

     

    >20

    BE

    DE

    LU

    IT

     

     

     

     

     

     

     

    Another piece of bad news (at least for firms) is that we can expect ESMA to push for more harmonisation and more investigative activity.  ESMA and other competent authorities have been concerned with the quality of reporting under EMIR and MiFID. This, combined with the EMIR regime being in its 4th  year and matching rates across repositories remaining challenging, pressure to improve reporting will continue.  Pressure to ensure compliance with the clearing obligation and risk mitigation techniques can also be expected in the coming year.  

    The report also drew attention to the fact that no work seems to have been carried out in terms of the anti-evasion provisions of EMIR.  This would be a complex area to assess but firms should be prepared for questions on this which means having a handle on what guarantees are in place between EU group entities and non-EU entities.

    Penalties across the EU

    The report highlights the approach to penalties as an area where there is a low level of harmonisation. We’ve created the table below which shows the divergence in percentage terms of the maximum caps (France at €100m) and minimum penalties (Bulgaria €40k) across the EU. 

    In the UK and Spain, there is no stated penalty cap. In the case of the UK, a per record penalty is applied which means that the penalty regime scales to the level of reportable activity and degree of non-compliance for the firm concerned. 

    Country

    Percentage of maximum

    Max € (000)

    Notes

    Spain

    n/a

    –

    Variable no stated maximum

    France

    100.00%

    100,000

    Capped at less than 10x gain made or loss avoided

    United Kingdom

    n/a

    –

    Variable no stated maximum

    Finland (articles 4 & 10)

    10.00%

    10,000

    Capped at less than 10% turnover

    Sweden

    5.00%

    5,000

    Now capped at 10% of turnover but figures relate to a decision when the old rules applied.

    Belgium (National Bank)

    5.00%

    5,000

    Capped at less than 10% turnover

    Italy

    5.00%

    5,000

    Capped at less than 10% turnover

    Greece

    3.00%

    3,000

     

    Ireland

    2.50%

    2,500

     

    Poland

    2.50%

    2,500

    < 10% of turnover

    Belgium (FSMA)

    2.50%

    2,500

    Capped at 3x gain made or loss avoided

    Luxembourg

    1.50%

    1,500

    Capped at 5x gain made or loss avoided

    Netherlands

    1.00%

    1,000

     

    Cyprus

    0.70%

    700

    Capped at 2x gain made or loss avoided

    Germany

    0.50%

    500

     

    Czech Republic

    0.40%

    400

     

    Austria

    0.15%

    150

     

    Malta

    0.15%

    150

     

    Latvia (legal persons)

    0.14%

    142

     

    Finland (articles 9 & 11)

    0.10%

    100

     

    Slovenia

    0.10%

    100

     

    Croatia

    0.07%

    67

     

    Latvia (natural persons)

    0.06%

    57

     

    Bulgaria

    0.04%

    40

     

     

    NCA powers across the EU

    NCA powers are relatively consistent allowing them to: summon and interview personnel, conduct on-site investigations and inspect documents. They also all have the power to issue fines, issue binding and non-binding letters whilst some NCAs have the power to issue criminal sanctions against individuals. 

    Actions firms should be taking for EMIR reporting

    Firms should be reviewing their EMIR control environment. This means assessing the more difficult activities of regular accuracy testing, reference data testing and front to back reconciliations as well as ensuring the governance process is robust and up-to-date. 

    Governance arrangements need to be looking at the operation of the reporting process itself, the assurance process around accuracy and completeness of reporting but also the remediation process, ensuring that known issues are being appropriately escalated, prioritised and remediated which includes replaying records to correct historic errors. 

    While we are known for providing accuracy testing and reconciliation services, we also help our clients mature their broader reporting controls with our Control Framework – all are key components of our ReportShield™ quality assurance service. We also, in conjunction with our consultancy partner Elixirr, run remediation programmes to bring firms’ trade repository records into line.  If you would like to discuss your reporting controls please contact us.

    A variation of this article was published by Thomson Reuters Accelus (subscription only) on 20 July 2018. 

  • Baskets, ISINs and bank holidays – ESMA publishes new guidance on EMIR

    Baskets, ISINs and bank holidays – ESMA publishes new guidance on EMIR

    ESMA has been busy updating its Q&As. Last week it was MiFID II and this week it’s EMIR. The newly updated Q&A gives guidance on how some specific fields should be populated and which competent authorities should receive certain data. They emphasise once again that simply passing validations is not good enough; the regulator is expecting accurate submissions.  In this blog, we outline some of the key updates. 

    Maturity date

    If maturity date falls on a weekend or bank holiday this is the date that is expected to be reported and not any adjusted date. From a matching perspective this makes logistical sense as different countries have different bank holidays. As well as this, for trades that have expiry dates many years in the future, bank holidays may not be known at the time of execution. I wonder however, if the trade’s adjusted maturity occurs at a later date than the unadjusted date, if we could see any failures to report some post-trade events that happen in between this period. Should ESMA have provided the same clarity for settlement dates?

    Underlying identification

    The guidance states that if an index does not have an ISIN it should be reported with the name that is identical to the names published by the index provider and include special characters. Trading systems tend to dislike special characters so there could be some circumstances where these are difficult to report. Lucky the S&P 500 has an ISIN!

    Access to data by competent authorities

    If the Cambridge Analytica scandal has taught us anything it’s that people care about who has access to their personal data. The same holds true for business data. Until now the guidance for derivatives where the underlying is a basket or an index has been for TRs to allow access to the data for all EU competent authorities. The new guidance is that authorities will only have access to the data if they share the same country as the ISIN or any ISINs that that basket or index is composed of. Other authorities will be allowed access to the data if they need it to carry out their responsibilities. It’s a well-meaning sentiment but it is a difficult change to implement and there are a lot of questions around this which we will follow up separately.

    Deliverable Currencies

    The new Q&A mandates that deliverable currency should be populated in most cases. Our accuracy testing reveals that this is not usually the case within the industry and repositories generally classify the fields as optional. In order to comply with the regulation some changes will need to be made in participants reporting processes.

    Effective Date

    The last new piece of guidance is that if there is no effective date specified in the contract it should be reported as the same date of the execution of the derivative. This is already fairly common practice in the industry but the guidance does not explicitly mention novation events. In the case of a novation where the contract does not contain an effective date, should it be reported as the execution date of the original contract or the date of step in? You decide … just make sure your counterparty agrees!

  • MiFID II Q&A update: New guidance on complex trades and national ID validations

    We are five full months into MiFID II. Competent Authorities are still experiencing teething issues with the instrument data, validations, response messages and providing reporting firms with extracts of their submitted reports. Firms are increasingly moving their focus from addressing validation issues and handling of response files to looking at the accuracy of their reporting. All parties should be working on the most pressing issues following the 80/20 rule.

    “Firms are increasingly moving their focus from addressing validation issues and handling of response files to looking at the accuracy of their reporting.”

    Working on validations to get all the transaction reports accepted by the regulator may not be the most pressing issue.  Firms can still be reporting 100% of their records inaccurately. It is therefore important that attention is turned away from validations to accuracy testing and identifying the valid but wrong population.

    Whilst there are many areas of reporting uncertainty, ESMA has decided to focus its guidance on strategy trades. Strategy trades are relatively rare in the reporting world and affect only a very small proportion of total reportable activity. 

    This post summarises the new guidance from ESMA.

    Complex Trade ID

    A strategy trade is a trade which is composed of more than one financial instrument or legs, where the execution of the trades are contingent on each other and a single price is given for the strategy contract as a whole. 

    When transaction reporting strategy trades, the Complex Trade ID (field 40), must be populated with a code that links each of the legs. This code must be unique to each strategy trade for the reporting firm. ESMA’s latest update to its Transaction Reporting Q&A on Friday (25 May) provides more guidance on how and when the Complex Trade ID should be populated. 

    The aim of the Complex Trade ID is to notify the users of the transaction report that the instrument reported is part of a broader strategy trade and to enable the user to identify any related transactions.  In the guidance they make it clear that:

    • The price reported is the price of the strategy as a whole not the price of the individual leg being reported.
    • The Trading Venue Transaction Identification Code (TVTIC) should be populated for each reported leg of the strategy. Presumably, this would only apply where the strategy itself was executed on a trading venue and the legs execute as part of that strategy. There is more complexity here and more scenarios which the Q&A does not address.  
    • The Complex Trade ID field must be populated even where only one leg of the strategy trade is reportable. It is still a strategy trade and the price must reflect this.
    • Where the strategy itself is allocated an ISIN you still report the individual legs and not the strategy as a whole.
    • In terms of reference data to be reported for strategy trades, the Q&A makes clear that the reference data for the legs must be submitted, not the reference data for a “strategy instrument”.

    National ID validations

    The only other update in the Q&A relates to the validations published for the national identifiers. We have commented in a previous post as to the complexity the approach gives rise to. This is the second update to these validations that have been published.  The latest is:

    • Czech Republic: “It should be noted that the special character “/” is just a separator and should be omitted in transaction reports.”

    Presumably there have been problems with firms including “/” in their identifiers.

    Kaizen’s accuracy testing checks all MiFID II data fields to ensure your reporting is correct. To find out more about how we can help you avoid the ‘valid but wrong’ problem, please get in touch. 

  • CFTC hints it will follow in ESMA’s footsteps

    CFTC hints it will follow in ESMA’s footsteps

    In the world of derivatives reporting the Dodd-Frank Act (DFA) may be the older cousin of EMIR but if we think about which regime is more mature, EMIR takes the cake. Since the reporting go-live in 2014, EMIR has grown through several different amendments to arrive at where we stand today. Its strict validation requirements aim to provide the data quality that is necessary to measure systemic risk. The CFTC on the other side of the Atlantic has remained relatively quiet since reporting go-live at the end of 2012. That is, until now…

    More complete and accurate data

    The CFTC has published a White Paper which gives a view of which direction the US regulation is heading towards. No awards for guessing that they want ‘more complete, more accurate, and higher quality data’. How can this be achieved? The CFTC is proposing to elaborate on requirements of part 49 to ensure that counterparties and repositories are continuously assessing the integrity of their data and insisting that any inaccurate or missing data is corrected. This can only be achieved if the requirements are clear. In the paper, CFTC admits that part 45 data fields are not well defined and this has led to inconsistent reports which cannot be relied upon for any meaningful analysis.

    The proposal is to take on board the CPMI-IOSCO harmonisation of data elements that were published in April. Amongst others, the report details that LEIs should be mandated to identify counterparties and MICs should be used to identify trading platforms. Sounds quite familiar, doesn’t it? As well as this there is an indication that collateral margin fields will be put in scope for reporting as is the case in EMIR and ASIC jurisdictions.

    Relax of timeliness requirements 

    Further harmonisation is suggested by the timeliness requirements being relaxed to a T+1 model. The philosophy is that if Rome wasn’t built in a day, it won’t collapse in a day either. If firms take the time to agree and confirm the terms of an OTC contract before reporting it, then the data received will be of a higher quality.

    Swaps Regulation Version 2.0 won’t be a complete copy and paste of EMIR though. There is no suggestion that the regime will move to dual-sided reporting and the real-time requirements of part 43, although maybe changing as well in terms of notional capsizes, will remain a unique aspect of Dodd-Frank reporting.

    No exact details or timescales are available yet however we’re pleased to remind our clients that our ReportShield™ accuracy testing service already checks the correctness of these fields under Dodd-Frank, so you can be reassured that you’re already one step ahead of the regulator. Alternatively, if you’d like some assurance that your DFA reporting is accurate, timely and complete, please don’t hesitate to contact us.

  • In the news: Dario Crispini talks LEIs with Funds Europe

    In the news: Dario Crispini talks LEIs with Funds Europe

    Our CEO Dario Crispini spoke to Nicholas Pratt at Funds Europe about some of the challenges of the introduction of Legal Entity Identifiers (LEIs) which are an important component of MiFID II.

    Extract: 

    Each fund managed in Europe has to have a registered LEI and the ESMA has imposed a ‘no LEI, no trade’ rule to underline the importance of the initiative.

    Currently there are 1.1 million LEIs in issue. However, many people think that’s some way off the desired total.

    “I would expect there needs to be a lot more LEIs registered to cover the market,” says Dario Crispini, chief executive of Kaizen Reporting, who has previously worked for the Financial Conduct Authority in the UK.

    Read the full story here. 

  • ESMA’s LEI solution is a Grandma-like gift

    ESMA’s LEI solution is a Grandma-like gift

    Thank you Santa, you have delivered the first wish on our Christmas list –  a solution for firms with clients without LEIs!

    Well…kind of.  ESMA has blinked first but late in its long standing game of Chicken with the industry and today announced it has relaxed its approach on the LEI requirements for reporting entities and issuer of financial instruments.  There was very little wriggle room for ESMA as it has no powers to amend the regulation and instead has had to relax one of the validations and pass on significant operational difficulties to firms and trading venues.

    ESMA recognises industry concerns

    In its statement, ESMA recognises three key concerns of the industry. First, that firms will not succeed in getting LEIs for all of their clients prior to 3 January 2018. At the same time, it acknowledges that these clients will still approach firms to trade with them post 3 January regardless of not having an LEI.  Finally, trading venues will face similar problems with non-EU issuers who will not have obtained LEI.  There is a fourth issue of handling corporate actions for clients without LEIs.  These are issues that Kaizen reflected previously in our blogs and publications and ESMA has now been persuaded by the consequences of the LEI obligations. In short, the LEI mandate would result in a scenario where clients without an LEI have no option but to trade with a US located bank or venue resulting in a material outflow of business from the EU financial system.

    A Christmas gift but not for life…

    ESMA’s proposal is a temporary but messy solution so as not to breach the regulations. For a period of six  months from 3 January, investment firms and trading venues can continue to provide trading services to clients without an LEI that would trigger a transaction reporting obligation. But only if two obligations are met:

    • The investment firm obtains the necessary documentation from the client to apply for an LEI on the client’s behalf
    • The trading venue reports its own LEI instead of the  LEI code of non-EU issuers whilst reaching out to them to get one

    Investment firms will have to apply immediately for the issuance of an LEI on behalf of the client and then submit all required reports for that client once the LEI has been issued.  ESMA and the NCAs accept that this solution will cause a delay in reports being made and they will actively monitor the timeliness of late reports.  At the same time, they will amend their validation rules to allow the acceptance of transaction reports where LEI issuance date is after the transaction reporting execution date.  But the FCA have already communicated that they will not be able to make this change for the 3rd January!

    ESMA and your Grandma

    Like Christmas presents from your Grandma, ESMA’s LEI ‘present’ is well meaning but does not quite hit the spot.  Worse of all, it doesn’t come with a receipt that will allow you to exchange for a better gift. The effect upon firms is a messy one:

    • Outreach: Firms will have to, at short notice, reach out to clients to obtain the required data to register them for an LEI and what happens if the client doesn’t want to play?
    • Register and pay for LEIs: Put in place a process at short notice to process LEI requests
    • First Mover Disadvantage: Those firms who respond first will end up paying for LEIs that then also benefit their competitors
    • LEI Duplication: Although the GLIEF system is meant to prevent duplication of LEI issuance, it will likely face its greatest test as multiple firms apply on behalf of clients
    • Excluding Reports: Firms will have to put in place processes to identify and exclude transactions without LEIs and then report once the LEIs issued
    • NCAs not ready: The FCA have already said they will not be able to make the validation changes in time, meaning that they will reject reports even if they follow process outlined by ESMA
    • ARMs and firms not ready: ARM validations and for some firms their own internal validation processes will have to be altered to allow the historic reports to be submitted with newly minted LEIs.

    So –  not quite the present we all wished for and we may well be left scratching our heads in January wondering how to put it together and make it work.  Fingers crossed we have better luck on our other nine items on our Christmas wish list…

  • MiFID II Q&A updates – an early Christmas present from ESMA

    MiFID II Q&A updates – an early Christmas present from ESMA

    ESMA has, this week, published updates to three of their Q&As on MiFID II which you need to be aware of for your MiFID II programmes as we approach go-live. 

    For transaction reporting, the latest update reiterates how you determine reportability for some specific instruments.  We believe that key amongst these is ESMA’s confirmation that units in collective undertakings and ETFs need only be assessed on the instrument itself and not on their underlying holdings. This point has been outstanding since the original data reporting consultation paper. 

    There are also other updates to Q&As including transparency topics and Market structure topics.

  • Dear Santa…a MiFID II Christmas wish list

    Dear Santa…a MiFID II Christmas wish list

    Dear Santa

    I have been very good this year. I planned my MiFID II transaction reporting project early. I read Levels 1, 2 & 3 (well maybe not all of level 3…). I put enough money in the budget, identified my risks and spoke to my peers.  In short I think I have done everything possible but I still think I might be in a little bit of trouble. So this year for Christmas I have one or two wishes that I hope you can grant so I can start the new year with a cheery grin as big as yours.

    Could you and Ruldolph please drop into my stocking this year:

    1. An LEI for all my clients who are refusing to get one even though I have offered to help many times in doing so.  I do want to keep talking to them next year!
    2. Help trading venues send the fields they need to for me to make my report.
    3. May my ARM be able to onward report to the FCA without any issues.
    4. A bright and sparkling new reconciliation that reconciles all my trades and not just the ones I sent
    5. Change ESMA’s mind and let them agree that the FIRDs list is a golden source of data
    6. Please just make ‘shortselling’ either go away or send me a new magical toy that will calculate it every day and correct it even  after I need to include a trade that was not captured the previous day
    7. Some really clever testing that identifies any of my mistakes so I can tell my Senior Manager Regime (SMR) manager all is well and he/she won’t lose their house
    8. Make all corporate actions involuntary even though they aren’t (our secret, Santa)
    9. Now I have lots of friends from different countries and I would like just one way of identifying them not several.
    10. An Xbox with the latest version of Overwatch

    Now Santa I hope you don’t think me too greedy, but compared to my friends in America and Hong Kong I think I might be in more need for Christmas presents than them.

    I’ll leave a mince pie for you and some carrots for Rudolph . Even if you can send me a few of the items I have asked for, I will be happy and I promise I’ll ask a lot less for next year.

    Love from…
    Little Johnny

    P.S If you can’t do 4 and 7 then please drop this letter over to those lovely people at Kaizen Reporting, I am sure they will be able to help!

  • Q – Who should read the latest MiFIR Q&A?

    Q – Who should read the latest MiFIR Q&A?

    A – Those involved in: portfolio management outsourcing, IPOs, corporate actions and trading of swaps which contain an index.

    ESMA has published its latest version of its Questions and Answers on MiFIR with updates exclusively on the topic of firms’ transaction reporting obligations under MiFIR article 26 and ESMA RTS 22. There are four questions raised, each marked with the update date of 14 November 2017.  Here we briefly explore the key points of each question and answer.

    Q7: How should transactions be transaction reported where portfolio management has been outsourced? (page 33)

    ESMA provides a new detailed scenario and answer to the question in the form of diagrams, example reports and narrative explanation. In this scenario, where firm (B) is outsourcing the portfolio management to another firm (Z), who is making the investment decisions on behalf of firm (B), ESMA confirms that firm B needs to report the algo or person who is primarily responsible for the decision to delegate.

    Q8: What are the reporting obligations for a primary issuance?

    ESMA has confirmed that all members of a syndicate need to report all execution legs by the ‘coordinating bank’ (CB) and the ‘billing and delivery bank(s) (B&D).  A CB is defined as a bank that will buy from the issuer/seller and sell to another bank or banks in the syndicate. A B&D bank will then sell to the clients, noting that a CB can also act as a BD. In relation to the time that needs to be reported, this should be the date time at which the pricing and the allocations are finalised between issuer and the syndicate, normally the first listing. ESMA has provided worked out examples for other fields.

    Q9: When are corporate events reportable?

    The industry is going to have to pick through the answers to question 9. ESMA reiterates that corporate actions are reportable where the investor has an opportunity to make an investment decision. It then goes on to recognise in practice that many corporate actions are as a result of mandatory events that bring them within the exclusions under 2(5)(i) of Article 26. This still leaves an element of interpretation on behalf of firms to identify these exclusions.  There is clear guidance on corporate events resulting from a default option and where an investor has given standing instruction.  For both categories a report is required.

    ESMA also confirms that it is the transaction resulting from the event that should be reported and provides a worked example. There are other points to review but in short and at first glance, this guidance reiterates that firms will need to put in place measures to identify reportable corporate actions.

    Q10: Are both legs of a swap reportable, when one leg contains an index such as LIBOR or EURIBOR?

    I think the answer simply says ‘look at example 106 in section 5:35.7.1’ but uses many more words than that to say this!

    The main purpose of this blog was to draw your attention to the latest Q&A and to highlight some of the key points. In terms of readiness for 3 January, I think the most significant impact will be the reporting of corporate actions and firms’ ability and capacity to separate those that are reportable from those that are not.

  • Big EMIR changes in MiFIR’s shadow and deadline fast approaching

    Big EMIR changes in MiFIR’s shadow and deadline fast approaching

    With so much focus on delivering reporting functionality for the upcoming MiFIR obligations, we shouldn’t forget the substantial changes required from EMIR’s Revised Technical Standards (RTS 2.0).

    The revised RTS was published in January in the Official Journal of the European Union and updated Q&As were published in April.  

    When will obligations come into effect?

    The new legislation will come into effect on 1 November 2017 with the exception of one rule, which came into effect immediately…the extension of the back-loading deadline (which we covered in this blog).  This came as a sigh of relief to those who had not yet started this task yet and a nasty kick in the teeth to those who had spent many painful hours digging through their archives searching for ancient data.  The justification for extending the deadline is that terminated trades do not increase systemic risk.  Given that one of the key objectives of the regulator is to identify systemic risk, the question ‘why does the regulator need this data?’ needs to be asked.  What will happen in 2019 when the new deadline approaches?

    Standardisation is welcome

    Many of the other new rules provide standardisation on how to populate existing fields. This is certainly a step in the right direction.  Counterparties no longer need to quibble over who is the buyer and who is the seller of their contract.  RTS 2.0 provides 10 lengthy rules to determine what is eventually reported out as a single letter – ‘B’ or ‘S’.  Disputes on which party should generate the UTI can be put to rest and altercations on counterparty identification will end as UTI generation responsibilities are created and LEIs are mandated.

    Standardisation is also desired for the ‘classification and precise identification of derivatives’. This is of course more easily said than done in a world where the industry always moves faster than regulation. Spreadbets and swaptions have become newly added contract types as they rise in popularity but ESMA has admitted that not every derivative can be put into a box by allowing the use of ‘other’ contract types.  Does this make the most complicated contracts the easiest to report?

    We also see clarifications and extensions to the allowed values for action type, which was a field that was introduced as part of the Level 2 validations.  ‘C’ is now confirmed to mean an early termination of a contract rather than a more general cancellation. ‘P’ has been introduced to identify the position component of the contract.  The need to report a transaction as ‘new’ followed by ‘compressed’ is replaced by this which should put a smile on some people’s faces as it means substantially less data to submit.  Some things never change though and action type ‘E’ should still be regarded as the kiss of death in terms of EMIR reporting.  Once action type ‘E’ has been reported by either counterparty, you can say goodbye to that UTI. Not even the new action type of ‘R’ for correction will be able to allow the re-reporting of that UTI.

    New fields?

    Lastly, no new legislation would be complete without the introduction of some completely new required fields.  ESMA will require a much more comprehensive view on what collateral details need to be reported. In addition, the party receiving the collateral will also need to report as well as the party posting.  The ‘level’ field has also been introduced so that submissions on a position level can be separated from a trade level.  However, definitions on exactly what is the difference between trade and position level are more difficult to come across.  One notable difference is that positions can have 0 notional whereas trades cannot.

    How we can help

    With such a focus on MiFIR there is a risk that firms may underestimate the material changes introduced by RTS 2.0.  Take the time to check whether you are on track to deliver on the required changes now and contact us if you would like help to understand the new obligations and/or get your testing and controls in place.

  • MiFID II guidelines update uneventful

    MiFID II guidelines update uneventful

    There is very little of note in ESMA’s update to its MiFID II guidelines on transaction reporting announced on Tuesday 8 August.  Most of the changes are to reflect the current references for regulations and a few corrections of CFI codes used in the examples. 

    Of note are the following:

    • Execution within the firm field

    Where an investment firm is instructed on where to execute a trade, the client is instructing the execution.  The original text stated you populated the “Execution within the firm field” with “Client”.  This has now been changed to “NORE” which we think means “No reference”. 

    (See 5.12: Block 5: Execution within the firm field)

    • Reporting as DEA provider

    A more significant update, is in respect of DEA trading where you are the DEA provider.  Previously, the guidelines indicated that the execution within the firm field should be populated with an Algo identifier for the order management system that routed the order to the trading venue.  This has now been changed to “NORE”. 

    (See 5.25: Direct Electronic Access (DEA)

    • Read ESMA’s full notice
    • Download the new guidelines
    • Download a tracked changes version of the new guidelines.
  • Significant changes proposed for EMIR reporting

    Significant changes proposed for EMIR reporting

    The European Commission has published its legislative proposals to amend European Market Infrastructure Regulation (EMIR).

    If implemented, they will result in significant changes to the current reporting obligations.

    Here is a quick rundown of the key changes being proposed:

    • Good news if you have not reported your historic trades – they are no longer needed
    • ETD reporting is going single sided, with the central counterparties (CCPs) picking up the burden.  The question remains for non-EU CCPs though.
    • Similarly, small non-financial counterparties (NFCs) will be able to rely upon financial counterparties (FCs) to take up the reporting burden.
    • Finally, trade repositories are going to be asked to ensure the quality of the data.

    The proposals follow on from a public consultation on EMIR and the Call for Evidence on financial regulation.  They also form part of the 2016 Commission’s Regulatory Fitness and Performance programme (REFIT).

    Yesterday the Commission also said it intended to present further proposed changes to EMIR on derivatives clearing as its scale and importance grows.

    We’ll be writing a more in-depth analysis of the proposals in the coming weeks.

    More information can be found on the European Commission’s EMIR webpage.

  • ESMA updates EMIR Reporting Q&As for backloading requirement

    ESMA updates EMIR Reporting Q&As for backloading requirement

    ESMA published its latest EMIR Q&As earlier this week to bring it in line with the revised technical standards which come into effect on 1 November this year.  This guidance is supported by the publication of revised validations to be applied by the trade repositories (the so-called L3 validations). Kaizen’s validation service will be available for clients to test their compliance with the validations from 1 May.  We will deal with EMIR RTS re-write in a forthcoming blog that will explore the impact of the EMIR changes. 

    The updated Q&A also deals with the requirements for back-loading of historic trades which is what we address in this article.   

    Back-loading of EMIR reports

    The back-loading obligation applies to firms with trades that were open or entered into after 12 August 2012 (the date from which EMIR took effect) and the commencement of EMIR reporting on 12 February 2014.  This requirement also affects firms that became subject to EMIR after the reporting obligation came into effect due to a relocation or re-categorisation of their business.  Any trades subject to the back-loading requirement must be submitted before the end of 12 February 2019. 

    The back-loading trades can be submitted in their end state and for exchange traded derivatives the concluding position for those cleared contracts.  Where these trades or positions are concluded or terminated after 11 August 2014 (the date when collateral and valuation reporting came into effect), the valuation and collateral fields must also be populated.  

    Reporting firms have been concerned about how to manage the exchange of the Trade ID (UTI) for historic trades.  Such a process would be extremely difficult however ESMA has clarified that where a trade is no longer live at the point of back-loading, the Trade ID or UTI will not have to be exchanged with the counterparty to the trade.

    ESMA has also made clear that following a corporate restructuring, the LEI of the corporate entity that is assuming the obligations for the demised entity’s derivative contracts, must be reported.  If the contracts are not being transferred, the contracts with the liquidated entity would be effectively terminated and should be reported as such.  This makes sense as it will ensure that the risk associated with those contracts is reflected against the entity that holds the risk. 

    A good outcome for firms?

    This is likely the best outcome that could be reached between ESMA and firms in that it allows the EMIR reporting requirement to be met without placing undue burden on reporting firms.  Still, it comes at a time when firms are more than busy with preparations for MiFID II with SFTR closely on its heels.  These changes won’t be the last either, with ongoing guidance via the Q&A process expected for MiFID II reporting both before and after 3 Jan 2018. 

    Dealing with constant change to reporting

    It is clear that firms need to develop speedy and effective processes to implement reporting changes but more than that –  the costs need to be brought under control.  Whilst your reporting solution will be the first area that needs to be addressed, the burden of testing any changes is not insignificant in terms of time, resources and overall cost.  Our testing approach provides early access to validation testing for our clients with full accuracy and completeness testing applied once the reporting solution is completed ahead of go-live.  This testing approach can be used to augment or replace your internal user acceptance testing.  It saves on costs and provides full visibility of your reporting quality, allowing corrections to code or static data to be made before revised reporting requirements take effect.

  • Q: Which ‘reporting crocodile’ will be nearest the canoe in 2017?

    Q: Which ‘reporting crocodile’ will be nearest the canoe in 2017?

    A: MiFID II, and it’s only 358 days away…

    In our last blog we looked back on the reporting events and challenges that shaped 2016 through the hits of Bowie; but as we begin 2017 we find ourselves asking, ‘where are we now?’ (last Bowie reference…promise!). In short, there are many reporting regimes that are contenders to win the accolade of the ‘reporting crocodile’ nearest the canoe for UK firms in 2017. However, the characteristics and specific demands that MiFID II requires of firms, establishes it as the most demanding and challenging regulatory reporting ask of 2017. The clock is ticking and as at the time of writing, we have 358 days until go-live!

    The other crocodiles circling the canoe

    For those of you who came back into the office to deal with the aftermath of your firm’s Bank of Israel Reporting go live, 3 January 2018 may seem a long way off. Equally if you are responding to the CFTC review of your DFA reporting through the NFA and their 4s letters or an official examination by them, again MiFID II seems a distant problem to contend with. Worse still, your firm may be facing regulatory censure on longstanding commitments such as MiFID I or, as we are seeing increasingly, fines from the CFTC in relation to accuracy of reports under the DFA regime. Then there is pressure from ESMA and competent authorities to improve the quality of EMIR reports. In addition to the EMIR Review and MiFID II, European firms need to contend with consultations on SFTR.  For those who have US and HK obligations there are the new SEC and HKMA obligations due throughout the first three quarters of the year.

    These ‘crocodiles’ are not just circling but hitting the canoe at the same time and of course, you cannot pick and choose which ones to deal with; all need to be grappled with. But what makes MiFID II stand out as the crocodile you need to deal with most?

    What are the characteristics of MiFID II that require special attention?

    In a nutshell – in many respects, MiFID II confers materially different obligations on firms and runs a much greater risk of regulatory censure following go-live compared to other G20 reporting obligations. There are three characteristics which mark out MiFID II for special attention:

    First, the sheer number of fields, many different from what has been asked of before. E.g. Trader ID, algo ID, short-selling field, pre-trade waivers, and precise execution time to the millisecond and beyond!

    Second, MiFID II builds upon an existing regime where competent authorities, most notably the FCA, have developed expertise in detecting data quality issues and have a regime in place to issue sanctions. Ana Fernandes of the FCA made it clear at the recent FCA TMU Transaction Reporting Forum, that expectations will remain high and the ability of the TMU to detect errors will be improved come 3 January 2018.

    Third, the sheer complexity of the MiFIR requirements dwarfs that of competing regimes. Whether it is determining what transactions need to be reported, what business events need to be excluded, notwithstanding ‘no LEI no trade’, the short-selling calculation, or how to put in place the mandated regulatory controls, the level of complexity is materially different than what has been expected before.

    Next, we explore some of these complexities and discuss what firms need to be doing now to ensure successful delivery this time next year.

    Your MiFID II to do list

    It’s the New Year and what better time to draft your ‘MiFID II Transaction Reporting to do list’?  Better still, we’ve done it for you…

    1. Reporting Solution – Build or Buy?

    Key to meeting the complex obligations of MiFID II is putting in place the appropriate reporting solution.  There is no fixed answer on whether to buy or build as it depends completely on your firm’s size, previous investment in meeting reporting obligations, and expected reporting volumes.

    At one end of the spectrum there are the large tier 1 banks who have been investing heavily in their reporting solutions over the last six years. In this case, it is most likely that there will be an extension of recent builds to cater for MiFID II requirements. A word of warning, IT architects and IT leads that expect a similar build to EMIR should think again, see below for examples of why.

    At the other end of the spectrum, are firms who have previously had little or no reporting obligations who are only now looking to make the decision on whether to build or buy. On balance, due to the complexity involved and time remaining, buying a solution and adapting it to your needs is probably the least risky option and you should choose a provider with a track record of providing reporting solutions that are ready to roll off the production line.

    2. Determine what trades are reportable, based upon instrument being traded

    At first glance it appears straightforward how to determine what instruments needs to be reported. Firms will be able to rely, to a certain degree, on the list that ESMA is mandated to provide under RTS 23. But even here there are significant implementation and operational issues with this list. For example, if it is not produced or there are issues with it then firms still have the obligation to report correctly, irrespective of the provision of the list.

    It become more complicated when you have to identify instruments which reference those traded or admitted to trading on trading venues.  How will firms identify and report the below examples?

    • Third country futures that reference instruments admitted or requested for trading on trading venue (RM, MTF or OTF)
    • OTC derivatives and 3rd country ETDs that reference instruments admitted or requested for trading on trading venue (RM, MTF or OTF)
    • How to identify, at the time of trade, the index constituents.

    Due to these inherent problems; determining which instruments are reportable becomes a materially more complex proposition compared to MiFID I, EMIR and DFA. Firms need to be working now with their counterparts, vendors and participate in discussions with their Trade Associations to put in place workable solutions.

    3. Establish what activity requires reporting

    Having figured out what instruments need reporting firms need to turn their attention to determining what activity is reportable. In short, take a look at RTS 22, Article 2 and the 14 different sets of activities that need to be excluded. The fact that many of these business activity exclusions have not been seen in EMIR, demonstrates again the material difference in the type of reporting solution required for MiFID II compared to previous reporting regimes. Firms will have to look at their trade data and ensure their reporting solutions are able to identify activity that should be excluded, as MiFIR does not allow for over-reporting.

    4. No LEI – No Trade

    Both the FCA and ESMA in recent public meetings have reiterated the point that firms must not trade with entities that do not have a LEI. This has been reiterated in the first MiFID II Q&A published by ESMA. There is considerable work for client onboarding teams and relationship managers to reach out to clients without LEIs and ensure compliance by 3 January 2018. Good luck!

    5. Short-sell calculation

    We will not discuss here the merits or otherwise of the short-selling requirement for transaction reporting (ok well, a little passing reference…suffice to say the value of this field is a best questionable.) Transactions in cash equities and government securities will require a calculation to identify transactions that take the firm short at any given point. Making an accurate calculation that takes into account late trade bookings and busts will be problematic and firms should not underestimate the time and cost that will be needed to ensure compliance.

    6. Under RTS 22, Article 15, ESMA high priests did say upon to firms, ‘thou shall test and reconcile one’s transaction reports….’

    Ok, maybe not as dramatically as that but ESMA now makes the obligation to test and reconcile mandatory under MiFIR. The important point to note is that controls are often the first casualty of delivery, as go-live approaches. For MiFID II this is not an option; firms need to ensure effective testing and reconciliations are in place at go-live. Failure to do so will be a breach. Looking to third party providers who have mutualised the costs of testing and reconciliations may make sense to ensure comprehensive and effective controls are in place prior to go live in 358 days time.

    There are many more items to add to the MiFID II Transaction Reporting to-do list.  Of course in the current environment there is no choice between which regimes you implement. That said, the complexity and the introduction of new demands on firms by MiFID II means it should be treated as the largest crocodile nearest the canoe when firms are planning their 2017 regulatory reporting delivery.

  • 2016: The reporting (Jean) Genie is well and truly out of the bottle

    2016: The reporting (Jean) Genie is well and truly out of the bottle

    David Bowie was many things to many people but a transaction reporting aficionado he was not. That said, in the year that saw the great man leave on his own “Space Oddity“, we use some of his most loved hits and lyrics to help us look back at reporting in 2016 …. and only hope he is not looking down to see us take such a liberty! David, we’re truly sorry…

    The reporting “Labyrinth” – new obligations

    Every year since the 2009 G20 Pittsburgh summit, which gave birth to the G20 reporting commitments, the industry has had to plan for and comply with new regulatory reporting obligations across the globe and 2016 has not been any different. Added to the “Labyrinth” of existing regulatory obligations, we have seen Canadian G20 reporting go live in July, the introduction of branch reporting in Hong Kong, and closer to home we have seen changes to EMIR reporting brought about by the introduction of clearing obligations. To cap the year off, firms will need their own “Heroes” working during the holiday season to make sure they can go live with Bank of Israel reporting on 1 January 2017!

    “Ch-ch-ch-ch changes”

    In regulatory reporting that has only recently gone live, 2016 has seen “Changes” or consultations on changes to their obligations. In accordance with Article 85(1) EMIR, the European Commission launched a review of the legislation on 21 May 2015 and published its final report on 23 November 2016.  As a result, the Commission has committed to a legislative review of EMIR in 2017 which will include an attempt to streamline trade reporting requirements.  In the US, we have seen no action relief expirations for CFTC DFA (Dodd Frank Act) reporting and the advent of SEC reporting drawing closer. The election of Donald Trump aligned with a Republican majority in the US Congress could mean substantial changes with the repeal of certain sections of the DFA in 2017 a distinct possibility.

    “Ashes to Ashes” for MiFID I transaction reporting

    As transaction reporting under MiFID I enters its final year, throughout 2016 firms have found themselves “Under Pressure”, trying to prepare for the much more demanding and complex ask of MiFID II.  Both buy side and sell side firms have been grappling with their understanding of the obligations imposed by MiFIR Article 26, the supporting RTS 22 and final guidelines.  The final guidelines document published in October represents a substantial investment by ESMA and the competent authorities.  Ana Fernandes of the FCA’s Transaction Monitoring Unit stood in public and compared the physical size of TRUP to the MiFIR guidelines. Her conclusion –  they have invested significant time and effort in the drafting of the regulations and supporting guidelines and their expectations of the standard of reporting is higher than that of  regimes that have recently gone live.  Throughout 2016 firms have been busy digesting what is required of them to comply with MiFIR transaction reporting obligations, realising it is significantly more complex than either EMIR or DFA.  In short, the significant increase in complexity of MiFIR reporting combined with the greater scrutiny of regulators means MiFIR could prove all-consuming for firms in 2017.

    Data Quality? Everything is not “Hunky Dory”

    As the year ended, the industry received messages both from the FCA and ESMA about the quality of the data that is being reported to them. Ana Fernandes and Olga Petrenko both struck the same chord at last month’s Transaction Reporting Conference at the BBA when they called out the poor quality of data still being reported.  Ana outlined that reporting under MiFID I, now live for nine years, still has significant errors – something that we highlighted when we analysed transaction reporting fines earlier this year.  Olga explained that ESMA is still receiving complaints from other bodies such as central banks about the quality of the data they are receiving from the reports made under EMIR.  Consequently, ESMA will have the improvement of data quality as its primary objective of 2017.  Both bodies are investing heavily to develop the capacity to identify data quality issues where they will increasingly compare reports, use independent sources of data, and introducing ‘business’ validations to identify errors and hold firms accountable in meeting their obligations.

    If these years are to be the “Golden Years” of reporting and less a “labyrinth” of competing demands, then the industry needs to invest heavily in accurate advice and appropriate solutions throughout 2017 so the quality of the data they report meets the increasing expectations of the regulators.

    There’s a lot to do as we head into 2017 but to soften the blow perhaps have a listen to Bowie over the festive season.

    Thank you for your support in 2016 and we wish you a restful break with your friends and family.

    Seasons greetings from us all at Kaizen.

  • 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!

  • UPDATE: Why populating the clearing obligation field won’t be so easy

    UPDATE: Why populating the clearing obligation field won’t be so easy

    UPDATED 9 September 2016

    Thomson Reuters Accelus has published an opinion piece by our CEO Dario Crispini.

    The article, Why populating the clearing obligation field won’t be so easy, comes off the back of the European Commission’s endorsement of the delegated regulation for mandatory clearing of interest rate swaps denominated in SEK, PLN and NOK currencies in June.

    The regulation extends the clearing obligation from the currency scope of certain EUR, GBP, JPY and USD Interest Rate Swaps and CDSs on the iTraxx main and crossover indices.

    Dario’s article takes a look at what contracts are caught by the clearing obligation and makes the point that completing the field will require great care as there are some hidden complexities.


    The full article is available at Thomson Reuters Accelus, a subscription only service.  If you’re not a subscriber, please download a copy here.

    Article 4 of EMIR introduces the clearing obligation for certain in-scope entities. Earlier this year ESMA published revised EMIR Q&As to give firms more information on how to complete the clearing obligation field which tells ESMA whether or not the contract entered into is subject to mandatory clearing. 

  • Updated EMIR trade reporting rules set stage for fines

    Updated EMIR trade reporting rules set stage for fines

    Kaizen’s CEO Dario Crispini spoke with Thomson Reuters Accelus about the revised EMIR trade reporting regime which aims to bring clarity to the regulatory technical standards first published in 2012.

    “Potentially the EMIR review is more important from an enforcement perspective than it is from an reporting perspective. I do expect to see some fines. The U.S regulators are further ahead and we will see some Dodd Frank fines first. The EMIR review does provide more of a legal platform for taking enforcement action across the various countries. It will be the enforcement processes of the relevant national competent authorities that are applied, which are not EU-wide,” Crispini said.

    The full article is available from Thomson Reuters Accelus, a subscription-only site.

    Extract

    One of the main reasons behind ESMA’s decision to revise the trade reporting RTS was to convert the guidance set out in the many Q&As and the level one and two validation processes into technical standards.

    The EMIR review brings new rules such as the RTS covering product identification and classification, as well as introducing clear obligations regarding unique trade identifier exchange and the timing of UTI exchange.

    “The EMIR review takes many guidelines published by ESMA in the Q&As and makes them regulations or secondary legislation that cannot be contested from an enforcement point of view. For example, if firms have not created a UTI according to the new guidelines, because they are now RTS, they can’t say it was only a guideline. It makes the enforcement process easier for each of the National Competent Authorities,” Crispini said.

    Link to original article

    Read Dario’s recent EMIR opinion piece on mandatory clearing: Why populating the clearing obligation field won’t be so easy

  • 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.

  • Updates From The Deutsche Boerse Buy-Side Working Group

    Updates From The Deutsche Boerse Buy-Side Working Group

    Stephen Hanks from the FCA provided some interesting feedback about MIFID II progress at the Deutsche Boerse Buy-Side Working Group (April 21) which we were speaking at and attending. We wanted to share some of the key points we learned at the event.

    Broad points of interest:

    • The finalised delegated acts for MiFID II should be published next week (week commencing 25 April) closely followed the week after with MIFIR delegated acts.
    • The FCA advised that with regards to the waiver volume caps, the debate continues around the appropriate calculation approach. This highlights the ongoing industry concerns regarding these caps being exceeded and all activity in a security being fully lit. As discussed at the working group, it is too early to assess the impact this could potentially have.
    • Questions also remain about principle trading by an institution operating an MTF and what the firm operating the MTF could put through the platform.
    • The FCA also suggested that EU level discussions implied that systematic internalisers would not be able to use matched principal activity as their primary trading model on the SI platform as such activity is considered to fall outside the purpose of the SI regime. The FCA advised that questions also around price improvement under the SI regime should also be dealt with in the delegated acts to be published in the next couple of weeks.

    From a transparency perspective the FCA provided the following comments:

    • Regarding the establishment of a CTP for equity securities, no indications of interest have been received by authorities from potential service providers.
    • For non-equity securities there will now be a phased approach for SSTI.
    • The FCA confirmed that size thresholds for bonds and the present 100k euro threshold was also being looked at by ESMA.
    • As per recent statements, ESMA will also be producing new advice for non-equity transparency.

    From a transaction reporting perspective:

    • ESMA is also reviewing the definition of an ARM and what activities would trigger the requirement to register as an ARM. Debate has been raised as a result of there being unregulated intermediaries conducting key activities between the regulated firm and its ARM. This would mean that regulators would only have locus over a portion of the process and not all of it.
    • The FCA advised that although there are questions around the benefits of including ‘short selling’ flags in the transaction report, this will remain a requirement.

    The main take away here is clearly the timing around the publication of the finalised acts. This will firm up requirements being created under the legislation. Those managing the MiFID II projects have been waiting for the acts to be finalised to progress the work required which is significant for all financial firms. The acts are also bound to raise further discussion points and once published, will provide the platform for progressing with the Level 3 work.

  • Continued uncertainty around future transparency under MiFID II

    Continued uncertainty around future transparency under MiFID II

    The European Commission’s late pushback on MiFID II will cause the industry further headaches and has not surprisingly frustrated ESMA.

    Last week, the Commission rejected three of the 28 MiFID II technical standards asking ESMA to take another look at them.

    ESMA has responded in three open letters, saying it will get to work straight away but has made it clear that the Commission has not followed procedure and should’ve got back to it by the end of December, not nearly three months later.

    One of the issues the Commission has asked for a rethink on are ESMA’s proposals for bringing more transparency to the bond markets – something we here at Kaizen are particularly interested in.

    Damage to liquidity

    The Commission’s concerns around bond market transparency are consistent with the views of the industry. The minutes of the FCA’s recent trade association roundtable highlighted not just worries from a bond market perspective but whether appropriate and equal consideration is being applied to the other asset classes coming into scope for transparency under MiFID II such as derivatives. The new regulation is clearly attempting to remove the opaque nature of these sectors. However arguments continue that the MiFID II RTS as currently drafted would potentially damage liquidity and would in fact be harmful to liquidity providers. The Commission has clearly acknowledged these concerns and ESMA is now revising its approach.

    Further challenges for implementation

    Although a rethink on MiFID II transparency may initially appear positive, for the industry as a whole it creates further problems. Without clarity on these standards, firms will have to make broad assumptions around the current guidance as they progress with MiFID II implementation. It is unclear how long it will take ESMA to review, but the European Parliament has been clear that further delays beyond 3rd Jan 2018 are not an option and the deadline must be met.

    Considerable challenges

    ESMA’s response not surprisingly has highlighted the ongoing frustrations that exist in this extremely delicate and challenging area.

    ESMA’s letter reveals that the Commission views the current transparency proposals on calculating liquidity inappropriate and that more frequent, timely calculations are required. It is understandable given that within the new market sectors liquidity fluctuates dramatically over short periods and a liquid security can rapidly move to being illiquid. ESMA has already faces considerable challenges sourcing the data to calibrate the regime as the MiFID only gives them the power to obtain transparency data post MiFID go-live.  In recognition of this conundrum the draft text proposes all FX derivatives be classified as illiquid for the transparency reporting obligations until such time as ESMA is able to source and assess more meaningful data.

    Developments here will need to be closely monitored as small changes in the regulations have the ability to create a major impact on MiFID II projects.

  • Why populating the clearing obligation field won’t be so easy

    Why populating the clearing obligation field won’t be so easy

    As we approach the deadline for mandatory clearing ESMA has published a further update to its EMIR Q&As providing guidance on the application of the clearing obligation for swaps resulting from exercise of swaptions.  With mandatory clearing only months away for OTC interest rate derivatives denominated in the G4 currencies (EUR, GBP, JPY and USD) we take a quick look at how mandatory clearing will impact EMIR reporting.

    From 21 June 2016 mandatory clearing will firstly affect firms who are individual or general clearing members of an authorised or recognised central counterparty (CCP).  Six months later, category 2 firms will be caught and category 3 firms a further six months after that. This means that firms will need to assess what category they will fall within, but also what category their counterparties will fall within as that will determine if and when mandatory clearing applies.  See our table at the end of this blog.

    Firms that aren’t in category 1 will need to do some data crunching to calculate whether their group is above or below the €8bn clearing threshold and they should be notifying their counterparties either way, something Kaizen can assist with.  Each of the three categories will need to be wary of the frontloading obligation which captures trades entered into or novated on or after the frontloading date dependent on the instrument and the remaining maturity on the trade.  So they will need to consider pricing based on the potential for eventual clearing of these trades if they remain open once the clearing obligation kicks in.

    Regarding the ESMA Q&A, it makes clear that for in scope derivative instruments and counterparties:

    1. All novations of any type which result in a new counterparty will be subject to the clearing obligation.
    2. For swaptions entered into prior to the frontloading window the resultant swaps will not be subject to the clearing obligation irrespective of when the swaption is exercised.
    3. For swaptions entered into after the start of the frontloading period:
    4. Mandatory clearing applies where the swaption is exercised during the frontloading period and the resultant swap is above the minimum remaining maturity per the RTS.
    5. And for any swaptions exercised after the clearing obligation takes effect the resultant swap will be subject to the clearing obligation.

    Reporting implications

    To report correctly, firms will need to complete the “clearing obligation” flag with the appropriate value.  This will require firms to assess whether each trade is subject to the mandatory clearing obligation irrespective of whether the trade is already cleared or not.  That will mean assessing all trades entered into after the frontloading period begins.  Currently, this field should be populated with an “N” but for Category 1 firms this may change post 21 June 2016.  Trades which will be subject to mandatory clearing entered into prior to this date should be flagged as “N” in the clearing obligation field until the clearing obligation takes effect.  The timing of this will be based on the firm’s category and that of its counterparty.

     

     

     

    Notes:
    NFC+:   Non-financial Counterparty above the clearing threshold, as referred to in Article 10 of EMIR
    AIF:    Alternative Investment Funds

  • MiFID II delay confirmed but there’s no time to waste

    MiFID II delay confirmed but there’s no time to waste

    The European Commission has confirmed the MiFID II implementation deadline has been extended by a year to 3 January 2018.

    While this isn’t in any way surprising, the clarity is welcome news for the industry after ESMA initially proposed a delay in November. The Commission says the delay is to ‘take into account of theexceptional technical implementation challenges faced by regulators and market participants.’

    Twenty-two months is still a very short time for firms to complete all the changes required for MiFID II.  Given the significant size and scope of the new reporting requirements – affecting a much larger group of market participants – those affected should take action now if they haven’t already done so to get themselves ready. 

    A year’s delay may seem like a long time but firms should not take their foot off the pedal.  The reprieve to 2018 means it is likely that regulators will have less tolerance for those who do not meet the new reporting requirements from the get-go.  In addition, those who leave it to the last minute may find themselves with much higher implementation costs.

    We can help firms prepare for the new transaction reporting requirements required under MiFID II from getting your transaction reporting in order through to bespoke training on the new requirements.

    Contact us to find out how we can give you MiFID II peace of mind.

  • ESMA’s latest EMIR Q&A provides clarity on notional fields

    ESMA’s latest EMIR Q&A provides clarity on notional fields

    15:57:02ESMA has issued a few new pieces of guidance via its latest EMIR Q&A update.

    The key point for EMIR reporting is the guidance on populating the notional field for futures and options at position level (transaction reporting, question 41).

    1. Notional for futures:  quantity x price multiplier x settlement price
    2. Notional for options: quantity x price multiplier x strike price

    That means that for a future on ICE on the FTSE 100 index the notional will be the quantity (number of contracts traded) x 10 (£10 per index point multiplier) x forward price (in index points).  For a position report this would be the average forward price weighted by quantity.

    The other updates are:

    • Additional default management guidance for CCPs under CCP question 3 (d) and
    • Access to data by the competent authorities under transaction reporting question 37 (a).

    These updates are helpful for firms in that they provide clarity on populating the notional field however questions remain about whether the notional for a buy would be different from a sell for trades.  It is clear that if you have 100 buys of FTSE 100 futures and then you do 50 sells, the notional on your position report would be reduced.  But is ESMA expecting the notional for the trades to be negative for sells?  It doesn’t appear to be the case from the Q&A.  More clarity from worked examples as per the recent consultation on MiFID II transaction reporting would be welcomed.

  • ESMA Data Portal Changes

    ESMA Data Portal Changes

    Firms subject to MiFID and other regulatory reporting obligations should be aware that ESMA is migrating its current data register to a new portal.

    These changes will be of particular interest and relevance to compliance and operations teams.

    The existing portal will be removed from 1 April.  The migration impacts the following published data sets which will have a direct impact on validation to ensure compliance with regulatory reporting:

    • Published list of shares admitted to trading on regulated markets
    • List of exempted shares
    • Register of systematic internalisers
    • List of authorised regulated markets
    • List of authorised multilateral trading facilities (MTFs)
    • Central counterparties

    To enable a smooth transition, ESMA is making the data register available on both portals for the rest of February and until the end of March.  As of 1 April 2016 the old portal will be shut down and not accessible.

    Firms that have established automated access to these lists should refer to the updated web service procedure ESMA has published.

    Developers responsible for the automated processes adopted in respect of the datasets should review the information detailed on ESMA’s website.

  • It’s crystal ball time – regulatory reporting in 2016

    It’s crystal ball time – regulatory reporting in 2016

    As the memories of performances of A Christmas Carol fade, the ghosts of Christmas past, present and future are a useful analogy to convey the challenges firms will encounter in meeting their regulatory reporting obligations in 2016.

    From the past, MiFID reporting of the 2007 vintage still provides a real and present risk to firms. The present, in the form of EMIR and DFA reporting, will undergo changes to requirements. Looking to the future there are a number new obligations that are due (REMIT, Money Markets) and significantly, the highly likely delay of MiFIR/MIFID II to 2018. A common theme running through all obligations is the increasing levels of scrutiny from regulators and therefore of firms’ senior management.

    Past

    Despite all the focus and costs expended upon the new reporting obligations globally, still the most material risk to firms in getting their reporting wrong is UK transaction reporting required under MiFID since 2007. Last year we saw fines break new records, reaching GBP£13m and it is not inconceivable that in 2016 firms may receive higher fines. It is crucial that firms do not take their eyes off the ball so that they continue to adhere to legacy reporting requirements.

    Present

    The introduction of EMIR and DFA obligations over last few years is still fresh in the minds of regulators, trade repositories and firms. In 2015 EMIR reporting has seen significant change with ESMA mandating trade repositories to introduce much higher levels of validation on firms’ submissions. In the year ahead we expect to learn of further significant changes to EMIR reporting obligations as a result of both the consultation of 2015 and knock-on effects of EMIR clearing. For those firms who have a DFA reporting obligation, the later part of 2016 will see changes to CFTC Part 45 rules as part of the rewrite. Firms will need to plan for changes to obligations that have only very recently been introduced.

    Future

    Wherever you look, there are new reporting obligations with compliance dates in 2016. In the energy markets, REMIT OTC obligations are due in the second quarter. In the third quarter Switzerland is set to introduce its version of EMIR. Despite the advent of trade repositories, the central banks are requiring their own reports. In the second and third quarters of this year, the Bank of England and the European Central Bank are requiring money market reports. MiFIR/MIFID II is the one omission from the list, due to the highly likely scenario that it will be delayed from January 2017 to January 2018. Despite this delay preparation for the MiFIR requirements for transaction, trade reporting and instrument data reporting will dominate the change agenda for 2016/17.

    Common theme – increased scrutiny

    Regardless of whether the reporting obligation is a legacy requirement, recently introduced, or with a compliance date in 2016/17, the expectations and scrutiny of regulators is only on an increased trajectory. As such, expect increased fines for those more mature reporting regimes (MiFID). For more recent regimes, fines (DFA) have already been issued or greater scrutiny from regulatory bodies is becoming evident (EMIR). Future reporting regimes will be expected to hit the ground running with high quality reports expected from the get-go. The importance of ensuring correct reporting has never been as important to firms and the financial system as a whole.

  • 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′]

  • Just a second…?

    Just a second…?

    MiFID II introduces the requirement to synchronise the business clocks of trading firms and their customers so that timestamps recorded are standardised across the industry. The idea is that regulators will be able to monitor for market abuse more accurately. Trading systems will need to synchronise themselves to a common source of time. But how will they do this? And what are the implications?

    On the back of the FCA’s MiFID II conference this week we were with the National Physical Laboratory (NPL) to find out. Their workshop, “UTC traceability for the global financial sector, realisation of a unified common clock” attempted to answer some of these questions. Taking the front seat was MiFID II’s RTS 25, which outlines the draft regulatory technical standards on clock synchronisation. The direct impact of this piece of regulation was apparent from the range of professionals from all aspects of the industry including financial firms, exchanges, consultants and scientific organisations.  Most notable was the presence of ESMA and the Bureau International des Poids et Mesures (BIPM) as both have a heavy hand to play in RTS 25. We suggest firms take a look at Table 2 in the Annex of RTS 25 which sets out the level of granularity applicable to their trading activities. It is important that firms are clear on what is expected of them and should be in advanced discussions around the technology to be adopted to meet the new regulatory obligations.

    Here are the key points we took away from the conference:

    1. The industry was concerned about deploying GPS as a means to synchronising their business clocks. It was felt that although it meets the regulators’ authorisation of “satellite systems” as a credited tool, it does not provide traceability back to UTC.  This was further supported by BIPM who claimed that due to the irregular leap second lag incurred through GPS signals, the only credible solution was a direct feed from a National Measurement Institute (NMI). ESMA was clear that both options remain and stood firm, stating that they must be realistic in what they ask from firms and not show any bias to any provider.
    2. The industry feels this needs to be part of the Level 3 discussions but it seems very unlikely that GPSs will be scrapped. We advise all firms to gear up based on the Level 2 RTS 25.
    3. The industry also showed concern around implementing the required technology and sought r advice from the regulator. However, ESMA’s view was very clear in stating it is up to the firm to implement what is required.
    4. ESMA highlighted the importance of firms reviewing their transparency systems on an ongoing basis once deployed. The type of review required is not clarified within the RTS, however we would recommend both internal and third party checks to ensure obligations are met.
    5. FIX is planning to update all versions of its protocol (back to FIX 4.2) to capture the accuracy of seconds in timestamps to 6, 9 or 12 decimal places.
    6. BATS Chi-X Europe is considering providing NPL time source feeds to its clients via a PTP feed if there is considerable demand.

    All in all, the industry is aware of the challenge in implementing this step and the effects it will have on their infrastructures. However, having the same “watch” is very much welcomed by all concerned, agreeing it will lead to better data publication and reporting, thus a more transparent industry as a whole.

    What do you think?  We would welcome feedback or comments about the issues raised in this blog and more broadly, about the MiFID II draft technical standards.

    We’ll be releasing further blogs around the finer details of MiFID II so stay tuned!

    In addition to our testing services, we are offering training courses for firms to help them prepare for the reporting elements of MiFID II. Please contact us to find out more. 

    Read our earlier blog on our reaction to the release of the draft RTSs.

  • 10 things we learned at the FCA’s MiFID II conference

    10 things we learned at the FCA’s MiFID II conference

    Like many of our clients MiFID II is uppermost of our minds at the moment. And on Monday we were discussing all things MiFID II at the FCA’s MiFID II Wholesale Firms Conference in London. Likely to be the first of many conferences about the new regulation, this was probably the earliest event possible given the regulatory technical standards (RTSs) were only released on 28 September.

    Our advice to firms?  Don’t delay: Get your heads around the new rules and get into the detail quickly.

    Here are our key take aways from the conference:

    Regulatory Process

    1. The UK is now working towards transposing the MiFID text into UK law and this must be completed by 3 July 2016 while the European Commission now has three months to consider the published regulatory and technical standards. The FCA’s view is that it is unlikely that the Commission will impose any changes and this position will be affirmed by Q1 2016.  The FCA will publish further consultation papers and these are likely to be split with a consultation paper in December 2015 and an additional one in early 2016.

    2. Regarding the timeline, the FCA acknowledged this is challenging for the industry and regulators alike. However delays to MiFID II are only possible if the Commission considers this is appropriate and it is not within the college of regulators’ powers to impose.  That said, we do think there will be a request for either a partial or full delay given the truncated timetable for what will be a lengthy legislative process.

    3. Organisations not currently within the scope of MiFID I may potentially fall into MiFID II particularly around the commodities space.  These firms will need to quickly plan how they will manage this authorisation process and should submit applications to the FCA by 3 July 2016.   Applications submitted post 3 July will be processed by the FCA on a best efforts basis but there will be no guarantee that applications will be completed before MiFID II goes live in January 2017.  Something that could be very detrimental to business.  A similar story applies to firms that will have to apply for trading venue status OTF or MTF, high frequency trading firms, or as a systematic internaliser.  All activity within firms will need to be assessed to confirm whether authorisation will be required and many platforms are expected to be captured such as broker crossing mechanisms which will come under the new OTF regime.

    Transparency

    4. Following a review by ESMA, the FCA confirmed that agreement had been reached on the approach to be adopted towards the calculation of liquidity and the transparency obligations that would therefore be imposed in respect of non-equity securities.

    5. ESMA, following extensive consultation with industry participants and having reviewed considerable datasets, proposes the liquidity calculation will be applied on an Instrument by Instrument Approach (IBIA).  The FCA believes this will mean real-time transparency reporting obligations for 4% of bonds with a significant portion of these being from sovereign debt.

    6. With regards to deferred publication regime, delays will be possible between two days and up to four weeks from the point of execution.  Venues will also be able to apply for pre-trade transparency ‘waivers’ where the execution is above standard market size. The FCA asked that venues apply for such waivers as soon as possible given that approval is required ahead of trading activity if reliance is to be placed upon any such waivers.

    Commodities

    7. Position limits will be imposed in the commodities sector. The limits will have a cap of between 5-35% of the deliverable supply. Such limits also extend to firms’ open interest positions which imply a potential delivery at such a level. Similarly, the FCA also confirmed that thresholds will be applied to speculative trading in such instruments, and firms exceeding the threshold would require authorisation under MiFID II.

    8. Position limits represent significant challenges for groups with multiple entities trading commodities as the limits are applied both across the group and to each entity so one entity in the group could be within the limits, while across the group the combined total exceeds the position limits. This type of calculation is also to be applied when evaluating whether a firm’s commodity trading activity is ancillary to its main activities or not.  Such calculations look at both the individual entity’s positions and the net positions across a consolidated group.

    9. Position reporting by venues is also a requirement under the new regulations.  The FCA is fully aware of the challenges that the requirements place, not least the need to identify clients down to the ‘end client’.

    10. In transaction reporting, the RTSs are pretty clear but one area we sought clarity on was the new complex trade ID field.  This field seeks to link trades that are part of a wider trading strategy.  Ana Fernandes from the Transaction Monitoring Unit gave a very clear exposition of the aims and drivers behind RTS 22 and confirmed that the aim was to capture true strategies and the intention was not to cover hedging activity or even matched principal activity (riskless principal). However Article 12 wording still points to these transactions being captured.  It is also worth noting that in the RTS ISINs are the only identifier for trading venue instruments.  We expect that was a shock for the likes of Eurex and ICE as the consultation proposal was for Aii codes as well as ISINs.

    What we liked:  In the last session, a panel of regulators including ESMA, BaFin and AMF were quizzed by Nick Bailey of the FCA.  We saw this as very positive in that it shows the regulators are talking to each other; indeed they said that such collusion would be in breach of the competition laws were they operating as firms.

    Once the regulators have had more time to digest the detail of the 900+ pages of RTSs we hope to see more of these events with greater detail and elaboration of the implications for firms and their trading activities.

    In addition to our testing services, we are offering training courses for firms on the reporting elements of MiFID II. If you are interested please contact us. 

     

  • Latest EMIR Q&A update looks like a major headache for Trade Repositories…

    Latest EMIR Q&A update looks like a major headache for Trade Repositories…

    ESMA’s latest update of its EMIR Q&A document requires reporting entities (or the party to which they have delegated reporting) to notify their trade repository when there is a change in their identifier.

    This means either:

    • A change in their Legal Entity Identifier (LEI) due to a merger or acquisition, or
    • Where the entity obtains an LEI when they previously reported another code (BIC or internal code).

    Once notified of the change, the Trade Repository is to notify the other repositories and update all open trades with the new value by replacing the old value in all the identifier fields where it had previously been used.  The Trade Repository is then to notify all the counterparties to the modified trades, as well as regulators.

    Why is this being introduced now?

    Level 2 validations take effect from November. The validations will affect updates to any open trades in the repositories where a BIC or internal code has been used to identify the reporting entity. Furthermore, there will always be corporate activity resulting in a need to change identifiers.

    The guidance provided is not as clear as it should be. On my reading, the Trade Repositories are to update all the open trades where the party changing the LEI is the ‘counterparty’ or ‘other counterparty’. I could be wrong on this but if so, the guidance needs to be updated.

    Major headache

    I am not sure how the Trade Repositories will like this change as they are required to amend client records quite substantially which introduces processing risk. Further, it is highly likely that client records will get out of synch with those at the Trade Repositories. I can’t see it as being anything other than a major headache for them particularly if they are to contact all the counterparties to trades where the reporting entity’s identifier has changed.

  • ESMA writes the control section of your transaction reporting BRD…

    ESMA writes the control section of your transaction reporting BRD…

    ESMA has published its eagerly awaited regulatory technical standards (RTS) for MiFID II for consideration by the European Commission.

    Chapter 7, Market Data Reporting (RTS 22) outlines the obligations for transaction reporting. And for those responsible for drafting their firm’s control section of the Business Requirements Document (BRD) Article 15 of RTS 22 makes their job very easy! Recent regulation, whether it be the Dodd Frank Act (DFA) in the US or EMIR in Europe, has become increasingly prescriptive of the controls expected of participating firms. Article 15 takes this prescriptive nature into a different league, placing testing and reconciliations front and centre.

    MiFIR (Article 26(7)) requires firms to verify the completeness, accuracy and timeliness of the transaction reports they submit. RTS 22 expands on this and explains that complete and accurate reporting data is essential to market surveillance and outlines how that is to be achieved.

    Under the first section of Article 15 there are the usual requirements relating to the security and functionality of data and measures to enable timely resumption of reporting when reporting systems go down and measures to identify errors and omissions.  More specifically there is requirement on firms to have mechanisms to avoid duplicate reporting and under reporting.

    Whereas over-reporting is tolerated under current obligations, reporting transactions where there is no obligation is not permitted and Article 15 says firms will need to have mechanisms in place to identify over-reporting.  Over-reporting is the submission of a transaction report where it is not required under the reporting rules.  This can be reporting a trade on an instrument that is not reportable or reporting a transaction on a non-reportable event such as dividend reinvestment.

    When firms become aware of any of these types of errors or omissions they need to be reported to the relevant competent authority. To that end ESMA mandates not only reconciliations but specifies the data sources and fields to be included; reconciliations should be between front office trading records and information contained in transaction reports and checks should be in place to prove the timeliness of reports and the accuracy and completeness of all the individual data fields.

    In tandem with regular reconciliations, Article 15 states that firms are required to put in place a testing methodology and approach for their reporting processes. The multimillion pound fines issued by the Financial Conduct Authority for transaction reporting breaches over the last five years have often been on transactions which have been reported as valid and been through some form of reconciliation process but ultimately have still breached Chapter 17 requirements of the supervisory manual.  It is these breaches that your testing approach must be able to identify.  The often piecemeal, sample-based testing that is common in firms today will not be satisfactory.

    Kaizen Reporting’s testing approaches are setting the industry standard and will enable you to meet your MiFID II requirements efficiently and cost effectively. We combine unrivalled regulatory knowledge with the latest data analytics to provide the highest level of confidence in transaction reporting. 

  • EMIR level 2 validations – are you ready?

    EMIR level 2 validations – are you ready?

    At the end of October ESMA is introducing new validations to be applied by Trade Repositories (TRs) which I think will be a good thing for reporting quality.  In this article I provide some context to the changes, but contend that validation on its own is not enough to deliver quality reporting.  Validations cannot identify records that are valid but wrong.  For that we need a much smarter approach.

    ESMA and national competent authorities have expressed concerns around the quality of reporting today and they expect firms to address this.  But to promote quality ESMA has taken its first step towards improvement with the introduction of additional validations.

    Some background

    ESMA originally required the TRs to apply very limited validations to EMIR reports. The idea was that the TRs would not reject records because of problems in data quality and submissions would not be delayed by problems with one or more data fields within the report.  Therefore ESMA and other regulators would have access to the data that was available irrespective of quality.

    This approach makes more sense the more data that is submitted with each record.  The reason is that with strict validation, a single error in one field would prevent the remaining data from being received by the TR.  However, this approach requires the reporting entity to have a strong control framework in place to ensure that errors are self-identified and rectified.

    The limited validation approach initially adopted by ESMA differs markedly from that taken for Transaction Reporting.  On launch of the Approved Reporting Mechanisms (ARMs) regime in November 2007 a detailed set of strict validations was specified by the FSA (now the FCA) to be in place before an ARM would receive authorisation. These validations are applied by the ARMs to all records submitted by reporting firms and if the record failed a validation it would be rejected by the ARM and the firm notified.  I am calling this approach strict validation.  Many firms apply their own validations prior to submitting their records to an ARM and the FCA also applies strict validation at the point of receipt creating multiple layers of strict validation the vast majority of which is duplicative.  So we see very low industry rejection rates for reports sent by ARMs to the FCA.

    Benefits of strict validation

    The primary benefit of strict validation is that the submitting firm keeps ‘holding the baby’, i.e. they know when their submission has failed and will be in breach of the timeliness obligations.  They are in effect forced to act to remedy the problem.  The reporting entity does not need to have a good control framework in place to know that they have a problem that needs fixing.

    ESMA has now undertaken a volte face and now requires the TRs to apply strict validations.  Nearly every field is subject to some sort of validation requirement per the L2 validations.

    The change in validation approach clearly introduces new challenges and costs for firms as well as the TRs.  These validations would have been better implemented before EMIR go-live, but it has taken the experience of poor quality data to crystalise this decision.

    So what should firms be doing to prepare?

    There is the immediate problem of ensuring that you will be able to continue to report post October.  That means assessing the impact of the new validations on existing positions and correcting in advance any errors that would result in updates to those positions being rejected.  Similarly, firms should consider whether their process for dealing with rejections can handle an increase in volumes particularly in the early period.

    More than that, firms should be looking at how to identify records that are valid but wrong.  This requires testing of the EMIR reports at the Trade Repository and reviewing the adequacy of their control framework over EMIR reporting more generally.  Errors can be introduced into the reporting process or are a result of an incorrect interpretation of the reporting requirements so care must be taken to ensure that the testing that is conducted doesn’t build in the same interpretation errors.

    More can be said on testing but I will leave that for another post. If you have any views on the above I would be keen to hear them.