Chapter 20: Exercises — Pre-Trade and Post-Trade Transparency Requirements

Exercise 1: Pre-Trade Waiver Classification

Learning objective: Apply the MiFID II pre-trade waiver regime to specific trade scenarios and determine whether a waiver applies, which waiver type, and whether the DVC is relevant.

Background:

Cornerstone Financial Group's execution desk is reviewing the following five pending equity trades. For each trade, the desk must determine: (a) whether a pre-trade transparency waiver is applicable, (b) if so, which waiver type, and (c) whether the Double Volume Cap is a relevant compliance consideration.

Reference information: - ESMA LIS threshold for Instrument A: EUR 650,000 notional - ESMA LIS threshold for Instrument B: EUR 4,200,000 notional - Instrument A: FTSE 250 mid-cap equity; liquid; standard market size EUR 10,000 - Instrument B: DAX large-cap equity; liquid; standard market size EUR 50,000 - Instrument C: AIM-listed small-cap equity; illiquid; LIS threshold EUR 90,000 - Instrument D: FTSE 100 large-cap equity; liquid; standard market size EUR 50,000

Tasks:

1. For each trade, identify whether a pre-trade waiver applies and, if so, which waiver type (LIS, RPW, NTW, or OMF). Explain your reasoning.

2. For each trade where the DVC is relevant, explain what the compliance team must check before routing the order.

3. For Trade 3, what alternative execution strategies are available to Cornerstone now that the RPW is suspended? Evaluate the trade-offs of each.

4. Would the answer to Trade 2 change if Instrument B's dark pool was also approaching its 4% venue DVC threshold? Explain what the compliance team should do.

Worked Guidance:

Trade 1 — Reference Price Waiver (RPW), DVC relevant: The trade notional (EUR 320,000) is below the LIS threshold (EUR 650,000), so the LIS waiver is not available. Execution at mid-point in a dark pool can proceed under the Reference Price Waiver. However, the RPW counts toward the DVC. Before routing, Cornerstone must confirm that the venue's rolling 12-month dark pool share of Instrument A is below 4%, and that the market-wide dark share is below 8%.

Trade 2 — LIS Waiver preferred; RPW also potentially available, DVC irrelevant for LIS: The notional (EUR 5,100,000) exceeds the LIS threshold (EUR 4,200,000). The LIS waiver is available and is the preferred route — it is not subject to the DVC. The firm could also use the RPW (if the DVC permits), but the LIS waiver is superior because it removes DVC exposure. Recommendation: use LIS waiver.

Trade 3 — No RPW available; RPW suspended by ESMA: If ESMA has published a suspension notice for this instrument on this venue under the DVC, the Reference Price Waiver is not available for six months. The LIS waiver is not available because the notional (EUR 320,000) is below the LIS threshold (EUR 650,000). Options: (a) route to a lit exchange (full pre-trade transparency, market impact risk); (b) seek a large-in-scale bilateral negotiation (NTW) if a willing counterparty can be found at above-LIS size — but the notional here is below LIS, making this difficult; (c) accept lit execution and manage with iceberg order functionality (OMF waiver) to limit visible size. The right answer is likely lit execution with an iceberg order.

Trade 4 — Negotiated Transaction Waiver (NTW): This is a bilateral OTC trade in an illiquid instrument. One of the qualifying conditions for the NTW is that the instrument is illiquid. The trade qualifies for an NTW waiver. The notional is below the LIS threshold so the LIS waiver is not available independently, but the illiquid instrument condition for NTW is satisfied. NTW on equity trades does count toward the DVC — check DVC compliance.

Trade 5 — Order Management Facility Waiver (OMF): This is a lit market trade using iceberg/reserve order functionality. The OMF waiver permits the reserve quantity of an iceberg order to be hidden from the order book. The visible portion (the displayed quantity) is subject to pre-trade transparency. The OMF waiver does NOT count toward the DVC — this is a lit market mechanism.

Exercise 2: Double Volume Cap Threshold Calculation

Learning objective: Calculate venue-level and market-wide dark pool trading percentages and determine whether DVC thresholds are breached.

Background:

Cornerstone's compliance team is reviewing a six-month trading data extract for ISIN GB00BH4HKS39 (a UK mid-cap equity). The extract covers all EU and UK trading venues. Post-Brexit, the DVC applies only to EU-listed shares on EU venues; however, the firm's UK compliance team applies the same monitoring logic internally even for UK shares, to facilitate consistent oversight.

Data: Total trading in GB00BH4HKS39 (shares, rolling 12-month period)

Tasks:

1. Calculate total volume across all venues (lit + dark).

2. Calculate the dark pool volume traded on each dark venue as a percentage of total volume. Which venues, if any, breach the 4% venue-level DVC cap?

3. Calculate the total dark pool volume across all venues as a percentage of total volume. Does the market-wide dark share breach the 8% cap?

4. If the XLON Dark pool was approaching but had not yet breached the 4% cap, at what absolute volume (in shares) would the cap be triggered? Calculate the exact threshold share count.

5. Cornerstone's institutional desk has a pending order to sell 500,000 shares of GB00BH4HKS39 in XLON Dark under the RPW waiver. Given the current volumes, what is the DVC status after this order executes? Would any threshold be breached?

Worked Solution:

Step 1 — Total Volume: Lit: 42,000,000 + 18,500,000 + 11,000,000 + 7,200,000 = 78,700,000 shares Dark: 3,800,000 + 2,100,000 + 1,200,000 + 890,000 = 7,990,000 shares Total: 86,690,000 shares

Step 2 — Venue-level dark percentages: - XLON Dark: 3,800,000 / 86,690,000 = 4.38% — BREACH (>4%) - BATD: 2,100,000 / 86,690,000 = 2.42% — within cap - Turquoise Dark: 1,200,000 / 86,690,000 = 1.38% — within cap - Instinet Dark: 890,000 / 86,690,000 = 1.03% — within cap

Result: XLON Dark has breached the 4% venue cap. RPW should already be suspended on XLON Dark for this ISIN.

Step 3 — Market-wide dark percentage: 7,990,000 / 86,690,000 = 9.22% — BREACH (>8%)

Result: The market-wide 8% cap is also breached. RPW should be suspended across all venues for this ISIN.

Step 4 — Exact threshold for XLON Dark: 4% cap threshold at current total volume = 0.04 × 86,690,000 = 3,467,600 shares XLON Dark has already exceeded this (3,800,000 > 3,467,600). The cap was breached at 3,467,601 shares.

Step 5 — After Cornerstone's 500,000 share order: New XLON Dark volume: 3,800,000 + 500,000 = 4,300,000 (venue already breached — order should not be routed here under RPW) New total: 86,690,000 + 500,000 = 87,190,000 New market-wide dark: 8,490,000 / 87,190,000 = 9.74% — still in breach.

Recommendation: Cornerstone should NOT route this order to XLON Dark under the RPW — both the venue cap and the market-wide cap are already breached. The firm should route to a lit venue or seek an LIS-exempt block trade.

Exercise 3: Post-Trade Reporting Timeline Calculation

Learning objective: Apply MiFIR RTS 1 and RTS 2 post-trade publication timelines to a portfolio of trades with different asset classes and liquidity classifications.

Background:

Priya Nair is reviewing a morning trading summary for a European asset manager. The following five trades were executed before 10:00 on a Tuesday (a full trading day). Priya must calculate the APA publication deadline for each trade and flag any where the deadline has already passed.

The current time is 10:45 (all times are CET). Trading day closes at 17:30 CET.

Tasks:

1. Calculate the APA publication deadline for each trade. Express the deadline as a specific time.

2. As of 10:45, which deadlines have already passed? For those trades, what are the compliance implications?

3. For Trade D, the firm argues that because the notional is above EUR 50 million, a 48-hour deferral applies rather than end-of-day. Evaluate this argument. Is it correct?

4. Trade C was executed in a dark pool under the RPW waiver. Does the waiver affect the post-trade publication obligation? Explain.

5. For Trade E, the IRS notional (EUR 50 million) exceeds the LIS threshold (EUR 5 million). What deferral, if any, applies?

Worked Solution:

Trade A — Liquid sovereign bond, OTC: Publication window: 15 minutes. Deadline: 09:12:30 + 15 min = 09:27:30. As of 10:45, this deadline has passed. The firm is already in breach — the trade should have been published at 09:27:30. Immediate escalation required.

Trade B — Illiquid corporate bond, notional EUR 28M: Illiquid instrument; notional EUR 28M is below the EUR 50M threshold for 48-hour deferral and below any LIS threshold. Standard deferral applies: end of trading day. Deadline: 17:30 CET today. As of 10:45, not yet in breach. The firm has approximately 6 hours and 45 minutes remaining.

Trade C — Equity, dark pool, RPW waiver: Equities: 1-minute publication window regardless of execution method or waiver. Deadline: 10:22:44 + 1 min = 10:23:44. As of 10:45, this deadline has passed. In breach. Note: The RPW waiver suspends pre-trade transparency — it does NOT suspend post-trade transparency. This is a common compliance misunderstanding. Escalate immediately.

Trade D — Illiquid corporate bond, notional EUR 95M: Illiquid instrument; notional EUR 95M exceeds the EUR 50M threshold. 48-hour deferral applies. Deadline: 08:30:00 on Tuesday + 48 hours = 08:30 Thursday. As of 10:45 Tuesday, not in breach. The firm's argument is correct for this trade.

Trade E — Liquid IRS derivative, notional EUR 50M above LIS: Liquid derivative; notional exceeds LIS threshold of EUR 5M. For liquid derivatives with large notional above the LIS threshold, a deferral period applies. Under RTS 2, this is typically 48 hours for liquid derivatives above LIS. Deadline: 10:00:00 + 48 hours = 10:00 Thursday. Not in breach as of 10:45 Tuesday.

Exercise 4: Coding Exercise — Extending the PostTradeReporter

Learning objective: Extend the PostTradeReporter class from the chapter to add SI status monitoring logic.

Background:

Rafael Torres is advising a broker-dealer that suspects it may have acquired Systematic Internalizer status in several equity instruments without having assessed this formally. He needs a Python function that can take a transaction history and determine which instruments exceed the SI thresholds.

Tasks:

Using the Trade dataclass and the structure of PostTradeReporter introduced in the chapter, implement the following function:

def assess_si_status(
    trade_history: pd.DataFrame,
    total_eu_volume_by_isin: pd.DataFrame,
    lookback_months: int = 6
) -> pd.DataFrame:
    """
    Assess Systematic Internalizer status for each instrument in the trade history.

    Args:
        trade_history: DataFrame with columns:
            - 'isin': str
            - 'trade_date': datetime
            - 'volume': float (shares/units)
            - 'trade_id': str
        total_eu_volume_by_isin: DataFrame with columns:
            - 'isin': str
            - 'total_eu_volume': float (total EU trading in instrument over period)
        lookback_months: Number of months to look back (default 6)

    Returns:
        DataFrame with one row per ISIN, columns:
            - 'isin': str
            - 'avg_daily_trades': float
            - 'firm_volume_pct': float (firm volume as % of total EU volume)
            - 'frequency_threshold_met': bool (avg > 1 trade/day)
            - 'volume_threshold_met': bool (firm pct > 0.4%)
            - 'si_status': bool (True if BOTH thresholds met)
            - 'recommendation': str
    """
    pass  # Implement this function

Requirements:

1. Filter trade_history to the lookback period (default 6 months from the most recent trade date in the dataset).

2. For each ISIN in the filtered dataset, calculate: - The number of trading days in the lookback period (assume 252 trading days per year; use the actual date range from the data). - The average number of trades per day (total trades / trading days). - The firm's volume as a percentage of total EU volume for that instrument.

3. Apply the SI test: SI status is triggered when BOTH the frequency threshold (>1 trade/day on average) AND the volume threshold (>0.4% of EU volume) are met.

4. For each ISIN, generate a recommendation string: - If SI status triggered: "SI STATUS REQUIRED — notify NCA and implement quote obligations" - If frequency met but not volume: "MONITOR — frequency threshold met; volume below 0.4%" - If volume met but not frequency: "MONITOR — volume threshold met; frequency below once/day" - If neither: "NO SI STATUS"

5. Write a test using a small synthetic dataset (3 ISINs, 6 months of daily trade data) to verify the output.

Bonus challenge: Extend the function to also check the alternative size threshold — 15,000 transactions per calendar year — and update the SI determination accordingly.

Exercise 5: Research Exercise — UK Consolidated Tape: Current Status and Timeline

Learning objective: Independently research the current status of the UK consolidated tape initiative and evaluate its implications for compliance technology.

Background:

During a client meeting, Priya Nair was asked by a UK asset manager whether they should "wait for the consolidated tape" before investing in new market data infrastructure or build out their own multi-APA data aggregation capabilities now.

Part A — Research Tasks:

Using publicly available regulatory documents (FCA Policy Statements, FCA Consultation Papers, Financial Services and Markets Act 2023, and FCA Market Data Consolidation consultation), research and answer the following:

1. What legislative framework enables the FCA to establish a UK consolidated tape? Which specific sections of the Financial Services and Markets Act 2023 are relevant?

2. What is the FCA's stated design preference for the UK equity consolidated tape — specifically, does it propose a pre-trade tape, a post-trade tape, or both? How does this differ from the EU's MiFIR Review approach?

3. As of 2024–2025, what stage is the UK consolidated tape procurement at? Has a provider been selected? When is the tape expected to go live?

4. Who are the key stakeholders who have engaged in the UK consolidated tape consultation, and what have been the main points of contention (e.g., revenue sharing, data quality, latency)?

Part B — Analysis:

5. Based on your research, draft a recommendation for the UK asset manager: should they invest now in multi-APA data aggregation infrastructure, or wait for the consolidated tape? Your answer should address: - The expected timeline for a live UK consolidated tape. - The data quality and coverage that the tape is expected to provide. - The risk of over-investing in infrastructure that becomes redundant. - The risk of under-investing and remaining dependent on manually stitched market data in the interim.

6. How would your recommendation change if the asset manager were a large firm vs. a boutique firm with limited technology budget?

Suggested primary sources: - FCA Consultation Paper CP23/15: "UK Consolidated Tape for Bonds" - FCA Policy Statement on Wholesale Markets Review - Financial Services and Markets Act 2023 (UK) - ESMA Consultation Paper on Consolidated Tape (for comparison) - AFME publications on consolidated tape design

Note: Exercises 1–3 have worked solutions or guidance in the text above. Exercise 4 is a coding implementation task. Exercise 5 is an open research exercise — there is no single correct answer; answers will depend on the regulatory developments current at the time of study.