Framework overlap

Does GDPR cover AML/CTF Act 2006 (Australia)?

You hold GDPR and have been told to do AML/CTF Act 2006 (Australia). Here is how much overlaps, control by control.

8% of AML/CTF Act 2006 (Australia) you already have

GDPR already covers about 8% of AML/CTF Act 2006 (Australia), leaving 36 of 39 controls as genuinely new work.

Already covered 1 Likely covered 2 New work 36

What is genuinely new work

Nothing in GDPR reaches these. This is the list to scope.

AMLCTF-107
General Record-Keeping
AMLCTF-108
Customer Identification Records
AMLCTF-111
Transaction Records
AMLCTF-114
Electronic Funds Transfer Records
AMLCTF-34
Customer Identification Obligation
AMLCTF-41
Suspicious Matter Reports (SMRs)
AMLCTF-43
Threshold Transaction Reports (TTRs)
AMLCTF-45
International Funds Transfer Instructions (IFTIs) - Sending
AMLCTF-46
International Funds Transfer Instructions (IFTIs) - Receiving
AMLCTF-47
Annual AML/CTF Compliance Reports
AMLCTF-81
Program Obligation
AMLCTF-84
Standard AML/CTF Program
AMLCTF-85
Joint AML/CTF Program
AMLCTF-AGENT-OVERSIGHT
Agent Oversight (Remittance/DCE)
AMLCTF-ENROL
AUSTRAC Enrolment
AMLCTF-NEW-PRODUCTS
New Product and Channel Risk
AMLCTF-PART-A
AML/CTF Program Part A
AMLCTF-PART-B
AML/CTF Program Part B (Customer Due Diligence)
AMLCTF-PartA-EDD
Employee Due Diligence
AMLCTF-PartA-OCDD
Ongoing Customer Due Diligence
AMLCTF-PartA-Officer
AML/CTF Compliance Officer
AMLCTF-PartA-Review
Independent Review
AMLCTF-PartA-Training
AML/CTF Risk Awareness Training
AMLCTF-PartA-TxnMon
Transaction Monitoring
AMLCTF-PartB-BO
Beneficial Ownership
AMLCTF-PartB-ECDD
Enhanced Customer Due Diligence
AMLCTF-PartB-PEP
Politically Exposed Persons
AMLCTF-PartB-RBA
Risk-Based Approach to CDD
AMLCTF-PartB-SCDD
Simplified Customer Due Diligence
AMLCTF-Penalty
Non-Compliance Penalties
AMLCTF-REGISTER
AUSTRAC Registration (Remittance/DCE)
AMLCTF-RELIANCE
Reliance on Third Parties
AMLCTF-Retention
7-Year Retention Period
AMLCTF-SANCTIONS
Sanctions Screening
AMLCTF-Structuring
Structuring Offence
AMLCTF-TIPPING
Tipping Off Prohibition
Show the 3 you already have
AMLCTF-PartA-RiskAssess
ML/TF Risk Assessment
AMLCTF-35
Identity Verification Standard
AMLCTF-82
Part A Compliance

How this is calculated

Already covered means a mapping runs from a control in GDPR to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition