With ESMA go-live fast approaching (29th April 2024) and the FCA go-live several months later, (30th September 2024), it’s understandable why the focus is on ESMA. In fact, although the gap in reporting obligations may create some operational migraines if not suitably accounted for, the overlap between FCA and ESMA reporting requirements mean that all effort is relevant effort.
That said, when comparing key documents (for example the validation rules, XML schemas and technical standards) between the FCA and ESMA EMIR REFITs, there are some subtle, and less subtle, divergences which are talked to below. Following this, there is merit in pulling resources to analyse FCA and ESMA reporting in tandem to assess the level of additional build effort based on the divergence of requirements.
A thematic summary of the divergences is as follows:
ISO Schemas
Flexibility – Although ESMA and FCA are aligned when it comes to the trade activity report (with a strict version to be used as soon as the regulations go live), the FCA differs when it comes to the trade/margin state reports. ESMA only recognise a relaxed version of the trade state reports which facilitates the generation of the report in both legacy (the current EMIR reporting rules) and REFIT format. Conversely, the FCA stipulate that the relaxed versions must be used by Trade Repositories during the 6-month transition window. After this time, “strict” versions of these schemas, that allow reporting in Refit format only, will be used.
Conditionality – FCA have embedded parts of the validation rule logic within the XML schema definitions itself to facilitate an earlier layer of accuracy. For example, certain elements are now mandatory in the schema which enforces the same outcome that is held within the validation rules. As well as the enforcement of optionality, there are also formatting requirements that have been moved into the XML layer.
Streamlining – Removed and streamlined the XML schema definitions by removing unnecessary fields – for example if the technical standards stipulate a price cannot be reported in Yield, then this format is removed as an option
Validation Rules
Execution agent has been added as an optional field (so where it is relevant in the transaction, is indeed required). This has been added within the Parties to the derivative section of the validation rules. This shows the FCAs attempting to align with CDE (Critical Data Elements) guidance. Note, it has recently been confirmed that ESMA will instead have Execution Agent as an entirely optional data input within the ISO wrapper, which bridges the gap somewhat.
Fields and data required that refer to underlying regulations for definitions are directed at UK based regulations as opposed to the European Union. This will require some internal due diligence to assess any impact.
Fields pertaining to dates differ due to catering for the FCA’s different implementation timeline
To cater for Brexit, the rules allow for different validations depending on whether the trade was concluded before or after the UK left the EU.
Additional conditionality has been added, where the FCA believe it makes sense for a field to be conditional on others or a divergence whereby ESMA may stipulate a field is optional whereas FCA say conditional.
Process and Controls
The FCA grant an additional three hours for trade repositories to make available the information necessary for counterparties to review their UK EMIR reporting submissions. The end of day response mechanism deadline for ESMA is T+1 06:00, whereas for FCA it’s T+1 09:00.
Methods and arrangements for reporting – the FCA are vague in stipulating that any ‘material’ error or omission must be notified to the FCA whereas ESMA provide more separate and distinct definitions with numerical thresholds provided for in the Final Guidelines.
The impact of the divergences between the reporting regimes will depend entirely on each firm’s build. Overall, the FCA are promoting both the ease of implementation (for example by aligning reconciliation tolerances with ESMA) and global harmonisation efforts, however, are not shy in diverging where they believe enhancements are made. There are of course nuances with most global REFITs/Rewrites when compared to one and other and it would be no shock to see regulatory prerogative being used to further rationalise their reporting regimes in the coming years
If you need help with regulatory interpretation, data governance, technical delivery or controls implementation; First Derivative can help you get it done. Contact us today.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. For more information please read our Cookies Policy. By clicking “Accept”, you consent to the use of ALL the cookies.
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
cookielawinfo-checbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
2 years
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_ga_J88N1N8PKD
2 years
This cookie is installed by Google Analytics.
_hjAbsoluteSessionInProgress
30 minutes
No description available.
_hjFirstSeen
30 minutes
This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
_hjid
1 year
This is a Hotjar cookie that is set when the customer first lands on a page using the Hotjar script.
_hjIncludedInPageviewSample
2 minutes
No description available.
CONSENT
16 years 3 months 23 days 13 hours 21 minutes
These cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
IDE
1 year 24 days
Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
test_cookie
15 minutes
The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
VISITOR_INFO1_LIVE
5 months 27 days
A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSC
session
YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devices
never
These cookies are set via embedded youtube-videos.
yt-remote-device-id
never
These cookies are set via embedded youtube-videos.