Brazil Open Finance (Resolução Conjunta No. 1/2020)vs6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673)
See exactly how Brazil Open Finance (Resolução Conjunta No. 1/2020) controls map to 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673). Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
Brazil Open Finance (Resolução Conjunta No. 1/2020) maps to 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) with 54% coverage across 13 directly mapped controls. Analysis of 24 Brazil Open Finance (Resolução Conjunta No. 1/2020) controls identifies 11 compliance gaps — primarily concentrated in Governance and Oversight.
Source: TheArtOfService Knowledge Graph | 24 controls analysed | 693 frameworks | 819K+ cross-framework mappings
Control Mappings
Showing 20 of 74 mapped controls across 5 domains. Sign up to explore all 819K+ mappings across 693 frameworks.
Consent and Data Sharing(20 mappings)
+54 more mappings
Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 693 frameworks.
Create Free Account →Free forever — no credit card required
Related Comparisons
Other Brazil Open Finance (Resolução Conjunta No. 1/2020) comparisons
Other 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) 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 Brazil Open Finance (Resolução Conjunta No. 1/2020) and 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673)?
Brazil Open Finance (Resolução Conjunta No. 1/2020) has 24 controls across its framework, while 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) covers 41 controls. Direct mapping analysis identifies 13 overlapping controls (54% coverage). The frameworks diverge most significantly in Governance and Oversight, where 3 Brazil Open Finance (Resolução Conjunta No. 1/2020) controls have no direct 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) equivalent.
How many controls map between Brazil Open Finance (Resolução Conjunta No. 1/2020) and 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673)?
Of 24 total Brazil Open Finance (Resolução Conjunta No. 1/2020) controls, 13 map directly to 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) controls — representing 54% coverage. The remaining 11 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping Brazil Open Finance (Resolução Conjunta No. 1/2020) to 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673)?
11 Brazil Open Finance (Resolução Conjunta No. 1/2020) controls have no direct equivalent in 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673). The highest concentration of gaps is in Governance and Oversight with 3 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 Brazil Open Finance (Resolução Conjunta No. 1/2020) and 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673)?
The domain with the highest gap count is Governance and Oversight (3 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.