# Electronic report file format specification – threshold transaction report

Copyright © 2026 Commonwealth of Australia

Revision: 1.0-DRAFT – May 2026

# Part I. Preparing reports for AUSTRAC

## Chapter 1. Introduction

## 1.1. Background

### 1.1.1. About AUSTRAC

The Australian Transaction Reports and Analysis Centre (AUSTRAC) is a Commonwealth government agency that was established in 1989.

AUSTRAC performs a dual role as Australia’s anti-money laundering and counter-terrorism financing (AML/CTF) regulator and financial intelligence unit. This dual role helps to build resilience in the financial system and enables AUSTRAC to use financial intelligence and regulation to disrupt money laundering, terrorism financing and other serious crime.

As Australia’s AML/CTF regulator, we regulate businesses (referred to as reporting entities) that provide designated:

- Financial services, including remittance and virtual asset services
- Bullion and precious metals, stones and products
- Gambling services
- Real estate services
- Professional services

As a financial intelligence unit, we collect and analyse financial reports and information from reporting entities to generate financial intelligence that contributes to law enforcement and national security investigations.

AUSTRAC administers the Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (AML/CTF Act).

### 1.1.2. Anti-Money Laundering and Counter-Terrorism Financing Act 2006

The AML/CTF Act implements a risk-based approach to regulation and sets out general principles and obligations. Details of how these obligations are to be carried out are set out in the Anti-Money Laundering and Counter-Terrorism Financing Rules 2025 (AML/CTF Rules). Together, the AML/CTF Act and Rules form part of Australia’s AML/CTF regime.

Australia's AML/CTF regime follows the international standards set by the Financial Action Task Force (FATF) and is in place to deter, detect and disrupt money laundering, terrorism financing and proliferation financing.

The AML/CTF regime imposes a number of obligations on reporting entities when they provide designated services. The key obligations are to:

- Enrol or register with AUSTRAC
- Develop and maintain an AML/CTF program
- Conduct customer due diligence
- Report transactions and suspicious matters to AUSTRAC
- Make and keep records.

### 1.1.3. Reporting obligations

The Anti-money Laundering and Counter-Terrorism Financing Act 2006 Anti-money Laundering and Counter-Terrorism Financing Act 2006 AML/CTF Act requires the reporting of suspicious matters, threshold transactions, international funds transfer instructions (to be replaced in the near future by international value transfer services), transfers of value involving unverified self-hosted virtual asset wallets, compliance reports and cross-border movements of monetary instruments.

These specifications are for reporting threshold transactions.

#### 1.1.3.1. Reports of threshold transactions

Under section 43 of the Anti-money Laundering and Counter-Terrorism Financing Act 2006 Anti-money Laundering and Counter-Terrorism Financing Act 2006 AML/CTF Act, threshold transactions are required to be reported if a reporting entity provides, or commences to provide, a designated service to a customer who is a party to a transfer of physical currency of A$10,000 (or foreign equivalent) or more.

## 1.2. Purpose of document

This document specifies the expected file type, naming convention, layout and content for electronic reporting of threshold transaction reports to AUSTRAC.

This is the definitive specification for reporting based on the requirements of the AML/CTF Act and Rules.

This document also outlines:

- How a reporting entity can go about testing their systems and communication interfaces with AUSTRAC prior to implementing changes to their production/live environments; and

- The available methods for submitting these files to AUSTRAC.

### 1.2.1. What is a threshold transaction?

It is a transaction involving the transfer of physical currency (i.e. cash) of A$10,000 or more (or the foreign currency equivalent) as part of providing a designated service. A transfer can include receiving or paying cash.

This type of transaction is a threshold transaction. The report form for reporting these transactions is called a threshold transaction report (TTR).

Notes:

1. Threshold transaction and physical currency are defined under section 5 of the AML/CTF Act.
2. Physical currency means the coin and printed money of Australia, or of a foreign country, that is designated as legal tender, circulates as and is customarily used and accepted as medium of exchange in the country of issue (i.e. cash).
3. The XML schema for electronic reporting of threshold transactions is based on the design of the single report form.

## 1.3. Reference material and source code library files

### 1.3.1. Related documents

This specification should be read in conjunction with the following reference documents:

Document | Description | Available from
--- | --- | ---
AML/CTF Act | The Act which outlines the obligations for reporting entities, AUSTRAC and AUSTRAC’s partner agencies under legislation of the Commonwealth of Australia. | AUSTRAC – www.austrac.gov.au; or Federal Register of Legislation – www.legislation.gov.au
Part 9, Division 2 of the AML/CTF Rules | Legislative rules which outlines the information that needs to be supplied in reports of threshold transactions. | AUSTRAC – www.austrac.gov.au; or Federal Register of Legislation – www.legislation.gov.au
Details to be advised | API specification outlining the requirements for automating the sending of report files to AUSTRAC. | AUSTRAC Online – online.austrac.gov.au Details to be advised.

### 1.3.2. XML schema definitions

The structure and contents of report files to be submitted to AUSTRAC is defined by the following XML schema defines the structure of an XML document in terms of constraints. The XML schema specification is published and maintained by W3C.XML schema defines the structure of an XML document in terms of constraints. The XML schema specification is published and maintained by W3C.XML schema definition file:

Schema | Version | Description | Available from
--- | --- | --- | ---
TTR-1-0.xsd | v1.0 DRAFT Effective from 1 July 2026 | The XML schema defines the structure of an XML document in terms of constraints. The XML schema specification is published and maintained by W3C.XML schema defines the structure of an XML document in terms of constraints. The XML schema specification is published and maintained by W3C.XML schema for threshold transaction reports. This schema describes the structure and content of a threshold transaction report (TTR) file containing one or more reports. | AUSTRAC Online – online.austrac.gov.au Details to be advised.

Reports made using this XML schema are pursuant to the requirements of section 43 of the AML/CTF Act. Criminal penalties may apply for providing false or misleading information and civil penalties may apply for failing to supply information.

## 1.4. Version compatibility and support information

This is the initial version of TTR reporting commencing on 1 July 2026. It is not compatible with any previous version of TTRs.

For assistance or further information, refer to Section 1.5, “Enquiries about this specification” Enquiries about this specification for contact details.

## 1.5. Enquiries about this specification

Where clarification is sought on any matter in relation to this document, enquiries should be directed to the AUSTRAC Contact Centre (contact@austrac.gov.au).

For further contact details, refer to https://www.austrac.gov.au/contact-us.

## Chapter 2. How to submit a report file to AUSTRAC

There are two available methods for submitting report files to AUSTRAC:

1. A file upload function available in AUSTRAC Online; or

2. Via the <to be advised> API.

This document outlines the requirements for the file submission options, so that a reporting entity can create a software solution:

- To extract the required information from their systems and format that information in the expected and acceptable format in a single file, for meeting reporting obligations under the AML/CTF Act and Rules; and
- To easily upload that file to AUSTRAC; or
- To automate submission of that file to AUSTRAC.

## 2.1. File upload

The file upload function is available in AUSTRAC Online. From Reporting | Make a Report navigate to the Threshold Transaction Report page. File upload is an option under How would you like to report?.

This function allows users to drag and drop a report file or browse to select a report file to be submitted to AUSTRAC.

## 2.2. <to be advised> API

Details to be advised

## Chapter 3. File format and structure

Each file submitted to AUSTRAC should consist of a single XML document containing threshold transaction reports (TTR) that conform to the following:

    <?xml version="1.0" encoding="UTF-8"?>
    <ttrList
       xmlns="http://austrac.gov.au/schema/reporting/TTR-1-0">
       <reAustracAccountNumber>...</reAustracAccountNumber>
       <fileName>...</fileName>
       <reportCount>...</reportCount>
       <ttr>
         <header>...</header>
         <customer>...</customer>
         <otherPerson>...</otherPerson>
         <recipient>...</recipient>
         <transaction>...</transaction>
       </ttr>
    </ttrList>

Where:

| is the XML declaration specifying the encoding;
| is the root element (first XML element) and must be <ttrList> for reports of threshold transactions;
| is the namespace (`xmlns`) attribute declaring the namespace of the schema used to validate structure and content;
| identifies the reporting entity (i.e. the business) the reports belong to;
| is the name of the file containing this XML document;
| is the number of reports to be found in this file; and
| is one or more TTR reports - the number of reports should match the amount specified in .

Refer to Appendix D, XML Overview for information on creating Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML documents.

## 3.1. Validation

To take advantage of the inherent document format validation features of Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML, reporting entities are expected to download the relevant XML schema definition (XSD) file and use this file to build and validate the completeness of their XML documents prior to submitting these documents to AUSTRAC.

To avoid unnecessary or misleading XML validation errors, AUSTRAC recommends the use of escape sequences or CDATA sections when extracted data contains characters which form part of XML syntax such as less than symbols (<) and ampersands (&). Escape sequences (e.g. <, &, etc.) instruct an XML parser to substitute the escape sequence for the special character it represents. CDATA sections instruct an XML parser to ignore any text within the section to preserve the text in its entirety when validating an XML document. Escape sequences should be used, unless the extracted text needs to be preserved.

Refer to Appendix D, XML Overview for further information on escaping and CDATA sections.

Upon submission to AUSTRAC, each XML document will be subjected to further content and context validation checks. This is to ensure the document contents have at least met the minimum requirements for the obligation of reporting threshold transactions under the Anti-money Laundering and Counter-Terrorism Financing Act 2006 Anti-money Laundering and Counter-Terrorism Financing Act 2006 AML/CTF Act and the Anti-Money Laundering and Counter-Terrorism Financing Rules 2025 Anti-Money Laundering and Counter-Terrorism Financing Rules 2025 AML/CTF Rules.

## 3.2. File encoding

AUSTRAC uses 8-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.8-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.UTF-8 character encoding and so recommends the use of an XML declaration at the start of each XML document specifying the character encoding of the XML document, especially if your systems use other character encodings, e.g. Windows-1252.

An example of an XML declaration:

    <?xml version="1.0" encoding="UTF-8"?>

Refer to Section D.3.1, “Character set encoding” for more information on encoding.

## 3.3. File naming convention

Files containing TTR reports are to be named using the following convention:

> `TTRyyyymmddssssssss.xml`

where:

> TTR

>   is fixed text identifying the report type of the report(s) contained in the file,

> yyyymmdd

>   is the date the file was created,

> ssssssss

>   is a unique identifier. It can be made up of 1-8 digits where each digit can be any number from 0-9. AUSTRAC recommends the use of a timestamp followed by a two (2) digit number.

>   For example, a file created on 01/07/2026 at around 11:30:45 AM may be named TTR2026070111304501.xml.

> `xml`

>   is the standard file extension suffix identifying the file as being an XML document.

## Chapter 4. How to conduct testing with AUSTRAC

To ensure a reporting entity’s data extraction and reporting software is adequate, and that no systemic data quality issues are present, all reporting entities using this method of reporting are required to undergo a test process prior to submitting reports to AUSTRAC.

To schedule testing, contact AUSTRAC via datacapabilities@austrac.gov.au.

For further contact details, refer to https://www.austrac.gov.au/contact-us.

# Part II. Schema reference

## Chapter 5. How to read this reference

This document complements the schema by describing what information is required in each of the XML elements.

The diagram below shows how each XML element is documented within Part II, “Schema reference”.

| The name of the element or type.
| Extends – declares that this element extends another. Refer to the documentation for that element to see what other attributes or child elements are required.
| Attributes – declares that this element has attributes that can be provided in the start tag. Look at the occurrence column to determine if the attribute is optional or mandatory.
| Choice – shows which child-elements are mutually exclusive; you can choose just one of these child elements. It is possible for a sequence to be one of the choices. In this case, if you choose the sequence you must supply all of the child elements necessary for that sequence.
| Sequence – shows which child-elements are part of an ordered sequence; these child-elements must be supplied in the same order that they appear in this documentation. It is possible for a choice to be one of the sequence items. In this case, you must choose just one of the choice elements to place at this position in the sequence.
| Attributes/child-element – shows the names of the attributes or child elements as they are to appear in the generated XML document. These are hyperlinked to the relevant sections in this document for each attribute and child element.
| Occurrence – shows how many times this child element is expected or permitted. For example:
`(1)` this element is mandatory and only one occurrence is expected
`(0..1)` this element is optional and can appear no more than once
`(0..5)` this element is optional and can appear up to five times
`(0..*)` this element is optional and there is no upper limit to how many times it may occur
`(1..3)` this element must appear at least once and no more than three times
`(1..*)` this element must appear one or more times (no upper limit)
| Assert – A 'Y' value in this column indicates the element is subject to an assert statement. Assert statements are used to set conditions for some elements in the report form, such as defining expectations for YesNo responses, when extra details are required or changing conditions when legal professional privilege (LPP) applies. Refer to the accompanying XML schema definition file (.xsd) for the rules of each assert statement and error message returned if the assert statement test fails.
| Type – shows the name of the element or type that defines the extension, attribute, or child element. Types define generic reusable data types or blocks of XML. The documentation for types tends to be less specific than the documentation that appears for each attribute and child element. These are usually hyperlinked to the relevant sections in this document to describe how to provide the necessary information for that data type or block of XML.
| Used within – provides a list of the places where this element or type is used; that is, the possible parent elements. These are usually hyperlinked to the relevant sections in this document for that element or type.
| Attributes & Child elements – provides a description of what information is expected for each attribute and child element.

Below is an example of the kind of XML that could be created for the example account structure shown in the diagram above:

    <exampleAccount id="abc-123">
      <title>Some Company &amp; Associates Ltd</title>
      <number>777888999</number>
      <type>CHEQUE</type>
      <signatoryName>John Smith</signatoryName>
      <signatoryName>Mary Brown</signatoryName>
      <currentBalance>222.33</currentBalance>
    </exampleAccount>

| The account element requires an ID attribute in the start tag.
| The title/name and number elements were defined by the AccountSimple base type that the exampleAccount extended.
| The type element was one of the choice elements that we had to choose from.
| There are two signatories for this account.
| We are providing an account balance.

Note: The schema also uses assert statements to set conditions for some elements in the report form, such as defining expectations for YesNo responses, when extra details are required or changing conditions when legal professional privilege (LPP) applies.

For an example of some complete reports refer to Appendix F, Sample TTR XML document.

## Chapter 6. Root element

This section describes the root element. Whilst a schema may define many elements as global (top-level) or root elements, AUSTRAC only expects one root element per XML document.

## global element6.1. <ttrList>

<ttrList> | Attribute/child-element | Occurrence | Assert | Type | Section
sequence – |  | <reAustracAccountNumber> | (1) | N | AAN | 9.1
| <submitterAustracAccountNumber> | (1) | N | AAN | 9.1
| <fileName> | (1) | N | TTRFileName | 9.51
| <reportCount> | (1) | Y | ReportCount | 9.46
| <ttr> | (1..*) | N | ttr | 7.1

### 6.1.1. Description

This is the root element for an XML document containing TTR reports.

### 6.1.2. Child elements

`<reAustracAccountNumber>`

  The AUSTRAC identifier assigned to the reporting entity obligated to report the threshold transaction reports.

  This identifier is assigned by AUSTRAC at the time of enrolment and is referred to as an AUSTRAC Account Number (AAN). The AAN is displayed to users when they log in to AUSTRAC Online.

  See also: AAN (9.1)

`<submitterAustracAccountNumber>`

  The AUSTRAC identifier assigned to the reporting entity or reporting group member submitting the threshold transaction reports.

  This identifier is assigned by AUSTRAC at the time of enrolment and is referred to as an AUSTRAC Account Number (AAN). The AAN is displayed to users when they log in to AUSTRAC Online.

  If the reporting entity is a member of a reporting group, another member of the group may discharge their reporting obligation by submitting the reports on their behalf.

  <submitterAustracAccountNumber> is used in conjunction with <reAustracAccountNumber> to indicate who is submitting reports on behalf of whom.

  If there is no reporting group or your business is reporting for itself, <submitterAustracAccountNumber> and <reAustracAccountNumber> will contain the same AAN.

  If your business is a reporting group member submitting the reports on behalf of another member, <submitterAustracAccountNumber> is the AAN of your business and <reAustracAccountNumber> is the AAN of the other member.

  See also: AAN (9.1)

`<fileName>`

  TTR report file identifier – this is the name of the file containing the threshold transaction reports to be sent to AUSTRAC. The content of this element must match the name of the file and be unique amongst all the files provided to AUSTRAC by the reporting entity.

  See also: TTRFileName (9.51)

`<reportCount>`

  The number of reports of threshold transactions in the file.

  Notes:

  1. The value of <reportCount> must match the number of reports in the file.

  See also: ReportCount (9.46)

`<ttr>`

  A report of a threshold transaction (see Section 1.2.1, “What is a threshold transaction?”).

  Use a separate <ttr> element to report each threshold transaction.

  See also: <ttr> (7.1)

## Chapter 7. Elements

This section describes all the globally defined elements within the schema as well as all their nested elements. Nested elements are those that are defined within the context of other parent elements.

## global element7.1. <ttr>

<ttr> | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – |  | <header> | (0..1) | N | header | 7.2
| <lppDetails> | (1) | N | LppDetails | 8.24
| <customer> | (1..*) | Y | customer | 7.3
choice – | sequence – |  | <otherPerson> | (1..*) | Y | otherPerson | 7.5
| <representedOrganisation> | (0..*) | N | representedOrganisation | 7.4
| <methodOfConductingTxn> | (1) | N | methodOfConductingTxn | 7.6
| <transaction> | (1) | N | transaction | 7.8
| <recipient> | (1..*) | Y | recipient | 7.7
| <isOtherDsProviderInvolved> | (1) | N | YesNo | 9.55
| <otherDsProvider> | (0..*) | Y | otherDsProvider | 7.13

### 7.1.1. Used within

<ttrList> (6.1)

### 7.1.2. Description

The purpose of this element is to record details (i.e. make a report) of a threshold transaction.

Notes:

1. There are two (2) choices to describe how the transaction was conducted:

   1. Use the <otherPerson> <representedOrganisation> sequence when an individual has conducted the transaction; or

   2. Use <methodOfConductingTxn> when a transaction is conducted using a type of deposit service where it is not possible to determine who conducted the transaction or when a payroll or cash courier service is used to conduct the transaction.

Use a separate <ttr> element for each TTR report to be reported to AUSTRAC.

### 7.1.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 7.1.4. Child elements

`<header>`

  Report administration or handling information.

  See also: <header> (7.2)

`<lppDetails>`

  Legal professional privilege (LPP) protects certain confidential communications between lawyers and their clients from being disclosed, including when making a report to AUSTRAC.

  For more information about LPP, when it applies and how to claim it, refer to the LPP guidance.

  LPP details include an indicator of whether or not a LPP claim applies and a means to attach a LPP form to this report if there is a claim.

  See also: LppDetails (8.24)

`<customer>`

  Provide details of the customer.

  Use a separate <customer> element for each customer involved in the threshold transaction.

  See also: <customer> (7.3)

`<otherPerson>`

  Provide details of any other person involved in the transaction. This could be someone acting on behalf of the customer or a third party making a payment into the customer's account.

  Use a separate <otherPerson> element for each individual conducting the transaction.

  Notes:

  1. The other person cannot be an organisation – it is the person who interacted with the reporting entity in order to carry out the transaction.

  See also: <otherPerson> (7.5)

`<representedOrganisation>`

  If the other person conducting the transaction is doing so on behalf of an organisation, then provide information about that organisation.

  See also: <representedOrganisation> (7.4)

`<methodOfConductingTxn>`

  Provide details of how the transaction was conducted when it cannot be determined who conducted it or when a payroll or cash courier service was involved.

  See also: <methodOfConductingTxn> (7.6)

`<transaction>`

  Provide details of transaction, including the designated service involved, cash amount and overall value of the transaction.

  See also: <transaction> (7.8)

`<recipient>`

  Provide details of the recipient.

  Use a separate <recipient> element for each recipient involved in the threshold transaction.

  See also: <recipient> (7.7)

`<isOtherDsProviderInvolved>`

  Indicate if there are any other designated service providers involved in the transaction.

  See also: YesNo (9.55)

`<otherDsProvider>`

  Details of other designated service provider(s) are expected to be provided if involved in the transaction.

  See also: <otherDsProvider> (7.13)

## global element7.2. <header>

<header> | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – |  | <interceptFlag> | (0..1) | N | YesNo | 9.55
| <specialReportingActivityId> | (0..1) | N | SpecialReportingActivityId | 9.47

### 7.2.1. Used within

<ttr> (7.1)

### 7.2.2. Description

The purpose of this element is to record report administration details, such as give instructions to AUSTRAC on how to handle the report, if need be.

### 7.2.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 7.2.4. Child elements

`<interceptFlag>`

  An optional flag that, when present, will cause this report to be intercepted by AUSTRAC Online prior to submission to AUSTRAC.

  The report will be available for reviewing and editing in the intercepted reports queue of the report dashboard under the AUSTRAC Online user who submitted the XML document. Once the intercepted report has been reviewed and/or amended, it can be submitted to AUSTRAC.

  This element is useful for when a legal professional privilege claim form has not been embedded as an attachment in the XML document and needs to be added to the report prior to submission to AUSTRAC. Refer to the "About this form" section on the single report form in AUSTRAC Online and Section 8.24, “LppDetails”.

  Omit this element if the report does not need to be manually reviewed in AUSTRAC Online.

  See also: YesNo (9.55)

`<specialReportingActivityId>`

  An optional identification reference that has been pre-arranged with AUSTRAC to signify this report is part of coordinated activity.

  Omit this element if the report is not part of a pre-arranged activity.

  See also: SpecialReportingActivityId (9.47)

## global element7.3. <customer>

<customer> | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – | choice – (0..1) |  | <individualDetails> | (1) | N | IndividualDetails | 8.23
| <organisationDetails> | (1) | N | OrganisationDetails | 8.29
| <isAccountInvolved> | (0..1) | N | YesNo | 9.55
| <account> | (0..*) | Y | Account | 8.1
| <isOnlineActivityIdentified> | (0..1) | N | YesNo | 9.55
| <onlineActivity> | (0..*) | Y | OnlineActivity | 8.26

Notes:

### 7.3.1. Used within

<ttr> (7.1)

### 7.3.2. Description

Provide details of the individual or organisation, who is a customer of the reporting entity for the designated service involved in the threshold transaction. There may be more than one customer depending on the designated service.

Use a separate <customer> element for each customer.

This element corresponds to the "Customer(s)" section on the single report form.

Notes:

1. Customer is the customer of the designated service as defined in section 6 of the AML/CTF Act.
2. There are two (2) choices to describe and provide details relating to the customer:

   1. <individualDetails> for individuals, and

   2. <organisationDetails> for organisations, such as companies, partnerships, associations, etc.

### 7.3.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 7.3.4. Child elements

`<individualDetails>`

  Provide the individual's full name, any other names they are known by, date of birth, gender, countries of citizenship, countries of tax residency, contact details, occupation and how the identity of the individual was verified.

  See also: IndividualDetails (8.23)

`<organisationDetails>`

  Provide the organisation's full legal name, other names used by the organisation (e.g. a former name or business name), business identifiers (e.g. ABN, ACN, LEI), countries of incorporation, formation or registration, countries of tax residency, registered office address, contact details, type of business or principal activity, legal form (e.g. company, partnership, trust), details of beneficial owners, details of directors or people with primary responsibility for governance and executive decisions and how the identity of the organisation was verified.

  If the organisation is an express trust, additional details about the trust are also required. Refer to Section 8.29, “OrganisationDetails” for details.

  See also: OrganisationDetails (8.29)

`<isAccountInvolved>`

  Indicate if the customer’s account or wallet was involved in the transaction.

  See also: YesNo (9.55)

`<account>`

  Details of the customer’s accounts or wallets must be provided, if involved in the transaction.

  Use a separate <account> element for each account or wallet involved in the transaction.

  See also: Account (8.1)

`<isOnlineActivityIdentified>`

  Indicate if the network/device identifiers associated with the customer’s online activity are known.

  See also: YesNo (9.55)

`<onlineActivity>`

  Details of the customer's online activity, if the transaction or designated service was provided online and these details are captured by your systems.

  Use a separate <onlineActivity> element for each network/device used by the customer.

  See also: OnlineActivity (8.26)

## global element7.4. <representedOrganisation>

<representedOrganisation> | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – |  | <organisationDetails> | (1) | N | OrganisationDetails | 8.29

### 7.4.1. Used within

<ttr> (7.1)

### 7.4.2. Description

Provide details of the organisation represented by the other person, <otherPerson>, for the purpose of conducting the transaction.

### 7.4.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 7.4.4. Child elements

`<organisationDetails>`

  Provide the organisation's full legal name, other names used by the organisation (e.g. a former name or business name), business identifiers (e.g. ABN, ACN, LEI), countries of incorporation, formation or registration, countries of tax residency, registered office address, contact details, type of business or principal activity, legal form (e.g. company, partnership, trust), details of beneficial owners, details of directors or people with primary responsibility for governance and executive decisions and how the identity of the organisation was verified.

  The level of detail is to the extent the information is known.

  See also: OrganisationDetails (8.29)

## global element7.5. <otherPerson>

<otherPerson> | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
choice – (0..1) |  | <sameAsCustomer> | (1) | N | PartyReference | 8.31
sequence – |  | <customerEmployee> | (1) | N | PartyReference | 8.31
| <individualDetails> | (1) | N | IndividualDetails | 8.23
| <isOnlineActivityIdentified> | (0..1) | N | YesNo | 9.55
| <onlineActivity> | (0..*) | Y | OnlineActivity | 8.26
| <isAuthorisationUsed> | (1) | N | YesNo | 9.55
| <agencyAuthorisation> | (0..*) | Y | AgencyAuthorisation | 8.9
sequence – |  | <individualDetails> | (1) | N | IndividualDetails | 8.23
| <isOnlineActivityIdentified> | (0..1) | N | YesNo | 9.55
| <onlineActivity> | (0..*) | Y | OnlineActivity | 8.26
| <isRepresentingOrganisation> | (1) | N | YesNo | 9.55
| <representsOrganisation> | (0..1) | Y | PartyReference | 8.31
| <isAuthorisationUsed> | (1) | N | YesNo | 9.55
| <agencyAuthorisation> | (0..*) | Y | AgencyAuthorisation | 8.9

### 7.5.1. Used within

<ttr> (7.1)

### 7.5.2. Description

Provide details of other persons involved in the transaction.

This element corresponds to the "Other person(s)" section on the single report form.

Notes:

1. Other persons involved in the transaction cannot be an organisation – it is the individual who interacted with the reporting entity to carry out the transaction.
2. When the other person is representing an organisation for the purpose of conducting the transaction provide details of that organisation by using the <isRepresentingOrganisation><representsOrganisation> sequence. This sequence is not needed for employees of the customer as the employee is representing the customer.
3. There are three (3) choices to describe the other person:

   1. Use <sameAsCustomer> when the customer conducted the transaction.

   2. Use the sequence <customerEmployee> <individualDetails> <isOnlineActivityIdentified> <onlineActivity> <isAuthorisationUsed> <agencyAuthorisation> when an employee of the customer conducted the transaction on behalf of their employer.

   3. Use the <individualDetails> <isOnlineActivityIdentified> <onlineActivity> <isRepresentingOrganisation> <representsOrganisation> <isAuthorisationUsed> <agencyAuthorisation> sequence when the other person is a third party to the transaction. That is, this individual is neither the customer nor an employee of the customer.

### 7.5.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 7.5.4. Child elements

`<sameAsCustomer>`

  If the other person, being the person who conducted the transaction, is the same as one of the customers of the threshold transaction then identify which customer by using the <sameAsCustomer> element. For example:

  >       :
  >     <customer id="cust-111">
  >       :
  >     </customer>
  >     <otherPerson id="ind-222">
  >       <sameAsCustomer refId="cust-111"/>
  >     </otherPerson>
  >       :

  See also: PartyReference (8.31)

`<customerEmployee>`

  If the other person is an employee of one of the customers of the threshold transaction then identify which customer by using the <customerEmployee> element. For example:

  >       :
  >         <customer id="cust-111">
  >         :
  >         </customer>
  >         <otherPerson id="ind-222">
  >         <customerEmployee refId="cust-111"/>
  >         <individualDetails>
  >         <fullName> ... </fullName>
  >         </individualDetails>
  >         :
  >         </otherPerson>
  >         :

  See also: PartyReference (8.31)

`<individualDetails>`

  Details of the third party who is not the customer or an employee of the customer.

  Provide the individual's full name, any other names they are known by, date of birth, gender, countries of citizenship, countries of tax residency, contact details, occupation and how the identity of the individual was verified.

  See also: IndividualDetails (8.23)

`<isOnlineActivityIdentified>`

  Indicate if the network/device identifiers associated with the individual’s online activity are known.

  See also: YesNo (9.55)

`<onlineActivity>`

  Details of the person's online activity, if the transaction or designated service was provided online and these details are captured by your systems.

  Use a separate <onlineActivity> element for each network/device used by the person.

  See also: OnlineActivity (8.26)

`<isAuthorisationUsed>`

  Indicate if the other person was authorised to act on behalf of the customer.

  See also: YesNo (9.55)

`<agencyAuthorisation>`

  If authorised to act on behalf of the customer, provide a description of the authority used by the other person.

  Use a separate <agencyAuthorisation> element to identify each authority.

  For example:

  >       :
  >         <customer id="cust-111"> ... </customer>
  >         <customer id="cust-222"> ... </customer>
  >         <otherPerson id="ind-333">
  >         :
  >         <agencyAuthorisation refId="cust-111">Trust deed</agencyAuthorisation>
  >         <agencyAuthorisation refId="cust-222">Power of attorney</agencyAuthorisation>
  >         </otherPerson>
  >         :

  See also: AgencyAuthorisation (8.9)

`<individualDetails>`

  Details of the third party who is not the customer or an employee of the customer.

  Provide the individual's full name, any other names they are known by, date of birth, gender, countries of citizenship, countries of tax residency, contact details, occupation and how the identity of the individual was verified.

  See also: IndividualDetails (8.23)

`<isOnlineActivityIdentified>`

  Indicate if the network/device identifiers associated with the individual’s online activity are known.

  See also: YesNo (9.55)

`<onlineActivity>`

  Details of the person's online activity, if the transaction or designated service was provided online and these details are captured by your systems.

  Use a separate <onlineActivity> element for each network/device used by the person.

  See also: OnlineActivity (8.26)

`<isRepresentingOrganisation>`

  Indicate if this individual represents an organisation, other than the customer, for the purpose of conducting the transaction.

  See also: YesNo (9.55)

`<representsOrganisation>`

  Provide details of the organisation the other person (the third party) represents.

  >       :
  >         <representedOrganisation id="org-222">
  >         <organisationDetails>
  >         <fullLegalName> ... </fullLegalName>
  >         </organisationDetails>
  >         :
  >         </representedOrganisation>
  >         <otherPerson id="ind-333">
  >         <individualDetails>
  >         <fullName> ... </fullName>
  >         </individualDetails>
  >         :
  >         <isRepresentingOrganisation>Y</isRepresentingOrganisation>
  >         <representsOrganisation refId="org-222"/>
  >         </otherPerson>
  >         :

  See also: PartyReference (8.31)

`<isAuthorisationUsed>`

  Indicate if the other person was authorised to act on behalf of the customer.

  See also: YesNo (9.55)

`<agencyAuthorisation>`

  If authorised to act on behalf of the customer, provide a description of the authority used by the other person.

  Use a separate <agencyAuthorisation> element to identify each authority.

  For example:

  >       :
  >         <customer id="cust-111"> ... </customer>
  >         <customer id="cust-222"> ... </customer>
  >         <otherPerson id="ind-333">
  >         :
  >         <agencyAuthorisation refId="cust-111">Trust deed</agencyAuthorisation>
  >         <agencyAuthorisation refId="cust-222">Power of attorney</agencyAuthorisation>
  >         </otherPerson>
  >         :

  See also: AgencyAuthorisation (8.9)

## global element7.6. <methodOfConductingTxn>

<methodOfConductingTxn> | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
choice – |  | <method> | (1) | N | TransactionMethod | 9.53
| <otherMethod> | (1) | N | Description | 9.24

### 7.6.1. Used within

<ttr> (7.1)

### 7.6.2. Description

The purpose of this element is to provide the type of deposit service used when it is not possible to determine who conducted the transaction (i.e. the customer or another person) or when a payroll or cash courier service was involved.

Notes:

1. There are two (2) choices to describe how the transaction was conducted:

   1. Use <method> when there is a predefined descriptor that describes how the transaction was conducted; or

   2. Use <otherMethod> when there is no predefined descriptor which adequately describes how the transaction was conducted.

### 7.6.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 7.6.4. Child elements

`<method>`

  Use one of the predefined values to indicate how the transaction was conducted when it could not be determined who conducted it.

  See also: TransactionMethod (9.53)

`<otherMethod>`

  Describe, if none of the predefined values are adequate, how the transaction was conducted when it could not be determined who conducted it.

  See also: Description (9.24)

## global element7.7. <recipient>

<recipient> | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
choice – (0..1) |  | <sameAsCustomer> | (1) | N | PartyReference | 8.31
sequence – |  | <sameAsOtherPerson> | (1) | N | PartyReference | 8.31
| <isAccountInvolved> | (0..1) | N | YesNo | 9.55
| <account> | (0..*) | N | Account | 8.1
sequence – |  | <sameAsRepresentedOrganisation> | (1) | N | PartyReference | 8.31
| <isAccountInvolved> | (0..1) | N | YesNo | 9.55
| <account> | (0..*) | Y | Account | 8.1
| <isSameAsReportingEntity> | (1) | N | YesNo | 9.55
sequence – | choice – (0..1) |  | <individualDetails> | (1) | N | IndividualDetails | 8.23
| <organisationDetails> | (1) | N | OrganisationDetails | 8.29
| <isAccountInvolved> | (0..1) | N | YesNo | 9.55
| <account> | (0..*) | Y | Account | 8.1

Notes:

### 7.7.1. Used within

<ttr> (7.1)

### 7.7.2. Description

Provide details of a person or organisation who is a beneficiary or who is to receive a payment (i.e. a recipient) in relation to the threshold transaction.

This element corresponds to the "Recipient(s)" section on the single report form.

Notes:

1. There are five (5) choices to describe the recipient:

   1. <sameAsCustomer> – use this when the recipient is the customer.

   2. <sameAsOtherPerson> – use this sequence when the recipient is the other person who conducted the transaction.

   3. <sameAsRepresentedOrganisation> – use this sequence when the recipient is the organisation represented by the other person.

   4. <isSameAsReportingEntity> – use this when the recipient is your business (i.e. the reporting entity).

   5. <individualDetails> or <organisationDetails> – use this sequence when the recipient is a completely different party from the customer, other person, the organisation represented by the other person or reporting entity.

2. For each of the choices with sequences, indicate if that recipient's accounts or wallets were involved in the transaction and provide the relevant details, if applicable.

### 7.7.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 7.7.4. Child elements

`<sameAsCustomer>`

  If a customer is the recipient, indicate which customer is a recipient by setting the `refId` attribute to the value of the `id` attribute of that customer. For example:

  >       :
  >     <customer id="cust-111">
  >       :
  >     </customer>
  >       :
  >     <recipient id="recp-333">
  >       <sameAsCustomer refId="cust-111"/>
  >     </recipient>
  >       :

  See also: PartyReference (8.31)

`<sameAsOtherPerson>`

  If the other person involved in the transaction is the recipient, indicate which person is a recipient by setting the `refId` attribute to the value of the `id` attribute of that individual.

  For example:

  >       :
  >     <otherPerson id="ind-222">
  >       :
  >     </otherPerson>
  >     <recipient id="recp-333">
  >       <sameAsOtherPerson refId="ind-222"/>
  >     </recipient>
  >       :

  See also: PartyReference (8.31)

`<isAccountInvolved>`

  Indicate if the recipient’s account or wallet was involved in the transaction.

  See also: YesNo (9.55)

`<account>`

  Details of the recipient’s accounts or wallets must be provided, if involved in the transaction.

  Use a separate <account> element for each account or wallet involved in the transaction.

  See also: Account (8.1)

`<sameAsRepresentedOrganisation>`

  If an organisation represented by a person is the recipient, indicate which organisation by setting the `refId` attribute to the value of the `id` attribute of that organisation.

  For example:

  >       :
  >     <customer id="cust-111">
  >       <fullName>Jack Brown</fullName>
  >       :
  >     </customer>
  >     <representedOrganisation id="org-222">
  >       <fullLegalName>Apex Examples Pty Ltd</fullLegalName>
  >       :
  >     </representedOrganisation>
  >     <otherPerson id="ind-333">
  >       <fullName>Jane Smith</fullName>
  >       :
  >       <representsOrganisation refId="org-222"/>
  >     </otherPerson>
  >     <recipient id="recp-444">
  >       <sameAsRepresentedOrganisation refId="org-222"/>
  >     </recipient>
  >       :

  See also: PartyReference (8.31)

`<isAccountInvolved>`

  Was the recipient’s account or wallet involved in the transaction?

  See also: YesNo (9.55)

`<account>`

  Details of the recipient’s account(s), if involved in the transaction.

  Use a separate <account> element for each account involved in the transaction.

  See also: Account (8.1)

`<isSameAsReportingEntity>`

  Indicate if the reporting entity is the recipient

  See also: YesNo (9.55)

`<individualDetails>`

  If the recipient is an individual, provide the individual's full name, any other names they are known by, date of birth, gender, countries of citizenship, countries of tax residency, contact details, occupation and how the identity of the individual was verified.

  See also: IndividualDetails (8.23)

`<organisationDetails>`

  If the recipient is an organisation, provide the organisation's full legal name, other names used by the organisation (e.g. a former name or business name), business identifiers (e.g. ABN, ACN, LEI), countries of incorporation, formation or registration, countries of tax residency, registered office address, contact details, type of business or principal activity, legal form (e.g. company, partnership, trust), details of beneficial owners, details of directors or people with primary responsibility for governance and executive decisions and how the identity of the organisation was verified.

  See also: OrganisationDetails (8.29)

`<isAccountInvolved>`

  Was the recipient’s account or wallet involved in the transaction?

  See also: YesNo (9.55)

`<account>`

  Provide details of the recipient's account(s) involved in the threshold transaction, held with or known by the reporting entity.

  Use a separate <account> element for each account.

  See also: Account (8.1)

## global element7.8. <transaction>

<transaction> | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – |  | <designatedService> | (1) | N | DesignatedSvc | 9.25
| <txnLocation> | (1) | N | AddressOrLocation | 8.8
| <txnDate> | (1) | N | Date | 9.21
| <txnTime> | (0..1) | N | Time | 9.52
| <txnRefNo> | (1) | N | TRN | 9.50
| <txnPurpose> | (0..1) | N | Description | 9.24
| <physicalCurrencyDirection> | (1) | N | PhysicalCurrencyDirection | 9.39
| <moneyReceived> | (1) | N | moneyReceived | 7.9
| <moneyProvided> | (1) | N | moneyProvided | 7.11
| <totalAmount> | (1) | N | AudAmount | 8.11

### 7.8.1. Used within

<ttr> (7.1)

### 7.8.2. Description

Provide details of the threshold transaction.

This element corresponds to the "Transaction details" on the single report form.

### 7.8.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 7.8.4. Child elements

`<designatedService>`

  The designated service to which the threshold transaction relates.

  See also: DesignatedSvc (9.25)

`<txnLocation>`

  Provide the address or location where the transaction took place (e.g. an office of the reporting entity, an offsite location).

  See also: AddressOrLocation (8.8)

`<txnDate>`

  The date when the transaction or activity took place.

  See also: Date (9.21)

`<txnTime>`

  The time of the date of when the transaction or activity took place.

  See also: Time (9.52)

`<txnRefNo>`

  Provide a unique reference number or identification code for the threshold transaction.

  See also: TRN (9.50)

`<txnPurpose>`

  Provide a description of the purpose of the transaction.

  See also: Description (9.24)

`<physicalCurrencyDirection>`

  Indicate if physical currency was received (or exchanged) or provided.

  See also: PhysicalCurrencyDirection (9.39)

`<moneyReceived>`

  Description of money or value received from the customer or the other person.

  See also: <moneyReceived> (7.9)

`<moneyProvided>`

  Description of the money or value provided to or invested for the customer or recipient.

  See also: <moneyProvided> (7.11)

`<totalAmount>`

  Total transaction value (including cash and any other value) expressed in Australian dollars.

  See also: AudAmount (8.11)

## global element7.9. <moneyReceived>

<moneyReceived> | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – |  | <cash> | (0..1) | N | cash | 7.14
| <otherMoneyReceived> | (0..1) | N | otherMoneyReceived | 7.10

### 7.9.1. Used within

<transaction> (7.8)

### 7.9.2. Description

The <moneyReceived> and <moneyProvided> elements are used to quantitatively describe each component of the transaction in the exchange of money/value that took place between the reporting entity and the customer (or parties) involved in the transaction.

The purpose of the <moneyReceived> element is to describe each component (i.e. cash, virtual assets and other products or instruments, including property) of the transaction along with its value, received by the reporting entity from the customer(s) or parties involved in the transaction. The value of its components should be compared against the value of the <moneyProvided> components to reconcile the transaction (i.e. this is analogous to double entry bookkeeping to describe purpose through the debit and credit entries associated with the transaction).

### 7.9.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 7.9.4. Child elements

`<cash>`

  Value of physical currency (i.e. notes and coins) received from the customer (or other person), if any.

  See also: <cash> (7.14)

`<otherMoneyReceived>`

  Details of each component other than cash that has a value (e.g. products or instruments such as cheques, virtual assets, property) received from the customer (or other person), if any.

  See also: <otherMoneyReceived> (7.10)

## global element7.10. <otherMoneyReceived>

<otherMoneyReceived> | Attribute/child-element | Occurrence | Assert | Type | Section
sequence – |  | <dci> | (0..*) | N | TTRVirtualAsset | 8.37
| <bui> | (0..*) | N | Bullion | 8.14
| <pmi> | (0..*) | N | PreciousMetal | 8.33
| <psi> | (0..*) | N | PreciousStone | 8.35
| <ppi> | (0..*) | N | PreciousProduct | 8.34
| <rdi> | (0..*) | N | RealEstate | 8.36
| <rsi> | (0..*) | N | RealEstate | 8.36
| <bci> | (0..*) | N | CurrencyAmount | 8.15
| <bdi> | (0..*) | N | CurrencyAmount | 8.15
| <bpi> | (0..1) | N | CurrencyAmount | 8.15
| <cbi> | (0..1) | N | CurrencyAmount | 8.15
| <chi> | (0..*) | N | CurrencyAmount | 8.15
| <cri> | (0..1) | N | CurrencyAmount | 8.15
| <dfi> | (0..1) | N | CurrencyAmount | 8.15
| <dti> | (0..1) | N | CurrencyAmount | 8.15
| <egi> | (0..1) | N | CurrencyAmount | 8.15
| <esi> | (0..1) | N | CurrencyAmount | 8.15
| <fai> | (0..1) | N | CurrencyAmount | 8.15
| <gci> | (0..1) | N | CurrencyAmount | 8.15
| <iti> | (0..1) | N | CurrencyAmount | 8.15
| <ldi> | (0..1) | N | CurrencyAmount | 8.15
| <moi> | (0..*) | N | CurrencyAmount | 8.15
| <ndi> | (0..1) | N | CurrencyAmount | 8.15
| <oci> | (0..1) | N | CurrencyAmount | 8.15
| <oti> | (0..*) | N | CurrencyAmountOther | 8.16
| <pdi> | (0..1) | N | CurrencyAmount | 8.15
| <sei> | (0..1) | N | CurrencyAmount | 8.15
| <svi> | (0..1) | N | CurrencyAmount | 8.15
| <tci> | (0..*) | N | CurrencyAmount | 8.15
| <wti> | (0..1) | N | CurrencyAmount | 8.15

### 7.10.1. Used within

<moneyReceived> (7.9)

### 7.10.2. Description

Details of component(s) other than cash received (or purchased) from the customer (or other person), if any.

See also Appendix B, "Other money received" transaction type

### 7.10.3. Child elements

`<dci>`

  Details and value of virtual assets received from the customer (or other person), if any.

  Use a separate <dci> element for each Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.virtual asset.

  See also: TTRVirtualAsset (8.37)

`<bui>`

  Details and value of bullion received from the customer (or other person), if any.

  Use a separate <bui> element for each type of bullion.

  See also: Bullion (8.14)

`<pmi>`

  Details and value of precious metals received from the customer (or other person), if any.

  Use a separate <pmi> element for each type of precious metal.

  See also: PreciousMetal (8.33)

`<psi>`

  Details and value of precious stones received from the customer (or other person), if any.

  Use a separate <psi> element for each type of precious stone.

  See also: PreciousStone (8.35)

`<ppi>`

  Details and value of precious products received from the customer (or other person), if any.

  Use a separate <ppi> element for each type of precious product.

  See also: PreciousProduct (8.34)

`<rdi>`

  Deposit paid out for real estate - the deposit amount paid out in relation to the sale of real estate and description of the property, if any.

  Use a separate <rdi> element for each property.

  See also: RealEstate (8.36)

`<rsi>`

  Settlement paid out for real estate - the settlement amount paid out in relation to the sale of real estate and description of the property, if any.

  Use a separate <rdi> element for each property.

  See also: RealEstate (8.36)

`<bci>`

  Bank cheques – aggregate value by currency of all bank cheques received, if any.

  Use a separate <bci> element for each aggregate currency value of bank cheques received, e.g. one <bci> element for an aggregate value in Australia dollars and another <bci> for US dollars, etc.

  See also: CurrencyAmount (8.15)

`<bdi>`

  Bank drafts – aggregate value by currency of all bank drafts received, if any.

  Use a separate <bdi> element for each aggregate currency value of bank drafts received, e.g. one <bdi> element for an aggregate value in Australia dollars and another <bdi> for US dollars, etc.

  See also: CurrencyAmount (8.15)

`<bpi>`

  Benefit payment/payout – aggregate value of all benefit payment(s)/payout(s) received, if any.

  See also: CurrencyAmount (8.15)

`<cbi>`

  Make payments on behalf of a customer (asset management) – aggregate value of payments made on behalf of a customer, if any.

  See also: CurrencyAmount (8.15)

`<chi>`

  Cheques – aggregate value by currency of all personal and business cheques received, if any.

  Use a separate <chi> element for each aggregate currency value of cheques received, e.g. one <chi> element for an aggregate value in Australia dollars and another <chi> for US dollars, etc.

  See also: CurrencyAmount (8.15)

`<cri>`

  Premium player commission/rebate (betting services) – aggregate value of all premium player commission(s)/rebate(s) received, if any.

  See also: CurrencyAmount (8.15)

`<dfi>`

  Derivatives/futures – aggregate value of all derivatives/futures received, if any.

  See also: CurrencyAmount (8.15)

`<dti>`

  Domestic value transfer received – aggregate value of all domestic funds transfers received, if any.

  See also: CurrencyAmount (8.15)

`<egi>`

  Electronic gaming machine collect – aggregate value of the customer’s win through electronic gaming machine collect(s), if any.

  See also: CurrencyAmount (8.15)

`<esi>`

  Disburse funds in escrow (asset management) – aggregate value of all the customer’s funds disbursed from escrow, if any.

  See also: CurrencyAmount (8.15)

`<fai>`

  Funds from account – aggregate value of all funds withdrawn from the customer's accounts or wallets, if any.

  See also: CurrencyAmount (8.15)

`<gci>`

  Gambling chips/tokens – aggregate value of the customer’s gambling chips/tokens to be redeemed or exchanged, if any.

  See also: CurrencyAmount (8.15)

`<iti>`

  International funds transfer – aggregate value of all international funds transfers received, if any.

  See also: CurrencyAmount (8.15)

`<ldi>`

  Loan drawdown – aggregate value of all loans drawn down or provided, if any.

  See also: CurrencyAmount (8.15)

`<moi>`

  Money/postal orders – aggregate value by currency of all money/postal orders received, if any.

  Use a separate <moi> element for each aggregate currency value of money/postal orders received, e.g. one <moi> element for an aggregate value in Australia dollars and another <moi> for US dollars, etc.

  See also: CurrencyAmount (8.15)

`<ndi>`

  Negotiable debt instruments (factoring, forfeiting, dealing in bills of exchange, promissory notes or letters of credit, redeeming bearer bond) – aggregate value of all negotiable debt instruments received, if any.

  See also: CurrencyAmount (8.15)

`<oci>`

  Other casino prize – aggregate value of other casino prize(s), if any.

  See also: CurrencyAmount (8.15)

`<oti>`

  Other (must include description) – value of any other component of value not covered by the predefined <otherMoneyReceived> options, if any.

  Multiple values may be aggregated if they are identical in nature. Otherwise, use a separate <oti> element for each unique component.

  See also: CurrencyAmountOther (8.16)

`<pdi>`

  Disburse property to purchase an asset (asset management) – aggregate value of all disbursed property to purchase an asset, if any.

  See also: CurrencyAmount (8.15)

`<sei>`

  Securities – aggregate value of all securities received, if any.

  See also: CurrencyAmount (8.15)

`<svi>`

  Stored value cards – aggregate value of all funds/value received from stored value cards, if any.

  See also: CurrencyAmount (8.15)

`<tci>`

  Traveller’s cheques – aggregate value of all traveller’s cheques received, if any.

  Use a separate <tci> element for each aggregate currency value of traveller's cheques received, e.g. one <tci> element for an aggregate value in Australia dollars and another <tci> for US dollars, etc.

  See also: CurrencyAmount (8.15)

`<wti>`

  Winning tickets (wagering) – aggregate value of the winning tickets received, if any.

  See also: CurrencyAmount (8.15)

## global element7.11. <moneyProvided>

<moneyProvided> | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – |  | <cash> | (0..1) | N | cash | 7.14
| <otherMoneyProvided> | (0..1) | N | otherMoneyProvided | 7.12

### 7.11.1. Used within

<transaction> (7.8)

### 7.11.2. Description

The <moneyReceived> and <moneyProvided> elements are used to quantitatively describe each component of the transaction in the exchange of money/value that took place between the reporting entity and the customer (or parties) involved in the transaction.

The purpose of the <moneyProvided> element is to describe each component (i.e. cash, virtual assets and other products or instruments, including property) of the transaction along with its value, provided by the reporting entity to the customer(s) or parties involved in the transaction. The value of its components should be compared against the value of the <moneyReceived> components to reconcile the transaction (i.e. this is analogous to double entry bookkeeping to describe purpose through the debit and credit entries associated with the transaction).

### 7.11.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 7.11.4. Child elements

`<cash>`

  Value of physical currency (i.e. notes and coins) provided to the customer (or recipient), if any.

  See also: <cash> (7.14)

`<otherMoneyProvided>`

  Details of each component other than cash that has a value (e.g. products or instruments such as cheques, virtual assets, property) provided to the customer (or recipient), if any.

  See also: <otherMoneyProvided> (7.12)

## global element7.12. <otherMoneyProvided>

<otherMoneyProvided> | Attribute/child-element | Occurrence | Assert | Type | Section
sequence – |  | <dco> | (0..*) | N | TTRVirtualAsset | 8.37
| <buo> | (0..*) | N | Bullion | 8.14
| <pmo> | (0..*) | N | PreciousMetal | 8.33
| <pso> | (0..*) | N | PreciousStone | 8.35
| <ppo> | (0..*) | N | PreciousProduct | 8.34
| <rdo> | (0..*) | N | RealEstate | 8.36
| <rso> | (0..*) | N | RealEstate | 8.36
| <cvo> | (0..*) | N | RealEstate | 8.36
| <rho> | (0..*) | N | RealEstate | 8.36
| <bao> | (0..1) | N | CurrencyAmount | 8.15
| <bco> | (0..*) | N | CurrencyAmount | 8.15
| <bdo> | (0..*) | N | CurrencyAmount | 8.15
| <beo> | (0..1) | N | CurrencyAmount | 8.15
| <bio> | (0..1) | N | CurrencyAmount | 8.15
| <blo> | (0..1) | N | CurrencyAmount | 8.15
| <bmo> | (0..1) | N | CurrencyAmount | 8.15
| <bno> | (0..1) | N | CurrencyAmount | 8.15
| <boo> | (0..1) | N | CurrencyAmount | 8.15
| <bpo> | (0..1) | N | CurrencyAmount | 8.15
| <bro> | (0..1) | N | CurrencyAmount | 8.15
| <bto> | (0..1) | N | CurrencyAmount | 8.15
| <bwo> | (0..1) | N | CurrencyAmount | 8.15
| <cho> | (0..*) | N | CurrencyAmount | 8.15
| <cpo> | (0..1) | N | CurrencyAmount | 8.15
| <cso> | (0..1) | N | CurrencyAmount | 8.15
| <cto> | (0..1) | N | CurrencyAmount | 8.15
| <dfo> | (0..1) | N | CurrencyAmount | 8.15
| <dto> | (0..1) | N | CurrencyAmount | 8.15
| <edo> | (0..1) | N | CurrencyAmount | 8.15
| <eso> | (0..1) | N | CurrencyAmount | 8.15
| <fao> | (0..1) | N | CurrencyAmount | 8.15
| <fco> | (0..1) | N | CurrencyAmount | 8.15
| <fmo> | (0..1) | N | CurrencyAmount | 8.15
| <gco> | (0..1) | N | CurrencyAmount | 8.15
| <hpo> | (0..1) | N | CurrencyAmount | 8.15
| <ito> | (0..1) | N | CurrencyAmount | 8.15
| <lro> | (0..1) | N | CurrencyAmount | 8.15
| <moo> | (0..*) | N | CurrencyAmount | 8.15
| <mro> | (0..1) | N | CurrencyAmount | 8.15
| <ndo> | (0..1) | N | CurrencyAmount | 8.15
| <nso> | (0..1) | N | CurrencyAmount | 8.15
| <oto> | (0..*) | N | CurrencyAmountOther | 8.16
| <pto> | (0..1) | N | CurrencyAmount | 8.15
| <pxo> | (0..1) | N | CurrencyAmount | 8.15
| <pyo> | (0..1) | N | CurrencyAmount | 8.15
| <seo> | (0..1) | N | CurrencyAmount | 8.15
| <sio> | (0..1) | N | CurrencyAmount | 8.15
| <sto> | (0..1) | N | CurrencyAmount | 8.15
| <tco> | (0..*) | N | CurrencyAmount | 8.15

### 7.12.1. Used within

<moneyProvided> (7.11)

### 7.12.2. Description

Details of component(s) other than cash provided (or sold) to the customer (or recipient), if any.

See also Appendix A, "Other money provided" transaction type

### 7.12.3. Child elements

`<dco>`

  Details and value of virtual assets provided to the customer (or recipient), if any.

  Use a separate <dco> element for each virtual asset.

  See also: TTRVirtualAsset (8.37)

`<buo>`

  Details and value of bullion provided to the customer (or recipient), if any.

  Use a separate <buo> element for each type of bullion.

  See also: Bullion (8.14)

`<pmo>`

  Details and value of precious metals provided to the customer (or recipient), if any.

  Use a separate <pmo> element for each type of precious metal.

  See also: PreciousMetal (8.33)

`<pso>`

  Details and value of precious stones provided to the customer (or recipient), if any.

  Use a separate <pso> element for each type of precious stone.

  See also: PreciousStone (8.35)

`<ppo>`

  Details and value of precious products provided to the customer (or recipient), if any.

  Use a separate <ppo> element for each type of precious product.

  See also: PreciousProduct (8.34)

`<rdo>`

  Deposit payment for real estate - the deposit amount in relation to the sale of real estate and description of the property, if any.

  Use a separate <rdo> element for each property.

  See also: RealEstate (8.36)

`<rso>`

  Settlement payment for real estate - the settlement amount in relation to the sale of real estate and description of the property, if any.

  Use a separate <rso> element for each property.

  See also: RealEstate (8.36)

`<cvo>`

  Conveyancer service - the conveyancing cost in relation to the sale/purchase of real estate and the description of the property, if any.

  Use a separate <rso> element for each property.

  See also: RealEstate (8.36)

`<rho>`

  Hold funds on behalf of a buyer of real estate - the value of funds held in relation to the buyer's purchase of real estate and the description of the property, if any.

  Use a separate <rso> element for each property.

  See also: RealEstate (8.36)

`<bao>`

  Business address – aggregate value of the cost for providing business address services to the customer (or recipient), if any.

  See also: CurrencyAmount (8.15)

`<bco>`

  Bank cheques issued – aggregate value by currency of all bank cheques issued to the customer (or recipient), if any.

  Use a separate <bco> element for each aggregate currency value of bank cheques issued, e.g. one <bco> element for an aggregate value in Australia dollars and another <bco> for US dollars, etc.

  See also: CurrencyAmount (8.15)

`<bdo>`

  Bank drafts issued – aggregate value by currency of all bank drafts issued to the customer (or recipient), if any.

  Use a separate <bdo> element for each aggregate currency value of bank drafts issued, e.g. one <bdo> element for an aggregate value in Australia dollars and another <bdo> for US dollars, etc.

  See also: CurrencyAmount (8.15)

`<beo>`

  Set up/establish a business – aggregate value of the cost to set up/establish a business for the customer (or recipient), if any.

  See also: CurrencyAmount (8.15)

`<bio>`

  Buy in to a game – aggregate value of the customer’s buy in to a game, if any.

  See also: CurrencyAmount (8.15)

`<blo>`

  Administration/liquidation of business – aggregate value of the cost for the administration or liquidation of business(es), if any.

  See also: CurrencyAmount (8.15)

`<bmo>`

  Merger/acquisition – aggregate value of the cost for the merger or acquisition of business(es), if any.

  See also: CurrencyAmount (8.15)

`<bno>`

  Business controlling interest transfer – aggregate value of the cost for transferring the controlling interest in business(es), if any.

  See also: CurrencyAmount (8.15)

`<boo>`

  Act as a company officer or equivalent – aggregate value of the cost of services to act as a company officer or equivalent, if any.

  See also: CurrencyAmount (8.15)

`<bpo>`

  Bet(s) placed – aggregate value of the customer’s bet(s) placed, if any.

  See also: CurrencyAmount (8.15)

`<bro>`

  Restructure a business – aggregate value of the cost to restructure business(es), if any.

  See also: CurrencyAmount (8.15)

`<bto>`

  Business ownership transfer – aggregate value of the cost to transfer business ownership, if any.

  See also: CurrencyAmount (8.15)

`<bwo>`

  Winding up/closure of business – aggregate value of the cost to wind up or close business(es), if any.

  See also: CurrencyAmount (8.15)

`<cho>`

  Cheques issued – aggregate value by currency of all cheques issued, if any.

  Use a separate <cho> element for each aggregate currency value of cheques issued, e.g. one <cho> element for an aggregate value in Australia dollars and another <cho> for US dollars, etc.

  See also: CurrencyAmount (8.15)

`<cpo>`

  Contribution/premium – aggregate value of the cost of all contributions/premiums, if any.

  See also: CurrencyAmount (8.15)

`<cso>`

  Shelf company – aggregate value of the cost of selling shelf company(ies) to the customer (or recipient), if any.

  See also: CurrencyAmount (8.15)

`<cto>`

  Transfer of a shelf company – aggregate value of the cost to transfer shelf company(ies) to the customer (or recipient), if any.

  See also: CurrencyAmount (8.15)

`<dfo>`

  Derivatives/futures – aggregate value of all derivatives/futures provided to the customer (or recipient), if any.

  See also: CurrencyAmount (8.15)

`<dto>`

  Domestic value transfer sent – aggregate value of all domestic value transfers sent on behalf of the customer, if any.

  See also: CurrencyAmount (8.15)

`<edo>`

  Equity or debt financing – aggregate value of the cost to provide equities or debt financing services to the customer, if any.

  See also: CurrencyAmount (8.15)

`<eso>`

  Receive funds in escrow – aggregate value of the funds placed into escrow for the customer, if any.

  See also: CurrencyAmount (8.15)

`<fao>`

  Funds to account – aggregate value of funds deposited to the customer's (or recipient's) accounts or wallets, if any.

  See also: CurrencyAmount (8.15)

`<fco>`

  Fees/charges/commissions – aggregate value of the cost of all fees/charges/commissions paid by the customer for services received, if any.

  See also: CurrencyAmount (8.15)

`<fmo>`

  Receive funds to be managed – aggregate value of all funds to be managed on behalf of the customer, if any.

  See also: CurrencyAmount (8.15)

`<gco>`

  Gambling chips/tokens issued – aggregate value of all gambling chips/tokens issued to the customer, if any.

  See also: CurrencyAmount (8.15)

`<hpo>`

  Hire purchase/finance lease payment – aggregate value of all hire purchase/finance lease payments made by the customer, if any.

  See also: CurrencyAmount (8.15)

`<ito>`

  International value transfer sent – aggregate value of all international value transfers sent on behalf of the customer, if any.

  See also: CurrencyAmount (8.15)

`<lro>`

  Loan repayment – aggregate value of all loan repayments made by the customer, if any.

  See also: CurrencyAmount (8.15)

`<moo>`

  Money/postal orders issued – aggregate value by currency of all money or postal orders issued to the customer (or recipient), if any.

  Use a separate <moo> element for each aggregate currency value of money/postal orders issued, e.g. one <moo> element for an aggregate value in Australia dollars and another <moo> for US dollars, etc.

  See also: CurrencyAmount (8.15)

`<mro>`

  Marker redemption (gambling) – aggregate value of all marker redemption(s) by the customer, if any.

  See also: CurrencyAmount (8.15)

`<ndo>`

  Negotiable debt instruments (dealing in bills of exchange, promissory notes, letters of credit or bearer bonds) – aggregate value of all negotiable debt instruments issued, if any.

  See also: CurrencyAmount (8.15)

`<nso>`

  Act as a nominee shareholder – aggregate value of the cost of service(s) to act as a nominee shareholder, if any.

  See also: CurrencyAmount (8.15)

`<oto>`

  Other (must include description) – value of any other component of value not covered by the predefined <otherMoneyProvided> options, if any.

  Multiple values may be aggregated if they are identical in nature. Otherwise, use a separate <oto> element for each unique component.

  See also: CurrencyAmountOther (8.16)

`<pto>`

  Manage property as a settlor of an express trust – aggregate value of the cost to manage property as a settlor of an express trust, if any.

  See also: CurrencyAmount (8.15)

`<pxo>`

  Act as a power of attorney, partner, trustee or equivalent – aggregate value of the cost to act as a power of attorney, partner, trustee or equivalent, if any.

  See also: CurrencyAmount (8.15)

`<pyo>`

  Prepare payroll – aggregate value of all payroll preparation(s), if any.

  See also: CurrencyAmount (8.15)

`<seo>`

  Securities – aggregate value of all securities provided to the customer (or recipient), if any.

  See also: CurrencyAmount (8.15)

`<sio>`

  Stored value cards issued – aggregate value of all stored value cards issued to the customer (or recipient), if any.

  See also: CurrencyAmount (8.15)

`<sto>`

  Stored value cards topped up – aggregate value of all stored value cards topped up for the customer (or recipient), if any.

  See also: CurrencyAmount (8.15)

`<tco>`

  Traveller’s cheques issued – aggregate value by currency of all traveller’s cheques issued to the customer (or recipient), if any.

  Use a separate <tco> element for each aggregate currency value of traveller's cheques issued, e.g. one <tco> element for an aggregate value in Australia dollars and another <tco> for US dollars, etc.

  See also: CurrencyAmount (8.15)

## global element7.13. <otherDsProvider>

<otherDsProvider> | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – |  | <fullName> | (1) | N | Name | 9.37
| <addressOrLocation> | (0..1) | N | AddressOrLocation | 8.8
| <designatedService> | (0..*) | N | DesignatedSvc | 9.25

### 7.13.1. Used within

<ttr> (7.1)

### 7.13.2. Description

Provide details of other designated service providers involved in the threshold transaction, including their full name, address or location and the designated service(s) they provided in relation to the transaction.

This element corresponds to the "Other designated service provider(s)" section on the single report form.

Examples where other designated services providers could be involved may include:

- which real estate agents, lawyers or conveyancers were involved in a real estate transaction

- a value transfer transaction may involve ordering, intermediary and beneficiary institutions and for remittance network providers this might include their affiliates

- which financial institution or business issued the cheques, bank cheques, bank drafts, money/postal orders or traveller's cheques

- which business issued the bills of exchange, promissory notes or letters credit

### 7.13.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 7.13.4. Child elements

`<fullName>`

  The full name of the other designated service provider involved in the threshold transaction.

  See also: Name (9.37)

`<addressOrLocation>`

  The address or location of the site or workplace of the other designated service provider involved in the transaction.

  See also: AddressOrLocation (8.8)

`<designatedService>`

  List the designated service(s) provided by this other provider in relation to the transaction.

  Use a separate <designatedSvc> element for each designated service.

  See also: DesignatedSvc (9.25)

## global element7.14. <cash>

<cash> | Attribute/child-element | Occurrence | Assert | Type | Section
sequence – |  | <ausCash> | (0..1) | N | AudAmount | 8.11
| <foreignCash> | (0..*) | N | CurrencyAmount | 8.15

### 7.14.1. Used within

<moneyReceived> (7.9), <moneyProvided> (7.11)

### 7.14.2. Description

The purpose of this element is to record the value of cash (i.e. physical currency in the form of notes and coins) received or paid out by the reporting entity as part of the transaction.

### 7.14.3. Child elements

`<ausCash>`

  The total value of Australian currency notes and coins involved in the transaction.

  See also: AudAmount (8.11)

`<foreignCash>`

  The type of foreign currency and value of the foreign currency notes and coins involved in the transaction.

  Use a separate <foreignCash> element for each type of foreign currency.

  See also: CurrencyAmount (8.15)

## Chapter 8. Complex types

This section describes all the globally defined complex types within the schema as well as all their nested elements. Complex types define structures that can have attributes and/or child elements. Nested elements are those that are defined within the context of other parent elements.

## complex type8.1. Account

Account | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – | choice – |  | <type> | (1) | N | AccountType | 9.6
| <typeOther> | (1) | N | Description | 9.24
| <title> | (0..1) | Y | AcctTitle | 9.9
| <bsb> | (0..1) | Y | AcctBSB | 9.7
| <number> | (0..1) | Y | AcctNumber | 9.8
| <proxy> | (0..1) | Y | proxy | 8.2
| <tokenDetails> | (0..1) | Y | AccountTokenDetails | 8.5
| <destinationTagMemo> | (0..1) | Y | destinationTagMemo | 8.3
| <isAccountProvider> | (0..1) | Y | YesNo | 9.55
| <provider> | (0..1) | Y | provider | 8.4
| <cardType> | (0..1) | Y | CardType | 9.18
| <isAccountHolder> | (0..1) | Y | YesNo | 9.55
| <isAccountSignatory> | (0..1) | Y | YesNo | 9.55
| <openedDate> | (0..1) | Y | DateNoTimeZone | 9.22

### 8.1.1. Used within

<customer> (7.3), <recipient> (7.7)

### 8.1.2. Description

This complex type specifies the elements to use to describe account or wallet details based on type, e.g.:

Type | Description
--- | ---
Bank account | A bank account can be described by its account title, BSB (Bank State Branch) of where the account is held and number; and/or by its proxy, such as a PayID (e.g. a mobile number, email address, ABN). If a bank account has a BSB, this number is expected to be provided. Otherwise, the <bsb> element can be omitted.
Card account | A card account can be described by its title (the name on the card), number and card type.
Digital wallet | A digital wallet (such as Apple Pay, WeChat Wallet) can be described by its token and token type.
Virtual asset wallet | The wallet can be described by its wallet address and any destination tag or memo details to indicate who the virtual assets are to be credited to. Not all virtual asset wallets have a destination tag or memo. But where they are used for the transfer of virtual assets this detail is expected to be reported.

If the reporting entity is the account or wallet provider, an indication of who is the account holder, signatory and when the account was opened is also expected.

Notes:

1. There are two (2) choices to describe the type of account or wallet:

   1. Use <type> when there is a predefined account or wallet type; or

   2. Use <typeOther> to provide a description when the predefined types do not adequately describe the type of account or wallet.

### 8.1.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.1.4. Child elements

`<type>`

  Type of account or wallet.

  See also: AccountType (9.6)

`<typeOther>`

  Provide a description of the account or wallet if one of the predefined types (listed in Section 9.6, “AccountType”) is not adequate. Do not use product or brand names to describe the account or wallet type.

  See also: Description (9.24)

`<title>`

  The title or name of the account or wallet.

  See also: AcctTitle (9.9)

`<bsb>`

  The Australian Bank State Branch (BSB) number of where the account is held, if applicable.

  See also: AcctBSB (9.7)

`<number>`

  The account number or virtual asset wallet address.

  See also: AcctNumber (9.8)

`<proxy>`

  PayID or other account proxy.

  See also: Account<proxy> (8.2)

`<tokenDetails>`

  If the card is tokenised, the token can be an acquirer or issuer (or other) token.

  The token may represent a payment card or a digital wallet.

  See also: AccountTokenDetails (8.5)

`<destinationTagMemo>`

  A destination tag or memo is an additional virtual asset wallet address attribute to identify the customer or recipient of a transfer to a shared wallet address on some centralised exchanges and/or for some types of virtual assets, such as Ripple (XRP), Stellar (XLM), Hedera (HBAR), etc.

  See also: Account<destinationTagMemo> (8.3)

`<isAccountProvider>`

  Indicate if your business is the account or wallet provider.

  See also: YesNo (9.55)

`<provider>`

  Provide the name of account or wallet provider, if known.

  See also: Account<provider> (8.4)

`<cardType>`

  For card account, indicated the type of card, e.g. credit card, debit card, stored value card.

  See also: CardType (9.18)

`<isAccountHolder>`

  Indicate if the individual or organisation linked to this account is an account holder.

  See also: YesNo (9.55)

`<isAccountSignatory>`

  Indicate if the individual linked to this account is an account signatory.

  See also: YesNo (9.55)

`<openedDate>`

  The date when this account was opened.

  See also: DateNoTimeZone (9.22)

## nested simple element8.2. Account<proxy>

### 8.2.1. Used within

Account (8.1)

### 8.2.2. Description

Asserted

### 8.2.3. Restrictions

Base type:

  xs:token

Maximum length:

  140

  See also: xs:maxLength (W3C XSD specification)

## nested simple element8.3. Account<destinationTagMemo>

### 8.3.1. Used within

Account (8.1)

### 8.3.2. Description

Asserted

### 8.3.3. Restrictions

Base type:

  xs:token

Pattern:

  [0-9a-zA-Z]{0,140}

  See also: xs:pattern (W3C XSD specification)

## nested simple element8.4. Account<provider>

### 8.4.1. Used within

Account (8.1)

### 8.4.2. Description

Asserted

### 8.4.3. Restrictions

Base type:

  xs:token

Maximum length:

  140

  See also: xs:maxLength (W3C XSD specification)

## complex type8.5. AccountTokenDetails

AccountTokenDetails | Attribute/child-element | Occurrence | Assert | Type | Section
sequence – | choice – |  | <type> | (1) | N | AccountTokenType | 9.5
| <typeOther> | (1) | N | Description | 9.24
| <token> | (1) | N | token | 8.6

### 8.5.1. Used within

Account (8.1)

### 8.5.2. Description

If the card is tokenised, the token can be an acquirer or issuer (or both) token.

The token may represent a payment card or a digital wallet.

Notes:

1. There are two (2) choices to describe the type of account or wallet token:

   1. Use <type> when there is a predefined token type; or

   2. Use <typeOther> when there is no predefined token type.

### 8.5.3. Child elements

`<type>`

  The account or wallet token type.

  See also: AccountTokenType (9.5)

`<typeOther>`

  Where there is no predefined token type, provide a brief description of the type of token.

  See also: Description (9.24)

`<token>`

  The token value or number.

  See also: AccountTokenDetails<token> (8.6)

## nested simple element8.6. AccountTokenDetails<token>

### 8.6.1. Used within

AccountTokenDetails (8.5)

### 8.6.2. Description

The token value or number.

### 8.6.3. Restrictions

Base type:

  xs:token

Pattern:

  [0-9a-zA-Z]{0,140}

  See also: xs:pattern (W3C XSD specification)

## complex type8.7. Address

Address | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – |  | <addr> | (1) | N | Addr | 9.10
| <suburb> | (1) | Y | Suburb | 9.49
| <state> | (0..1) | Y | State | 9.48
| <postcode> | (0..1) | Y | Postcode | 9.40
| <countryCode> | (1) | N | CountryCode | 9.19

### 8.7.1. Used within

BaseOrganisationDetails (8.12), IndividualDetails (8.23), RealEstate (8.36)

### 8.7.2. Description

This complex type is used to describe a residential, postal and business address of an individual; or a business, postal and registered office address of an organisation.

Provide an address by placing the constituent parts within separate child elements.

Notes:

1. All elements of this complex type are mandatory for an Australian address.

2. <addr>, <suburb> and <countryCode> are mandatory for a foreign address. <state> and <postcode> should be provided where applicable or known, as not all countries have states or use a postcode system.

### 8.7.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.7.4. Child elements

`<addr>`

  Provide the unit/number and street portion of an address.

  Do not provide suburb, town, city, postcode, state or country names in this field.

  See also: Addr (9.10)

`<suburb>`

  Provide the suburb, town or city name.

  See also: Suburb (9.49)

`<state>`

  Provide the designation of a state, province, county or territory (Australian or foreign) in a standard acronym or as a full name.

  See also: State (9.48)

`<postcode>`

  A postcode or zipcode.

  See also: Postcode (9.40)

`<countryCode>`

  Provide a country code expressed as a standard two-letter code as per Standard a two-letter code that represents a country name, recommended as the general purpose code published and maintained by ISO Standard a two-letter code that represents a country name, recommended as the general purpose code published and maintained by ISOISO 3166-1 alpha-2.

  See also: CountryCode (9.19)

## complex type8.8. AddressOrLocation

AddressOrLocation | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – |  | <addr> | (0..1) | Y | Addr | 9.10
| <suburb> | (1) | N | Suburb | 9.49
| <state> | (0..1) | Y | State | 9.48
| <postcode> | (0..1) | Y | Postcode | 9.40
| <countryCode> | (1) | N | CountryCode | 9.19
| <otherLocationDetails> | (0..1) | N | Description | 9.24

### 8.8.1. Used within

<transaction> (7.8), <otherDsProvider> (7.13)

### 8.8.2. Description

This complex type is used to describe an address or location of where the transaction took place, products or instruments were issued or another designated service provider is located.

The address is the full physical address.

The location is the city, suburb or town.

Both address and location may include other location details, if required.

Provide an address or location by placing the constituent parts within separate child elements.

Notes:

Where an address is provided the following details are expected:

1. All elements of this complex type are mandatory for an Australian address.

2. <addr>, <suburb> and <countryCode> are mandatory for a foreign address. <state> and <postcode> should be provided where applicable or known, as not all countries have states or use a postcode system.

Where a location is provided the following details are expected:

1. For Australian locations <suburb>, <state> and <countryCode> are mandatory

2. For foreign locations <suburb> and <countryCode> are mandatory

### 8.8.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.8.4. Child elements

`<addr>`

  Provide the unit/number and street portion of an address.

  Do not provide suburb, town, city, postcode, state or country names in this field.

  See also: Addr (9.10)

`<suburb>`

  Provide the suburb, town or city name.

  See also: Suburb (9.49)

`<state>`

  Provide the designation of a state, province, county or territory (Australian or foreign) in a standard acronym or as a full name.

  See also: State (9.48)

`<postcode>`

  A postcode or zipcode.

  See also: Postcode (9.40)

`<countryCode>`

  Provide the country expressed as a standard two-letter code as per Standard a two-letter code that represents a country name, recommended as the general purpose code published and maintained by ISO Standard a two-letter code that represents a country name, recommended as the general purpose code published and maintained by ISOISO 3166-1 alpha-2.

  See also: CountryCode (9.19)

`<otherLocationDetails>`

  Provide any other location details.

  See also: Description (9.24)

## complex type8.9. AgencyAuthorisation

AgencyAuthorisation | Attribute/child-element | Occurrence | Assert | Type | Section
extends – |  | Description | 9.24
attributes –
| refId | (1) |  | xs:IDREF | E.4

### 8.9.1. Used within

<otherPerson> (7.5)

### 8.9.2. Description

A generic type that allows you to describe in free format any agency authorisation that a party may have to act on behalf of another party and associate that authority to that other party.

An example of usage is <agencyAuthorisation> which uses this complex type:

>     <agencyAuthorisation refId="party-111">Power of attorney</agencyAuthorisation>

Some suggested agency authorisations

Agency/outsourcing agreement

  A document given by a person/organisation to another authorising the latter to act for the former, commonly used by businesses.

ASIC company extract/return, letter on letterhead from office holder(s)

  A document showing an appointed or registered representative of an organisation is authorised to act on behalf of that organisation (e.g. company director/secretary, association chairman/secretary/treasurer, etc.).

ASIC Form 5011/minutes of meeting

  A document authorising a person/organisation to administer or wind up a business (such as an administrator, liquidator or receiver).

Birth certificate/adoption document

  A document showing the person(s) responsible for or who can act on behalf of their child.

Court/tribunal order

  An order for a person/organisation to act on behalf of another (e.g. an order appointing a guardian or liquidator).

Delegated authority

  A written document given by a person to another person/organisation authorising the latter to stand in or act for the former.

Employee ID/representation document

  Documentation showing a person/organisation who can represent (i.e. stand or act in place of) another (e.g. an employee representing their employer).

Guardianship documentation

  A document showing that a person/organisation is entrusted with the care of a minor (i.e. child) or some other person legally incapable of managing their own affairs.

Letter of introduction/authorisation

  A document given by a person/organisation to another authorising the latter to act for the former.

Power of attorney

  A legal document given by a person/organisation to another authorising the latter to act for the former.

Trust deed

  A document appointing a person/organisation (often called the trustee) to administer the affairs of a company, institution, etc.

Will/probate

  A document appointing a person/organisation to carry out the terms of a Will (such as an executor or testamentary trustee of a deceased estate).

### 8.9.3. Attributes

`refId`

  Provide the reference ID of the associated party for which this agency authorisation is for.

  See also: xs:IDREF (E.4)

## complex type8.10. Attachment

Attachment | Attribute/child-element | Occurrence | Assert | Type | Section
extends – |  | xs:base64Binary | E.9
attributes –
| id | (1) |  | xs:ID | E.3
| fileName | (1) |  | xs:token | E.8

### 8.10.1. Used within

LppDetails (8.24)

### 8.10.2. Description

This complex type is used to describe the supporting documents to be attached to the report.

### 8.10.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

`fileName`

  Provide the file name of the attachment.

  See also: xs:token (E.8)

## complex type8.11. AudAmount

AudAmount | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – |  | <currencyCode> | (1) | N | CurrencyCode | 9.20
| <amount> | (1) | N | Amount | 9.12

### 8.11.1. Used within

<transaction> (7.8), <cash> (7.14), VirtualAsset (8.40)

### 8.11.2. Description

This complex type specifies the elements to use to describe the Australian currency code and value of that currency.

### 8.11.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.11.4. Child elements

`<currencyCode>`

  The currency must be AUD - the three-letter Standard codes for the representation of currencies and funds published and maintained by ISO Standard codes for the representation of currencies and funds published and maintained by ISOISO 4217 alphabetic code for Australian currency. For example:

      <currencyCode>AUD</currencyCode>

  See also: CurrencyCode (9.20)

`<amount>`

  Value of the currency involved.

  See also: Amount (9.12)

## complex type8.12. BaseOrganisationDetails

BaseOrganisationDetails | Attribute/child-element | Occurrence | Assert | Type | Section
sequence – |  | <fullLegalName> | (0..1) | N | Name | 9.37
| <abn> | (0..1) | N | ABN | 9.2
| <acn> | (0..1) | N | ACN | 9.3
| <arbn> | (0..1) | N | ARBN | 9.4
| <lei> | (0..1) | N | LEI | 9.35
| <bic> | (0..1) | N | BIC | 9.13
| <businessName> | (0..*) | N | Name | 9.37
| <isIncorporatedOverseas> | (0..1) | N | YesNo | 9.55
| <businessLicence> | (0..*) | Y | ForeignBusinessLicence | 8.21
| <taxResidencyCountryCode> | (0..*) | N | CountryCode | 9.19
| <businessAddress> | (0..1) | N | Address | 8.7
| <postalAddress> | (0..1) | N | PostalAddress | 8.32
| <registeredAddress> | (0..1) | N | OtherAddress | 8.30
| <phone> | (0..*) | N | PhoneNum | 9.38
| <email> | (0..*) | N | Email | 9.28
| <occupationBusinessActivity> | (0..1) | N | Description | 9.24
choice – (0..1) |  | <businessStructure> | (1) | N | BusinessStructure | 9.17
| <businessStructureOther> | (1) | N | Description | 9.24

Notes:

### 8.12.1. Used within

OrganisationDetails (8.29), EntityOrganisationDetails (8.20)

### 8.12.2. Description

This complex type is used to describe the names, identifying, contact, legal form and ownership details of an organisation.

Notes:

1. There are two (2) choices to describe the type of business structure:

   1. Use <type> when there is a predefined business structure; or

   2. Use <typeOther> when there is no predefined business structure type.

### 8.12.3. Child elements

`<fullLegalName>`

  Provide the full legal name of the organisation.

  See also: Name (9.37)

`<abn>`

  Provide the Australian Business Number (ABN) of the organisation.

  This is an 11-digit number issued to individuals and organisations by the Australian Taxation Office (ATO).

  See also: ABN (9.2)

`<acn>`

  Provide the Australian Company Number (ACN) of the organisation.

  This is a 9-digit number issued to companies registered in Australia by the Australian Securities and Investments Commission (ASIC).

  See also: ACN (9.3)

`<arbn>`

  Provide the Australian Registered Body Number (ARBN) of the organisation.

  This is a 9-digit number issued by Australian Securities and Investments Commission (ASIC).

  See also: ARBN (9.4)

`<lei>`

  Provide the Legal Entity Identifier (LEI) of the organisation.

  A LEI is a globally recognised identifier for businesses similar to an ABN. It is a 20-character, alphanumeric code based on ISO 17442 "Financial services - Legal entity identifier (LEI)". LEIs are issued by organisations accredited by the Global Legal Entity Identifier Foundation (GLEIF).

  See also: LEI (9.35)

`<bic>`

  Provide the BIC (Business Identifier Code).

  A BIC is 8 to 11-character, alphanumeric code based on ISO 9362. BICs are an international identifier issued by the Society for Worldwide Interbank Financial Telecommunication (Swift) to its members. BICs are used to facilitate international funds transfers and the exchange of other messages between Swift members.

  See also: BIC (9.13)

`<businessName>`

  If the organisation is known by another name provide this other name.

  Provide any trading name(s) under which the organisation is operating.

  Use a separate <businessName> element for each alternate name.

  See also: Name (9.37)

`<isIncorporatedOverseas>`

  Indicate if the organisation was incorporated, formed or registered outside of Australia.

  See also: YesNo (9.55)

`<businessLicence>`

  If the organisation was incorporated, formed or registered outside of Australia, provide the foreign business registration/licence number of the organisation and the country of where the organisation was incorporated, formed or registered.

  Use a separate <businessLicence> element for each foreign business registration/licence number.

  See also: ForeignBusinessLicence (8.21)

`<taxResidencyCountryCode>`

  List all countries where the organisation is treated as a tax resident.

  Use a separate <taxResidencyCountryCode> element for each country of tax residency.

  See also: CountryCode (9.19)

`<businessAddress>`

  The full street address of the organisation’s business address. This address cannot be a post box or similar address.

  See also: Address (8.7)

`<postalAddress>`

  The postal address associated with the organisation.

  See also: PostalAddress (8.32)

`<registeredAddress>`

  The full street address of the organisation’s office registration address. This address cannot be a post box or similar address.

  See also: OtherAddress (8.30)

`<phone>`

  Provide the organisation's phone number(s) including the country dial code and area code.

  Use a separate <phone> element for each telephone number.

  See also: PhoneNum (9.38)

`<email>`

  Provide the organisation's email address(es).

  Use a separate <email> element for each email address.

  See also: Email (9.28)

`<occupationBusinessActivity>`

  Provide details of the organisation's business or principal activity.

  See also: Description (9.24)

`<businessStructure>`

  Provide the legal form which best describes the business structure of the organisation (e.g. company, partnership, trust).

  See also: BusinessStructure (9.17)

`<businessStructureOther>`

  Provide a description of the legal form, if the type is not one of the predefined types.

  See also: Description (9.24)

## complex type8.13. BeneficialOwner

BeneficialOwner | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – |  | <individualDetails> | (1) | N | IndividualDetails | 8.23

### 8.13.1. Used within

OrganisationDetails (8.29)

### 8.13.2. Description

This complex type is used to describe details of a beneficial owner of an organisation.

A beneficial owner is an individual who directly or indirectly owns 25% or more of the entity or controls the entity's operations.

### 8.13.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.13.4. Child elements

`<individualDetails>`

  Provide the beneficial owner's full name, any other names they are known by, date of birth, gender, countries of citizenship, countries of tax residency, contact details, occupation and identity details.

  See also: IndividualDetails (8.23)

## complex type8.14. Bullion

Bullion | Attribute/child-element | Occurrence | Assert | Type | Section
extends – |  | CurrencyAmount | 8.15
sequence – |  | <type> | (0..1) | N | BullionType | 9.16
| <description> | (0..1) | N | Description | 9.24
| <serialNumber> | (0..1) | N | IdNumber | 9.33

### 8.14.1. Used within

<otherMoneyReceived> (7.10), <otherMoneyProvided> (7.12)

### 8.14.2. Description

This complex type is used to describe property details in relation to bullion.

Bullion means gold, silver, platinum or palladium, in the form of a bar, coin, ingot, plate, wafer or like form, that may bear a mark that identifies the fineness and quality of the bullion. Bullion is generally traded at a price determined by the spot price.

### 8.14.3. Child elements

`<type>`

  The type of bullion.

  See also: BullionType (9.16)

`<description>`

  The form or description of the bullion, e.g. bar, coin, ingot, plate, wafer, etc.

  See also: Description (9.24)

`<serialNumber>`

  The serial number of the bullion, if any.

  See also: IdNumber (9.33)

## complex type8.15. CurrencyAmount

CurrencyAmount | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – | choice – |  | <currencyCode> | (1) | N | CurrencyCode | 9.20
| <currencyOther> | (1) | N | Description | 9.24
| <amount> | (1) | N | Amount | 9.12
| <exchangeRate> | (0..1) | Y | DecimalNumber | 9.23

### 8.15.1. Used within

<otherMoneyReceived> (7.10), <otherMoneyProvided> (7.12), <cash> (7.14), CurrencyAmountOther (8.16), Bullion (8.14), PreciousMetal (8.33), PreciousProduct (8.34), PreciousStone (8.35), RealEstate (8.36)

### 8.15.2. Description

This complex type is used to describe a value by currency code or description, amount and exchange rate used.

Notes:

1. There are two (2) choices to describe the currency code:

   1. Use <currencyCode> when the currency code is on the Standard codes for the representation of currencies and funds published and maintained by ISO Standard codes for the representation of currencies and funds published and maintained by ISOISO 4217 list of currency names and codes; or

   2. Use <currencyOther> to describe the currency when it does not have an Standard codes for the representation of currencies and funds published and maintained by ISO Standard codes for the representation of currencies and funds published and maintained by ISOISO 4217 code.

### 8.15.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.15.4. Child elements

`<currencyCode>`

  Currency code expressed as a standard three-letter code as per Standard codes for the representation of currencies and funds published and maintained by ISO Standard codes for the representation of currencies and funds published and maintained by ISOISO 4217.

  Refer to the Standard codes for the representation of currencies and funds published and maintained by ISO Standard codes for the representation of currencies and funds published and maintained by ISOISO 4217 standard (available from www.iso.org) for a full list of currency names and codes. AUSTRAC uses the alphabetic currency codes for processing transaction reports.

  See also: CurrencyCode (9.20)

`<currencyOther>`

  A description of the currency is expected to be provided if the currency involved in the transaction does not have an Standard codes for the representation of currencies and funds published and maintained by ISO Standard codes for the representation of currencies and funds published and maintained by ISOISO 4217 code.

  This may be a currency that has limited use, such as a soft currency or region specific currency, that may be pegged to a standard currency but is not freely traded or convertible on global markets.

  This element is not to be used to describe a virtual asset or cryptocurrency. Refer to Section 8.40, “VirtualAsset”, if you need to describe a virtual asset.

  See also: Description (9.24)

`<amount>`

  Provide the value of the Australian or foreign currency without converting the value based on the exchange rates.

  See also: Amount (9.12)

`<exchangeRate>`

  Provide the exchange rate used to convert foreign currency to Australian dollars.

  Omit this element if the currency is Australia dollars (i.e. the exchange rate is 1:1) or the exchange rate is unknown.

  See also: DecimalNumber (9.23)

## complex type8.16. CurrencyAmountOther

CurrencyAmountOther | Attribute/child-element | Occurrence | Assert | Type | Section
extends – |  | CurrencyAmount | 8.15
sequence – |  | <description> | (1) | N | Description | 9.24

### 8.16.1. Used within

<otherMoneyReceived> (7.10), <otherMoneyProvided> (7.12)

### 8.16.2. Description

This complex type specifies the elements to use to describe the value of each “other” transaction component. Other, being a type which does not fall into any of the predefined transaction component types.

### 8.16.3. Child elements

`<description>`

  A free format description of the component.

  See also: Description (9.24)

## complex type8.17. DatetimeRange

DatetimeRange | Attribute/child-element | Occurrence | Assert | Type | Section
sequence – |  | <startDate> | (1) | N | Date | 9.21
| <startTime> | (0..1) | N | Time | 9.52
| <endDate> | (0..1) | Y | Date | 9.21
| <endTime> | (0..1) | N | Time | 9.52

### 8.17.1. Used within

OnlineActivity (8.26)

### 8.17.2. Description

This complex type is used to describe a date and time range.

### 8.17.3. Child elements

`<startDate>`

  Provide the start date. This can be used to capture the start of a transaction or a start of when a device/system was used.

  See also: Date (9.21)

`<startTime>`

  Optional time of the start date.

  See also: Time (9.52)

`<endDate>`

  Provide the end date. This can be used to capture the end of a transaction or the end of when a device/system was used.

  See also: Date (9.21)

`<endTime>`

  Optional time of the end date.

  See also: Time (9.52)

## complex type8.18. Director

Director | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – |  | <fullName> | (0..1) | N | Name | 9.37
| <directorId> | (0..1) | N | DirectorId | 9.27

### 8.18.1. Used within

OrganisationDetails (8.29)

### 8.18.2. Description

This complex type is used to describe the details about a company director or an individual with primary responsibility for the governance and executive decisions of the organisation.

### 8.18.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.18.4. Child elements

`<fullName>`

  Provide the full name of the director or individual with primary responsibility for the governance and executive decisions of the organisation.

  See also: Name (9.37)

`<directorId>`

  Provide the individual's director identification number (DIN or director ID).

  The director ID is a 15-digit number. Australian director IDs are administered by the Australian Business Registry Services (ABRS).

  See also: DirectorId (9.27)

## complex type8.19. Entity

Entity | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – | choice – |  | <individualDetails> | (1) | N | IndividualDetails | 8.23
| <organisationDetails> | (1) | N | EntityOrganisationDetails | 8.20

### 8.19.1. Used within

TrustParticipant (8.39), TrustDetails (8.38)

### 8.19.2. Description

This complex type is used to categorise an entity as an individual or organisation and describe the details required based on the category.

Notes:

1. There are two (2) choices:

   1. Use <individualDetails> when the entity is an individual; or

   2. Use <organisationDetails> when the entity is an organisation.

### 8.19.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.19.4. Child elements

`<individualDetails>`

  Provide the individual's full name, any other names they are known by, date of birth, gender, countries of citizenship, countries of tax residency, contact details, occupation and identification details.

  See also: IndividualDetails (8.23)

`<organisationDetails>`

  Provide the organisation's full legal name, other names used by the organisation (e.g. a former name or business name), business identifiers (e.g. ABN, ACN, LEI), countries of incorporation, formation or registration, countries of tax residency, registered office address, contact details, type of business or principal activity, business structure (e.g. company, partnership, trust) and the verified identifications.

  See also: EntityOrganisationDetails (8.20)

## complex type8.20. EntityOrganisationDetails

EntityOrganisationDetails | Attribute/child-element | Occurrence | Assert | Type | Section
extends – |  | BaseOrganisationDetails | 8.12
sequence – |  | <isIdentityVerified> | (0..1) | N | YesNo | 9.55
| <identification> | (0..*) | Y | Identification | 8.22

### 8.20.1. Used within

Entity (8.19)

### 8.20.2. Description

This complex type is used to describe the details of an organisation.

### 8.20.3. Child elements

`<isIdentityVerified>`

  Indicate if the identity of the organisation was verified.

  See also: YesNo (9.55)

`<identification>`

  Provide details of any identification documents or identity verification services used by the reporting entity to confirm the identity of the organisation. Identification checks are expected to be from reliable and independent sources.

  Use a separate <identification> element for each form of identification.

  See also: Identification (8.22)

## complex type8.21. ForeignBusinessLicence

ForeignBusinessLicence | Attribute/child-element | Occurrence | Assert | Type | Section
sequence – |  | <number> | (1) | N | IdNumber | 9.33
| <countryCode> | (1) | N | ForeignCountryCode | 9.30

### 8.21.1. Used within

BaseOrganisationDetails (8.12)

### 8.21.2. Description

This complex type is used to describe the foreign business registration or licence details of an organisation.

### 8.21.3. Child elements

`<number>`

  Provide the organisation's foreign business registration or licence number.

  See also: IdNumber (9.33)

`<countryCode>`

  Provide the country which issued this business registration or licence number to the organisation, expressed as a standard two-letter country code as per ISO 3166-1 alpha-2.

  See also: ForeignCountryCode (9.30)

## complex type8.22. Identification

Identification | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – | choice – |  | <type> | (1) | N | IdType | 9.34
| <typeOther> | (1) | N | Description | 9.24
| <number> | (0..1) | Y | IdNumber | 9.33
| <issuer> | (0..1) | Y | IdIssuer | 9.32
| <countryCode> | (0..1) | Y | CountryCode | 9.19

### 8.22.1. Used within

OrganisationDetails (8.29), EntityOrganisationDetails (8.20), IndividualDetails (8.23)

### 8.22.2. Description

This complex type is used to describe details of documentation sighted or verification services used to confirm the identity of a individual or organisation.

Notes:

1. There are two (2) choices to describe the type of identification document sighted or verification service by the reporting entity:

   1. Use <type> when there is a predefined identification type; or

   2. Use <typeOther> to provide a description when there is no predefined identification type.

### 8.22.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.22.4. Child elements

`<type>`

  Type of identification.

  See also: IdType (9.34)

`<typeOther>`

  Provide a description of the identification document or verification service where there is no predefined identification type.

  See also: Description (9.24)

`<number>`

  Provide an identification document number or name, if no identifying code is available.

  See also: IdNumber (9.33)

`<issuer>`

  Name of the government body, State, Territory or organisation that issued the identification document or provided the verification service.

  See also: IdIssuer (9.32)

`<countryCode>`

  Provide the country of where the identification details were issued or originated from, expressed as a standard two-letter country code as per ISO 3166-1 alpha-2.

  See also: CountryCode (9.19)

## complex type8.23. IndividualDetails

IndividualDetails | Attribute/child-element | Occurrence | Assert | Type | Section
sequence – |  | <fullName> | (0..1) | N | Name | 9.37
| <altName> | (0..*) | N | Name | 9.37
| <birthDate> | (0..1) | N | BirthDate | 9.15
| <gender> | (0..1) | N | Gender | 9.31
| <citizenshipCountryCode> | (0..*) | N | CountryCode | 9.19
| <taxResidencyCountryCode> | (0..*) | N | CountryCode | 9.19
| <isSoleTrader> | (0..1) | N | YesNo | 9.55
| <isAbnHolder> | (0..1) | Y | YesNo | 9.55
| <abn> | (0..1) | Y | ABN | 9.2
| <residentialAddress> | (0..1) | N | Address | 8.7
| <postalAddress> | (0..1) | N | PostalAddress | 8.32
| <businessAddress> | (0..1) | N | OtherAddress | 8.30
| <phone> | (0..*) | N | PhoneNum | 9.38
| <email> | (0..*) | N | Email | 9.28
| <occupationBusinessActivity> | (0..1) | N | Description | 9.24
| <isIdentityVerified> | (0..1) | N | YesNo | 9.55
| <identification> | (0..*) | Y | Identification | 8.22

### 8.23.1. Used within

<customer> (7.3), <otherPerson> (7.5), <recipient> (7.7), Entity (8.19), BeneficialOwner (8.13)

### 8.23.2. Description

This complex type is used to describe the details of an individual. This includes the individual's full name, any other names they are known by, date of birth, gender, countries of citizenship, countries of tax residency, contact details, occupation and identification details.

### 8.23.3. Child elements

`<fullName>`

  Provide the full name of the individual, i.e. given names and family name.

  See also: Name (9.37)

`<altName>`

  If the individual is known by another name provide this other name.

  This may include:

  - a business name as a sole trader
  - a former name which may have legally changed (e.g. through marriage)
  - an anglicised version of a foreign name, or
  - nickname

  Use a separate <altName> element for each alternate name.

  See also: Name (9.37)

`<birthDate>`

  Provide the individual's date of birth.

  See also: BirthDate (9.15)

`<gender>`

  Provide the individual's gender.

  Gender may be determined according to identity documents already collected, or by the title used to prefix the name of the individual (e.g. Mr, Mrs, Miss, Ms).

  Omit this element if the gender of the individual is unknown.

  See also: Gender (9.31)

`<citizenshipCountryCode>`

  List the countries the individual is a citizen of.

  Use a separate <citizenshipCountryCode> element for each country of citizenship.

  See also: CountryCode (9.19)

`<taxResidencyCountryCode>`

  List the countries where the individual is treated as a tax resident.

  Use a separate <taxResidencyCountryCode> element for each country of tax residency.

  See also: CountryCode (9.19)

`<isSoleTrader>`

  Indicate if the individual is a sole trader.

  See also: YesNo (9.55)

`<isAbnHolder>`

  Indicate if the individual has an ABN.

  See also: YesNo (9.55)

`<abn>`

  If the individual is a sole trader and has an Australian Business Number (ABN), provide their ABN.

  An ABN is an 11-digit number issued to individuals and organisations by the Australian Business Register (ABR), which is operated and managed by the Australian Taxation Office (ATO).

  See also: ABN (9.2)

`<residentialAddress>`

  Provide the full street address of the individual’s residential address. This address cannot be a post box or similar address.

  See also: Address (8.7)

`<postalAddress>`

  Provide the postal address of the individual.

  See also: PostalAddress (8.32)

`<businessAddress>`

  Provide the full street address of the individual's business address, if they are a sole trader. This address cannot be a post box or similar address.

  See also: OtherAddress (8.30)

`<phone>`

  Provide the individual's phone number(s) including the country dial code and area code.

  Use a separate <phone> element for each telephone number.

  See also: PhoneNum (9.38)

`<email>`

  Provide the individual's email address(es).

  Use a separate <email> element for each email address.

  See also: Email (9.28)

`<occupationBusinessActivity>`

  Provide the occupation, business or principal activity details of the individual.

  See also: Description (9.24)

`<isIdentityVerified>`

  Indicate if the identity of the individual was verified.

  See also: YesNo (9.55)

`<identification>`

  Provide details of any identification documents or identity verification services used by the reporting entity to confirm the identity of the individual. Identification checks are expected to be from reliable and independent sources.

  Use a separate <identification> element for each form of identification.

  See also: Identification (8.22)

## complex type8.24. LppDetails

LppDetails | Attribute/child-element | Occurrence | Assert | Type | Section
sequence – |  | <lppFlag> | (1) | N | YesNo | 9.55
| <lppClaimForm> | (0..1) | Y | Attachment | 8.10

### 8.24.1. Used within

<ttr> (7.1)

### 8.24.2. Description

This complex type is used to provide any legal professional privilege (LPP) details relating to the threshold transaction report.

### 8.24.3. Child elements

`<lppFlag>`

  Indicate if the reporting entity is claiming LPP for this report.

  See also: YesNo (9.55)

`<lppClaimForm>`

  If claiming LPP, use this element to attach and associate a completed LPP form to this report.

  Omit this element, if:

  1. the LPP form is to be sent to AUSTRAC via another channel (e.g. email), or

  2. the report is to be intercepted by AUSTRAC Online for the LPP form to be manually attached to the report.

  See also: Attachment (8.10)

## complex type8.25. NameWithId

NameWithId | Attribute/child-element | Occurrence | Assert | Type | Section
extends – |  | Name | 9.37
attributes –
| id | (1) |  | xs:ID | E.3

### 8.25.1. Used within

TTRVirtualAsset (8.37)

### 8.25.2. Description

This complex type extends a Name type of an individual or organisation to include an id attribute.

### 8.25.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

## complex type8.26. OnlineActivity

OnlineActivity | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – | choice – |  | <type> | (1) | N | DeviceType | 9.26
| <typeOther> | (1) | N | Description | 9.24
| <identifier> | (1) | N | IdNumber | 9.33
| <usageDatetimeRange> | (0..1) | N | DatetimeRange | 8.17
| <applicationName> | (0..1) | N | applicationName | 8.27
| <userName> | (0..1) | N | userName | 8.28

### 8.26.1. Used within

<customer> (7.3), <otherPerson> (7.5)

### 8.26.2. Description

This complex type is used to describe any online activity related to a party and transaction. This includes, the network/device identifier used (e.g. IP address, MAC address, etc.), the date and time range of the online activity, the website or mobile app used, and the username used.

Notes:

1. There are two (2) choices to describe the type of network/device identifier:

   1. Use <type> when there is a predefined network/device identifier type; or

   2. Use <typeOther> when there is no suitable, predefined type which describes the network/device identifier.

### 8.26.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.26.4. Child elements

`<type>`

  Use one of the predefined network/device identifier types to indicate what the identifier number relates to, e.g. an IP address, a MAC address, etc.

  See also: DeviceType (9.26)

`<typeOther>`

  Provide a description of the device identifier type if the type is not one of the predefined types.

  See also: Description (9.24)

`<identifier>`

  Provide the identifier (i.e. a name, series of numbers, etc.) used which represents or uniquely identify a device, network or system.

  See also: IdNumber (9.33)

`<usageDatetimeRange>`

  The date and time range, when this device or system was used.

  Start and End datetime, each including offset information. The <endDate> must be on or after <startDate>.

  See also: DatetimeRange (8.17)

`<applicationName>`

  Provide the name of the website or mobile application used.

  See also: OnlineActivity<applicationName> (8.27)

`<userName>`

  Provide the username used to access the website or mobile application.

  See also: OnlineActivity<userName> (8.28)

## nested simple element8.27. OnlineActivity<applicationName>

### 8.27.1. Used within

OnlineActivity (8.26)

### 8.27.2. Description

Provide the name of the website or mobile application used.

### 8.27.3. Restrictions

Base type:

  xs:token

Maximum length:

  140

  See also: xs:maxLength (W3C XSD specification)

## nested simple element8.28. OnlineActivity<userName>

### 8.28.1. Used within

OnlineActivity (8.26)

### 8.28.2. Description

Provide the username used to access the website or mobile application.

### 8.28.3. Restrictions

Base type:

  xs:token

Maximum length:

  140

  See also: xs:maxLength (W3C XSD specification)

## complex type8.29. OrganisationDetails

OrganisationDetails | Attribute/child-element | Occurrence | Assert | Type | Section
extends – |  | BaseOrganisationDetails | 8.12
sequence – |  | <director> | (0..*) | N | Director | 8.18
| <beneficialOwner> | (0..*) | N | BeneficialOwner | 8.13
| <isExpressTrust> | (0..1) | Y | YesNo | 9.55
| <trustDetails> | (0..1) | Y | TrustDetails | 8.38
| <isIdentityVerified> | (0..1) | N | YesNo | 9.55
| <identification> | (0..*) | Y | Identification | 8.22

### 8.29.1. Used within

<customer> (7.3), <representedOrganisation> (7.4), <recipient> (7.7)

### 8.29.2. Description

This complex type extends BaseOrganisationDetails to include additional details about directors or who is responsible for governance and executive decisions, beneficial owners, trust participants and identification details of an organisation.

### 8.29.3. Child elements

`<director>`

  Provide details of directors or the individuals with primary responsibility for the governance and executive decisions of the organisation.

  Use a separate <director> element for each individual.

  See also: Director (8.18)

`<beneficialOwner>`

  Provide details of all beneficial owners of the organisation.

  Use a separate <beneficialOwner> element for each beneficial owner.

  See also: BeneficialOwner (8.13)

`<isExpressTrust>`

  Indicate if the trust is an express trust.

  See also: YesNo (9.55)

`<trustDetails>`

  If the organisation is an express trust, provide the details of the trust.

  See also: TrustDetails (8.38)

`<isIdentityVerified>`

  Indicate if the identity of the party was verified. If verified, identification details are required to be reported.

  See also: YesNo (9.55)

`<identification>`

  Provide details of any identification documents or identity verification services used by the reporting entity to confirm the identity of the organisation. Identification checks are expected to be from reliable and independent sources.

  Use a separate <identification> element for each form of identification.

  See also: Identification (8.22)

## complex type8.30. OtherAddress

OtherAddress | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
choice – |  | <sameAs> | (1) | N | AddressType | 9.11
sequence – |  | <addr> | (1) | N | Addr | 9.10
| <suburb> | (1) | Y | Suburb | 9.49
| <state> | (0..1) | Y | State | 9.48
| <postcode> | (0..1) | Y | Postcode | 9.40
| <countryCode> | (1) | N | CountryCode | 9.19

### 8.30.1. Used within

BaseOrganisationDetails (8.12), IndividualDetails (8.23)

### 8.30.2. Description

This complex type is used to describe any other address associated with an individual or organisation.

An individual or organisation may also have a postal address (Section 8.32, “PostalAddress”).

Other addresses are:

- Business address for individual, if they are a sole trader.

- Registered office address for an organisation.

This address cannot be a post box or similar address.

Notes:

1. All elements of this complex type are mandatory for Australian based addresses.

2. <state> and <postcode> should be provided where applicable for foreign based addresses, as not all countries have states or use a postcode system.

There are two choices for other address:

1. Indicate if the address is the same as another address for this party.

2. Provide the address using the sequence of child elements.

### 8.30.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.30.4. Child elements

`<sameAs>`

  Indicate if the address is the same as:

  - Residential address or postal address of an individual.

  - Business address or postal address of an organisation.

  See also: AddressType (9.11)

`<addr>`

  Provide the unit/number and street portion of an address.

  Do not provide suburb, town, city, postcode, state or country names in this field.

  See also: Addr (9.10)

`<suburb>`

  Provide the suburb, town or city name.

  See also: Suburb (9.49)

`<state>`

  Provide the designation of a state, province, county or territory (Australian or foreign) in a standard acronym or as a full name.

  See also: State (9.48)

`<postcode>`

  A postcode or zipcode.

  See also: Postcode (9.40)

`<countryCode>`

  Provide the country expressed as a standard two-letter code as per Standard a two-letter code that represents a country name, recommended as the general purpose code published and maintained by ISO Standard a two-letter code that represents a country name, recommended as the general purpose code published and maintained by ISOISO 3166-1 alpha-2.

  See also: CountryCode (9.19)

## complex type8.31. PartyReference

PartyReference | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| refId | (1) |  | xs:IDREF | E.4

### 8.31.1. Used within

<otherPerson> (7.5), <recipient> (7.7), TTRVirtualAsset (8.37), TrustParticipant (8.39)

### 8.31.2. Description

This complex type specifies the attribute to use to cross-reference or associate parties already mentioned in a transaction report, by setting the `refId` attribute to the `id` value of the party referenced.

### 8.31.3. Attributes

`refId`

  This value must match the id of a party that has already been defined elsewhere.

  See also: xs:IDREF (E.4)

## complex type8.32. PostalAddress

PostalAddress | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
choice – |  | <sameAs> | (1) | N | MainAddressType | 9.36
sequence – |  | <addr> | (1) | N | Addr | 9.10
| <suburb> | (1) | Y | Suburb | 9.49
| <state> | (0..1) | Y | State | 9.48
| <postcode> | (0..1) | Y | Postcode | 9.40
| <countryCode> | (1) | N | CountryCode | 9.19

### 8.32.1. Used within

BaseOrganisationDetails (8.12), IndividualDetails (8.23)

### 8.32.2. Description

This complex type is used to describe a postal address/location of a person or organisation.

Notes:

1. All elements of this complex type are mandatory for Australian based addresses.

2. <state> and <postcode> should be provided where applicable for foreign based addresses, as not all countries have states or use a postcode system.

There are two choices for other address:

1. Indicate if the address is the same as another address for this party.

2. Provide the address using the sequence of child elements.

### 8.32.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.32.4. Child elements

`<sameAs>`

  Indicate if the address is the same as Business Address for an organisation or same as Residential address for an individual.

  See also: MainAddressType (9.36)

`<addr>`

  Provide the unit/number and street portion, or PO Box number (or similar), of an address.

  Do not provide suburb, town, city, postcode, state or country names in this field.

  See also: Addr (9.10)

`<suburb>`

  Provide the suburb, town or city name.

  See also: Suburb (9.49)

`<state>`

  Provide the designation of a state, province, county or territory (Australian or foreign) in a standard acronym or as a full name.

  See also: State (9.48)

`<postcode>`

  A postcode or zipcode.

  See also: Postcode (9.40)

`<countryCode>`

  Provide the country expressed as a standard two-letter code as per Standard a two-letter code that represents a country name, recommended as the general purpose code published and maintained by ISO Standard a two-letter code that represents a country name, recommended as the general purpose code published and maintained by ISOISO 3166-1 alpha-2.

  See also: CountryCode (9.19)

## complex type8.33. PreciousMetal

PreciousMetal | Attribute/child-element | Occurrence | Assert | Type | Section
extends – |  | CurrencyAmount | 8.15
sequence – |  | <metal> | (0..1) | N | PreciousMetalType | 9.41
| <description> | (0..1) | N | Description | 9.24
| <serialNumber> | (0..1) | N | IdNumber | 9.33

### 8.33.1. Used within

<otherMoneyReceived> (7.10), <otherMoneyProvided> (7.12)

### 8.33.2. Description

This complex type is used to describe property details in relation to precious metals.

Precious metal can be gold, iridium, osmium, palladium platinum, rhodium, ruthenium or silver, or an alloy with at least 2% weight of any of these substances.

### 8.33.3. Child elements

`<metal>`

  The type of precious metal.

  See also: PreciousMetalType (9.41)

`<description>`

  Provide a description of the precious metal if it is an alloy or not one of the predefined types.

  See also: Description (9.24)

`<serialNumber>`

  The serial number of the precious metal, if any.

  See also: IdNumber (9.33)

## complex type8.34. PreciousProduct

PreciousProduct | Attribute/child-element | Occurrence | Assert | Type | Section
extends – |  | CurrencyAmount | 8.15
sequence – |  | <product> | (0..1) | N | PreciousProductType | 9.42
| <description> | (0..1) | N | Description | 9.24
| <serialNumber> | (0..1) | N | IdNumber | 9.33

### 8.34.1. Used within

<otherMoneyReceived> (7.10), <otherMoneyProvided> (7.12)

### 8.34.2. Description

This complex type is used to describe property details in relation to precious products.

Precious products are jewellery, watches, other objects of personal adornment and goldsmith's or silversmith's wares (e.g. ornaments, tableware, smoker's requisites and other articles of personal, household, office or religious use).

### 8.34.3. Child elements

`<product>`

  The type of precious product.

  See also: PreciousProductType (9.42)

`<description>`

  Provide a description of the jewellery, watch, other object of personal adornment or article of goldsmith's or silversmith's wares.

  See also: Description (9.24)

`<serialNumber>`

  The serial number of that precious product, if any.

  See also: IdNumber (9.33)

## complex type8.35. PreciousStone

PreciousStone | Attribute/child-element | Occurrence | Assert | Type | Section
extends – |  | CurrencyAmount | 8.15
sequence – | choice – (0..1) |  | <stone> | (1) | N | PreciousStoneType | 9.43
| <description> | (1) | N | Description | 9.24
| <serialNumber> | (0..1) | N | IdNumber | 9.33

Notes:

### 8.35.1. Used within

<otherMoneyReceived> (7.10), <otherMoneyProvided> (7.12)

### 8.35.2. Description

This complex type is used to describe property details in relation to precious stones.

Precious stones may include beryl, corundum, diamond, garnet, jadeite/jade, opal, pearl and topaz.

Notes:

1. There are two (2) choices to describe the type of precious stone:

   1. Use <stone> when there is a predefined type of precious stone; or

   2. Use <description> to provide a description if none of the predefined types adequately describes the type of precious stone.

### 8.35.3. Child elements

`<stone>`

  The type of precious stone.

  See also: PreciousStoneType (9.43)

`<description>`

  Provide a description of the stone when there is no predefined type.

  See also: Description (9.24)

`<serialNumber>`

  The serial number of that precious stone, if any.

  See also: IdNumber (9.33)

## complex type8.36. RealEstate

RealEstate | Attribute/child-element | Occurrence | Assert | Type | Section
extends – |  | CurrencyAmount | 8.15
sequence – |  | <propertyAddress> | (0..1) | N | Address | 8.7
| <propertyId> | (0..1) | N | IdNumber | 9.33

### 8.36.1. Used within

<otherMoneyReceived> (7.10), <otherMoneyProvided> (7.12)

### 8.36.2. Description

This complex type is used to describe property details in relation to real estate.

### 8.36.3. Child elements

`<propertyAddress>`

  Provide the address of the property.

  See also: Address (8.7)

`<propertyId>`

  Provide the property ID details, e.g. the plan and lot numbers for the real estate.

  See also: IdNumber (9.33)

## complex type8.37. TTRVirtualAsset

TTRVirtualAsset | Attribute/child-element | Occurrence | Assert | Type | Section
extends – |  | VirtualAsset | 8.40
sequence – |  | <assetControllerSameAs> | (0..*) | N | PartyReference | 8.31
| <assetControllerName> | (0..*) | N | NameWithId | 8.25
| <assetHolderSameAs> | (0..*) | N | PartyReference | 8.31
| <assetHolderName> | (0..*) | N | NameWithId | 8.25

### 8.37.1. Used within

<otherMoneyReceived> (7.10), <otherMoneyProvided> (7.12)

### 8.37.2. Description

This complex type extends the VirtualAsset type to include the names of:

- any individual, organisation or decentralised autonomous organisation (DAO) who controls or controlled the virtual asset, and

- any individual or organisation in whose name the virtual assets are, or were, held.

### 8.37.3. Child elements

`<assetControllerSameAs>`

  Associate the virtual asset controller to a customer or other person, if they are a controller.

  For example:

  >       :
  >     <customer id="cust-111">
  >       :
  >     </customer>
  >       :
  >     <virtualAsset id="va-333">
  >       <assetControllerSameAs refId="cust-111"/>
  >     </virtualAsset>
  >       :

  See also: PartyReference (8.31)

`<assetControllerName>`

  For all other controllers of the virtual asset, list them by name.

  Use a separate <assetControllerName> element for each name.

  See also: NameWithId (8.25)

`<assetHolderSameAs>`

  Associate the virtual asset holder to a customer or other person, if they are or were the holder of the virtual asset.

  For example:

  >       :
  >     <customer id="cust-111">
  >       :
  >     </customer>
  >       :
  >     <virtualAsset id="va-333">
  >       <assetHolderSameAs refId="cust-111"/>
  >     </virtualAsset>
  >       :

  See also: PartyReference (8.31)

`<assetHolderName>`

  For all other holders of the virtual asset, list them by name.

  Use a separate <assetHolderName> element for each name.

  See also: NameWithId (8.25)

## complex type8.38. TrustDetails

TrustDetails | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – | choice – |  | <trustType> | (1) | N | TrustType | 9.54
| <trustTypeOther> | (1) | N | Description | 9.24
| <trustName> | (0..1) | N | Name | 9.37
| <trustParticipant> | (0..*) | N | TrustParticipant | 8.39
| <isTenOrLessBeneficiaries> | (0..1) | N | YesNo | 9.55
choice – (0..1) |  | <trustBeneficiary> | (1..10) | Y | Entity | 8.19
choice – (1..*) |  | <beneficiaryTypeOrClass> | (1) | Y | BeneficiaryTypeOrClass | 9.14
| <beneficiaryTypeOrClassOther> | (1) | Y | Description | 9.24

Notes:

### 8.38.1. Used within

OrganisationDetails (8.29)

### 8.38.2. Description

This complex type is used to provide details of the trust and its beneficiaries.

Notes:

1. There are two (2) choices to describe the type of trust:

   1. Use <trustType>

   2. Use <trustTypeOther>

2. There are two (2) choices to describe the beneficiaries of the trust:

   1. When there are 10 or less beneficiaries and the beneficiaries are named in the trust deed, use the <trustBeneficiary> element

   2. Otherwise use the <beneficiaryTypeOrClass> or <beneficiaryTypeOrClassOther> elements.

3. There are two (2) choices to describe the type or class of beneficiary:

   1. Use <beneficiaryTypeOrClass> when there is a predefined type or class of beneficiary; or

   2. Use <beneficiaryTypeOrClassOther> to provide a description when the predefined types or classes to not adequately describe the type or class of beneficiary.

### 8.38.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.38.4. Child elements

`<trustType>`

  A predefined code representing the type of the trust.

  See also: TrustType (9.54)

`<trustTypeOther>`

  Provide a description of the trust type, if the type is not one of the predefined types.

  See also: Description (9.24)

`<trustName>`

  The trust name.

  See also: Name (9.37)

`<trustParticipant>`

  Provide the details of each trust participant.

  Use a separate <trustParticipant> element for each participant.

  See also: TrustParticipant (8.39)

`<isTenOrLessBeneficiaries>`

  Indicate if there are 10 or less beneficiaries.

  See also: YesNo (9.55)

`<trustBeneficiary>`

  If there are 10 or less beneficiaries which have been named in the trust deed, provide full details of each trust beneficiary.

  Use a separate <trustBeneficiary> element for each named beneficiary.

  See also: Entity (8.19)

`<beneficiaryTypeOrClass>`

  If there are more than 10 beneficiaries or just a type or class of beneficiary listed in the trust deed, use a predefined code to indicate the type or class of the beneficiary.

  Use a separate <beneficiaryTypeOrClass> element for each distinct type or class of beneficiary.

  See also: BeneficiaryTypeOrClass (9.14)

`<beneficiaryTypeOrClassOther>`

  Provide a description of the beneficiary type or class, if the beneficiary class or type is not one of the predefined types.

  See also: Description (9.24)

## complex type8.39. TrustParticipant

TrustParticipant | Attribute/child-element | Occurrence | Assert | Type | Section
attributes –
| id | (1) |  | xs:ID | E.3
sequence – |  | <roleCode> | (1..5) | N | FiduciaryRoleType | 9.29
choice – |  | <sameAs> | (1) | N | PartyReference | 8.31
| <other> | (1) | N | Entity | 8.19

### 8.39.1. Used within

TrustDetails (8.38)

### 8.39.2. Description

This complex type is used to provide details of a trust participant and to indicate the role(s) they have with the trust.

Notes:

1. There are two (2) choices in relation to a trust participant:

   1. Use <sameAs> to associate the trust participant with another party (e.g. a customer or other person)

   2. Use <other> to provide full details of the trust participant.

### 8.39.3. Attributes

`id`

  Provide an alphanumeric `id` value to uniquely indicate the element within the Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML document.

  See also: xs:ID (E.3)

### 8.39.4. Child elements

`<roleCode>`

  List the role(s) of the trust participant from the predefined trust fiduciary role types.

  Use a separate <roleCode> element for each role.

  See also: FiduciaryRoleType (9.29)

`<sameAs>`

  Indicate if this party is the same as the other party in the report by using the <sameAs> element. For example:

  >       :
  >     <customer id="cust-111">
  >       :
  >     </customer>
  >       :
  >     <trustParticipant id="settlor-333">
  >       <sameAs refId="cust-111"/>
  >       :
  >     </trustParticipant>
  >       :

  See also: PartyReference (8.31)

`<other>`

  Details of the trust participant are expected to be provided if not one of the other parties listed in the report.

  See also: Entity (8.19)

## complex type8.40. VirtualAsset

VirtualAsset | Attribute/child-element | Occurrence | Assert | Type | Section
extends – |  | AudAmount | 8.11
sequence – |  | <code> | (0..1) | N | code | 8.41
| <description> | (0..1) | N | Description | 9.24
| <backingAsset> | (0..1) | N | Description | 9.24
| <blockchainTransactionId> | (0..1) | N | blockchainTransactionId | 8.42
| <numberOfUnits> | (0..1) | N | DecimalNumber | 9.23
| <exchangeRate> | (0..1) | N | DecimalNumber | 9.23

### 8.40.1. Used within

TTRVirtualAsset (8.37)

### 8.40.2. Description

This complex type is used to describe details about a Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.virtual asset in terms of the virtual asset code/ticker, description, backing asset (if any), blockchain transaction ID, number of units and exchange rate.

An example of usage is:

      <virtualAsset>
        <currencyCode>AUD</currencyCode>
        <amount>12000.00</amount>
        <code>BTC</code>
        <description>Bitcoin</description>
        <numberOfUnits>5</numberOfUnits>
        <backingAsset>Some Backing Asset</backingAsset>
        <blockchainTransactionId>234893a8b8098c990965def483793048356944939</blockchainTransactionId>
      </virtualAsset>

### 8.40.3. Child elements

`<code>`

  The code or ticker associated with the Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.virtual asset, e.g. BTC for Bitcoin, ETH for Ethereum.

  See also: VirtualAsset<code> (8.41)

`<description>`

  The description or name associated with the Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.virtual asset, e.g. Bitcoin, Ethereum.

  See also: Description (9.24)

`<backingAsset>`

  The description of the commodity, product, object or thing the Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.virtual asset is backed by or pegged to, e.g. gold, exchange-traded funds, US dollars.

  See also: Description (9.24)

`<blockchainTransactionId>`

  The transaction hash (i.e. identifier) of the blockchain transaction, if applicable for this Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.virtual asset transfer.

  See also: VirtualAsset<blockchainTransactionId> (8.42)

`<numberOfUnits>`

  The number of units or value of the Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.virtual asset. If more than 10 decimal places, truncate to 10 decimal places.

  See also: DecimalNumber (9.23)

`<exchangeRate>`

  The exchange rate, which was used in the conversion of virtual asset units to AUD.

  See also: DecimalNumber (9.23)

## nested simple element8.41. VirtualAsset<code>

### 8.41.1. Used within

VirtualAsset (8.40)

### 8.41.2. Description

The code or ticker associated with the Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.virtual asset, e.g. BTC for Bitcoin, ETH for Ethereum.

### 8.41.3. Restrictions

Base type:

  xs:token

Maximum length:

  20

  See also: xs:maxLength (W3C XSD specification)

Pattern:

  [a-zA-Z0-9]+[\\@$a-zA-Z0-9]*

  See also: xs:pattern (W3C XSD specification)

## nested simple element8.42. VirtualAsset<blockchainTransactionId>

### 8.42.1. Used within

VirtualAsset (8.40)

### 8.42.2. Description

The transaction hash (i.e. identifier) of the blockchain transaction, if applicable for this Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.virtual asset transfer.

### 8.42.3. Restrictions

Base type:

  xs:token

Maximum length:

  1024

  See also: xs:maxLength (W3C XSD specification)

Pattern:

  [0-9a-zA-Z]+

  See also: xs:pattern (W3C XSD specification)

## Chapter 9. Simple types

This section describes all the globally defined simple types within the schema. Simple types define structures that can only have text content. These types do not have any child elements or attributes.

## simple type9.1. AAN

### 9.1.1. Used within

<ttrList> (6.1)

### 9.1.2. Description

AUSTRAC Account Number (AAN) of the reporting entity.

This is a 9-digit number issued by AUSTRAC to businesses when they enrol as a reporting entity.

### 9.1.3. Restrictions

Base type:

  xs:token

Pattern:

  [0-9]{9}

  See also: xs:pattern (W3C XSD specification)

## simple type9.2. ABN

### 9.2.1. Used within

BaseOrganisationDetails (8.12), IndividualDetails (8.23)

### 9.2.2. Description

Australian Business Number (ABN) of the organisation.

This is an 11-digit number issued to businesses by the Australian Business Register (ABR), which is operated and managed by the Australian Taxation Office (ATO).

### 9.2.3. Restrictions

Base type:

  xs:token

Pattern:

  [0-9]{11}

  See also: xs:pattern (W3C XSD specification)

## simple type9.3. ACN

### 9.3.1. Used within

BaseOrganisationDetails (8.12)

### 9.3.2. Description

Australian Company Number (ACN) of the organisation.

This is a 9-digit number issued to companies registered in Australia by the Australian Securities and Investments Commission (ASIC).

### 9.3.3. Restrictions

Base type:

  xs:token

Pattern:

  [0-9]{9}

  See also: xs:pattern (W3C XSD specification)

## simple type9.4. ARBN

### 9.4.1. Used within

BaseOrganisationDetails (8.12)

### 9.4.2. Description

An Australian Registered Body Number (ARBN) of the organisation.

This is a 9-digit number issued by Australian Securities and Investments Commission (ASIC).

### 9.4.3. Restrictions

Base type:

  xs:token

Pattern:

  [0-9]{9}

  See also: xs:pattern (W3C XSD specification)

## simple type9.5. AccountTokenType

### 9.5.1. Used within

AccountTokenDetails (8.5)

### 9.5.2. Description

The type of digital wallet token.

### 9.5.3. Restrictions

Base type:

  xs:token

Allowable values:

  ACQUIRER | Acquirer token
  ISSUER | Issuer token
  MERCHANT | Merchant token
  NETWORKSCHEME | Network or scheme token
  PAYMENT | Payment token

  See also: xs:enumeration (W3C XSD specification)

## simple type9.6. AccountType

### 9.6.1. Used within

Account (8.1)

### 9.6.2. Description

The type of account or wallet.

### 9.6.3. Restrictions

Base type:

  xs:token

Allowable values:

  BETTING | Betting account
  BULLION | Bullion account
  CARD | Card account
  CHEQUE | Cheque or savings account
  CUSTODY | Custodial account
  DIGTLWALLET | Digital wallet
  DIGWALL | Virtual asset wallet
  FCUR | Foreign currency account
  HIRE | Lease/hire-purchase account
  INS | Insurance policy
  INVEST | Investment account
  LOAN | Loan or mortgage account
  PENSION | Pension/annuity account
  REMIT | Remittance account
  RETIRE | Retirement savings account
  SUPER | Superannuation or approved deposit fund (ADF) account
  TRADE | Trading account
  TRUST | Trust account

  See also: xs:enumeration (W3C XSD specification)

## simple type9.7. AcctBSB

### 9.7.1. Used within

Account (8.1)

### 9.7.2. Description

Bank State Branch (BSB) is a 6-digit number to identify the Australian financial institution of where the account is held and at which branch.

The first two digits are used to identify the bank. The third digit is used to identify where the bank is located. The last three digits are used to identify the branch of the bank.

### 9.7.3. Restrictions

Base type:

  xs:token

Pattern:

  [0-9]{6}

  See also: xs:pattern (W3C XSD specification)

## simple type9.8. AcctNumber

### 9.8.1. Used within

Account (8.1)

### 9.8.2. Description

The number or identifier associated with an account, card, insurance policy or wallet.

### 9.8.3. Restrictions

Base type:

  xs:token

Maximum length:

  50

  See also: xs:maxLength (W3C XSD specification)

## simple type9.9. AcctTitle

### 9.9.1. Used within

Account (8.1)

### 9.9.2. Description

The title or name of an account, card, insurance policy or wallet associated with an individual, organisation or group of people (e.g. a joint account).

### 9.9.3. Restrictions

Base type:

  xs:string

Maximum length:

  140

  See also: xs:maxLength (W3C XSD specification)

## simple type9.10. Addr

### 9.10.1. Used within

AddressOrLocation (8.8), PostalAddress (8.32), OtherAddress (8.30), Address (8.7)

### 9.10.2. Description

Provide the unit/number and street portion of an address.

Do not provide suburb, town, city, postcode, state or country names in this field.

Notes:

1. If the address element is requesting a physical location for a business or residence address then a full street address must be provided. Post boxes or similar addresses are not acceptable.

2. If the address element is requesting a postal or alternate address then either full street addresses or post box (or similar) addresses are acceptable.

Examples of a full street address are:

- 93 Victoria Street

- 3/27 Philips Road

- First floor flat, 25 Fitzjohns Avenue

- Suite 45, Building A, 78 Hawkesbury Road

- Level 27, 45-49 Wilson Street

- Suite A, Hampton Court, Albert Lane

- Collie Downs Farm, Wirra via

Examples of a post box (or similar) address are:

- PO Box 1234

- GPO Box 5678

- Locked Bag 8899

- Private Bag 7788

- RMB 123

### 9.10.3. Restrictions

Base type:

  xs:string

Maximum length:

  140

  See also: xs:maxLength (W3C XSD specification)

## simple type9.11. AddressType

### 9.11.1. Used within

OtherAddress (8.30)

### 9.11.2. Description

Predefined description for type of address.

Main address -

- Business address for an organisation

- Residential address for an individual

Postal address - Postal address for an organisation or individual

### 9.11.3. Restrictions

Base type:

  xs:token

Allowable values:

  M | Main address
  P | Postal address

  See also: xs:enumeration (W3C XSD specification)

## simple type9.12. Amount

### 9.12.1. Used within

CurrencyAmount (8.15), AudAmount (8.11)

### 9.12.2. Description

A currency amount.

An amount can be expressed in either of the two (2) patterns below:

1. European decimal comma format – A minimum of 1 and a maximum of 15 digits to the left of the decimal point and a maximum of 2 digits to the right of the decimal point. No thousands separators. Digits to the right of the decimal point are optional but if present they must be preceded by a dot or comma as the decimal point.

   Examples:

                 78
                908.99
          786236558
            8744386,49

2. Decimal point format – A minimum of 1 and a maximum of 15 digits to the left of the decimal point. Commas as thousands separators are required. When used they must have between 1 and 3 digits to the left and exactly 3 digits to the right of each separator. A maximum of 2 digits to the right of the decimal point are allowed. If present the digits to the right of the decimal point must be preceded by a dot as the decimal point.

   Examples:

                 55
                645.81
              1,765
            983,454.00
        236,653,892.30

Notes:

1. Only a numeric value is expected. Do not use currency symbols, plus and minus signs, or embedded whitespace.

### 9.12.3. Restrictions

Base type:

  xs:token

Patterns:

  - [0-9]{1,15}([.,][0-9]{0,2})?

  - [0-9]{1,3}(,[0-9]{3}){0,4}(\.[0-9]{0,2})?

  See also: xs:pattern (W3C XSD specification)

## simple type9.13. BIC

### 9.13.1. Used within

BaseOrganisationDetails (8.12)

### 9.13.2. Description

Bank Identification Code ( The Business Identifier Code, also known as the SWIFT code – an international standard defined by the ISO 9362. It is primarily used for routing business transactions and identifying business parties in financial communications. The BIC is essential for ensuring that international payments are processed accurately and efficiently.A BIC can be either 8 characters (BIC 8) or 11 characters (BIC 11). The structure is as follows: Institution Code (4 characters): The first four characters represent the institution's name and are alphabetic (e.g., "AGIG" for a specific bank). Country Code (2 characters): The next two characters are alphabetic and represent the country where the institution is located, following the ISO 3166-1 standard (e.g., "US" for the United States). Location Code (2 characters): The following two characters can be either alphabetic or numeric and provide geographical distinction within the country (e.g., "33" for a specific city or region). Branch Code (3 characters, optional): The last three characters are optional and identify a specific branch of the institution (e.g., "XYZ" for a particular branch).The Business Identifier Code, also known as the SWIFT code – an international standard defined by the ISO 9362. It is primarily used for routing business transactions and identifying business parties in financial communications. The BIC is essential for ensuring that international payments are processed accurately and efficiently.A BIC can be either 8 characters (BIC 8) or 11 characters (BIC 11). The structure is as follows: Institution Code (4 characters): The first four characters represent the institution's name and are alphabetic (e.g., "AGIG" for a specific bank). Country Code (2 characters): The next two characters are alphabetic and represent the country where the institution is located, following the ISO 3166-1 standard (e.g., "US" for the United States). Location Code (2 characters): The following two characters can be either alphabetic or numeric and provide geographical distinction within the country (e.g., "33" for a specific city or region). Branch Code (3 characters, optional): The last three characters are optional and identify a specific branch of the institution (e.g., "XYZ" for a particular branch).BIC) is a unique code used to identify a specific bank or financial institution during international transactions.

A BIC is 8 to 11-character, alphanumeric code based on ISO 9362. BICs are an international identifier issued by the Society for Worldwide Interbank Financial Telecommunication (Swift) to its members. BICs are used to facilitate international funds transfers and the exchange of other messages between Swift members

### 9.13.3. Restrictions

Base type:

  xs:token

Pattern:

  [A-Z]{4}-?[A-Z]{2}-?[A-Z0-9]{2}(-?[0-9]{3})?

  See also: xs:pattern (W3C XSD specification)

## simple type9.14. BeneficiaryTypeOrClass

### 9.14.1. Used within

TrustDetails (8.38)

### 9.14.2. Description

Predefined descriptions for a type or class of beneficiary of a trust.

Some values are listed below:

Code | Description
--- | ---
DESCENDANT | Child, grandchild or great-grandchild of the primary beneficiary
INVESTOR | Investor
PRIMARY | Primary beneficiary
SECONDARY | Secondary beneficiary
TERTIARY | Tertiary beneficiary
RELATIVE | Other relative of the primary beneficiary
SPOUSE | Spouse or de-facto of the primary beneficiary
RELATED_ENTITY | Related entity (trust, company or other non-individual entity, which is entitled - under the terms of the trust deed - to benefit from the trust OR an entity in which a primary beneficiary is the shareholder, beneficiary or has decision-making authority)

### 9.14.3. Restrictions

Base type:

  ReferenceData

## simple type9.15. BirthDate

### 9.15.1. Used within

IndividualDetails (8.23)

### 9.15.2. Description

Date of birth of an individual.

Specify the date as per DateNoTimeZone noting the extra restrictions (shown below) limiting the date range.

### 9.15.3. Restrictions

Base type:

  DateNoTimeZone

Minimum value (inclusive):

  1870-01-01

  See also: xs:minInclusive (W3C XSD specification)

## simple type9.16. BullionType

### 9.16.1. Used within

Bullion (8.14)

### 9.16.2. Description

Type of bullion.

Some values are listed below:

Type code | Description
--- | ---
GOLD | Gold
SILVER | Silver
PLATINUM | Platinum
PALLADIUM | Palladium

### 9.16.3. Restrictions

Base type:

  ReferenceData

## simple type9.17. BusinessStructure

### 9.17.1. Used within

BaseOrganisationDetails (8.12)

### 9.17.2. Description

A predefined code representing the type of business structure for an organisation.

### 9.17.3. Restrictions

Base type:

  xs:token

Allowable values:

  A | Association | An association, such as an incorporated association, provides a means for groups, such as community groups and clubs, to set up an independent legal identity.
  C | Company | A company or corporation is a legal entity (i.e. it can enter into agreements in its own name). A company is usually made up of shareholders and officers (at least one or two directors and a secretary). Companies are usually registered with government bodies such as Australian Securities and Investments Commission.Australian Securities and Investments Commission.ASIC or its foreign equivalent.
  COOP | Co-operative | Co-operative is a business entity owned and operated by its members for their mutual benefit, often with a "one member, one vote" structure rather than control based on share volume.
  G | Government Body | A government body is an entity or emanation established under legislation of a State, Territory or the Commonwealth of Australia, or its foreign equivalent.
  P | Partnership | A partnership is a relationship or association between two (2) or more persons with a view to profit. The persons may be individuals or companies. The rights of the partnership are governed by a partnership agreement.
  T | Trust | A trust is a relationship or association between two (2) or more persons whereby one party holds assets in trust for the other. The holder of the assets is called the trustee. The trustee trades goods and services on behalf of the trust. The other party, for whom the assets are held in trust, is called the beneficiary.

  See also: xs:enumeration (W3C XSD specification)

## simple type9.18. CardType

### 9.18.1. Used within

Account (8.1)

### 9.18.2. Description

Card type.

### 9.18.3. Restrictions

Base type:

  xs:token

Allowable values:

  CARDUNKNOWN | Unknown card type
  CREDIT | Credit card
  DEBIT | Debit card
  VALCARD | Stored value card

  See also: xs:enumeration (W3C XSD specification)

## simple type9.19. CountryCode

### 9.19.1. Used within

ForeignCountryCode (9.30), AddressOrLocation (8.8), PostalAddress (8.32), OtherAddress (8.30), Address (8.7), Identification (8.22), BaseOrganisationDetails (8.12), IndividualDetails (8.23)

### 9.19.2. Description

A country expressed as a standard two-letter code as per Standard a two-letter code that represents a country name, recommended as the general purpose code published and maintained by ISO Standard a two-letter code that represents a country name, recommended as the general purpose code published and maintained by ISOISO 3166-1 alpha-2.

Below is a sample of countries known by a name other than their ISO official short name and their Alpha 2 code:

Common (other name) | ISO 3166-1 alpha-2
--- | ---
Myanmar (Burma) | MM
Timor-Leste (East Timor) | TL
United Kingdom (Great Britain) | GB
Cambodia (Kampuchea) | KH
Holy See (Vatican City) | VA
Samoa (Western Samoa) | WS

ISO 3166 is the standards document titled codes for the representation of names of countries and their subdivisions which is published and maintained by the International Organisation for Standardisation (ISO) (www.iso.org).

### 9.19.3. Restrictions

Base type:

  xs:token

Pattern:

  [A-Z]{2}

  See also: xs:pattern (W3C XSD specification)

## simple type9.20. CurrencyCode

### 9.20.1. Used within

CurrencyAmount (8.15), AudAmount (8.11)

### 9.20.2. Description

Currency code expressed as a standard three-letter code as per Standard codes for the representation of currencies and funds published and maintained by ISO Standard codes for the representation of currencies and funds published and maintained by ISOISO 4217.

Below is a sample of some well known currency codes:

Currency code | Currency name
--- | ---
AUD | Australian dollar
CAD | Canadian dollar
EUR | European Union euro
GBP | Pound sterling
HKD | Hong Kong dollar
IDR | Indonesian rupiah
JPY | Japanese yen
NZD | New Zealand dollar
SGD | Singapore dollar
THB | Thai baht
USD | United States dollar

Standard codes for the representation of currencies and funds published and maintained by ISO Standard codes for the representation of currencies and funds published and maintained by ISOISO 4217 is the standards document titled codes for the representation of currencies and funds which is published and maintained by the International Organisation for Standardisation (ISO) (www.iso.org).

### 9.20.3. Restrictions

Base type:

  xs:token

Pattern:

  ([A-Z]{3})|OTHER

  See also: xs:pattern (W3C XSD specification)

## simple type9.21. Date

### 9.21.1. Used within

<transaction> (7.8), DatetimeRange (8.17)

### 9.21.2. Description

This simple type sets the date range AUSTRAC will accept as reasonable for dates such as transaction dates.

### 9.21.3. Restrictions

Base type:

  DateNoTimeZone

Minimum value (inclusive):

  2000-01-01

  See also: xs:minInclusive (W3C XSD specification)

## simple type9.22. DateNoTimeZone

### 9.22.1. Used within

Account (8.1), Date (9.21), BirthDate (9.15)

### 9.22.2. Description

A Gregorian date in strict `YYYY-MM-DD` format with no time zone or offset information. Leading zeroes are required in both the month and day components, e.g. March is 03, not 3.

Examples of valid dates are:

- 2008-12-12

- 1964-01-31

- 2025-02-28

- 2000-02-29

Examples of invalid dates are:

- 2008-5-26 (month should be 05)

- 2007-08-32 (day is beyond upper limit)

- 2007-10-06+02:00 (offset not permitted)

- 1900-02-29 (1900 was not a leap year)

- 2008-12 (not fully specified, missing day)

- 01-10-26 (year does not conform)

- 20080-07-16 (year does not conform)

- 2008-03-261 (day does not conform)

### 9.22.3. Restrictions

Base type:

  xs:date

Pattern:

  [0-9]{4}-[0-9]{2}-[0-9]{2}

  See also: xs:pattern (W3C XSD specification)

## simple type9.23. DecimalNumber

### 9.23.1. Used within

CurrencyAmount (8.15), VirtualAsset (8.40)

### 9.23.2. Description

A decimal number with up-to 10 digital places.

An amount can be expressed in either of the two (2) patterns below:

1. European decimal comma format – A minimum of 1 and a maximum of 15 digits to the left of the decimal point and a maximum of 10 digits to the right of the decimal point. No thousands separators. Digits to the right of the decimal point are optional but if present they must be preceded by a dot or comma as the decimal point.

   Examples:

                 78
                908.992638
          786236558
            8744386,4920983

2. Decimal point format – A minimum of 1 and a maximum of 15 digits to the left of the decimal point. Commas as thousands separators are required. When used they must have between 1 and 3 digits to the left and exactly 3 digits to the right of each separator. A maximum of 10 digits to the right of the decimal point are allowed. If present the digits to the right of the decimal point must be preceded by a dot as the decimal point.

   Examples:

                 55
                645.81897
              1,765
            983,454.00
        236,653,892.30675765

Notes:

1. Only a numeric value is expected. Do not use currency symbols, plus and minus signs, or embedded whitespace.

### 9.23.3. Restrictions

Base type:

  xs:token

Patterns:

  - [0-9]{1,15}([.,][0-9]{0,10})?

  - [0-9]{1,3}(,[0-9]{3}){0,4}(\.[0-9]{0,10})?

  See also: xs:pattern (W3C XSD specification)

## simple type9.24. Description

### 9.24.1. Used within

<methodOfConductingTxn> (7.6), <transaction> (7.8), AddressOrLocation (8.8), Account (8.1), AccountTokenDetails (8.5), Identification (8.22), BaseOrganisationDetails (8.12), TrustDetails (8.38), IndividualDetails (8.23), OnlineActivity (8.26), CurrencyAmount (8.15), CurrencyAmountOther (8.16), VirtualAsset (8.40), Bullion (8.14), PreciousMetal (8.33), PreciousProduct (8.34), PreciousStone (8.35)

### 9.24.2. Description

Generic description field. Free text with a maximum allowed length of 500 characters.

### 9.24.3. Restrictions

Base type:

  xs:token

Minimum length:

  1

  See also: xs:minLength (W3C XSD specification)

Maximum length:

  500

  See also: xs:maxLength (W3C XSD specification)

## simple type9.25. DesignatedSvc

### 9.25.1. Used within

<transaction> (7.8), <otherDsProvider> (7.13)

### 9.25.2. Description

The designated services.

Refer to section 6 of the AML/CTF Act for a list of all designated services.

The enumeration descriptions below provide references to the designated services relevant to this report type.

### 9.25.3. Restrictions

Base type:

  xs:token

Allowable values:

  ACC_DEP | Account and deposit taking services | Subsection 6(2), items 1–5
  ASSET_MGMT | Asset management | Subsection 6(5B), item 3
  BET_ACC | Betting accounts | Subsection 6(4), items 11–13
  GAM_BETT | Betting services | Subsection 6(4), items 1-4
  BUS_STRUCT | Business structuring services | Subsection 6(5B), item 6
  BULSER | Buy or sell bullion | Subsection 6(3), item 1
  PRECIOUS | Buy or sell precious metals, precious stones or precious products | Subsection 6(3), item 2
  BUS_SELL | Buying, selling, or transferring a company or legal entity | Subsection 6(5B), item 2
  CHQACCSS | Chequebook access facilities | Subsection 6(2), items 14–16
  CONVEY | Conveyancing services | Subsection 6(5B), item 1
  GAM_CURR_EXCH | Currency exchange by gambling service providers | Subsection 6(4), item 14
  CUR_EXCH | Currency exchange services | Subsection 6(2), item 50
  CUST_OR_DEP | Custodial or depository services | Subsection 6(2), item 46
  BILL_DL | Dealing in bills of exchange, promissory notes or letters of credit | Subsection 6(2), item 34
  SEC_DEAL | Dealing in securities, derivatives or foreign exchange contracts | Subsection 6(2), item 33
  CRDACCSS | Debit card access facilities | Subsection 6(2), items 18-20A
  GAM_CHIP_EXCH | Exchange of gaming chips or tokens for money or virtual assets | Subsection 6(4), items 7-8
  BUS_EQ_DEBT | Facilitating business equity and debt financing | Subsection 6(5B), item 4
  CORP_LEGAL | Facilitating or performing roles in corporate/legal arrangements | Subsection 6(5B), item 7
  FACT_REC | Factoring receivables | Subsection 6(2), item 8
  FINLEASE | Finance leasing | Subsection 6(2), items 10-11
  AFSL_ARR | Financial advisory services | Subsection 6(2), item 54A
  VIR_OFFER | Financial services connected to virtual asset offer/sale | Subsection 6(2), item 50C
  BILL_FOR | Forfaiting bills of exchange or promissory notes | Subsection 6(2), item 9
  GAMCHSKL | Games of chance or skill (excluding gaming machines and lotteries) | Subsection 6(4), items 6 and 9
  GAM_MACH | Gaming machines | Subsection 6(4), items 5 and 10
  LOAN_GUA | Guaranteeing loans | Subsection 6(2), item 48
  HIREPUR | Hire-purchase | Subsection 6(2), items 12-13
  INTERMEDIARY | Intermediary services | Subsection 6(2), item 31
  BILL_ISS | Issuing bills of exchange, promissory notes or letters of credit | Subsection 6(2), item 17
  PAYORDRS | Issuing money or postal orders | Subsection 6(2), items 27-28
  SEC_SELL | Issuing or selling securities or derivatives | Subsection 6(2), item 35
  TRAVLCHQ | Issuing travellers cheques | Subsection 6(2), items 25-26
  LIFE_INS | Life or sinking fund insurance services | Subsection 6(2), items 37-39
  LOAN_MAK | Loan services | Subsection 6(2), items 6, 7 and 48–49
  NOMINEE_SHARE | Nominee shareholder services | Subsection 6(5B), item 8
  PAYROLL | Payroll services | Subsection 6(2), item 52
  PENSIONS | Providing pensions or annuities | Subsection 6(2), items 40-41
  ADDRESS | Providing registered or principal address services | Subsection 6(5B), item 9
  RED_BEAR | Redeeming bearer bonds | Subsection 6(2), item 36
  RS_NETWK | Remittance network services | Subsection 6(2), item 32A
  BUS_RSA | Retirement savings account services | Subsection 6(2), items 44-45
  SAFE_DEP | Safe deposit box facilities | Subsection 6(2), item 47
  REA_NON_BROK | Sales or transfers of real estate - non-brokered | Subsection 6(5A), item 2
  REA_BROK | Sales, purchases or transfers of real estate - brokered | Subsection 6(5A), item 1
  SHELF_CO | Shelf company services | Subsection 6(5B), item 5
  VALCARDS | Stored value card services | Subsection 6(2), items 21-24
  SUPERANN | Superannuation funds or approved deposit funds | Subsection 6(2), items 42-43
  FIN_EFT | Value transfer services | Subsection 6(2), items 29-30
  DCE | Virtual asset exchange services (with money) | Subsection 6(2), item 50A
  VIR_EXCH | Virtual asset exchange services (with other virtual assets) | Subsection 6(2), item 50B
  VIR_SAFE | Virtual asset safekeeping services | Subsection 6(2), item 46A

  See also: xs:enumeration (W3C XSD specification)

## simple type9.26. DeviceType

### 9.26.1. Used within

OnlineActivity (8.26)

### 9.26.2. Description

Type of network or device identifier, where there is a predefined type, as listed below.

### 9.26.3. Restrictions

Base type:

  xs:token

Allowable values:

  IMEI | International mobile equipment identity | 15-17 digit number usually displayed as "AA-BBBBBB-CCCCCC-D".
  IMSI | International mobile subscriber identity | 15 digit number.
  IP | Internet protocol address | 32-bit numeric, expressed as 4 numbers separated by periods. Each number can be 0-255; or 128-bit value, expressed as eight groups of four hexadecimal digits , each group value between 0 and FFFF
  MAC | Media access control address | 6-byte (48-bits) in length displayed in MM:MM:MM:SS:SS:SS format.
  SEID | Secure element identification number

  See also: xs:enumeration (W3C XSD specification)

## simple type9.27. DirectorId

### 9.27.1. Used within

Director (8.18)

### 9.27.2. Description

Director identification number (DIN or director ID).

The director ID is a 15-digit number. Australian director IDs administered by the Australian Business Registry Services (ABRS).

### 9.27.3. Restrictions

Base type:

  xs:token

Pattern:

  [0-9]{15}

  See also: xs:pattern (W3C XSD specification)

## simple type9.28. Email

### 9.28.1. Used within

BaseOrganisationDetails (8.12), IndividualDetails (8.23)

### 9.28.2. Description

An email address. Email addresses should conform to the Internet Standard RFC 5322 which, generally, can be defined as `local-part@domain-name`.

### 9.28.3. Restrictions

Base type:

  xs:token

Maximum length:

  320

  See also: xs:maxLength (W3C XSD specification)

Pattern:

  [a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}

  See also: xs:pattern (W3C XSD specification)

## simple type9.29. FiduciaryRoleType

### 9.29.1. Used within

TrustParticipant (8.39)

### 9.29.2. Description

The fiduciary role of the trust participant.

### 9.29.3. Restrictions

Base type:

  xs:token

Allowable values:

  APPOINTOR | Appointor
  GUARDIAN | Guardian
  PROTECTOR | Protector
  SETTLOR | Settlor
  TRUSTEE | Trustee

  See also: xs:enumeration (W3C XSD specification)

## simple type9.30. ForeignCountryCode

### 9.30.1. Used within

ForeignBusinessLicence (8.21)

### 9.30.2. Description

A country, other than Australia, expressed as a standard two-letter code as per ISO 3166-1 alpha-2.

ISO 3166 is the standards document titled “codes for the representation of names of countries and their subdivisions” which is published and maintained by the International Organisation for Standardisation (ISO) (www.iso.org).

### 9.30.3. Restrictions

Base type:

  CountryCode

Pattern:

  ([B-Z][A-Z]|A([A-T]|[V-Z]))

  See also: xs:pattern (W3C XSD specification)

## simple type9.31. Gender

### 9.31.1. Used within

IndividualDetails (8.23)

### 9.31.2. Description

Type of gender.

### 9.31.3. Restrictions

Base type:

  xs:token

Allowable values:

  M | Male
  F | Female
  X | Non-binary
  T | Different term

  See also: xs:enumeration (W3C XSD specification)

## simple type9.32. IdIssuer

### 9.32.1. Used within

Identification (8.22)

### 9.32.2. Description

The name of the government body or organisation that issued the identification document. The following table contains a list of some common or suggested identification document issuers by ID type:

ID type | ID issuer(s)
--- | ---
Issuer | Acronym/abbreviated name
Bank account | Various banks, building societies, credit unions and financial institutions.
Benefits card/ID | Benefit/entitlement issuers:
Centrelink | Centrelink
Department of Veteran’s Affairs | DVA
Medicare Australia | Medicare
Seniors card issuers:
National Seniors Australia | National Seniors
State of issue | Australian state or territory
Birth certificate | State of issue | Australian state or territory
Business registration/licence | Business Registration Service | BRS
Australian Securities and Investments Commission | ASIC
Credit/debit card | Various banks, building societies, credit unions, authorised deposit-taking institutions and finance companies
Customer account/ID | Various businesses and government agencies, such as: local councils for rates notices retailers for store cards utility providers for electricity, gas, telephone, water, etc.
Driver’s licence | State of issue | Australian state or territory
Australian Defence Force | ADF
Employee ID | Various employers
Employer number | Various government bodies and industry associations
Identity card/number | Various foreign governments
Membership ID | Various associations, businesses, clubs, health funds, etc.
Passport | Country of issue | Australia or foreign country
Photo ID | Proof of age card/photo card issuers:
State of issue | Australian state or territory
Firearms licence issuers:
Australian Federal Police | AFP
Northern Territory Police | NT Police
NSW Police Force | NSW Police
Queensland Police Service | QLD Police
South Australia Police | SA Police
Tasmania Police | TAS Police
Victoria Police | VicPol
Western Australia Police | WA Police
Military ID issuer:
Australian Defence Force | ADF
Security ID | State of issue | Australian state or territory
Social security ID | Centrelink | Centrelink
Social media account/user name | Various social media platforms,e.g. Facebook, Instagram, Kuaishou, LinkedIn, Reddit, Snapchat, Telegram, TikTok, WeChat, Weibo, WhatsApp, X (formerly known as Twitter), YouTube
Student ID | Various education providers such as primary schools, secondary schools, universities, technical colleges (TAFEs) and private colleges (such as language colleges)
Tax number/ID | Australian Taxation Office | ATO
State of issue | Australian state or territory
Various foreign governments |
Telephone/fax number | Various telecommunications companies

### 9.32.3. Restrictions

Base type:

  xs:token

Maximum length:

  100

  See also: xs:maxLength (W3C XSD specification)

## simple type9.33. IdNumber

### 9.33.1. Used within

Identification (8.22), ForeignBusinessLicence (8.21), OnlineActivity (8.26), Bullion (8.14), PreciousMetal (8.33), PreciousProduct (8.34), PreciousStone (8.35), RealEstate (8.36)

### 9.33.2. Description

The unique identifier/number associated with identification documents, networks, devices or systems, properties or serial numbers.

### 9.33.3. Restrictions

Base type:

  xs:token

Maximum length:

  100

  See also: xs:maxLength (W3C XSD specification)

## simple type9.34. IdType

### 9.34.1. Used within

Identification (8.22)

### 9.34.2. Description

A predefined code representing the type of identification.

### 9.34.3. Restrictions

Base type:

  xs:token

Allowable values:

  BENE | Benefits card/ID
  BUSR | Business registration/licence
  C | Credit/debit card
  D | Driver's licence
  EMID | Employee ID
  IDNT | Identity card/number
  MEMB | Membership ID
  P | Passport
  SOSE | Social security ID
  T | Telephone number
  TXID | Tax number/ID (except Australian tax file numbers (TFN))
  SOID | Social media account/user name
  DGTLID | Digital ID
  ARNU | Alien registration number
  BCNO | Birth certificate
  CUST | Customer account/ID
  EMPL | Employer number
  PHOT | Photo ID
  SECU | Security ID
  STUD | Student ID
  A | Bank account
  OVS | Online verification service

  See also: xs:enumeration (W3C XSD specification)

## simple type9.35. LEI

### 9.35.1. Used within

BaseOrganisationDetails (8.12)

### 9.35.2. Description

The Legal Entity Identifier (LEI) of the organisation.

A LEI is a globally recognised identifier for businesses similar to an ABN. It is a 20-character, alphanumeric code based on ISO 17442. LEIs are issued by organisations accredited by the Global Legal Entity Identifier Foundation (GLEIF).

### 9.35.3. Restrictions

Base type:

  xs:token

Maximum length:

  20

  See also: xs:maxLength (W3C XSD specification)

Pattern:

  [A-Z0-9]+[A-Z0-9]*

  See also: xs:pattern (W3C XSD specification)

## simple type9.36. MainAddressType

### 9.36.1. Used within

PostalAddress (8.32)

### 9.36.2. Description

Used to differentiate between different types of addresses.

### 9.36.3. Restrictions

Base type:

  xs:token

Allowable values:

  M | Business address for an organisation or Residential address for an individual

  See also: xs:enumeration (W3C XSD specification)

## simple type9.37. Name

### 9.37.1. Used within

<otherDsProvider> (7.13), BaseOrganisationDetails (8.12), TrustDetails (8.38), IndividualDetails (8.23), Director (8.18)

### 9.37.2. Description

The name of an individual or organisation.

### 9.37.3. Restrictions

Base type:

  xs:string

Maximum length:

  140

  See also: xs:maxLength (W3C XSD specification)

## simple type9.38. PhoneNum

### 9.38.1. Used within

BaseOrganisationDetails (8.12), IndividualDetails (8.23)

### 9.38.2. Description

Contact telephone number(s) (e.g. landline number or mobile number) of an individual or organisation including international access codes and area codes.

### 9.38.3. Restrictions

Base type:

  xs:token

Maximum length:

  20

  See also: xs:maxLength (W3C XSD specification)

Pattern:

  (\+\d{1,3}[- ]?)?(\(\d{1,4}\)|\d{1,4})[- ]?(\d{2,4}[- ]?)+\d{2,4}

  See also: xs:pattern (W3C XSD specification)

## simple type9.39. PhysicalCurrencyDirection

### 9.39.1. Used within

<transaction> (7.8)

### 9.39.2. Description

Indicate if the reporting entity received/exchanged or provided physical currency (i.e. cash).

### 9.39.3. Restrictions

Base type:

  xs:token

Allowable values:

  RECEIVED | Received (or currency exchanged)
  PROVIDED | Provided

  See also: xs:enumeration (W3C XSD specification)

## simple type9.40. Postcode

### 9.40.1. Used within

AddressOrLocation (8.8), PostalAddress (8.32), OtherAddress (8.30), Address (8.7)

### 9.40.2. Description

A postcode or zipcode.

### 9.40.3. Restrictions

Base type:

  xs:token

Maximum length:

  15

  See also: xs:maxLength (W3C XSD specification)

## simple type9.41. PreciousMetalType

### 9.41.1. Used within

PreciousMetal (8.33)

### 9.41.2. Description

Precious metal type.

Some values are listed below:

Type code | Description
--- | ---
ALLOY | An alloy, provide a description
GOLD | Gold
IRIDIUM | Iridium
OSMIUM | Osmium
PALLADIUM | Palladium
PLATINUM | Platinum
RHODIUM | Rhodium
RUTHENIUM | Ruthenium
SILVER | Silver
OTHER | Other, provide a description

### 9.41.3. Restrictions

Base type:

  ReferenceData

## simple type9.42. PreciousProductType

### 9.42.1. Used within

PreciousProduct (8.34)

### 9.42.2. Description

Precious product type.

Some values are listed below:

Type code | Description
--- | ---
JEWELLERY | Jewellery
WARES | Goldsmith's or silversmith's wares
WATCH | Watch
OTHER | Other object of personal adornment

### 9.42.3. Restrictions

Base type:

  ReferenceData

## simple type9.43. PreciousStoneType

### 9.43.1. Used within

PreciousStone (8.35)

### 9.43.2. Description

Precious stone type.

Some values are listed below:

Type code | Description
--- | ---
BERYL | Beryl (e.g. emerald, morganite)
CORUNDUM | Corundum (e.g. ruby, sapphire)
DIAMOND | Diamond
GARNET | Garnet
JADE | Jadeite/jade
OPAL | Opal
PEARL | Pearl
TOPAZ | Topaz

### 9.43.3. Restrictions

Base type:

  ReferenceData

## simple type9.44. ReferenceData

### 9.44.1. Used within

TrustType (9.54), BeneficiaryTypeOrClass (9.14), BullionType (9.16), PreciousMetalType (9.41), PreciousProductType (9.42), PreciousStoneType (9.43)

### 9.44.2. Description

Reference data code (i.e. one of the allowable values).

### 9.44.3. Restrictions

Base type:

  xs:token

Maximum length:

  20

  See also: xs:maxLength (W3C XSD specification)

Pattern:

  [A-Z_]*

  See also: xs:pattern (W3C XSD specification)

## simple type9.45. ReferenceNumber

### 9.45.1. Used within

TRN (9.50)

### 9.45.2. Description

A reference number.

### 9.45.3. Restrictions

Base type:

  xs:token

Maximum length:

  60

  See also: xs:maxLength (W3C XSD specification)

## simple type9.46. ReportCount

### 9.46.1. Used within

<ttrList> (6.1)

### 9.46.2. Description

The number of reports of threshold transactions within the XML document.

### 9.46.3. Restrictions

Base type:

  positiveInt

Maximum value (inclusive):

  50000

  See also: xs:maxInclusive (W3C XSD specification)

## simple type9.47. SpecialReportingActivityId

### 9.47.1. Used within

<header> (7.2)

### 9.47.2. Description

An optional identification code that has been pre-arranged with Australian Transaction Reports and Analysis Centre Australian Transaction Reports and Analysis CentreAUSTRAC to signify that this report is part of a special reporting activity.

For example, a pre-arranged back capture of historical reports or the resubmission of a set of reports.

If the report is not part of a pre-arranged special reporting activity, then please omit this element.

### 9.47.3. Restrictions

Base type:

  xs:token

Maximum length:

  35

  See also: xs:maxLength (W3C XSD specification)

## simple type9.48. State

### 9.48.1. Used within

AddressOrLocation (8.8), PostalAddress (8.32), OtherAddress (8.30), Address (8.7)

### 9.48.2. Description

A standard acronym or full name designation of an Australian state or territory or foreign state, province, county, etc.

### 9.48.3. Restrictions

Base type:

  xs:token

Maximum length:

  35

  See also: xs:maxLength (W3C XSD specification)

## simple type9.49. Suburb

### 9.49.1. Used within

AddressOrLocation (8.8), PostalAddress (8.32), OtherAddress (8.30), Address (8.7)

### 9.49.2. Description

The name of a suburb, town or city.

### 9.49.3. Restrictions

Base type:

  xs:token

Maximum length:

  35

  See also: xs:maxLength (W3C XSD specification)

## simple type9.50. TRN

### 9.50.1. Used within

<transaction> (7.8)

### 9.50.2. Description

A transaction reference number assigned to the transaction by the reporting entity, if any.

### 9.50.3. Restrictions

Base type:

  ReferenceNumber

## simple type9.51. TTRFileName

### 9.51.1. Used within

<ttrList> (6.1)

### 9.51.2. Description

File name format of an XML document containing TTR reports (see Section 3.3, “File naming convention”)

### 9.51.3. Restrictions

Base type:

  xs:token

Pattern:

  [tT][tT][rR]20[0-9][0-9](0[1-9]|1[0-2])(0[1-9]|[1-2][0-9]|3[0-1])[0-9]{1,8}\.[xX][mM][lL]

  See also: xs:pattern (W3C XSD specification)

## simple type9.52. Time

### 9.52.1. Used within

<transaction> (7.8), DatetimeRange (8.17)

### 9.52.2. Description

A time component in a strict `hh:mm:ss` format.

Examples of valid times are:

- 00:55:12

- 15:55:12

- 22:55:12

Examples of invalid times are:

- 24:55:12 (hour is beyond upper limit)

- 20-10-06 (invalid format)

### 9.52.3. Restrictions

Base type:

  xs:time

Pattern:

  ([0,1][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]

  See also: xs:pattern (W3C XSD specification)

## simple type9.53. TransactionMethod

### 9.53.1. Used within

<methodOfConductingTxn> (7.6)

### 9.53.2. Description

An enumeration type to indicate how the transaction was conducted, for when:

1. A deposit service, such as an ATM or night safe deposit, where there was no contact between a representative of the reporting entity and the customer and/or the individual who conducted the transaction;

2. A payroll or cash courier service was involved; or

3. Some other method where it was not possible to determine who conducted the transaction.

### 9.53.3. Restrictions

Base type:

  xs:token

Allowable values:

  C | For transactions utilising a payroll or cash courier service to conduct the transaction.
  A | For deposit transactions made via an automatic teller machine (ATM).
  N | For deposit transactions made via an express deposit, night safe, quick drop or similar facility.

  See also: xs:enumeration (W3C XSD specification)

## simple type9.54. TrustType

### 9.54.1. Used within

TrustDetails (8.38)

### 9.54.2. Description

A predefined code representing the type of the trust.

Some values are listed below:

Trust code | Description
--- | ---
BARE | Bare trust
DISCRET | Discretionary trust
CHARITY | Charitable trust
FIXED | Fixed trust
HYBRID | Hybrid trust
PROTECT | Protective trust
DISABILITY | Special disability trust
SUPERANN | Superannuation trust
TESTAMENT | Testamentary trust
UNIT | Unit trust

### 9.54.3. Restrictions

Base type:

  ReferenceData

## simple type9.55. YesNo

### 9.55.1. Used within

<ttr> (7.1), <header> (7.2), <customer> (7.3), <otherPerson> (7.5), <recipient> (7.7), LppDetails (8.24), Account (8.1), BaseOrganisationDetails (8.12), OrganisationDetails (8.29), EntityOrganisationDetails (8.20), TrustDetails (8.38), IndividualDetails (8.23)

### 9.55.2. Description

Yes/No indicator.

### 9.55.3. Restrictions

Base type:

  xs:token

Allowable values:

  Y | Yes
  N | No

  See also: xs:enumeration (W3C XSD specification)

## simple type9.56. positiveInt

### 9.56.1. Used within

ReportCount (9.46)

### 9.56.2. Description

Any positive integer greater than zero and composed of decimal numerals.

### 9.56.3. Restrictions

Base type:

  xs:int

Minimum value (inclusive):

  1

  See also: xs:minInclusive (W3C XSD specification)

# Part III. Appendices

## Appendix A. "Other money provided" transaction type

The below table show the possible transactions that could be conducted as part of a designated service.

Transactions that involve receiving cash and providing a product, service or instrument are provided below.

Financial services

Designated service | Transaction type |
--- | --- | ---
<otherMoneyProvided> |
ACC_DEP | Account and deposit taking services | Bank cheques issued | <bco>
Bank drafts issued | <bdo>
Cheques issued | <cho>
Contribution/premium | <cpo>
Domestic value transfer sent | <dto>
Funds to account | <fao>
International value transfer sent | <ato>
LOAN_MAK | Loan services | Loan repayment | <lro>
LOAN_GUA | Guaranteeing loans
FINLEASE | Finance leasing | Hire purchase/finance lease payment | <hpo>
HIREPUR | Hire-purchase
CHQACCSS | Chequebook access facilities | Bank cheques issued | <bco>
Bank drafts issued | <bdo>
Cheques issued | <cho>
Funds to account | <fao>
BILL_ISS | Issuing bills of exchange, promissory notes or letters of credit | Negotiable debt instruments | <ndo>
CRDACCSS | Debit card access facilities | Funds to account | <fao>
VALCARDS | Stored value card services | Stored value cards issued | <sio>
Stored value cards topped up | <sto>
TRAVLCHQ | Issuing traveller's cheques | Traveller's cheques issued | <tco>
PAYORDRS | Issuing money or postal orders | Money/postal orders issued | <moo>
FIN_EFT INTERMEDIARY RS_NETWK | Value transfer services Intermediary services Remittance network services | Domestic value transfer sent | <dto>
International value transfer sent | <ito>
SEC_DEAL | Dealing in securities, derivatives or foreign exchange contracts | Securities | <seo>
BILL_DL | Dealing in bills of exchange, promissory notes or letters of credit | Negotiable debt instruments | <ndo>
RED_BEAR | Redeeming bearer bonds
SEC_SELL | Issuing or selling securities or derivatives | Derivatives/futures | <dfo>
Securities | <seo>
LIFE_INS | Life or sinking fund insurance services | Contribution/premium | <cpo>
PENSIONS | Providing pensions or annuities
SUPERANN | Superannuation funds or approved deposit funds
BUS_RSA | Retirement savings account services
DCE | Virtual asset exchange services (with money) | Virtual asset | <dco>
VIR_OFFER | Financial services connected to virtual asset offer/sale
PAYROLL | Payroll services | Prepare payroll | <pyo>

Bullion and precious metals, stones and products

Designated service | Transaction type |
--- | --- | ---
<otherMoneyProvided> |
BULSER | Buy or sell bullion | Bullion | <buo>
PRECIOUS | Buy or sell precious metals, precious stones or precious products | Precious metal | <pmo>
Precious products | <ppo>
Precious stones | <pso>

Gambling services

Designated service | Transaction type |
--- | --- | ---
<otherMoneyProvided> |
GAM_BETT | Betting services | Bet placed | <bpo>
GAMCHSKL | Games of chance or skill (excluding gaming machines and lotteries) | Buy in to a game | <bio>
GAM_CHIP_EXCH | Exchange of gaming chips or tokens for money or virtual assets | Gambling chips/tokens issued | <gco>
Marker redemption | <mro>
BET_ACC | Betting accounts | Funds to account | <fao>

Real estate services

Designated service | Transaction type |
--- | --- | ---
<otherMoneyProvided> |
REA_BROK REA_NON_BROK | Sales, purchases or transfers of real estate - brokered Sales or transfers of real estate - non-brokered | Deposit payment for real estate | <rdo>
Settlement payment for real estate | <rso>

Professional services

Designated service | Transaction type |
--- | --- | ---
<otherMoneyProvided> |
CONVEY | Conveyancing services | Conveyancer service | <cvo>
Hold funds on behalf of a buyer of real estate | <rho>
BUS_SELL | Buying, selling, or transferring a company or legal entity | Business controlling interest transfer | <bno>
Business ownership transfer | <bto>
ASSET_MGMT | Asset management | Manage property as a settlor of an express trust | <pto>
Receive funds in escrow | <eso>
Receive funds to be managed | <fmo>
BUS_EQ_DEBT | Facilitating business equity and debt financing | Equity or debt financing | <edo>
SHELF_CO | Shelf company services | Shelf company | <cso>
Transfer of a shelf company | <cto>
BUS_STRUCT | Business structuring services | Administration/liquidation of business | <blo>
Merger/acquisition | <bmo>
Restructure a business | <bro>
Set up/establish a business | <beo>
Winding up/closure of business | <bwo>
CORP_LEGAL | Facilitating or performing roles in corporate/legal arrangements | Act as a company officer or equivalent | <boo>
Act as a power of attorney, partner, trustee or equivalent | <pxo>
NOMINEE_SHARE | Nominee shareholder services | Act as a nominee shareholder | <nso>
ADDRESS | Providing registered or principal address services | Business address | <bao>

## Appendix B. "Other money received" transaction type

The below table show the possible transactions that could be conducted as part of a designated service.

Transactions that involve providing cash and receiving a product, service or instrument are provided below.

Financial services

Designated service | Transaction type |
--- | --- | ---
<otherMoneyReceived> |
ACC_DEP | Account and deposit taking services | Bank cheques | <bci>
Bank drafts | <bdi>
Benefit payment/payout | <bpi>
Cheques | <chi>
Domestic value transfer received | <dti>
Funds from account | <fai>
International value transfer received | <iti>
LOAN_MAK | Loan services | Loan drawdown | <ldi>
LOAN_GUA | Guaranteeing loans
FACT_REC | Factoring receivables | Negotiable debt instruments | <ndi>
BILL_FOR | Forfaiting bills of exchange or promissory
CHQACCSS | Chequebook access facilities | Bank cheques | <bci>
Bank drafts | <bdi>
Cheques | <chi>
Funds from account | <fai>
CRDACCSS | Debit card access facilities | Funds from account | <fai>
VALCARDS | Stored value card services | Stored value cards | <svi>
TRAVLCHQ | Issuing traveller's cheques | Traveller's cheques | <tci>
PAYORDRS | Issuing money or postal orders | Money/postal orders | <moi>
FIN_EFT INTERMEDIARY RS_NETWK | Value transfer services Intermediary services Remittance network services | Domestic value transfer received | <dti>
International value transfer received | <iti>
SEC_DEAL | Dealing in securities, derivatives or foreign exchange contracts | Derivatives/futures | <dfi>
BILL_DL | Dealing in bills of exchange, promissory notes or letters of credit | Negotiable debt instruments | <ndi>
RED_BEAR | Redeeming bearer bonds
LIFE_INS | Life or sinking fund insurance services | Benefit payment/payout | <bpi>
PENSIONS | Providing pensions or annuities
SUPERANN | Superannuation funds or approved deposit funds
BUS_RSA | Retirement savings account services | Benefit payment/payout | <bpi>
Funds from account | <fai>
DCE | Virtual asset exchange services (with money) | Virtual asset | <dci>
VIR_OFFER | Financial services connected to virtual asset offer/sale

Bullion and precious metals, stones and products

Designated service | Transaction type |
--- | --- | ---
<otherMoneyReceived> |
BULSER | Buy or sell bullion | Bullion | <bui>
PRECIOUS | Buy or sell precious metals, precious stones or precious products | Precious metal | <pmi>
Precious products | <ppi>
Precious stones | <psi>

Gambling services

Designated service | Transaction type |
--- | --- | ---
<otherMoneyReceived> |
GAM_BETT | Betting services | Premium player commission/rebate | <cri>
Winning tickets (wagering) | <wti>
GAM_MACH | Gaming machines | Electronic gaming machine collect | <egi>
GAMCHSKL | Games of chance or skill (excluding gaming machines and lotteries) | Other casino prize | <oci>
GAM_CHIP_EXCH | Exchange of gaming chips or tokens for money or virtual assets | Gambling chips/tokens | <gci>
BET_ACC | Betting accounts | Funds from account | <fai>

Real estate services

Designated service | Transaction type |
--- | --- | ---
<otherMoneyReceived> |
REA_BROK REA_NON_BROK | Sales, purchases or transfers of real estate - brokered Sales or transfers of real estate - non-brokered | Deposit paid out for real estate | <rdi>
Settlement paid out for real estate | <rsi>

Professional services

Designated service | Transaction type |
--- | --- | ---
<otherMoneyReceived> |
CONVEY | Conveyancing services | Deposit paid out for real estate | <rdi>
Settlement paid out for real estate | <rsi>
ASSET_MGMT | Asset management | Disburse funds in escrow | <esi>
Disburse property to purchase an asset | <pdi>
Make payments on behalf of a customer | <cbi>

## Appendix C. Glossary of terms and abbreviations

ABN

  Australian Business Number – this registration number is issued by the ATO.

ACN

  Australian Company Number – this registration number is issued by the ASIC.

ADF

  approved deposit fund

AFSL

  Australian financial service licence – this type of licence is issued by the Australian Securities and Investments Commission (ASIC).

AML/CTF Act

  Anti-money Laundering and Counter-Terrorism Financing Act 2006

AML/CTF Rules

  Anti-Money Laundering and Counter-Terrorism Financing Rules 2025

ASCII

  American Standard Code for Information Interchange. A 7-bit character encoding defining 128 control codes and characters.

ASIC

  Australian Securities and Investments Commission.

ATO

  Australian Taxation Office

AUD

  Australian dollars – AUD is the three-letter ISO 4217 currency code for Australia dollars.

AUSTRAC

  Australian Transaction Reports and Analysis Centre

AUSTRAC Online

  AUSTRAC’s internet based system for reporting entities. Apart from the many features of AUSTRAC Online, this system provides a means by which a reporting entity can electronically submit reports to AUSTRAC as part of their reporting obligations.

BIC

  The Business Identifier Code, also known as the SWIFT code – an international standard defined by the ISO 9362. It is primarily used for routing business transactions and identifying business parties in financial communications. The BIC is essential for ensuring that international payments are processed accurately and efficiently.

  A BIC can be either 8 characters (BIC 8) or 11 characters (BIC 11). The structure is as follows:

  Institution Code (4 characters): The first four characters represent the institution's name and are alphabetic (e.g., "AGIG" for a specific bank).

  Country Code (2 characters): The next two characters are alphabetic and represent the country where the institution is located, following the ISO 3166-1 standard (e.g., "US" for the United States).

  Location Code (2 characters): The following two characters can be either alphabetic or numeric and provide geographical distinction within the country (e.g., "33" for a specific city or region).

  Branch Code (3 characters, optional): The last three characters are optional and identify a specific branch of the institution (e.g., "XYZ" for a particular branch).

BSB

  Bank State Branch number – a number which identifies where an account is held and with which Australian financial institution.

Code page

  A character set encoding. Usually a subset of a family of character set encodings that share the same value space. For example, `Windows-1252` (Western European) and `Windows-1256` (Arabic) are two of many Windows code pages (character sets) that each define 256 code points in the value space #x00..#xFF.

Control code

  A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).

EBCDIC

  Extended Binary Coded Decimal Interchange Code. A generic term for a variety of code page specific encodings that specify 256 control codes and characters using 8-bit values.

Element (XML)

  An element is a portion of an XML document which either begins and ends with a matching pair of start and end tags, or consists only of an empty-element tag. See Section D.1.1, “Key terminology” for more information.

Financial institution

  A financial institution is defined in section 5 of the AML/CTF Act, and means an authorised deposit-taking institution (ADI), or a bank, or a building society, or a credit union or a person specified in the AML/CTF Rules.

HTTP

  Hypertext Transfer Protocol – an internet protocol for transferring data between computer systems.

IP

  Internet protocol

ISO

  International Organisation for Standardisation (www.iso.org)

ISO 3166

  Standard codes for the representation of names of countries and their subdivisions published and maintained by ISO

ISO 3166-1 alpha-2

  Standard a two-letter code that represents a country name, recommended as the general purpose code published and maintained by ISO

ISO 4217

  Standard codes for the representation of currencies and funds published and maintained by ISO

LEI

  Legal Entity Identifier - a 20-character alphanumeric code which conforms to ISO 17422 and is overseen by the Global Legal Entity Identifier Foundation (GLEIF).

Partner agency

  AUSTRAC works closely with a range of Australian government partners that have functions, or are responsible for, or deals with law enforcement, investigation of corruption, intelligence, national security, protection of public revenue, regulation, social justice, etc. For a list of AUSTRAC's government partners, refer to the AUSTRAC website.

Person

  A reference to a person in this document means an individual, a company, a trust, a partnership, a corporation sole or a body politic.

Physical currency

  defined under section 5 of the AML/CTF Act, the coin and printed money (i.e. legal tender or cash currency) of a currency.

Reporting entity

  A person or organisation, carrying on a business, which has obligations under the AML/CTF Act (refer to section 5 of the AML/CTF Act).

RFC 1867

  Request For Comments, No. 1867 – form-based file upload in hypertext markup language (HTML). A specification for an internet based protocol used for transferring files between computer systems. Refer to www.faqs.org/rfcs/rfc1867.html for details.

RSA

  retirement savings account

Suspicious matter report (SMR)

  A report made under section 41 of the AML/CTF Act, where the reporting entity formed a suspicion of a matter that may be related to an offence, such as money laundering, the financing of terrorism, proceeds of crime, tax evasion, a person is not who they claim to be, or any other offence under an Australian Commonwealth, State or Territory law.

SWIFT

  Society for Worldwide Interbank Financial Telecommunication – an organisation which facilitates electronic funds transfer between financial and other institutions. Refer to www.swift.com for further details.

Tag (XML)

  A tag is part of an XML document that begins with `<` and ends with `>` and is used to markup/identify (give meaning to) content. See Section D.1.1, “Key terminology” for more information.

Threshold transaction report (TTR)

  A report made under section 43 of the AML/CTF Act of a transaction involving the transfer of physical currency valued at A$10,000 or more (or its foreign equivalent).

URL

  Uniform Resource Locator – a unique address associated with a resource such as a file, server, etc. located on the internet.

UTF-8

  8-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.

UTF-16

  16-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.

UTF-32

  32-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.

Virtual asset

  Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.

  Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.

W3C

  World Wide Web Consortium - an international consortium of organisations for the development of platform independent web standards and specifications for the internet (www.w3.org).

XML

  Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.

XML schema

  XML schema defines the structure of an XML document in terms of constraints. The XML schema specification is published and maintained by W3C.

XSD

  XML schema definition – XML schema defines the structure of an XML document in terms of constraints. The XML schema specification is published and maintained by W3C.

## Appendix D. XML Overview

XML (extensible markup language) defines a set of rules for encoding (marking-up) documents in a textual data format.

## D.1. Document data/content

### D.1.1. Key terminology

This section provides a brief description of commonly used terminology and constructs. For comprehensive information please refer to the XML specification which is published and maintained by the World Wide Web Consortium (W3C) (www.w3.org).

Markup and Content

  XML documents contain both markup and content. Markup can be identified as:

  - beginning and ending with `<` and `>` characters; or
  - beginning and ending with `&` and `;` characters.

  Other text in the document which is not markup is content.

Tag

  A tag is markup that begins with `<` and ends with `>` . There are three kinds of tag:

  - start-tags, e.g. `<address>`,
  - end-tags, e.g. `</address>`, and
  - empty-element tags, e.g. `<address/>`.
Element

  An element is a portion of the XML document which either begins and ends with a matching pair of start and end tags, or consists only of an empty-element tag.

  Any content nested within the start and end tags is the element’s content, and it may contain markup. Any elements nested within the start and end tags are known as child elements.

  In the example below the elements title, bsb and number are child elements of the account element. The text between the tags, like John Citizen, is content.

      <account>
        <title>John Citizen</title>
        <bsb>111222</bsb>
        <number>777888999</number>
      </account>

Attribute

  An attribute is markup that consists of a name-value pair and appears within a start tag or an empty-element tag.

  In the example below there is one attribute named id with a value of AB-1234.

      <transaction id="ABC-1234">

Escaping

  There are five predefined entities to use to escape the characters used to identify markup. Use:

  `&lt;`

    to write a less-than (`<`) character,

  `&gt;`

    to write a greater-than (`>`) character,

  `&amp;`

    to write an ampersand (`&`) character,

  `&apos;`

    to write a single-quote/apostrophe (`'`) character – this is only necessary when required to write single-quotes/apostrophes within an attribute value that has been quoted with single-quotes,

  `&quot;`

    to write a double-quote (`"`) character – this is only necessary when required to write double-quotes within an attribute value that has been quoted with double-quotes.

  The example below shows how to write an ampersand in a name:

      <fullName>Jim &amp; Sons Pty Ltd</fullName>

CDATA section

  Character data section – an XML language construct to instruct XML parsers to ignore any character data within the section thus preserving the contents of the section in its entirety (including whitespace). A CDATA section starts with `<![CDATA[` and ends with `]]>`. The example below shows how to use a CDATA section:

      <comment><![CDATA[Preserving  contents   &   spacing  is  sometimes   necessary]]></comment>

XML declaration

  XML documents may declare some information about themselves at the beginning of the document. It is common to declare XML version and the character set encoding, e.g.

      <?xml version="1.0" encoding="UTF-8"?>

## D.2. Document structure

### D.2.1. Well-formed

XML documents provided to AUSTRAC must be well-formed. The XML specification defines well-formed to mean that the XML document conforms to syntax rules in the specification. Some of the key syntax rules are:

- The document has a single root element that contains all other elements.

- For every start tag there is a matching end tag.

- Elements are correctly nested. That is, an element’s start and end tags are wholly within a parent element’s start and end tags – there is no overlap.

- Element tags are case-sensitive, the start and end tags must match exactly.

- The special markup syntax characters, such as & and < only appear as markup and not as content.

XML documents that are not well-formed cannot be parsed or processed by AUSTRAC and an error message will be returned.

### D.2.2. Schema-valid

XML documents can be valid in that they conform to a structure/grammar defined in a schema.

All XML documents provided to AUSTRAC must be schema-valid, and declare which schema they are valid against via the namespace attribute (`xmlns`) in the root element.

XML documents that are not schema-valid cannot be processed by AUSTRAC and an error message will be returned.

### D.2.3. Other validation

The transaction reports supplied to AUSTRAC in XML documents must also meet the requirements of the AML/CTF Act and the AML/CTF Rules.

AUSTRAC carries out extra validation that complements the well-formed and schema-valid constraints.

## D.3. Document encoding

Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML documents can be encoded using a variety of characters sets. Each character set specifies how A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes and characters (code points) in that set are mapped to numeric values (stored as bytes) in a file. Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.Extensible markup language – describes a set of rules for encoding documents. The XML specification is published and maintained by W3C.XML documents can also be encoded with a byte order mark (BOM) at the beginning of the file.

### D.3.1. Character set encoding

AUSTRAC uses UTF-8 character encoding and so prefers UTF-8 encoded XML documents. However, AUSTRAC can also accept XML documents with a different character encoding provided that the encoding type is declared at the start of the XML document.

Some common character set file encodings are:

> American Standard Code for Information Interchange. A 7-bit character encoding defining 128 control codes and characters.American Standard Code for Information Interchange. A 7-bit character encoding defining 128 control codes and characters.ASCII

>   Defines 128 A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes and characters (code points) using 7-bit values. ASCII encoded files should have their 7-bit code points stored in separate 8-bit bytes with the eighth bit set to zero. Any bytes with a value in the range #x80..#xFF are considered to be errors.

> 8-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.8-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.UTF-8

>   Defines A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes and characters (code points) in the Unicode standard using between one and four 8-bit values. It is backward compatible with American Standard Code for Information Interchange. A 7-bit character encoding defining 128 control codes and characters.American Standard Code for Information Interchange. A 7-bit character encoding defining 128 control codes and characters.ASCII in that the first 128 code points are aligned. It is not backward compatible with the upper 128 characters and A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes from Windows-1252, ISO-8859-1, or other Extended ASCII 8-bit character sets.

> 16-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.16-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.UTF-16

>   Defines A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes and characters (code points) in the Unicode standard using between one and two 16-bit values.

> 32-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.32-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.UTF-32

>   Defines A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes and characters (code points) in the Unicode standard using one 32-bit value.

> ISO-8859-1

>   A Western European A character set encoding. Usually a subset of a family of character set encodings that share the same value space. For example, `Windows-1252` (Western European) and `Windows-1256` (Arabic) are two of many Windows code pages (character sets) that each define 256 code points in the value space #x00..#xFF.A character set encoding. Usually a subset of a family of character set encodings that share the same value space. For example, `Windows-1252` (Western European) and `Windows-1256` (Arabic) are two of many Windows code pages (character sets) that each define 256 code points in the value space #x00..#xFF.code page that defines 256 A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes and characters (code points) using 8-bit values. The lower 128 code points match those of American Standard Code for Information Interchange. A 7-bit character encoding defining 128 control codes and characters.American Standard Code for Information Interchange. A 7-bit character encoding defining 128 control codes and characters.ASCII. The uppers 128 code points add A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes and Western European characters. ISO-8859-1 is commonly confused with Windows-1252; they differ in the value range #x80..#x9F.

> Windows-1252

>   A Western European A character set encoding. Usually a subset of a family of character set encodings that share the same value space. For example, `Windows-1252` (Western European) and `Windows-1256` (Arabic) are two of many Windows code pages (character sets) that each define 256 code points in the value space #x00..#xFF.A character set encoding. Usually a subset of a family of character set encodings that share the same value space. For example, `Windows-1252` (Western European) and `Windows-1256` (Arabic) are two of many Windows code pages (character sets) that each define 256 code points in the value space #x00..#xFF.code page that defines 256 A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes and characters (code points) using 8-bit values. The lower 128 code points match those of American Standard Code for Information Interchange. A 7-bit character encoding defining 128 control codes and characters.American Standard Code for Information Interchange. A 7-bit character encoding defining 128 control codes and characters.ASCII. The uppers 128 code points add Western European characters. Windows-1252 is commonly confused with ISO-8859-1; they differ in the value range #x80..#x9F.

> IBM500

>   Is an Extended Binary Coded Decimal Interchange Code. A generic term for a variety of code page specific encodings that specify 256 control codes and characters using 8-bit values.Extended Binary Coded Decimal Interchange Code. A generic term for a variety of code page specific encodings that specify 256 control codes and characters using 8-bit values.EBCDIC Western European A character set encoding. Usually a subset of a family of character set encodings that share the same value space. For example, `Windows-1252` (Western European) and `Windows-1256` (Arabic) are two of many Windows code pages (character sets) that each define 256 code points in the value space #x00..#xFF.A character set encoding. Usually a subset of a family of character set encodings that share the same value space. For example, `Windows-1252` (Western European) and `Windows-1256` (Arabic) are two of many Windows code pages (character sets) that each define 256 code points in the value space #x00..#xFF.code page that defines 256 A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes and characters (code points) using 8 bits values.

> IBM1047

>   Is an Extended Binary Coded Decimal Interchange Code. A generic term for a variety of code page specific encodings that specify 256 control codes and characters using 8-bit values.Extended Binary Coded Decimal Interchange Code. A generic term for a variety of code page specific encodings that specify 256 control codes and characters using 8-bit values.EBCDIC Western European A character set encoding. Usually a subset of a family of character set encodings that share the same value space. For example, `Windows-1252` (Western European) and `Windows-1256` (Arabic) are two of many Windows code pages (character sets) that each define 256 code points in the value space #x00..#xFF.A character set encoding. Usually a subset of a family of character set encodings that share the same value space. For example, `Windows-1252` (Western European) and `Windows-1256` (Arabic) are two of many Windows code pages (character sets) that each define 256 code points in the value space #x00..#xFF.code page that defines 256 A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes and characters (code points) using 8 bits values.

Do not use the following character set file encodings:

> Extended ASCII

>   This is not a recognised encoding and should not be specified. It is a generic term for a variety of A character set encoding. Usually a subset of a family of character set encodings that share the same value space. For example, `Windows-1252` (Western European) and `Windows-1256` (Arabic) are two of many Windows code pages (character sets) that each define 256 code points in the value space #x00..#xFF.A character set encoding. Usually a subset of a family of character set encodings that share the same value space. For example, `Windows-1252` (Western European) and `Windows-1256` (Arabic) are two of many Windows code pages (character sets) that each define 256 code points in the value space #x00..#xFF.code page specific encodings, like Windows-1252 and ISO-8859-1, that specify A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes and characters (code points) using 8-bit values. The lower 128 code points are often identical to American Standard Code for Information Interchange. A 7-bit character encoding defining 128 control codes and characters.American Standard Code for Information Interchange. A 7-bit character encoding defining 128 control codes and characters.ASCII. The upper 128 code points are highly dependent on the operating system and regional languages being used.

> Extended Binary Coded Decimal Interchange Code. A generic term for a variety of code page specific encodings that specify 256 control codes and characters using 8-bit values.Extended Binary Coded Decimal Interchange Code. A generic term for a variety of code page specific encodings that specify 256 control codes and characters using 8-bit values.EBCDIC

>   This is not a recognised encoding and should not be specified. It is a generic term for a variety of A character set encoding. Usually a subset of a family of character set encodings that share the same value space. For example, `Windows-1252` (Western European) and `Windows-1256` (Arabic) are two of many Windows code pages (character sets) that each define 256 code points in the value space #x00..#xFF.A character set encoding. Usually a subset of a family of character set encodings that share the same value space. For example, `Windows-1252` (Western European) and `Windows-1256` (Arabic) are two of many Windows code pages (character sets) that each define 256 code points in the value space #x00..#xFF.code page specific encodings, like IBM1047 and IBM500, that specify A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes and characters (code points) using 8-bit values.

### D.3.2. Byte order mark (BOM)

The byte order mark (BOM) is the Unicode character code U+FEFF at the beginning of a file or data stream containing Unicode A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).A code point in a character set that represents an instruction rather than a written symbol. Control codes are also known as control characters, and non-printing characters. (e.g. tab, new-line, carriage return characters, etc.).control codes and characters.

The BOM is used to:

1. Signal endianness (byte order) of the multibyte values used for 16-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.16-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.UTF-16 and 32-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.32-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.UTF-32; or

2. Enable deduction of the character set encoding by observing the initial byte values. For example, a BOM could make it clear that the character set is 8-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.8-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.UTF-8 and not some other 8-bit encoding like Windows-1252 or ISO-8859-1.

A BOM must not be provided if the encoding specifies the endianness; do not provide a BOM if you have specified the encoding as UTF-16BE, UTF-16LE, UTF-32BE, or UTF-32LE.

Different character set encodings of the BOM will result in different initial byte values being observed at the beginning of the file or data stream. For example:

Encoding | Endianness | Observed bytes (hexadecimal) | Observed bytes (decimal) | Observed characters (Windows-1252)
--- | --- | --- | --- | ---
UTF-8 | `` | `EF BB BF` | `239 187 191` | `ï»¿`
UTF-16 | big-endian | `FE FF` | `254 255` | `þÿ`
UTF-16 | little-endian | `FF FE` | `255 254` | `ÿþ`
UTF-32 | big-endian | `00 00 FE FF` | `0 0 254 255` | `□□ÿþ`
UTF-32 | little-endian | `FF FE 00 00` | `255 254 0 0` | `þÿ□□`

#### D.3.2.1. Big-endian versus little-endian

Endianness (byte order) refers to how numbers are stored and used within a computer.

Big-endian computers store their numbers with the most-significant bytes (and the digits those bytes represent) leftmost in the data structure. This reflects how we write numbers.

Little-endian computers store their numbers with the most-significant bytes (and the digits those bytes represent) rightmost in the data structure. This is contrary to how we write numbers.

The table below shows some 2-byte representations of numbers in their big and little endian forms:

Number (decimal) | Number (hexadecimal) | Big-endian representation | Little-endian representation
--- | --- | --- | ---
`0` | `0` | `00 00` | `00 00`
`1` | `1` | `00 01` | `01 00`
`36` | `24` | `00 24` | `24 00`
`424` | `1A8` | `01 A8` | `A8 01`
`5288` | `14A8` | `14 A8` | `A8 14`
`10404` | `28A4` | `28 A4` | `A4 28`
`32994` | `80E2` | `80 E2` | `E2 80`
`65535` | `FFFF` | `FF FF` | `FF FF`

### D.3.3. UTF-8 encoding

UTF-8 is a variable width encoding – it represents each character using between one and four bytes/octets. The table below shows how characters are encoded into one to four bytes/octets.

Unicode character range (hexadecimal) | Bytes/octets per character | UTF-8 byte/octet sequence (binary)
--- | --- | ---
`U+0000 - U+007F` | `1` | `0xxxxxxx`
`U+0080 - U+07FF` | `2` | `110xxxxx 10xxxxxx`
`U+0800 - U+FFFF` | `3` | `1110xxxx 10xxxxxx 10xxxxxx`
`U+010000 - U+10FFFF` | `4` | `11110xxx 10xxxxxx 10xxxxxx 10xxxxxx`

Use the above information to encode characters using UTF-8. For each character:

1. Determine the number of octets required.

2. Prepare the most-significant (high-order) bits of each octet sequence as shown.

3. Spread the binary bits of your character across the positions marked with x.

The above is a brief overview of UTF-8 encoding. The complete Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org). They also provide a frequently asked questions (FAQs) page dedicated to UTF-8, UTF-16, UTF-32 and BOM queries.

AUSTRAC has observed that occasionally files have been declared as being encoded using UTF-8 when in fact they have been encoded using Windows-1252 or ISO-8859-1. See Section D.3.4.2, “Intermittent uploading problems/XML decoding problems” for a description of what occurs when this happens.

#### D.3.3.1. UTF-8 encoding examples

The table below shows some letters and words that may have been provided in names or addresses or that are commonly auto-corrected by software applications. It also shows for comparison how the letter/word would have been encoded when using the English alphabet which does not use accents/diacritics.

Letter/word | Unicode characters | Encoded bytes/octets (hexadecimal)
--- | --- | ---
UTF-8 | Windows-1252
`e` | `U+0065` | `65` | `65`
`é` | `U+00E9` | `C3 A9` | `E9`
`cafe` | `U+0063 U+0061 U+0066 U+0065` | `63 61 66 65` | `63 61 66 65`
`café` | `U+0063 U+0061 U+0066 U+00E9` | `63 61 66 C3 A9` | `63 61 66 E9`
`Lubz` | `U+004C U+0075 U+0062 U+007A` | `4C 75 62 7A` | `4C 75 62 7A`
`Lübz` | `U+004C U+00FC U+0062 U+007A` | `4C C3 BC 62 7A` | `4C FC 62 7A`
`No` | `U+004E U+006F` | `4E 6F` | `4E 6F`
`Nº` | `U+004E U+00BA` | `4E C2 BA` | `4E BA`

### D.3.4. Common file encoding problems

#### D.3.4.1. Incorrect encoding specified in XML declaration

This commonly occurs when the XML document has been encoded using the default operating system file encoding and the XML declaration within the document asserts a different encoding.

AUSTRAC uses the encoding information in the XML declaration to enable accurate decoding of the file. If this information is absent or incorrect the file may not be able to be decoded or read. It may also be difficult for AUSTRAC to provide any feedback about the quality or content of the XML document if it cannot be decoded or viewed.

#### D.3.4.2. Intermittent uploading problems/XML decoding problems

This commonly occurs when the file has been declared as being encoded in 8-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.8-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.UTF-8 but has actually been encoded using the Windows-1252 or ISO-8859-1 encoding.

The symptoms are that XML documents are accepted by AUSTRAC upload without error for months at a time until eventually a character like é appears, perhaps in a business name like Jack’s Café. In UTF-8 the character é would be encoded as two bytes (`C3 A9`) whereas in Windows-1252 or ISO-8859-1 it would be encoded with one byte (`E9`).

The problem with the character é when not encoded correctly is that it begins with the binary `1110` which signals to the UTF-8 decoder that this is part of a three-byte character encoding. The next two bytes normally fail decoding resulting in a malformed XML error.

This problem exists for all upper 127 characters encoded with Windows-1252 or ISO-8859-1 in any XML document declared as UTF-8.

This problem normally arises due to a misconception that 8-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.8-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.UTF-8 is backward compatible with extended ASCII (256 characters/code-points) which it is not. 8-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.8-bit Unicode Transformation Format. It defines an encoding to represent characters in the Unicode Standard. Unicode transformation formats are published and maintained by The Unicode Consortium (www.unicode.org) including a FAQs page dedicated to UTF-8, UTF-16, UTF-32 & BOM questions and answers.UTF-8 is only backward compatible with standard ASCII (128 characters/code-points).

## Appendix E. Schema data types

XML schema defines a set of data types which other schemas can use and build upon.

## E.1. xs:date

The date data type is based upon the ISO 8601 extended date format which is:

> `[-]YYYY-MM-DD[Z|(+|-)hh:mm]`

where:

> [-]

>   an optional leading minus sign to denote that the date is before the common era (BCE).

> YYYY

>   the year as a four-digit integer.

> MM

>   the month as a two-digit integer between 1 and 12 inclusive.

> DD

>   the day-of-month as a two-digit integer: between 1 and 30 inclusive if the month is one of 4, 6, 9, or 11; between 1 and 28 inclusive if the month is 2 and year is not divisible 4, or is divisible by 100 but not by 400; between 1 and 29 inclusive if the month is 2 and year is divisible by 400, or by 4 but not by 100; between 1 and 31 inclusive otherwise.

> [Z|(+|-)zh:mm]

>   Is an optional time zone. Use Z to specify universal coordinated time (UTC) or +/-zh:mm to specify the number of hours (zh) and minutes (mm) offset from UTC, where zh is an integer between 0 and 14 inclusive.

Notes:

1. Whitespace is collapsed before validating that the date matches the date pattern, thus leading and trailing whitespace will be ignored.

2. Collapsing whitespace involves removing any leading and trailing whitespace and replacing any contiguous blocks of interspersed whitespace with single space (#x20) characters.

3. Whitespace is considered to be tab (#x9), linefeed (#xA), carriage return (#xD) and space (#x20) characters.

4. Dates in the format YYYYMMDD are not permitted; the year, month and day integers must be separated by dashes.

See also: xs:date (W3C XSD specification)

## E.2. xs:dateTime

The dateTime data type is based upon the ISO 8601 extended date-time format which is:

> `[-]YYYY-MM-DDThh:mm:ss.sss[Z|(+|-)zh:zm]`

where:

> [-]

>   an optional leading minus sign to denote that the date is before the common era (BCE).

> YYYY

>   Year as a four-digit integer.

> MM

>   Month as a two-digit integer between 1 and 12 inclusive.

> DD

>   Day-of-month as a two-digit integer: between 1 and 30 inclusive if the month is one of 4, 6, 9, or 11; between 1 and 28 inclusive if the month is 2 and year is not divisible 4, or is divisible by 100 but not by 400; between 1 and 29 inclusive if the month is 2 and year is divisible by 400, or by 4 but not by 100; between 1 and 31 inclusive otherwise.

> T

>   The letter T separates the date portion from the time portion.

> hh

>   Hours as a two-digit integer between 0 and 23 inclusive.

> mm

>   Minutes as a two-digit integer between 0 and 59 inclusive.

> ss.sss

>   Seconds as a decimal value greater than or equal to 0 and less than 60.

> [Z|(+|-)zh:mm]

>   Is an optional time zone. Use Z to specify universal coordinated time (UTC) or +/-zh:mm to specify the number of hours (zh) and minutes (mm) offset from UTC, where zh is a two digit integer between 0 and 14 inclusive.

Notes:

1. Whitespace is collapsed before validating that the date-time matches the dateTime pattern, thus leading and trailing whitespace will be ignored.

2. Collapsing whitespace involves removing any leading and trailing whitespace and replacing any contiguous blocks of interspersed whitespace with single space (#x20) characters.

3. Whitespace is considered to be tab (#x9), linefeed (#xA), carriage return (#xD) and space (#x20) characters.

4. Date-times in the format YYYYMMDDhhmmss.sss are not permitted; the date numerals must be separated by dashes, the time numerals must be separated by colons, and the date portion must be separated from the time portion by the letter T.

See also: xs:dateTime (W3C XSD specification)

## E.3. xs:ID

Defines data that uniquely identifies an element within the XML document.

Simplistically, IDs can be composed of a contiguous set of characters, digits, dashes and underscores. For a more complete specification see the W3C schema specification definition of xs:ID.

Notes:

1. Whitespace is collapsed before validating that the ID is unique within the document, thus leading and trailing whitespace will be ignored.

2. Collapsing whitespace involves removing any leading and trailing whitespace and replacing any contiguous blocks of interspersed whitespace with single space (#x20) characters.

3. Whitespace is considered to be tab (#x9), linefeed (#xA), carriage return (#xD) and space (#x20) characters.

See also: xs:ID (W3C XSD specification)

## E.4. xs:IDREF

Defines data that references an element within the XML document using its unique identifier.

IDREFs must reference an element that exists in the document.

Notes:

1. Whitespace is collapsed before validating that the IDREF references an element within the document, thus leading and trailing whitespace will be ignored. The element IDs being compared also have their whitespace collapsed.

2. Collapsing whitespace involves removing any leading and trailing whitespace and replacing any contiguous blocks of interspersed whitespace with single space (#x20) characters.

3. Whitespace is considered to be tab (#x9), linefeed (#xA), carriage return (#xD) and space (#x20) characters.

See also: xs:IDREF (W3C XSD specification)

## E.5. xs:int

int is derived from long by setting the value of maxInclusive to be 2147483647 and minInclusive to be -2147483648. The base type of int is long.

The value space of integer is the infinite set {...,-2,-1,0,1,2,...}. The base type of integer is long.

integer has a lexical representation consisting of a finite-length sequence of decimal digits (#x30-#x39) with an optional leading sign. If the sign is omitted, "+" is assumed. For example: -1, 0, 126789675, +100000.

See also: xs:int (W3C XSD specification)

## E.6. xs:string

A string (of text) that has its whitespace preserved; leading, trailing, and interspersed blocks of whitespace (including newlines) is considered important to the data value.

Notes:

1. Any other restrictions (like minimum and maximum lengths and regular-expression patterns) are imposed upon the value of the data inclusive of all whitespace characters.

2. Whitespace is considered to be tab (#x9), linefeed (#xA), carriage return (#xD) and space (#x20) characters.

See also: xs:string (W3C XSD specification)

## E.7. xs:time

The time data type is based upon the ISO 8601 extended time format which is:

> `hh:mm:ss.sss[Z|(+|-)zh:zm]`

where:

> hh

>   Hours as a two-digit integer between 0 and 23 inclusive.

> mm

>   Minutes as a two-digit integer between 0 and 59 inclusive.

> ss.sss

>   Seconds as a decimal value greater than or equal to 0 and less than 60.

> [Z|(+|-)zh:mm]

>   Is an optional time zone. Use Z to specify universal coordinated time (UTC) or +/-zh:mm to specify the number of hours (zh) and minutes (mm) offset from UTC, where zh is a two digit integer between 0 and 14 inclusive.

Notes:

1. Whitespace is collapsed before validating that the time matches the time pattern, thus leading and trailing whitespace will be ignored.

2. Collapsing whitespace involves removing any leading and trailing whitespace and replacing any contiguous blocks of interspersed whitespace with single space (#x20) characters.

3. Whitespace is considered to be tab (#x9), linefeed (#xA), carriage return (#xD) and space (#x20) characters.

4. Times in the format hhmmss.sss are not permitted; the time numerals must be separated by colons.

See also: xs:time (W3C XSD specification)

## E.8. xs:token

A string (of text) that has its whitespace collapsed the string is said to have been tokenised.

Notes:

1. Whitespace is collapsed before other restrictions (like minimum and maximum lengths and regular-expression patterns) are imposed.

2. Collapsing whitespace involves removing any leading and trailing whitespace and replacing any contiguous blocks of interspersed whitespace with single space (#x20) characters.

3. Whitespace is considered to be tab (#x9), linefeed (#xA), carriage return (#xD) and space (#x20) characters.

See also: xs:token (W3C XSD specification)

## E.9. xs:base64Binary

Base64Binary represents Base64-encoded arbitrary binary data.

The value space of base64Binary is the set of finite-length sequences of binary octets. For base64Binary data the entire binary stream is encoded using the Base64 Alphabet, see in [RFC 2045].

The lexical forms of base64Binary values are limited to the 65 characters of the Base64 Alphabet defined in [RFC 2045], i.e. a-z, A-Z, 0-9, the plus sign (+), the forward slash (/) and the equal sign (=), together with the characters defined in [XML 1.0 (Second Edition)] as white space. No other characters are allowed.

See also: xs:base64Binary (W3C XSD specification)

## Appendix F. Sample TTR XML document

The following XML document contains examples of three (3) TTR reports for transactions relating to:

1. An account deposit by a third party;

2. An account withdrawal with a cash supplement to purchase a bank cheque by the customer;

3. An account deposit via a night safe facility.

4. A threshold transaction relating to Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.Defined under section 5B of the AML/CTF Act, a digital representation of value that functions as a medium of exchange, a store of economic value, unit of account, an investment and is not issued by or under the authority of a government body, and may be transferred, stored or traded electronically.Virtual asset is also commonly referred to as cryptocurrency, crypto asset, digital currency or virtual currency.virtual asset activity.

    <?xml version="1.0" encoding="UTF-8"?>
    <ttrList xmlns="http://austrac.gov.au/schema/reporting/TTR-1-0">
        <reAustracAccountNumber>123456789</reAustracAccountNumber>
        <submitterAustracAccountNumber>123456789</submitterAustracAccountNumber>
        <fileName>TTR2025071801.xml</fileName>
        <reportCount>4</reportCount>

        <ttr id="rpt-01">
            <lppDetails>
                <lppFlag>Y</lppFlag>
                <lppClaimForm id="rpt-01-lpp"
                              fileName="LppClaimForm.doc">U29tZSBjb250ZW50IGluIGJhc2U2NCBmb3JtYXQ=
                </lppClaimForm>
            </lppDetails>
            <customer id="cst-01-01">
                <individualDetails>
                    <fullName>John Citizen</fullName>
                    <birthDate>1972-02-12</birthDate>
                    <residentialAddress id="adr-01-02">
                        <addr>U205C/601 High Street</addr>
                        <suburb>Penrith</suburb>
                        <state>NSW</state>
                        <postcode>2751</postcode>
                        <countryCode>AU</countryCode>
                    </residentialAddress>
                    <occupationBusinessActivity>Customer Service Manager</occupationBusinessActivity>
                    <isIdentityVerified>Y</isIdentityVerified>
                    <identification id="idt-01-01">
                        <type>D</type>
                        <number>9999XX</number>
                        <issuer>RTA NSW</issuer>
                        <countryCode>AU</countryCode>
                    </identification>
                </individualDetails>
                <account id="act-01-01">
                    <type>CHEQUE</type>
                    <title>John Citizen</title>
                    <bsb>992001</bsb>
                    <number>0123456789</number>
                    <isAccountProvider>N</isAccountProvider>
                    <provider>CBA</provider>
                </account>
            </customer>
            <otherPerson id="ind-01-01">
                <individualDetails>
                    <fullName>John Brown</fullName>
                    <occupationBusinessActivity>Accountant</occupationBusinessActivity>
                </individualDetails>
                <isOnlineActivityIdentified>N</isOnlineActivityIdentified>
                <isRepresentingOrganisation>Y</isRepresentingOrganisation>
                <representsOrganisation refId="org-01-01"/>
                <isAuthorisationUsed>N</isAuthorisationUsed>
            </otherPerson>
            <representedOrganisation id="org-01-01">
                <organisationDetails>
                    <fullLegalName>Brown, Marron &amp; Co Accountants</fullLegalName>
                    <businessAddress id="adr-01-03">
                        <addr>Suite 9, 99 Herbert Street</addr>
                        <suburb>Pyrmont</suburb>
                        <state>NSW</state>
                        <postcode>2009</postcode>
                        <countryCode>AU</countryCode>
                    </businessAddress>
                </organisationDetails>
            </representedOrganisation>
            <transaction id="txn-01-01">
                <designatedService>ACC_DEP</designatedService>
                <txnLocation id="adr-01-01">
                    <addr>40A Harris Street</addr>
                    <suburb>Ultimo</suburb>
                    <state>NSW</state>
                    <postcode>2007</postcode>
                    <countryCode>AU</countryCode>
                </txnLocation>
                <txnDate>2025-10-05</txnDate>
                <txnTime>09:10:05</txnTime>
                <txnRefNo>DEP20111005-0235</txnRefNo>
                <physicalCurrencyDirection>RECEIVED</physicalCurrencyDirection>
                <moneyReceived id="mrv-01-01">
                    <cash>
                        <ausCash id="csh-01-01">
                            <currencyCode>AUD</currencyCode>
                            <amount>18000.00</amount>
                        </ausCash>
                    </cash>
                </moneyReceived>
                <moneyProvided id="mpr-01-01">
                    <cash>
                        <foreignCash id="mrv-01-01-fc1">
                            <currencyCode>EUR</currencyCode>
                            <amount>5000.00</amount>
                            <exchangeRate>0.51</exchangeRate>
                        </foreignCash>
                    </cash>
                    <otherMoneyProvided>
                        <fao id="mpr-01-01-fao">
                            <currencyCode>AUD</currencyCode>
                            <amount>18000.00</amount>
                        </fao>
                    </otherMoneyProvided>
                </moneyProvided>
                <totalAmount id="tam-01-01">
                    <currencyCode>AUD</currencyCode>
                    <amount>18000.00</amount>
                </totalAmount>
            </transaction>
            <recipient id="rcp-01-01">
                <sameAsCustomer refId="cst-01-01"/>
            </recipient>
            <isOtherDsProviderInvolved>N</isOtherDsProviderInvolved>
        </ttr>

        <ttr id="rpt-02">
            <lppDetails>
                <lppFlag>Y</lppFlag>
            </lppDetails>
            <customer id="cst-02-01">
                <individualDetails>
                    <fullName>Jane Citizen</fullName>
                    <birthDate>1976-06-25</birthDate>
                    <residentialAddress id="adr-02-02">
                        <addr>38 Burgundy Street</addr>
                        <suburb>Heidelberg</suburb>
                        <state>VIC</state>
                        <postcode>3084</postcode>
                        <countryCode>AU</countryCode>
                    </residentialAddress>
                    <occupationBusinessActivity>Chiropractor</occupationBusinessActivity>
                    <identification id="idt-02-01">
                        <type>BENE</type>
                        <number>9999999991</number>
                        <issuer>Medicare Australia</issuer>
                        <countryCode>AU</countryCode>
                    </identification>
                </individualDetails>
                <account id="act-02-01">
                    <type>CARD</type>
                    <title>Jane Citizen</title>
                    <number>0123456789</number>
                    <isAccountProvider>Y</isAccountProvider>
                    <cardType>DEBIT</cardType>
                    <isAccountHolder>Y</isAccountHolder>
                    <isAccountSignatory>Y</isAccountSignatory>
                    <openedDate>2024-05-25</openedDate>
                </account>
            </customer>
            <otherPerson id="ind-02-01">
                <sameAsCustomer refId="cst-02-01"/>
            </otherPerson>
            <transaction id="txn-02-01">
                <designatedService>ACC_DEP</designatedService>
                <txnLocation id="adr-02-01">
                    <addr>1040A La Trobe Street</addr>
                    <suburb>Docklands</suburb>
                    <state>VIC</state>
                    <postcode>3008</postcode>
                    <countryCode>AU</countryCode>
                </txnLocation>
                <txnDate>2025-10-04</txnDate>
                <txnRefNo>BCHQ20111005-0041</txnRefNo>
                <physicalCurrencyDirection>RECEIVED</physicalCurrencyDirection>
                <moneyReceived id="mrv-02-01">
                    <cash>
                        <ausCash id="csh-02-01">
                            <currencyCode>AUD</currencyCode>
                            <amount>10000.00</amount>
                        </ausCash>
                    </cash>
                    <otherMoneyReceived>
                        <fai id="mrv-02-01-fao">
                            <currencyCode>AUD</currencyCode>
                            <amount>50010.00</amount>
                        </fai>
                    </otherMoneyReceived>
                </moneyReceived>
                <moneyProvided id="mpr-02-01">
                    <otherMoneyProvided>
                        <bco id="mpr-02-01-bco">
                            <currencyCode>AUD</currencyCode>
                            <amount>60000.00</amount>
                        </bco>
                        <fco id="mpr-02-01-fco">
                            <currencyCode>AUD</currencyCode>
                            <amount>10.00</amount>
                        </fco>
                    </otherMoneyProvided>
                </moneyProvided>
                <totalAmount id="tam-02-01">
                    <currencyCode>AUD</currencyCode>
                    <amount>60010.00</amount>
                </totalAmount>
            </transaction>
            <recipient id="rcp-02-01">
                <sameAsCustomer refId="cst-02-01"/>
            </recipient>
            <isOtherDsProviderInvolved>Y</isOtherDsProviderInvolved>
            <otherDsProvider id="ds-provider-02-02">
                <fullName>Westpac Banking Corporation</fullName>
                <addressOrLocation id="ds-provider-02-02-addr">
                    <suburb>Sydney</suburb>
                    <state>NSW</state>
                    <postcode>2000</postcode>
                    <countryCode>AU</countryCode>
                    <otherLocationDetails>Corner of York street and King street</otherLocationDetails>
                </addressOrLocation>
                <designatedService>CHQACCSS</designatedService>
            </otherDsProvider>
        </ttr>

        <ttr id="rpt-03">
            <lppDetails>
                <lppFlag>N</lppFlag>
            </lppDetails>
            <customer id="cst-03-01">
                <organisationDetails>
                    <fullLegalName>Citizen Marine &amp; Automotive Group Pty Ltd</fullLegalName>
                    <abn>55999999003</abn>
                    <businessName>Citizen Prestige Cars</businessName>
                    <businessAddress id="adr-03-02">
                        <addr>1022-1028 Sterling Highway</addr>
                        <suburb>North Fremantle</suburb>
                        <state>WA</state>
                        <postcode>6159</postcode>
                        <countryCode>AU</countryCode>
                    </businessAddress>
                </organisationDetails>
                <account id="cst-03-01-act">
                    <type>CHEQUE</type>
                    <title>Citizen Marine &amp; Automotive
                        Group Pty Ltd (T/A Citizen Prestige Cars)
                    </title>
                    <bsb>996088</bsb>
                    <number>0123456789</number>
                    <isAccountProvider>Y</isAccountProvider>
                    <isAccountHolder>Y</isAccountHolder>
                    <isAccountSignatory>Y</isAccountSignatory>
                    <openedDate>2024-05-25</openedDate>
                </account>
            </customer>
            <methodOfConductingTxn id="mtx-03-01">
                <method>N</method>
            </methodOfConductingTxn>
            <transaction id="txn-03-01">
                <designatedService>ACC_DEP</designatedService>
                <txnLocation id="adr-03-01">
                    <addr>1A/88 High Street</addr>
                    <suburb>Fremantle</suburb>
                    <state>WA</state>
                    <postcode>6160</postcode>
                    <countryCode>AU</countryCode>
                </txnLocation>
                <txnDate>2025-10-05</txnDate>
                <txnRefNo>NDEP20111005-0135</txnRefNo>
                <physicalCurrencyDirection>RECEIVED</physicalCurrencyDirection>
                <moneyReceived id="mrv-03-01">
                    <cash>
                        <ausCash id="csh-03-01">
                            <currencyCode>AUD</currencyCode>
                            <amount>20000.00</amount>
                        </ausCash>
                    </cash>
                    <otherMoneyReceived>
                        <chi id="mrv-03-01-chi">
                            <currencyCode>AUD</currencyCode>
                            <amount>45950.00</amount>
                        </chi>
                        <oti id="mrv-03-01-oti">
                            <currencyCode>AUD</currencyCode>
                            <amount>55000.00</amount>
                            <description>EFTPOS Summary Slip</description>
                        </oti>
                    </otherMoneyReceived>
                </moneyReceived>
                <moneyProvided id="mpr-03-01">
                    <otherMoneyProvided>
                        <fao id="mpr-03-01-fao">
                            <currencyCode>AUD</currencyCode>
                            <amount>120950.00</amount>
                        </fao>
                    </otherMoneyProvided>
                </moneyProvided>
                <totalAmount id="tam-03-01">
                    <currencyCode>AUD</currencyCode>
                    <amount>120950.00</amount>
                </totalAmount>
            </transaction>
            <recipient id="rcp-03-01">
                <sameAsCustomer refId="cst-03-01"/>
            </recipient>
            <isOtherDsProviderInvolved>N</isOtherDsProviderInvolved>
        </ttr>

        <ttr id="rpt-04">
            <lppDetails>
                <lppFlag>N</lppFlag>
            </lppDetails>
            <customer id="cst-04-01">
                <individualDetails>
                    <fullName>Joe Citizen</fullName>
                    <residentialAddress id="adr-04-02">
                        <addr>1/380D Prospect Road</addr>
                        <suburb>Blair Athol</suburb>
                        <state>SA</state>
                        <postcode>5084</postcode>
                        <countryCode>AU</countryCode>
                    </residentialAddress>
                    <phone>0499 999 999</phone>
                    <email>citizen99@gmail.com</email>
                </individualDetails>
                <account id="act-03-01">
                    <type>DIGWALL</type>
                    <number>199ZYXhAbc87pdeFjKLH6MNo5qRSTuvWXX</number>
                </account>
            </customer>
            <otherPerson id="ind-04-01">
                <sameAsCustomer refId="cst-04-01"/>
            </otherPerson>
            <transaction id="txn-04-01">
                <designatedService>DCE</designatedService>
                <txnLocation id="adr-04-01">
                    <addr>365 Prospect Road</addr>
                    <suburb>Blair Athol</suburb>
                    <state>SA</state>
                    <postcode>5084</postcode>
                    <countryCode>AU</countryCode>
                </txnLocation>
                <txnDate>2018-04-03</txnDate>
                <txnRefNo>DIG20180603-0001</txnRefNo>
                <physicalCurrencyDirection>RECEIVED</physicalCurrencyDirection>
                <moneyReceived id="mrv-04-01">
                    <cash>
                        <ausCash id="mrv-04-01-aud">
                            <currencyCode>AUD</currencyCode>
                            <amount>20000.00</amount>
                        </ausCash>
                        <foreignCash id="mrv-04-01-fc1">
                            <currencyCode>USD</currencyCode>
                            <amount>5000.00</amount>
                            <exchangeRate>0.61</exchangeRate>
                        </foreignCash>
                        <foreignCash id="mrv-04-01-fc2">
                            <currencyCode>EUR</currencyCode>
                            <amount>5000.00</amount>
                            <exchangeRate>0.51</exchangeRate>
                        </foreignCash>
                    </cash>
                </moneyReceived>
                <moneyProvided id="mpr-04-01">
                    <otherMoneyProvided>
                        <dco id="dc-04-01">
                            <currencyCode>AUD</currencyCode>
                            <amount>19995.00</amount>
                            <code>BTC</code>
                            <description>Bitcoin</description>
                            <numberOfUnits>1.66408668</numberOfUnits>
                        </dco>
                        <fco id="mpr-04-01-fco">
                            <currencyCode>AUD</currencyCode>
                            <amount>5.00</amount>
                        </fco>
                    </otherMoneyProvided>
                </moneyProvided>
                <totalAmount id="tam-04-01">
                    <currencyCode>AUD</currencyCode>
                    <amount>20000.00</amount>
                </totalAmount>
            </transaction>
            <recipient id="rcp-04-01">
                <sameAsCustomer refId="cst-04-01"/>
            </recipient>
            <isOtherDsProviderInvolved>N</isOtherDsProviderInvolved>
        </ttr>
    </ttrList>

## Appendix G. Revision history

Revision History
Revision 1.0 | April 2026 |
Initial document. This is the initial release of the XML schema and specifications based on Part 9, Division 2–Reports of threshold transactions of the AML/CTF Rules). This version is not backwards compatible with any previous versions or formats of threshold transaction reports introduced in 2008 and updated in 2011 and 2018.