Financial Transaction Reports (State Provisions) Act 1992

Cash dealer and reporting entity are the key regulated persons. The Act adopts the definitions from the Commonwealth FTR Act and AMLCTF Act respectively (section 3(2)). This means the state obligation attaches to the same universe of banks, credit unions, bullion sellers, gambling venues, accountants, lawyers, real estate agents, and other designated services providers that are already subject to Commonwealth anti‑money laundering rules. However, because the Act also s 6 imposes a duty on “cash dealer” (using the FTR Act definition) in relation to transactions not reported under Commonwealth law, a person could be a “cash dealer” under the FTR Act but not a “reporting entity” under the AMLCTF Act, and thus be subject to the state reporting duty only for transactions not captured by the older FTR Act regime.

Suspect transaction is not defined directly in the Act but is key to the duty in section 6. The trigger is “reasonable grounds to suspect that information that the cash dealer has concerning the transaction” may be relevant to a state offence investigation, a police function, or enforcement of the two state asset‑forfeiture laws. The test is objective (reasonable grounds) and the suspicion must relate to the information itself, not necessarily that the transaction is criminal. This is broader than the Commonwealth threshold, which typically requires suspicion that the transaction involves proceeds of crime or is financing terrorism. Here the information need only “may be relevant” to an investigation - a relatively low bar that could capture many transactions that a cash dealer might not otherwise report to AUSTRAC.

Further information is the additional material a cash dealer or reporting entity must provide to police on request under sections 5, 5A, and 6(6). It is defined by reference to being “directly or indirectly related” to the original communication. That is a very wide connecting factor - it could include account statements, identity documents, transaction patterns, internal notes, correspondence, and even information about other customers or accounts that may be indirectly linked. There is no explicit requirement that the request be reasonable, proportionate, or limited to information the entity can practically retrieve within the time frame. The obligation is to comply “to the extent that the cash dealer has the further information” - which implies that if the information is not held, there is no obligation to create it, but if it is held (including in outdated, hard‑to‑retrieve systems), it must be provided.

Protected information means information obtained under the Act (section 3(1)). This triggers the secrecy duty in section 9. The duty applies to the Commissioner of Police, police officers, and “any other person who has access to protected information in the course of official duties”. It prohibits recording or divulging the information unless in performance of a duty relating to enforcement of a law of the State, Commonwealth, another State, or a Territory. This creates a statutory information‑handling restriction but with a wide exception. Information can be passed to law enforcement across jurisdictions, but not for administrative, commercial, or private purposes. The provision also overrides court compulsion to disclose unless necessary for law enforcement - a significant departure from ordinary discovery and subpoena rules.

The primary regulated persons are cash dealers and reporting entities operating in South Australia. Since the definitions are cross‑referenced to Commonwealth Acts, this includes any entity that carries on a business of providing financial services, gambling services, bullion trading, or digital currency exchange, as well as professionals such as lawyers, accountants, real estate agents, and trust and company service providers when they engage in designated transactions. The Act does not carve out small businesses or low‑volume operators; a person who is a cash dealer under the FTR Act on even one occasion could be subject to the state duty if a transaction triggers the suspicion in section 6. The compliance burden falls on the entity itself, not only on compliance officers. Section 7(1)(b) extends liability protection to officers, employees, and agents, but the primary duty to report and provide further information is on the cash dealer or reporting entity as a legal person.

South Australia Police - specifically the Commissioner of Police and any police officer - are the requesting authority. They have the power to demand further information under sections 5, 5A, and 6(6) without any need for a warrant, court order, or external oversight. The request need only specify the information and the time period. There is no requirement that the request be in writing, though in practice it likely would be. This is a significant power: police can demand sensitive financial and personal information from private businesses based solely on receipt of a Commonwealth suspect‑transaction report. The Act does not limit how often a request can be made or the number of requests per entity.

Victims or subjects of transactions are indirectly affected. The Act facilitates the flow of their financial information to law enforcement without their knowledge or consent. The secrecy provision (section 9) restricts further dissemination but still permits wide sharing among law enforcement agencies across Australia. There is no mandatory notification to the person whose transaction is reported or about whom further information is sought. This affects privacy rights and the ability of individuals to challenge the collection or use of their data.

AUSTRAC CEO receives the reports under section 6 and the original communications under the Commonwealth Acts. The state Act does not impose new duties on AUSTRAC, but it uses its CEO’s approval power for the form of reports under section 6(3). In practice, this means a cash dealer must use the same form as for a suspicious matter report under the AMLCTF Act, integrating the state and Commonwealth reporting channels. The state report is communicated to the AUSTRAC CEO, who presumably forwards it to South Australia Police or makes it available.

Courts are affected by the secrecy provision in section 9(3): a person is not required to divulge protected information to a court unless necessary for enforcement of a law of the State, Commonwealth, another State, or Territory. This limits the scope of ordinary court process (subpoenas, discovery, summonses) for information that comes under the Act. It creates a potential conflict with the principle that courts should have access to all relevant evidence.

The Act imposes duties and also confers protections (rights) on those who comply. The central duty is to provide further information to police on request. Under sections 5, 5A, and 6(6), if a cash dealer or reporting entity has already communicated a suspect transaction report to AUSTRAC (under either Commonwealth Act or under section 6 of this Act), and the Commissioner of Police or a police officer requests further information, the entity must comply within the specified period and to the extent it has the information. This is a mandatory duty backed by criminal penalties. There is no discretion to refuse on grounds of commercial sensitivity, legal professional privilege, or data protection - unless another law overrides (see interaction with other laws). The duty also applies to “further information” that is “directly or indirectly related” - a very broad scope that could include documents concerning third parties, internal analysis, and historical records.

The next duty, in section 6, requires a cash dealer to proactively report a suspect transaction that is not reportable under the Commonwealth Acts. The dealer must form a suspicion (on reasonable grounds) that information about the transaction may be relevant to a state offence, a police function, or enforcement of the two state asset‑forfeiture laws. The report must be made “as soon as practicable” after forming the suspicion. This imposes a new vigilance obligation on cash dealers: they must assess every transaction not only for Commonwealth reporting triggers but also for potential state relevance. Because the state test is broader (mere “relevance” to an investigation rather than proceeds‑of‑crime or terrorism suspicion), this could create a lower threshold that captures many more transactions, increasing compliance costs and the volume of reports police must process.

The duty not to make false or misleading statements under section 8 applies to anyone giving information under the Act. It covers both positive false statements and omissions that make a statement misleading. The high maximum penalty (4 years imprisonment for an individual) reflects the seriousness of providing false information to law enforcement.

The secrecy duty under section 9 applies to police and other officials who access protected information. They must not record or divulge it except in the performance of a duty relating to law enforcement. This is a duty to protect confidentiality, but with a carve‑out that allows wide sharing among law enforcement agencies. It also confers a right on the person holding the information to refuse to produce it in court unless necessary for law enforcement.

Rights and protections: Section 7 provides a complete immunity from civil or criminal proceedings for cash dealers, reporting entities, and their officers/employees/agents in relation to anything done that was required under the Act, or done in the mistaken belief that it was required. This is an important protection against, for example, defamation claims by a customer whose transaction is reported, or breach of confidentiality claims. The mistaken belief protection is unusually broad: if an entity provides information to police thinking the Act requires it (even if it does not), it is protected. This could encourage over‑compliance. Section 7(2) also provides that complying with the reporting duties does not constitute money laundering for the purposes of the state offence under section 138 of the Criminal Law Consolidation Act 1935.

The Act creates several criminal offences, each with different maximum penalties. Failure to provide further information to police on request (sections 5(3), 5A(3), 6(8)) carries a maximum penalty of $30,000 for a body corporate and $8,000 or 2 years imprisonment (or both) for a natural person. The same penalty applies for failure to make a report under section 6(1) (the duty to report a suspect transaction not reported under Commonwealth law). These are strict liability offences? The Act does not specify a fault element for failure to comply. The common law presumption that fault is required may apply, but given the public interest in compliance, a court could interpret the duty as one of strict liability with a defence of reasonable excuse. The wording “must ... comply” suggests an absolute obligation, but the phrase “to the extent that the cash dealer has the further information” introduces a limit based on factual availability. If the entity does not have the information, there is no breach. However, if it has the information but fails to provide it within the period, the offence is made out.

The false or misleading statements offence (section 8) is a more serious crime, with maximum penalties of $40,000 for a body corporate and $15,000 or 4 years imprisonment for an individual. It requires knowledge: the person must know the statement is false or misleading, or know that omission makes it misleading. This is a subjective fault element, which makes it harder to prove but reflects the seriousness of deliberate deception.

The secrecy offence (section 9(2)) - unauthorised recording or divulging of protected information - carries the same $8,000/2 year maximum as the failure‑to‑provide offence. This applies to police and other officials. The breach is only if the recording or divulging is not in the performance of a law‑enforcement duty. This gives some discretion to officials, but misuse of information for private purposes or for non‑law‑enforcement government functions could be criminal.

Enforcement of these offences would be by the ordinary criminal justice process in South Australia: police investigate, the Director of Public Prosecutions decides whether to charge, and the matter is heard in the Magistrates Court or higher. There is no specific regulatory body created by this Act; it relies on existing police and prosecution resources. The penalties are modest relative to the potential harm of failing to provide information (e.g., impeding an investigation). However, the false‑statement penalty is more significant.

The Act does not provide for any civil penalties, infringement notices, or administrative enforcement. It is purely criminal. This means the evidentiary standard is beyond a reasonable doubt. Practically, a failure to comply may not be detected unless police follow up or another person reports it. The Act also does not create a right of action for individuals harmed by a breach of secrecy or by false reporting - the only sanction is criminal.

The Act expressly relies on the Commonwealth FTR Act and AMLCTF Act for definitions and for the trigger events that give rise to the further‑information duty. Without a report under those Commonwealth Acts (or under section 6), the duties under sections 5, 5A, and 6(6) would not apply. The Act also adopts the AUSTRAC CEO’s approval for the form of reports under section 6(3). This creates a dependency: if the Commonwealth Acts are amended or repealed, the state Act may become unworkable (though the state Act could be amended in turn).

Section 7(2) provides that compliance with the reporting duties (state or Commonwealth) does not constitute money laundering under section 138 of the Criminal Law Consolidation Act 1935 (SA). This is a safe harbour that overrides the state money‑laundering offence. Without this, a cash dealer who reports a transaction could potentially be said to have engaged in the transaction itself, which might be an element of money laundering. The provision ensures that reporting is not self‑incrimination. However, it only protects the person who is involved in the transaction as a cash dealer or reporting entity; it does not protect the customer.

The Act also interacts with state asset‑forfeiture laws: the Criminal Assets Confiscation Act 2005 and the Serious and Organised Crime (Unexplained Wealth) Act 2009. The further‑information request can be for information that may assist in enforcement of those Acts. This means police can use the reporting pipeline to gather evidence for civil forfeiture proceedings, which have a lower standard of proof than criminal proceedings. There is no requirement that a criminal investigation be underway; the request can be purely for asset‑confiscation purposes.

Secrecy (section 9) overrides ordinary obligations of confidentiality and court process. It provides that a person is not required to divulge protected information to a court unless necessary for law enforcement. This limits the application of rules of evidence and civil procedure. It also means that a party in civil litigation cannot subpoena a police officer to disclose information obtained under this Act, unless that disclosure is necessary for law enforcement. This could hamper civil claims against police or others.

The Act does not explicitly override legal professional privilege, the Privacy Act 1988 (Cth), or the Spent Convictions Act 2009 (SA). However, the compelled disclosure under the Act may conflict with those protections. For example, a lawyer who is a reporting entity and who has communicated with a client about a transaction could argue that further information is subject to legal professional privilege. The Act does not address this. A court might imply that privilege is preserved unless clearly overridden. Similarly, the Privacy Act generally prohibits disclosure of personal information without consent, but the state Act’s requirement could be considered a lawful authority under the Privacy Act.

The Act also interacts with state criminal law - for example, the offence of money laundering (s 138 Criminal Law Consolidation Act) is displaced by compliance with the reporting duties, but other offences like dealing with proceeds of crime or withholding information might still apply.

The Act was originally enacted in 1992 to complement the Commonwealth Financial Transaction Reports Act 1988. It was significantly amended by the Financial Transaction Reports (State Provisions) (Miscellaneous) Amendment Act 2013 (No 4/2013), which commenced on 1 April 2013. This amendment brought the Act into line with the new Commonwealth anti‑money laundering regime (the AMLCTF Act 2006). Key changes: the long title was updated to reference the AMLCTF Act; a definition of “AMLCTF Act” was inserted; the definition of “Commonwealth Act” was deleted; a new definition of “FTR Act” was inserted; section 3(3) (which presumably defined something obsolete) was deleted; section 5 was rewritten to refer to “AUSTRAC CEO” instead of “the Director” and to add the three purposes for further information (state offence, police function, asset forfeiture); a new section 5A was inserted for reporting entities under the AMLCTF Act; section 6 was substantially substituted - the duty now extends to information relevant to state asset‑forfeiture laws, the reporting form is linked to the AMLCTF Act s 41 form, and the further‑information request subsection was replaced; section 7(1) was amended to add “reporting entity” references; section 7(2) was substituted to include compliance with the AMLCTF Act sections; section 8 penalties were increased; and section 9(1) was amended to include “any other person who has access to protected information in the course of official duties” (broadening the secrecy duty).

Earlier amendments: in 2002, the Criminal Law Consolidation (Offences of Dishonesty) Amendment Act 2002 amended sections 5(2), 6(1), 6(7), and 7(2) to update cross‑references to the state money‑laundering offence and other changes (commenced 5 July 2003). In 2005, the Criminal Assets Confiscation Act 2005 amended sections 5(2) and 6(1) and (7) to add references to that Act (commenced 2 April 2006). The 2013 amendment was the most comprehensive, reflecting the shift in Commonwealth law and consolidating the state provisions.

The Act has not been amended since 2013. The legislative history note warns that references to other legislation may be obsolete; for example, the FTR Act has been largely superseded by the AMLCTF Act, but the state Act retains both references. The “Legislative history” table shows some provisions were deleted or amended - e.g., section 2 (commencement) was omitted under the Legislation Revision and Publication Act 2002. Historical versions are available for 2003 and 2006.

The source text provides no reference to any litigation concerning this Act. No cases are cited, and there is no schedule of judicial decisions. This is not surprising given the Act’s narrow scope and the fact that it is rarely litigated. The Act operates largely behind the scenes in police investigations and compliance. Offences under the Act (failure to provide information, false statements, breach of secrecy) could be prosecuted, but none appear in the public record of the source. It is possible that the courts have considered the Act in the context of challenges to search warrants or disclosure obligations, but the source does not mention any.

Given the requirement to ground claims in the source, we must note that the Act does not include any litigation history. The deep dive should state that the source contains no information about cases, and therefore no analysis of precedents or judicial interpretation can be provided. This is a limitation for practitioners: they cannot rely on court rulings to clarify ambiguous terms like “directly or indirectly related” or the scope of the mistaken belief protection.

Several provisions contain traps for the unwary. First, the “indirectly related” test for further information (sections 5(2), 5A(2), 6(7)) is extremely broad. A police request could demand information about transactions or customers that are not directly part of the original report but are linked through bank accounts, addresses, or counterparties. A cash dealer who limits the search to the transaction itself may miss information that is “indirectly related”. This creates a risk of non‑compliance if the entity does not fully appreciate the breadth.

Second, the protection in section 7(1)(a)(ii) for action taken in the “mistaken belief that it was required under this Act” could encourage over‑disclosure. An entity may disclose information to police without a valid request, believing it is required, and still be protected from civil or criminal liability. This reduces the incentive to check the legal basis for requests, potentially leading to privacy breaches. Conversely, a cash dealer who refuses a request because they believe it is not required may lose the protection if the court finds the request was valid.

Third, the secrecy provision (section 9) applies to anyone who has access to protected information in the course of official duties. This includes not just police but also other government employees who might see the information (e.g., in asset‑confiscation offices). They can be criminally liable for unauthorised disclosure, even if the disclosure is minor. The exception for “performance of a duty relating to the enforcement of a law” is vague; a disclosure to a colleague in a different law enforcement agency may be permitted, but disclosure to a prosecuting authority may also be covered. The risk is that officials might be too cautious and fail to share information that could be useful across agencies.

Fourth, the obligation to provide further information “within the period specified in the request” (sections 5(1), 5A(1), 6(6)) does not require the period to be reasonable. A police officer could demand information within 24 hours, even if the entity has to locate and retrieve data from archives or third parties. The entity must comply “to the extent that it has the information”; if it cannot retrieve it in time, it may be in breach. There is no explicit defence of impracticability. Entities should negotiate realistic time frames or seek extension in writing.

Fifth, the report under section 6(1) must be made “as soon as practicable” after forming the suspicion. This is a subjective test, but if a dealer delays reporting while investigating further, they risk non‑compliance. The Act does not allow a grace period to gather more evidence; the suspicion itself triggers the duty. Also, the report must be in the form approved for AMLCTF Act s 41 - i.e., the suspicious matter report (SMR) form. This means the dealer must use a Commonwealth form for a state‑only report, which may cause confusion because the form is designed for Commonwealth triggers.

Sixth, the false or misleading statement offence (section 8) applies to any information given under the Act, including responses to verbal requests for further information. An employee who provides an incomplete or inaccurate answer orally could be liable if they know it is misleading. This imposes a duty of care on all staff who handle such requests.

Finally, the Act contains a provision that a person is not required to divulge protected information to a court unless necessary for law enforcement (section 9(3)). This could be used to resist a subpoena from a private litigant, but it also means that a court may not have access to relevant evidence. A party in a civil case who believes police hold information about a transaction may be unable to compel its production. Conversely, if the information is necessary for law enforcement (e.g., the police are prosecuting a related offence), the court can compel it.

Compliance with this Act requires institutionalising three main processes: handling police requests for further information, making proactive state‑only reports, and protecting information secrecy.

First, each cash dealer or reporting entity that operates in South Australia should designate a compliance officer responsible for responding to police requests under sections 5, 5A, and 6(6). The entity must have procedures to quickly identify and retrieve all information “directly or indirectly related” to a previous suspect‑transaction report. This requires linking the original report to relevant transaction records, customer files, correspondence, internal notes, and possibly other accounts or transactions that the original report may touch. A single request could require searching multiple databases, physical files, and email archives. The entity must be able to produce the information within the specified period; if the period is unreasonably short, the entity should request an extension in writing, but the Act does not require the police to grant it. Documenting the search efforts and any limitations is prudent in case of non‑compliance allegations.

Second, the entity must train staff to identify transactions that may need to be reported under section 6(1) - transactions that are not reportable under Commonwealth law but where the dealer has reasonable grounds to suspect the information may be relevant to a state offence, a police function, or asset‑forfeiture enforcement. This is a broader test than the Commonwealth suspicion of proceeds‑of‑crime or terrorism financing. Staff must be taught to consider whether the information might assist an investigation into any state offence (e.g., fraud, drug trafficking, tax evasion, even minor offences) or could help police in any of their functions (e.g., missing persons, public safety). The standard is low: “may be relevant”. This could lead to over‑reporting to avoid penalties. The report must be made “as soon as practicable” after forming the suspicion - ideally within 24 hours, but at least no later than is reasonable. The report must be communicated to the AUSTRAC CEO using the form approved for AMLCTF Act s 41 - the SMR form. The form must include the grounds for suspicion and be signed. The entity must keep a copy for its records and for future further‑information requests.

Third, the entity must ensure that any information provided under the Act is accurate and not misleading. This means verifying data before submission, especially if it is provided orally or informally at a police request. The false‑statement penalty is severe, so a robust verification protocol is needed. Officers and employees should be instructed not to guess or estimate; if precise information is not available, they should state that it is not held rather than provide incomplete or approximate data.

Fourth, access to “protected information” (any information obtained under the Act) must be restricted. The entity itself is not directly subject to the secrecy duty (section 9 applies to police and officials), but the entity may receive requests from police that contain protected information, or it may generate reports that contain sensitive data. The entity should treat such information as confidential and only use it for compliance purposes. While the entity is not bound by section 9, general privacy and confidentiality obligations apply.

Fifth, the entity should document compliance with all requests and reports. If a police request is ambiguous or overly broad, the entity can seek clarification from the requesting officer. The entity should also consider whether legal professional privilege might apply to some of the further information - the Act does not expressly override privilege, so the entity may need to assert privilege unless a court orders disclosure. Seeking legal advice before refusing a request is advisable.

Finally, entities should review their contracts and terms of service to ensure they have the right to disclose customer information to AUSTRAC and police as required by law. The protection in section 7(1) covers actions required under the Act, but not disclosures beyond what is required. The mistaken belief protection only applies if the entity believed the action was required - a belief must be reasonable? The Act does not say, but a wholly unreasonable belief may not be a defence. Therefore, training should emphasise understanding the scope of the duties to avoid over‑disclosure.