A tailored course, built for your situation
Mastering MiFID II for Capital Markets Compliance Practitioners
Build defensible, source-backed compliance reasoning that holds up under peer review and regulatory scrutiny.
The situation this course is for
You’ve done the work, followed the process, and documented your controls, but in review sessions, your rationale gets questioned. Not because it's flawed, but because you can't instantly point to the exact article, precedent, or example that supports your interpretation. That gap erodes confidence, even when you're correct.
Who this is for
Senior compliance practitioner in financial services, responsible for implementing and defending MiFID II requirements within audit cycles and cross-functional reviews.
Who this is not for
Entry-level analysts who don’t own interpretation calls, or executives who rely on teams to explain details. This is for individual contributors who must defend their judgment directly.
What you walk away with
- Cite MiFID II articles and ESMA guidance accurately during peer challenges
- Walk through the reasoning behind trade reporting rules using real audit examples
- Reference specific provisions in RTS 22 and RTS 27 when questioned on data transparency
- Explain best execution obligations with sourced case examples from past EBA findings
- Structure documentation so your logic is clear, traceable, and defensible on first review
The 12 modules (with all 144 chapters)
- Tracing MiFID II from Directive the current cycle to RTS finalisation
- Key differences between MiFID I and MiFID II scope
- How ESMA’s Q&As influence national regulator decisions
- The role of the European Commission in delegated acts
- Understanding the separation of execution and research
- When MiFID II applies vs when CFTC or SEC rules take precedence
- Structure of Title I through Title VI in practical terms
- How RTS and ITS specifications change implementation
- The purpose of Article 4 exemptions and how they’re audited
- Differences between firm-level and product-level compliance
- How Brexit altered MiFID II application for UK-linked entities
- Mapping MiFID II to internal policy numbering systems
- Defining best execution under Article 27 and RTS 27
- How to structure a broker assessment methodology
- Documenting venue quality beyond latency metrics
- Using transaction cost analysis as supporting evidence
- Responding to pushback on dark pool usage
- When cost transparency outweighs execution speed
- How ESMA’s the current cycle findings shifted broker review expectations
- Mapping execution quality to client type and order size
- Integrating liquidity provider data into decision logs
- Handling pushback from internal quants on routing logic
- Proving best execution when no single venue wins on all metrics
- Building a defensible rebuttal to 'we could have done better' claims
- Understanding the 65 fields required in a standard report
- Common errors in execution timestamping and how to avoid them
- Mapping ISO 20022 standards to MiFID II report templates
- When to report off-market trades and corrections
- Handling OTC derivatives under SFTR overlap
- Client classification fields: professional vs eligible counterparty
- Using LEIs correctly in counterparty identification
- Timezone handling for cross-border executions
- Reconciling internal trade logs with ARM submissions
- Responding to regulator queries on report backlogs
- How CESR’s guidance shapes ARM data quality expectations
- Building a checklist for pre-submission validation
- Defining what qualifies as an inducement under Article 22
- When bundled commissions breach inducement rules
- Creating a compliant research payment policy
- Using RPA to track research consumption and budget use
- Documenting approval for minor non-monetary benefits
- How ESMA’s the current cycle review tightened soft dollar rules
- Handling third-party content distribution within compliance
- When internal research must be treated as an inducement
- Separating research budgets from execution budgets in practice
- Auditing research spend against analyst engagement logs
- Responding to internal audit on desk-level research usage
- Building a defensible position when peers push back on allocations
- Mapping MiFID II product governance to PRIIPs KID rules
- Defining target market for structured products
- Documenting distribution restrictions by jurisdiction
- Client suitability assessments for leveraged products
- When a product must be redesigned based on review data
- Using complaint trends to inform target market updates
- Integrating CRM data into product governance reviews
- How ESMA’s the current cycle guidelines raised bar for retail products
- Handling cross-border distribution conflicts
- Building audit trails for product approval committees
- Responding to regulator follow-ups on distribution logs
- Creating a defensible rationale for high-risk product approvals
- Defining what qualifies as algorithmic trading under RTS 11
- Required pre-trade risk controls for automated strategies
- Minimum tick size compliance in algorithm design
- When algo strategies require regulator notification
- Post-trade surveillance of self-trading patterns
- Documenting circuit breaker logic for internal review
- Testing protocols for latency-sensitive strategies
- Integrating market data quality checks into algo logic
- Handling backtesting discrepancies with regulators
- How ESMA’s the current cycle report changed algo monitoring expectations
- Mapping algo logic to trade reporting categories
- Building defensible justifications for strategy modifications
- Top 10 errors identified in FCA enforcement actions
- How timestamp precision affects execution sequence claims
- Correcting reports without triggering scrutiny
- Handling multi-leg trades and composite instruments
- When to report novations and when not to
- Mapping OTC confirmations to transaction reports
- Reconciling internal blotter data with ARM output
- Responding to ESMA aggregate data queries
- Using sample datasets from past enforcement cases
- Building traceability from trade capture to final report
- How peer firms resolved backreporting obligations
- Creating a defensible rationale for timing variances
- Defining functional independence under Article 16
- Documenting budget and staffing decisions for regulators
- Creating clear escalation paths for breach reporting
- When compliance can halt a trading strategy
- Integrating with internal audit without duplication
- Using past enforcement cases to justify headcount
- Balancing control ownership across front and middle office
- Reporting directly to senior management with evidence
- Handling conflicts between PnL and compliance mandates
- Building defensible positions on resourcing constraints
- Referencing ESMA guidelines on compliance function size
- Mapping compliance activities to MiFID II article citations
- Defining PDMRs under MAR and their reporting duties
- Maintaining and updating insider lists automatically
- Detecting suspicious transactions in dark pools
- Integrating transaction monitoring with MAR thresholds
- Handling delayed disclosures with documented rationale
- Responding to ESMA queries on position limits
- Mapping dual reporting requirements: MiFID II and MAR
- Using machine learning to flag potential insider patterns
- Documenting decisions not to report borderline cases
- Building audit trails for insider trading investigations
- How national regulators coordinate MAR enforcement
- Creating defensible rebuttals to false positive alerts
- Criteria for professional client status under MiFID II
- When eligible counterparty status applies
- Documenting client knowledge and experience assessments
- Handling self-certification with audit trails
- Reviewing client status after significant changes
- Integrating CRM data into categorisation decisions
- Responding to regulator follow-ups on classification
- Avoiding misclassification in cross-border onboarding
- Using transaction history to support categorisation
- Building defensible positions on borderline clients
- Referencing ESMA’s guidelines on client treatment
- Mapping client types to reportable fields in trade data
- Minimum retention periods for trade records and communications
- Acceptable formats for electronic storage
- Indexing voice recordings for regulator queries
- Using metadata to accelerate retrieval
- Handling cross-border data sovereignty issues
- Integrating email archiving with trade reporting
- Responding to ESMA’s data access requests
- Building defensible positions on data loss incidents
- Using encryption without blocking access
- Mapping retention policies to article-specific rules
- Testing retrieval processes under time pressure
- Documenting destruction procedures with audit logs
- Structuring responses to ESMA data calls
- Using MiFID II text to support interpretation choices
- Referencing past enforcement actions in replies
- Building response templates with citation placeholders
- Coordinating input from legal, compliance, and tech
- Handling follow-up questions without overcommitting
- Preparing for on-site inspection workflows
- Using internal audit findings as prep material
- Documenting rationale for changes post-review
- Building defensible positions on ambiguous rules
- Integrating external counsel input without losing ownership
- Closing loops after regulator feedback is received
How this maps to your situation
- Initial policy setup and interpretation
- Ongoing audit and peer review cycles
- Regulatory inquiry preparation
- Post-review improvement planning
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 90 minutes per module, designed to be consumed incrementally over 8, 10 weeks. Total investment: ~18 hours.
How this compares to the alternatives
Generic compliance courses teach broad principles. This course teaches how to defend your specific MiFID II decisions using actual text, enforcement data, and regulator expectations, so you’re never left searching for the right reference.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.