Australia AML customer due diligence and third-party reliance
Use the FATF findings on customer due diligence and third-party reliance to prepare a current Australian reliance decision, written agreement and assessment schedule.
Complete initial due diligence before providing a designated service unless an applicable delayed or other provision applies. For a section 37A arrangement, plan risk-based assessments at intervals of no more than two years and write each assessment record within 10 business days of completion.
Reviewed
Inside this guide
4 steps · 4 templates
Who it applies to
Australian reporting entities considering reliance on eligible third parties that have carried out customer identification or other permitted procedures. Confirm whether an ongoing arrangement, case-by-case reliance or another legal route applies.
What you’ll produce
A signed reliance decision, an approved arrangement and retrieval test where applicable, completed customer decisions and a dated reassessment record.
The fourth enhanced follow-up assessed technical compliance at publication. Use current law, Rules and AUSTRAC guidance to determine the conditions attached to reliance and the remaining responsibilities of your business.
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 2024 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 Choose the basis for relying on another party · AML officer + Australian counsel + provider relationship owner [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
What did the other party collect or verify, and which decisions will your team still make?
Can your team retrieve required information and evidence through the agreed channel when a real case needs it?
Worked scenario
A fictional lender receives business customer referrals from an Australian reporting entity. Compliance checks the proposed reliance scope and evidence access. A test reveals that one type of ownership evidence is unavailable, so the lender assigns its own verification for that part of the workflow.
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
01
Choose the basis for relying on another party
Who AML officer + Australian counsel + provider relationship ownerWhen Before relying on externally verified information
Classify the proposal as ongoing reliance, case-by-case reliance or an outsourced process. Verify legal basis, eligibility and regulatory status. Record covered procedures, customer types and which checks the reporting entity still performs.
What to produce
Australia CDD reliance scope decisionDecision memo
Gather first
Third-party proposal
Entity and customer scope
Current Act and Rules
Provider regulatory evidence
Risk assessment
How to prepare it
Describe who performed the CDD, why your entity wants to use it and which services, customer types and checks it proposes to cover.
Check which reliance route applies and whether the provider is eligible. Record the evidence of authorisation or regulation and the conditions still to be met.
Assign responsibility for remaining checks and decisions. Record any unresolved eligibility or evidence questions and who must approve the approach.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional provider review
The lender confirms the referral partner is an Australian reporting entity and records the evidence, date and scope of the proposed reliance.
Fictional scope decision
Compliance permits reliance on identified and verified data for an approved subset of business customers. The lender retains risk classification and any required additional checks.
Check before handing it over
The memo identifies the legal route, eligible entity, evidence, covered work and accountable decision owner.
Send the signed scope to legal, onboarding and third-party assurance.
Who Legal + senior manager + operations leadWhen Before signing or using an ongoing arrangement
Agree the CDD standards and information to be shared or retrieved. Test access with synthetic cases under the relevant Rules. Obtain the required senior manager approval and retain the signed arrangement and test evidence.
What to produce
Australia CDD arrangement and retrieval testSpreadsheet
Gather first
Draft agreement
Approved scope decision
Applicable rule requirements
Secure delivery process
Synthetic cases
How to prepare it
Match each agreement clause to the applicable legal requirement, available information or evidence, delivery timing and responsible party.
Run an evidence retrieval exercise with synthetic records. Confirm authorised access and expected retrieval time and record gaps and retests.
Obtain the required senior manager approval and store the signed version, test evidence and approved operational procedures together.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional test
The team asks for the verification evidence for case AU-CDD-013. The partner returns the agreed data and a supporting record through the secure channel.
Fictional failure
The response initially omits evidence for one ownership field. The lender excludes that procedure from reliance until both parties fix and retest it.
Check before handing it over
The signed arrangement covers the approved scope and the actual exchange of required evidence works for the tested cases.
Send the scope, approval and operating instructions to onboarding and the reassessment owner.
Who Onboarding analyst + authorised reviewerWhen Before providing the designated service unless an applicable provision allows delay
Check the permitted scope, risk and available information for the customer. Record what was received and verified, outstanding steps, the applicable timing and the reviewer’s decision. Perform any additional due diligence your entity owes.
What to produce
Australia relied-on CDD decision recordCase worksheet
Gather first
Customer application
Partner-provided data and evidence
Applicable arrangement or case-by-case basis
Individual risk assessment
Approval procedure
How to prepare it
Check the customer and service against the allowed scope. Record what was collected and verified by the other party, the verification date and any differences.
Complete the necessary checks your entity retains. Record the customer risk decision, outstanding information and the timing that applies before the service begins.
Capture the decision, evidence references and reviewer. Use approved restricted storage for identity documents and assign later updates as needed.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional case row
The partner verified the identity of a representative. The lender separately obtains and records current evidence of the representative’s authority.
Fictional decision
The reviewer signs the reconciled file after completing the outstanding controls. The case notes the basis, date and approved scope of reliance.
Check before handing it over
A second reviewer can see how each required check was covered and verify the timing of the decision.
Return the case outcome to onboarding and retain the evidence in the controlled system.
Who AML assurance lead + compliance officerWhen At the risk-based interval, or after a material change affecting the arrangement
Assess continued compliance with the Rules and record results, evidence and actions. Keep the written record within the statutory timeframe. If the arrangement no longer supports reliance, follow the applicable requirement to conduct your own initial due diligence.
What to produce
Australia CDD reliance reassessment logDecision log
Gather first
Signed arrangement
Previous assessment
Records of actual requests and responses
Change notices
Current AML/CTF Rules
How to prepare it
Record the risk-based reassessment due date and applicable event triggers. Recheck eligibility and whether the arrangement continues to meet the relevant requirements.
Test delivery and completeness using a documented sample. Record method, evidence, results and corrective actions. Assign initial CDD to your entity where the arrangement fails the applicable test.
Record the completion date and when the written record was prepared. Give the reviewer’s conclusions to accountable owners and schedule follow-up.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional trigger
The partner changes its verification platform. Assurance opens a review covering evidence availability and the procedures affected by the change.
Fictional close
The assurance lead records the test date and the signed written assessment within the applicable timeframe and assigns follow-up for the affected customer files.
Check before handing it over
The result is dated, supported by evidence and traceable to current rules and follow-up owners.
Share the decision with the AML officer, affected teams and the owner of the agreement.