CORE MODULE

Pre-Configured Policies

What you'll learn in this guide

The Verify module comes with a set of ready-made verification policies you can put to work straight away. We'll walk through what each one checks, how they differ, and which type fits the kind of verification you're running.

Overview

A verification policy is the rule set CX Platform applies when it checks someone's identity. It decides things like whether an address needs verifying, whether to run politically exposed person (PEP) and watchlist screening, and how many identity documents the person has to provide.

Rather than building every rule set from scratch, CX Platform ships with several pre-configured policies covering the most common verification scenarios. You can apply one as it is, or reach for the Advanced policy when you need to set your own rules.

The policies fall into three groups: Standard for everyday onboarding, Advanced for fully custom rules, and Specialised for specific scenarios like self-serve joining or withdrawals. Each one is covered below.

‍

How the policies differ
‍
Every policy is built from the same handful of settings — address checks, PEP and watchlist screening, and the number of identity documents needed. What sets each policy apart is which of these checks it switches on, as shown in the comparison table further down.

‍

Standard policy

The Standard policy is your general-purpose baseline. Someone can join through online onboarding without their address being verified and without PEP or watchlist screening. They'll need one identity document if their address verifies, or two if it can't be verified.

It's the right choice for straightforward onboarding where extra screening isn't required.

Advanced policy

The Advanced policy is fully customisable — you set the rules yourself instead of relying on a fixed configuration.

Because the settings are yours to define, the Advanced policy isn't included in the comparison table below. Reach for it when none of the ready-made policies fit and you need verification rules tailored to your defined requirements.

Specialised policies

These policies are purpose-built for specific scenarios. They start from the same checks as the Standard policy but adjust them to suit the situation.

Member Join

Built for self-serve online joining. It verifies the member's address but doesn't ask them to enter it, because they've already typed it into the join form on the previous screen. One or two documents are then required, depending on whether the address verifies.

SuperMatch 2

A custom policy for the ATO's SuperMatch 2 service. It covers Tax File Number (TFN) eligibility and an interim allowance, and behaves like this:

  • If the TFN isn't linked to a member or employer record, access is denied.
  • If the member qualifies under the interim allowance, no verification is required.
  • Otherwise, standard checks apply — one or two documents, as per the table below.

Withdrawal

For withdrawing money out of a super account. This is the strictest of the pre-configured policies: it asks for the address to be entered, and runs both PEP and watchlist / sanction screening on top of the usual document checks.

Compare the policies at a glance

Here's how the four fixed policies line up across each setting. The Advanced policy isn't shown, since its values are whatever you configure for your fund.

Requirement Standard Member Join SuperMatch 2 Withdrawal
Address verification Optional Optional Optional Optional
Address input required No No Yes Yes
PEP check required No No No Yes
Watchlist / sanction check required No No No Yes
Documents required (address verified) 1 1 1 1
Documents required (address not verified) 2 2 2 2

‍

Accepted identity documents

All four fixed policies accept the same set of identity documents:

  • Australian driver's licence
  • Australian immigration card (ImmiCard)
  • Australian passport
  • Australian visa (foreign passport)
  • Centrelink pensioner / health concession card
  • Medicare card

‍

Not sure which to pick?
‍
Start with Standard for everyday onboarding, use a Specialised policy when you're handling a specific scenario like joining or withdrawals, and switch to Advanced only when you need to define your own rules.

‍

That's the full set of pre-configured policies. Each one is ready to use as soon as you open the module — just choose the one that matches your scenario, and the right checks are applied for you.