Electronic Transactions (Queensland) Act 2001 — Zoe

Queensland act

Electronic Transactions (Queensland) Act 2001

In ForceQLD

Jurisdiction

Queensland

Act Number

42 of 2001

Collection

act

Plain English Summary

6/10 complexity

What this law does, in plain English

The Act makes electronic communications legally effective for State laws in a number of common situations where the law previously referred to paper or handwritten processes. It does so by saying that an otherwise-valid transaction or legal requirement is not defeated merely because it was done electronically (s 8).
More specifically, the Act treats electronic alternatives as meeting State-law requirements about: giving information or notices (s 11–12); signatures (s 14); producing documents (s 16–17); recording and keeping information and documents (s 19–21). In each case the electronic method meets the legal requirement only if certain factual conditions are satisfied: for example, it was reasonable to expect the information would be readily accessible for later reference, the method preserved the integrity of the information, and the recipient consents (see s 11(2), s 14(1)(a),(b),(c), s 16(2), s 20(2), s 21(2)).
The Act also sets rules about when an electronic message is sent or received (time of dispatch and receipt — s 23–24) and where it is taken to have been sent or received for legal purposes (place of dispatch and receipt — s 25). Those rules include default assumptions about a party’s place of business and allow parties to agree different arrangements (s 23(1), s 24(1), s 25(1)–(2)).
The Act clarifies when an electronic communication is attributable to (and therefore binds) a purported originator: it binds the originator only if it was sent by the originator or with the originator’s authority, subject to existing law on actual or apparent authority (s 26).

JSON API

Deep Dive

5,555 words · generated 12/06/2026

What it does

This instrument sets a statutory baseline for treating electronic communications as satisfying a wide range of formal and procedural requirements under State laws. It does two things mechanically. First, it declares that a transaction or required act is not invalid merely because it was conducted wholly or partly by electronic communications (s 8). Second, it converts many discrete formal requirements that previously demanded paper, signatures, particular storage media, or in-person action into tests that can be satisfied by electronic equivalents if specified conditions are met (Parts 2 and 3, notably ss 11-21). The statutory tests are expressed repeatedly as conjunctive reasonableness, consent and integrity or accessibility thresholds. For example, a writing requirement is satisfied where the information is given electronically provided that it was reasonable to expect the information would be readily accessible for subsequent reference and the recipient consents (s 11). A signature requirement is satisfied where a method identifies the person and indicates their intention and is either as reliable as appropriate to the purpose or proven in fact to have fulfilled those functions, and the recipient consents (s 14). Production and retention requirements are satisfied where electronic forms maintain the integrity of the information and are reasonably accessible, and where consent or any regulation-specified storage medium is complied with (ss 16, 17, 19-21).

The instrument also sets default rules for timing and place for dispatch and receipt of electronic communications (ss 23-25), attribution of messages (s 26), and a set of additional rules that apply to contracts formed or performed under the State law (ss 26A-26E). The contract provisions treat widely accessible electronic proposals as invitations to treat unless the proposer clearly intends to be bound (s 26B), protect contracts formed by automated message systems from invalidation solely because no human intervened (s 26C), and give a limited right to withdraw an erroneous input where an automated system did not allow correction and no material benefit was taken (s 26D). Where other State laws require particular technology, devices, signatures, unique identifiers or methods, the statutory baseline does not override them (ss 13, 15, 18).

Current sections

Direct links to the current provisions in Electronic Transactions (Queensland) Act 2001.

Official source available

Zoe has indexed the source text for search and analysis. Use the official register for the original document and download formats.

View on official register

Sourced from Queensland Legislation (legislation.qld.gov.au), CC BY 4.0.

Who pays / bears the compliance cost: parties who rely on electronic processes — businesses, government offices and individuals — must ensure their electronic methods meet the Act’s factual tests (e.g. reliability, integrity, accessibility) or obtain the recipient’s consent (see s 11(2), s 14(1)(b), s 16(2)(a), s 20(2)(a), s 21(2)(b)). Those are implementation costs (system design, storage, audit trails) borne by the sender/keeper and sometimes the addressee if consent is required. Keepers required to retain electronic communications must also store additional metadata (origin, destination, timestamps) to meet s 21(2)(c).
Incentives and behaviour change: the Act gives private parties an incentive to use electronic methods because those methods can satisfy writing, signature, production and record-keeping requirements when the statutory conditions are met (s 8; s 11–21). At the same time, the recipient’s right to withhold consent or insist on particular formats (or existing special-tech rules in other laws) creates an incentive for senders to negotiate acceptable formats or retain paper fallbacks (s 11(2)(b), s 13, s 15, s 18).
Trade-offs and opportunity costs: the Act prefers flexible, technology-neutral factual tests ("reasonable to expect... readily accessible", "reliable way of maintaining integrity") over prescribing specific technologies (see s 11(2)(a), s 14(1)(b)(i), s 16(2)(a), s 20(2)(a)). That lowers the risk of rapid technological obsolescence but makes legal compliance fact-specific and may increase litigation or administrative decision costs because courts or agencies will need to assess technical reliability case by case.
Compliance burden and administrative discretion: multiple provisions leave key assessments to context and judgment (for example, whether a method is "as reliable as appropriate" (s 14(1)(b)(i)) or whether integrity has been maintained (s 16(3), s 20(3), s 21(3))). That creates discretion for decision-makers and potential compliance uncertainty for users who must document and demonstrate reliability and integrity.
Interaction with other laws and regulation: the Act expressly preserves other State laws that require particular storage devices, specific electronic-signature formats or particular identification methods (s 13, s 15, s 18). Regulations may also require particular data-storage devices for keeping records (s 19(2), s 20(2)(c), s 21(2)(e)). Those carve-outs concentrate compliance obligations on certain transactions and can impose specialised technical requirements beyond the Act’s general tests.
Cross-border and jurisdictional effects: the Act applies to contracts whose proper law is the State law even when parties are overseas (s 26A). Time and place rules (s 23–25) create default assumptions about dispatch/receipt and a party’s place of business that affect timing, jurisdiction and choice-of-law-related outcomes; parties can override those defaults by agreement (s 23(1), s 24(1), s 25(1)).
Fraud, attribution and risk allocation: the attribution rule (s 26) ties binding effect to whether the communication was sent by the originator or with authority, but it does not displace ordinary legal rules about actual or apparent authority (s 26(2)). That allocation of risk shifts pressure onto parties to secure their systems and to manage authority and access to automated systems.

Main concepts

The legislation organises around a small number of repeated legal tests and concepts. These are the legal foci to which all practical compliance and litigation questions must be directed.

Non-invalidity by reason of electronic communication (s 8). The base rule is permissive. Transactions or acts are not invalid merely because they were made electronically. This is subject to more specific provisions in the same chapter which displace the general rule to the extent of inconsistency (s 8(2)).
Consent (ss 11-12, 14, 16-17, 19-21). Consent from the person to whom information, signatures or documents are to be given is a recurring requirement. Consent is an enabling condition for treating electronic delivery, signatures or production as equivalent to the paper or prescribed form.
Reasonable expectation of accessibility and usability for subsequent reference (ss 11, 12, 16-17, 19-21). The statute uses an objective reasonableness test at the time information is given, recorded or the document generated. The statutory phrase is “reasonable to expect the information would be readily accessible so as to be useable for subsequent reference” and is included in the tests for writing, production, recording and keeping electronic communications.
Integrity of information (ss 16, 17, 20, 21). For documents and kept electronic communications the statute requires that generation and keeping methods provide a reliable way of maintaining integrity, defined to mean that the information remains complete and unaltered apart from endorsements or immaterial changes arising in the normal course of communication, storage or display (ss 16(3), 17(3), 20(3), 21(3)).
Particular technology carve-outs (ss 13, 15, 18). Where another State law mandates a particular storage device, kind of electronic communication, an electronic signature however described, a unique electronic identifier, or a particular method for identifying an originator, those specific rules are preserved and the general permissive standards do not displace them.
Time and place rules (ss 23-25). Statutory defaults establish when an electronic communication is taken to be dispatched and received. Dispatch is when the communication leaves an information system under the originator’s control or when it is received if it has not left such a system (s 23). Receipt is when the message is capable of being retrieved at an electronic address designated by the addressee, with an assumption that reachability equals capability of retrieval unless agreed otherwise (s 24). Place of dispatch and receipt is taken to be the place of business of the originator and the addressee, with rules for determining place of business if multiple locations or no clear indication exist, and exclusions that equipment location alone is not a place of business (s 25).
Attribution and authority (s 26). A purported originator is bound only where the communication was sent by the purported originator or with their authority, unless otherwise agreed. The section does not limit State laws that attribute acts under principles of actual or apparent authority.
Contract-specific rules (ss 26A-26E). These sections apply the above rules to contract formation and performance where the proper law is a State law. They include rules about invitations to treat (s 26B), machine-formed contracts (s 26C), withdrawal rights for input errors against automated systems (s 26D), and the application of the chapter to contracts (s 26E).

These concepts generate recurring practical questions: what counts as consent, how to demonstrate the “reasonable expectation” of accessibility at the relevant time, what technical or procedural measures will prove the integrity of an electronic form, and how to record and retain the metadata required by s 21. The statute frames compliance as a combination of objective tests and parties’ choices, with contractual agreement able to vary the default timing, place and attribution rules.

Who it affects

The provisions allocate roles and burdens to identifiable categories of actors. The principal affected groups are originators, addressees, keepers, parties to contracts, and operators of automated message systems.

Originators. The person or entity that sends an electronic communication is treated as the originator. The statute imposes default rules about when a communication is dispatched and where that dispatch is taken to occur (ss 23, 25). Originators who want to ensure a particular time or place of dispatch can agree that with addressees to vary the defaults. Originators who rely on electronic signatures must ensure the method used identifies them and indicates their intention and is either as reliable as appropriate or proven in fact to have fulfilled those functions (s 14).
Addressees. The person or entity to whom information or a document is required to be given must consent to electronic delivery for writing, signature and production requirements to be met in the electronic form, unless a specific other law requires particular technology (ss 11-12, 14, 16-17). Addressees thus decide whether they will accept electronic communication in substitution for paper or prescribed forms. They also decide whether an electronic address is “designated” for receipt in the sense used in s 24.
Keepers. Persons required to keep information that was the subject of an electronic communication are specifically addressed by s 21. Keepers must maintain, or cause another to maintain, the information in electronic form for the period and must retain “additional information” sufficient to identify origin, destination and sent and received times, and ensure the integrity and accessibility of both the primary information and the additional information (s 21(2)(a)-(d)).
Parties to contracts. The contract-specific part applies to contracts whose proper law is under the State law (s 26A). Both businesses and consumers fall within that application, as the part applies whether the contract is for business or personal, family or household purposes (s 26A(1)(b)). Where an offer is made through generally accessible electronic means the proposer is treated as making an invitation to treat unless there is clear intention to be bound (s 26B).
Operators of automated message systems. Operators of systems that automatically interact with individuals or other systems are affected by s 26C (contracts not invalid solely because no human reviewed each action) and by s 26D (input error withdrawal rights where no correction opportunity was given). System designers therefore bear practical costs in how the interface handles errors and in preserving audit trails and correction opportunities, because failure to offer correction gives rise to a statutory right to withdraw certain communications.
Regulators and legal advisers. While not the statute’s direct addressees, regulators and advisers will be engaged because the statute preserves other State law technical requirements (ss 13, 15, 18) and construing “reasonable expectation,” “readily accessible” and “integrity” will require interpretive guidance when disputes arise.

Who pays. The principal financial burdens fall on originators and keepers: originators must adopt reliable signature and delivery methods and obtain recipient consent where required; keepers must provide storage, integrity controls and metadata retention capabilities. Addressees who refuse electronic delivery avoid the cost of maintaining electronic acceptance, but may incur administrative costs when receiving paper. Automated system operators may bear development costs to provide correction opportunities or to instrument logging for later proof.

Who decides. Many duties are conditional on the addressee’s consent or on parties’ agreements about dispatch/receipt/place. Where parties do not agree, statutory defaults determine time and place of dispatch/receipt (ss 23-25) and attribution (s 26). The statute therefore invests significant decision-making power in the parties, subject to its objective tests.

Key duties and rights

The legislative text creates a set of duties (often conditional) and statutory rights. The statute’s structure is largely permissive but conditional on meeting tests. Key duties and rights are as follows.

Duties

Duty to obtain or respect consent. A repeated statutory condition is that the person to whom information, signature, or document is required to be given must consent to the use of electronic communication (ss 11(2)(b), 12(2)(b), 14(1)(c), 16(2)(c), 17(2)(c), 20(2)(c)). Absent consent, the statutory conversion does not operate.
Duty to ensure accessibility and usability for subsequent reference. Where writing, recordkeeping, production or keeping requirements are to be satisfied electronically, the person giving, recording or keeping the information must ensure that, at the relevant time, it was reasonable to expect the information would be readily accessible and usable for subsequent reference (ss 11(2)(a), 12(2)(a), 16(2)(b), 17(2)(b), 19(2)(a), 20(2)(b), 21(2)(a), 21(2)(d)).
Duty to maintain integrity. For electronic production and keeping of documents, the method must be reliable for maintaining the integrity of the information when generated or kept (ss 16(2)(a), 17(2)(a), 20(2)(a), 21(2)(b)). Integrity in the statute means remaining complete and unaltered except for endorsements or immaterial changes in the normal course of communication, storage or display (ss 16(3), 17(3), 20(3), 21(3)).
Duty to retain additional metadata when keeping electronic communications. A keeper must also ensure that during the prescribed period they keep sufficient additional information to identify the origin and destination of the communication, and when it was sent and received (s 21(2)(c)-(d)).
Duty to comply with regulations requiring specific storage devices. If a regulation prescribes a particular data storage device, the electronic keeping obligation is only satisfied if that device requirement is met (ss 19(2)(b), 20(2)(c), 21(2)(e)).
Duty to use reliable signature methods. When a signature is required, the person relying on electronic means must use a method to identify the person and indicate intention, with the method either as reliable as appropriate for the purposes or proven in fact to have fulfilled those functions (s 14(1)(a)-(b)).

Rights

Right to use electronic communications to satisfy State-law requirements. Provided the statutory tests are met, persons have a positive right to satisfy writing, signature, production, recording and keeping requirements by electronic means (ss 11-12, 14, 16-17, 19-21).
Right to withdraw part of an electronic communication made in error against an automated message system. Where an input error occurs and the system did not allow correction, the individual has the right to withdraw the portion of the communication in which the error was made, provided the person notifies the other party as soon as possible and has not used or received material benefit or value from goods or services received (s 26D(2)).
Right to contract formation by automated systems. Contracts formed by automated message systems or interactions between such systems and individuals are not invalid solely because no individual reviewed or intervened in each action (s 26C).
Rights to contractual variation of defaults. Parties can agree to vary defaults about time and place of dispatch and receipt and attribution, so contract drafters retain the right to supersede statutory rules by agreement (ss 23-26).

Conditionalities and limitations

Preservation of other State laws. Where another State law prescribes particular technical requirements or devices, the permissive conversion to electronic form does not apply and those laws remain effective (ss 13, 15, 18).
Exception for more specific provisions. The general non-invalidity rule in s 8 does not apply to the extent a more specific provision in the chapter deals with the validity of the transaction (s 8(2)). Similarly, the contracts part does not apply to the extent parts 1 to 3 would have the same effect of their own force or another State law in substantially similar terms would have that effect (s 26E(2)).

Practical interaction of duties and rights creates risk: the rights to use electronic processes are conditional on consent and objective tests that can be contested, and the duties to keep metadata and integrity evidence create ongoing operational costs for keepers and originators.

Penalties and enforcement

The text supplied contains no express criminal penalties, civil fines, or named enforcement powers specific to the electronic transactions provisions. The statutory scheme instead operates primarily by altering the legal effect of acts and records under State laws rather than by prescribing new sanctioning regimes.

Consequences and enforcement mechanisms should be read as follows, based strictly on the provided provisions:

Compliance produces substantive legal effect. The sections operate to deem requirements satisfied where the statutory tests are met. The “penalty” for failure to meet those tests is the absence of that deeming effect, which means the underlying State law requirement may remain unsatisfied, with whatever consequences that State law already attaches. For example, if a regulation requires a document to be kept on a particular kind of data storage device and that requirement is not met, the alternative electronic keeping will not be effective under the statute (ss 20(2)(c), 21(2)(e)).
Civil remedies lie in existing State law. Where the electronic form is alleged to be invalid or insufficient, enforcement, remedies and sanctions will usually be those contained in the underlying State law. The instrument preserves other State laws that create obligations and consequences (s 13, s 15, s 18, s 26E(2)). Therefore, enforcement actions are likely to be pursued under those State laws rather than under these provisions.
Attribution, evidence and civil liability. Sections such as s 26 on attribution and the integrity provisions (ss 16, 17, 20, 21) affect evidential questions in disputes. For example, a recipient can bind a purported originator only where the communication was sent by the originator or with authority, except where otherwise agreed (s 26(1)). The parties will therefore litigate to establish whether a method was as reliable as appropriate or proven in fact (s 14), or whether the integrity condition was met.
No specific enforcement body specified. The instrument does not create a new body to supervise or audit compliance with electronic transaction standards. That role remains with existing administrative or judicial mechanisms under State law.
Contractual remedies partly preserved. The contract-specific provisions (ss 26A-26E) create statutory defaults but do not specify remedies for breach beyond general rules of contract and law. The right to withdraw an erroneous communication under s 26D is procedural and its consequences are to be determined under applicable rules of law (s 26D(4)).

In short, the provided text modifies the legal consequences of certain acts and imposes technical compliance duties without creating a standalone enforcement or penalty regime. Enforcement therefore will be exercised under the State laws to which these provisions refer and through normal judicial or administrative processes available in those State laws.

How it interacts with other laws

Interaction with other State laws is a central structural feature of the statute. The instrument is explicitly designed to be a default framework that State laws can displace or supplement in specified ways.

Preservation of specialised technical requirements

Where a State law requires information to be given or produced using a particular data storage device or particular kind of electronic communication, the conversion rules in ss 11-12, 16-17, 19-21 do not operate to override those prescriptions (ss 13, 15, 18). The statutes therefore coexist with specialised regulatory regimes that mandate specific technologies, methods or identifiers.

Signatures and unique identification

Section 15 expressly preserves State laws that require an electronic communication to contain an electronic signature however described, to contain a unique identification in electronic form, or to require a particular method to identify the originator and indicate intention. That means statutes imposing authentication regimes, statutory signatures, or unique digital identifiers can and do remain effective notwithstanding the permissive provisions here.

Attribution and agency

Section 26 leaves intact State laws that attribute conduct to others under agency principles or provide that a person is bound by conduct engaged in by another within actual or apparent authority. The statutory defaults on attribution therefore sit alongside, and do not displace, established rules of agency and attribution in State law.

Application to contracts and overlap with parts 1-3

The contract-specific provisions apply unless parts 1-3 would of their own force have the same effect as this part, or another State law in substantially similar terms would of its own force have the same effect (s 26E(2)). This is a non-extension clause that prevents duplication or conflict where an existing law already produces the same outcomes.

Timing and territorial issues

The defaults about time and place of dispatch and receipt apply even if the information system supporting an electronic address is located in a different place than that at which the communication is taken to have been dispatched or received (ss 23(2), 24(3)). Section 25 specifies how place of business is determined and excludes equipping or technology location as a place of business. These rules therefore interact with choice of law and territorial jurisdiction considerations in State law claims.

Regulations

Several sections expressly note that where a regulation requires particular storage devices or methods, the statutory tests are met only if the regulation’s requirement is met (ss 19(2)(b), 20(2)(c), 21(2)(e)). The instrument therefore anticipates subordinate legislation that may modify technical compliance obligations.

Evidence and civil procedure

The integrity and accessibility tests (ss 16, 17, 20-21) will affect evidentiary disputes about the authenticity, completeness and reliability of electronic records in litigation under State laws. The statute frames these as statutory factors, but whether evidence is admissible, persuasive, or dispositive remains within the bounds of the relevant State law and rules of evidence.

No displacement of remedies

The instrument does not provide express remedies or penalties of its own in the text provided. Remedies available for non-compliance therefore remain those in the underlying State laws, regulations and common law.

Overall, the statutory architecture establishes a flexible default mechanism while expressly preserving the primacy of other State laws where those laws contain more specific technical or procedural requirements or where existing parts of the legislative scheme would otherwise duplicate the effect.

Amendment history

The legislative text contains in-line amendment annotations that identify several post-enactment changes. The document does not provide a full chronology beyond these inserted notes, but the following entries are present in the text as provided.

Sections 14 and 15. The text records that s 14 was amended in 2013 (2013 No. 35 s 72) and s 15 was amended in 2013 (2013 No. 35 s 73). The effect of those amendments is not described in the material supplied beyond the amendment flags.
Section 16. The production of document provision carries amendment notes: amended 2002 No. 34 s 17 and 2010 No. 42 s 214 sch. These indicate that s 16 has been amended at least twice, once in 2002 and once in 2010.
Section 20. The keeping written documents provision has amendment notes similar to s 16: amended 2002 No. 34 s 17 and 2010 No. 42 s 214 sch.
Section 23 and 24 and 25. Each has a note “sub 2013 No. 35 s 74” indicating substitutional amendments were made in 2013, at least to the text of those sections.
Contract part insertions. Sections 26A through 26E are marked as inserted in 2013 by 2013 No. 35 s 75. Additionally, s 26B, s 26C, s 26D, and s 26E each carry the same insertion note, confirming that the contract-specific provisions were added as a package in 2013.
Section 14 cross-referenced the amendment note earlier mentioned and is flagged with the 2013 amendment.

The annotation style shows the statute has been the subject of at least two waves of amendment activity: earlier technical amendments to production and keeping requirements (2002 and 2010), and a suite of modernisation measures in 2013 that substituted time/place rules and added the contract-related provisions.

The supplied text does not include dates of original enactment, explanatory memoranda, or the precise textual changes effected by each amendment. The amendment notes are limited to statutory citations and years. Researchers needing a full legislative history will need to consult the State law’s consolidated version or parliamentary records to reconstruct the original text and to read the amendment instruments themselves.

Gotchas

The statute contains multiple practical traps for parties who treat electronic use as a simple substitution for paper. The following operational and legal “gotchas” emerge directly from the text.

Consent is central but undefined. Many deeming conditions require the person to whom information, signature or documents are required to be given to consent to electronic delivery (ss 11(2)(b), 12(2)(b), 14(1)(c), 16(2)(c), 17(2)(c), 20(2)(c)). The statute does not define how consent must be manifested, documented or withdrawn. Absent a contractual or regulatory mechanism specifying consent mechanics, proving consent in a dispute will depend on surrounding facts and likely on records, which means parties should document consent proactively.
“Reasonable to expect” is an ex ante standard. Multiple sections use an ex ante objective reasonableness test about accessibility at the time the information was given or recorded (for example ss 11(2)(a), 19(2)(a), 21(2)(a)). In practice this requires parties to show that at the moment of generation or delivery it was reasonable to expect continued accessibility. Post-hoc failures of access may still meet the statutory test if they were not reasonably predictable at the time, but proving that fact may be contested.
Integrity defined narrowly but operationally exacting. Integrity is maintained only if the information remains complete and unaltered except for endorsements or immaterial changes arising in normal communication, storage or display (ss 16(3), 17(3), 20(3), 21(3)). System-generated conversions, format migrations, or automated transformations may be characterised as material changes unless processes and logs demonstrate immateriality. The statute places an evidential burden on originators and keepers to show the reliability of methods used.
Keeper metadata obligations. Section 21 requires keepers to also keep additional information sufficient to identify origin, destination and sent and received times. Failure to keep that metadata will defeat the statutory deeming of compliance. In practice this requires robust logging and retention policies beyond mere content storage.
Regulations may still prescribe specific devices. Several sections expressly caveat that if a regulation prescribes a particular kind of storage device, the electronic keeping obligation is only satisfied if that device is used (ss 19(2)(b), 20(2)(c), 21(2)(e)). Entities cannot rely solely on compliance with the Act if subordinate regulation imposes a different technical standard.
Signatures: two alternative tests. Section 14 offers two alternative ways to meet a signature test: a method that is as reliable as appropriate to the purpose, or a method proven in fact to have fulfilled the identification and intention functions, by itself or with further evidence. This leaves open both prospective design standards and retrospective proof. Relying on ad hoc or minimal methods risks later failure to meet either test.
Time and place defaults may be manipulated. The statute assumes parties’ indicated place of business unless disproved (s 25(2)(a)), and excludes merely the location of equipment from being a place of business (s 25(3)). Parties that fail to indicate place of business or that have multiple locations may face litigation over which place has the “closest relationship” to the transaction. Domain names and email addresses do not create place presumptions (s 25(4)), but absence of a clear address can leave parties subject to statutory assumptions that may be unfavourable.
Automated systems and withdrawal rights are narrow. Section 26D provides a right of withdrawal only where an individual makes an input error, the automated system did not provide an opportunity to correct the error, the person notifies the other party as soon as possible, and the person has not used or received material benefit or value. The right is not an automatic rescission right and its practical effect depends on applicable rules of law (s 26D(3)-(4)). Failure to provide correction opportunities can create exposure, but the remedy is conditional and its consequences uncertain.
No new penalties in text supplied. There are no express penalties in the material provided. Non-compliance therefore results in the underlying State-law consequences rather than a dedicated enforcement regime under this chapter. Parties should assess what sanctions the specific State law creates.
Discrepancy between “capable of being retrieved” and actual awareness. Section 24 treats receipt as the time the message becomes capable of being retrieved at a designated address, and provides for a different test where an addressee becomes aware that a message has been sent to another address. This creates potential disputes about whether an addressee was reasonably capable of retrieval versus actually aware, and parties who rely on timely notification should document both network delivery and acknowledgements.

These are concrete operational risks that arise from the statutory wording. Each is a point where evidential or factual dispute is likely and where parties should build procedural controls to avoid losing the benefit of the statutory deeming rules.

How to comply

Compliance under the statute requires aligning technological, contractual and recordkeeping practices to the statutory tests. The following practical checklist maps the statutory conditions into concrete steps and controls that originators, addressees, keepers and automated system operators should consider.

Document consent processes

Obtain explicit documented consent where State-law requirements must be satisfied electronically (ss 11(2)(b), 12(2)(b), 14(1)(c), 16(2)(c), 17(2)(c), 20(2)(c)). Consent can be recorded in written agreements, click-through consents with clear audit trails, or otherwise documented in logs that demonstrate the addressee’s agreement to accept electronic forms.
Where consent is implied by conduct in a contractual setting, record the conduct and make it contractually explicit if possible.

Design for demonstrable accessibility at the relevant time

Ensure systems and storage solutions are configured to make documents “readily accessible so as to be useable for subsequent reference” at the time they are generated or received (ss 11(2)(a), 16(2)(b), 19(2)(a), 20(2)(b), 21(2)(a)).
Maintain retention schedules and technology roadmaps that show expected accessibility across the retention period. Document migrations, format changes and the rationale for any media migration as part of an audit trail.

Implement integrity controls and evidentiary logging

Implement cryptographic hashes, checksums, audit logs, tamper-evident storage or equivalent measures to demonstrate that the method of generating or keeping an electronic form provided a reliable way of maintaining integrity (ss 16(2)(a), 20(2)(a), 21(2)(b)).
Keep logs of endorsements and of any immaterial changes that occur through normal processes to show they fall within the statutory exception (ss 16(3), 17(3), 20(3), 21(3)).

Collect and retain metadata required for keepers

For information that was the subject of an electronic communication, design retention to also store origin, destination and sent/received times as additional information (s 21(2)(c)). Ensure this metadata is readily retrievable and preserved against loss for the statutory retention period.

Build signature processes to satisfy either statutory test

Adopt signature methods that are “as reliable as appropriate for the purposes” in practice, taking into account transaction risk, regulatory context and any relevant agreement (s 14(1)(b)(i)).
Alternatively, where novel methods are used, ensure there is demonstrable proof that the method in fact identified the signer and indicated intention, supported by further evidence when necessary (s 14(1)(b)(ii)). Maintain logs and corroborating evidence.

Check for regulatory or statute-specific device or method requirements

Review the corpus of State laws and subordinate regulations that apply to your activities for any prescriptive requirements regarding data storage devices, electronic signature forms, unique electronic identifiers or particular methods of originator identification (ss 13, 15, 18). Where such requirements exist, comply with them; the general permissive rules will not displace them.

Agree contractual overrides to statutory defaults

If parties wish to vary the defaults on dispatch and receipt timing or place of business, agree express contract terms (ss 23-25). Specify designated electronic addresses, business locations for dispatch/receipt, and the agreed legal effects of the use of particular information systems.

Design automated message systems to provide correction opportunities

Where an interactive or automated ordering or contracting system is used, provide functionality that allows users to review and correct inputs before final submission. Doing so reduces the chance an individual will later exercise the limited withdrawal right in s 26D and avoids uncertainty about the consequences.

Keep records of place of business indicators

Indicate and record the party’s place of business clearly where possible to avoid default assumptions under s 25. If multiple locations exist, document which location has the closest relationship to particular transactions to reduce disputes.

Prepare operational policies and audit trails

Develop internal policies that document how the enterprise will meet “reasonable to expect” and “reliability” tests, including retention schedules, format migration policies, integrity verification procedures and incident response processes for data loss or corruption.
Conduct periodic audits that produce demonstrable evidence of compliance with the statutory tests and capture any changes to systems that may affect accessibility or integrity.

Train staff and allocate responsibilities

Allocate responsibilities for consent capture, metadata retention, integrity verification and dispute handling among legal, IT and records teams to ensure that when an evidentiary question arises the organisation has the records required by the statute.

Review contracts and customer terms

Amend consumer and business terms to make clear whether interactive proposals are invitations to treat or intended to be offers, to avoid uncertainty under s 26B.
State how errors in inputs will be handled, whether the counterparty will accept corrections and what remedies apply.

By mapping statutory conditions into operational controls and contractual language, entities can reduce the risk that a court later finds that the statutory deeming did not apply. The emphasis in the statute on ex ante reasonableness and demonstrable integrity means contemporaneous documentation and system design are the principal means of proving compliance.