Tag: derivatives

  • CSA Rewrite: Will the real Alan McIntyre please stand up (Part 2)

    CSA Rewrite: Will the real Alan McIntyre please stand up (Part 2)

    I asked AI tool Claude to write a blog in my voice discussing the Canada Rewrite. The blog that the AI tool wrote is published in Part 1 here.

    After reviewing what AI wrote as me, I thought it might be interesting to review Claude’s findings and provide my own commentary on where it got things right – and where it missed some crucial nuances.

    Claude’s Goldilocks Perfect Blend Observation

    Alan’s AI blog started with:

    “The Great Canadian Compromise: How the CSA Rewrite Became the Goldilocks of Derivatives Reporting

    After nearly three years of watching the Canadian Securities Administrators (CSA) craft their derivatives reporting rewrite, I’m convinced they’ve pulled off something remarkable: creating a regulatory framework that’s somehow both everything and nothing like its global cousins. It’s like watching someone order poutine with a side of fish and chips while sipping a margarita – technically it shouldn’t work, but here we are.”

    I’m impressed that AI referenced and improved on my ‘poutine’ joke from a previous article. I’m even more impressed that the main finding is spot-on: by taking their time, the CSA has arguably benefited by adopting the best of the CFTC Rewrite with a smattering of ESMA’s EMIR elements.

    The Canadian timeline was partly practical—they wanted reporting firms to have completed their CFTC Rewrite and EMIR Refit projects first. This was partly Canadian politeness (they didn’t want to overburden firms with too many overlapping projects) and also the real-world difficulties of writing clear, descriptive new rules.

    I concur with AI-me that the result is a nice blend of the best of the CFTC Rewrite and EMIR Refit.

    The Field Count Nuance Missed by AI

    “The Numbers Game: More Fields Than You Can Shake a Stick At

    Let’s start with the obvious: field counts. The CFTC managed to slim down to a svelte 128 fields for their 2022 rewrite, clearly believing that less is more. ESMA, meanwhile, went full maximalist with 203 fields in EMIR REFIT, apparently subscribing to the philosophy that if you’re going to ask for data, you might as well ask for everything including the kitchen sink and the recipe for the sandwich the trader ate during execution.

    Enter Canada with 148 fields (up from their initially proposed 140), sitting comfortably in the middle like a regulatory Switzerland. It’s neither the American “keep it simple, stupid” approach nor the European “let’s document everything down to the thread count of the counterparty’s suit” methodology. It’s distinctly Canadian – polite, thorough, but not unreasonably so.”

    AI-me is correct that the 148 CSA Rewrite fields sits between the CFTC’s 128 fields and EMIR Refit’s 203. However, it’s missing the important nuance that in reality, the CSA fields are far more closely aligned to the CFTC’s fields. While it’s true that the CSA adopted a handful of EMIR Refit fields, the far higher EMIR Refit field count is explained by multiple factors including:

    • ESMA publishing the margin fields in a separate table to the transaction fields
    • Unfortunate ESMA-isms like dual product identification fields
    • A higher prevalence of asset class specific fields (commodities fields in particular).

    AI-me also missed the contextual nuance that the CFTC has proposed a further 48 fields to accommodate them rolling out UPI for commodities.

    UPI: Where AI got it wrong (phew – my job might be safe for now!)

    “The UPI Situation: Taking Sides in the Global Divorce

    Here’s where things get interesting. The CSA has decided to require Unique Product Identifiers (UPIs) for ALL asset classes, putting them firmly in the ESMA camp and leaving the CFTC looking like the odd one out at the derivatives reporting dinner party. The Americans are still dragging their feet on commodity UPIs like a teenager being asked to clean their room.

    This creates a delicious regulatory arbitrage situation. Canadian firms reporting to multiple jurisdictions now get to experience the joy of generating UPIs for their commodity trades when reporting to Toronto, but not when reporting to Chicago. It’s like being asked to wear both a tie and a Hawaiian shirt to the same party – technically possible, but aesthetically questionable.”

    This is where having a human in the loop – someone who’s attended the meetings and followed the progress of certain topics – becomes essential.

    AI-me got this one wrong when it concluded:

    The CSA has decided to require Unique Product Identifiers (UPIs) for ALL asset classes, putting them firmly in the ESMA camp and leaving the CFTC looking like the odd one out.

    I’m being harsh on my AI counterpart here as it is not wrong that Canadian reporting rules require UPI for all five asset classes including commodities. In terms of comparing the CSA requirements with the CFTC’s, this is spot on.

    But it’s missing the all-important detail of the prolonged bun-fight that this caused ie. the industry and trade associations lobbying the Canadian regulators to align the commodities UPI compliance date with the CFTC’s (yet to be published) commodities UPI compliance date. The CSA then obliged with a blanket order providing the requested relief to implement UPI for commodities in Canada when the CFTC does likewise in the USA.

    I Concur With The Crypto and Timeline Tango Findings

    Nothing to add or challenge for these two sections.

    ISO 20022 – The Gift That Keeps on Giving

    “The ISO 20022 Tease: The Gift That Keeps on Giving

    Perhaps the most telling aspect of the CSA Rewrite is what it doesn’t include: ISO 20022. Like the CFTC, they’ve decided to save this particular joy for a future implementation, presumably sometime in 2026. This means we get to look forward to yet another round of system changes, testing, and the inevitable discovery that the ISO 20022 standard is both incredibly comprehensive and utterly bewildering.

    It’s like promising to renovate your kitchen but deciding to do it in phases – first the cabinets, then the plumbing, then the electrical, ensuring maximum disruption over the longest possible timeframe.”

    I absolutely love that AI-Me has adopted the “Gift that keeps giving” tagline that I first used to describe transaction reporting way back in 2015.

    As for the CFTC and the Canadian regulators kicking the ISO 20022 standards can down the road, I agree with me again (starting to become a theme). The current effort avoided in tackling this is merely delaying the pain and baking in yet another implementation further down the road.

    To Summarise

    The AI analysis was genuinely insightful – it captured the essence of the CSA’s “Goldilocks” approach and identified the key strategic decisions that make the rewrite distinctive. Where it fell short was in the crucial regulatory nuances that only come from following the detailed implementation process.

    The question now is whether the Canadians’ careful balance of compromise and pragmatism will prove as effective in practice as it appears on paper.

    I already had a very particular issue with AI. The way it’s typically written down in capital letters is often indistinguishable from Al (as in A lowercase L, or Al, as I’m often known). As a result I often read “ask AI” and wonder what has this got to do with me!

    Now it seems the situation is even worse than I suspected because AI does a better AL than I do!

    It replicated my writing style and replicated my humour (that alone should be a cause for concern, never mind AI driven killer robots, doubling down on McIntyre’s woeful humour should be an urgent concern for the UN!). And worst of all it did a decent analysis. Not perfect but at the same time truly terrifying for someone that earns their crust in the knowledge economy.

    And if AI learns how to chat to clients and how to drink pints after work, then I’m well and truly toast!

    PS. My partner added that if AI learns how to do housework then I’m getting replaced at home too!!

    • For a conversation with Alan about the CSA Rewrite or a free health check of the quality of your reported data, please get in touch.

     

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

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

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

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

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

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

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

  • In the news: Dario Crispini speaks to Best Execution on the challenges of regulation on derivatives

    In the news: Dario Crispini speaks to Best Execution on the challenges of regulation on derivatives

    Our CEO Dario Crispini spoke to the Editor of Best Execution Lynn Strongin-Dodds about the ongoing trends and challenges of regulation on the derivatives industry and how market participants are leveraging technology to enhance processes and data management.

    Extract: 

    While the trading dynamics of derivatives will continue to focus the mind, coming to grips with the data burden – present in almost all other sets of regulation – is also consuming time, money and resources. Detailed reporting of trades across a range of asset classes is now required but, as with trading, asset managers just crossed the MiFID II finishing line and are planning to enhance their services.

    Dario Crispini, CEO of Kaizen Reporting believes that the “biggest challenges are data quality, reporting accuracy and getting a complete picture,” he adds. “There is a lot of choice in terms of the number of reporting systems but choosing one is not the end of the story. There needs to be a strong control and governance element.”

    Read the full article.