CDD & KYC

Identity Verification
Three Paths, One Evidence Trail

Safe harbour, non-safe harbour, and manual verification — each path produces structured evidence with full provider reference IDs, method tracking, and audit-ready documentation.

Overview

How It Works

Customer due diligence is at the heart of Tranche 2 obligations. Sentine supports three distinct verification paths: safe harbour procedures (AUSTRAC-described for medium and lower risk customers), non-safe harbour verification, and manual verification with structured evidence capture.

For each verification, Sentine records the method path taken, stores provider reference IDs (e.g., DVS transaction IDs), and captures the evidence supporting the method. This three-part record — method, reference, evidence — is exactly what you need to demonstrate your CDD procedures during an audit.

Beneficial owner and controller identification is built into the workflow. For companies, trusts, and partnerships, Sentine guides your team through identifying individuals with 25% or greater ownership, trustees, directors, and other controllers — with structured documentation for cases where information cannot be obtained.

Workflow

Step by Step

Follow the structured workflow from start to finish.

01

Select Verification Path

Choose safe harbour (AUSTRAC-described procedures), non-safe harbour, or manual verification based on customer risk level and circumstances.

02

Customer ID Capture

Collect identity documents through the secure client portal or staff upload. Passport, licence, or other accepted documents with front/back capture.

03

Provider Verification

Run automated checks via the identity verification provider (FrankieOne). Results are normalised through the adapter pattern for vendor-agnostic storage.

04

BO/Controller Identification

For entities: identify beneficial owners (25%+ ownership), controllers, trustees, and directors. Record unknown reasons where information cannot be obtained.

05

Evidence Recording

Store verification method path, provider reference IDs, normalised results, and supporting evidence. Each check creates an immutable audit trail entry.

Capabilities

Key Features

Everything you need for this workflow, built into the platform.

Safe Harbour Guidance

Step-by-step guidance through AUSTRAC-described safe harbour procedures for medium and lower risk customers.

Provider Adapter Pattern

Vendor-agnostic integration layer. FrankieOne with a normalised result model that avoids provider lock-in.

Manual Fallback Path

When provider checks return refer or fail, structured manual verification captures the same evidence trail.

Beneficial Owner Identification

Systematic BO/controller identification for companies, trusts, and partnerships with 25% ownership threshold tracking.

Method Path Recording

Every verification stores which path was taken (safe_harbour, non_safe_harbour, manual) alongside source reference IDs.

Normalised Results

Provider results are normalised into a standard model with flags for mismatches, expired documents, and duplicates.

Regulatory Context

Verification Under the AML/CTF Act

The AML/CTF Act requires reporting entities to verify customer identity before providing a designated service. AUSTRAC describes safe harbour verification procedures for medium and lower risk customers. Sentine records the verification method path, source reference IDs, and evidence — demonstrating that your firm followed appropriate procedures regardless of which path was taken.

  • Safe harbour: AUSTRAC-described procedures for medium/lower risk
  • Method path storage: safe_harbour | non_safe_harbour | manual
  • Provider reference IDs (DVS transaction IDs) must be retained
  • Beneficial owners: 25% ownership threshold for companies

Streamline Your CDD Process

Structured verification paths with complete evidence trails — ready for audit from day one.

Get Started