Application dossier: documents you need for a successful Austria MiCA license filing
A strong Austria MiCA license dossier is a coherent evidence package, not a stack of disconnected PDFs. The FMA will test whether the documents tell one consistent story about your services, ownership, controls, technology, and financial viability.
The core dossier usually includes:
- Program of operations describing services, client types, jurisdictions, channels, and operational flow;
- Business plan and financial projections with realistic assumptions and downside scenarios;
- Corporate documents, constitutional documents, registration extracts, and ownership chart;
- UBO and qualifying holding disclosures with source-of-funds evidence;
- Governance arrangements, board structure, role descriptions, conflicts framework, and delegation matrix;
- AML/CFT framework, business-wide risk assessment, onboarding rules, monitoring logic, sanctions controls, and suspicious activity process;
- Travel Rule operating model including data fields, messaging approach, exception handling, and counterparty due diligence;
- Safeguarding and reconciliation policies for client assets and client funds where relevant;
- Complaints handling policy and consumer communication framework;
- Outsourcing policy and vendor register with oversight, SLAs, audit rights, and exit planning;
- ICT and cybersecurity documentation including architecture, access governance, incident response, BCP/DR, logging and monitoring;
- DORA-relevant control documentation for ICT risk, third-party oversight, and resilience testing;
- Fit and proper packages for directors and key function holders.
The best way to manage the dossier is to assign an owner to each document and force cross-consistency checks. For example, the outsourcing map must match the ICT architecture, the business plan must match the revenue logic, and the AML risk assessment must match the actual services and target geographies. Most weak applications fail on these internal contradictions, not on missing buzzwords.
Core legal and corporate documents
Corporate documents establish who is applying, who controls the applicant, and whether the structure is transparent enough for supervision.
- Articles / constitutional documents and corporate registry extracts;
- Ownership chart from immediate shareholders to UBOs;
- UBO disclosures and identification documents;
- Qualifying holding data for 10%+ holders;
- Source-of-funds / source-of-wealth evidence;
- Board resolutions and authorization records for the filing.
Where foreign documents are involved, founders should plan for notarization, apostille, sworn translation, and timing mismatch between corporate issuance dates and filing deadlines.
Governance, AML/CFT and internal controls
The FMA expects a control framework that is proportionate, but real. That means governance documents must show who owns risk, who approves exceptions, who monitors compliance, and how issues escalate to management.
- Governance map with board, management, compliance, AML, risk and ICT responsibilities;
- AML manual tailored to the business model;
- Business-wide ML/TF risk assessment;
- CDD/EDD procedures for retail, corporate and higher-risk clients;
- Sanctions and adverse media controls;
- Travel Rule workflow and data retention logic;
- Training plan and independent review approach.
An advanced but useful addition is a control evidence map showing which system, team, or provider generates proof for each control. That makes the file much stronger because it moves the discussion from policy language to operational evidence.
ICT, cybersecurity and DORA-ready documentation
ICT documentation should explain how the platform works, how it fails, and how the firm remains in control when it fails.
- System architecture covering wallets, custody stack, exchange engine, APIs, cloud, nodes, and compliance tools;
- Access-control model with privileged access governance and maker-checker logic;
- Incident response plan with severity classification and escalation chain;
- Business continuity and disaster recovery with defined RTO/RPO assumptions;
- Third-party ICT register and criticality assessment;
- Testing schedule for vulnerability management, backup restoration, and resilience checks;
- Logging and evidence retention for audit trail integrity.
One operational nuance that materially improves readiness is to document manual fallback procedures for sanctions alerts, transfer holds, and wallet incidents. Regulators know systems fail. They want to see that governance survives failure.