What is AUSTRAC?

The Australian Transaction Reports and Analysis Centre (AUSTRAC) is the government agency responsible for detecting, deterring, and disrupting criminal abuse of Australia’s financial system. Established under the Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (AML/CTF Act), AUSTRAC regulates reporting entities and enforces compliance with money laundering and terrorism financing controls.

For product teams, AUSTRAC’s role translates into technical requirements: customer identification workflows, transaction monitoring systems, suspicious matter reporting mechanisms, and audit trails that can withstand regulatory scrutiny. AUSTRAC does not care how you build these capabilities. It cares that you can demonstrate they exist and function correctly.

Who AUSTRAC Applies To

AUSTRAC obligations apply to reporting entities under the AML/CTF Act. As of March 2026, the scope expands significantly under Tranche 2 reforms.

Who AUSTRAC applies to: entity types, examples and when obligations start
Who AUSTRAC applies to: entity types, examples and when obligations start

If your platform facilitates payments, currency exchange, digital asset transfers, or remittances for Australian customers, you are almost certainly a reporting entity. DCE providers (crypto exchanges, DeFi gateways with fiat on/off-ramps) have been regulated since 2018. The Tranche 2 expansion brings professional services into scope for the first time.

Key Dates: Tranche 2 Reforms

Tranche 2 represents the most significant expansion of Australia’s AML/CTF regime since 2006. Here are the critical deadlines for product and compliance teams:

Key dates for the Tranche 2 reforms and the action each one requires
Key dates for the Tranche 2 reforms and the action each one requires

These are hard deadlines. Systems built without AUSTRAC compliance from day one create technical debt that becomes exponentially more expensive to remediate under audit pressure.

What AUSTRAC Expects from Your Systems

AUSTRAC does not prescribe specific technologies. It prescribes outcomes: identification, monitoring, reporting, and record keeping. Your engineering implementation must deliver these outcomes in a way that generates defensible evidence.

What AUSTRAC expects from your systems: obligations, technical requirements and evidence
What AUSTRAC expects from your systems: obligations, technical requirements and evidence

The most common audit failure: systems that perform compliance actions but do not log the evidence those actions occurred. AUSTRAC audits are evidence-based. If your system verified a customer but did not record the timestamp, method, and result, it did not happen.

Implementation Steps for Product Teams

Building AUSTRAC-compliant systems from scratch avoids the technical debt of retrofitting compliance into production platforms. Here is the implementation sequence that minimises rework:

  1. Map your obligations before writing code.Determine whether you are a reporting entity, which services trigger obligations, and what customer thresholds apply. This is a Technical Advisory exercise, not a development task.
  2. Choose your verification architecture.API-based eKYC integration (Onfido, Sumsub, Jumio) is fastest for platforms with existing infrastructure. Direct DVS (Document Verification Service) integration offers lower ongoing costs for Australia-focused platforms. Custom modules provide full control but require 3–6 months. Match architecture to your compliance scope and timeline.
  3. Implement risk-based verification tiers.AUSTRAC does not require identical verification for every customer. Low-value, low-risk customers can use simplified identification. High-value or high-risk customers trigger Enhanced Due Diligence. Tier your verification workflows by risk score, not blanket maximum verification for all users.
  4. Build your transaction monitoring from day one.Monitoring cannot be added later without reprocessing historical transactions. Define alert rules, investigation workflows, and SMR submission processes before your first production transaction. Reference AUSTRAC’s risk-based approach guidance for rule calibration.
  5. Design for audit trail generation.Every compliance action your system takes must generate a log entry. Verification timestamp. Risk assessment applied. Alert triggered. Investigation outcome. SMR filed or dismissed. These logs are your evidence. Store them in tamper-evident systems with retention enforcement.
  6. Test your reporting mechanisms.AUSTRAC requires Threshold Transaction Reports (TTRs) and International Funds Transfer Instructions (IFTIs) for certain transaction types. Build and test reporting submission flows before production launch. Late or incorrect reporting triggers enforcement action.
  7. Document your AML/CTF program.Your program describes how your technical controls implement AUSTRAC’s requirements. This is not marketing material. It is a technical specification auditors will test against your actual system behaviour. Write it after your architecture is defined but before production deployment.

Platforms that follow this sequence pass first audit with minimal remediation. Platforms that build first and retrofit compliance later face 3–6 month delays, reputational damage, and enforcement risk during the gap period.

Building the Right Audit Trail

AUSTRAC audits examine your evidence, not your promises. The audit trail your systems generate determines audit outcomes more than the sophistication of your compliance logic.

What to log:

  • Customer verification: timestamp, method, document type, verification result, risk rating assigned, staff override (if manual review occurred)
  • Ongoing due diligence: profile update trigger, data changed, re-verification outcome, analyst decision
  • Transaction monitoring: alert generated, rule triggered, investigation opened, evidence reviewed, outcome (SMR filed / dismissed / escalated), analyst identity and timestamp
  • Reporting: SMR/TTR/IFTI submission timestamp, AUSTRAC acknowledgment reference, report content hash

How to store it:

  • Tamper-evident storage: append-only logs, cryptographic signing, or blockchain-based audit trails
  • 7-year retention minimum from the end of the customer relationship (longer for certain high-risk entities)
  • Searchable and exportable for AUSTRAC requests: JSON/CSV export capability, date range filtering, customer ID indexing
  • Access controls and audit logs: who accessed what compliance data, when, and why

Common mistakes:

  • Logging actions but not outcomes: “verification initiated” without “verification passed/failed”
  • No timestamp granularity: date without time makes sequencing impossible during investigations
  • Staff decisions without rationale: “SMR dismissed” without “reason: transaction consistent with customer profile”
  • Overwriting data: updating customer profiles without retaining change history

The gold standard: your audit trail should allow AUSTRAC to reconstruct every compliance decision your platform made, in sequence, with the evidence available to your system at decision time. If you cannot do this, your audit trail is incomplete.

AML/CTF: Anti-Money Laundering and Counter-Terrorism Financing. The regulatory framework AUSTRAC enforces.

Tranche 2 AML Reforms: The 2026 expansion of AUSTRAC obligations to professional services sectors.

Need Help Building AUSTRAC-Compliant Systems?

AUSTRAC compliance is not a checkbox. It is an engineering challenge that shapes your architecture, data flows, and audit capabilities from day one.

We help Australian product teams build systems that pass AUSTRAC audits without killing user experience.

Our compliance-first approach integrates verification, monitoring, and audit trail generation into your product roadmap before code is written, eliminating the technical debt of retrofitted compliance.

Frequently Asked Questions

Operating as a reporting entity without AUSTRAC registration is a criminal offence under the AML/CTF Act. Maximum penalties: AUD $22.2 million for corporations, AUD $4.4 million for individuals. Beyond financial penalties, unregistered operation prevents you from offering designated services legally. If your platform already has customers, late registration does not exempt you from retrospective compliance obligations for the period you operated unregistered.

Yes. AUSTRAC does not require in-house verification systems. Third-party providers (Onfido, Sumsub, Jumio, IDnow) are acceptable as long as their methods meet AUSTRAC’s verification standards and you retain evidence of the verification in your own audit trail. The critical requirement: you remain responsible for compliance outcomes even when using third-party tools. If the provider’s verification fails and you onboard a sanctioned individual, AUSTRAC holds you accountable, not the vendor.

AUSTRAC does not publish mandatory rule sets. It expects a risk-based approach: your rules should be calibrated to the risks your business faces based on customer types, transaction patterns, and jurisdictions served. Indicators of insufficient monitoring: zero alerts generated over extended periods, no documented rule tuning process, inability to explain why specific thresholds were chosen. Reference the AUSTRAC ML/TF Risk Assessment for baseline risk factors, then document how your rules address those risks for your specific business model.

Tranche 1 (current) covers financial institutions, money remitters, gambling providers, and digital currency exchanges. Tranche 2 (commencing 1 July 2026) extends obligations to professional services: lawyers, accountants, real estate agents, dealers in precious metals and stones. The core obligations are the same (customer identification, transaction monitoring, suspicious matter reporting), but risk profiles differ significantly. A real estate agent faces different ML/TF risks than a crypto exchange. AUSTRAC expects your AML/CTF program to reflect your actual risk environment, not a generic template.

If your obligations are unclear, your risk profile is undefined, or you’re unsure which technical architecture meets your requirements: yes. A Technical Advisory engagement maps your AUSTRAC obligations to your product roadmap, defines your verification architecture, and produces a fixed-price proposal for compliant implementation. The alternative is building first and discovering compliance gaps during audit, which is exponentially more expensive to remediate. Five days of discovery prevents six months of rework.

Read more

A Clickable Prototype Proves the Story, Not the System

1 min18 November 2026
Read the article

SaaS: Streamlining Modern Business Operations through Cloud Technology

1 min11 May 2026
Read the article

Consumer Data Right (CDR): What Teams Must Ship

1 min28 April 2026
Read the article

Need a technical read on your next product decision?

Tell us what is changing in the product, delivery plan or live system. We will help identify the right next conversation.