The Act constructs its regime around a small set of definitional and mapping concepts that determine how existing AMP law and the Code interact.

Definitions and scope. AMP is defined as the entity continued by the Australian Mutual Provident Society’s Act 1910 (s 3(1)). The Act defines Code to mean the Companies (New South Wales) Code and Code regulations to mean the regulations applying as regulations made under the Code because of the Companies (Application of Laws) Act 1981 (s 3(1)). The terms member and officer are defined by reference to AMP and the Code; officer has the same meaning as in the Code (s 3(1)). A reference to the Code or the Code regulations is a reference to the version in force at the commencement of section 4, or, if later regulations under this Act so provide, as in force at a later specified time (s 3(2)). That provides for an initial lock-in or later updating by regulation.

Application by analogy. The central mechanism is analogue application: the Code and Code regulations apply to AMP "as if" AMP had been duly registered and incorporated under the Code on the commencement of s 4 (s 4(1)(a)). Members and officers are treated as if they were members and officers of such a company (s 4(1)(b)). Part 80 of the Supreme Court Rules is also made to apply to AMP, its members and officers in the same way the Code applies (s 4(2)).

Exclusions and exceptions. The Act expressly lists Code provisions that do not apply to AMP in Schedule 1, and gives the Governor regulatory power to disapply specified provisions of the Code or the Code regulations (s 5; s 13(2)). The Schedule enumerates particular sections of the Code (for example, Code ss 35(6)-(9), 37, 39, 82, 217(1) and (2), 274 and 360) as not applying to AMP (Schedule 1). However, the Act reintroduces some Code liability for share-holding members: although members are generally not liable for AMP’s debts on winding up (s 12(1)), s 360 of the Code applies to present and past members who hold or have held shares in AMP (s 12(3)).

By-laws as constitution. The Act makes AMP’s by-laws, lodged under s 2, the functional memorandum and articles for the purposes of application of the Code (s 10(1)-(2)). The by-laws must be divided into parts appropriate for memorandum and articles (s 2(4)), and they may be altered only in accordance with the Code and the Code regulations applying to memoranda and articles (s 10(3)). The Act also carries forward particular demutualisation constraints by linking to the Australian Mutual Provident Society (Demutualisation and Reconstruction) Act 1997 (s 2(4); s 10 note).

Transitional continuity. Schedule 2 establishes continuity mechanics. Existing members continue as members at commencement, subject thereafter to the by-laws (Schedule 2 cl 4). Directors, officers and auditors appointed and holding office immediately before commencement are taken to have been validly appointed as if the Code applied at the time, and they continue in office subject to the Code, the Code regulations and the by-laws (Schedule 2 cls 5-6). Previous meetings (last annual meeting and adjourned meetings) are treated as annual general meetings or adjourned meetings for the purposes of the Code (Schedule 2 cl 7). Schedule 2 also prescribes the requirements for the registered office notice and office hours that AMP must lodge with the CAC (Schedule 2 cl 8).

Regulatory and administrative powers. The Governor has power to make regulations for matters required or convenient for carrying the Act into effect (s 13(1)). The regulations may exempt AMP from specified provisions of the Code or Code regulations (s 13(2)). The Subordinate Legislation Act 1989 is declared not to apply to those regulations (s 13(3)). The CAC is required to accept the proposed by-laws lodged in accordance with s 2 and to issue a certificate for the purposes of the commencement condition (s 2(5)).

Together, these concepts operationalise a hybrid governance model: AMP retains its statutory corporate identity while adopting the procedural and substantive corporate governance framework of the Code, subject to specified carve outs and regulated exceptions, with particular transitional treatment of office-holders, auditors and members.

Entities and persons named in the Act. The immediate subjects of the Act are AMP, its members, and its officers. The Act’s definitions make AMP the Australian Mutual Provident Society continued under the 1910 Act (s 3(1)). Member and officer are used throughout, and the Code’s meanings are imported for officers (s 3(1)). The Corporate Affairs Commission (CAC) and the Minister have specific roles in the commencement and registration process (s 2(3)-(5); Schedule 2 cl 8). The Governor is empowered to make regulations under s 13.

Who pays. Financially, the Act mainly places existing liabilities on AMP’s property for debts and winding-up costs: present and past members are not liable to contribute to the property of AMP for payment of debts or the costs of winding up, subject to the exception for members who hold shares (s 12(1)-(3)). Therefore, the primary financial obligation for corporate liabilities rests with AMP itself, not with its general membership, except where Code s 360 is engaged for share-holding members (s 12(3)).

Decision-makers and delegated authority. The Minister must approve the proposed by-laws lodged by AMP before proclamation may be made under s 2(2)-(3). The CAC is required to accept the lodged by-laws and to issue a certificate that the by-laws have been lodged (s 2(3), (5)). The Governor makes regulations for matters necessary to carry the Act into effect, and those regulations may further specify which Code provisions apply or do not apply to AMP and its members and officers (s 13(1)-(2)). By-laws may be altered only in accordance with the Code and Code regulations that apply to memoranda and articles, which places procedural control over constitutional amendments in the Code machinery (s 10(3)).

Operationally affected officers and stakeholders. Current directors, officers and auditors are taken to have been appointed in accordance with the Code and by-laws (Schedule 2 cls 5-6) and continue in office subject to the Code, the Code regulations and the by-laws. Members whose membership pre-exists the commencement continue as members but their ongoing status is subject to the by-laws (Schedule 2 cl 4). Meetings adjourned or held prior to commencement are given recognition under the Code (Schedule 2 cl 7).

Third-party interactions. The Act narrows administrative interactions in certain respects: annual returns are to be accompanied only by the documents that the Commonwealth Life Insurance Act 1945 requires (s 9), which channels some disclosure obligations into Commonwealth insurance law rather than the Code’s usual annual-return requirements. The CAC is authorised to accept notices in the forms prescribed under the Code for registered office and hours (Schedule 2 cl 8), and the Subordinate Legislation Act 1989 does not apply to regulations under s 13(3), which affects the procedural regime for any delegated instruments.

Concentrations and exceptions. A discrete group,members who hold or have held shares,are treated differently with respect to winding-up liability, as s 12(3) resurrects Code s 360 for those persons. The Act also removes particular Code provisions for AMP via Schedule 1, which creates a set of special-purpose exceptions affecting the way AMP’s governance will operate in particular areas listed in that Schedule.

In summary, the Act affects four functional groups: AMP as corporate entity; its members generally and a subset who have held shares; officers, directors and auditors who occupy governance roles; and government regulators,the Minister, Governor and CAC,who control commencement, form of by-laws and the detailed regulatory carve outs.

The Act creates rights and duties primarily by invoking the Code and the Code regulations, and by prescribing how AMP’s by-laws operate as the constitution for those purposes.

Duty to comply with Code as applied. Subject to the Act’s qualifications, AMP, its members and its officers are subject to the obligations, duties and procedural requirements of the Code and the Code regulations as if AMP were a company registered under the Code on the commencement day (s 4(1)). That brings into force Code-based duties of directors and officers as defined in the Code, and procedural duties attaching to membership and corporate administration. Sections 69 and 226(9) of the Code are explicitly applied with the effect that conversion and director-related provisions are engaged as though AMP were a company limited by guarantee (s 7).

By-laws as constitution and amendment regime. The by-laws lodged under s 2 are designated to be the memorandum and articles of AMP for the purposes of Code application (s 10(2)(a)). They bind AMP and persons who are members "from time to time" (s 10(2)(b)). Alteration or addition to the by-laws is permitted only in accordance with the Code and Code regulations that apply to memoranda and articles of association, so constitutional change is subject to the Code’s formal procedures (s 10(3)). The by-laws must be divided into material appropriate for a memorandum (Part 1) and material appropriate for articles (Part 2) as required by the demutualisation Act (s 2(4); s 10(1) note).

Membership and membership rights. Membership is to be governed by the by-laws, subject to the demutualisation Act’s constraints (s 11). The Act restricts a particular interpretation of class rights under the Code: holding a life insurance policy, annuity, or other contract with differing terms does not, by itself, constitute membership in a class having special rights for purposes of Code s 127 (s 8). That alters how class rights inquiries are to be resolved in disputes involving AMP’s policyholders.

Annual reporting duty. The Act narrows the documents that must accompany AMP’s annual return under the Code regulations: only the documents required by section 52 of the Commonwealth Life Insurance Act 1945 must accompany AMP’s annual return (s 9). This establishes a cross-reference that aligns AMP’s disclosure obligations with Commonwealth insurance law for annual return purposes.

Meetings, officers and auditors. Transitional clauses treat prior appointments and meetings as valid under the Code and by-laws on commencement. Directors and other officers appointed before commencement and holding office immediately before commencement are taken to have been appointed in accordance with the Code and the by-laws and continue subject to the Code and by-laws (Schedule 2 cl 5). Similarly, auditors appointed before the commencement remain auditors and are taken to have been appointed under the Code and by-laws, and continue subject to the Code and by-laws (Schedule 2 cl 6). The last annual meeting held before commencement is taken to have been an annual general meeting for Code purposes, and adjourned meetings are carried forward (Schedule 2 cl 7).

Liability and rights on winding up. The general rule is that present and past members are not liable to contribute to AMP’s debts or winding-up costs; AMP’s property alone is liable (s 12(1)-(2)). An exception applies where present or past members have held shares: Code s 360 applies to those persons, thereby potentially reimposing contributory liability consistent with the Code for share-holders (s 12(3)).

Regulatory duties. The Governor may make regulations as necessary for carrying the Act into effect, and may provide that specified Code provisions do not apply to AMP or to its members or officers (s 13(1)-(2)). The Act further excludes the Subordinate Legislation Act 1989 from applying to those regulations (s 13(3)), which affects the procedural duties attached to delegated instruments.

Administrative duties. Schedule 2 requires AMP to lodge notice of its proposed registered office with the CAC "on, or as soon as practicable after, the commencement" and permits AMP to lodge notice of office hours during which the registered office is to be open to the public (Schedule 2 cl 8(1)). The notices must be in forms prescribed for Code purposes concerning s 217(1) and (2) of the Code and must comply with Code s 530A (Schedule 2 cl 8(2)). The CAC is authorised to accept these notices (Schedule 2 cl 8(3)).

Overall, the Act imports and binds AMP and its governance actors to the Code’s duties, while specifying constitutional mechanics through the by-laws and making targeted statutory adjustments for membership, reporting and liability.

The Act does not create a standalone penalty regime within its text. Instead, enforcement and remedial mechanisms operate predominantly by importing the enforcement architecture of the Code and associated court rules, subject to the Act’s modifications and exclusions.

Court procedure and jurisdiction. Part 80 of the Supreme Court Rules is made to apply to AMP, its members and its officers in the same manner as the Code and the Code regulations apply (s 4(2)). That connects enforcement and dispute resolution for Code-based obligations to the Supreme Court procedural framework, enabling court-based remedies and applications to be pursued under the procedural rules that govern corporate disputes.

Code-based enforcement. Because the Act makes the Code apply to AMP "as if" it had been duly registered, the Code’s enforcement provisions, officer duties, derivative actions, remedies for breaches of directors’ duties and other statutory remedies under the Code will be available in relation to AMP, except where the Act or regulations specifically exclude particular Code provisions (s 4(1); s 5; s 13(2)). The Schedule 1 list of Code sections that do not apply to AMP removes certain Code mechanisms in specified contexts; parties must consult that Schedule when determining which enforcement pathways are available (s 5; Schedule 1).

Regulatory instruments. The Governor’s regulations may specify that certain provisions of the Code or Code regulations do not apply to AMP or to its members and officers (s 13(2)). Because the Subordinate Legislation Act 1989 does not apply to those regulations (s 13(3)), the usual procedural and review mechanisms that attend subordinate legislation may not apply, which could affect judicial review or parliamentary scrutiny processes, to the extent those are tied to the Subordinate Legislation Act.

Administrative acceptance and certification. The CAC is required to accept the proposed by-laws lodged in accordance with s 2 and to issue a certificate for the purposes of commencement (s 2(5)). That administrative certification has a direct legal effect on the commencement of the Act’s operative application to AMP. Disputes about the CAC’s acceptance or the validity of the by-laws would therefore be litigable within the usual administrative and corporate law frameworks, and the Supreme Court rules imported for corporate disputes would govern procedure (s 4(2); s 2(3), (5)).

Member liability enforcement in winding up. The Act prescribes that AMP’s property alone is liable to meet debts on winding up and that members are not liable to contribute, but it preserves Code s 360 for any member who holds or has held shares in AMP (s 12(1)-(3)). Enforcement of contribution obligations in a winding-up would therefore follow the Code’s mechanisms where s 360 is engaged; otherwise, the claimants’ recourse is limited to AMP’s assets.

No express new offences. The Act contains no express criminal offences or pecuniary penalties in its text. Enforcement therefore depends on the Code’s civil and potentially criminal provisions where those are imported, and on court-based remedies administered under the Supreme Court Rules applied by s 4(2). Compliance failures that the Code would treat as breaches of directors’ duties, statutory reporting obligations or other company law contraventions will be actionable to the extent the relevant Code provisions apply to AMP and are not excluded by Schedule 1 or later regulations made under s 13(2).

Practical enforcement consequences. Practitioners should assess each enforcement question by (1) identifying the Code provision that would ordinarily govern conduct, (2) checking whether the Act or regulations have disapplied that provision in whole or in part (s 5; s 13(2)), and (3) invoking the Supreme Court procedural rules that apply (s 4(2)). Administrative actions tied to commencement and registration obligations are enforceable as they relate to the CAC and the Minister’s roles, given the statutory duties these actors have under s 2 and Schedule 2 cl 8.

This Act is expressly designed to integrate AMP’s governance into the Code while preserving certain statutory relationships and limiting cross-application of other State company law.

Non-constitution as a company for other State laws. The Act explicitly provides that nothing in it is to be taken as constituting AMP as a company for the purposes of any law, or previous law, of the State relating to companies (s 6). That statement limits the Act’s effect to making the Code and Code regulations apply to AMP, without converting AMP’s legal character for all other statutory or regulatory regimes. Practitioners should not assume that other State company laws outside the Code are engaged merely because the Code is applied to AMP under this Act.

Cross-reference to Commonwealth insurance law. The Act narrows certain reporting requirements by tying AMP’s annual return attachments to the Commonwealth Life Insurance Act 1945: the only documents that regulation 56A(b)(ii) of the Code regulations requires to accompany an annual return of AMP are those that section 52 of the Life Insurance Act 1945 requires to be lodged for the relevant financial year (s 9). This cross-reference channels some disclosure and reporting obligations into Commonwealth insurance law as opposed to the Code’s typical corporate disclosure regime.

Demutualisation overlay. Section 2 and the notes to s 10 refer to the Australian Mutual Provident Society (Demutualisation and Reconstruction) Act 1997. The Act requires AMP’s proposed by-laws to be divided into parts appropriate for a memorandum and articles in a manner consistent with s 11(2) of that 1997 Act (s 2(4); s 10 note). Those cross-references incorporate legislative design choices from the demutualisation statute into the constitutional structure imposed by the Code.

Compatibility with regulatory instruments. The Act gives the Governor power to make regulations necessary or convenient for carrying out the Act (s 13(1)). Those regulations may specify that certain Code provisions or Code regulations do not apply to AMP or to its members or officers (s 13(2)). Importantly, the Subordinate Legislation Act 1989 does not apply to these regulations (s 13(3)), which affects the statutory architecture for delegated instruments and may limit some procedural statutory oversight normally provided by the Subordinate Legislation Act.

Interaction with the Companies (Application of Laws) Act 1981. The Act defines Code regulations as the provisions applying as regulations made under the Code because of section 7 of the Companies (Application of Laws) Act 1981 (s 3(1)). It also provides, in s 3(2), that references to the Code or Code regulations are to the versions in force at the commencement of s 4, or as updated by regulations under this Act at a later specified time. That creates an initial freeze or a controlled updating mechanism via regulation.

Transitional continuity with prior AMP statute. The Act preserves AMP’s identity and continuation under the Australian Mutual Provident Society’s Act 1910 (Schedule 2 cl 2). It therefore operates alongside that prior enabling statute rather than replacing it, which affects the interaction between pre-existing AMP legal obligations and the newly applied Code obligations.

Selective non-application of Code provisions. Schedule 1 lists specific Code sections that do not apply to AMP (Schedule 1). Users must cross-check any Code-based compliance question against Schedule 1 to determine whether a given Code section is operative for AMP. For example, Schedule 1 lists Code s 360 among other sections as not applying; however, s 12(3) of this Act reintroduces Code s 360 in the particular circumstance of members holding shares. That demonstrates the Act can both disapply and selectively reapply Code provisions in different contexts.

Administrative and procedural forms. Schedule 2 cl 8 requires notices for registered office and office hours to be in forms prescribed under the Code for the purposes of Code s 217(1) and (2) and to comply with Code s 530A. The CAC is authorised to accept such notices (Schedule 2 cl 8(3)). That aligns AMP’s registry interactions with the Code’s forms and filing requirements.

In short, the Act creates an interface layer: it imports the Code’s corporate governance and enforcement mechanisms for AMP while preserving AMP’s statutory identity and channeling some reporting obligations into Commonwealth insurance law. It also provides for selective exclusions and controlled updates via regulations that are outside the Subordinate Legislation Act 1989 framework.

The Act text contains embedded amendment annotations that indicate targeted legislative changes. The visible amendment notes in the source are the primary record provided by this instrument.

1996 amendment to regulations power. Section 13 carries an annotation "s 13: Am 1996 No 30, Sch 1." That indicates the regulations power in s 13 was amended by Act number 30 of 1996 (Schedule 1). The text of s 13 in the current Act gives the Governor power to make regulations, permits disapplication of specified Code provisions by regulation (s 13(2)), and exempts those regulations from the Subordinate Legislation Act 1989 (s 13(3)).

1997 demutualisation amendments. Several sections include annotations "Am 1997 No 56, Sch 1" with bracketed paragraph numbers indicating particular amendment entries. Sections 2, 10, 11 and 12 show those amendment annotations:

• Section 2: "s 2: Am 1997 No 56, Sch 1 [1]." In the text, s 2(4) and related transitional rules reference the Australian Mutual Provident Society (Demutualisation and Reconstruction) Act 1997, signalling that the 1997 Act introduced the division of by-laws into Parts 1 and 2 and other demutualisation-related mechanics.
• Section 10: "s 10: Am 1997 No 56, Sch 1 [2]." The provision that by-laws are taken to be the memorandum and articles and the constraints on alteration by Code procedures bear that annotation.
• Section 11: "s 11: Am 1997 No 56, Sch 1 [3]." Membership criteria are linked to the demutualisation Act.
• Section 12: "s 12: Am 1997 No 56, Sch 1 [4] [5]." Member liability rules and the interplay with Code s 360 reflect the 1997 amendment entries.

2003 repeal entry. The Act contains a notation for section 14 that displays "s 14: Rep 2003 No 82, Sch 3." Section 14 in the Act is marked as repealed. The source does not include the repealed text, but it records that s 14 was repealed by Act number 82 of 2003 (Schedule 3).

Notes on amendment provenance. The amendment annotations supplied are the only documentary amendment history present in the Act text provided. They identify specific amending Acts by year and number (for example, 1996 No 30; 1997 No 56; 2003 No 82) and, in the case of the 1997 Act, indicate cross-linkage to the demutualisation statute. The source does not provide the substantive amending instrument texts or parliamentary explanatory material beyond the inline annotations.

Practical effect of amendment history. The annotations show that the Act was adjusted to accommodate AMP’s demutualisation and reconstruction processes in the late 1990s and that certain provisions were updated or repealed in later years. Users should consult the amending Acts themselves for precise amendment language and for any consequential changes not visible in the consolidated text. The Act itself provides for its own interaction with the demutualisation Act via s 2(4) and the Schedule references.

Limitations of this record. The source gives the amendment citations but not the full legislative history such as exposure drafts, second reading speeches, or earlier versions beyond the quoted annotations. For a complete chronological account of amendments, the primary amending Acts referenced should be inspected. The Act as provided is the operative consolidated text with in-text annotations indicating the amending instruments and where repeals have been recorded.

The Act text supplied does not cite any judicial decisions or contain a running list of litigation concerning its application. No cases or judgments are named in the statutory text or in the schedules provided. Consequently, this Act’s text does not record any litigation history.

That absence does not mean litigation is impossible or has not occurred in practice; it means the Act itself contains no in-built references to case law. For practitioners, the Act creates several predictable categories of dispute that would be litigated under the Code-anchored framework the Act imports. Those categories are suggested by the Act’s mechanics and transitional rules in the text:

• Interpretation and enforcement of by-laws. The by-laws become the memorandum and articles for Code purposes (s 10(2)). Disputes may arise about the correct interpretation of those by-laws, the validity of by-laws lodged for commencement, or procedural compliance with Code-based amendment requirements (s 10(3); s 2(3)-(5)). Such disputes would be litigated by reference to the Code and the by-laws, and court procedure would follow the Supreme Court Rules applied under s 4(2).

• Commencement and CAC certification. The commencement condition requires AMP to lodge proposed by-laws approved by the Minister and for the CAC to issue a certificate that the by-laws have been lodged (s 2(2)-(3), (5)). Disputes could concern whether the CAC properly accepted a lodgement or whether the Minister’s approval complied with statutory requirements. The Act makes the CAC’s role mandatory ("is required to accept" in s 2(5)), which might give rise to administrative law challenges in appropriate cases.

• Application and scope of excluded Code provisions. Because Schedule 1 lists Code provisions that do not apply to AMP (s 5; Schedule 1), litigation could concern whether a given Code section applies or has been effectively disapplied by the Act or by regulations under s 13(2). The Act also selectively reintroduces Code s 360 for share-holding members (s 12(3)), which may produce litigation about contributory liability in winding-up scenarios.

• Members’ liability on winding up. The Act limits members’ liability (s 12(1)-(2)) while preserving Code s 360 for members who have held shares (s 12(3)). Winding-up proceedings and creditor/member disputes could engage these provisions and the Code’s insolvency-related mechanisms.

• Officer duties and breaches. The Act imports the Code’s duties for officers and directors (s 4(1); s 7). If a director or officer is alleged to have breached Code duties, enforcement would proceed under the Code’s remedies, with procedural application through the Supreme Court Rules (s 4(2)).

• Reporter and disclosure disputes. The Act redirects the annual return attachments to Commonwealth insurance reporting requirements (s 9), which could create inter-jurisdictional disputes about compliance and disclosure obligations between State Code requirements and Commonwealth insurance law.

Absence of recorded cases means anyone researching precedent must search court databases, law reports and tribunal records for decisions that have arisen from AMP’s conversion/regulatory arrangements or from disputes raising the Act’s provisions. Where disputes are grounded in the Code as applied, case law construing the corresponding Code provisions will be relevant, but practitioners must track whether particular Code sections were excluded for AMP by Schedule 1 or by regulations under s 13(2).

This Act contains several structural and procedural features likely to produce traps for the unwary. These are factual mechanics grounded in the Act’s text and its transitional framework.

Commencement is conditional and certificate-driven. The majority of the Act does not come into force automatically. Proclamations under s 2 may not be made unless AMP has lodged proposed by-laws approved by the Minister and the CAC has issued a certificate stating the proposed by-laws have been lodged (s 2(2)-(3)). Further, the CAC is "required to accept" the proposed by-laws lodged in accordance with s 2 and to issue the certificate (s 2(5)). Parties should not assume the Code’s application begins until these administrative preconditions are met and properly evidenced.

By-laws must be structured to match memorandum/articles mapping. The Act requires the by-laws to be divided into Part 1 (appropriate for a memorandum) and Part 2 (appropriate for articles) as a condition of commencement and application (s 2(4)). The by-laws lodged under s 2 become the memorandum and articles for Code purposes (s 10(2)). If the by-laws are not properly divided or drafted in alignment with this structure, procedural challenges to validity or to the availability of certain Code mechanisms could arise.

Selective non-application of Code sections. Schedule 1 lists Code provisions that do not apply to AMP (s 5; Schedule 1). Lawyers should not assume all Code sections are in play. For each Code-based compliance or enforcement question, the Schedule must be checked to confirm whether that Code provision applies. Conversely, s 12(3) reintroduces Code s 360 for members who hold or have held shares despite its appearance in Schedule 1, so practitioners must track exceptions within exceptions (s 12(3); Schedule 1).

"Not a company" declaration has legal effects. The Act expressly states that nothing in it is to be taken as constituting AMP a company for the purposes of any State law relating to companies (s 6). That means other State company laws outside the Code may not apply to AMP simply because the Code does. Practitioners should avoid assuming that a mere application of the Code converts AMP into a company for unrelated statutory regimes.

Annual return attachments tied to Commonwealth law. The Act limits the documents required for AMP’s annual return to those required under section 52 of the Commonwealth Life Insurance Act 1945 (s 9). If compliance practitioners rely on standard Code annual-return requirements, they may over- or under-provide the wrong material. The right test is the Commonwealth insurance statute, not the Code’s default regulation 56A(b)(ii).

Regulations outside the Subordinate Legislation Act 1989 regime. Regulations under s 13 are expressly exempted from the Subordinate Legislation Act 1989 (s 13(3)). That affects the usual statutory checks on delegated instruments, such as the form of parliamentary tabling and review mechanisms that the Subordinate Legislation Act might otherwise require. Users should not assume those procedural protections apply to regulations made under s 13.

Transitional cessation of old by-laws. The by-laws in force immediately before commencement cease to be by-laws of AMP on the commencement (Schedule 2 cl 3). Although members and officers are carried forward for continuity purposes (Schedule 2 cls 4-6), the constitutional instrument in force changes at commencement, and operational governance must be administratively aligned to the newly lodged by-laws.

Member liability nuance. The general rule is that present and past members are not liable to contribute to AMP’s property for debts or winding-up costs; AMP’s property alone is liable (s 12(1)). But s 12(3) brings Code s 360 into play for members who hold or have held shares. Practitioners must identify whether an individual member has held shares, because that status materially changes contributory exposure on winding up.

Forms and registered office notice technicalities. Schedule 2 cl 8 requires AMP to lodge notice of its proposed registered office and possibly office hours "on, or as soon as practicable after, the commencement," and those notices must be in the forms prescribed for Code s 217(1) and (2) and comply with Code s 530A (Schedule 2 cl 8(1)-(2)). Failure to lodge these notices in the correct form promptly may produce administrative non-compliance even where substantive governance issues are otherwise settled.

Alteration of by-laws only under Code procedures. By-laws may be altered or added to only in accordance with the Code and the Code regulations applying to memoranda and articles of association (s 10(3)). Attempts to change AMP’s constitutional rules outside the Code’s formal amendment procedures will be ineffective.

Ministerial approval as a gating item. Ministerial approval of proposed by-laws is a statutory prerequisite to proclamation under s 2(3)(a). That places significant practical control over the timing and content of AMP’s constitutional arrangements with the executive branch.

Taken together, these “gotchas” are procedural and legal technicalities that can have operational impact on commencement, constitutional form, disclosure, member liability, and regulatory oversight. Each must be checked against the Act’s text,particularly ss 2, 4, 5, 9, 10, 12, 13 and Schedule 2,before action is taken.

This section sets out practical, text-grounded steps and responsibilities to bring AMP and its officers into compliance with the statutory framework established by the Act. Each step cites the relevant provision.

1. Prepare and lodge by-laws approved by the Minister before proclamation (s 2(2)-(3); s 10(1)).

   • Responsibility: AMP legal and governance team to draft; Minister’s office to approve.
   • Requirements: Divide proposed by-laws into Part 1 (memorandum-appropriate matter) and Part 2 (articles-appropriate matter) consistent with s 2(4) and the demutualisation Act referenced (s 2(4); s 10(1) note). Lodge those by-laws with the Corporate Affairs Commission in the form required by the Code.

2. Obtain CAC certificate of lodgement (s 2(3), (5)).

   • Responsibility: AMP to lodge; CAC to accept and certify.
   • Note: The Act requires the CAC to accept compliant by-laws and issue the certificate (s 2(5)). The proclamation needed to bring the Act into force cannot be made until these administrative steps occur (s 2(2)-(3)).

3. Ensure by-laws are treated as memorandum and articles and maintain amendment procedures under the Code (s 10(2)-(3)).

   • Responsibility: Board and company secretary to maintain records and follow Code procedures when altering the by-laws.
   • Operational step: When proposing constitutional amendments, follow the Code and Code regulations applying to memoranda and articles to ensure validity.

4. Align membership rules to by-laws (s 11; Schedule 2 cl 4).

   • Responsibility: Membership administration to update registers and procedures.
   • Action: Confirm that all persons who were members immediately before the commencement continue as members on commencement (Schedule 2 cl 4), and thereafter that membership is governed by the new by-laws (s 11; Schedule 2 cl 4).

5. Treat current officers and auditors as validly appointed under the Code and by-laws, and ensure ongoing compliance with Code duties (Schedule 2 cls 5-6).

   • Responsibility: Board, auditors, and compliance officers.
   • Action: Record that existing directors, officers and auditors are taken to have been appointed under the Code and the by-laws and confirm they understand Code duties, reporting, and removal procedures (Schedule 2 cls 5-6).

6. Adjust annual return and disclosure practices to reflect the Life Insurance Act linkage (s 9).

   • Responsibility: Finance, company secretary, compliance.
   • Action: For the annual return, provide only those documents required by section 52 of the Life Insurance Act 1945. Do not assume the full suite of Code regulation 56A(b)(ii) attachments applies.

7. File registered office and office hours notices promptly (Schedule 2 cl 8).

   • Responsibility: Company secretary to lodge notices with the CAC "on, or as soon as practicable after, the commencement" (Schedule 2 cl 8(1)).
   • Form and compliance: Use the forms prescribed under Code s 217(1) and (2) and ensure compliance with Code s 530A as required by Schedule 2 cl 8(2). The CAC is authorised to accept these notices (Schedule 2 cl 8(3)).

8. Audit and meeting records.

   • Responsibility: Board and auditors.
   • Action: Note that the last annual meeting before commencement is taken to have been an annual general meeting for Code purposes, and adjourned meetings are treated as adjourned in Code terms (Schedule 2 cl 7). Ensure minute books and meeting records reflect that treatment.

9. Assess member liability exposure.

   • Responsibility: Finance and legal teams.
   • Action: Generally, members are not liable for AMP’s debts on winding up (s 12(1)). However, identify any members who hold or have held shares, because Code s 360 applies to those persons (s 12(3)). For those members, treat contributory liability as potentially engaged in winding-up scenarios.

10. Check Schedule 1 exclusions and s 13 regulations before relying on particular Code provisions.

    • Responsibility: Legal counsel to maintain a Schedule 1 matrix.
    • Action: Before relying on a specific Code provision in corporate governance, compliance or litigation, verify whether that provision is excluded by Schedule 1 (s 5; Schedule 1). Also monitor regulations made under s 13 that may disapply additional provisions of the Code or Code regulations (s 13(2)). Note that the Subordinate Legislation Act 1989 does not apply to those regulations (s 13(3)), so procedural expectations for delegated instruments may differ.

11. Observe procedural requirements for by-law amendment.

    • Responsibility: Board and company secretary.
    • Action: Any change to the by-laws must conform to the Code and relevant Code regulations on altering memoranda and articles (s 10(3)). Follow the Code’s formal notice, voting and filing requirements for constitutional amendments.

12. Maintain compliance programmes reflecting Code duties for directors and officers.

    • Responsibility: Board, risk and compliance functions.
    • Action: Train directors and officers on Code-based duties imported by s 4(1) and on any Code sections applied specifically under the Act (including s 69 and s 226(9) as applied under s 7). Ensure Director induction and continuous disclosure processes are updated.

13. Recordkeeping and public accessibility.

    • Responsibility: Company secretary.
    • Action: Keep accurate registers and ensure the registered office and office hours are accessible to the public as contemplated by Schedule 2 cl 8. Maintain company books in a form compatible with both the Code and relevant insurance law reporting requirements.

14. Engage regulator liaison and seek confirmation where uncertain.

    • Responsibility: Senior legal counsel and regulatory affairs officers.
    • Action: Where there is doubt about the applicability of a Code provision, seek interpretative guidance from the CAC or legal advice. For matters such as the validity of by-laws, Ministerial approval and CAC certification, document interactions with the Minister’s office and the CAC to create an administrative record consistent with s 2(3)-(5) and Schedule 2 cl 8.

These compliance steps derive directly from the Act’s operative provisions: ss 2, 3, 4, 5, 9, 10, 11, 12, 13 and Schedule 2. Following them will align AMP’s constitutional arrangements, reporting and governance with the statutory rules the Act prescribes.