/810-regulations-eu-mifid-ii

name: 810-regulations-eu-mifid-ii
description: Use when reviewing Java enterprise evidence for MiFID II investment services, investment activities, client classification, suitability, appropriateness, order-handling evidence, best-execution evidence, algorithmic-trading governance evidence, market-access governance evidence, transaction evidence, record keeping, monitoring, or compliance-owner handoff. This should trigger for requests such as Review a Java investment-service platform for MiFID II evidence; Assess suitability, appropriateness, order-handling evidence, or best-execution evidence; Document audit, monitoring, or clock-synchronisation gaps for algorithmic-trading governance; Assess investment-service engineering evidence before production release. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.18.0

MiFID II Regulation for Java Enterprise Investment Service Controls

Use this Skill to review Java enterprise evidence for investment-service platforms, advisory workflows, portfolio systems, client onboarding services, order-lifecycle record systems, execution-evidence services, market-connectivity governance, algorithmic-trading governance evidence, product-governance tooling, record-keeping systems, CI/CD workflows, and operational tooling that may support Directive 2014/65/EU (MiFID II) investment-service obligations.

Apply this Skill to determine what engineering controls, compliance evidence, and escalation paths are needed before a system is released, connected to production trading or client data, used for investment advice or portfolio management, used in order-handling workflows, or used around algorithmic-trading or market-access governance workflows. This Skill reviews evidence and recommends controls only; live trading operations remain outside its scope and require authorized business systems and qualified owners.

This Skill is not legal advice. It helps Java engineers, architects, tech leads, platform teams, product teams, risk teams, operations teams, and reviewers identify when MiFID II concerns may apply and how to translate investment-service expectations into enterprise architecture controls such as investment-service scope inventories, client classification evidence, suitability and appropriateness workflows, order-handling records, best-execution evidence, algorithmic trading controls, clock synchronisation, transaction and audit records, monitoring, change control, incident escalation, documentation, and compliance evidence handoff.

The purpose of this Skill is to increase awareness of potential gaps in the system and create engineering evidence for qualified review. The response produced by this Skill does not represent legal advice, a legal opinion, an investment-firm classification, an investment-service determination, a jurisdictional determination, or a final regulatory decision.

The main question is:

> When does a Java enterprise system require MiFID II-aware investment-service controls, and what engineering evidence should reviewers expect?

External reference: [Directive 2014/65/EU (MiFID II)](https://eur-lex.europa.eu/eli/dir/2014/65/oj/eng).

MiFID II chapters summary reference: [MiFID II chapters summary](references/810-regulations-eu-mifid-ii-chapters-summary.md).

Java engineering examples reference: [MiFID II engineering examples](references/810-regulations-eu-mifid-ii-engineering-examples.md).

Questionnaire asset: [MiFID II engineering review questionnaire](assets/questions/810-mifid-ii-engineering-review-questionnaire.md).

Report template asset: [MiFID II engineering review report template](assets/reports/810-mifid-ii-engineering-review-report-template.md).

Scope

This Skill applies to:

• Java systems that may support investment firms, trading venues, data reporting service workflows, portfolio management, investment advice, order-lifecycle evidence, execution evidence, dealing-on-own-account evidence, underwriting evidence, placement evidence, market-making evidence, or related ancillary-service evidence
• Spring Boot, Quarkus, Micronaut, and framework-agnostic Java services with investment-service, trading-governance, client classification, suitability, appropriateness, order-handling evidence, best-execution evidence, algorithmic-trading governance, market-access governance, audit evidence, or record-keeping concerns
• APIs, message consumers, batch jobs, trading-connectivity evidence adapters, order-lifecycle evidence services, suitability engines, client onboarding services, product catalogs, transaction stores, report exports, compliance dashboards, release workflows, and monitoring systems
• Systems requiring evidence for professional, retail, or eligible-counterparty classification; product target-market decisions; investment advice; appropriateness checks; suitability reports; order-routing decision records; execution-quality records; algorithmic-trading governance controls; timestamp precision; audit trails; complaints; and compliance-owner handoff
• Changes involving database migrations, Kafka or messaging contracts, feature flags, trading-rule evidence, algorithm deployment evidence, market data integration evidence, order state transitions, retention policies, observability schemas, and production release gates

MiFID II Engineering Review

Treat regulated-service classification, investment-firm status, jurisdiction, client-impact decisions, advice or recommendation classification, best-execution interpretation, algorithmic trading obligations, transaction reporting duties, and regulatory interpretation as governance decisions for legal, compliance, risk, product, operations, trading, market-structure, data-protection, security, and accountable business owners.

Engineering teams should still create evidence that makes those decisions reviewable:

• Which investment service, client journey, financial instrument, order-evidence flow, trading-venue eviden