The table below provides background on the various initiatives underway within the FIX Trading Community™. If you are interested in learning more details about or getting involved in any of the below initiatives, please contact the organisation’s Program Office.
|Name of Initiative||Purpose||Latest Status|
|Brexit||The impact of Brexit on how the cross-border trading between UK and EU in financial services and capital markets is still unknown. However, there will be an impact on potential trading scenarios which will impact transaction lifecycle in relation to reference data, transactional data, and standards.||Identified values for Shared Trading Obligation identification to be used in conjunction with OrderAttributeType (2594)|
Extension produced to address cases where an STO is defined out-of -band.
Recommended FIX tags for the purpose of MiFID II post trade transparency and STO determination
Co-ordinating with the MIFID II Reference Data Working Group to discuss the impact of difference of data upon the likely scenarios of divergence from the UK and ESMA FIRDS Database.
|Consolidated Audit Trail (CAT)||To further assist firms with their CAT implementations specifically looking at where FIX coverage is necessary to support the various CAT reporting requirements whether it be through existing tags or the creation of new tags.||The group currently has two areas of focus:|
FIX to CAT Mapping Exercise – Identified FIX extensions needed to address requirements related to data reporting required by the CAT NMS plan.
Identified a standardized use of FIX to communicate Firm Designated Identifier) FDIDs across different market participants. FDID is a unique identifier for each trading account required to provide data to the central repository.
|Consolidated Tape (CT)||The EU Commission and ESMA are pursuing the creation of a Consolidated Tape. Since March 2019 the Commission and ESMA have hosted a number of discussions and roundtables to which FIX has been invited to respond.||Currently, there are two active working groups looking at the data standards that would be required to provide a clear and unambiguous consolidated tape. Due to the differing natures of Equities and Fixed Income, those standards are being bifurcated into separate work streams, but are following a similar path of considering all of the trade scenarios in use, identifying where additional trade flags are required to ensure absolute clarity of the meaning of the data, and reviewing and revisiting the trade flows trees that were originally created by the working groups during MiFID implementation.|
|Cybersecurity||To discuss current issues and challenges on this front, review processes and procedures, and leverage the community to develop best practices on how best to handle security concerns.||The initial FIX-over-TLS (FIXS) standard was produced for using the Internet Transport Layer Security (TLS) protocol with FIX. Follow link in the first column to access the standard. The group is now looking at better ways to authenticate firms at the application level.|
A new initiative, FIX Authentication (FIXA), brings a number of benefits, including improved security, greater flexibility and ease of use as well as removing out-of-date methods. The current thinking is to leverage HTTP Authentication which is widely used on the Internet today, and introduce it as a new framework with authentication schemes for FIX.
|Digital Asset||The Digital Asset Working Group centers around the development of best practices for the electronic trading of digital assets (Cryptocurrencies, Crypto assets, STOs) leveraging the FIX family of standards.|
PODCAST: Ryan Pierce, co-chair of the FIX Digital Assets Working Group, provided a brief update on the current status of the working group and the development of the Digital Token Identifier (DTI) standard.
WEBINAR: Second in a series of FIX Trading Community webinars, a panel of experts discuss the institutional financial services readiness for the leading digital asset categories.
|The group has produced drafts of best practices document for buy-side to sell-side trading, and between market participant to trading venue. This group has taken a prominent role in the ISO TC68/SC8/WG3 initiative to create a standard symbology or registry for digital tokens, referred to as a Digital Token Identifier (DTI). Additionally, the group provides a forum for communication between various tokenization standards and is actively promoting and supporting industry efforts to create codes of conduct and digital asset classification schemes.|
FIX has a modern web-based technology stack using JSON and SBE encoding operating over FIXP, the FIX high performance session layer, which compliments the cryptocurrency trading venues(exchanges).
|Execution Venue||To standardise the reporting of the executing venue and create a set of guidelines to provide greater transparency for buy-side clients about where and how their orders are executed by their brokers.|
PODCAST: Brian Lees, Capital Group and co-chair of the Global Buyside Committee, discusses Execution Venue Reporting Guidelines.
|An updated version of the ‘Execution Venue Reporting Best Practices’ was distributed (see link in first column).|
The latest revision produced addresses changes to Tag29 guidelines to reflect MiFID requirements and the impact that MiFID was having on determination of whether executions were principal or agency in Tag 29 as well as their CSA Eligibility. A collaborative exercise which included buyside and sell side participants from around the globe resulted in a global approach for some values and the identification of regional flavours for others. Additionally, changes to Tag 851 include new values and the codifying of values already being utilized in the industry.
|EMEA Equities Business Practices||Since the implementation of MiFID II 2½ years ago the Equity markets continue to develop and as firms understand more about the impact of the regulation and how it impacts FIX. Whilst significant progress continues to be made, there is still scope for further improvement and this will likely only to be achieved through ongoing industry collaboration. This group is being reinstated after having been side-lined during the implementation of MiFID where a number of different groups were set up given the magnitude of the implementation task.||The aim of the group will be to advance the use of FIX and open industry data standards in the Equities arena working with buy-side, sell-side, venue and all members, through improved manual and automated processes and – where appropriate – the adoption of new automation initiatives:|
|EMEA Fixed Income Business Practices||Fixed Income business practice has improved markedly over the past decade as a result of regulation, drive for more efficiency and associated cost savings, and the never-ending pursuit of automation.||The aim of the group is will be to advance the use of FIX and open industry data standards in the Fixed Income arena working with buy-side, sell-side, venue and all members, through improved manual and automated processes and – where appropriate – the adoption of new automation initiatives and look at issues such as:|
|FICC||To oversee the multi-asset class activities and strategic considerations of FIX with regards to the Derivatives, Fixed Income and Foreign Exchange areas especially given many of the common and overlapping initiatives in the pre-trade, trade and post-trade space. Market consolidation, regulatory changes often involve multiple asset classes, and portfolio diversification increases the need for a comprehensive view.||Several sets of FIX best practices have been developed in both the fixed income and foreign exchange arenas. Additionally, a MiFID FICC Advisory Subgroup was developed to work alongside existing FIX MiFID working groups to review content and standards that are being created in the organisation and for the group to review from a FICC perspective.|
|FIXatdl||The FIXatdl (previously known as the Algorithmic Trading working group is looking to improve and update the FIXatdl standard which enables algorithmic strategy providers to release specification to clients in a computer readable XML format. Objective is to add new functionality to the current version, FIXatdl 1.1 to address new features and changes which have been proposed by several sell-side firms and vendors of OMS platforms which support FIXatdl.||The group is working towards finalizing FIXatdl 1.2 with new features to be included:|
|FIX Orchestra||To address the work of generating machine readable rules for FIX Specifications to improve operational efficiency and the value of the FIX Protocol by reducing the time and effort it takes to onboard, certify, and deploy new FIX connections with counterparties.||The GTC believes the FIX Orchestra Technical Specification to now be of suitable quality and having achieved fit for purposefulness to be adopted. Therefore, the FIX Orchestra Draft Standard will require two implementations to move it to Technical Standard – Version 1.0. Potential adopters are strongly encouraged to begin working with the v1.0 Draft Standard.|
|Full Lifecycle and Ecosystem||Many of these efforts solve a particular problem or take a vertical approach, sometimes missing an opportunity to connect the full investment life cycle and broader ecosystem horizontally to create additional leverage and support a wider set of risk and efficiency best practices, and solve other non-discretionary and business drivers. The full life cycle and ecosystem working group will take a more holistic and broader view in driving FIX connectivity and create new opportunities to develop end to end processing. This group will complement established FIX working groups and seek new ways to advance overall FIX value and return on investment.|
|High Performance||To focus on specific aspects where fit-for-purposefulness of FIX for high performance financial transactions can be improved.||The working group which is organized into subgroups focused on specific aspects where fit-for-purposefulness of FIX for high performance financial transactions can be improved, continues to meet. Subgroups include Application layer, Session layer, FIX Simple Binary Encoding (SBE), ASN.1 and Google Protocol Buffers. SBE and FIXP were moved to GitHub to add participation outside of the FIX Trading Community.|
|MiFID II||To discuss and address specific regulatory technical standards (RTS) items and provide guidelines and best practices to meet these regulatory requirements.||The Best execution and Reference data MIFID II subgroups are currently revisiting:|
|Market Model Typology (MMT)||The FIX MMT data standard is an efficient operational solution for fulfilling trade flagging requirements raised by regulators.|
MiFID/MiFIR RTS 1 and RTS 2 (Level 2 regulation) prescribe the adjunction of so-called trade flags embedded in outgoing market data messages. Trade flags provide standardised explanations about the type of price formation, the level of pre- and post-trade transparency that led to executions. FIX MMT supports the unambiguous identification of all execution types, irrespective of who is the original data producer. Consistent trade flags are of paramount importance to investors for assessing the quality of the price information they receive.
Consistent codes get disseminated efficiently across the market data value chain without the need of any local re-interpretation. MMT has been designed to support straight-through processing in data feeds, databases and display services.
FIX MMT data standard delivers higher data quality and lower processing costs.
|The current version 3.04 of MMT data standard has been in place since MiFID/MIFR entry into force early 2018. More than 75% of all equity execution messages in Europe currently convey MMT flags. Latest update of the MMT FAQ on:|
|Monitoring, Onboarding and Software Testing (MOST)||To raise the quality and reliability of platforms operated by FIX Trading Members. Decreasing the time to market and reduce costs related to outages and software issues in production.||The group will create a catalogue of tools & methods for Monitoring, Onboarding and Software Testing of FIX-related applications. Discuss open-source and commercial solutions available for the members. Create technical guidelines related to reliability of platforms.|
|Post-Trade||To explore how to effectively address the many challenges impacting global post-trade processing to encourage the development of increased transparency, reduced costs and greater efficiencies in this space.||The group released a series of post-trade payment processing messages as an extension of FIX messaging. The group will begin moving on to create materials around netting, instruction, and settlement management. There will also be a focus on the new EU settlement regime, CSDR, as a use case to bring together updated FIX messaging in a European context.|
|Repo||To develop and maintain a standard and a detailed set of guidelines and message specifications for automating the full life cycle of Repos via FIX, including post trade, asset servicing, collateral management, regulatory reporting through the full life cycle and eco system of Brokers, Clients, Custodians and Service Providers.||The group will identify the FIX messages per each categorization of Repo components. Most recently, the group has published a gap analysis for public comment addressing the requirements identified by the group related to trade and post-trade workflows for bilateral repo transactions. Additionally, two recommended practices on bilateral trade and post-trade have also been published.|
The group will continue exploring tri-party repos and produce similar documents to identify any existing FIX messages already in place and gaps where new FIX messages is to be introduced.
|Securities Lending||To develop a set of messages to support automated processing of securities lending. The focus will be on cleared securities lending but consideration will be given for extensibility to non-cleared activity. The messages are intended to support loans collateralized by cash and non-cash securities and to support practices by global CCPs that cleared securities lending transactions.||The group is in the process of generating an entire set of security lending messages for both pre and post trade. The group is working in sync with the SFTR Working Group identifying the gaps and mapping the workflow/fields required for securities lending.|
|SFTR||To assist firms as they meet the challenges posed by the European Commission’s introduction of the Securities Financing Transactions Regulation (SFTR). Identify the data, operational and reporting issues created by the introduction of SFTR, and guide the industry in associated implementation and best practice.||The group published a gap analysis addressing the requirements of EU SFTR transactions include repurchase agreements (repos), buy-sell back/sell-buy back, securities lending and margin lending transactions. The group is currently reviewing the list of fields put together by ICMA/ISLA (and augmented by FIX) that are required between counterparties to meet reporting and matching requirements for SFTR. The group has added some fields we consider to be useful and once the list has been validated, FIX will cross-refer these fields to the relevant FIX tags. The group will then work to investigate each field to complete the validation of the list of fields, following which FIX can cross-refer to FIX tags, for inclusion into a FIX Best Practice document.|