We manage your security to weather the AI storm →

← Resource Hub

Crypto Compliance Manual Template: What to Document

By Owen ThurmPublished 11 min read

Crypto Compliance Manual Template: What to Document

Quick answer. A crypto compliance manual should document governance, AML, sanctions and Travel Rule procedures, custody and client-asset controls, ICT and security policies, third-party oversight, and incident and complaints handling. Control each requirement as one row: owner, procedure, evidence, test, deadline and review date.

Watch: Crypto Compliance Manual Template: What to Document 1:40
Video transcript

Supervisors read your compliance manual to see how your firm runs. Here is what to document, section by section.

A complete manual covers governance, AML with the Travel Rule, custody, ICT and security, third-party oversight, and incidents and complaints.

The EU AML Regulation applies from 10 July 2027. Until then, national AML rules govern, so track it as a dated milestone.

Document how Travel Rule data is sent and checked, what to do when it is missing, how you assess self-hosted addresses, and sanctions screening.

MiCA requires a custody policy that minimises loss from fraud, cyber threats or negligence. That makes it a security document too.

A manual describes controls. Testing shows they work. DORA requires yearly tests of systems supporting critical or important functions, outside microenterprises, with findings fixed and validated.

There is no universal incident clock. DORA's first notice is due within four hours of classification. NYDFS and VARA allow 72 hours, each from a different starting point.

Control each requirement as one row: owner, procedure, evidence, test, deadline and review date. This is Guardian's synthesis, not a regulator's form.

Read the full template in the article. Guardian's compliance assessments test the controls your manual describes and map findings to MiCA, DORA, NYDFS or VARA. Your advisers keep the legal calls.

Setting Up the Compliance Manual

A crypto compliance manual is the document set a supervisor reads to see how your firm runs. Under MiCA, much of it is filed with the CASP application. European Union, EUR-Lex

MiCA has applied since 30 December 2024, and its transitional periods ended by 1 July 2026 at the latest. DORA has applied to authorised CASPs since 17 January 2025.

Article 62 of MiCA asks applicants to describe governance, internal controls, AML risk controls, continuity, ICT security, segregation of client assets, complaints handling and custody policies.

For the security controls alone, with their articles, use our MiCA compliance checklist for CASPs. This template covers the whole manual, including AML, the Travel Rule and complaints.

Start with a scope register: each service, jurisdiction and client-asset activity, and the rules that reach it.

Build one common baseline, then add overlays for local scope, reporting clocks, certification dates and testing conditions. Similar wording across regimes does not make obligations interchangeable.

Applicability depends on your activities, size, authorisations and exemptions. Confirm it with counsel; this template is not legal advice.

Where this article discusses regulation, it covers the technical and security side only. It is not legal advice; confirm how the rules apply to you with counsel.

Governance and Accountability

Under DORA, the management body defines, approves and oversees the ICT risk framework, and is accountable for implementing it. European Union, EUR-Lex

From 10 July 2027, the EU AML Regulation requires management-approved written AML policies and regular compliance reporting to that body.

MiCA requires management body members of good repute with the right knowledge, skills and experience. It also requires records of all services, orders and transactions for five years.

  • Approval record for each policy: approving body, date and version.
  • Organisation chart with reporting lines for compliance, risk, security and internal audit.
  • Mandate, independence and resources of each control function.
  • Conflicts-of-interest policy covering identification, prevention, management and disclosure.
  • Role-based training plan, with completion records.
  • Record-keeping policy, with a retention period per record type.
  • Version log: owner, approver, change summary and next review date.

AML, Sanctions and Travel Rule

Write AML policies for the rules that apply today. The EU AML Regulation applies from 10 July 2027; until then, national AML rules govern. European Union, EUR-Lex

Track the 2027 baseline as a dated milestone, not a live obligation. Our guide to AMLA's CDD standards for CASPs covers the draft detail.

The Travel Rule requires originator and beneficiary information to accompany each crypto-asset transfer. Document how you send, receive, check and keep it.

Write the procedure for missing or incomplete data, including when to execute, reject, return or suspend a transfer.

For a transfer above EUR 1,000 involving a self-hosted address, record how you assessed whether your customer owns or controls it.

Article 23 of the Travel Rule requires CASPs to keep policies, procedures and controls that apply EU and national restrictive measures to transfers. The EBA sanctions screening guidelines for CASPs have applied since 30 December 2025. European Banking Authority

Where you have a U.S. nexus, OFAC's virtual currency guidance sets a sanctions baseline: management commitment, risk assessment, internal controls, testing and training. U.S. Department of the Treasury, OFAC

  • Business-wide risk assessment by customer, product, transaction, delivery channel and geography.
  • Add chain and counterparty CASP risk as crypto-specific factors.
  • Customer and beneficial-owner identification and verification steps.
  • PEP and enhanced due diligence triggers, with approval levels.
  • Ongoing monitoring rules, alert thresholds and tuning records.
  • Suspicious-transaction escalation, decision and filing steps.
  • Sanctions screening of customers, transfers and listed wallet addresses, with blocking, freezing and escalation; IP and geographic controls where OFAC applies.
  • Independent testing and quality assurance, with remediation tracked to closure.

Custody and Client Assets

MiCA Article 75 governs CASPs that provide custody and administration of crypto-assets for clients. European Union, EUR-Lex

The custody policy must minimise the risk of loss from fraud, cyber threats or negligence. Write it with your security team, not only legal.

A custodian is liable for losses from an incident attributable to it, up to the asset's market value at the time of loss.

  • Custody agreement terms, by client type.
  • Register of positions opened for each client.
  • Statements of position at least every three months.
  • Onchain segregation of client and firm holdings, with an address register.
  • Key approval and safeguarding system, including multisig, and how clients' means of access is protected.
  • Key rotation, recovery and destruction steps, each with an owner.
  • Procedures to return client assets as soon as possible.
  • Subcustodian selection, contracts and ongoing oversight.
  • Reconciliation frequency, owner and break handling.

ICT and Security Policies

DORA, the CASP application RTS, NYDFS Part 500 and VARA's Technology and Information Rulebook all expect written ICT controls. European Union, EUR-Lex, New York State Department of Financial Services, Dubai Virtual Assets Regulatory Authority

DORA requires yearly tests of systems supporting critical or important functions, except at microenterprises. Tests include scans, source code review where feasible, scenario tests and pentests.

Threat-led penetration testing every three years applies only if your authority identifies you. Record whether it does.

Unless exempt under 500.19(a), NYDFS covered entities add annual pentests from inside and outside system boundaries, risk-based scanning and audit trails. All file a certification or acknowledgment by 15 April.

VARA-licensed VASPs need a CISO separate from the Compliance Officer. The rulebook also bars any single point of failure in access to virtual assets.

Dependency assumptions belong here too. In Guardian's M0 Liquidity Delivery review, finding I-14 noted the Portal relied on bridge adapters alone for replay protection. Guardian

It was an informational audit finding, since resolved, not an exploit. The lesson for the manual: name each external dependency on a critical path, and the control backing it.

Outsourcing does not move responsibility to the provider. Keep an ICT contract register, flag critical or important functions and write an exit plan for each.

  • ICT asset and data inventory, with dependencies mapped.
  • Access management: least privilege, MFA and periodic access reviews.
  • Cryptographic key controls across the key lifecycle.
  • Secure development and change management.
  • Vulnerability management, testing programme and findings register.
  • Logging, detection and audit trails.
  • Backups, restore tests, business impact analysis and recovery objectives.
  • Provider due diligence, security requirements, audit rights and concentration risk.

Incident and Complaints Handling

Write one incident procedure with a deadline matrix per jurisdiction. There is no universal clock, and each starts at a different moment.

Under DORA, the intermediate report follows within 72 hours of the initial notice, and the final report within one month of the latest intermediate report. European Union, EUR-Lex

For every clock side by side, use our crypto incident reporting requirements matrix.

MiCA requires effective, transparent complaint procedures, free of charge to clients. Complaints must be recorded, investigated fairly and answered within a reasonable period.

Recurring filings sit outside this procedure; our guide to crypto regulatory reporting puts them in one calendar.

  • Severity criteria and early warning indicators.
  • Roles, decision log and internal escalation.
  • Evidence preservation steps.
  • Client and regulator notice templates.
  • Complaint intake, tracking and response times.
  • Recovery validation before services resume. Dubai Virtual Assets Regulatory Authority
  • Root cause analysis and post-incident review.
  • Corrective actions with owners and closure dates.
RegimeApplies toTriggerFirst notice
DORAAuthorised CASPs and ART issuersMajor ICT-related incident4 hours from classification; 24 hours from awareness at most
NYDFS Part 500New York covered entitiesCybersecurity incident72 hours after determining it occurred
VARAVARA-licensed VASPs in DubaiMaterial cybersecurity or continuity event72 hours from detection

The Compliance Manual Template

Control the manual as one record per requirement. This format is Guardian's synthesis of the rules above, not a regulator's form.

Mark residual risk honestly. A row marked partial, with a dated fix, is more credible than a manual claiming full coverage.

FieldWhat to recordExample
Requirement IDA unique, stable referenceAML-TR-04
Jurisdiction and applicabilityWhere it applies, and whyEU; custody service
ObligationRule in plain words, with its articleReturn client assets, MiCA Art. 75(6)
Policy or procedureDocument and section numberCustody Procedure 3.2
Owner and approverNamed role and approving bodyHead of Custody; management body
SystemWhere the control runsWallet platform, signing service
Evidence artifactWhat proves the control workedDated recovery test record
Test method and frequencyHow and how often it is checkedYearly recovery drill
Trigger and deadlineThe event that starts a clockMajor incident: 4 hours from classification
Escalation and exceptionsWho decides, who approves waiversCompliance lead, then risk committee
Retention periodHow long evidence is keptFive years for MiCA transaction records
Status and reviewsResidual risk, last and next reviewPartial; fix owner and next review set

Frequently Asked Questions

Is there an official MiCA compliance manual template?

No. MiCA Article 62 and RTS 2025/305 set what an application must describe, and Implementing Regulation (EU) 2025/306 sets the application forms. None of these texts prescribes a compliance manual layout, so check your national authority's own forms. European Union, EUR-Lex

Does OFAC sanctions guidance apply to a firm outside the U.S.?

OFAC sanctions bind U.S. persons and activity within U.S. jurisdiction. A non-U.S. firm can still face exposure if it causes a U.S. person to violate them. The guidance itself recommends a programme rather than setting rules. Map your U.S. nexus first. U.S. Department of the Treasury, OFAC

How often should a crypto compliance manual be reviewed?

DORA requires the ICT risk framework to be reviewed at least yearly and after major ICT incidents. VARA requires its Cybersecurity Policy to be reviewed at least annually. Also review after a new service, system change or rule change. European Union, EUR-Lex, Dubai Virtual Assets Regulatory Authority

Does a written manual replace security testing?

No. The manual describes controls; testing shows they work. DORA requires independent testers, internal or external, and every finding to be classified, fixed and validated. European Union, EUR-Lex

Sources

Test the Controls Your Manual Describes

Guardian's compliance assessments test the custody, ICT and incident controls in your manual, then map findings, retests and evidence to MiCA, DORA, NYDFS or VARA. Your advisers keep the legal calls.