Australia AML/CTF risk assessment for new technology and services
Use the 2018 follow-up to understand how Australia added new technology risk requirements. Apply current Australian law to scope a product change, test controls and obtain written approval.
An up-to-date risk assessment is required before providing designated services under section 26E, subject to applicable provisions. AUSTRAC specifies written approval for certain updates and documentation within 14 days. Check transition relief per obligation.
Reviewed
Inside this guide
4 steps · 4 templates
Who it applies to
Australian reporting entities changing a designated service, customer group, delivery channel, jurisdiction or material AML/CTF control. Determine the relevant entity, activity and 2026 transition arrangements.
What you’ll produce
A signed change assessment, tested controls, an updated AML/CTF program and a decision record showing when the service may proceed.
FATF’s 2018 compliant rating for Recommendation 15 reflects the version assessed at that time. The 2024 follow-up applied the revised standard and re-rated it partially compliant.
Which risks will we reduce and how will we measure it?
Set a target for each priority service or outcome. Use a current baseline to decide the investment needed, what can be phased in, and who accepts remaining risk.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
Select one service and test a high-impact control with its owner. Record what actually happened, what failed and the proposed target.
Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor progress against the target, failed control tests and gaps that leave a critical service exposed.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
Australia FATF 2018 follow-up kickoff brief
Business reason and required outcome [Contract, obligation or approval]
Scope and exclusions [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones [Date, source and owner]
Executive sponsor and authorized signer [Names]
Project lead and backup [Names]
First workstream Define the proposed change and designated service · Product owner + Australian counsel + AML officer [Name and due date]
People, effort and external costs [Estimate, owner and contingency]
Evidence folder and reviewer access [Location, access owner and review date]
Decisions and blockers [Item, options, owner and decision date]
First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Select one service and test a high-impact control with its owner. Record what actually happened, what failed and the proposed target.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START
How this works in practice
Two questions to check scope
Which designated services, customers, jurisdictions or controls are affected by the proposed change?
Can the senior manager trace each material risk to the actual controls and the tested release version?
Worked scenario
A fictional remittance provider moves business onboarding to a mobile flow. Its AML officer maps which customer evidence changes, the test team verifies that incomplete cases reach the reviewer, and a senior manager approves the updated assessment in writing before the service uses the new flow.
Use the 2026 service scope and transition matrix for a whole-of-business review.
FROM THE SOURCE
Cases and numbers
FATF · third enhanced follow-up
7 of 40Recommendations re-rated in the 2018 follow-up
Seven of 40 technical ratings changed in 2018
The report linked Recommendation 15’s upgrade to a January 2018 change requiring reporting entities to address risks from new services, methods and technologies.
What to check When a service changes, document how controls address the changed risk and retain the actual test and approval evidence.
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
01
Define the proposed change and designated service
Who Product owner + Australian counsel + AML officerWhen At intake and before committing to launch
Identify the entity, activity, service and proposed customer journey. Determine whether the change affects a designated service or introduces new or significantly changed risk. Record applicable law and any transition or registration tasks.
What to produce
Australia AML technology change scope memoDecision memo
Gather first
Product proposal
Current service and policy inventory
Proposed workflow
Applicable Act, Rules and transition guidance
How to prepare it
List the contracting entity, proposed activities and planned start. Compare the current and proposed customer journey, jurisdictions, third parties and system responsibilities.
Have counsel confirm designated service scope, applicable authorisations and effective dates. Record which assumptions need evidence before approval.
Assign the AML officer and product owner to update the risk assessment, controls and release evidence. Record who decides whether the change can proceed.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional intake
The release changes business onboarding from an agent-assisted process to mobile. Product records which evidence is collected and where it goes for review.
Fictional scope decision
Counsel records the designated service and applicable Part 1A provisions. The product owner schedules the risk assessment before enabling mobile onboarding.
Check before handing it over
The signed memo makes the proposed change, applicable obligations, review owners and open questions clear.
Give the memo to the risk analyst, test lead and release approver.
Who AML risk lead + operations + technology ownerWhen Before providing the affected designated service where applicable
Assess inherent risk using current service, customer, channel and jurisdiction information. Map material risks to policies, controls, evidence and owners. Document how the change affects existing controls and any remaining exposure.
What to produce
Australia AML technology risk and control matrixSpreadsheet
Gather first
Approved intake
Latest risk assessment and policies
Journey and vendor evidence
Applicable AUSTRAC risk information
How to prepare it
Log each assessed scenario, affected service and source. Record inherent risk, the evidence used to assess it and any expected change in exposure.
Map each scenario to the preventive or detective measure, procedure, owner and test. Explain what remains after the control and identify any action or escalation.
Reconcile the matrix to the updated risk assessment and policy provisions. Present open issues and evidence to the appropriate decision owner.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional control row
A remote submission has inconsistent records. Operations checks that the existing referral and review policy still applies to the changed customer journey.
Fictional action row
A reviewer cannot see one required support record. Product assigns a fix and adds the expected evidence to the retest plan.
Check before handing it over
A reviewer can trace every material risk to a control, owner and test or an assigned decision.
Send the reviewed matrix to quality assurance and the AML officer for test selection and policy sign-off.
Who Quality assurance + operational control owners + AML reviewerWhen After implementation and before the release decision
Test synthetic standard, incomplete and referral cases in the proposed release. Review access, evidence retention and who can approve cases. Retest failures and document which cases and environments the evidence covers.
What to produce
Australia AML technology release test fileTest worksheet
Gather first
Risk and control matrix
Release manifest
Synthetic onboarding cases
Reviewer permissions
Expected records and retention rules
How to prepare it
Choose cases for each critical control, including normal processing, referrals and incomplete files. Document the expected result and required evidence.
Run each case in the candidate release. Record its input, output, release version, reviewer, evidence reference and time. Assign defects to named owners.
Retest after fixes and preserve the original and later results. Have the AML reviewer sign the conclusion with test coverage and unresolved limitations.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional referral test
Case AU-TECH-12 supplies contradictory ownership records. The system routes it to the authorised reviewer and retains evidence of the assigned decision.
Fictional retest
The first run dropped an attachment reference. The team fixes it and retains both test results and the new release identifier.
Check before handing it over
A reviewer can reproduce the planned cases and verify how each failure or limitation was resolved or escalated.
Provide the signed evidence and open items to the senior manager and release owner.
Who Senior manager + AML officer + governing body contactWhen Before service where required and as updates take effect
Record policy and risk assessment versions, the applicable approval requirement and the senior manager’s dated decision. Provide written risk updates to the governing body as required. Document updates on the applicable schedule and set review triggers.
What to produce
Australia AML change approval and review logDecision log
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.
Worked example
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.
Check before handing it over
The release decision, written approvals, scope and dates align with the actual assessment and deployment.
Share authorised decisions with product, operations and compliance and retain them in the program evidence register.
Use the FATF findings on customer due diligence and third-party reliance to prepare a current Australian reliance decision, written agreement and assessment schedule.