The Field Effect attended Broadridge’s ‘Take Control of Your SFTR Compliance’ seminar last week


The Field Effect attended Broadridge’s ‘Take Control of Your SFTR Compliance’ seminar last week where it was great hear how firms are preparing for their SFTR readiness, along with making new acquaintances. It was interesting to hear the views of the operational impact of SFTR and how the market can learn from implementation challenges relating to the recent MIFID 2 regulation.

David Field, Managing Director at The Field Effect was a panellist in the discussion, and provided insight as to how the firms should consider the way they approach their operational challenges, along with how the regulation can allow for firms to generate business value, as opposed to mere compliance.

The Field Effect have identified three categories of data attribute sources: fields that we expect in the primary trading systems (like time stamp, notional etc), fields that can be derived from that PTS data (such as looking up an LEI from a PTS counterpart ID), and fields that will probably come from somewhere else (e.g. reference data such as agreement ID and version).  We have analysed the data requirements for all products, split by mandatory, conditional and optional.  Interesting to note that, in the case of Repo for example, about a third of the data should be in the PTS, a third must be derived from PTS data, and a third must come from elsewhere.  The trick now is to tag each of those data attributes to the actual source systems, which will almost certainly vary by asset class tech stack, It’s complicated!

Contact us to understand more about how you can manage the impact of SFTR on your firm along with your strategic regulatory initiatives.

The post The Field Effect attended Broadridge’s ‘Take Control of Your SFTR Compliance’ seminar last week appeared first on The Field Effect.

Also join Simon Davies from The Field Effect at the RegTek webinar on SFTR below.

SFTR will creep up on firms by 2019, join us to get ahead of the game and hear perspectives from every angle. We have Paul Bradford, Head of Stock Loan and Repo trading at ING who will provide views on the effect of SFTR on the trading desk. Fabian Klar from REGIS-TR will explain their plans, and compare SFTR to other reporting regulations. Simon Davies will paint a picture of what an SFTR compliance plan should look like, and how long you need to be ready. Mark Steadman will update us on the Deriv/SERV plans and how SFTR will impact other streams of reporting. Alan McIntyre will contrast implementing SFTR with previous projects, and explain where re-use of previous infrastructure can be made. Other areas for discussion include changes to business processes, reconciliation requirements, data volumes, data formats, delegated reporting, the quality of the actual regulatory text, and your counterparties involvement.


  • Paul Bradford: Head of Stock Loan and Repo Trading at ING
  • Fabian Klar, VP Business Development at REGIS-TR
  • Simon Davies, Senior Consultant at The Field Effect
  • Mark Steadman, European Head of Product Development, DTCC Deriv/SERV
  • Alan McIntyre, Senior Business Analyst, RegTek.Solutions


  • How does SFTR affect a trading desk?
  • Will SFTR change trading behaviour?
  • What are the plans at REGIS to support SFTR?
  • How does SFTR compare with OTC reporting?
  • What is being said in the market about preparing for SFTR?
  • What would a typical SFTR project look like? (content and timing)
  • Tell us about the data requirements for SFTR – how do they compare with futures reporting?
  • What are the plans at DTCC to prepare for SFTR?
  • How will SFTR change business processes?
  • What are the reconciliation requirements for SFTR?
  • How can firms re-use their previous reporting platforms for SFTR?
  • How well are the regulations from ESMA written?
  • Does the volume of data for SFTR bring new challenges?
  • How would delegated reporting work for SFTR?
  • Does SFTR require cooperation from your counterparties?

March 13th at 15:00 UK Time


RSS Categories: