ASIC Corporations (mFund) Instrument 2024/18

This instrument deploys a small set of recurring conceptual devices: exemption from a statutory duty, conditional reliance on electronic confirmations, delegated duties for upstream intermediaries, reliance on market operator rules, documentary evidence requirements, temporally bounded availability tests and a sunset date.

Exemption mechanism. Section 5 grants an exemption from compliance with subsection 1016A(2) of the Corporations Act for responsible entities in respect of issues following electronic applications through mFund. The exemption is conditional, not automatic; the responsible entity must satisfy the tests in s 5(2). The instrument is made under the statutory power cited in s 3, namely paragraphs 1020F(1)(a) and (c).

Electronic confirmation as trigger. The exemption is triggered by an electronic confirmation accompanying the mFund application that a Product Disclosure Statement, identified by date, has been given to the acquirer by a financial services licensee or their authorised representative (s 5(2)(a)). The instrument therefore recognises an electronic attestation as a functional substitute for the responsible entity’s direct delivery of a PDS but only where other conditions apply.

Non-defectiveness requirement. One condition is that the PDS referred to in the confirmation must have been prepared by the responsible entity and was not defective at the time of application, where ‘defective’ is taken to have the meaning given in subsection 1016A(1) of the Act (s 5(2)(b)(i)-(ii); s 4). Section 7 then specifies how supplementary PDSs are treated for these purposes, including taking the date of the most recent supplementary PDS as the relevant date.

Reliance on ASX rules and website availability. The responsible entity must have no reason to believe that the requirements of the ASX Operating Rules and ASX Settlement Operating Rules have not been satisfied in relation to the particular application and confirmation (s 5(2)(c)). In addition, the responsible entity must reasonably believe that the PDS referred to in the confirmation was available free of charge on the website of ASX at the time the application was made (s 5(2)(d)). These two limbs introduce third-party fact checks: compliance depends in part on the state of ASX’s systems and rules.

Delegated responsibilities to licensees who transmit. Section 8 inserts an obligation into Part 7.9 of the Act as applied to financial services licensees and their authorised representatives transmitting applications through mFund. The licensee must either have given the person the PDS or have been notified in writing by another licensee/representative that the other has given it, and must ensure that the date of the PDS is specified in the electronic statement and is the date of the most recent PDS available on ASX’s website at the time of application (s 8(2A)(c)-(e)). There is an express “all things reasonably necessary” standard for the licensee’s conduct (s 8(2A)(b)).

Temporal rules and supplements. The instrument repeatedly uses the phrase “as at the time the application was made” to fix evidential and compliance points in time (s 5(2)(b)(ii), s 5(2)(d), s 8(2A)(e)). Section 7 clarifies treatment of Supplementary Product Disclosure Statements, requiring the date of the most recent Supplementary PDS to be used when determining whether the PDS date in the confirmation matches the current availability on ASX’s website.

Post-issue reporting and retention. A responsible entity that relies on the exemption must provide a written notice to the acquirer within five business days about the PDS and availability of a free copy, notify ASX within ten business days if it has reason to believe a retail client did not receive the PDS, and retain records for seven years, including copies of all mFund applications and any statements by acquirers that they had not been given the PDS (s 6).

Sunset. The instrument has a statutory expiry at the start of 1 April 2029 (s 9), making the changes temporary unless replaced or extended.

Definitions and anchoring to ASX. The instrument defines ASX, ASX Operating Rules, ASX Settlement and ASX Settlement Operating Rules and confines the exemption to the mFund facility as defined (s 4). The requirement in s 5(2)(e) that mFund be the subject of an exemption under s 791C of the Act connects this instrument to another statutory exemption regime.

These concepts together construct a framework where the responsible entity may avoid a particular subsection’s obligation in narrowly specified circumstances, accountability is shifted upstream to licensees and market-operated systems, and post-issue monitoring and recordkeeping are used to produce evidence of compliance.

Responsible entities of registered schemes. The primary legal effect operates on responsible entities that issue interests in registered schemes. Section 5 gives those responsible entities an explicit conditional exemption from complying with subsection 1016A(2) of the Act for issues arising from electronic applications made through mFund, but only when the conditions in s 5(2) are satisfied. Responsible entities who rely on the exemption are subject to the notice, reporting and recordkeeping conditions in s 6.

Financial services licensees and authorised representatives. Section 8 extends the operation of Part 7.9 of the Act to financial services licensees and their authorised representatives who transmit electronic applications through mFund, as if Part 7.9 were modified by the inserted subsections. The inserted text imposes affirmative duties on licensees to take “all things reasonably necessary” to ensure that the PDS has been given, that the PDS date is specified in the electronic statement, and that the date shown is the date of the most recent PDS available on ASX’s website at the time of application (s 8(2A)(a)-(e)). Authorised representatives who transmit applications are expressly covered and so must operate to the licensee’s standards.

ASX and ASX Settlement. Both ASX Limited and ASX Settlement Pty Limited are named in the definitions (s 4). The instrument conditions the exemption in part on the operation of the ASX Operating Rules and ASX Settlement Operating Rules (s 5(2)(c)) and on the PDS being available free on ASX’s website at the relevant time (s 5(2)(d), s 8(2A)(e)). The instrument therefore makes ASX’s operational state and rule compliance a determinative factor in whether the responsible entity may rely on the exemption. Section 6(b) also requires a responsible entity to notify ASX in writing within 10 business days if it has reason to believe a retail client did not receive the PDS.

Acquirers, including retail clients. Persons acquiring an interest via mFund are affected in two ways. The instrument conditions the exemption on an electronic confirmation that a PDS with a specified date was given to the acquirer by a licensee or authorised representative (s 5(2)(a)). Where the exemption is relied on, the responsible entity must notify the acquirer in writing within five business days after issue about the PDS referenced in the confirmation and state that a paper or electronic copy is available free of charge if they did not receive it (s 6(a)). For retail clients, the responsible entity must notify ASX if it has reason to believe they were not given the PDS before applying (s 6(b)).

Registered schemes and PDS authors. The instrument requires that the PDS specified in the confirmation be prepared by the responsible entity (s 5(2)(b)(i)). Where supplementary PDSs exist, s 7 prescribes how the PDS and its date are treated for the purposes of sections 5 and 6.

Other market participants. Intermediaries, platform operators and compliance professionals who support responsible entities or licensees will be implicated by the recordkeeping, notification and “reasonable steps” tests. The instrument ties compliance to the ASX website’s state, so any service provider that manages hosting or content on ASX’s web pages or assists in capturing PDS availability will have a functional role in compliance evidence.

Regulatory bodies. The instrument is made by a delegate of the Australian Securities and Investments Commission (Kate Metz) under powers in the Corporations Act (s 3). The obligations on responsible entities and on licensees are legally binding instrument provisions and are therefore within the regulatory compliance and supervisory perimeter, although the instrument itself does not set out enforcement sanctions.

Temporal population. The instrument applies to electronic applications made through the mFund facility while the instrument is in force (commencing the day after registration and ending on 1 April 2029) (s 2, s 9). It therefore affects transactions in that window.

In sum, the instrument allocates pre-application and evidential duties to financial services licensees and authorised representatives who transmit via mFund, provides a conditional statutory exemption that benefits responsible entities if they can satisfy the factual predicates, and relies on ASX and ASX Settlement’s operational state to determine applicability.

Duties imposed on responsible entities. If a responsible entity wishes to rely on the exemption from subsection 1016A(2) for issues arising from mFund applications, it must ensure the conditions in s 5(2) are met. Those include that the application carries an electronic confirmation that a Product Disclosure Statement with a specified date was given to the acquirer by a financial services licensee or authorised representative (s 5(2)(a)); that the PDS was prepared by the responsible entity and was not defective as at the time the application was made (s 5(2)(b)(i)-(ii)); that the responsible entity has no reason to believe the ASX Operating Rules and ASX Settlement Operating Rules requirements were unsatisfied in relation to the application and confirmation (s 5(2)(c)); that the responsible entity reasonably believes the PDS was available free of charge on ASX’s website at the time the application was made (s 5(2)(d)); and that mFund is the subject of an exemption under s 791C of the Act (s 5(2)(e)).

Post-issue notification duty. A responsible entity that relies on the exemption must, within five business days after the issue of the interest, notify the acquirer in writing that the PDS with the specified date exists and that the acquirer may obtain an electronic or paper copy free of charge if they did not receive it (s 6(a)).

Reporting duty to ASX. A responsible entity must notify ASX in writing within ten business days if it has reason to believe that a person who acquired an interest as a retail client via mFund had not been given, before applying, the PDS specified in the electronic confirmation (s 6(b)).

Recordkeeping duty. A responsible entity must keep for seven years: records demonstrating compliance with the s 6(a) notice requirement; a copy of all applications received through mFund; and any acquirer statements indicating they were not given the PDS before applying (s 6(c)(i)-(iii)).

Duties imposed on financial services licensees and authorised representatives transmitting applications. Section 8 treats Part 7.9 of the Act as applying to licensees and authorised representatives who transmit electronic applications through mFund as if modified to insert the new subsection (2A). That subsection requires that the licensee must not transmit an electronic application for the issue of an interest unless, and must ensure an authorised representative does not transmit such an application unless the licensee has done all things reasonably necessary to ensure, that (a) the licensee or its authorised representative has given the person the PDS, or (b) has been notified in writing by another licensee or authorised representative that the other has given the person the PDS; (c) the date of the PDS is specified in an electronic statement forming part of or accompanying the application; and (d) the date of the PDS is the date of the most recent PDS for the interest that is available on the ASX website at the time the application is made (s 8(2A)(c)-(e), (2A)(a)-(b)).

Exception for non-restricted issues. Subsection (2B) provides that the inserted subsection (2A) does not apply where the licensee or authorised representative believes on reasonable grounds that an issue is not a restricted issue (s 8(2B)). The instrument does not define “restricted issue” within its text.

Supplementary PDS treatment. Subsection (2C) applies the modifications in relation to Supplementary Product Disclosure Statements so that references to a PDS include its supplements and references to the date of a PDS become references to the date of the most recent Supplementary PDS (s 8(2C)). Section 7 contains parallel rules for sections 5 and 6.

Rights conferred or clarified. The instrument confers a conditional right for a responsible entity not to comply with subsection 1016A(2) in the specified circumstances (s 5(1)). That right is not unconditional; it requires satisfaction of the factual predicates and compliance with the ongoing duties in s 6. Financial services licensees receive no new legal right to transmit mFund applications; rather they acquire a set of procedural duties and a standard of care expressed as “all things reasonably necessary” to ensure the pre-transmission conditions are satisfied (s 8(2A)(b)).

Temporal and evidential standards. The instrument imposes time-based tests that determine duties, for example the “as at the time the application was made” standard for PDS non-defectiveness and ASX website availability (s 5(2)(b)(ii), s 5(2)(d), s 8(2A)(e)), and short reporting windows , five and ten business days , which translate into business process obligations (s 6(a)-(b)).

Interdependence with ASX rules and s 791C exemption. The exemption available to responsible entities is dependent on two external legal facts: that ASX’s operating rules and ASX Settlement’s operating rules requirements were satisfied in relation to the application (s 5(2)(c)); and that mFund is the subject of an exemption under s 791C (s 5(2)(e)). These link the responsible entity’s duties and rights to third-party rule compliance and another statutory exemption.

Retention of legal liability beyond this instrument. The instrument does not specify civil or criminal sanctions for non-compliance in its text. It modifies duties and creates recordkeeping and reporting obligations, but it does not purport to extinguish other legal duties that might arise under the Corporations Act or common law. The right given to responsible entities in s 5(1) is narrowly defined to subsection 1016A(2) and does not claim to affect other obligations in the Act or under other laws.

The instrument itself is silent on specific penalties, fines or criminal sanctions. It creates exemptions, duties and reporting and retention obligations, but it does not include an express enforcement section imposing new penalties within the instrument text.

Legal character and enforcement locus. The instrument is a legislative instrument made under paragraphs 1020F(1)(a) and (c) of the Corporations Act (s 3). That statutory provenance means the instrument is part of the regulatory framework issued by the Australian Securities and Investments Commission, and non-compliance with duties in the instrument would be relevant to regulatory oversight. The instrument does not itself specify ASIC enforcement actions, but the duties it creates operate within the broader Corporations Act framework. The instrument therefore functions as a binding legislative modification rather than as guidance.

Failure to meet conditions and consequences for the exemption. The exemption in s 5(1) is conditional. If a responsible entity cannot establish the factual predicates in s 5(2) , for example, if the PDS was defective as at the time the application was made (s 5(2)(b)(ii)), if the responsible entity has reason to believe ASX Operating Rules requirements were not satisfied (s 5(2)(c)), or if mFund is not the subject of the s 791C exemption (s 5(2)(e)) , the responsible entity will not be entitled to rely on the s 5(1) exemption. The instrument does not set out consequences in the instrument text, but the absence of the exemption would leave the responsible entity subject to the original statutory obligation in subsection 1016A(2) of the Act.

Time-sensitive reporting and records as enforcement facilitators. Sections 6 and 8 establish short timeframes and record retention obligations: a five-business-day written notice to the acquirer after issue (s 6(a)), ten-business-day notification to ASX if there is reason to believe a retail client did not receive the PDS (s 6(b)), and seven-year retention of specified records (s 6(c)). These obligations create documentary evidence that would be relevant in regulatory inquiries or civil proceedings even though the instrument does not itself state penalties.

Evidential disputes and enforcement risk. The instrument imports fact-based standards , “no reason to believe” (s 5(2)(c)) and “reasonably believes” (s 5(2)(d)) , and an “all things reasonably necessary” standard for licensees (s 8(2A)(b)). Such standards are inherently fact-intensive and will be evaluated against the supporting records that the instrument requires be retained for seven years (s 6(c)). Failure to have adequate records will impair a respondent’s ability to demonstrate compliance; the instrument therefore builds its own evidential expectations.

Interaction with other statutory enforcement powers. The instrument links to other sections of the Corporations Act: it exempts from s 1016A(2), requires that mFund be exempt under s 791C (s 5(2)(e)), and operates via modifications to Part 7.9 as indicated in s 8. The instrument does not purport to alter enforcement powers available elsewhere in the Act that ASIC or other authorities may exercise. In short, the instrument does not create its own enforcement regime but produces duties and evidential requirements that can be relied on in enforcement actions founded on the Act or other applicable law.

No express criminal or civil penalty schedule in the instrument. There is no schedule of fines, civil penalties or criminal offences within the instrument text. Any consequences for breaches will therefore arise from pre-existing regulatory and statutory mechanisms outside the instrument itself. The instrument’s notice, reporting and retention obligations are precise, and their breach will likely have regulatory significance in oversight or enforcement activity under the Corporations Act, though the instrument itself does not set out a penalty matrix.

Temporal enforcement window. The instrument will cease to have effect at the start of 1 April 2029 (s 9). Enforcement or retrospective regulatory scrutiny of transactions that occurred under the instrument while it was in force will remain possible under the Act and other applicable law notwithstanding the instrument’s repeal, subject to limitation periods and other legal constraints outside the instrument text.

Direct references to the Corporations Act. The instrument is made under paragraphs 1020F(1)(a) and (c) of the Corporations Act 2001 (s 3) and expressly modifies how subsection 1016A(2) of the Act applies in certain circumstances by creating an exemption for responsible entities (s 5(1)). It also relies on the definition of “defective” in subsection 1016A(1) of the Act (s 4, definition of defective) and inserts a modified subsection into Part 7.9 of the Act to impose duties on financial services licensees and their authorised representatives who transmit applications through mFund (s 8).

Interaction with s 791C exemption. The instrument requires that mFund be the subject of an exemption under section 791C of the Act for a responsible entity to rely on the s 5 exemption (s 5(2)(e)). That links this instrument to the operation of another statutory exemption regime in the Corporations Act. The instrument does not itself grant the s 791C exemption; it conditions applicability on an existing or parallel statutory exemption.

Relationship to ASX governance and operating rules. Several provisions tie the instrument’s operation to compliance with ASX’s operating rules. Section 5(2)(c) requires the responsible entity to have no reason to believe that the requirements of the ASX Operating Rules and ASX Settlement Operating Rules have not been satisfied in relation to the application and the confirmation. Sections 4 and 5 also tie PDS availability to ASX’s website , the responsible entity must reasonably believe that the PDS was available free of charge on ASX’s website as at the time the application was made (s 5(2)(d)), and the inserted Part 7.9 subsection requires the licensee to ensure the PDS date in the electronic statement is the date of the most recent PDS available on ASX’s website at the time of application (s 8(2A)(e)). Those links make ASX’s own operation a factual determinant of statutory compliance under the instrument.

Supplementary PDSs and the Act’s definition of defective. Section 7 governs how supplementary Product Disclosure Statements are treated for the purposes of sections 5 and 6. It directs that references to a Product Disclosure Statement be read as references to the PDS and each Supplementary PDS that supplements it, and that references to the date of the PDS be read as the date of the most recent Supplementary PDS (s 7(a)-(b)). The instrument also includes a note explaining that in determining whether a PDS is defective for the purposes of subparagraph 5(2)(b)(ii), information in a Supplementary PDS is taken to be contained in the PDS, citing subsection 1016A(1) of the Act. That cross-reference uses the Act’s existing definition of “defective” rather than creating a new standard.

Relationship to existing PDS obligations. The instrument’s note in s 8 references section 1012B of the Act, which requires giving a Product Disclosure Statement before offering to arrange for the issue of an interest as a retail client. The instrument therefore operates alongside existing regime obligations rather than replacing them. It creates an exemption from one subsection (1016A(2)) for responsible entities where the instrument’s conditions are met, while imposing parallel duties on licensees and authorised representatives who transmit applications so that the Act’s PDS-disclosure regime is given effect by intermediaries and market processes.

Evidence and procedural law interaction. The instrument requires specified records to be kept for seven years (s 6(c)). These records will interact with evidence law and statutory time limits in any proceedings or regulatory investigations, though the instrument does not itself alter evidentiary or limitation rules.

No express interaction with other legislation set out in the instrument. The text does not reference other Commonwealth statutes, privacy law, electronic transactions laws or criminal statutes. It therefore operates within the Corporations Act regime and ASX rule environment without expressly amending or disclaiming interaction with other legislative instruments.

Temporal limits and repeal. The instrument commences the day after registration (s 2) and is repealed at the start of 1 April 2029 (s 9). Transactions that occur during the instrument’s operative period will be governed by the instrument’s exemptions and duties; the instrument does not itself specify how ongoing obligations survive repeal, so broader statutory principles in the Act and general law will determine post-repeal effects.

In sum, the instrument is tightly integrated with the Corporations Act provisions it cites and with ASX’s operating rules and website availability. It creates conditional carve-outs and added duties that operate in tandem with existing PDS disclosure obligations under the Act.

Instrument provenance. The instrument is titled ASIC Corporations (mFund) Instrument 2024/18 and is signed by Kate Metz, delegate of the Australian Securities and Investments Commission, dated 21 March 2024. Section 1 fixes the instrument’s name.

Commencement and finality. Section 2 states the instrument commences on the day after registration on the Federal Register of Legislation. The instrument contains an express repeal provision: it is repealed at the start of 1 April 2029 (s 9). Therefore the instrument is temporally bounded and set to expire automatically on that date unless remade or extended.

No amendments recorded within the instrument text. The instrument itself does not contain any amendment history or transitional provisions beyond its commencement and repeal dates. There are no schedules of prior versions, no serial amendment notes, and no references to prior instruments being varied or repealed by this instrument within the text provided. The instrument therefore appears as a standalone legislative instrument without internal amendment annotations.

Authority and legal power. Section 3 records the source of authority for the instrument as paragraphs 1020F(1)(a) and (c) of the Corporations Act 2001. The instrument was made by an ASIC delegate rather than by Parliament, consistent with the framework for legislative instruments under the Corporations Act.

Notes and cross-references. The instrument contains notes indicating statutory context, for example the note in s 8 referencing section 1012B of the Act regarding the requirement to give a Product Disclosure Statement to a retail client before making an offer. Section 7 contains a note explaining how the definition of “defective” in subsection 1016A(1) of the Act should be read to include supplementary PDS information. These notes provide interpretive context but are not stated as formal amendments.

Version control absent. The text provided does not include a formal version control history, explanatory memorandum, second reading speech or regulatory impact statement. The file header in the supplied text contains a label “Mfund legislative instrument - comparison document - ag comments (004)” but the instrument proper does not record any draft history or previous iterations. The instrument’s formal dating and the delegate’s signature are the only temporal markers inside the instrument text itself.

Practical consequence. For practitioners this means the operative legal text is the instrument as signed and dated 21 March 2024; its operative period extends from commencement (day after registration) until 1 April 2029; and no internal amendments are recorded in the provided text. Any future changes would need to be via a new instrument or amendment instrument made under the relevant statutory powers.

No cases or litigation are cited in the instrument text. The instrument contains no recital of judicial decisions, no references to precedent or disputes, and no litigation history.

Potential litigation and dispute nodes indicated by the instrument. Although the instrument itself contains no litigation record, the provisions create factual and legal tensions that could generate disputes in practice. The instrument frames several evidentiary and reasoned-belief standards that are fact-intensive and therefore litigable. Key nodes that could become subjects of litigation or administrative review include:

• Whether a Product Disclosure Statement was “not defective” at the time the application was made (s 5(2)(b)(ii)), taking into account the definition of “defective” in subsection 1016A(1) of the Act. Disputes may arise over the content of the PDS and whether supplementary information should be read into it under s 7 and the note thereto.

• Whether the responsible entity had “no reason to believe” that ASX Operating Rules and ASX Settlement Operating Rules requirements were not satisfied in relation to the application and confirmation (s 5(2)(c)). That is a potentially subjective assessment hinging on what the responsible entity knew or should have known about ASX rule compliance in a specific case.

• Whether the responsible entity “reasonably believes” that the PDS was available free of charge on ASX’s website as at the time the application was made (s 5(2)(d)). The timing and method of proving website availability, including capturing snapshots or server logs, may be contested.

• Whether the financial services licensee or authorised representative did “all things reasonably necessary” to ensure the person had been given the PDS or that written notification from another licensee/representative establishing delivery existed (s 8(2A)(b)-(c)). The standard may be subject to conflicting accounts of steps taken prior to transmission.

• The meaning and application of “restricted issue” for the s 8(2B) exception, noting that the instrument does not define the term in this text. Disputes could arise over whether the exception applies in particular facts.

• The adequacy of post-issue notices and the timing of compliance with the five-business-day notice to acquirers and ten-business-day notification to ASX (s 6(a)-(b)). Failure to meet these timeframes and the sufficiency of the notices could be contested.

Evidential consequences of recordkeeping obligations. Section 6(c) requires retention for seven years of records demonstrating compliance, copies of all mFund applications, and records of any acquirer statements about non-receipt of the PDS. These records will be the primary documentary evidence in any regulatory or civil dispute. A failure to retain or produce these records could be decisive in litigation or administrative proceedings.

No judicial interpretation to rely on. Because the instrument contains no litigation history, practitioners cannot rely on judicially established interpretations of the inserted or modified provisions. Any litigation or tribunal proceedings that do arise will therefore be initial opportunities to establish interpretive guidance for the instrument’s standards such as “no reason to believe”, “reasonably believes”, “all things reasonably necessary” and the mechanics of PDS availability on the ASX website.

Regulatory review and administrative proceedings. Disputes may not only be litigated in courts; they might be resolved through ASIC inquiries or administrative processes under the Corporations Act or through ASX’s own regulatory mechanisms given the instrument’s dependence on ASX rules and the ASX website. The instrument requires notification to ASX (s 6(b)), which could trigger ASX action or information requests.

For now the instrument records no litigation history. Practitioners should therefore assume that interpretive questions will be resolved by factual evidence and, ultimately, by court or tribunal decisions if contested.

Several drafting features and factual predicates in the instrument create potential pitfalls for responsible entities, financial services licensees, authorised representatives, intermediaries and compliance teams. The following items identify traps that are directly supported by the instrument text.

Narrow and conditional exemption. Section 5(1) exempts a responsible entity from subsection 1016A(2) only in relation to issues following electronic applications made through mFund and only where the specific conditions in s 5(2) are satisfied. Absent those precise facts, the exemption does not apply. Do not assume the exemption applies to non-mFund electronic applications or to other disclosure obligations in the Act.

Electronic confirmation must specify the PDS date. The trigger is an electronic confirmation that a Product Disclosure Statement with a specified date has been given to the acquirer by a licensee or authorised representative (s 5(2)(a)). The confirmation must therefore include an identifiable date for the PDS. A missing or ambiguous date in the confirmation undermines the exemption.

PDS must be prepared by the responsible entity and not defective. The instrument requires that the PDS referred to in the confirmation have been prepared by the responsible entity and that it was not defective as at the time the application was made (s 5(2)(b)(i)-(ii)). Responsible entities must therefore ensure they authored the PDS and that its content, including any supplementary statements, renders it non-defective within the meaning of subsection 1016A(1) of the Act. Section 7 complicates this by specifying how supplementary PDSs are treated; review supplementary PDSs closely.

Interplay with Supplementary Product Disclosure Statements. Section 7 applies sections 5 and 6 to PDSs that have supplementary PDSs as if references to a PDS include the supplementary documents and the date is the date of the most recent Supplementary PDS. However the instrument expressly excludes subparagraph 5(2)(b)(ii) from the “as if” modification and then, in a note, directs that information in a Supplementary PDS be taken to be contained in the PDS for the defective test. This textual pattern is subtle; practitioners should not treat the treatment of supplements as automatic without documenting how the most recent supplement’s date aligns with the PDS date in the electronic confirmation (s 7 and the note).

Dependence on ASX rule compliance and website state. The responsible entity must have no reason to believe that the ASX Operating Rules and ASX Settlement Operating Rules requirements have not been satisfied in relation to the application and confirmation (s 5(2)(c)). The responsible entity must also reasonably believe that the PDS was available free of charge on ASX’s website at the time of application (s 5(2)(d)). Both limbs make the exemption contingent on third-party systems and rule compliance. If ASX’s systems are down, or if web content is not accessible at the relevant time, the exemption could be unavailable.

Temporal precision matters. Multiple provisions use “as at the time the application was made” or “at the time the application was made” (s 5(2)(b)(ii), s 5(2)(d), s 8(2A)(e)). Practitioners must capture and timestamp the operative evidence , confirmations, website snapshots, server logs , to demonstrate the state of the PDS and ASX website at the precise application moment.

Varying standards of belief. The instrument uses different standards: “no reason to believe” (s 5(2)(c)), “reasonably believes” (s 5(2)(d)), and “all things reasonably necessary” for licensees (s 8(2A)(b)). These phrases have different impetuses and evidential expectations. Recordkeeping and contemporaneous decision notes will matter when showing which standard was applied and why.

Short notification windows. Responsible entities must notify the acquirer within five business days after issue (s 6(a)) and notify ASX within ten business days if the responsible entity has reason to believe a retail client did not receive the PDS (s 6(b)). These short windows require operational procedures and monitoring to trigger timely notices.

Seven-year retention. The instrument requires retention for seven years of records demonstrating compliance with the s 6(a) notice requirement, copies of all mFund applications, and records of acquirer statements implying non-receipt of a PDS (s 6(c)). Failure to retain appropriate records will both undermine the responsible entity’s ability to rely on the exemption and may create regulatory exposure.

What constitutes an acceptable electronic confirmation. The instrument requires an electronic confirmation that a PDS with a specified date has been given to the acquirer by a licensee or authorised representative (s 5(2)(a)). The instrument does not specify the form or content of that confirmation beyond the date requirement. There may therefore be disputes about whether an electronic statement meets the instrument’s standard.

Notification to ASX may be operationally awkward. The duty to notify ASX in writing within ten business days if there is reason to believe a retail client did not receive the PDS (s 6(b)) creates a direct communications pathway between responsible entities and ASX. Responsible entities must have procedures to identify such situations and a process to prepare and deliver the required ASX notification.

mFund’s s 791C exemption is a precondition. Section 5(2)(e) conditions the responsible entity’s ability to rely on s 5(1) on mFund being the subject of an exemption under s 791C of the Act. Responsible entities must verify that that exemption exists and remains in place for the relevant application; the instrument does not itself confer that other exemption.

Exception for non-restricted issues not defined here. The licensee-level insertion in s 8(2B) exempts the subsection where the licensee reasonably believes an issue is not a restricted issue. The instrument does not define “restricted issue”. Parties must therefore check other parts of the Act or ASIC guidance to determine the boundaries of that exception.

Relevance of who prepared the PDS. The PDS must have been prepared by the responsible entity (s 5(2)(b)(i)). A PDS prepared by a third party will not meet the condition even if the responsible entity has authorised it. Ensure internal publication and authoring records show responsible entity authorship.

Sunset planning. The instrument ceases effect at the start of 1 April 2029 (s 9). Processes built around reliance on the instrument must include a plan for the instrument’s expiry and for how obligations will be handled after that date.

In short, the instrument creates practical traps around timing, evidence capture, interdependence on ASX systems and rule compliance, differing standards of belief, and short notification windows. Designing controls that produce contemporaneous evidence will reduce these risks.

This section sets out practical steps, drawn from the instrument text, that responsible entities, financial services licensees and authorised representatives should take to implement the instrument’s requirements and to create the documentary trail the instrument expects.

For responsible entities

1. Verify the mFund and s 791C status. Confirm that the mFund facility being used is the ASX Managed Fund Settlement Service as defined (s 4) and that mFund is the subject of an exemption under s 791C of the Act for the relevant period (s 5(2)(e)). Maintain a dated record of where and when this verification was made.

2. Author the Product Disclosure Statement. Ensure the PDS that will be referenced in electronic confirmations is prepared by the responsible entity (s 5(2)(b)(i)). Maintain version-control metadata and publication logs to prove authorship and timing.

3. Ensure non-defectiveness as at application time. Review the PDS (including any supplements) to confirm it is not defective at the time the application is made. For schemes with supplementary PDSs, treat the suite (PDS plus supplements) as the relevant disclosure and use the date of the most recent supplement where applicable (s 7; note on subsection 1016A(1)). Keep contemporaneous notes of any content changes and the times they took effect.

4. Capture website availability at application time. Implement a process to capture and timestamp the state of the ASX website showing the PDS availability at the moment applications are made, for example server logs, time-stamped screenshots or archival records. This supports the “reasonably believes” test that the PDS was available free of charge on ASX’s website as at the time the application was made (s 5(2)(d)).

5. Monitor ASX rule compliance. Establish checks to ensure there is no reason to believe that ASX Operating Rules or ASX Settlement Operating Rules requirements have not been satisfied in relation to specific applications and confirmations (s 5(2)(c)). Document the checks and the basis for any conclusions.

6. Post-issue notices to acquirers. Create template written notices that identify the PDS by date, explain that the PDS should have been given to the acquirer and state that a paper or electronic copy is available free of charge. Ensure the templates satisfy s 6(a) and implement procedures to dispatch these notices within five business days of issue.

7. Notification to ASX. Put in place triggers and monitoring to detect statements, complaints or other evidence that an acquirer who is a retail client did not receive the PDS before applying. Prepare procedures to notify ASX in writing within ten business days in such cases, consistent with s 6(b).

8. Record retention. Maintain a secure and searchable records system to retain for seven years: