Foreign Acquisitions and Takeovers (Register Notices) Data Standard 2023

The instrument introduces a concise data standard attached to register notices under Division 3 of Part 7A of the Act. The core concepts it uses and the operational implications are:

• Register notice and registrable interest: The instrument operates only in the register-notice context established by the Act (definitions in s 4 of the Act are noted in cl 4). It focuses on registrable interests (cl 4 definition) to which Division 3 of Part 7A of the Act applies. The instrument does not redefine those statutory concepts; it prescribes what information the Registrar may request when those statutory events occur (cl 6).

• Electronic platform as primary channel: The Registrar provides an electronic platform for giving notices (cl 5(1)). The instrument contemplates exceptions where the platform cannot accept the information and allows the Registrar to permit another form, including another electronic form (cl 5(2)). The Legislation Act 2003, s 14(4), applies to forms made under cl 5(2) (note to cl 5(2)).

• Identity and verification data: The Registrar may require identity verification for individuals, companies, trustees and agents, and proof of agent authority (cl 6(2)(a)(i)-(iii)). Where the registrable interest involves a foreign person, the Registrar may require identity information for that foreign person (cl 6(2)(a)(iv)). The instrument thus formalises identity-related disclosure as part of the register-notice record.

• Asset-type specific data: The instrument lists discrete, asset-class specific fields the Registrar may request: for land, title, holding type, nature of land (commercial, residential, agricultural), current and intended use, location, size and lease information (cl 6(2)(g)); for water, entitlement, licence, use and lease (cl 6(2)(h)); for mining/exploration tenements, licence details, ANZSIC code, land size, location and lease (cl 6(2)(i)); and for businesses, name, business identifier (ABN/ACN), ANZSIC code, main location, structure, industry sector and circumstances of significant agreements or constituent documents (cl 6(2)(j)). The inclusion of ANZSIC code and ABN/ACN fields indicates a structured data intent.

• Registrar discretion over records: The Registrar can combine notices (cl 7), can correct or update Register entries on the Registrar’s reason to believe there are errors or omissions (cl 8(1)), and may accept substantial compliance with the data standard (cl 11). These provisions confer operational discretion on the Registrar to manage records and to accommodate imperfect submissions.

• Obligations to supply and to correct: Persons must provide information or documents when requested by the Registrar to accompany a register notice (cl 6(1)). Persons must also inform the Registrar if they believe there are errors in information held on the Register (cl 8(2)). Clause 6(2) additionally allows requests both before and after a notice is given to establish or verify particular matters.

• Communications and signatures: Electronic communications are the default (cl 9(1)), with a permitted alternative if electronic contact is not possible (cl 9(2)). A signed declaration is required from the person who submits the notice, confirming capacity and the truth of the information (cl 10), with section 10 of the Electronic Transactions Act 1999 applying to signature requirements (note to cl 10).

• Protected information: The data collected under this standard are treated as “protected information” under s 120 of the Act (note to cl 6). That classification affects access and handling of the data under the Act, though the instrument does not itself restate s 120’s access rules.

These concepts map to a procedural architecture: electronic lodgement of standardised data fields, Registrar-led verification and correction powers, and statutory cross-references for timing, signature validity and criminal liability for false statements.

The instrument directly affects all persons who must give register notices under Division 3 of Part 7A of the Act. That group includes, depending on the statutory scope in the Act, foreign persons acquiring registrable interests, domestic entities and trustees where they fall within the register-notice regime, and agents acting on their behalf. Clause 6(2)(a) identifies the categories the Registrar may seek to verify: relevant individuals (including when a partnership involving individuals or an individual submits), companies and trustees, agents and foreign persons. The obligations in cl 6(1) and cl 10 are placed on the person giving the register notice, or an authorised agent submitting for them.

Specific affected parties and practical roles:

• Foreign persons acquiring registrable interests: The instrument contemplates that a foreign person will be a data subject and may need to provide identity and transaction details (cl 6(2)(a)(iv), cl 6(2)(b)-(f)). The data required depends on the asset type acquired.

• Individuals, partnerships, companies and trustees: Where notices are lodged by these parties, the Registrar may request identity verification for them as submitters (cl 6(2)(a)(i)-(ii)). Company or trust submitters must be prepared to supply corporate or trustee identity information and supporting documents.

• Agents acting for applicants: Agents lodging on behalf of others must provide proof of their authority to act (cl 6(2)(a)(iii)) and must provide the signed declaration required under cl 10 that they are authorised to act on the applicant’s behalf.

• Owners or holders of registrable interests: For interests in land, water, tenements or businesses, the registered owners or persons with an obligation to give notice will need to supply the asset-specific data listed in cl 6(2)(g)-(j). For businesses, the instrument requires business or entity identifiers such as ABN or ACN (cl 6(2)(j)(ii)) and ANZSIC codes (cl 6(2)(i)(ii), cl 6(2)(j)(iii)).

• Persons with access rights under the Act: The Registrar will communicate electronically with persons who have provided information and any other person who is permitted by law to access information in relation to a register notice (cl 9(1)(a)-(b)). The instrument thus affects third parties who have statutory access rights to register information under the Act, because the Registrar will use electronic communications as the operational means to communicate.

• The Registrar and the administering agency: The Registrar is given operational authority and discretion to set the electronic platform, request additional data, combine notices, correct records and accept substantial compliance (cl 5-8, cl 11). The instrument therefore affects Registrar resourcing and processes, though it does not itself set budgets.

Who bears compliance costs: The legal duty to provide the information and to supply responses to Registrar requests lies with the person lodging the register notice or their authorised agent (cl 6(1), cl 10). Those persons therefore bear the time, effort and document-collection costs for meeting identity, asset-specific and transaction-verification requirements. The instrument does not state fees, but the compliance burden is operationally placed on submitters.

Who decides and exercises discretion: The Registrar decides on alternative submission methods where the platform cannot accept information (cl 5(2)); requests and accepts further information to establish or verify matters (cl 6(2)); combines notices (cl 7); corrects or updates the Register (cl 8); communicates by non-electronic means if needed (cl 9(2)); and accepts substantial compliance (cl 11). The instrument centralises decision-making and discretionary operational control in the Registrar’s hands.

The instrument creates procedural duties on persons lodging register notices and confers operational rights and discretions upon the Registrar. Below are the principal duties and rights with section references and the behaviour they induce.

Duties on submitters and related persons

• Use of electronic platform: A register notice must be given via the electronic platform provided by the Registrar (cl 5(1)). This makes electronic lodgement the standard mode of compliance.

• Provision of requested information and documents: A person must provide information or documents to accompany a register notice when requested by the Registrar (cl 6(1)). The Registrar may request these before or after the notice is given to establish or verify specific matters (cl 6(2)). The requested matters are extensive and include identity verification, the reason for providing the notice, dates of acquisition or registered circumstances, registrable event day, consideration details, percentage interest and asset-type specific fields (cl 6(2)(a)-(j)).

• Signed declaration: The person who submits a register notice must provide a signed declaration that they are the applicant or authorised to act for the applicant, and that the information provided is true and correct (cl 10). The Electronic Transactions Act 1999, s 10, applies to the signature requirement (note to cl 10). The signed declaration carries the risk of criminal exposure under the Criminal Code Act 1995 (Schedule) sections 137.1 and 137.2 for false or misleading statements, as cross-referenced in the note to cl 10.

• Inform the Registrar of errors: A person must inform the Registrar if they believe there are errors in, or corrections required to, information held in the Register (cl 8(2)). This creates a proactive duty to flag inaccuracies.

Rights and discretions of the Registrar

• Determine submission method exceptions: The Registrar may allow information to be provided by another manner where the electronic platform cannot accept it, including another electronic form (cl 5(2)). This creates an administrative right to deviate from the default lodgement method.

• Request verification and supporting documents: The Registrar may request information or documents to establish or verify specified matters, both before and after a notice is lodged (cl 6(2)). This is a broad verification power covering identity, transaction details, asset specifics and agent authority.

• Combine notices: The Registrar may combine register notices given under Division 3 of Part 7A of the Act into a single notice (cl 7). Combining notices is a procedural right that can affect timing and record management.

• Correct or update Register entries: The Registrar may correct or update any information recorded or held in the Register where the Registrar has reason to believe information is incorrect or missing (cl 8(1)). This is an administrative right to alter Register content.

• Communicate electronically: The Registrar will communicate electronically with persons who have provided information and others permitted by law to access register notice information (cl 9(1)). The Registrar may choose another communication manner where a person is unable to communicate electronically (cl 9(2)).

• Accept substantial compliance: The Registrar may accept that a register notice meets the data standard if it substantially complies or has variations the Registrar considers appropriate having regard to the person’s circumstances (cl 11). This confers flexibility and an informal power to tolerate deviations from strict compliance.

Other legal intersections that create duties or protections

• Timing of notice: The time a register notice is required to be given is set out in s 130W of the Act and may be extended under s 130Z of the Act, as noted in cl 6. Submitters must therefore be attentive to statutory timing provisions in the Act in addition to the data standard’s content requirements.

• Protected information: Information collected under the data standard is “protected information” within the meaning of s 120 of the Act, as stated in the note to cl 6. That places statutory limits on access and handling under the Act’s provisions.

• Signature and false statements: Section 10 of the Electronic Transactions Act 1999 applies to signature requirements (note to cl 10). False or misleading information may constitute an offence under Criminal Code Act 1995 (Schedule) ss 137.1 and 137.2, as cross-referenced (note to cl 10). The instrument therefore links compliance with general Commonwealth signature and false-statement rules.

Behavioural impacts

• Submitters must compile documentary evidence to meet identity and asset-specific requests, increasing preparatory work ahead of lodgement.
• Agents must maintain and be able to produce proof of authority.
• Submitters must monitor and, where necessary, correct Register entries after lodgement.
• The Registrar’s capacity to accept substantial compliance and to allow alternative lodgement methods provides administrative flexibility but also introduces uncertainty for submitters about the standard of detail required in edge cases.

This instrument itself does not create new statutory offences or specify monetary penalties, but it links compliance obligations to existing Commonwealth law and places practical enforcement levers in the Registrar’s hands.

Criminal exposure

• False or misleading information: The instrument explicitly warns that a person may commit an offence if they knowingly give false or misleading information or documents, cross-referencing sections 137.1 and 137.2 of the Schedule to the Criminal Code Act 1995 (note to cl 10). Those provisions criminalise making false or misleading statements in certain Commonwealth contexts. The instrument therefore positions the signed declaration required under cl 10 as potentially exposing submitters and agents to criminal sanction if they knowingly provide false information.

Administrative enforcement and operational levers

• Refusal, further requests and timeframes: While the instrument does not list a power to refuse lodgement, cl 6(1) makes it mandatory for persons to provide information or documents when requested by the Registrar, and cl 6(2) allows requests before or after lodgement. Practically, failure to respond to requests may affect the Register entry status or the Registrar’s administrative handling of the notice under the Act. The instrument also notes that the timing for giving register notices is governed by s 130W of the Act and extensions under s 130Z; enforcement of timing would therefore flow from those Act provisions, not from the data standard itself.

• Registrar corrections: The Registrar may correct or update information in the Register if there is reason to believe it is incorrect or incomplete (cl 8(1)). This is an administrative enforcement mechanism that allows the Registrar to alter records to reflect the Registrar’s view of correct information; submitters must inform the Registrar of errors (cl 8(2)), creating an obligation to cooperate to maintain accurate records.

• Substantial compliance: The Registrar may accept substantial compliance or variations deemed appropriate in light of the person’s circumstances (cl 11). This is an internal enforcement moderation mechanism enabling the Registrar to treat non-material defects as compliant to avoid punitive responses for minor errors.

Process and evidential implications

• Signed declaration: The required signed declaration (cl 10) provides a specific evidential document that the Registrar and, if relevant, prosecuting authorities can point to when assessing claims of knowingly false statements. The Electronic Transactions Act 1999 s 10 applies to signature requirements (note to cl 10), so electronic signatures that meet that Act’s tests should be accepted.

• Protected information consequences: Data collected are “protected information” under s 120 of the Act (note to cl 6). The instrument itself does not describe the access control or penalties for unauthorised disclosure, but classification as protected information brings with it the Act’s statutory treatment of such information, which affects who can access the information and how it may be used in enforcement contexts.

Limits of the instrument’s enforcement specification

• No express fines or civil penalties: The instrument does not establish civil penalty provisions, infringement notices or administrative fines. Any sanctioning for non-compliance with the requirement to give timely or accurate register notices must therefore be sought under the Act or other relevant Commonwealth legislation.

• Dependence on Act enforcement provisions: Enforcement of timing and substantive registration consequences depends on the Act’s existing enforcement framework, including the provisions cited in the instrument such as s 130W, s 130Z and s 120. The data standard mainly provides procedural content and verification expectations rather than standalone punitive measures.

This data standard cross-references and operates alongside several Commonwealth statutory instruments, so compliance requires attention to multiple legal texts. The instrument itself states specific cross-links.

Primary statute: the Foreign Acquisitions and Takeovers Act 1975

• Legal basis and scope: The instrument is made under subsection 130ZZ(1) of the Act (cl 3) and applies to register notices given under Division 3 of Part 7A of the Act (notation in cl 4 and repeated throughout). The Act, therefore, provides the substantive legal regime to which this procedural standard attaches. Timing requirements for register notices are set out in s 130W of the Act and may be extended under s 130Z, as noted in cl 6’s explanatory note. The data standard does not alter the Act’s substance; it specifies the data and procedural mechanics for notices required under the Act.

Protected information and access rules

• Section 120 of the Act: Information collected under this data standard is “protected information” within the meaning of s 120 of the Act (note to cl 6). The instrument does not restate s 120’s rules, but this cross-reference means information handling, disclosure permissions and penalties concerning protected information will be governed by the Act’s s 120.

Electronic transactions and forms law

• Electronic Transactions Act 1999: The signature requirement in cl 10 is subject to s 10 of the Electronic Transactions Act 1999 (note to cl 10), which affects whether electronic signatures satisfy the instrument’s signed declaration requirement. Practically, the Electronic Transactions Act determines formal validity of signatures and the conditions under which electronic communications and signatures are legally effective.

• Legislation Act 2003: Subsection 14(4) of the Legislation Act 2003 applies to any forms made under cl 5(2) (note to cl 5(2)). That provision governs the legal status and publication requirements for statutory forms. The instrument therefore places forms used as alternatives to the electronic platform within the Legislation Act’s form-making regime.

Criminal law

• Criminal Code Act 1995: The instrument refers to ss 137.1 and 137.2 of the Schedule to the Criminal Code Act 1995 as provisions that may render a person criminally liable for knowingly giving false or misleading information or documents (note to cl 10). This links the statutory requirement for truthful declarations on register notices to the Criminal Code’s general false-statement offences.

Interaction with the Foreign Investment Reform (Protecting Australia’s National Security) Act 2020

• Commencement dependency: Clause 2(1) provides that the commencement of the instrument is the later of the day after registration and the day after Part 2 of Schedule 3 to the Foreign Investment Reform (Protecting Australia’s National Security) Act 2020 commences. That means the instrument’s operative start date is tied to the commencement timing of provisions in that Act, creating a dependency between the instruments for timing and administrative sequencing.

Operational interplay and administrative law

• Registrar discretion and administrative law: The instrument vests various discretionary powers in the Registrar: to accept alternative lodgement methods (cl 5(2)), to request additional information (cl 6(2)), to combine notices (cl 7), to correct records (cl 8(1)), and to accept substantial compliance (cl 11). These discretionary powers will be subject to standard administrative law principles and reviewability, though the instrument itself does not set review processes or standards beyond giving the discretionary authority.

Limits and boundaries

• The instrument does not alter substantive ownership, property or commercial law regimes. It prescribes information to be provided to the Registrar and how the Registrar will manage that information. Any civil consequences, acquisition invalidity, divestment obligations, or other substantive remedies remain functions of the Act or other substantive statutes, not of this data standard.

• The instrument references other laws for signature validity, form-making and criminal liability but does not reproduce those laws. Practitioners must read the instrument alongside the Act, the Electronic Transactions Act 1999, the Legislation Act 2003 and the Criminal Code Act 1995 to fully understand legal effects.

The instrument itself includes limited amendment history in its commencement table and an explicit note that the table relates only to the instrument as originally made. From the text provided:

• Date and maker: The instrument was made by Chris Jordan, Commissioner of Taxation in his capacity as Registrar, dated 11 May 2023 (the signature block at the front).

• Name: The instrument’s name is the Foreign Acquisitions and Takeovers (Register Notices) Data Standard 2023 (cl 1).

• Commencement clause: Clause 2 establishes the commencement rule. Clause 2(1) states that the whole instrument commences on the later of the day after it is registered and the day after Part 2 of Schedule 3 to the Foreign Investment Reform (Protecting Australia’s National Security) Act 2020 commences. Clause 2(2) clarifies that information in column 3 of the table is not part of the instrument and may be edited in any published version; that is an administrative housekeeping statement relating to the commencement table.

• No subsequent amendments recorded in the instrument: The text contains a note indicating the commencement table relates only to the instrument as originally made and will not be amended in the instrument document to reflect later amendments. The instrument as presented does not show any later amendments, repeal provisions, or amendments to other instruments.

• Authority: The instrument is made under subsection 130ZZ(1) of the Act (cl 3). There is no clause within the instrument that amends earlier instruments or prescribes transitional arrangements beyond the commencement provision.

Implications for practitioners

• Because the instrument is an administrative data standard, any future changes or updates would typically be reflected by a new instrument or amendment instrument made under the same authority. The instrument does not itself set an ongoing amendment procedure beyond standard legislative instrument mechanisms.

• The instrument’s commencement being tied to an external legislative commencement introduces the possibility that its effective start date was delayed until the referenced Schedule 3, Part 2 commenced. The instrument’s own text does not provide an operative commencement date in absolute terms; practitioners need to check the register of legislative instruments and the commencement of the referenced provision in the Foreign Investment Reform Act 2020 to determine what date the instrument came into force.

• The note in cl 2(2) signalling that the table's column 3 may be edited in published copies suggests that non-substantive editorial adjustments to explanatory information may occur in public versions. Substantive changes, however, would require a formal amendment instrument.

The instrument contains no litigation history and the text does not recount any judicial consideration, decisions, or cases referring to it. The instrument itself is a statutory administrative instrument prescribing a data standard and therefore may be the subject of administrative review or judicial review in future if disputes arise regarding the Registrar’s exercise of discretion under its clauses, but no such matters are recorded within the instrument’s text.

What the instrument’s text discloses about potential litigation vectors

• Administrative discretion: The Registrar’s discretions (for example, to accept alternative lodgement methods under cl 5(2), to combine notices under cl 7, to correct the Register under cl 8(1), and to accept substantial compliance under cl 11) are administrative functions. If a party disputes the application of those discretions in a particular case,for example, if the Registrar refuses to accept a non-standard lodgement or corrects an entry in a way a submitter contests,those acts could potentially be challenged by merits or judicial review processes under Commonwealth administrative law. The instrument does not itself provide appeal or review procedures.

• Criminal liability linkages: The instrument references criminal offences for knowingly making false or misleading statements (Criminal Code Act 1995 Schedule ss 137.1, 137.2; note to cl 10). Any prosecution under those sections would follow the normal criminal process and could generate litigation where the facts and mens rea are contested. The instrument does not alter the operation of those criminal provisions.

• Evidence and procedural documentation: The signed declaration required by cl 10 provides documentary evidence that could be relied upon in enforcement or litigation contexts. The instrument also requires, and authorises the Registrar to request, documentation relevant to identity and transaction details (cl 6). Disputes about what was supplied, whether it was sufficient, or whether the Registrar properly corrected the Register might prompt administrative or judicial procedures.

Absence of cases in instrument

• The instrument names no cases and records no prior judicial interpretation of its clauses. Any litigation history will therefore have to be established from external sources, statutory registers or court records after the instrument’s commencement. The text itself contains no litigation references.

The instrument contains a number of practical traps and operational frictions practitioners should recognise. These are not evaluative judgments; they are concrete features of the instrument likely to produce compliance friction, uncertainty or operational consequences.

1. Electronic-platform default and limited explicit fallback: Clause 5(1) requires giving a register notice via the Registrar’s electronic platform. Clause 5(2) permits the Registrar to allow an alternative method only where the platform cannot accept the information. That places the onus on submitters to use the platform in nearly all cases, and on the Registrar to permit exceptions. Practically, if the platform rejects a file or a submitter cannot gain access, an applicant must secure the Registrar’s permission to use an alternative method; there is no automatic alternative provided in the instrument.

2. Broad verification power after lodgement: Clause 6(2) allows the Registrar to request information before or after a register notice is given to establish or verify a wide array of facts, including identity, dates, consideration, percentage interest and asset-specific details. This means lodgement is not necessarily the end of document-gathering; the Registrar can require further documentation post-lodgement, potentially affecting transaction certainty and timing.

3. Asset-specific data demands: The instrument lists detailed fields for land (cl 6(2)(g)), water (cl 6(2)(h)), tenements (cl 6(2)(i)) and businesses (cl 6(2)(j)). Expect to be asked for technical identifiers (land title details, water entitlement details, tenement licence details), ANZSIC codes, ABN/ACN and uses of assets. If those identifiers are not readily available at the time of lodgement, submitters must plan to gather them promptly on request.

4. Combining notices may change administrative timing: Clause 7 permits the Registrar to combine register notices into a single notice. Combining may alter how notices are processed, how timing is calculated under the Act, and which transactions are treated together for administrative purposes. Submitters should consider transaction structuring and the possibility that separate transactions could be administratively consolidated.

5. Substantial compliance is discretionary: Clause 11 allows the Registrar to accept notices that “substantially comply” or have variations deemed appropriate given the person’s circumstances. This gives helpful flexibility but creates uncertainty about the tolerable margin of error. Submitters cannot rely on a defined standard of “substantial” compliance; acceptability depends on the Registrar’s assessment.

6. Requirement to inform the Registrar about errors: Clause 8(2) places a proactive duty on persons to inform the Registrar of errors in Register information. This is forward-looking; if a submitter discovers an error but does not inform the Registrar, the instrument places an affirmative obligation to notify and thus a continuing compliance duty.

7. Protected information classification: Information is “protected” under s 120 of the Act (note to cl 6). That affects who can access it and potentially how the information may be used in commercial contexts or litigation. Practitioners should not assume unconstrained access to Register data and should be aware that protections in s 120 apply.

8. Signature formalities and criminal risk: The signed declaration (cl 10) must be provided; the Electronic Transactions Act 1999 s 10 applies to signature validity. False statements can lead to criminal liability under Criminal Code provisions (note to cl 10). Agents must keep their authorisation documentation up to date and ensure the truthfulness of submissions.

9. Commencement dependency: Clause 2 ties the instrument’s commencement to the later of registration and the commencement of Part 2 of Schedule 3 to the Foreign Investment Reform (Protecting Australia’s National Security) Act 2020. This means the instrument might have a deferred start date that practitioners must verify rather than assume it applied immediately on registration.

10. No stated appeals or review mechanism for Registrar discretion: The instrument grants multiple discretions to the Registrar but provides no express internal review or appeal mechanism. Any challenge to Registrar decisions would rely on general administrative law remedies, not on an instrument-specific review procedure.

11. Forms governed by the Legislation Act: Clause 5(2) cross-references s 14(4) of the Legislation Act 2003 for forms made under cl 5(2). Forms used as alternative methods therefore carry the formalities and public availability rules required by that Act.

12. Data structure expectations: The requirement to supply ANZSIC codes, ABN/ACN and other identifiers indicates the Registrar intends structured data. Where businesses or tenement data do not fit cleanly into those codes, submitters should be prepared to explain classifications and to supply supporting documentation.

13. Unstated processing times and outcomes: The instrument prescribes content and process but does not state processing times, confirmation procedures or consequences of non-compliance beyond corrections and criminal exposure for false statements. For timing and consequence details, practitioners must look to the Act and to the Registrar’s published processes.

This section sets out a practical compliance checklist derived directly from the instrument’s clauses and notes, followed by procedural recommendations tied to the rules in the instrument. Each item cites the relevant clause.

Pre-lodgement preparation

• Use the electronic platform: Prepare to give the register notice via the Registrar’s electronic platform, unless you have prior agreement from the Registrar to use another method due to platform incapacity (cl 5(1)-(2)). Confirm the Registrar’s published platform specifications and acceptable file formats before submission.

• Identify the applicable statutory timing: Review s 130W of the Act for the time by which the register notice must be given, and any extension provisions under s 130Z of the Act (note to cl 6). The data standard does not set timing itself.

• Collect identity documentation: Assemble identity verification documents for the relevant individuals, companies or trustees as applicable, and documentation evidencing an agent’s authority if an agent will submit (cl 6(2)(a)(i)-(iii)). Be ready to provide identification for foreign persons where they are the submitter or data subject (cl 6(2)(a)(iv)).

• Prepare transaction and timing evidence: Have documentary evidence of the reason for the notice, the date the registrable interest was acquired or the registered circumstance began or ceased, the registrable event day, consideration paid, and any calculation of percentage interest (cl 6(2)(b)-(f)).

Asset-specific documentation

• For Australian land: Obtain land title details, title holding type, classification of land (commercial, residential, agricultural), current and intended use, precise location, land size and any relevant lease information (cl 6(2)(g)(i)-(vii)). If land is held through a trust or corporation, prepare supporting corporate/trust documents demonstrating the holding structure.

• For registrable water interests: Compile water entitlement and licence details, current and intended use of the water, and any lease documentation (cl 6(2)(h)). Ensure identifiers match those recorded in state water registers if applicable.

• For exploration or mining tenements: Prepare tenement licence details, the relevant ANZSIC code, land size, location and lease information (cl 6(2)(i)). Be prepared to justify ANZSIC classifications.

• For businesses or business assets: Have the business or entity name, ABN or ACN, ANZSIC code, main business location, business structure and industry sector details. If a significant agreement was entered into, terminated or a constituent document was altered, prepare documentation describing the circumstances (cl 6(2)(j)(i)-(vi)).

Lodgement and declaration

• Complete the register notice via the platform: Upload the prepared documents in the format required by the platform (cl 5(1)). Where the platform is unable to accept the information, contact the Registrar to request permission to use an alternative form (cl 5(2)); any forms used will be subject to s 14(4) of the Legislation Act 2003 (note to cl 5(2)).

• Signed declaration: Ensure the submitter provides a signed declaration that they are the applicant or are authorised to act for the applicant and that the information is true and correct (cl 10). Use an electronic signature compliant with s 10 of the Electronic Transactions Act 1999 (note to cl 10).

Post-lodgement interactions

• Respond to Registrar requests: Be ready to provide additional information or documents both before and after lodgement when requested by the Registrar to establish or verify matters listed in cl 6(2). Maintain organised copies of all provided materials and a record of communications.

• Monitor and correct Register entries: If you identify errors in the Register, inform the Registrar promptly as required by cl 8(2). Expect that the Registrar may also correct or update Register information where the Registrar has reason to believe it is incorrect or incomplete (cl 8(1)).

• Anticipate possible combining of notices: If multiple related register notices are involved, be aware that the Registrar may combine notices into a single notice (cl 7). If combining would affect your timing or strategic position, raise the issue with the Registrar early.

Best-practice record-keeping

• Keep originals and verifiable copies of identity and transaction evidence, agent authorisations and the signed declaration. The instrument links register notice obligations to criminal liability for false statements (note to cl 10). Maintain contemporaneous records to substantiate assertions.

• Document classification rationale for ANZSIC codes and business structure choices, so you can respond quickly if the Registrar requests clarification on industry classification (cl 6(2)(i)(ii), cl 6(2)(j)(iii)).

Managing uncertainty and discretionary outcomes

• Where the data standard is not perfectly met, consider asking for an express pre-lodgement confirmation from the Registrar that the alternative format or variant information will be accepted, recognising that cl 11 gives the Registrar discretion to accept substantial compliance. Obtain written confirmation where possible.

• If a submitter cannot communicate electronically, notify the Registrar and seek confirmation of an alternative communication method, relying on cl 9(2). Keep a record of any arrangements made.

• Consider the potential for administrative review: If the Registrar exercises discretion adversely (for example, refuses to accept a non-standard lodgement or corrects the Register on a basis you contest), preserve records of communications and consider administrative law remedies available under Commonwealth law, noting that the instrument does not provide an internal appeal process.

Practical checklist (minimum items to have ready at lodgement)

• Name of business or entity and business identifier such as ABN or ACN when applicable (cl 6(2)(j)(i)-(ii)).
• ANZSIC code where specified for tenements or businesses (cl 6(2)(i)(ii), cl 6(2)(j)(iii)).
• Precise asset identifiers: land title details, water entitlement/licence IDs, tenement licence details (cl 6(2)(g)(i), cl 6(2)(h)(i-ii), cl 6(2)(i)(i)).
• Dates: acquisition date, registrable event day, registered circumstance start or cessation (cl 6(2)(c)-(d)).
• Consideration paid and percentage interest held (cl 6(2)(e)-(f)).
• Current and intended uses of the asset (cl 6(2)(g)(iv), cl 6(2)(h)(iii)).
• Lease information where relevant (cl 6(2)(g)(vii), cl 6(2)(h)(iv), cl 6(2)(i)(v)).
• Business structure, main location and industry sector for business assets (cl 6(2)(j)(iii)-(v)).
• Evidence of agent authority where an agent lodges on behalf of a person (cl 6(2)(a)(iii)).
• A signed declaration in the form acceptable under the Electronic Transactions Act 1999 (cl 10 and note).

Final notes

• Confirm the effective commencement date in the instrument’s register entry because cl 2 ties commencement to an external provision.
• Treat all information provided as protected under s 120 of the Act and handle disclosure accordingly (note to cl 6).
• Keep a contemporaneous audit trail of all submissions and Registrar communications.