Person AUSTRAC screen

The AUSTRAC screen of a person answers the question an identity-check provider cannot: is this person a listed person under the AML/CTF Act, and what does my AML/CTF program have to do about it? It is sold mainly to integrators, as the sanctions and PEP source inside their own AUSTRAC solutions. An integrator bundles an identity check (a document or biometric check) with this screen; VerityRadar supplies the screening part, and this page documents exactly what that part returns and what it still leaves to you.

The screen is deterministic: it reads the person's date of birth and citizenships from the request, resolves the DFAT and PEP determinations from the structured screening hits, and writes one austrac_compliance module into the investigation response. It never authors the person's adverse-media findings — those come from the standard adverse-media process and are bucketed here.

1. The request

POST /api/ai-investigate (bearer JWT or long-lived API key; rate-limited under ai-investigations-per-ip).

A complete person AUSTRAC request:

{
  "subjectType": "person",
  "organizationName": "Rosa Delgado",
  "country": "VE",
  "dateOfBirth": "1979-03-22",
  "citizenships": ["VE"],
  "additionalIdentifiers": [
    { "type": "passport", "value": "987654321", "issuingCountry": "VE" }
  ],
  "austracScreen": true,
  "privacyNoticeAcknowledged": true
}

A screen costs 1 credit (Basic), 2 (Advanced) or 3 (AUSTRAC). AUSTRAC includes the Advanced research, so advancedSearch adds nothing to an AUSTRAC screen.

400 rules

Every guard below runs ahead of the billing path, so a refused request costs nothing. The person-identifier refusals carry creditsCharged: 0.

A 402 (insufficient credits or an exhausted per-key budget) is a billing failure, not a refusal: the request was valid but could not be paid for.

2. The response

The response is the v2 investigation envelope. The screen is the austrac_compliance module in modules[] (moduleId: "austrac_compliance", category: "compliance", displayOrder: 190, tier: "free"). Its status is one of listed, possible_match, found, not_found or inconclusive; its severity is derived by the same rules as every other module.

The module's data object:

3. Mapping to AUSTRAC's Initial CDD form for an individual

The screen is organised to answer the items on AUSTRAC's Initial CDD form for an individual.

What the screen does not cover

cddRecord.notCovered names what remains the reporting entity's responsibility and is not part of this screen:

• Identity verification — that the person is who they claim to be. This is the identity-check provider's job, not the screen's.
• A representative's authority — that a person acting for a customer has authority to act.
• The nature and purpose of the business relationship.
• Source-of-funds or source-of-wealth evidence — the screen can trigger the obligation (source_of_funds_wealth) but does not collect the evidence.

4. Sample response and sample report

A fictional sample is published alongside this guide and kept in sync with the live schema by the report-sample tests.

• Sample response — verityradar-sample-individual-austrac.json, a fictional person whose austrac_compliance module carries the full field set above.
• Sample report — Individual, AUSTRAC, the same subject rendered through the product's own PDF renderer.

5. Data coverage

What this screen can find is bounded by the data the crawler ingests. The Screening Data Coverage Statement is the authoritative record of that; it is available on request from VerityRadar while its public host is prepared. The screen itself draws on three dated lists, recorded in cddRecord.lists:

• the DFAT Consolidated List (dated in dfatListUpdated),
• the FATF high-risk and other monitored jurisdictions (the countryRisk band source),
• the DFAT sanctioned countries (the country-specific regimes Australia implements).