The Corporations Act provisions concerning removal of a responsible entity
48 Section 601FM of the Corporations Act provides a mechanism by which the members of a registered scheme may remove the responsible entity. It states:
(1) If members of a registered scheme want to remove the responsible entity, they may take action under Division 1 of Part 2G.4 for the calling of a members' meeting to consider and vote on a resolution that the current responsible entity should be removed and a resolution choosing a company to be the new responsible entity. The resolutions must be extraordinary resolutions if the scheme is not listed.
(2) If the members vote to remove the responsible entity and, at the same meeting, choose a company to be the new responsible entity that consents, in writing, to becoming the scheme's responsible entity:
(a) as soon as practicable and in any event within 2 business days after the resolution is passed, the current responsible entity must lodge a notice with ASIC asking it to alter the record of the scheme's registration to name the chosen company as the scheme's responsible entity; and
(b) if the current responsible entity does not lodge the notice required by paragraph (a), the company chosen by the members to be the new responsible entity may lodge that notice; and
(c) ASIC must comply with the notice when it is lodged.
(3) A person must not lodge a notice under subsection (2) unless the consent referred to in that subsection has been given before the notice is lodged.
49 Significantly, it provides for the calling of a members meeting to consider and vote on a resolution to remove and a resolution choosing a new company. It has been held that conditional resolutions of the kind proposed to members in this case meet the requirements of s 601FM(1): City Pacific Limited, in the matter of City Pacific Limited v Bacon (No 2) [2009] FCA 772; (2009) 178 FCR 81 at [30].
50 Generally, a body corporate may pass a resolution that is conditional: VAW (Kurri Kurri) Pty Ltd v Scientific Committee [2003] NSWCA 297; (2003) 58 NSWLR 631 at [124]. However, it is to be noted that the Corporations Act contemplates that the members of a registered scheme may pass a resolution removing the responsible entity whilst not, at the same meeting, passing a resolution 'choosing a company to be the new responsible entity', in which case the responsible entity must ensure the scheme is wound up: s 601NE(1)(d). Therefore, it must be intended that there could be a resolution to remove a responsible entity without a resolution to choose a new responsible entity being considered and not passed. That is to say, resolutions that have conditionality of the kind expressed in the Resolutions are not required by the Corporations Act. Therefore, it is not the case that there must be a choice of a new responsible entity in order for there to be a valid resolution to remove.
51 The somewhat strange requirement expressed in s 601NE(1)(d) to the effect that where a responsible entity has been removed without replacement the responsible entity must apply to wind-up the scheme sits somewhat uncomfortably with other provisions concerning appointment of a temporary responsible entity, convening meetings by that temporary responsible entity for the purpose of 'choosing' a new responsible entity and appointing a person to be responsible for winding up: s 601FN, s 601FQ and s 601NF. In that context, it is not clear whether the responsible entity that is to apply to wind up is the removed responsible entity or an entity that has been appointed as a temporary responsible entity.
52 Nevertheless, the terms of s 601NE(1)(d) may explain why particular care was taken to propose conditional resolutions. They are a reason why care must be taken before concluding that Resolution A could have operative effect if Resolution B is found to be contrary to the requirements of the Corporations Act.
53 The important point to note for present purposes is the requirement that a resolution is required to be put to members 'choosing' the new responsible entity.
54 The same language is to be found in s 601FL which deals with retirement by a responsible entity. It provides that a responsible entity may retire by convening a meeting of members to explain its reasons for wanting to retire and to enable the members to vote on a resolution to choose a new responsible entity: s 601FL(1). If the members choose a new responsible entity then the notice procedure requesting ASIC to alter the record of the scheme's registration must be followed: s 601FL(2). If the members do not choose a new responsible entity then the current responsible entity may apply for appointment of a temporary entity: s 601FL(3) and s 601FP.
55 So, it is in a context where a number of provisions refer to choosing a responsible entity that the language used in s 601FK is to be considered. It provides that a company 'cannot be chosen or appointed as the responsible entity or temporary responsible entity of a registered scheme unless it meets the requirements of s 601FA'. In context, the reference to 'chosen' must encompass the choice made by members by a resolution.
56 Section 601FA provides that the responsible entity of a managed investment scheme must be a public company that holds an AFSL authorising it 'to operate a managed investment scheme'.
57 For reasons I have given, Huntley's AFSL does not authorise it to operate the Project. The fact that Huntley is authorised to operate 'a managed investment scheme', but not the scheme in question does not meet the requirements of s 601FK.
58 The language used in s 601FA must be read in the context of the detailed provisions concerning application for and grant of an AFSL. As I have noted, they require the licence to be granted with a condition that specifies the particular financial products or classes of financial products to which it applies and the licence may apply to a specific managed investment scheme. In that context, it would defeat the detailed provisions concerning AFSLs if the singular authority to operate a named scheme was sufficient to satisfy the requirements of s 601FA in respect of a different scheme on the basis that the responsible entity was licensed to operate 'a managed investment scheme'. Properly understood, the requirement of s 601FA is that the responsible entity be the holder of an AFSL that authorises the operation of a managed investment scheme of the requisite kind, namely the particular scheme that the entity is operating (or is chosen to operate).
59 It was argued for Mr Scott that the requirements of s 601FK would be met if, by the time Huntley came to be included on the record of the scheme's registration, its AFSL covered the Project. Support was sought to be obtained from the fact that it is not until the record is changed that any removal of SPL will take effect: Huntley Management Limited v Australian Olives Limited [2010] FCAFC 98; (2010) 186 FCR 430 at [63].
60 However, the submission advanced ignores the express requirement that both at the time the responsible entity is chosen and when it is appointed that it must meet the requirements of s 601FA. So, if it does not do so it can neither be chosen nor appointed. There is logic in the legislative scheme requiring the licence to be held at the time the resolution is presented to members to consider choosing the proposed new responsible entity. It would pose difficulties for members if they could be required to vote for a new responsible entity in circumstances where they could not know with certainty whether the proposed new responsible entity would obtain the requisite licence and if so how long that may take.
61 Notably, s 601FM(2) requires the removed responsible entity as soon as practicable and in any event within two business days to lodge a notice asking ASIC to alter the register to name the chosen company as the scheme's responsible entity. This provision does not contemplate an extended hiatus.
62 It follows that at the time when Resolution B was considered at the meeting on 23 July 2018 (assuming for present purposes that it was a valid meeting of members), it was a resolution to choose Huntley as the responsible entity at a time when s 601FK provided that Huntley could not be chosen. The resolution purported to make a choice that was prohibited by the terms of the Corporations Act.
63 Further, it was a resolution which, if passed, would require SPL to proceed as soon as practicable and in any event within two business days to lodge with ASIC a notice asking it to alter the record of the scheme's registration if the consent of Huntley was forthcoming. If SPL does not lodge the notice as required, then Huntley may do so (assuming it has been validly chosen): s 601FM(2)(b). Otherwise, if there is no consent from Huntley then by operation of s 601FM(3) the notice must not be lodged with ASIC.
64 SPL has not lodged the notice because it takes the view that the Resolutions were invalid and has commenced these proceedings. Huntley has not lodged the notice because it is still seeking to amend its AFSL to include the Project in the list of managed investment schemes in its licence that it may operate. In that regard it appears that Huntley is not relying upon the contention advanced by Mr Scott to the effect that it is authorised by its AFSL to operate the Project (a contention I have not accepted).
65 In an affidavit relied upon by Mr Scott, Mr Foxall (an employee of Huntley) says that on 24 January 2018 Huntley lodged an application to vary its AFSL to include the TFS Sandalwood Project 2002 and approval was obtained on 7 June 2018. He then says that after 7 June 2018 (both before and after the meeting on 23 July 2018), Huntley lodged an application to include other TFS Sandalwood projects including the Project. ASIC has asked Huntley to provide further information and Huntley has provided that information and Huntley is 'waiting for the Approval to be granted'.
66 Mr Foxall also says that in his experience which he says includes dealing with at least 40 managed investment schemes it is ASIC's practice that it does not issue variations to AFSLs enabling a responsible entity to become a new responsible entity until after the relevant resolutions have been passed by members of the scheme. Submissions were advanced relying upon that evidence. There was no attempt to engage support from ASIC in that submission which is significant given that ASIC was notified of the application and did not seek to appear. If the orders sought were fundamentally opposed to a practice followed by ASIC which ASIC sought to maintain then it would be expected the submissions to that effect would be advanced by ASIC.
67 However, even if that evidence is accepted, the practice adopted by ASIC concerning applications for licences though relevant to the interpretation of the licences themselves (in the manner I have described above concerning the regulatory guides) is not a matter to be brought to account when interpreting s 601FK.
68 As I have noted, for Mr Scott, reliance was placed upon the decision in Huntley Management Ltd v Australian Olives Ltd. In that decision, the Court made the following observation at [65] concerning the process for changing a responsible entity:
The legislation envisages four steps: the passing of the resolution by the members of the scheme; the lodgement of a request with ASIC that it alter its record in order to give effect to that resolution; ASIC's consideration of that request; and the alteration by ASIC of its record in order to give effect to the request.
69 The issue before the Court in that case concerned the precise point in time when the changeover of a responsible entity for a registered scheme becomes effective. The Court held that it did not become effective unless and until the ASIC record is relevantly altered: at [66]. However, that conclusion does not bear upon the resolution of the present question as to what is required as part of the first step, namely the passing of the resolution and the consequences that follow if a resolution is purportedly passed in a manner that does not meet that requirement.
70 For reasons I have given, the requirement was not met in this case because at the time that the Resolution was purportedly passed Huntley did not have an AFSL that covered the operation of the Project as a registered scheme.