Language:
PRODUCTS
SECTORS
MORE
Quantum Security 🔍 Search Request Access →
gateAUSTRAC — Australia AML/CTF Act 2006 Gate
// The problem

Three deadlines counted differently is a classic place where something slips through.

Australia has the most differentiated reporting system of any implemented jurisdiction: a Suspicious Matter Report within 24 hours, a Threshold Transaction Report within 10 business days at 10,000 AUD or more, an International Funds Transfer Instruction Report at 10,000 AUD or more. gateAUSTRAC checks all three as independent, parallel-running deadlines.

24-hour SMR deadline as the sharpest reporting duty of any jurisdiction
The 24-hour Suspicious Matter Report deadline under section 43 is significantly shorter than comparable deadlines in the UK, Switzerland, or Singapore. The gate seals the moment of detection to calculate this deadline deterministically.
// Architecture

5 clusters, checked sequentially.

Every cluster is dispositive (material_block_mode: true), a hit blocks bindingly, not merely for documentation.

CLUSTER 1
AUSTRAC Registration & Programme
Checks AUSTRAC registration (§6) and a documented AML/CTF programme (§81) covering CDD, monitoring, and training.
austrac_registered · amlctf_program
CLUSTER 2
CDD & EDD & UBO & PEP
Checks CDD (§33), enhanced due diligence for high risk (§37), UBO identification (§33), and PEP screening (§35).
cdd · edd_high_risk · ubo_identified · pep_screened
CLUSTER 3
SMR Within 24 Hours
Checks Suspicious Matter Report filing within 24 hours to AUSTRAC (§43), the sharpest deadline of any jurisdiction.
smr_within_24h
CLUSTER 4
TTR & IFTI
Checks Threshold Transaction Report at 10,000 AUD or more within 10 business days (§43) and IFTI report at 10,000 AUD or more (§46).
ttr_filed_if_applicable · ifti_filed_if_applicable
CLUSTER 5
DFAT Sanctions & Retention
Checks DFAT Consolidated Sanctions List screening and 7-year retention (§105).
dfat_screened · retention_7y
No case, no doubt
Every cluster returns its own sealed result. A single hit in an active cluster is enough to block the overall action.
// Test results

Two tested scenarios.

All values on this page are fictional test data and serve only to illustrate the gate logic.

Scenario C1C2C3C4C5 Verdict Latency
Full compliance (13/13)PASSPASSPASSPASSPASSAUSTRAC_SEALED408ms
7 critical violations + TTR + IFTIFAILFAILFAILFAILnot evaluatedBLOCK_AUSTRAC_11_FLAGS371ms
Cryptographic chain continuation
Every test produces a deterministic receipt_id, an input_snapshot_hash, an HMAC-SHA256 signature, and a merkle_link to the previous receipt. Persistence occurs in the gateAUSTRACReceipt entity with a 10-year retention period.
// Clarification

What gateAUSTRAC is not.

  • Not automatic recognition by AUSTRAC. The gate delivers a cryptographic proof, not regulatory filing confirmation.
  • Not an independent filing system. The gate seals the pre-check, it does not itself file an SMR, TTR, or IFTI with AUSTRAC.

For AUSTRAC-registered entities that want to make three parallel reporting deadlines provable.

GATE CATALOG · REGULATORY DETERMINATION DOMAIN

gateAUSTRAC

gateAUSTRAC determines encoded Australian AML/CTF, reporting, entity and transaction conditions for a defined scope. The gate contributes a bound regulatory determination state; it creates neither regulatory authority nor Execution Permission.

DOMAIN_DETERMINATION_ONLY = true · EXECUTION_AUTHORITY = false · EXECUTION_PERMISSION = false
gateAUSTRAC regulatory determination domain
AUTHORITY BOUNDARY

AUSTRAC STATE IS NOT REGULATORY AUTHORITY.

CAN

  • deterministically evaluate encoded regulatory conditions
  • bind determinations to source, scope, time and input state
  • surface missing, expired or conflicting regulatory dependencies
  • produce attributable evidence for the concrete determination

CANNOT

  • replace a regulator, supervisor, court or competent institution
  • create legal or regulatory authority through score, consensus, AI or administration
  • turn a gate PASS into an Execution Right on its own
  • mint an ExecutionCapabilityToken on its own
REGULATORY STATE

Regulatory determination is evidence. Not regulatory authority.

SOURCE

Authoritative source

The relevant rule must originate outside the system from a legitimate normative or institutional source.

SCOPE

Defined matter

The determination is limited to the encoded subject, entity, transaction or operation under review.

TIME

Point-in-time state

Effective dates, transition periods, expiry and version state remain explicit.

INPUT

Canonical input

A reproducible determination requires a defined canonical input state.

DEPENDENCY

Dependencies

Missing or contradictory dependencies remain visible rather than being converted into invented permission.

EVIDENCE

Bound evidence

The resulting state can be bound to source, input, scope and time for later verification.

RELATED DETERMINATION DOMAINS

Regulatory domains compose. They do not confer authority on one another.

Only scope-relevant determinations become dependencies in Execution Rights resolution. The links shown are not a universally mandatory sequence.

EXECUTION RIGHTS

Five dimensions. Regulatory state can inform them; no gate replaces them.

AAUTHORITY
RRULE
JJURISDICTION
TTIME
DDEPENDENCY
ALL FIVE REQUIRED DIMENSIONS VALID → VALID EXECUTION RIGHT · ANY REQUIRED DIMENSION ABSENT → NO VALID EXECUTION RIGHT → NO CAPABILITY → NO EXECUTION
INVARIANT

A regulatory PASS is a determination. Never a permission by itself.

AUTHORITY → DETERMINATION → EXECUTION RIGHTS → CAPABILITY OR NONE → EXECUTION OR NONE → EVIDENCE

Request Access →