MOD-CMP · Compliance reporting

The reports your regulator expects, before they ask.

Monitor transactions for suspicious patterns, exchange Travel Rule data with other providers, and produce the reports your licence requires, from the same data the platform runs on.

Talk to us about this module See the connectors

8connectors
5platforms run it
+1your own, too

01 · The job
Monitoring, reporting, evidence.
Every transaction is checked against monitoring rules, alerts become cases with the evidence attached, and suspicious activity reports are prepared in your regulator's format. Periodic reports are produced on schedule and kept for audit.
- Transaction monitoring rules and alerts
- Suspicious activity reports
- Travel Rule messaging for crypto transfers
- Regulatory and tax reports (MiCA, DAC8, CRS)
- Record keeping and retention
- Exports for auditors
02 · The connectors
Monitoring engines and Travel Rule networks.
Specialist monitoring engines add their typologies to your rules, and Travel Rule providers carry sender and recipient data between crypto asset service providers.
Transaction monitoring
- ComplyAdvantage
- Chainalysis KYT
- Elliptic
- Hawk AI
Travel Rule
- Notabene
- Sygna
- 21 Analytics
- TRP
Report formats
- MiCA
- DAC8
- CRS / FATCA
03 · Your own
Your compliance programme.
Your MLRO's rules, thresholds and report templates are set in the platform, and any report can be scheduled or produced on demand.
In-house, or a provider you already use
- Your monitoring rules
- Your report templates
- Your retention periods

In production

Running in these platforms.

Questions

Asked about this module.

Does the platform cover the Travel Rule?

Yes. Crypto transfers above the thresholds carry the required sender and recipient data through a Travel Rule provider, and incoming data is checked before funds are credited.

Can our compliance team change the monitoring rules?

Yes, from the backoffice, and every change is logged and versioned.

Same family

The whole library