A tailored course, built for your situation
Mastering MiFID II for Software Engineers in Financial Compliance
Turn regulatory complexity into clean, auditable implementation.
$199 one-time
24-hour access provisioning
30-day money-back guarantee
Hand-built implementation playbook
12 modules. 12 chapters per module. 144 chapters total.
12 modules, each with 12 chapters (144 chapters total), text-based, plus downloadable templates and a hand-built implementation playbook delivered alongside course access.
Engineers stuck translating vague compliance asks into systems waste cycles on rework, misalignment, and late-stage corrections.
The situation this course is for
Compliance teams issue broad directives. Engineering teams build. Then auditors find gaps, and the loop restarts. The cost isn’t just time; it’s credibility. When deliverables bounce between functions, ownership blurs and trust erodes.
Who this is for
Software engineers in financial services who are expected to implement regulatory requirements but lack direct access to compliance decision-making or canonical implementation patterns.
Who this is not for
Leaders focused on policy design, auditors verifying controls, or vendors selling compliance tooling. This is not for those outside the implementation loop.
What you walk away with
- Produce MiFID II transaction reporting outputs that pass internal review on first submission
- Reference authoritative control mappings for RTS 21 and RTS 22 without escalating to compliance
- Build pre-trade transparency modules using validated logic patterns from past audits
- Own the full cycle from MiFID II requirement to deployed control without handoff delays
- Gain recognition as the go-to implementer for new regulatory sprints
The 12 modules (with all 144 chapters)
Module 1. Introduction to MiFID II in Software Delivery
Map MiFID II's core obligations to engineering responsibilities. Identify where code directly satisfies regulatory requirements and where it supports compliance adjacent systems.
12 chapters in this module
- Scope of MiFID II for technical teams
- Key articles affecting system design
- Transaction reporting mandate overview
- Pre-trade transparency rules
- Post-trade reporting obligations
- Best execution requirements
- Algorithmic trading registration
- Systematic internaliser status
- Research payment separation
- Inducements and disclosures
- Recordkeeping expectations
- Audit trail design principles
Module 2. Designing for RTS 21 Compliance
Implement granular trade reporting logic that satisfies ESMA's technical standards. Use schema templates and validation rules derived from live submissions.
12 chapters in this module
- RTS 21 field specifications
- Instrument identification using ISIN
- Client identification with LEI
- Order creation timestamps
- Order modification events
- Order cancellation tracking
- Trade confirmation timing
- Execution venue codes
- Quantity and price formatting
- Currency and settlement logic
- Post-trade transparency flags
- Error correction protocols
Module 3. Implementing RTS 22 Pre-Trade Transparency
Build systems that publish required data before execution. Use reference implementations for deferral logic and waiver handling approved in peer audits.
12 chapters in this module
- Liquidity segmentation rules
- Deferral eligibility criteria
- Size of minimum tick increments
- Price-to-trade ratio checks
- Market maker exemption paths
- Dark book logic patterns
- Transparency clock alignment
- Trading pause handling
- Waiver request workflows
- Regulatory clock sync
- Data publication frequency
- Exception logging for auditors
Module 4. Best Execution Framework Integration
Code systems that capture and report best execution analysis. Integrate with execution venues to preserve evidence for periodic reviews.
12 chapters in this module
- Venue inclusion logic
- Historical venue performance data
- Order routing decision logging
- Client segmentation rules
- Cost-of-delay tracking
- Price improvement metrics
- Slippage calculation methods
- Non-displayed venue weighting
- Broker selection transparency
- Execution time benchmarks
- Report aggregation patterns
- Audit trail completeness
Module 5. Algorithmic Trading Controls
Implement mandatory safeguards for automated strategies. Use control templates that mirror those approved in regulator-facing reviews.
12 chapters in this module
- Pre-trade risk checks
- Order rate limiting
- Position monitoring logic
- Circuit breaker thresholds
- Kill switch implementation
- Backtesting validation
- Strategy registration fields
- Trading halt propagation
- Latency measurement
- Fail-safe defaults
- Model validation hooks
- Change control for algo updates
Module 6. Recordkeeping and Audit Trail Design
Build tamper-resistant, complete logs that satisfy retention rules. Structure data for fast retrieval during audits or investigations.
12 chapters in this module
- Data retention duration
- Immutable logging patterns
- Timestamp accuracy standards
- Sequence number integrity
- Data format preservation
- Access control for logs
- Chain of custody tracking
- Encryption at rest
- Indexing for retrieval
- Audit log completeness
- Chain of changes reporting
- System downtime logging
Module 7. Transaction Reporting Workflows
Automate end-to-end submission pipelines. Use transformation rules and validation layers that reduce manual intervention.
12 chapters in this module
- Data source integration
- Normalization logic
- Validation rule sets
- Error handling patterns
- Resubmission workflows
- Reconciliation methods
- Batch vs stream processing
- Payload structure templates
- Regulator-specific formatting
- Submission acknowledgement
- Monitoring and alerts
- Drift detection systems
Module 8. Control Mapping to Regulatory Text
Link system controls directly to MiFID II articles and RTS clauses. Use source-backed mapping to justify design choices during audits.
12 chapters in this module
- Article-by-article mapping
- Control-to-clause linking
- Evidence collection strategies
- Audit narrative templates
- Cross-reference matrices
- Change impact analysis
- Versioning control mappings
- Peer-reviewed mappings
- Regulator feedback loops
- Gap identification methods
- Control ownership assignment
- Periodic review scheduling
Module 9. Testing and Validation for Compliance
Design test suites that validate regulatory adherence. Use real-world edge cases from past enforcement actions to harden systems.
12 chapters in this module
- Test case derivation from RTS
- Boundary condition analysis
- Negative scenario testing
- Data quality checks
- End-to-end simulation
- Regulatory logic validation
- Error recovery paths
- Failover testing
- Data consistency checks
- Reconciliation testing
- Audit trail completeness
- Test documentation standards
Module 10. Change Management for Regulatory Systems
Implement controlled updates without breaking compliance. Use versioning, approval workflows, and backward compatibility patterns.
12 chapters in this module
- Change request process
- Impact assessment templates
- Approval workflow design
- Rollback procedures
- Version control strategy
- Backward compatibility
- Deprecation timelines
- Notification systems
- Audit trail for changes
- Stakeholder alignment
- UAT coordination
- Production cutover
Module 11. Cross-Functional Collaboration Patterns
Work effectively with compliance and audit teams. Use shared artefacts and terminology to reduce friction and rework.
12 chapters in this module
- Glossary alignment
- Shared documentation
- Joint review meetings
- Feedback integration
- Escalation paths
- Status reporting
- Clarification request handling
- Assumption tracking
- Regulatory update intake
- Compliance sign-off workflows
- Peer validation
- Lessons learned integration
Module 12. Course Capstone: End-to-End Implementation
Apply all modules to a complete MiFID II reporting pipeline. Deliver a working prototype with full documentation and audit readiness.
12 chapters in this module
- Requirements synthesis
- System architecture design
- Control mapping output
- Code implementation
- Testing strategy
- Validation results
- Audit trail completeness
- Change management plan
- Operational runbook
- Handoff to operations
- Monitoring setup
- Final compliance review
How this maps to your situation
- When you inherit a vague compliance ticket
- When regulators request transaction reports
- When audit flags a control gap
- When new trading logic must be certified
Before vs. after
Before
Receiving MiFID II tasks as high-level directives without clear implementation patterns or ownership.
After
Receiving MiFID II deliverables directly from compliance teams with trust in your ability to execute independently.
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 2.5 hours per module, or 30 hours total to complete all modules and exercises.
If nothing changes
Continuing without structured implementation knowledge means repeated rework, delayed approvals, and missed opportunities to lead regulatory engineering initiatives. Others will own the narrative if you don't own the artefacts.
How this compares to the alternatives
Most compliance courses target policy teams or auditors. This course is built for engineers who must turn regulation into code , with specific, tested implementation patterns not found in general training.
Frequently asked
Is this course for developers or compliance officers?
This course is specifically designed for software engineers in financial services who are tasked with implementing MiFID II requirements in code.
How is the course structured?
12 modules, each containing 12 chapters (144 chapters total).
Will I receive templates I can use at work?
Yes , every module includes downloadable templates and worked examples aligned to MiFID II requirements.
$199 one-time. Approximately 2.5 hours per module, or 30 hours total to complete all modules and exercises..
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.
30-day money-back guarantee·
144 chapters·
Hand-built playbook included·
Account access within 24 hours