A superannuation fund's AML risk does not spread evenly across the relationship. It concentrates in a handful of events, separated by years of nothing. A member joins at twenty-five and claims at sixty-seven, and in between the fund may see no member-initiated activity at all beyond contributions arriving on an employer's schedule.
That shape breaks the two approaches most compliance programmes default to. Transaction monitoring has almost no signal to work with. An annual review cycle checks the account on a date chosen by the calendar rather than by anything the member did, and will routinely miss a rollover and a benefit payment that both happened in the eleven months since the last review.
What each check has to establish
The rail above shows when the checks fire. What each one has to prove is different, and that is what decides whether a result is usable later.
| Event | What the check must establish | Why it cannot wait |
|---|---|---|
| Join | Identity verified, member clear against sanctions, PEP and adverse media | The only decline that costs nothing |
| Roll in or out | Member still clear, receiving fund legitimate | How a dormant account becomes active, and a known early-release fraud route |
| Contribution outside profile | Whether the pattern has an explanation | One of very few behavioural signals a fund receives |
| Claim a benefit | Member still clear, and the claimant is the member | Payment is irreversible once made |
| Beneficiary claim | Beneficiary verified and screened as a new party | The claimant has no file with the fund at all |
| Detail change | Whether a withdrawal request follows shortly after | The sequence is the signal, not either event alone |
Why the beneficiary step is the one most often missed
A death benefit claimant is a person the fund has no file on. They were never onboarded, never identity-verified, and never screened, yet the fund is about to pay them a lump sum. If the workflow treats the beneficiary as a field on the member's record rather than as a party in their own right, no check ever runs against them.
Nomination and claim are separate moments and both need handling. A nomination made in 2015 tells you who the member intended to benefit, not who is standing in front of you in 2038.
Where the audit burden actually lands
The question a reviewer asks is not whether the fund screens members. It is which check ran immediately before a specific payment, and what the result was. Answering that years later means the screening record has to be tied to the event that triggered it, not filed by date.
That is the practical argument for event-driven screening over a review calendar. A calendar-based programme can be fully compliant on paper and still be unable to show that anything was checked before the payment a regulator is asking about.
What runs continuously
Between events, the member is not generating signal, but the lists are still moving. A member can become a politically exposed person, appear on a sanctions list, or attract adverse media without doing anything through the fund at all. Continuous re-screening against list changes is what covers the decades where the event-driven checks have nothing to fire on.
For whether these obligations apply to your fund and how they are supervised, see the superannuation and pensions industry page. For the underlying screening components, see PEP and sanctions screening, identity verification and transaction monitoring.