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).
| Field | Type | Notes |
|---|---|---|
subjectType | string | "person" to screen a person. |
organizationName | string | Required. Carries the person's name. |
country | string | ISO 3166-1 alpha-2 country of residence. Never used to filter screening. |
dateOfBirth | string | ISO yyyy-MM-dd. Disambiguates same-name people on the lists. |
citizenships | string[] | ISO 3166-1 alpha-2 codes. At least one is required for an AUSTRAC screen. |
additionalIdentifiers | object[] | { "type", "value", "issuingCountry"? } — passport, licence, etc. |
austracScreen | bool | true requests the AUSTRAC screen (3 credits). |
advancedSearch | bool | Adds the Advanced research evidence. Included in an AUSTRAC screen. |
privacyNoticeAcknowledged | bool | Required (true) for subjectType: "person". |
customerProfile | object | Optional. What the customer declared about itself: sector, purpose, funding, valueBand and the free-text sectorOther/purposeOther. Accepted only with austracScreen: true. Its ids are the ones GET /api/austrac/customer-profile/options serves; a blank field is an absent one. See section 4. |
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,
"customerProfile": {
"sector": "real_estate",
"purpose": "buy_residential_property",
"funding": "third_party",
"valueBand": "1_5m_to_5m"
}
}
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.
| Error | When | Message |
|---|---|---|
austrac_person_requires_identifiers | An AUSTRAC screen of a person is requested without a dateOfBirth or with no citizenships. | Submit them, or run a Basic or Advanced screen. |
person_identifiers_require_person | dateOfBirth, citizenships or additionalIdentifiers are sent on a non-person subjectType. | Submit them with "person", or leave them out. |
invalid_citizenship | A citizenships value is not an ISO 3166-1 alpha-2 code. | Resubmit with two-letter codes, for example "AU". |
invalid_date_of_birth | dateOfBirth is not ISO yyyy-MM-dd, or is in the future or before 1900. | Submit the subject's real date of birth as an ISO date. |
privacy_notice_required | An individual is screened without privacyNoticeAcknowledged: true. | Show the collection notice and resubmit with the acknowledgement. |
organizationName is required | The name is missing or blank. | Send the person's name. |
customer_profile_requires_austrac | A non-empty customerProfile is sent without austracScreen: true. | Submit it with the AUSTRAC screen, or leave it out. |
invalid_customer_profile | A customerProfile field carries an id the options endpoint does not serve, an entry that does not apply to a person, an other code with no text (or text beside a code that is not other), text over 100 characters, or a charityOrNpo answer, which belongs to an organisation. | The response's errors[] names the JSON path, for example customerProfile.sector. |
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:
| Field | Meaning |
|---|---|
sanctionsAuthority | The list the DFAT determination is read from — always the DFAT Consolidated List. |
dfatDetermination | listed, not_listed, possible_match or inconclusive. |
dfatDeterminationReason | Why the determination is what it is. |
dfatListUpdated | The date the DFAT Consolidated List was last updated, for the CDD record. |
subjectCitizenships | The screened person's citizenships. |
dfatComparisons | Per-record DFAT comparison: recordId, name, recordBirthDates, recordNationalities, listedOn, lastUpdated, outcome. |
foreignListings | Foreign-regime listings only: authority, program, sourceUrl. |
pepDetermination | none, domestic, foreign or international_organisation. |
pepPosition | The PEP office identified. |
pepSourceUrl | The source that identifies the PEP. |
pepCurrentOrFormer | current or former. |
pepEndDate | When the office ended, only when the PEP status rests on a former office. |
formerPepOffices | Other offices formerly held, each title, endDate, sourceUrl. |
foreignDobExclusions | Same-name foreign records excluded because their date of birth belongs to someone else. |
pepDobExclusions | Same-name PEP records excluded on date of birth. |
comparisons | Every same-name record weighed, in the shared RecordComparison shape. |
relatives | Always not_determinable on a public person screen. |
reviewRequired | Whether the screen needs manual review (listed, possible_match, inconclusive, or a foreign/international-organisation PEP). |
countryRiskMethod | How country risk is assessed (FATF lists + DFAT sanctions; the Basel AML Index is deliberately excluded). |
countryRisk | One row per country of residence and citizenship: country, band, reason, callForAction. |
riskFactors | The A1 factors present: id, label, level. |
indicativeRating | low, medium or high, derived from the risk factors. |
triggeredObligations | The AML/CTF obligations triggered: id, label, citation. |
adverseMedia | The bucketed adverse-media findings: profitGeneratingOffence, profitGenerating, minor, excluded, namesakes (each item label, url). |
customerProfile | The declaration as the customer made it, or null when none was sent: source (declared_by_customer), listVersion, declared[] (per answered input, field, code, label, other and the printed text), raisedFactors[] (id, label, level, citation) and notAssessed[] (per unanswered input, field, or per undecided factor, factorId, each with a stable reason and the printed text). For an input the reason is not_asked, not_stated or other_not_evaluated; for the high-value factor it is purpose_not_given, purpose_not_stated, purpose_other, value_not_given, value_not_stated, funding_not_given, funding_not_stated or funding_other, the first input the rule could not read. See section 4. |
cddRecord | What was screened, when, with which lists and sources, and what is not covered. |
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.
| Form item | Module field(s) it answers |
|---|---|
| D1 — Sanctions | sanctionsAuthority, dfatDetermination, dfatDeterminationReason, dfatListUpdated, dfatComparisons, foreignListings, foreignDobExclusions, comparisons |
| D3 — PEP | pepDetermination, pepPosition, pepSourceUrl, pepCurrentOrFormer, pepEndDate, formerPepOffices, pepDobExclusions, relatives |
| A1 — Risk factors | countryRiskMethod, countryRisk, riskFactors, indicativeRating, triggeredObligations, adverseMedia, customerProfile |
| CDD record | cddRecord (screenedAt, inputs, lists, searchTerms, sourcesReviewed, notCovered) |
| Disambiguation | subjectCitizenships (feeds both D1 and D3), reviewRequired (flags the whole screen for review) |
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. When the customer declares a
purposeincustomerProfile, this line narrows incddRecord.notCoveredto "the nature and purpose of the business relationship beyond the purpose the customer declared" rather than disappearing: what the customer said is recorded, it is not verified evidence, and the rest of the list stays. - 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. The declared customer profile
The AUSTRAC form's A1 risk factors are questions about the customer's own circumstances, which a public screen cannot observe. customerProfile lets the reporting entity pass on what the customer declared so the screen can apply the rules, cite them, and show the reader which inputs were never answered. It is optional, and it is never a clearance: every raised factor names the starter-kit rule it rests on, and an input that was not given is listed under notAssessed rather than left silent.
The lists are versioned (2026-10) and served by GET /api/austrac/customer-profile/options (bearer JWT), which returns each entry's code, label and appliesTo — the same spelling as subjectType, so a client can match the two. A value band's minAud is exclusive and its maxAud inclusive, so a value on a boundary sits in the band below it; the labels say so ("Over $1 million to $1.5 million", "Up to $10,000", and "Over $5 million" for the open-ended top band).
| Field | Ids | Notes |
|---|---|---|
sector | real_estate, legal_or_accounting, financial_services, remittance_or_digital_currency, gambling, precious_metals_or_stones, art_antiques_or_luxury_goods, motor_vehicle_dealer, construction, mining_or_extractive, cash_intensive_business, government_or_public_sector, charity_or_npo_sector, employee_other_sector, student_retired_or_not_employed, other | sectorOther (up to 100 characters) is required when other is chosen and refused beside any other id. |
purpose | buy_residential_property, buy_commercial_property, sell_property, lease_or_manage_property, ongoing_business_relationship, one_off_transaction, investment, other | purposeOther follows the same rule. A stated purpose narrows the nature-and-purpose line in cddRecord.notCovered to what lies beyond the purpose the customer declared; it does not remove it. |
funding | mortgage, own_funds, third_party, other, unknown | No free text. mortgage (wholly or partly) suppresses high_value_without_mortgage; own_funds and third_party let it stand; other and unknown leave it undecided. No answer raises a factor of its own. |
valueBand | under_10k, 10k_to_100k, 100k_to_1m, 1m_to_1_5m, 1_5m_to_5m, 5m_and_over, unknown | A band, never an amount. 1_5m_to_5m or 5m_and_over raises high_value_without_mortgage on a purchase purpose when funding is not a mortgage; exactly $1.5 million is in the band below. |
charityOrNpo | Organisation only | Refused on a person. See the organisation AUSTRAC screen. A person's assessment lists it under notAssessed as not asked, so the kit's charity factor is never left unmentioned. |
On this screen the rules table raises high_value_without_mortgage for the purchase of a property valued over $1.5 million without a mortgage, with the starter-kit citation and its source page. sector is recorded as declared and raises no factor: no rule we can cite reads it for an individual, and the response says so rather than inventing a citation. purpose raises no factor of its own, but it decides that one: only buy_residential_property and buy_commercial_property are purchases, and an absent or other purpose leaves the factor undecided. A factor raised from the declaration counts toward indicativeRating exactly as an evidence-raised factor does.
5. 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_compliancemodule carries the full field set above. - Sample report — Individual, AUSTRAC, the same subject rendered through the product's own PDF renderer.
6. 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
countryRiskband source), - the DFAT sanctioned countries (the country-specific regimes Australia implements).