> Disclaimer: This content is for educational and reference purposes for software builders only. It does not constitute medical, legal, financial, or regulatory advice. Consult a qualified professional before making decisions based on this content.
Algorithmic Trading
Algorithmic trading under MiFID II (MiFID II Art. 4(1)(39), RTS 6) refers to trading in financial instruments where a computer algorithm automatically determines individual parameters of orders. Investment firms engaged in algorithmic trading must have pre-trade controls (order-to-trade ratios, maximum order sizes), real-time monitoring, kill-switch functionality, and annual self-assessment. Builders of automated trading platforms must implement all pre-trade risk controls before orders reach the venue.
Approved Publication Arrangement (APA)
An APA is a reporting mechanism approved by NCAs under MiFID II to publish trade reports on behalf of investment firms for OTC trades. APA-published trade reports satisfy the transparency requirements of MiFID II Articles 20 and 21. Builders of OTC trading platforms must integrate with at least one approved APA to fulfil their post-trade transparency obligations.
ARM (Approved Reporting Mechanism)
An ARM is an entity approved by an NCA to submit transaction reports to the relevant NCA on behalf of investment firms. MiFID II Article 26 requires investment firms to report every transaction in financial instruments admitted to trading on an EU trading venue to their NCA via an ARM. Builders of trading systems must implement ARM integration with a minimum set of RTS 22 fields including LEI, ISIN, price, quantity, timestamps and counterparty details.
Best Execution
Best execution under MiFID II (Art. 27) requires investment firms to take all sufficient steps to obtain the best possible result for their clients when executing orders, considering price, cost, speed, likelihood of execution, size, nature of the order, and any other relevant consideration. Firms must publish annual RTS 27 venue execution quality reports and RTS 28 broker execution quality reports. Builders of OMS platforms must implement best-execution logic that records the venue selection rationale for every order.
Central Counterparty (CCP)
A CCP is a clearing house that interposes itself between counterparties to a trade, becoming the buyer to every seller and the seller to every buyer. MiFID II and EMIR require that certain OTC derivative transactions be cleared through CCPs. Builders of OTC trading platforms must implement CCP clearing connectivity, margin calculation, and real-time position reporting to ensure compliance with mandatory clearing obligations. (MiFID II Art. 29; EMIR Art. 4)
Client Categorisation
Client categorisation under MiFID II (Art. 4(1)(10-12)) classifies clients as Retail Clients, Professional Clients, or Eligible Counterparties. The categorisation determines the level of investor protection (product suitability, disclosure requirements, best-execution obligations) that applies. Builders must implement a categorisation workflow that collects the required client data, evaluates elective professional status criteria, and stores the categorisation decision with its evidence. (MiFID II Art. 4(1)(10-12), Annex II)
Commodity Derivatives
Commodity derivative positions under MiFID II are subject to position limits and position reporting. Competent authorities set position limits on the size of a net position in a commodity derivative that any person can hold. Investment firms with commodity derivative positions above the large trader threshold must report daily to their NCA. Builders of commodity trading platforms must implement position limit monitoring with automated alerts when approaching thresholds. (MiFID II Art. 57-58)
DVC (Double Volume Cap)
The double volume cap mechanism under MiFIR Art. 5 (Regulation (EU) 600/2014, CELEX:32014R0600) limits the use of dark trading (reference price waivers and negotiated transaction waivers) to 4% of trading in a given financial instrument on a single venue and 8% across all EU venues over a rolling 12-month period. Builders of dark pool systems must implement real-time DVC monitoring and automatically switch from dark to lit trading when caps are breached. (MiFIR Art. 5)
ESMA (European Securities and Markets Authority)
ESMA is the EU regulatory agency responsible for the consistent application of MiFID II across EU member states. ESMA publishes technical standards (Regulatory Technical Standards - RTS, Implementing Technical Standards - ITS) that specify the detailed requirements for transaction reporting, transparency, and product governance. Builders must follow ESMA's RTS and ITS, which are directly applicable as EU law, when implementing MiFID II-compliant systems.
Eligible Counterparty
An eligible counterparty under MiFID II (Art. 30) is the highest-level client category. Eligible counterparties include investment firms, credit institutions, insurance companies, pension funds, and other authorised financial institutions. When dealing with eligible counterparties, investment firms have reduced best-execution and disclosure obligations. Builders must implement client categorisation logic that correctly identifies eligible counterparties and applies the appropriate protection regime.
Financial Instrument Reference Data
MiFID II Art. 27 RTS 23 requires investment firms to maintain accurate reference data for all financial instruments they trade. The ESMA Financial Instrument Reference Data System (FIRDS) is the authoritative source for ISINs and reference data for instruments admitted to trading on EU venues. Builders of transaction reporting systems must integrate with ESMA FIRDS to validate ISINs and populate mandatory reference data fields in their RTS 22 transaction reports.
ISIN (International Securities Identification Number)
An ISIN is a 12-character alphanumeric code that uniquely identifies a financial instrument globally (ISO 6166). MiFID II RTS 22 transaction reports require ISINs as the instrument identifier for instruments admitted to trading. Builders of trading and reporting systems must validate ISINs through ESMA FIRDS or a national numbering agency (NNA) API and reject instruments with unrecognised or invalid ISINs before transaction reporting.
KID (Key Information Document)
A KID is a standardised 3-page disclosure document required under the PRIIPs Regulation for packaged retail and insurance-based investment products. The KID must present performance scenarios, costs, risk indicator, and recommended holding period in a standardised format. Builders of retail investment product platforms must implement KID generation, versioning, and delivery workflows. The KID must be provided to retail clients before they conclude a transaction in any PRIIP.
KIID (Key Investor Information Document)
A KIID is the predecessor to the KID for UCITS funds, required under the UCITS Directive. The KIID presents the fund's objectives and investment policy, risk and reward profile (SRRI), charges, past performance, and practical information in a standardised 2-page format. Builders of fund distribution platforms must implement KIID retrieval, version management, and client delivery tracking to demonstrate compliance with pre-sale disclosure obligations.
Legitimate Interest Waiver
MiFID II permits pre-trade transparency waivers for orders held in an order management facility pending disclosure. Under Art. 4(2), competent authorities may waive pre-trade transparency requirements for orders that are large in scale or belong to a class of orders where revealing the order would have a material market impact. Builders of dark pool or block-trading platforms must track waiver type for every order and ensure the correct waiver reason code is reported in post-trade disclosures.
Market Maker
A market maker under MiFID II (Art. 4(1)(7)) is a person who holds themselves out as willing to buy and sell financial instruments on their own account. Investment firms acting as market makers must enter into written market-making agreements with trading venues and must have automated order submission, real-time risk management, and systems capable of operating within the liquidity provision obligations. (MiFID II Art. 17, RTS 8)
NCA (National Competent Authority)
An NCA is the financial regulator in each EU member state responsible for authorising and supervising investment firms and trading venues. MiFID II transaction reports (RTS 22) must be submitted to the NCA of the firm's home member state. Builders of compliance systems for EU investment firms must parameterise their reporting endpoints and field mappings for each NCA, as submission formats may have minor national variations.
OTC (Over-the-Counter) Trade
An OTC trade is a transaction in a financial instrument that does not take place on a regulated market, MTF, or OTF. MiFID II requires post-trade transparency for OTC trades in instruments admitted to trading on EU venues: the trade must be published via an APA within 15 minutes of execution (T+0 for liquid instruments). Builders of OTC trading platforms must integrate with an APA and implement the correct deferred publication flag for large-in-scale trades. (MiFID II Art. 20-21)
OTF (Organised Trading Facility)
An OTF is a multilateral system (not a regulated market or MTF) where third-party buying and selling interests in bonds, structured finance products, emission allowances, and non-equity derivatives can interact. Operators of OTFs must apply a trading methodology for the execution of trades. Builders of electronic platforms that match buyers and sellers of non-equity instruments must determine whether their platform meets the OTF definition and obtain the required NCA authorisation. (MiFID II Art. 4(1)(23))
Position Limit
A position limit is the maximum net long or short position that any person can hold in a commodity derivative at any time. MiFID II Art. 57 requires NCAs to set position limits for commodity derivatives traded on EU venues. Builders of commodity trading platforms must implement real-time position tracking across all venues and accounts, compare positions to the applicable limits, and implement automated blocks when clients approach their position limit. (MiFID II Art. 57)
Product Governance
MiFID II product governance requirements (MiFID II Art. 24(2), Delegated Directive Art. 9-10) require manufacturers and distributors of financial products to identify a target market for each product and ensure it is sold only to clients within the target market. Builders must implement target market data models, compatibility assessments between client profiles and product target markets, and reporting of product-client compatibility decisions. (MiFID II Art. 24, Delegated Directive 2017/593/EU)
Professional Client
A professional client under MiFID II (Art. 4(1)(10), Annex II) is a client who possesses the experience, knowledge, and expertise to make their own investment decisions and properly assess the risks involved. Professional client status may be assigned automatically (per se professional clients: large undertakings, institutional investors, national governments) or electively upon the client's request. Builders must implement the elective re-categorisation workflow, including the three-criteria test for retail-to-professional upgrade.
RTS 22 (Regulatory Technical Standard 22)
RTS 22 specifies the format, content, and timing of MiFID II transaction reports submitted to NCAs. Each report must contain a minimum of 65 fields including the reporting firm's LEI, the client's LEI or national identifier, the instrument's ISIN, price, quantity, execution venue, and trading date-time in UTC. Builders of transaction reporting systems must map their internal trade data model to all 65 RTS 22 fields and submit reports via an ARM within T+1. (Commission Delegated Regulation (EU) 2017/590)
RTS 27 (Execution Quality Report)
RTS 27 requires execution venues (regulated markets, MTFs, OTFs, systematic internalisers) to publish quarterly reports on the quality of trade execution at the venue level. Reports include data on price, cost, speed, likelihood of execution, and market impact. Builders of trading venue platforms must implement automated generation of RTS 27 reports in the ESMA-mandated XML format and publish them on the venue's website by the first business day of the following quarter. (Commission Delegated Regulation (EU) 2017/575)
RTS 28 (Order Routing Report)
RTS 28 requires investment firms to publish annual reports on the top five execution venues per instrument class where they executed orders in the preceding year, together with a summary on quality of execution. Builders of OMS platforms must capture the execution venue for every order, aggregate by instrument class, and generate the annual RTS 28 report in CSV and XML format for publication on the firm's website by 30 April of the following year. (Commission Delegated Regulation (EU) 2017/576)
Retail Client
A retail client under MiFID II (Art. 4(1)(11)) is a client who does not qualify as a professional client or eligible counterparty. Retail clients receive the highest level of investor protection under MiFID II, including: mandatory suitability assessments for investment advice and portfolio management, appropriateness assessments for complex instruments, KID/KIID delivery before transactions, and best-execution reporting. Builders of retail investment platforms must implement all retail-only compliance controls and document them in a compliance manual.
SI (Systematic Internaliser)
A systematic internaliser under MiFID II (Art. 4(1)(20)) is an investment firm that executes client orders against its own proprietary capital, outside a regulated market or MTF, on an organised, frequent, systematic, and substantial basis. SIs must publish binding quotes for liquid equity instruments up to standard market size and non-equity instruments. Builders of internalisation systems must implement SI threshold monitoring and quote publication obligations if the SI threshold is met. (MiFID II Art. 18)
SFTR (Securities Financing Transactions Regulation)
SFTR (EU 2015/2365) requires financial counterparties and non-financial counterparties above threshold to report securities financing transactions (repos, securities lending, margin lending) to a trade repository within T+1. SFTR reports contain 153 fields covering transaction details, collateral, and clearing information. Builders of repo or securities lending platforms must implement SFTR reporting pipelines, including ISO 20022 XML message generation and connectivity to authorised trade repositories. (EU 2015/2365)
Suitability Assessment
A suitability assessment under MiFID II Art. 25(2) is required when an investment firm provides investment advice or portfolio management services. The firm must collect information on the client's knowledge and experience, financial situation, and investment objectives, and assess whether the recommended service or product is suitable. Builders must implement suitability assessment workflows that capture and store all client data inputs, record the suitability determination with its reasoning, and generate suitability reports for delivery to clients before execution.
Trading Venue
A trading venue under MiFID II (Art. 4(1)(24)) means a regulated market, MTF, or OTF. Investment firms are required to execute transactions in shares admitted to trading on regulated markets on a regulated market, MTF, SI, or equivalent third-country trading venue (share trading obligation - STO). Builders of equity trading systems must implement STO logic that routes orders to compliant venues and flags OTC transactions that may violate the STO. (MiFID II Art. 23)
Transaction Report
A transaction report under MiFID II Art. 26 is a report that every investment firm must submit to its NCA for each transaction in any financial instrument admitted to trading or traded on a trading venue. The report must be submitted by T+1 via an ARM. Transaction reports are the primary tool for market abuse detection by NCAs. Builders must implement transaction reporting pipelines that capture all 65 RTS 22 mandatory fields and submit reports within the prescribed deadline. (MiFID II Art. 26; RTS 22)
UCITS (Undertakings for Collective Investment in Transferable Securities)
A UCITS is a type of EU-regulated investment fund that can be marketed and sold to retail investors across the EU. UCITS funds are subject to strict investment restrictions, diversification requirements, and mandatory KIID disclosure. Builders of fund distribution platforms must implement KIID retrieval, version control (KIIDs must be updated at least annually), and client delivery tracking with timestamps. (UCITS Directive 2009/65/EC, as amended)
Waiver (Pre-Trade Transparency)
A pre-trade transparency waiver under MiFIR Art. 4 (Regulation (EU) 600/2014, CELEX:32014R0600) allows a competent authority to waive the obligation to publish pre-trade order information for orders that are large in scale (LIS), reference price (using mid-point of the EBBO), or negotiated transaction waivers. Each waiver use must be flagged in post-trade reports with the appropriate waiver indicator. Builders must store the waiver indicator as part of the order lifecycle record and include it correctly in post-trade APA publications. (MiFIR Art. 4; RTS 1)
EMIR (European Market Infrastructure Regulation)
EMIR (EU 648/2012) is the EU regulation governing OTC derivatives, central counterparties, and trade repositories. EMIR requires mandatory clearing of standardised OTC derivatives through CCPs and bilateral risk mitigation measures (daily valuation, dispute resolution, portfolio reconciliation) for non-cleared OTC derivatives. Builders of OTC derivatives platforms must implement EMIR-compliant clearing workflows, collateral management, and reporting pipelines to authorised trade repositories. (Regulation (EU) 648/2012)
LEI (Legal Entity Identifier) - MiFID II Context
Under MiFID II RTS 22, every investment firm submitting transaction reports must use its own LEI as the reporting party identifier, and must use the client's LEI (or a national identifier for retail clients) as the client identifier field. LEIs must be renewed annually with the Global LEI Foundation (GLEIF); a lapsed LEI is an invalid identifier in transaction reports. Builders must implement automated LEI renewal alerts and validate LEI status against the GLEIF API before submitting RTS 22 reports. (MiFID II Art. 26; RTS 22 Field 4)
Market Abuse Regulation (MAR)
MAR (EU 596/2014) prohibits insider dealing, market manipulation, and unlawful disclosure of inside information in EU financial markets. MiFID II transaction reports submitted by investment firms to NCAs are the primary data source for NCA market abuse surveillance. Builders of trading platforms must implement MAR-compliant suspicious transaction and order reporting (STOR) procedures, inside information management policies, and insider lists. (Regulation (EU) 596/2014)
MTF (Multilateral Trading Facility)
An MTF under MiFID II (Art. 4(1)(22)) is a multilateral system operated by an investment firm or market operator that brings together multiple third-party buying and selling interests in financial instruments in a non-discretionary way. MTFs must comply with pre- and post-trade transparency requirements, transaction reporting, and market abuse surveillance obligations. Builders of electronic trading platforms that match multiple third-party interests must determine whether their system meets the MTF threshold and obtain NCA authorisation. (MiFID II Art. 18-20)
Order Execution Policy
An order execution policy under MiFID II Art. 27 is the written document that specifies how an investment firm will execute client orders to achieve best execution. The policy must list the execution venues used for each class of financial instrument and must be reviewed at least annually and whenever a material change occurs. Builders of OMS platforms must record the execution venue selection decision for every order, linking it to the firm's current order execution policy version, to provide an auditable best-execution evidence trail.
PRIIPs Regulation
The PRIIPs Regulation (EU 1286/2014) requires manufacturers and sellers of packaged retail and insurance-based investment products to prepare a standardised Key Information Document (KID). The KID must not exceed 3 pages and must present performance scenarios, costs, risk indicator (SRI), recommended holding period, and complaint information. Builders of retail investment product platforms must implement automated KID generation from product master data, version control, and delivery tracking with date/time stamps. (Regulation (EU) 1286/2014)
Wrapper (Product Wrapper)
In MiFID II product governance, a wrapper is a legal structure (UCITS fund, structured product, insurance wrapper) that packages an underlying financial instrument for distribution to clients. Each wrapper is a separate product for product governance purposes and requires its own target market identification. Builders of product lifecycle management systems must model each wrapper as a distinct product entity with independent target market and distribution strategy attributes. (MiFID II Delegated Directive Art. 9-10)