The authorized model becomes a baseline
Once authorization is granted, the governance and operating assumptions presented to the authority become a reference point for later change. New products, providers, group restructurings, key people or technology arrangements should enter a controlled legal and compliance review before implementation.
Build change control into product governance
A practical framework uses a trigger list, defined legal sign-off, documented approvals and an evidence trail. The goal is to identify whether a commercial change affects the regulatory perimeter, the authorization file, outsourcing arrangements or other supervisory expectations before go-live.
MiCA and DORA should not create duplicate control systems
For CASPs in DORA scope, ICT governance, incident management, testing and third-party risk should be mapped once and evidenced coherently. Parallel registers and competing ownership models create inconsistencies. A common control architecture can serve multiple regulatory obligations while preserving the distinct legal requirements.
Supervisory readiness is not an annual policy refresh
Recurring work should review governance, open findings, material changes, provider dependencies, evidence, incidents and regulatory developments. The objective is to maintain a defensible operational record and the ability to respond quickly to supervisory requests, not to generate a fresh binder each year.
Remediation needs closure criteria
Where a regulator or internal review identifies a gap, the action should be linked to the underlying requirement, risk, owner, deadline and required evidence. Closure follows reassessment; it is not achieved merely because a document was rewritten.
Turning the analysis into a controlled mandate
In a live mandate concerning post-authorization compliance, the work cannot stop at high-level advisory language. The legal conclusion should be translated into a controlled workplan covering change control, material changes, outsourcing and the MiCA/DORA interface. Each material issue receives a factual owner and legal owner, required documents, decision point, dependencies and a completion criterion. This allows the team to distinguish true blockers from parallel workstreams and from tasks requiring a specialist or local counsel. It also provides disciplined change-control when the client alters a business assumption during the project, rather than allowing scope and responsibility to expand informally.
Failure modes to identify before they become regulatory statements
The most expensive problems are not always difficult points of law. They are often commercial go-live before legal sign-off, stale policies and parallel registers that create conflicting data. Those inconsistencies should be found before they become a filing, supervisory statement, board representation or contractual commitment. The delivery model uses an issue log recording severity, legal implication, business impact, owner and required decision. Where a gap cannot responsibly be closed in time, it should be disclosed internally and managed through an informed decision rather than hidden by drafting that creates a larger problem later.
Evidence, quality control and later review
A strong project file allows an independent reviewer to trace the path from requirement to decision and implementation. Depending on the matter, the record should include change logs, legal sign-offs, provider reviews, incident records, management reporting and remediation evidence. Evidence should not sit in an unstructured folder: it should be linked to a requirement or action and carry an owner, date, version and review status. Before filing, closure or management assurance, a second consistency review should test whether claims, contracts, governance records and operational proof remain aligned.
Cross-border and professional-practice controls
In cross-border work, the language of a deliverable does not determine the governing law. group changes may affect more than one jurisdiction and require coordinated local advice. Each country therefore passes a separate jurisdiction, practice-rights and professional-conduct gate. OIKONOMAKIS LAW may coordinate the overall matter, while local-law opinions or representation are allocated to appropriately qualified professionals where required. The same distinction applies to marketing: a service that can be delivered into a market is not automatically eligible for every form of paid targeting or personalized solicitation in that jurisdiction.
Deeper analysis and implementation
Regulatory change governance
Post-authorization compliance requires a defined regulatory change gate. A new service, market, custody provider, material cloud dependency, intra-group transfer of a function, senior-management change or significant technology redesign can affect the basis on which authorization was granted. Business owners need a trigger list that brings Legal and Compliance into the decision before implementation rather than after the change has created a deviation.
The change record should connect business rationale, legal analysis, risk assessment, approvals, required notifications, revised procedures and supporting evidence. This creates a defensible decision trail rather than a collection of retrospective explanations.
MiCA and DORA converge operationally
For CASPs within DORA, ICT risk management, incident governance, resilience testing and third-party oversight should not be built as an entirely separate compliance system. Common ownership and evidence can be used where the obligations genuinely overlap. ESMA’s 2026 Common Supervisory Action on CASP digital operational resilience for custody reinforces the importance of operational controls, incident response and third-party dependencies in the supervisory agenda.
An annual review therefore needs more than policy refresh. It should sample control evidence, reconcile material changes, review outsourcing and major incidents, test governance reporting and assess whether the operating model still corresponds to the authorized description. Open deviations should enter a tracked remediation process with evidence-based closure.
Primary / official sources for publication verification
Regulation (EU) 2023/1114 (MiCA) — https://eur-lex.europa.eu/eli/reg/2023/1114/oj/eng — EU MiCA framework.
Regulation (EU) 2022/2554 (DORA) — https://eur-lex.europa.eu/eli/reg/2022/2554/oj/eng — Core DORA framework.
ESMA — MiCA — https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica — Current supervisory material.
Prepared by Christos Oikonomakis, Chairman, OIKONOMAKIS LAW
