Category: EMIR Reporting

The European Market Infrastructure Regulation (EMIR) is a body of legislation for over-the-counter (OTC) derivatives, central counterparties and trade repositories. EMIR requires the reporting of all derivatives, whether OTC or exchange traded, to a trade repository. Check out Kaizen’s insights into EMIR reporting.

  • EMIR Inter-TR reconciliations in the EU and UK: what firms need to know ahead of April and September deadlines

    EMIR Inter-TR reconciliations in the EU and UK: what firms need to know ahead of April and September deadlines

    Two years on from the go-live of EMIR Refit, additional Inter-TR (trade repository) reconciliation requirements are coming into force for firms operating under EU EMIR and UK EMIR. The upcoming EU deadline at the end of April is followed by the UK in September.

    EMIR Refit’s reconciliation requirements were introduced in a phased approach:

    • Phase 1 fields – went live at the start of EMIR Refit (approx. 80 fields)
    • Phase 2 fields – two years on from go-live, a further 61 fields, bringing the total number of reconcilable fields to 148.

    What are Inter-TR reconciliations?

    Inter-TR reconciliations require trade repositories to compare derivatives reports submitted across different TRs to ensure consistency between counterparties for the same trade. Where both sides of a trade are reported to different repositories, regulators expect certain data fields to match.

    Many of these additional ‘phase 2’ fields, particularly valuation and lifecycle-related data, bring stricter matching requirements, with many requiring exact alignment between counterparties.

    In practice, this means more data to get right, less tolerance for differences, and a much higher likelihood of reconciliation breaks if firms are not fully aligned.

    Why this matters now

    Regulators have been clear that data quality remains a significant issue, and that they are using EMIR data (and that of other regulatory reporting regimes) not just to detect systemic risk but for a much wider set of supervisory measures and policies. Pairing rates, field consistency, and lifecycle reporting often fall short of regulatory expectations which is consistent with the outcomes seen in our own testing of hundreds of firms’ data.

    Inter-TR reconciliation is designed to address this by:

    • Identifying mismatches between counterparties
    • Highlighting systemic data quality issues
    • Increasing transparency across the reporting ecosystem.

    For firms, this introduces a new level of visibility. Errors that may previously have gone unnoticed internally will now be surfaced externally.

    Key challenges firms will face

    • Data alignment across counterparties

    With a significantly expanded data set under EMIR Refit, aligning reporting interpretations across counterparties becomes more complex. Even small differences, such as formatting, timing, or field population, can result in reconciliation breaks.

    • Lifecycle event consistency

    Lifecycle events remain a key challenge. Amendments, compressions, and terminations must now be reported consistently across both sides of the trade and across repositories.

    As more lifecycle-related fields are brought into scope for reconciliation, firms without strong controls in this area are likely to see a growing volume of breaks.

    • UTI and pairing accuracy

    Accurate UTI generation and sharing is critical. Failures here will directly impact pairing rates, which underpin successful reconciliation. Firms should not assume that existing UTI processes will hold up under increased scrutiny.

    • Operational readiness

    Inter-TR reconciliation introduces new workflows, including exception management and remediation. With a larger volume of reconciled fields, firms should expect a corresponding increase in breaks particularly in the early stages. Clear ownership, prioritisation frameworks, and scalable processes will be essential.

    What does good look like?

    Firms that approach inter-TR reconciliation effectively will focus on three key areas:

    • Proactive testing of data to catch issues before submission
    • Counterparty engagement to align on reporting approaches
    • Structured exception management to investigate and resolve breaks efficiently.

    Final thoughts

    Inter-TR reconciliation is a clear signal that regulators are moving towards a more data-driven, holistic view of reporting compliance. For firms, the challenge is no longer just to report but to report consistently, accurately, and in alignment with counterparties. With deadlines fast approaching, now is the time to ensure that reconciliation processes are robust enough to stand up to this new level of scrutiny.

    Kaizen’s Completeness Controls provide a comprehensive, independent reconciliation from source system data to reports made to end points, covering eligibility, reportability, pairing and matching, and timeliness. Contact us for a demo of our platform or for a conversation with Tim or one of our regulatory experts.

  • Kaizen returns to Eurex Derivatives Forum 2026

    Kaizen returns to Eurex Derivatives Forum 2026

    Date: 25 and 26 February | Location: Congress Center Messe Frankfurt | Hear us speak: 13:40, 25 February in breakout room: Illusion 3

    We are delighted to be returning to Frankfurt for the leading European event focused on trading and clearing for derivatives across asset classes. 

    On Wednesday 25 February from 13:40, we hope you can join Matthew Vincent, Managing Director, Tim Hartley, EMIR Reporting Director and John Graham, Senior Director of Regulation, FIA for a deep dive session into Regulatory Reporting in Transition. 

    The regulatory reporting landscape is undergoing significant transformation, with firms expected to manage evolving requirements while maintaining high-quality, accurate submissions. This session will examine ESMA’s latest updates to EMIR and MiFIR reporting, focusing on both the practical challenges and the opportunities arising from these changes. In this session, speakers will:

    • Break down the latest ESMA updates, including key changes to EMIR and MiFIR reporting requirements
    • Explore the wider regulatory reporting landscape, focusing on implementation challenges, supervisory expectations, and data-quality considerations
    • Share practical and actionable insights to help firms prepare effectively for the upcoming changes and strengthen their reporting frameworks.

    You can find the team in the exhibit hall throughout.

    Redeem your free ticket using code: Kaizen-DFF

    Register

  • ESMA’s Data Quality report (EMIR) – five critical takeaways

    ESMA’s Data Quality report (EMIR) – five critical takeaways

    During April, ESMA released the latest version of its EMIR and SFTR Data Quality report.  Kaizen’s Jonathan Lee commented on the SFTR elements in an earlier blog. Below we take a deep dive into the key takeaways regarding EMIR Reporting.

    1. Valuation and collateral submissions are a hot topic for ESMA

    Using a simple word count, collateral and valuations are mentioned more than any other topic in this report.  Collateral and valuation reporting is a daily requirement for Financial Counterparties (FCs) and Non-Financial Counterparties that are above the clearing threshold for OTC trading (NFC+s).

    ESMA stresses the ‘importance of valuation data for economic and financial risk analysis’, evidencing what is clearly a key component of EMIR Reporting and a continuing area of scrutiny for authorities.

    The report highlights that ‘more than 20%’ of open derivatives do not receive an updated valuation, despite the clear reporting requirement to do so.  As mentioned in Jonathan Lee’s SFTR analysis, many of the metrics included are ‘flawed’, including this ‘20%’ figure, as the sample analysis only took into account derivatives with valuations over 15 days old, rather than those over one day old.  As part of their daily reporting requirement, firms are expected to provide collateral and valuation updates every day, and if this is truly a key focus for ESMA, future analysis would be far more accurate (and more damning), if it followed the actual reporting requirement.  For this reason, it is a fair assumption that far more than 20% of open derivatives are not receiving daily collateral or valuation updates.

    Firms would be wise to note this important discrepancy and ensure that all collateral and valuation reporting reflects the daily reporting requirement ahead of future iterations of the report. More importantly, ensure all collateral and valuation reporting is accurate ahead of enhanced scrutiny by regulators for this key area of EMIR reporting.

    2. Pairing remains a problem for EMIR Reporting

    An important issue the report highlights is the lack of successful reconciliation.  An important and telling statistic is that only ‘60%’ of pair-able submissions do successfully pair.  This shows an upward trend from 40% to 53% and now 60%, since ESMA began tracking the yearly statistic.

    The pairing phase of reconciling the two sides to each derivative relies on the reporting counterparty LEI, other counterparty LEI and the UTI to create a unique ID for that submission. These allow the trade repositories to search for the other report submission pertaining to the same derivative.  Only derivatives where both sides are required to be reported in the same jurisdiction are included in these statistics.

    The whopping 40% of all reportable derivatives that fail to pair will be due to a limited range of factors, such as one counterparty having not reported the derivative successfully, one or both counterparties reporting with an incorrect LEI or UTI, disagreement on the number of trades to be reported for that derivative, and finally, general processing issues within the trade repository pairing process.

    ESMA condemns this large volume of unpaired derivatives as ‘not satisfactory’, notably as the reporting of these fields has been mandatory since reporting began in 2014.

    The pairing of derivatives is vital to the success and efficiency of EMIR Reporting, which is inherently focused on the level of risk and exposure in the market.  If two successful reporting submissions for the same derivative do not include the correct identifiers to enable pairing, the authorities will simply think that two unrelated single sided submissions have been completed, and that they are (incorrectly) awaiting the other side of the derivative to be reported.  Not only is this poor from a completeness and accuracy point of view, but vitally the exposure could potentially be seen as double the volume of market risk currently live for both counterparties and the economy at large.

    3. Data provided to the NCAs isn’t always the same as data provided to ESMA

    Generally, the data reported to the trade repository is the regulator’s view of derivative activity at each firm.  NCAs view the specific sections of EMIR data that they have been mandated to view, and ESMA has the ability to see all data, due to its regulatory oversight of EMIR Reporting for EEA firms.

    However, the report highlights that data is provided to the various authorities in different ways, such as ‘TRACE’ or via sFTP.  Also highlighted was the admission that when the trade repositories allocate data to each NCA, this does not necessarily match what ESMA believes the NCA should see, resulting in both over and under reporting of data to the NCAs.

    Whilst this finding does not impact the ability of counterparties to submit reports successfully, it does limit the ability of NCAs to efficiently supervise all firms to which they are mandated. And in practical terms it is extremely hard for an NCA to identify such shortcomings in the quality of data that they have been provided.

    4. Non-reporting and timeliness of reports

    Approximately ‘10%’ of the sample of EMIR reporting tested under the report are reported late by counterparties.  Non-reporting dropped sharply to ‘5%’ but this figure is likely to be due to Brexit splitting the two EMIR Reporting regimes across EEA and UK based firms.  Again, this is a good example of a likely ‘flawed’ metric used in this report.

    Strangely the analysis does not take into account the conversion from local to UTC Coordinated Universal Time, despite UTC being a well-used reporting format under many EMIR fields, including reporting timestamp.  Further to this, the analysis does not take into account ‘public, bank or national’ holidays, even though ESMA admits in this report and other sources that they should be taken into account and adding to the flawed nature of many metrics included in this report.  As previously argued, such analysis should absolutely follow the reporting requirement to which firms are required to adhere to, instead of ‘moving the goal posts’ for the ease of data analysis.

    The report also mentions the sharp decline in non-reports to less than ‘5%’, but admits that this has been dramatically impacted by Brexit (reported derivatives dropped ‘by 50%’) which split the reporting requirement into two separate EMIR jurisdictions.  For this reason, it is worth noting that it is now significantly harder to gauge an accurate view on non-reporting for the same derivatives, where counterparties are split across the EEA and UK.

    5. ESMA has great expectations for all impacted bodies

    The final key takeaway from the report is that a lot more is explicitly expected from all stakeholders of EMIR Reporting.

    For reporting counterparties, ESMA includes strong language on the expectations of firms, namely that they are expected to have all necessary checks and balances in place ‘to ensure completeness, accuracy and timeliness’ of reported derivatives.  In addition, firms are expected to ‘actively engage’ in identifying and remediating any report rejections, reconciliation breaks, and other data quality issues for ‘already reported data’.

    In short, firms are required to take ownership and ensure high quality data for both new submissions and anything previously reported.  Importantly, this will include all delegated reporting, remembering that even if firms delegate the action of reporting, the obligation of reporting remains with the counterparty to the derivative.  In addition, it will also impact firms required to perform what has informally become known as ‘mandatory delegated reporting’, where an FC has executed an OTC derivative facing an NFC- in the same reporting jurisdiction.

    For the authorities, they have an explicit commitment to continue perusing improved data quality under EMIR.  ESMA and the NCAs ‘will take further action’ to improve the quality of data where ‘insufficient quality’ has been identified and prevails.Q

    And finally for trade repositories, they have been identified as required to increase the quality of reports provided to the NCAs, as well as ensuring the consistency and accountability across standard ‘end of day reports’ to firms, such as the ‘trade state report’ and the ‘trade activity report’.

    What’s next?

    In summary, the report continues data quality themes initiated in last year’s report, but with renewed vigour, more examples of wrongdoing, and arguably significantly stronger wording from ESMA. 

    Valuations and collateral reporting will be a key focus of NCA scrutiny over the next 12 months, and firms would be wise to prioritise this in their data accuracy reviews, not only of future reporting, but also of any historical submissions to the trade repository.

    We welcome the focus of such reports, but are keen to see future versions encompass all reporting requirements, and importantly, we urge ESMA to ensure that all metrics at least mirror the prescribed reporting requirements, instead of being influenced by ease of calculation. 

    And finally, we are very keen to see the same style of scrutiny for UK EMIR reporting from the FCA, giving UK firms ample opportunity to review any reporting shortcomings ahead of the looming EMIR Refit changes for derivatives reporting. 

    Read the consultation paper on the FCA’s website.

    • Do you know the true state of your EMIR reporting data quality? If you are in any doubt about how the quality of your EMIR trade and position level reports measure up, please contact us.
  • EMIR, MiFIR, SFTR Reporting Core Training – new course dates announced

    EMIR, MiFIR, SFTR Reporting Core Training – new course dates announced

    We’re pleased to announce new dates for our CPD-accredited EMIR, SFTR and MiFID/MiFIR Reporting Core Training Courses which we are delivering remotely. 

    Developed and delivered by our regulatory specialists David Nowell (EMIR and MiFIR) and Jonathan Lee (SFTR), these popular half-day courses are also at a significantly discounted price for a limited time only!

    Click on the links below for more details and to book your place.

    Training is an integral part of the systems and controls that firms need to have in place around reporting. Despite the coronavirus pandemic, regulators have made it clear that they are monitoring the quality of regulatory reports closely. 

    If you have any questions about our training courses or for enquiries about bespoke options, please email our Training Team. 

  • LISTEN: Kaizen CEO Dario Crispini on The Regis-TR RoundUp podcast

    Tune in to Dario Crispini on Episode 4 of The Regis-TR RoundUp!

    Dario covers off his early days at the UK regulator, the FSA (now FCA) and the launch of MiFID reporting. He also discusses whether the EMIR Refit can really make EMIR an effective early warning system for global financial crises, and how to prepare for the delayed SFTR roll-out and the problems it could cause for both market participants and regulators.

    The podcast also highlights the incredible efforts of Kaizen’s James Deehan in rowing 3,000 miles across the Atlantic to raise money for the Teenage Cancer Trust.

    Click on the green arrow below to listen!


     

  • EMIR: Lies, damned lies and trade repository statistics

    EMIR: Lies, damned lies and trade repository statistics

    Earlier this month ESMA published its Supervision Annual Report 2019 and Work Programme 2020. These reports are always interesting to gauge ESMA’s view on the adequacy of the quality of trade data reports (and what it’s going to do about it if the data doesn’t reach the required standard).

    How to measure EMIR reporting data quality

    ESMA describes the pairing and matching process as “one of the key data quality processes”. EMIR is a two-sided reporting obligation, i.e. both counterparties to a trade have to report their ‘version’ of the trade. If both sides report it with the same unique trade identifier and counterparty identifiers, then it will ‘pair’. If both parties report with the same common data attributes (such as quantity and price), then it will ‘match’. Clearly, if the trades don’t pair or match, then there is a data quality problem with the report from one or both of the counterparties.

    So the pairing and matching statistics are key data quality metric. Unfortunately, the pairing and matching rates quoted in the report – 59% and 29% respectively – might suggest the quality of the reports is not up to the required standard.

    Is EMIR reporting data quality improving?

    In its 2018 Annual Report, ESMA stated that, as of September 2018, the average pairing rate across trade repositories (TRs) was 86%. We also know from a Freedom of Information request, that the average matching rate was 40%. This suggests that the quality of trade reports has decreased substantially. However, this is where we need to consider Disraeli’s view of “lies, damned lies and statistics” and be very careful with the story they tell. The 2018 pairing figure was derived from information provided by TRs and measured the rates against trade reports. The 2019 figure in the latest report is actually derived by ESMA based on the ‘trade state reports’ at a single point in time, so we are not comparing data produced using the same methodology.

    Use of the trade state report (TSR) is a very interesting choice. The TSR, as the name suggests, is the latest state of a trade, taking into consideration subsequent modifications such as partial terminations. It sounds like a sensible methodology, but it has a big issue when it comes to exchange traded derivatives (ETDs). Unlike most OTC derivatives, ETD trades are immediately netted into a position level report. So the TSR for an ETD is actually a position level report rather than a trade level report. The significance of this is that, unlike trade reports, there is no agreement yet between the counterparties on what UTI to use on a position level report. Therefore, there is a significant probability (I calculate it at 85.256%) that the pairing rates for ETDs is very low.

    However, there is a more important issue related to these statistics (both pairing and matching) – do they or do they not include delegated reports? With delegated reporting, one party reports on behalf of both counterparties – ie. it would be difficult for the reporting counterparty not to report trades that both pair and match. So, for the statistics to not be potentially misleading, we need to know the pairing and matching rates for non-delegated reporting.

    Another interesting statistic in the annual report is the top reason for non-matching fields. Bearing in mind that these top ten breaks are for TSRs as of 9 August 2019, some of the fields, such as Product_ID_2 haven’t existed since November 2017. It is unclear what value offering statistics against fields that can no longer be corrected, actually delivers.

    What is the true state of EMIR reporting data quality?

    At Kaizen, our ReportShield™ assurance services test every field in every single trade state report to ensure that they are populated in accordance with the regulatory technical standards and the ESMA Q&A. We can also test the consistency of all the trade reports submitted against the actual values of the position level report.

    If you are in any doubt about how the quality of your EMIR trade and position level reports measure up, contact us. 

 
  • Trade associations publish EMIR reporting ‘best practices’

    Trade associations publish EMIR reporting ‘best practices’

    The trade associations ISDA, EFAMA, EVIA, FIA, GFMA, and GFXD have published ‘Best practice’ guidance for firms on how to populate fields in EMIR trade and position reports. The best practices, released on 3 March, cover both OTC and ETD “and were developed to improve the accuracy and efficiency of trade reporting and to reduce compliance costs”.  If firms follow the new guidance it should also improve the matching rates between the counterparties when they submit a report referencing the same trade (both counterparties have to report their version of the trade and ESMA uses the ‘match’ statistics as a quality indicator).

    The trade association initiative should therefore be applauded as many firms believe there are gaps in the regulatory technical standards and the ESMA Q&A that require the firms to make an interpretation on how the field should be populated. Historically, the matching rates have been disappointing and the new best practices document should help them arrive at the same interpretation of how the fields should be populated resulting in an improvement in matching rates.  However, a number of issues remain:

    Legal status of the best practice document

    In short, it has no legal status as it is not endorsed by ESMA. So although it is a very helpful as an educational document for the industry and it should help improve the matching rates, there is no guarantee that the regulators will consider all the interpretations to be correct (although the trade associations have discussed the best practice document with regulators).

    Potential contradictions with the ESMA requirements (e.g. Clearing member ID)

    This is a difficult one. For example, take ‘Clearing Member ID’. The trade association best practice for ETDs is that this field shall only be populated in instances where the reporting party is not the clearing member. This makes perfect sense to me. Unfortunately, ESMA’s Q&A answers the question: If a counterparty is itself the Clearing Member (CM) to a trade, should it be reported in both the “counterparty” and “CM” fields?” with ‘yes’.  Since the trade association best practice seems aligned with the RTS, rather than the Q&A, perhaps it’s safe to follow best practice.

    However, there are other instances where there seems to be divergence from the Q&A that doesn’t have the clear and obvious support of the RTS. For example, the ETD best practice for deliverable currency is that it should only be populated where the asset class is ‘CU’ for currency. Again, this seems sensible, but TR Q 47 says the field should be populated ‘for all single currency derivatives, as well as those with a specific FX component.’

    Gaps in the best practice document

    Whilst the document provides best practices for many fields, it is not comprehensive. For many fields, best practice is not required – for example, it should be obvious to all how to populate ‘Reporting counterparty ID’ (although we still see a number of errors with this field!). There are a number of others, such as ‘Beneficiary’. ‘Report Tracking Number’ and the infamous ‘Position Level UTI’, where best practice is required. However, trade associations need to complete discussions with ESMA before they can provide best practice for all fields.

    Will all participants adopt the best practices?

    Best practices will only increase the matching statistics if all participants follow them. It is impressive that seven major trade associations have reached agreement on best practices for a number of the fields. However, not all participants will be represented by these trade associations. For example, the CCPs may have differing views. Perhaps this is best evidenced with the ‘Maturity Date’ field where the best practices document notes: “Reporting firms populate this field with the ‘last trade date’ which conflicts with CCP’s interpretation of this field. Most CCPs populate this field with ‘settlement date’.  Regulatory guidance required.”

    So in our view the best practices document is a valuable tool to help firms increase the quality and matching rates of their EMIR trade reports. However it is not a panacea for the myriad of EMIR trade reporting difficulties. As we have said before there are some fundamental issues that make EMIR trade reporting more of a burden than it should be for firms and less valuable than it should be for regulators.

    If your EMIR reporting isn’t up to best practice, we can help. Please get in touch for a conversation with one of our regulatory experts to find out more.

    Our EMIR reporting core training courses also cover all aspects of the reporting requirements to gain an excellent overall understanding of the scope, drivers, trading scenarios and key fields that make up an EMIR report.  Book your place now.

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

    Post-Brexit regulatory reporting wish list: EMIR trade reporting

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

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

    1. Eliminating trade reporting for ETDs

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

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

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

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

    1. ‘Beneficiary’

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

    1. Reporting Timestamp

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

    1. Trading Capacity

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

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

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

    1. Country of the other counterparty

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

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

    1. Basket derivatives

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

    1. Duplicate fields

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

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

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

     

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

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

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

  • SMCR: Five key questions to ask on regulatory reporting

    SMCR: Five key questions to ask on regulatory reporting

    The Senior Managers and Certification Regime (SM&CR or SMCR) goes live today for buy-side organisations and other solo regulated firms*. The regime has been in operation for the past few years for banks, building societies, credit unions and branches of foreign banks operating in the UK and the largest investment firms regulated by the PRA and FCA.

    Regulatory reporting controls, governance and ultimately sign off will be key to senior managers in these firms as they take on the additional responsibilities of SMCR. If this is you, what do you need to do from a regulatory reporting perspective? Here are five questions you should be able to answer:

    1. What category is my firm in?  You need to understand the three types of categorisation under the senior managers regime (Limited Scope, Core or Enhanced) and the certification regime, as well as the conduct rules that will apply to the rest of employees’ monitoring and auditing activities.
    2. Have my Senior Management Functions (SMFs) been properly trained? Most functions will be the same as under the previous Approved Persons Regime but have they been trained to understand the responsibility and consequences of their actions?
    3. Is our governance now in line with SMCR?  Are the right procedures & policies and controls in place for recording the implementations, steps and the decisions made by your firm to comply with the regulation?
    4. Have I mapped out my management responsibilities? Who is impacted (e.g. Head of Legal is not) and what Controlled Functions have transferred to SMFs?
    5. Am I protected? We have seen firms fined under various regulatory regimes such as MiFID and EMIR but there have been few penalties or consequences directly for the executives within those firms – yet. With SMCR making individual senior managers within firms accountable, our services can provide you with peace of mind that you have the right controls in place to meet your regulatory reporting requirements and reduce your regulatory risk.

    Join in the conversation over on our LinkedIn.

    More information: https://www.fca.org.uk/firms/senior-managers-certification-regime

    *These include investment firms – brokers, securities firms, asset managers, financial advisers.

  • Kaizen Reporting wins Regulatory Reporting Product of the Year

    Kaizen Reporting wins Regulatory Reporting Product of the Year

    FOR IMMEDIATE RELEASE

    27 November 2019, London: Leading regulatory reporting firm Kaizen Reporting, developer of the multi-award-winning assurance service, ReportShield™, announced today that it has won ‘Regulatory Reporting Product of the Year’ at the Risk Markets Technology Awards 2020. Hosted and run by Risk, the awards were set up in order to recognise market-leading technologies and third-party vendors that enable sell-side firms to operate more efficiently and transparently.

    The 2020 awards drew 180 pitches across nearly 30 categories and recognised companies that were able to demonstrate they had responded to the market’s changing needs. The winners were decided by a panel of nine global industry experts and two from the Risk.net editorial team.

    Dario Crispini, CEO of Kaizen Reporting, commented: “At Kaizen our aim is to transform the quality of regulatory reporting data through providing our customers with the best possible solutions when it comes to trade and transaction reporting. The continued enhancements and services we have introduced in the past year show our commitment to our customers and in retaining our reputation as an industry-leader in reporting services and RegTech solutions.”

    The award caps off a fantastic month of accolades for Kaizen. Yesterday it was announced it had been selected as one of the world’s most innovative RegTech companies for the second year in a row in the prestigious RegTech 100 listing. Earlier in the month, it was also recognised with the Regulation Asia award for Data Assurance in Singapore.

    Kaizen’s ReportShield™ is a set of services that act as a shield against reporting issues, helping investment firms to meet their reporting obligations and effectively manage their reporting risks. The service includes a number of controls required for complete and accurate trade and transaction reporting including Kaizen’s flagship accuracy testing, advanced regulatory reconciliation service and testing of reference data.

    (ends)

    For media inquiries, please contact Fiona Wilde on media@kaizenreporting.com or +44 (0) 20 3912 3271.

  • Kaizen Reporting “one of the world’s most innovative RegTech firms” for second year

    Kaizen Reporting “one of the world’s most innovative RegTech firms” for second year

    FOR IMMEDIATE RELEASE

    26 November 2019, London: Leading regulatory technology firm, Kaizen Reporting today announced that it has been selected for the RegTech 100 listing, an exclusive directory of the world’s leading RegTech companies, for the second year in a row. The RegTech 100 companies were chosen by a panel of analysts and industry experts as the world’s best solution providers that address the challenges and opportunities of dealing with regulatory issues within financial services.

    Chosen from a longlist of over 1,000 companies, Kaizen was selected for its innovative solutions for trade and transaction reporting. The company’s ReportShield™ quality assurance services combine regulatory expertise and advanced technology to deliver a full assessment of regulatory reporting quality.  Many financial firms use ReportShield™ to assess the quality of their data for reporting regimes such as MiFIR, EMIR, Dodd Frank, MAS, Canada and HKMA reporting as well as the upcoming SFTR regime.

    Dario Crispini, CEO of Kaizen Reporting, said, “We are delighted to have been included in the RegTech 100 list for the second consecutive year. Being listed again is a real honour and testament to our team here at Kaizen who have worked so hard to put us at the forefront of the RegTech sector.”

    Mariyan Dimitrov, head of research at RegTech Analyst, said, “Having reviewed over 1,000 RegTech companies from around the world, Kaizen Reporting stood out as a worthy contender for this year’s RegTech 100. The services they offer and their all-encompassing testing method allows clients to see the full picture of the quality of their trade and transaction reporting.”

    Kaizen’s ReportShield™ is a set of services that act as a shield against reporting issues, helping investment firms meet their reporting obligations and manage their reporting risks effectively. ReportShield™ includes a number of controls required for complete and accurate reporting including Kaizen’s flagship accuracy testing, advanced regulatory reconciliation service and reference data testing.

    Earlier this month, Kaizen was also recognised with a Regulation Asia Award for Excellence for Data Assurance in Singapore.

    (ends)

    For media inquiries, please contact Fiona Wilde on media@kaizenreporting.com or +44 (0) 20 3912 3271.

  • FCA to increase its scrutiny of EMIR reporting

    FCA to increase its scrutiny of EMIR reporting

    The FCA is likely to increase its focus on EMIR trade reporting quality in response to a recent report from ESMA that criticises the regulator’s approach. In its response to the criticism, the FCA has said it is revising its EMIR data quality strategy which will include the creation of a new central data quality team and the upgrading of its cloud infrastructure to receive EMIR data and check for quality issues.

    What’s the background?

    A recent report from ESMA has concluded that there are number of insufficient supervisory controls over the quality of the FCA’s EMIR data. The FCA was not the only NCA called out – six were assessed. ESMA’s findings will probably not have come as a surprise to many firms. UK firms are used to the FCA being extremely proactive in monitoring the quality of MiFID II transaction reporting however as we’ve pointed out previously, less so with EMIR.

    But isn’t EMIR more important than MiFID II?

    EMIR reporting should be considered as the most important regulatory reporting requirement as it is designed to help regulators monitor for systemic risk – ie. helping to ensure that there is not a collapse of the entire financial system. So it is essential that the regulators have a strong supervisory regime to ensure that the quality of the data reported by firms is sufficient to enable the guardians of financial stability to perform their functions. In a statement contained in ESMA’s Final Report, the FCA rightly points out that it is the Bank of England that is largely responsible for financial stability in the UK, so there are more limited ways in which EMIR data can be integrated into its overall supervisory approach.

    What does the FCA do currently?

    Just over two years ago, the FCA issued a fine of £34.5m to an investment firm for failing to comply with Article 9 of EMIR. This is the only fine it has issued so far for the regime. There is also a requirement on firms to report breaches. However, there is a telling story on the number of error forms submitted to the FCA: earlier this year following an FOI request, the FCA confirmed to us that it received notifications from 384 firms for MiFID II transaction reporting breaches since go-live compared to just 75 for EMIR trade reporting in the period since Q2 2018 when the EMIR breach form became available.  

    When you consider that around 9,000 UK entities have an EMIR reporting obligation and 3,000 UK entities have a MiFID II reporting obligation, this statistic becomes even more concerning.  We can say with confidence that this is most definitely not because UK firms’ EMIR reporting is better than their MiFID II transaction reporting. For example,  in our quality assurance testing we detect a significantly larger amount of errors in the EMIR reports than we do in the MiFID II transaction reports.

    What should firms do?

    Be prepared for a far more intrusive investigation of your EMIR reports. Our advice is to look at your EMIR reporting now.  If you are unsure about the quality of your EMIR reports, or just want to know how good – or bad – your reporting is, then this is why we here at Kaizen exist. Our ReportShield™ testing services have been developed to provide a full assessment the quality of your reporting.  Contact us for a discussion on how we can give you full transparency of your EMIR reporting quality.

    Read the ESMA report on its website.

  • Kaizen Reporting Wins Singapore Regtech Award for ReportShield™ Data Assurance Solution

    Kaizen Reporting Wins Singapore Regtech Award for ReportShield™ Data Assurance Solution

    FOR IMMEDIATE RELEASE

    14 November 2019, London – Kaizen Reporting is delighted to announce it has won the Regtech Award for Data Assurance in the 2nd Regulation Asia Awards for Excellence 2019 at a ceremony in Singapore.

    Following a rigorous selection process involving a judging panel of subject-matter experts and the Regulation Asia editorial team, Kaizen Reporting emerged as the category winner for its ReportShield™ quality assurance solution, a set of services developed to solve the problem of poor quality regulatory reporting. The solution is unique in its all-encompassing testing approach which fully assesses the quality of data that firms have reported to the regulator.

    One judge called the service “one-of-a-kind”. Multiple users have attested to its effectiveness in helping to ensure higher quality data in regulatory reports. According to one user, regulators have also provided “extremely positive” feedback on the data assurance processes applied.

    Ian Rennie, Managing Director of Kaizen Reporting (pictured) said, “We are honoured that Kaizen has been recognised in the Regulation Asia Awards for Excellence. Complete and accurate regulatory reporting is expected by regulators across the region and globally and we are delighted that our automated testing services are helping clients meet regulatory expectations and providing them with peace of mind in their reporting quality.”

    Brad Maclean, Co-founder and Executive Chairman, Regulation Asia said: “Kaizen Reporting has developed a unique solution to address a wide range of issues around regulatory reporting. This award recognises the firm’s continued success in developing superior technology and helping firms navigate challenging data environments and ever-changing regulatory requirements.”

    Earlier this year Kaizen Reporting was also awarded Best Reporting Platform or Service for the Sell side at the Sell-side Technology Awards in London and Best Technology Provider for Regulatory Compliance by the Fintech and RegTech Global Awards. In 2017, Kaizen’s testing was recognised by the UK government with the Queen’s Award for Enterprise for innovation, one of the UK’s highest business accolades.

    About Kaizen Reporting

    Kaizen Reporting are regulatory reporting experts on a mission to improve the quality of reporting in the financial services industry. Kaizen has combined regulatory expertise with advanced technology develop its multi-award winning ReportShield™ quality assurance services which are unique in providing full visibility of reporting quality. Kaizen’s services are used by some of the world’s largest banks, asset managers, hedge funds and brokers. Whether it’s MiFIR, EMIR, MAS, HKMA, ASIC, Dodd Frank, SFTR or another G20 regulation, Kaizen helps its clients reduce costs, improve quality and increase confidence in their regulatory reporting.

    About the Regulation Asia Awards for Excellence 2019 

    Regulation Asia Awards for Excellence recognises technology companies, legal and consulting firms, and exchanges that have shaped the regulatory landscape in Asia Pacific, as well as outstanding technology projects both in mature and emerging markets by large tech firms and innovative startups that help meet the requirements of a specific regulatory change infrastructure. For a full list of award winners, visit www.regulationasia.com/awards.  

    For more information, please contact Fiona Wilde, Head of Communications, on +44 (0) 203 912 3271 or media@kaizenreporting.com

     

     

  • Look before you leap: Understanding the limitations of AI in the regulatory space

    Look before you leap: Understanding the limitations of AI in the regulatory space

    Last week I went to the Commodity Future Trading Commission (CFTC) in Washington DC to attend the Fintech Forward 2019 conference. I was grateful for the opportunity to speak on a panel about AI in the 21st Century Marketplace: Exploring the Role of AI and Related Fintech in CFTC Markets.

    Artificial Intelligence (AI) is an exciting tool that has shot to prominence in the last few years, with applications spanning the gamut from Snapchat filters and Spotify recommendations to sophisticated systems that catch fraudulent transactions or see the signs of lung cancer before expert radiologists. But how will AI impact the regulatory compliance space?

    AI and data quality: don’t get too excited

    At Kaizen we’re primarily concerned with helping firms check the data quality of the transaction reports that they have to submit under a variety of régimes from around the world such as MiFIR, EMIR and the Dodd-Frank Act. We have to be careful not to be too optimistic about the role AI can play in this. AI is most useful when we don’t exactly know the logic that a computer programme should be following, so we need the AI to ‘learn’ it from the data. But with regulatory reporting, the rules are clearly laid out – meaning that rule-based “expert systems” are the right technology for testing reports.

    Yet, despite the seemingly straightforward nature of accurate reporting, at Kaizen we’ve found that firms can commonly make errors in as many as 90% of records. Firms should be wary of “running before they can walk” by increasing the complexity of their reporting pipelines with AI while they are still making basic mistakes setting up their reporting systems.

    But AI can help with market integrity

    Where AI can really come into its own in regulatory compliance is market integrity – particularly safeguards against market abuse such as insider trading. Under the Market Abuse Regulation firms are required to monitor, detect and report suspicious transactions that take place on their platforms. Unlike with regulatory reporting, there are no hard-and-fast rules of what abusive trades look like. This is where the power of AI and machine learning (ML) can be brought to bear, learning how to find the anomalous needles in the gargantuan haystack of reported transactions.

    AI goes rogue

    At FinTech Forward I also commented on challenges that AI might pose for regulators and market participants. One big challenge regulators may face is the question of accountability: who is to blame if an AI ‘goes rogue’? The notion of a super intelligent AI that understands its actions still belongs in science fiction; contemporary AIs are really just mathematical models that extrapolate patterns, so the idea of holding an AI responsible itself is silly. It isn’t only the programmers who determine how an AI will behave; the AI can be heavily influenced by matters like what data fields the AI can ‘see’, what training data is in scope, and what metric for success the AI will use. Fundamentally, accountability for an AI need not be different from any other automated computer system.

    The challenges of algorithmic bias

    Another challenge for regulators is the issue of algorithmic bias – when an AI can behave unfairly in a systematic way, due to unintended problems with the training data or the question that was posed. One famous example is a recruitment AI that Amazon scrapped because it was unintentionally disfavouring women. Regulators that use AIs for enforcement have to be careful to minimize algorithmic bias. It isn’t only individuals who might get caught up. As a hypothetical example, if regulators only trained their AI on data from Tier 1 investment banks then they might end up unfairly over-flagging transactions from hedge funds.

    Black box models

    One problem for market participants who deploy AIs is the lack of interpretability for “black box” models. State-of-the-art AIs can have millions of parameters and it’s impossible to know what they’re doing, and this means it can be hard to quantify the risks. Moreover, the inherently adversarial aspect of market participation means that AI complexity is more of a risk than it would be in collaborative contexts such as self-driving cars – a counterparty’s AI might learn to persuade a black box AI to misprice securities, for example. Few market participants deploy AIs without a human in the loop.

    In the future, we’ll see AI play an ever increasing role in our lives, including finance and regulation. But as long as the technology is still in its infancy it’s important to temper the hype by understanding the limitations. Deploying AI systems has the potential to add huge value, but as always, firms should look before they leap.

    Watch Sam in action at Fintech Forward 2019.

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

  • Brexit – FCA Statement on EMIR Trade Reporting

    Brexit – FCA Statement on EMIR Trade Reporting

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

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

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

    Counterparties within scope of ‘UK EMIR’

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

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

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

    Inter TR Reconciliation

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

    Will this all work?

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

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

    Read the statement on the FCA website.

    ***

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

  • In the news: David Nowell speaks to Practice Insight

    In the news: David Nowell speaks to Practice Insight

    Our Senior Regulatory Reporting Specialist David Nowell recently spoke to Thomas Helm at Practice Insight for a special report on the accumulative impact of post-crisis reforms. In the report Thomas Helm joins the dots of transparency initiatives to reveal the bigger picture. David commented on data quality for the 124 data fields of EMIR trade reporting and the kind of errors we regularly see here at Kaizen. 

    “David Nowell says he frequently comes across errors, such as notional amounts in the “quintillions” in the Emir space, and that these errors can distort the public data aggregations. When compiling the public data aggregations we’d artificially disregard notionals above a certain level because they were obviously false, he says.

    Read the full report.         

  • 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 versus EMIR – which is the most important reporting regime?

    MiFIR versus EMIR – which is the most important reporting regime?

    There are many similarities between the MiFIR transaction reporting and EMIR trade reporting requirements. Both are T+1 reporting regimes and there is a large overlap in the instrument set that they cover. However, there are distinct regulatory drivers behind each regime: MiFIR transaction reporting is primarily used to detect market abuse whilst EMIR trade reporting is used primarily to monitor for systemic risk.

    There is no doubt that combating market abuse is a very important regulatory service; everybody benefits from clean markets. Complete and accurate transaction reports are vital to help the regulators perform this task effectively. However, systemic risk is even more important as it represents the risk of collapse of the entire financial system -there is no point monitoring for market abuse if the financial system has collapsed around you.

    It is very interesting therefore to compare the number of errors and omissions forms for MiFIR breaches against the number of equivalent forms for EMIR trade reporting breaches. Statistics from the UK Financial Conduct Authority (FCA) obtained through a Freedom of Information Act request show that it received notifications from 384 firms MiFIR transaction reporting breaches since go-live compared to a paltry 75 for EMIR trade reporting in the period since Q2 2018 when the EMIR breach form became available. So, it is tempting to believe that firms recognise the relative importance of EMIR trade reporting and are making greater efforts to ensure the accuracy of data they report. Sadly, this is not the case. At Kaizen, we perform data quality checks on firms’ transaction reports and trade reports. For EMIR we initially find that a much lower number of EMIR trade reports are accurate than compared with the MiFIR reports we test. This reflects the complexity of the reporting regime, but we find firms’ reporting quality rapidly improves once we have highlighted and explained the errors to them.

    So this presents an apparent anomaly. The evidence suggests the quality of EMIR trade reports is at a lower level than the quality of MiFIR transaction reports, yet over five times as many firms have notified the FCA of MiFIR transaction reporting errors than they have for EMIR trade reporting. It is not difficult to understand why this is the case; the FCA is constantly reminding the industry on the need to notify them of MiFIR transaction reporting breaches, and to correct those errors, but it appears to be comparatively silent on the need to notify them of EMIR reporting breaches. What is more difficult to understand is why the FCA appears to be less active in meeting its G20 commitments in ensuring the same level of high quality in EMIR trade reporting data.

    If you’re concerned about the quality of your MiFIR transaction reporting data or EMIR trade reporting data or would simply like confirmation that it is accurate and complete, please get in touch for a complementary consultation with one of our regulatory experts.

  • EMIR Refit – white elephant regulation

    EMIR Refit – white elephant regulation

    Many firms are waking up to the fact that ‘EMIR Refit’ is being implemented on 17 June 2019 and they may be having a coronary over how it might impact EMIR trade reporting. For once, firms can relax as the only big(ish) change for trade reporting takes effect from June 2020.

    Before diving into the detail, let’s take a step back and remind ourselves what EMIR Refit is all about.

    The aim of EMIR Refit is to make its compliance burden more proportionate, particularly for the non-financial counterparties (NFCs). Now that is an absolutely splendid aim, so how has it worked out with trade reporting? After the colossal amount of time spent on the debate, I have to conclude that it’s a massive disappointment for reporting, resulting in the following meagre pickings:

    1. Mandatory delegated reporting on behalf of NFC- firms from 18 June 2020. This is the only meaningful change from Refit. From 18 June 2020 (repeat 2020, not 2019) ‘financial counterparties’ will become responsible and legally liable for reporting the details of derivative contracts they have concluded with an NFC-  on behalf of both. The NFC- can still choose to report on its own behalf if it wants to, but it must give its counterparty notice of its intentions to avoid duplicative reporting.
    2. Removal of the back-loading obligation. There is no longer an obligation for counterparties to report historic data on derivatives that were outstanding on or after 16 August 2012 and which terminated before the EMIR reporting start date of 12 February 2014. This might sound like a welcome dispensation for the industry, but it wasn’t a very practical requirement in the first place – what possible value could the regulators extract from trades terminated five years in the past? The revised reporting technical standards also virtually forced this change as it is highly unlikely that any counterparty will have the required information to report these ancient trades in the post-2017 standards.
    3. Intra-Group Exemption – There may be too many conditions to be met for this to be of much use, but an exemption from the reporting obligation is available for intra-group transactions where all the following criteria are met:
      • at least one counterparty is an NFC;
      • both counterparties are fully consolidated;
      • both counterparties are subject to appropriate centralised risk evaluation, measurement and control procedures;
      • the parent undertaking is not a financial counterparty.

    Additionally, counterparties must notify their NCA of their intention to apply this exemption

    1. Fund management company reporting obligations. Fund management companies and Alternative Investment Fund Managers will become solely responsible and liable for reporting derivative trades made by their UCITS, AIFs and institutions for occupational retirement provision.

    Delegated reporting

    So the only substantial change to trade reporting introduced by EMIR Refit is the mandatory delegated reporting by financial counterparties on behalf of their NFC minuses. Although many financial counterparties provide delegated reporting already, they will be concerned by the addition of legal responsibility for the accuracy of the delegated reporting they provide. This concern may highlight one of the loopholes of EMIR trade reporting – although delegated reporting may boost the pairing rates, it might not actually be very good. There is a great temptation to simply ‘flip’ elements of a trade report and present this as delegated reporting on behalf of the counterparty. The true requirements of delegated reporting could be far more onerous, particularly with the increased complexity of many elements introduced in the 2017 revised reporting technical standards. This is evidenced by Refit stressing the obligation on the NFC- firms to supply all the required information to their financial counterparties in order for them to report accurately on their behalf.

    It is also questionable whether the mandatory delegated reporting will help the NFC- firms that much. It will only work as planned if all their counterparties are EU firms. Many of their current counterparties may already be non-EU counterparties, so they will have to maintain their trade reporting infrastructure. Of course, a hard Brexit would seriously negate the value of this new measure as ESMA would not have any power to force a UK financial counterparty to provide delegated reporting for a non-EU NFC- (but maybe it could force the NFC- to only deal with EU firms).

    A lost opportunity

    Many firms had hoped that the Commission’s review of EMIR during 2015 and 2016 could lead to fundamental changes in the trade reporting requirements. Expectations included the removal of ETDs from the reporting obligation and the removal of the dual-sided reporting obligation. At the very least, many financial counterparties hoped that the review would lead to the removal of the obligation to report individual ETD trades and to rely on the end-of-day position reports. Since the main purpose of EMIR trade reporting is to monitor for systemic risk, there appears to be little value in collecting reports of ETD trades when they are immediately netted into an end of day position report. Additionally, key elements of EMIR trade reporting like lifecycle events and collateral reporting can only really be sensibly applied to the end of day positions for ETDs. Perhaps the only value of ETD trade reports is for the detection of market abuse – but this is the driver behind MiFIR transaction reporting and their inclusion in EMIR is expensive duplication.

    If the purpose of EMIR Refit is to address disproportionate compliance costs and to streamline reporting, then it can only be described as a lost opportunity. The existing EMIR trade reporting regime might be considered white elephant regulation – expensive and onerous to comply with, yet difficult to understand how it meets its objectives. Even the November 2017 revisions failed to disguise the fact that ETDs have been shoe-horned into reporting regime primarily designed around OTC derivatives.

    If you have concerns about whether you are meeting your EMIR trade reporting requirements or would like confirmation your reporting is accurate and complete, please get in touch with us for a conversation with one of regulatory experts.

  • ESMA publishes new EMIR Q&A

    ESMA publishes new EMIR Q&A

    With ESMA publishing documents faster than it’s possible to read them, we ‘welcome’ another EMIR Q&A today. The good news for reporting is that it mainly impacts clearing and there are only two amendments in the trade reporting section.

    The first of these comes in TR Question 36 – the reporting of OTC derivative notations. This is a simple clarification from ESMA, stating that:

    “For reporting purposes, only instances where a counterparty (being a CCP or another counterparty) steps into the derivative contract and becomes a new counterparty to the derivative contract should be reported with Action Type “New”. For the original report relating to the existing transaction derivative, counterparties should send a termination report marked as ’C= Early termination’, completing the field “Termination date”. The remaining counterparty and the new counterparty should then send a new report with action type “New” relating to the new transaction derivative.”

    So, there’s some new words in TR Question 36, but no change to reporting.

    The second change impacts TR Question 42 – population of ‘Clearing Obligation’ and ‘Cleared’ (fields 2.34 & 2.35) – and this marks a welcome simplification with the new instructions becoming applicable from 17 June 2019. The implementation of EMIR Refit removes obsolete references to frontloading leaving the remaining instructions far more digestible:

    “The field [Clearing Obligation] should be populated in following way: 

    • The field is not applicable to the transactions executed on a regulated market and should be left blank
    • In the case of cleared trades, the field “Clearing obligation” should be populated with “N” and the field “Cleared” – with “Y.”

    Even with the Q&A, understanding how to trade report correctly under EMIR can be a complicated and perplexing task. At Kaizen, we find many of the mistakes firms make with their reporting stem from a basic misunderstanding of the requirements.

    If you want to unravel the mysteries of EMIR trade reporting and avoid the potential pitfalls leading to breaches, why not attend one of our CPD and CISI accredited courses. In our experience, a small investment in training can help avoid costly remediation at a later stage.

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

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

    UPDATED – 19 February 2019

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

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

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

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

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

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

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

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

  • Another year of significant growth, success and development for Kaizen

    Another year of significant growth, success and development for Kaizen

    FOR IMMEDIATE RELEASE

    17 December 2018, London: Leading regulatory reporting firm Kaizen Reporting, developer of the multi-award-winning assurance service, ReportShield™, has rounded off a successful year of exciting expansion, both of its specialist team and its services, consolidating its market-leading reputation. With several influential senior hires, the launch of a tailored, expert-led regulatory reporting training service and numerous prestigious award wins, Kaizen has continued to set itself apart at the forefront of the industry.

    Kaizen began the year with a significant partnership with challenger consultancy Elixirr to deliver a complete end-to-end regulatory reporting remediation service for financial institutions, a much-needed partnership for responding to increasing levels of complexity in market regulations.

    This was followed with the hiring of two senior staff: the former chair of the ICMA taskforce on SFTR, Jonathan Lee, and the former regulator and EMIR and MiFIR expert, David Nowell. The addition of two highly-respected regulatory veterans further consolidated Kaizen’s position as market leader, bringing clients even greater assurance services for EMIR, MIFID II transaction reporting, Dodd-Frank and SFTR.

    Kaizen continued to win awards, and in December ReportShield was named ‘Best New Regulatory Reporting Product’ by the FOW International Awards. It was also one of a select group of companies chosen to exhibit at the fourth annual FIA Innovators Pavilion in Chicago, launched to showcase forward-thinking solutions for the global derivatives market. In addition, Kaizen was listed in the RegTech 100, a global directory of companies providing the most innovative solutions in regulation.

    Earlier this month Kaizen announced an expansion of its MiFIR offering, adding APA trade reporting. At the same time Chris Machin, a MiFIR trade reporting specialist, joined Kaizen to head the development of its new service.

    Dario Crispini, CEO of Kaizen, commented: “Our successes in 2018 are down to the commitment and innovation of our fantastic team here at Kaizen. We have doubled our client base and increased the staff numbers supporting our clients by a third. We have made even greater strides towards solidifying our position as the leading regulatory assurance provider. It’s not only a testament to our hard work, but also to the value of the service we are delivering to our clients.”

    “Our successes in 2018 are down to the commitment and innovation of our fantastic team here at Kaizen”

    Ian Rennie, Managing Director of Kaizen, added: “What I think has particularly differentiated this year from previous years is the expertise we have brought on board in the form of Jonathan, David and Chris. We now not only offer an unrivalled service across more regimes but also the specialist expertise from well-known players in this space, bringing even more peace of mind to our clients.”

    Dario continued, “Looking ahead to 2019, we will see regulators increasingly focus on the quality of data being reported for MiFID II, EMIR, Dodd-Frank and other G20 regulations. For MiFID II in particular, the UK regulator, the FCA, is already writing to firms to warn them about improving their data quality. We will also see the extension of the SMCR regime which will put further pressure on senior individuals within financial institutions to ensure their reporting is accurate and complete. And now that the regulatory technical standards have been approved, preparation for SFTR reporting will also increasingly demand time and focus from financial institutions. Putting the right controls in place at an early stage will result in compliant and efficient reporting from go-live”

    ReportShield is a set of services that help financial firms meet their reporting control obligations and effectively manage their reporting risks.  The service includes Kaizen’s award-winning accuracy testing which is unique in its ability to test all reported data, providing firms with full visibility of the quality of their reporting.

    (ends)

    For media inquiries, please contact Fiona Wilde at communications@kaizenreporting.com or +44 (0) 20 3912 3271.

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

     

  • Stockholm conference: New regulatory insights on EMIR and MiFIR reporting

    Stockholm conference: New regulatory insights on EMIR and MiFIR reporting

    It was great to be a part of last week’s Trade and Transaction Reporting Northern Europe Conference in Stockholm and in particular, hear insights from the European Commission and the Dutch and Finnish National Competent Authorities (NCAs) on EMIR and MiFIR, as well as the latest on SFTR reporting timelines. 

    European Commission’s Fitness Check

    Gerd Heinen, Policy Officer at the European Commission, spoke about the Commission’s ‘Fitness Check’ on supervisory reporting. The objective of the Commission’s project is to “identify areas where the cost and burden of supervisory reporting can be reduced without compromising the objectives of financial stability, market integrity, and consumer protection”. I’m sure both the reporting firms and the recipient regulatory bodies would agree this is a worthy and valuable project. However, the two sides certainly didn’t agree in their responses to the Commission’s public consultation, particularly on whether the reporting requirements were fit for purpose.

    The Commission published a summary report following its consultation, which contains some fascinating statistics and cost estimates. My particular favourite is that only four per cent of respondents thought that all the existing supervisory reporting requirements were relevant for maintaining financial stability and upholding market integrity and investor protection. I also enjoyed the Commission’s observation that “out of 391 responses received, 258 came from industry stakeholders (all of which were in the same sector and from the same member state), who provided very similar responses to sections 1 and 3”.

    The Commission expects to publish its conclusions of its Fitness Check in the first half of 2019 and ‘if necessary’ follow publication with recommendations to streamline and simplify supervisory reporting.

    MiFIR data quality issues in Europe

    I equally enjoyed a joint presentation from the Dutch and Finnish National Competent Authorities (NCAs) on their observations on MiFIR transaction reporting implementation. From a Brexit perspective, it was interesting to note that just over 50% of all transaction reports received by the Dutch NCA were from UK firms routed via the UK’s FCA. The corresponding figure for the Finnish NCA was even higher at roughly 80%.

    When it came to reporting quality issues, the Dutch and Finnish regulators presented the following areas of concern:

    • Gaps in reporting
    • Rejected transactions not corrected
    • Use of CONCAT instead of higher priority identifier
    • Incorrect national identifier format
    • Wrong trading venue identifier (On market vs XOFF) – Operator MIC instead of Segment MIC
    • LEI codes
    • Timestamp granularity
    • Default trading times
    • Trading place identifier
    • Price
    • Reporting of transaction chains
    • Non-flat ‘INTC’ end of day.

    There are some similarities here with the UK FCA findings presented in their summer forum. However, it is noticeable that this work extends beyond the relatively simple ESMA defined validations and firms need to be aware that the NCAs are now extending their quality assessment to ‘business validations’ such as ‘flat INTC accounts’ as well.

    At Kaizen, we believe you need to be a few steps ahead of the NCA in discovering errors in your transaction reports.  Even if reports pass through the ARM and NCA validation checks, it doesn’t mean that the data contained within them is correct. Our accuracy testing service carries out over 1000 tests on every transaction report to detect errors and give full transparency of the quality of your reporting so you don’t fall foul of the regulator. 

    For more information on Kaizen’s accuracy testing and how we can help solve your MiFIR (and EMIR) reporting challenges, please contact us.

  • Book now! Kaizen launches regulatory reporting training service led by industry expert David Nowell

    Book now! Kaizen launches regulatory reporting training service led by industry expert David Nowell

    FOR IMMEDIATE RELEASE

    23  October 2018, London: Leading regulatory technology firm Kaizen Reporting today announced that it is launching a training service led by the company’s new Senior Regulatory Reporting Specialist, David Nowell. The training will initially focus on MiFIR transaction reporting before expanding to include EMIR trade reporting and the upcoming Securities Financing Transaction Regulation (SFTR).

    A former regulator, Nowell has 30 years’ financial services experience. Having previously worked as a transaction reporting technical specialist at the UK FSA, as head of transaction reporting for a tier-1 investment firm and head of compliance for an Approved Reporting Mechanism and Trade Repository, David has a thorough understanding of both the importance and the challenges in meeting the regulatory reporting requirements. He also has extensive experience of client training on both MiFIR transaction reporting and EMIR trade reporting.

    Dario Crispini, CEO of Kaizen, commented: “David is widely seen as a leading authority in the industry. The FCA frequently warns about the risk to institutions of inadequately trained regulatory reporting teams and in many of its warning notices cites a lack of training as a factor in its decision to censure a firm for incorrect reporting.  Expanding our services to include training makes sense for us, and we are looking forward to helping our clients improve their knowledge in this space.”

    David Nowell, Senior Regulatory Reporting Specialist at Kaizen, commented: “Training is an integral part of the systems and controls that firms need in place to be reporting accurately. It’s impossible to get your regulatory reporting correct unless you understand the legislation from the Level 1 text down to the regulatory technical standards, guidelines, Q&A and validations. Our new courses are designed to help get our clients up to speed quickly, allowing them to understand what needs to be done to report correctly as soon as possible.”

    David adds, “Ensuring your staff are properly trained on the reporting regulations can save costs in the long run as it will increase a firm’s chances of avoiding regulatory sanctions for incomplete or inaccurate reports and the additional expense of costly back reporting exercises.”

    The training service includes four-hour classroom-style workshops as well as in-house sessions for financial institutions. 

    (Ends) 

    For more information please visit our training page or for inquiries about the service please email training@kaizenreporting.com

    For media inquiries, please contact Fiona Wilde at media@kaizenreporting.com or +44 (0) 20 3912 3271.

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

  • EMIR trade reporting: lifting the lid on pairing and matching

    EMIR trade reporting: lifting the lid on pairing and matching

    EMIR trade reporting is part of the regulatory response to the financial crisis of 2007/2008.  It requires complete and accurate reporting of derivatives to trade repositories (TRs) to enable regulators to monitor for any build-up of systemic risk. Unlike Dodd Frank, EMIR is a dual reporting regime – both counterparties have a reporting obligation (if they are captured by EMIR). This has caused consternation among some parts of the industry as they believe the inherent duplication is wasteful and just increases costs for the industry. The other side of the argument is that dual-sided reporting reinforces the quality of the data by highlighting errors if the two sides of the report don’t “pair” or “match”. The TRs inform the reporting firms where the trade reports have not matched or even paired with the versions supplied by their counterparty.

    How do the TRs pair and match the trade reports?

    The first stage is to find out if both counterparties to the trade have a reporting obligation. This is done by examining the values in the ‘ID of the other counterparty’ field (1.4) and the ‘Country of the other Counterparty’ field (1.5). If these indicate that the ‘other counterparty’ has a reporting obligation, then the TR will set out to find the other side of the trade report – ie. to ‘pair’ it with the report submitted by the ‘other counterparty’.

    This ‘pairing’ is achieved by using the ‘Unique Trade Identifier’ (UTI) in each report and the LEIs in the ‘Reporting Counterparty ID’ field (1.2) and ‘ID of the Other Counterparty’ field (1.4). If the receiving TR does not have both sides of the report, it will request the data from the other TRs. If the two reporting counterparties have failed to use the same UTI, or if they have entered the wrong LEI in either counterparty field, then the TRs will not be able to ‘pair’ the trade.

    If the TRs are able to pair both ‘sides’ of the trade report, they will then check a subset of the fields to ensure that they ‘match’ (as each counterparty is reporting the same trade, the trade details should match). The current set of fields subject to this matching process are as follows:

    • Counterparty side
      (aka buy/sell indicator)
      if one counterparty
      has said ‘B’ the other
      must be ‘S’ and vice versa.
    • Contract Type
    • Asset Class
    • Product Classification Type
    • Product Classification
    • Product Identification Type
    • Product Identification
    • Underlying ID Type
    • Underlying ID
    • Notional Currency 1
    • Notional Currency 2
    • Trade ID
    • Venue of Execution
    • Compression
    • Price/Rate
    • Price Notation
    • Currency of Price
    • Notional
    • Price Multiplier
    • Quantity
    • Delivery Type
    • Execution Timestamp
    • Effective Date
    • Maturity Date
    • Termination Date
    • Confirmation Timestamp
    • Confirmation Means
    • Clearing Obligation
    • Cleared
    • Clearing Timestamp
    • CCP
    • Intragroup
    • Fixed Rate Leg 1
    • Fixed Rate Leg 2
    • Exchange Rate 1
    • Forward Exchange Rate
    • Exchange Rate Basis
    • Commodity Base
    • Commodity Details
    • Option Type
    • Option Exercise Style
    • Strike Price
    • Strike Price Notation
    • Maturity Date of the Underlying
    • Seniority
    • Reference Entity
    • Frequency of Payment
    • Series
    • Version
    • Index Factor
    • Tranche
    • Attachment Point
    • Detachment Point

    Many of these fields must match exactly, whilst others have to match within a tolerance. The matching on a few of these fields is conditional – for example, the Underlying ID must match where the Underlying ID Type is ‘I’ (for ISIN), but does not need to match where the Underlying ID Type is ‘X’ (for index) and free text has been used.

    What happens if the report fails to pair or all the fields do not match?

    The TRs will still accept the report, but they will inform the reporting counterparty if the report does not pair and it will also identify all the fields that have not matched if a pair has been found. The reporting counterparties are then expected to resolve the issues with their counterparty.

    How good are the pairing and matching rates?

    The pairing rates are a little disappointing and the matching rates are extremely low. Whilst the pairing rates have increased since the implementation of the revised reporting technical standards last year (probably due to the guidance on the UTI generating party being formally added to the regulation), the matching rates have not.

    Does this matter?

    Yes. Remember, one of the drivers behind dual-sided reporting is to reinforce the quality of the data and the disappointing rates indicate that there are issues with data quality. While firms may not have seen much action from the NCAs on EMIR data quality aspects (although the £35m fine levied by the UK FCA may have come as a shock), ESMA clearly flagged that it will focus on data quality in its annual report and work plan:

    “ESMA continued to closely engage with NCAs and exchange data to identify counterparties where reporting causes large amounts of breaks in the reconciliation process. ESMA plans to further intensify its engagement with the NCAs as part of the NCA cooperation process related to data quality.”

    Firms most definitely need to be aware that NCAs are monitoring the pairing and matching rates and could target those firms seen as outliers. Whilst the reason for unpaired or unmatched reports could lay with the ‘other counterparty’, those firms with comparatively low pairing and matching rates overall will be in the sights of the NCAs.

    What can firms do to improve matching rates?

    Low matching rates are a very good indication of poor quality EMIR trade reports. Sadly, there’s no short cut on this one; to improve the matching rates, firms need to improve the quality of the data they submit. This is where Kaizen can help. We can offer a reconciliation from the front office trading data to the data submitted in your name to the trade repository. We can also run an accuracy test on all your trade and position reports, including a check that your outstanding positions are an accurate reflection of your trade reports. We also offer training on the EMIR reporting standards. For further information 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.

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

  • Media release: Leading regulatory expert David Nowell joins rapidly-growing Kaizen team

    Media release: Leading regulatory expert David Nowell joins rapidly-growing Kaizen team

    We’re delighted to announce another senior new hire in the space of a week! David Nowell, the former head of regulatory compliance at London Stock Exchange’s UnaVista, will be joining us next week. Nowell will be a Senior Regulatory Reporting Specialist, bringing with him extensive experience including over ten years at the Financial Services Authority (FSA). The news about David comes at an exciting time for us, with several new hires from tier 1 banks and the recent recruitment of Jonathan Lee, former SFTR taskforce leader at ICMA, and the addition of Elixirr (announced in March) to existing partnerships, with companies including UnaVista.

    David’s impressive knowledge of and involvement in regulatory compliance is evident in his responsibilities at UnaVista, the largest Approved Reporting Mechanism, where he was tasked with ensuring continued compliance with EMIR and MiFID reporting requirements as well as liaising with various regulatory authorities. These duties and his advice to and training for firms helped to consolidate his reputation as a leading voice in regulation and an important factor in Kaizen’s decision to enlist his services.

    Dario Crispini, CEO of Kaizen, commented: “I’m delighted for David to be joining the team to further enhance the service we provide to our client base of tier 1 and 2 banks, fund managers and brokers. Our formula of combining market-leading data scientists with industry experts is what sets us apart from competitors, and with David fitting perfectly into the latter category I’m confident he’ll be a crucial part of our operations in the months and years ahead.”

    Ian Rennie, Managing Director of Kaizen, added: “Many years of direct involvement with regulatory authorities as well as product and solution development makes for a perfect background for the service we provide to our clients. Our effective and proven quality assurance service gives financial institutions the confidence they need to focus resources elsewhere in the knowledge that they are fully compliant with ever-more stringent reporting requirements.”

    David Nowell said: “Kaizen has built a reputation of being at the forefront of its field, so this step in my career was the natural choice. I very much look forward to working together with Kaizen’s talented team and being part of the innovation and expertise that the firm consistently produces.”

    Editorial contacts

    Fiona Wilde
    Email: media@kaizenreporting.com
    Tel: +44 (0) 20 3912 3271

     

     

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

  • Media release: Kaizen announces an excellent 2017, with new clients, offices and award wins

    Media release: Kaizen announces an excellent 2017, with new clients, offices and award wins

    For immediate release – Thursday 14 December 2017

    Kaizen Reporting, the leading provider of regulatory reporting quality assurance, has had another very successful year. Strong demand for Kaizen’s automated testing services has seen it double its client base and number of employees, which necessitated a move to new offices. Kaizen has also extended its services to cover more G20 jurisdictions and regulations including EMIR 2.0 and the upcoming MiFID II. Kaizen was recognised for its pioneering approach to quality assurance with the Queen’s Award for Enterprise, one of the UK’s highest business accolades.

    Dario Crispini, Kaizen CEO, says, “2017 has been a fantastic year for Kaizen and I think we will look back on this year as our ‘breakthrough’ year. Demand for our services has really taken off.  Our revenues have grown by nearly 150% and we have signed a large number of new clients including four tier 1 banks and several of the world’s biggest asset managers, hedge funds and brokers; we also made some significant new hires. 2018 is looking to be just as successful with new services, partnerships and growth already in the pipeline.”

    As well as winning the Queen’s Award earlier this year, Kaizen’s flagship ReportShield™ service also won Best Compliance and Regulatory Solution at October’s Fund Services Awards.

    Crispini added, “The awards we’ve received have been the icing on the cake this year and we see them as further acknowledgement of the impact our services are having on the industry.  Regulatory reporting is getting more complex and challenging for firms, but we take that burden away from our clients and give them confidence in their reporting.”

    ReportShield™ provides firms with an automated set of controls that give full transparency of reportable data, detecting even minor errors. This gives financial firms the ability to identify and manage their regulatory reporting risks, building real confidence in their reporting – and most importantly, avoiding regulatory censure. 

    Dario continues, “Looking ahead to 2018, the MiFID II pain will continue and we expect firms to turn their attention to the deployment of appropriate controls for MiFID II. At the same time EMIR and DFA reporting quality, resulting in remediation of reporting issues, will become more important, along with the challenges of SFTR implementation and the impact of the Senior Manager’s Regime on reporting.”

    ***ends***

    For media inquiries, please contact Fiona Wilde, Head of Communications and Marketing on 07834 731 602 or media@kaizenreporting.com

  • FCA’s first EMIR reporting fine highlights importance of robust testing and controls

    FCA’s first EMIR reporting fine highlights importance of robust testing and controls

    The £34.5 million fine issued this week by the FCA is the first enforcement action for failing to comply with Article 9 of EMIR and highlights the increasing importance the regulator is placing on data quality.

    It was generally accepted that the regulator would eventually take enforcement action against a firm for EMIR breaches and there would have to be a firm first in line.  In this case it was Merrill Lynch International, however it could probably have been one of many firms that have struggled to deal with the EMIR reporting requirements. 

    The FCA understands that reporting won’t be 100% all the time however its final notice highlights insufficient testing to ensure the accuracy and completeness of reports as well as weaknesses in oversight arrangements that would have contributed to the under reporting of 68 million exchange-traded-derivatives over a two year period. 

    Poor quality data is industry wide 

    While these are serious failures, we would argue that they are not unique to Merrill Lynch.  Poor quality data is a widespread industry problem, something that the regulator and we here at Kaizen have been highlighting for some time. 

    Just last week Ana Fernandes, of the FCA’s Markets Reporting team, focused on the issue of data quality at an industry conference we attended.  She highlighted the importance of  having comprehensive in-depth testing and reconciliations in place at a frequency appropriate to trading volumes.  Firms must test for the accuracy and completeness of their transaction reports and have the appropriate oversight arrangements to detect and remedy systemic problems.  Ana said there were ‘high expectations’ come 3 January 2018 when MiFID II goes live that they would see better data and this is as essential for EMIR, as it is for MiFID and MIFID II.

    Just the tip of the iceberg

    Last year we published our analysis of FCA MiFID I reporting fines which shows how easy it is to get reporting wrong.  More often than not, firms continue to get false confidence from the validations provided by ARMs and Trade Repositories without testing whether the data at source is correct.  Ana in her speech last week focused on just that, “Don’t think that because the file has gone to the ARM and the FCA that it is done” she said. 

    The final notice clearly demonstrates the FCA’s expectations for robust and comprehensive testing of reporting.  This requirement is more clearly articulated for MiFID II, where testing for accuracy and completeness is mandatory under RTS 22, Article 15 and these controls should be in place at go-live.  Similarly, from 1 November (next week!) when EMIR Level 3 goes live, a lot of reporting requirements currently in the EMIR Q&As become part of the Regulatory Technical Standards and therefore become more easily enforceable by the national competent authorities.

    The FCA says the fine, the largest so far, ‘reflects the importance’ it puts on this type of reporting and the important role it plays in ensuring a transparent market. The action also shows that the regulator will fine you more if you’ve got it wrong previously and that it is applying the same approach to EMIR as it does with MiFID in terms of fining on a per record basis. 

    Expect more fines as regimes mature

    As the G20 reporting regimes mature, we are seeing a general trend of increased enforcement activity.  The CFTC has been active recently re DFA, and we also saw the recent ASIC fine by the Australian regulator so I expect further fines to follow.

    Improving firms’ reporting data quality is the reason we at Kaizen exist.  We have several clients that report over 100k trades per day to a trade repository.  With these types of volumes, it’s very easy to end up facing an eye watering fine which is why we have designed our services to protect both the firm and the individuals with reporting oversight responsibility under the senior manager’s regime. 

    Please don’t hesitate to contact us if you would like to discuss your regulatory reporting data quality or any of the issues raised in this piece.

  • In the news: Dario Crispini speaks to Best Execution on derivatives identifiers

    In the news: Dario Crispini speaks to Best Execution on derivatives identifiers

    Our CEO Dario Crispini spoke to Lynn Strongin-Dodds of Best Execution about the steps being taken towards greater standardisation of data contracts, content, identifiers and post-trade procedures. 

    Last year the International Swaps and Derivatives Association (ISDA) published a paper entitled “Future of Derivatives Processing and Market Infrastructure” which called for firms to work together to develop standardised data contracts, content, identifiers and post-trade procedures. While few expected to see the industry change overnight progress has been slower than expected.

    “Under EMIR and MiFID, you have regulatory pressure to standardise instruments that are traded OTC because of the clearing and margin rules. However, one of the problems with the ISINs in the derivatives space is that they are only focused on Europe and are not global. If you trade an ETD on a third country market you will need an alternative. Another point of contention around OTC derivatives is that the DSB is run by ANNA, whose members are all profit-making companies and I am not sure that is the right approach,” Dario told Best Execution. 

    Read the full article here. 

  • Kaizen hires ex-trade repository specialist to support growth

    Kaizen hires ex-trade repository specialist to support growth

    Leading regulatory reporting assurance company Kaizen Reporting is pleased to announce that James Mooney has joined its team in London as a regulatory consultant. James is a derivatives regulatory expert whose most recent role was at global financial services corporation Depository Trust and Clearing Corporation (DTCC). Prior to that he was with Fidelity Investments.

    Kaizen Founder and CEO Dario Crispini, said, “I’m delighted that James has joined Kaizen to support our growing client base of tier 1 and 2 banks, fund managers and brokers. He brings a deep understanding of trade repository requirements across multiple jurisdictions including DFA, EMIR, Canada, ASIC, MAS and HKMA. Alongside his technical knowledge, his practical knowledge of the regulations and experience of serving large global clients are invaluable.”

    The new role reflects the growth Kaizen is experiencing as it responds to increased demand for its quality assurance services that address the increasing complexities of regulations such as MiFID II and EMIR. Its client base has significantly expanded in the past two quarters to include an additional three tier 1 banks, several of the largest global asset management firms and one of the world’s largest brokers.

    Dario, formerly head of the FCA’s Transaction Monitoring Unit, continues, “Firms have struggled to get their reporting correct under the much less complicated MiFID regime for nearly ten years – and it’s about to get a lot more challenging. Testing and reconciliations are mandatory under MiFID II and it’s important that firms put the right controls in place now so that they hit the ground running with their reporting on 3 January 2018.”

    James Mooney, said, “It’s great to be joining Kaizen at such an exciting time as it takes on more clients and expands the jurisdictions it covers. Kaizen are the industry experts in regulatory reporting and pioneers in their approach to testing, which is fast becoming the industry standard. Its mission to give its clients confidence in their reporting quality really resonated with me and I’m proud to be part of a team that wants to improve data quality standards in the industry.”

    Kaizen’s pioneering ReportShield™ quality assurance services provide firms with an automated set of testing and controls that give full transparency of reported data, ensuring that clients meet their regulatory obligations. The service recently won a Queen’s Award for Enterprise for innovation in recognition of its impact on the industry.

    For media inquiries, please contact Fiona Wilde at media@kaizenreporting.com.

  • New rules = new tools: DTCC simplifies technology ahead of EMIR rewrite

    New rules = new tools: DTCC simplifies technology ahead of EMIR rewrite

    This week we attended the DTCC’s Partners Forum in London to get a taste of what the future holds for firms reporting data to the global trade repository (GTR).  As reporting rules become more complex across all global jurisdictions, the DTCC is aiming to simplify the functionality of the GTR.  Of course anything that makes reporting more straightforward is something we welcome here at Kaizen but there is a lot of work to do to prepare and resource appropriately to make sure you comply with the both changes in obligations and at DTCC. 

    The next phase of the GTR Re-architecture is going to be aligned with the go-live weekend for EMIR RTS on October 28th and is scheduled to be rolled out globally in 2018.

    If you have access to DTCC’s learning center you can see all of the latest updates here.

    Straightforward ingestion

    The new harmonized template is a ‘one size fits all’ solution to understanding how to format and upload data to the repository.  It acts as a one-stop-shop for finding the required information across all five asset classes and also enables filtering on specific products within asset classes, giving greater clarity on what fields are required to be reported.

    Practical processing

    DTCC have also adopted a new ‘latest is greatest’ approach in trade state calculation.  This removes the complexities of multiple submissions being interdependent on each other. UTI locks will also become a thing of the past which will make successful submission to the GTR easier.  However, this puts more responsibility on data submitters to ensure that counterparties are correct and to remove any incorrect submissions.  Delegated submissions will also be split into two parts and allow for separate processing per counterparty.

    Error messages are also being redesigned and will give greater insight into exactly where the error lies and what needs to be corrected.

    Upgraded reports and portal

    What we view as the greatest benefit of the Re-Architecture is the new way in which counterparties and third parties will have access and visibility to data.  Participants will have absolute transparency on what has been reported to the regulator and who it has been reported for.  Historic data will also be retrievable with the new search tool.  Eventually recurring queries can be scheduled to allow bespoke reports to be generated for every user on a timeline that will suit them.

    Changes in context

    The DTCC Re-Architecture is a big step in the right direction in terms of simplifying the way data is submitted and viewed but there is a lot of work to do to get to a place where you can truly take advantage of its benefits – and the clock is ticking.

    We are helping a number of firms understand and get the correct controls in place for the new EMIR RTS obligations due to come into force on I November, please get in contact if you would like to have a conversation about this or any other upcoming changes to reporting obligations. 

  • Transparency is still an issue 10 years post financial crisis

    Transparency is still an issue 10 years post financial crisis

    “If these things were so large, how come everyone missed them?”
    The Queen – 5 November 2008

    It’s ten years this month since the financial crisis began and we’re reminded that it was Her Majesty The Queen who spoke for the nation when she asked why it had taken so many financial experts by surprise.

    Her Majesty asked the question at a visit to the London School of Economics a few months after the collapse of Lehman Brothers.  The reply?  “At every stage, someone was relying on somebody else and everyone thought they were doing the right thing.”

    Could it happen again?

    August 9 2007 is largely known for being ‘the day the world changed’ when BNP Paribas froze three of their funds, indicating they had no way of valuing the assets inside them.  The run on British bank Northern Rock began a month later.  One year later in September 2008, Lehman Brothers filed for bankruptcy, prompting worldwide panic.

    Now, ten years on, could it happen again?  Have efforts to prevent another financial crash been successful?  The Governor of the Bank of England Mark Carney thinks so.  Last month he said that the things that caused the last financial crisis had been fixed.  Carney believes that the reforms agreed by the G20 have created a safer, simpler and fairer financial system.  

    Part of this reform agenda was a substantial increase in reporting requirements which are meant to bring greater transparency and allow regulators to be able to spot the build-up of systemic risk.  But persistent data quality issues continue to thwart making good on this objective.

    Data quality is the big issue

    Why?  The regulations that have arisen out of the ashes of the financial crisis including EMIR, Dodd Frank Act and the soon to be live MiFID II are meant to put in place reporting regimes that give regulators all the information they need to identify the build-up of systemic risk and detect market abuse.  The idea being that if there is to be a next time, regulators can’t stand behind the reason that they had limited visibility.  However, the increase in breadth and depth of information required has led to a corresponding and manifest increase in complexity which has led in turn to a decrease in data quality – which, if left undetected, can have serious and dire consequences for firms and regulators alike.

    We’ve highlighted before the problems that banks are having with their regulatory reporting quality – the very reason Kaizen is kept in business!  Last year the FCA found 65,000 data quality breaches in a week when testing only four of the MiFID transaction reportable fields.  Our own analysis has found at least 65% of transactions are being reported incorrectly with firms completely unaware of the inaccuracies of their data.  And this is in a mature regime which is comparatively simple compared to MiFID II, EMIR and DFA. 

    Stuck between a rock and a hard place

    If regulators, having asked for a substantial increase in reported data, are then unable to identify the build up of systemic risk, this will ring hollow in the corridors of power of the G20 governments.  Under this pressure regulators will have increasingly low tolerance with firms who persist with reports that have significant data quality issues.  

    For the industry to be able to add ‘improved transparency’ to Carney’s list of positive changes since the financial crash, there needs to be a sustained and comprehensive improvement in the quality of the data that firms report to regulators.

    Regulators cannot afford to allow data quality issues to persist.  They will take the necessary actions and we can expect increased censure and fines to follow as required.

    What next?

    In this context and environment it is critical for firms to be able to identify and quantify data quality issues in their reporting, which is exactly what Kaizen does for our clients and how we explained what we do to the Queen in our recent conversation with her at Buckingham Palace!  

    In all seriousness, please contact us if you have concerns about the quality of your regulatory reporting or would like confirmation of its accuracy and completeness.  We are here to help. 

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

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

  • Brokers would like to dump delegated reporting, may start to charge

    Brokers would like to dump delegated reporting, may start to charge

    Kaizen’s CEO Dario Crispini spoke with Thomson Reuters Accelus about the burden of EMIR-related delegated reporting for some broker-dealers and suggests delegated reporting may reduce with the revisions to the EMIR RTS later this year. 

    “Firms that offer delegated reporting services are trying to walk away from that a little bit. I’m expecting delegated reporting to reduce with the larger buy side firms using revisions to the EMIR RTS going live on 1 November this year as a trigger to launch their own direct reporting, but delegated reporting will not disappear altogether. There are clients who are delegating their reporting to the large broker dealers and they are not planning on making a change there,” Dario told Regulatory Intelligence.

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

    Extract

    There are a few factors pushing some of the bigger asset managers to consider doing their own reporting.

    “There is some unhappiness about data quality from an ESMA and FCA point of view. The FCA are going to be more actively looking at data quality and taking action against firms. We expect that to happen in the next six to 12 months. The view is that the FCA is moving to leverage their reporting capability.  Data quality is going to remain a problem across the industry and could be a problem for firms delegating their reporting as they have less control over reporting quality,” said Crispini.

    Buy-side firms can delegate reporting but the obligation for accuracy, completeness and timeliness remains with them.  The buy-side has enlisted consultants to conduct data testing and reporting validation but it’s not always easy to get the broker to make the required changes. What is more, buy-side firms end up giving their broker a free audit.

    Link to original article

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

  • 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

  • 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

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

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

  • Is indirect clearing any clearer?

    Is indirect clearing any clearer?

    ESMA has published its latest consultation on Indirect Clearing Arrangements under both EMIR and MIFIR. The consultation paper covers both ETD and OTC derivatives and is designed to ensure consistency between the two regimes.

    The paper looks at “longer chains” and states that:

    “The requirements applicable to a direct client would need to be extended to all the intermediaries between the clearing member and the counterparty at the end of the chain. This means in particular that the provisions related to default management apply throughout the chain, including the requirement to protect through contractual arrangements, to the extent possible, what is owed to the indirect client in relation to the indirect clearing services from the insolvency of any of the intermediary clients providing clearing services.”

    For more information please refer to the Consultation Paper.

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

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

  • ESMA reveals latest on MiFID II progress

    ESMA reveals latest on MiFID II progress

    On 7th July, Clifford Chance hosted a workshop on MiFID II progress and implementation at which ESMA’s Head of Markets Division Rodrigo Buenaventura provided an update.

    Mr Buenaventura outlined the continuing challenges faced by ESMA. He confirmed that the eagerly awaited final Technical and Regulatory Standards will now be published in September. With regards to timeline and what now appears to be building rumours around delay, Mr Buenaventura confirmed that there is no discussion at this time in this regard and ESMA is moving towards the 3rd Jan 2017 date. Despite recognising this would be challenging, they currently consider this as achievable. Furthermore, he advised that there is no current provision for phasing in particular aspects of the legislation, although acknowledged that over time this could be considered but it was too early for such consideration.

    He highlighted the key issues that require further consideration and these are clearly still a concern to market participants. These include:

    • non-equity transparency
    • commodity reporting
    • liquidity classification

    ESMA is considering the most appropriate approach towards liquidity calculation and whether this should be undertaken against individual securities or whether to adopt a group approach, for example a dependency upon issuance size. Their preference is currently unclear and will require further analysis.

    The liquidity calculation determines what instruments must be trade reported for market transparency. ESMA believes that the number of instruments that will be subject to trade reporting obligations will increase twenty fold.

    ESMA highlighted they will have a different role under MiFID II as consolidator of various important market data for transparency purposes in order to calculate liquidity and establish reporting obligations. They consider a single engine for this is beneficial to the financial community, avoiding reporting obligations to multiple CAs.

    ESMA also recognises there are significant challenges in respect of the establishment of position limits and that the European environment is completely different to the US. In the US some 60 limits exist whereas in Europe this runs into the thousands.

    Particularly interesting to those in the regulatory reporting arena was the fact ESMA confirmed it has significant concerns around the quality of the data reported under both the MiFID and EMIR regimes. Mr Buenaventura stated they are determined to ensure improvements in the quality of reporting and are working with the various colleges in an effort to address this.  ESMA recognises the importance of improving the quality of derivative reporting ahead of MiFID II implementation.

    ESMA advised they have undertaken significant analysis of market data, having reviewed more than two terabytes of EMIR data on top of significant bond market data to consider the appropriate way forward. ESMA recognised they will need to work with market providers in an effort to source the appropriate data for liquidity calculation and establishing appropriate position limits.

    Overall, ESMA stated they consider the implementing legislation should be an improvement for market participants given the harmonisation that regulation creates as opposed to a directive. Supervision convergence should ensure consistent approaches around requirements across the EU.

    With regards to the approach around implementation, questions were raised around adopting a similar approach to the EBA and the implementation of CRD given the issues experienced with EMIR Q&A.  ESMA will consider this and acknowledged the level of queries will be considerably higher and possibly ten times the 2000 or so queries that were raised under EMIR.

    Overall, Mr Buenaventura highlighted the importance placed on reporting and the significant changes that are taking place.  Furthermore, he stated that the focus on the problems with current standards provides a clear indication that regulators are serious about ensuring reporting quality is improved in order to implement the new legislation effectively. ESMA clearly recognise that the poor quality of data today is detrimental to the objectives the reporting obligation are attempting to achieve and so firms should take note of the obligation to have a control framework in place at MiFID II go-live.

  • ESMA publishes 13th version of its EMIR Q&As

    ESMA publishes 13th version of its EMIR Q&As

    Is the latest version of the EMIR Q&As a major change or a minor amendment? Well, the Q&As include just two revisions to TR questions but as they deal with validations, the changes can well be considered significant.

    For most reporting entities the EMIR validations will only help provide more visibility over reporting quality. However, it may mean that data problems will prevent firms from reporting at all and so a review of the impact of the validations should be considered before these are applied by the Trade Repositories at the end of October 2015. Not only that, the NCAs are using rejection rates as a proxy for data quality and will be using these to decide which reporting firms to visit.

    The other change that has been slipped into the Q&As via the validations is the approach around “lapsed” LEI codes. These are codes that have passed a 2 year period since issue but have not been renewed.

    Under Q&A TR Answer 10(b), ESMA stated that duly maintained LEI codes must be used however, lapsed codes are to be accepted by TRs when used to identify a counterparty. This is clearly a choice that ESMA is making around the LEI. Such codes are maintained where the owner has reconfirmed the data associated with the LEI record at the LOU, a process that happens every 2 years from issue. As these details change very infrequently, there is little risk in using lapsed LEI codes to identify a counterparty to a trade. Even where the details are incorrect, it is highly probable that the LEI will identify the correct party given that such codes are never reused.

  • ESMA publishes 12th version of its EMIR Q&As

    ESMA publishes 12th version of its EMIR Q&As

    ESMA has published its 12th version of the EMIR Q&As on 31 March 2015. This latest publication principally deals with the application of the clearing exemption.

    This will only impact reporting in respect of the following:

    • Sovereign wealth funds will fall within EMIR as Alternative Investment Funds and will therefore have a reporting obligation.
    • Where an obligation to clear arises and therefore clearing details must be reported.
    • Where an exemption from the clearing obligation is not granted.
    • Where a trade is novated for clearing.

    Further details of each update can be found below:

    OTC Q6(g) Intragroup exemption from the clearing obligation:

    Where counterparties apply to two separate jurisdictions, both Competent Authorities must approve the exemption otherwise it should not be relied upon. The counterparties should wait for responses from both CAs before placing reliance on the exemption.

    OTC Q13(d) Sovereign wealth funds established in third countries:

    “Sovereign wealth fund will qualify as financial counterparty under EMIR where it meets the definition of an AIF and it would be subject to Directive 2011/61/EU (AIFMD) if it was established in the Union. However, where a sovereign wealth fund does not meet the definition of an AIF and is out of scope of the AIFMD, such a sovereign wealth fund shall be treated as non-financial counterparty in accordance with Article 10 of EMIR.”

    OTC Q13(d) Pension scheme arrangements:

    Where pension scheme arrangements, as defined in Article 2 (10) EMIR, are granted an exemption under Article 89 and outsources management of its assets to a third party, the exemption will still apply. The manager should meet the following criteria in managing the exempt assets:

    1. Does not comingle exempt and non-exempt assets.
    2. The derivative contract clearly identifies that it is concluded for an exempt pension scheme under Article 2 (10) and Article 89 (1 & 2) (as appropriate).
    3. Keep the assets and records in a way to allow regulators to check that the derivative contract reduces investment risks directly related to the financial solvency of the pension scheme.

    OTC 17(b) Frontloading period:

    Contracts entered into during the clearing frontloading period do not need to be cleared, where the intragroup exemption is granted before the clearing obligation takes effect.

    OTC Q20 Clearing obligation regarding novations:

    All types of trade novations are covered by the clearing obligation. The example ESMA provides is where a counterparty (being a CCP or another counterparty) steps into the trade and become a new counterparty to the trade. They will therefore be subject to the clearing obligation.

    OTC Q21 Guarantees in respect of third country contracts:

    The responsibility under Art 2.1 of RTS for guarantees in respect of Third Country contracts will lie with the EU guaranteeing party. As such the EU entity will need to make the arrangements to have the required information to assess whether the guarantee should be deemed to have a significant and material effect in the EU.

    OTC Q22 Guarantees in respect of third country contracts:

    Where multiple guarantees are being provided they should be considered in together where the guarantees are provided to the same entity, as the guarantor EU entity will be subject to a single entity’s risk.

    OTC Q23 (a) Guarantees in respect of third country contracts:

    Article 2 RTS on Third Country contracts does not apply to contracts entered into before the RTS comes into force.

    OTC Q23 (b) Guarantees in respect of third country contracts:

    Article 2 RTS on Third Country contracts does apply to contracts entered into after the RTS comes into force but guarantees were given by an EU entity prior to the effective date of the RTS.

    CCP Q6 (f) Under Article 14 of EMIR – Authorisation of a CCP:

    “CCPs cannot be authorised to offer services preventing the interposition of the CCP between clearing members, i.e. preventing clearing members to clear contracts with other clearing members.”

    CCP Q8 (n) Article 39 of EMIR – Segregation and portability:

    Repayment of excess margin to clients under auto repay arrangements.

    According to article 39(6) of EMIR, “When a client opts for individual segregation any margin in excess of the client’s requirement shall be posted to the CCP. As such, any excess collateral allocated to an individually segregated account must either be maintained at the CCP in accordance with article 39(6) or returned to the client.” ESMA go on to say that CCPs should offer clearing members the possibility of switching off auto pay as long as the CCP is permitted to hold the holding excess margin.

  • Obligation to use LEIs picks up pace

    Obligation to use LEIs picks up pace

    LEIs are already required when reporting under EMIR but their use is to be mandatory from 2015 under COREREP and FINREP.

    The EBA published its recommendations on use of LEIs in regulatory reporting and the FCA has adopted the recommended approach. This means that UK firms must have registered both themselves and group companies for an LEI by the end of the year. They are required for COREREP and FINREP submissions for both the reporting firm and any relevant group entities when submitting on a consolidated basis. LEIs are also to be used to identify counterparties when reporting where an LEI has been issued for the counterparty.

    Firms are advised to obtain an LEI from a local operating unit and the FCA expect firms to register their LEIs immediately upon receipt using the FCA survey tool.

    They have become regulators’ entity identifier of choice so we can expect to see it as mandatory for a range of reporting obligations not least under MiFID II and Security Finance Transaction Reporting.

  • NYSE LIFFE MIC changes following migration to ICE Futures Europe

    NYSE LIFFE MIC changes following migration to ICE Futures Europe

    The NYSE LIFFE Market Identifier Code (MIC code) is to change following their migration to ICE Futures Europe including guidance on BClear instruments.

    This change has a direct impact upon firms’ regulatory reporting obligations impacting both EMIR trade repository reporting and MIFID transaction reporting obligations. This note summarises the changes and what action firms should be taking.

    The ICE migration is complicated in that the exchange contracts are being migrated over 5 different dates with the final date of migration being 17th November 2014. Firms should note that fixed income instruments migrated over three different dates therefore the MIC for the respective contract needs to accurately reflect these changes. Further complexity is that close attention is also required in respect of the appropriate MIC being applied for example the MIC code is different for Equity Index Futures (IFLL) and Options (IFLO) contracts and this needs to be identified correctly in firms static data and subsequent reporting.

    What should firms be doing?

    Firms’ static data needs to be amended to reflect the correct MIC code at the time of the changeover for the impacted contracts. Post implementation quality assurance testing should be applied to ensure that EMIR and MiFID transaction reports reflects the MIC changeover and any timing errors are corrected.

    With various LIFFE contracts being migrated to new MIC codes in stages firms will need to take great care to ensure that they use the correct MIC code for the relevant contract at the right time. For quick reference table detailing the precise changes to the appropriate MIC and the respective dates this was applied please refer to the below table which contains the full details.

    LIFEE Contract Migration to ICE Futures Europe

    [supsystic-tables id=’7′]

    BClear

    Firms should also note, that going forward, trading previously undertaken utilising LIFFE BClear for wholesale market activity, will now be undertaken under ICE “block” trading rules. When reporting as per the above table, firms should consider the product sector and contract type and report the appropriate MIC ongoing from it’s respective migration date. Dependent upon the security, this trading activity will be subject to MiFID and/or EMIR reporting requirements. Firms are advised when reporting this activity that they are required to report the appropriate MIC in recognition of the particular security.

    See below for further clarification.

    • “Block” trade on an Equity Index Future the appropriate MIC is IFLL
    • “Block” trade on an Equity Index Option the appropriate MIC is IFLO
    • “BlocK” trade on White Sugar Futures and Options the appropriate MIC is IFLX

    Firms should refer to the “LIFFE to ICE Futures Europe Transition Notice” published September 2014 for further details of the migration impact.