COPRSETR WORKSHEET
Australia AML change approval and review log
Australia FATF 2018 follow-up · Step 4 · Capture the written approval and review triggers- Who prepares it
- Senior manager + AML officer + governing body contact
- When to prepare it
- Before service where required and as updates take effect
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Fictional approval
- The senior manager approves the tested onboarding flow for the existing customer segment. The approval record lists the assessed version and test references.
- Fictional implementation row
- Compliance records when the program update was documented, the date of the governing body notice and the first operating review owner.
Gather first
- Versions of risk assessment and policies
- Approved test file
- Relevant Act provisions and AUSTRAC guidance
- Release and governance calendar
How to prepare it
- Record whether the update relates to a new or significantly changed risk or a material policy change. Document what is being approved and which statutory timing and internal deadlines apply.
- Capture the senior manager’s written decision, role, date and evidence. Record when the required risk update was provided to the governing body and when the program update was documented.
- Record the permitted scope and assign post-release checks and review triggers. Track unresolved items to closure and keep previous versions with their approval evidence.
Review
The release decision, written approvals, scope and dates align with the actual assessment and deployment.
Handoff
Share authorised decisions with product, operations and compliance and retain them in the program evidence register.
Use the issuer’s current instructions and any required forms when you submit.
AUSTRAC documentation and approval guidance (opens in a new tab)