TEFCA — Trusted Exchange Framework and Common AgreementvsFATF Recommendation 16 — Virtual Asset Travel Rule
See exactly how TEFCA — Trusted Exchange Framework and Common Agreement controls map to FATF Recommendation 16 — Virtual Asset Travel Rule. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
TEFCA — Trusted Exchange Framework and Common Agreement maps to FATF Recommendation 16 — Virtual Asset Travel Rule with 35% coverage across 8 directly mapped controls. Analysis of 23 TEFCA — Trusted Exchange Framework and Common Agreement controls identifies 15 compliance gaps — primarily concentrated in QHIN Designation and Obligations.
Source: TheArtOfService Knowledge Graph | 23 controls analysed | 693 frameworks | 819K+ cross-framework mappings
Control Mappings
Showing 14 of 14 mapped controls across 4 domains. Sign up to explore all 819K+ mappings across 693 frameworks.
Privacy and Security Requirements(6 mappings)
Exchange Purposes and Use(3 mappings)
Technical Framework (QTF)(4 mappings)
Trusted Exchange Framework Principles(1 mappings)
Related Comparisons
Other TEFCA — Trusted Exchange Framework and Common Agreement comparisons
Other FATF Recommendation 16 — Virtual Asset Travel Rule comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.
Free
- ✓ 693 framework browser
- ✓ Cross-framework mappings (819K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between TEFCA — Trusted Exchange Framework and Common Agreement and FATF Recommendation 16 — Virtual Asset Travel Rule?
TEFCA — Trusted Exchange Framework and Common Agreement has 23 controls across its framework, while FATF Recommendation 16 — Virtual Asset Travel Rule covers 22 controls. Direct mapping analysis identifies 8 overlapping controls (35% coverage). The frameworks diverge most significantly in QHIN Designation and Obligations, where 4 TEFCA — Trusted Exchange Framework and Common Agreement controls have no direct FATF Recommendation 16 — Virtual Asset Travel Rule equivalent.
How many controls map between TEFCA — Trusted Exchange Framework and Common Agreement and FATF Recommendation 16 — Virtual Asset Travel Rule?
Of 23 total TEFCA — Trusted Exchange Framework and Common Agreement controls, 8 map directly to FATF Recommendation 16 — Virtual Asset Travel Rule controls — representing 35% coverage. The remaining 15 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping TEFCA — Trusted Exchange Framework and Common Agreement to FATF Recommendation 16 — Virtual Asset Travel Rule?
15 TEFCA — Trusted Exchange Framework and Common Agreement controls have no direct equivalent in FATF Recommendation 16 — Virtual Asset Travel Rule. The highest concentration of gaps is in QHIN Designation and Obligations with 4 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.
Which control domains have the most gaps between TEFCA — Trusted Exchange Framework and Common Agreement and FATF Recommendation 16 — Virtual Asset Travel Rule?
The domain with the highest gap count is QHIN Designation and Obligations (4 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.