Entities are expected to implement the Machinery of Government (MoG) change in a way consistent with the MoG principles and operational protocols outlined in the Executive Overview.
Accountable authority instructions
Accountable authorities can issue accountable authority instructions (AAIs) and associated operational guidance to assist them to meet their obligations under the Public Governance, Performance and Accountability Act 2013 (PGPA Act). These instructions can form a key part of an entity’s internal controls and operational framework, focusing on the entity’s particular needs, in order to promote the efficient, effective, economical and ethical use of relevant money, relevant property and appropriations. Entities should review their AAIs to ensure appropriate arrangements are in place.
Finance has produced model AAIs as guidance for entities. The model AAIs cover core topics that are applicable to the majority of officials in most entities.
For further information, refer to RMG-206 Model accountable authority instructions.
Appropriations
Where a function is transferred between non-corporate Commonwealth entities (NCEs), the established protocol of ‘finances follow function’ applies to the transfer of annual appropriations and special appropriations (including special accounts).
Transfers of annual appropriations will be through a section 75 determination made under the PGPA Act.
Unspent annual appropriations for a function at the MoG change date of effect, are to be transferred to the receiving entity, subject to any decision by the Cabinet or Prime Minister. Where internal budget supplementation has been provided for a function, or internal budget reductions taken from a function as at the time of the MoG change, these are to be reflected in the transfers to the receiving entity.
Transferring entities are to provide receiving entities with supporting information on decisions made on internal budget supplementation or internal budget reductions, including who made the decisions, the date of the decisions and the date of their effect.
Section 75 of the PGPA Act only applies to transfers of functions between NCEs which are funded through annual appropriations (which can include receipts retained by the transferring entity under section 74 of the PGPA Act (retainable entity receipts)). Entities should contact the Annual Appropriations Team in Finance to discuss amounts to be included in the section 75 determinations and the timetable to enable the preparation of any determinations.
Transfer of appropriations may be made in tranches, as required, with the first determination typically made to commence on the MoG change date of effect:
- For administered annual appropriations, sufficient appropriations must be transferred to enable the receiving entity’s appropriation to be used for any administered payments from the MoG change date of effect until the next determination will be made (if any). Interim arrangements may be put in place for the transferring entity to continue to assist with administering functions (including making payments) under delegation or authorisation from the receiving entity, however the receiving entity’s appropriation must be used for all administered payments relating to the functions transferred. It is not appropriate for the transferring entity’s appropriations to be used for administered payments for functions that have transferred to the receiving entity.
- For departmental annual appropriations, an estimate of the amount required for departmental payments until the next determination will be made (if any) should also be transferred on the MoG change date of effect.
In relation to corporate Commonwealth entities (CCEs), as there are different situations that apply when transferring functions involving CCEs, entities should contact the Annual Appropriations Team in Finance in the first instance.
For transfers of functions which are funded through special appropriations or special accounts, please see the information below.
Affected entities must identify what appropriations are affected by a MoG change, the amount of appropriations to be transferred to the receiving entity to support the functions from the MoG change date of effect (commencement date), and how those appropriations can be accessed.
This may include:
- current year annual appropriations—Appropriation Act Nos 1/3/5 Departmental and Administered (operating and/or capital budget) and Appropriation Act Nos 2/4/6 (Payments to States, ACT, NT and local government, new administered outcomes, equity injections and/or administered assets and liabilities), including any retainable entity receipts (see section below) which may relate to the function being transferred, and any amounts withheld under section 51 of the PGPA Act and/or quarantined
- prior years’ unspent annual appropriations (across the categories noted above), including any amounts withheld and/or quarantined
- special appropriations, including special accounts, associated with the functions
- appropriations held by other Commonwealth entities who may administer amounts on behalf of the transferring entity and who may need to continue to do so for the receiving entity.
Transferring entities must ensure any amounts held in bank accounts relating to functions transferring (including by other Commonwealth entities on behalf of the transferring entity) are remitted back to the OPA for re-crediting against the relevant appropriation in the Cash Management (CM) module of the Central Budget Management System (CBMS) and subsequent transfer to the receiving entity under section 75 of the PGPA Act. These amounts cannot be directly transferred to the receiving entity’s bank account or retained by other Commonwealth entities.
Section 74 of the PGPA Act and section 27 of the Public Governance, Performance and Accountability Rule 2014 (PGPA Rule) apply to NCEs. These sections allow NCEs to retain certain kinds of receipts related to their departmental operations by crediting the amounts to the entity’s most recent departmental annual appropriation. These amounts are referred to as ‘retainable entity receipts’.
Where there is a MoG change, the receiving NCE is entitled to receive the amounts retained under section 74 of the PGPA Act and section 27 of the PGPA Rule relating to the function transferring. However, the following circumstances should be noted:
- if the transferring entity has retained prepayments for departmental goods or services that are now to be provided by the receiving entity, then the annual appropriation amounts to be transferred to the receiving entity must include such prepaid amounts
- cash that forms part of a bank account balance held by a transferring entity’s bank or another Commonwealth entity on behalf of the transferring entity is to be transferred back to the OPA for re-crediting against the relevant appropriation in the CM module of CBMS. To remit the amount back, the transferring entity should contact the OPA Administration and Banking Team in Finance for assistance. This must occur before the calculation of the appropriations to be transferred has been undertaken:
- for annual appropriations - that cash can be included in the amount transferred by the section 75 determination
- for special appropriations (including special accounts) - the available balance in the CM module must be accurate and up-to-date prior to being transferred to the receiving entity.
Retainable entity receipts received after the MoG change date of effect should be treated as revenue by the receiving entity in the period the cash is received, unless it is a repayment of an amount within the same financial year as the original payment. In this case, the relevant appropriation would be re-credited and the expense reduced.
Further information on the operation of section 74 of the PGPA Act and section 27 of the PGPA Rule is available in RMG-307 Retainable Receipts.
An NCE may have functions which are managed using a special account, such as those that involve the collection of fees or charges. Special accounts may either be established by a determination made by the Minister for Finance (under section 78 of the PGPA Act) or by provisions contained in an Act (under section 80 of the PGPA Act). Special accounts allow amounts collected from other parties to be retained and spent. All amounts held in special accounts are considered part of the Consolidated Revenue Fund (CRF) until spent.
The accountable authority for a special account is either specified in the special account determination, or in the Act containing the special account provisions.
When an AAO transfers ‘matters dealt with by the department’ and those matters utilise a special account, the relevant special account is usually transferred to the new department/entity on the date of effect of the AAO change. This applies to special accounts established either by a determination or by an Act.
The accountable authority of the receiving entity will be responsible for the special account, unless legislation allocates the special account to a specific official or an entity other than the receiving entity. Where the legislation allows, the portfolio Minister may choose to allocate management of a special account to a particular entity in his or her portfolio and in such instances the portfolio Minister should write to advise the Minister for Finance.
If the establishing determination or Act for a transferring special account requires amendment or needs to be repealed/revoked, the portfolio Minister should write to the Minister for Finance to request his or her agreement to the change.
The receiving entity will need to contact the CBMS Service Centre to set up relationships in CBMS before it is able to request cash from the OPA. Further information on the Reference Data Set (RDS) is available from CBMS Data Management.
For further information on special accounts, see RMG-100 Guide to Appropriations.
A special appropriation is a type of appropriation contained in an Act which allows money to be drawn from the CRF.
When an AAO transfers ‘matters dealt with by the department’ and those matters utilise a special appropriation, the relevant special appropriation is transferred on the date of effect of the AAO change.
The accountable authority of the receiving entity will be responsible for the special appropriation, unless legislation allocates the special appropriation to a specific official or an entity other than the receiving entity. A portfolio Minister may choose to formally delegate management of a special appropriation to any relevant entity in his or her portfolio and in such instances the portfolio Minister should write to advise the Minister for Finance.
The receiving entity will need to contact the CBMS Service Centre to set up relationships in CBMS before it is able to request cash from the OPA. Further information on the RDS is available from CBMS Data Management.
After the creation of a CBMS relationship for the receiving entity by Finance, the receiving entity will need to enter budget estimates against that item in the Annual Estimates (AEs) module and request the relevant Agency Advice Unit (AAU) to validate the estimates. The transferring entity must also enter adjustments to remove the estimates for that item from the date of the MoG change onwards.
Affected entities should also request the OPA Administration and Banking Team in Finance to adjust appropriation balances in the CM module of CBMS to reflect the MoG change. Finance will ensure that the CBMS adjustments entered net off across the transferring and receiving entities.
Where the transferring entity continues to draw amounts on behalf of the receiving entity, third party drawing access to these appropriations may be required. Affected entities should contact the OPA Administration and Banking Team in Finance to request a copy of the third-party agreement form.
After the transfer of cash and estimates data and once no data remains in the transferring entity’s old programs, Finance will deactivate these programs and appropriations.
For further information on special appropriations, see RMG-100 Guide to Appropriations.
Annual estimates
The established protocols of ‘employees follow function’, ‘finances follow function’ and ‘obligations follow function’ also apply to the transfer of annual estimates for the forward years.
Internal budget supplementation and reductions are reflected in the transfer of annual estimates for the forward years so that no unfunded positions or activities are transferred. Affected entities may wish to agree the transfer of annual estimates through an exchange of letters at the Chief Financial Officer (CFO) level, or higher if appropriate.
Once agreed, affected entities should enter adjustments in the AEs module of CBMS to reflect the transfer of annual estimates. A 'How to Guide on Program Restructures' is available in the CBMS Reference Material to assist entities with these adjustments. On request, Finance can assist entities with the transfer of annual estimates where whole CBMS programs are being moved from the transferring entity to the receiving entity. However, where only part of a CBMS program transfers to the receiving entity, these adjustments need to be entered by the entity.
Assets & liabilities
Entities are required to record the transfer of assets and liabilities at the value recognised in the books of the transferring entity as at the transfer date. Entities may wish to use the transferring entity’s last monthly financial statements as a starting point for the calculation of the net book values of assets and liabilities to be transferred.
Assets and liabilities transfer between entities when control passes from one entity to another, or when effective administrative responsibility transfers for administered items.
For further information on transfers of assets and liabilities including valuation, please see:
Audit committees & fraud and corruption control plans
The accountable authority of the receiving entity will need to ensure that its audit committee complies with the requirements of the resource management framework (section 45 of the PGPA Act and section 17 of the PGPA Rule). In particular, the accountable authority must ensure that the audit committee consists of persons who have appropriate qualifications, knowledge, skills or experience to assist the committee to perform its functions.
Note that the audit committee of an entity affected by a MoG change may need to ensure that their skills base relates to any new business and is no longer focussed on matters that have transferred to another entity.
For further information, see RMG-202 Audit Committees.
Accountable authorities are also responsible for ensuring their entities have appropriate fraud and corruption control arrangements, and for setting the ethical tone within their entity. Section 15 of the PGPA Act provides that an entity’s accountable authority must govern the entity in a way that promotes proper use and management of the public resources for which it is responsible, the achievement of the purposes, and the financial sustainability of the entity for which the accountable authority is responsible.
Section 10 of the PGPA Rule provides that an accountable authority must ‘take all reasonable measures to prevent, detect and respond to fraud and corruption relating to the entity’, including conducting assessments of fraud and corruption risks regularly and when there is a substantial change in the structure, functions or activities of the entity, and developing and implementing control plans to deal with fraud and corruption risks, and updating the plans as soon as practicable after conducting the assessments.
For more information see the Attorney-General's Department's Commonwealth Fraud and Corruption Control Framework.
Average Staffing Levels
The Average Staffing Levels (ASL) policy applies to functions within the Australian Government General Government Sector (GGS).
ASL is defined as the average number of employees (ongoing and non-ongoing) receiving wages or salaries over the financial year, with adjustments for casual and part-time employees, to show the full-time equivalent. It includes agency heads/accountable authorities, statutory office holders (except for appointees to judicial and related office positions), board/committee members, uniformed employees and overseas personnel, but excludes contractors and those employees on unpaid leave. Unfunded positions do not count towards ASL, see Annual estimates for more information.
MoG changes may increase or decrease the ASL estimate of entities based on the agreed transfer of ASL between entities and/or portfolios (‘employees follow function’). Where an entity takes on responsibility for a new function or employees from another entity, the ASL equivalent of any person transferred is added to the receiving entity’s ASL estimate, and removed from the transferring entity’s ASL estimate. Transfers within the Australian Government GGS must result in either a net nil impact or a reduction in ASL at a whole-of-government level.
Where positions associated with a function are funded but are currently unfilled, transferring entities should transfer both the ASL and funding associated with those positions.
For further information, including the methodology for calculating ASL, entities should refer to the most recent guidance issued on ASL (available via CBMS), or contact their Agency Advice Unit (AAU).
Entities may consider using the Standard Departmental Costing Template (SDCT) to calculate funding to be transferred with ASL, where the transferring entity does not have an appropriate internal cost allocation model in place and where this is agreed as an appropriate tool by both the transferring and receiving entities. A copy of the SDCT, along with the associated Departmental Costing Model Principles, can be downloaded from CBMS Estimates Memoranda.
Bank accounts
NCEs must operate bank accounts in accordance with the PGPA Act and policy guidance on managing cash. Entities should contact the OPA Administration and Banking Team in Finance for advice on banking arrangements following the announcement of a MoG change.
Entities must advise both the OPA Administration and Banking Team in Finance and the Reserve Bank of Australia when a new bank account is opened, or if an existing bank account is amended or closed. Notification to both parties is required regardless of the transactional bank used.
Entities affected by a MoG change should consider the impacts to their banking arrangements and contact the OPA Administration and Banking Team in Finance for advice that is specific to their banking arrangements. Some of those impacts may include:
- establishing new primary accounts (such as a bank account that can receive drawings from the OPA)
- returning bank account balances to the OPA
- a need to transfer bank accounts to the receiving entity
- changes to the bank account ‘type’ (such as departmental/administered).
For further guidance, refer to RMG-413 Banking and management of CRF money.
Central Budget Management System
Affected CBMS users in both the transferring and receiving entities may need to have their CBMS access reviewed and updated. Users will be required to submit a CBMS Access Form indicating on the form whether they need to Add Access or Remove Access. Further information can be found at CBMS Data Management.
Receiving entities may also need to request RDS changes to create relationships between new programs and existing appropriation items (for further information, see the sections on Special appropriations and Special accounts under Appropriations).
The Reference Data Set (RDS) provides the framework for data entry and reporting in CBMS. To ensure all relevant changes are made in CBMS, entities must notify the relevant AAU to coordinate changes with the CBMS Service Centre. The following changes are required to be reflected in CBMS:
- changes to existing portfolios
- changes to existing entities
- new portfolios
- new entities
- changes to appropriation items (see the sections on Special appropriations and Special accounts under Appropriations)
- changes to existing outcomes and programs, noting there are separate approval processes associated with (a) new or amended outcome statements, (b) new programs, and (c) merging or combining programs
- new outcomes and programs, noting that there are separate approval processes associated with (a) new or amended outcome statements and (b) new programs.
Entities should contact the CBMS Service Centre for advice on the requirements for RDS changes.
In some instances, when an entity transfers to a different portfolio, its existing programs will need to be duplicated against the receiving portfolio, with cash balances in the CM module and estimates in the AEs module moved from the old programs to the new programs. Finance may provide assistance to entities with these transfers, if required, and will consult with them on the timing of the transfers.
Where RDS changes in CBMS are required to reflect the MoG changes, entities should contact their AAUs for approval. This will allow entities to submit drawing requests against appropriations that they administer.
Entities should remove any future dated drawings in the CM module they no longer retain authority to spend. Entities should contact the OPA Administration and Banking Team in Finance if they require assistance with reflecting MoG changes in the CM module of CBMS.
To reduce delays in actioning requests, entities should keep the OPA Administration and Banking Team and CBMS Service Centre in Finance informed of changes to key contacts within their finance/treasury teams, including CFOs and CFO delegates.
Changes to third party relationship agreements in the CM module may be required following MoG changes.
Third party relationship agreement is an arrangement where an appropriated entity authorises another entity (the drawing entity) to access the appropriated entity’s appropriation in CBMS for drawing, receipts and journals.
The entity that administers the relevant appropriation (i.e. the appropriated entity) remains responsible for entering estimates and actuals data in CBMS, and for reporting in Portfolio Budget Statements (PBS), Portfolio Additional Estimates Statements (PAES) and annual reports (including the amounts of cash expended by the drawing entity).
To authorise access, the appropriated entity must complete a third party agreement form. This form and additional guidance on third party relationship agreements can be obtained from the OPA Administration and Banking Team in Finance.
Following the completion of any CBMS RDS changes and agreement between CFOs on appropriation amounts and forward estimates amounts to be transferred, Finance will advise entities when they will be able to process the necessary estimates and actuals adjustments in CBMS.
Changes to estimates in CBMS will usually be made in the next available estimates update following the MoG change. Finance can assist, where required, in moving the estimates between entities.
Changes to actuals reporting should be made during the monthly or annual actuals reporting period following the date of effect of the MoG changes.
Activities that are subject to charging (for example, fees or levies)
A transferring entity should provide relevant materials such as a costing model, charging model and any associated data in respect to the activity. The receiving entity should review these materials for applicability, for example, new indirect costs (such as receiving entity’s HR/IT/support services).
A receiving entity may need to consider implementing new procedures if it gains a charging activity. There may be value in the receiving entity obtaining relevant procedures from the transferring entity.
A transferring entity should transfer any revenue retained from charging arrangements, whether for direct or indirect costs of the activity being transferred.
- in the absence of a specific decision by the Government, there should not be any accumulated ‘surpluses’ resulting from a charging activity, irrespective of the classification of the activity within the Australian Government Charging Framework, whether the funding is classified as departmental or administered, or the mechanism under which revenues are retained (for example, section 74 of the PGPA Act, special account, etc.)
- where there is a specific Government decision allowing the retention of accumulated surpluses associated with the charging arrangements, for example capital costs, these accumulated surpluses should be transferred to the receiving entity.
For information regarding charging activities (including cost recovery activities) please refer to section 27(2) of the PGPA Act Rule, RMG-302 Implementing the Charging Framework, or contact the Charging Policy Team in Finance.
Competitive neutrality
All government business activities are required to apply competitive neutrality policy. Competitive neutrality aims to foster competitive markets by neutralising the potential of government entities to distort markets and by improving the efficiency of government entities. A transferring entity should provide relevant materials to the receiving entity in respect to the activity subject to competitive neutrality such as a costing model, charging model and any associated data.
For information regarding the management of competitive neutrality arrangements, please refer to the Australian Government Competitive Neutrality Policy Statement and the Australian Government Competitive Neutrality Guidelines for Managers.
Corporate plan requirements
Following a MoG change, the accountable authorities of both the transferring and the receiving entity will need to consider if a variation to the entities' corporate plans is required.
For further information see:
- sections 16E and 16F of the PGPA Rule
- RMG-132 Corporate plans for Commonwealth entities, or
- contact PGPA & Digital Reporting Branch in Finance for advice on corporate plan requirements.
Data sharing
Entities affected by a MoG change who are accredited or sharing data under the Data Availability and Transparency Act 2022 (the DAT Act) need to report changes to their organisational structure to the Office of the National Data Commissioner (ONDC) in Finance.
For further information:
- see Guidance note 2024:1 Reporting requirements under the DATA Scheme on the ONDC website, or
- contact the ONDC in Finance for further advice on how the MoG change affects any accreditations obtained, or data sharing agreements entered into, under the DAT Act.
Delegation of powers
The accountable authority of an NCE with new functions may need to delegate his or her powers under the PGPA Act and PGPA Rule to other appropriate officials (such as the CFO) so that they can undertake financial activities on behalf of the entity.
PGPA legislation, associated instruments and policies provide additional information on delegations of powers.
One such scenario where delegations may be appropriate is where there are travelling employees and credit cards:
- where a MoG change has an immediate effect, consideration must be given to communication with employees who are away from their normal workplace, such as those travelling interstate or overseas
- the receiving entity should consider the application of any whole-of-government delegations and relevant internal sub-delegations for transferring employees
- employees who are travelling will typically be using a whole-of-government travel card, which will continue to operate
- transferring entities should seek to make contact with any employees who are travelling to alert them of the MoG change and to advise them of possible impacts on them, including in relation to delegations they may exercise while travelling.
Employee leave entitlements
For advice on accounting for MoG changes, including a method to calculate funding to be transferred for employee entitlements, please refer to RMG-118 Accounting for machinery of government changes.
The effective date for calculating the funding for employee entitlements to be transferred is the date on which the employee transfers became effective under the Public Service Act 1999 (PS Act) or other relevant legislation.
It is imperative that entities finalise the list of transferring employees well before the completion date for the MoG change, as this can delay the calculation of funding and the value of assets and liabilities to be transferred.
For advice on how to calculate the value of employee entitlement liabilities to be transferred, please refer to sections 24 to 26 of the FRR and the Employee benefits section of RMG-125 Commonwealth Entities Financial Statements Guide.
Financial reporting arrangements
Accountable authorities of entities are required under section 42 of the PGPA Act, to provide annual financial statements to the Auditor-General.
Chapter 2, Part 2-3, Division 4 of the PGPA Rule provides the reporting arrangements that apply under various MoG scenarios. Sections 17A-17J set out the special reporting requirements that apply where an entity has ceased to exist or functions have been transferred as a result of a MoG change. These reporting arrangements are designed to ensure that:
- all accountability obligations are met following MoG changes
- there is no duplication of reporting of operations impacted by these changes, including reporting relating to key management personnel (KMP).
The reporting requirements at:
- Subdivision A, sections 17A-17D of the PGPA Rule apply where an entity has ceased to exist
- Subdivision B, sections 17E-17G of the PGPA Rule apply where an entity has not ceased to exist but some or all functions have been transferred
- Subdivision C, sections 17H-17J of the PGPA Rule apply to reporting on transferred functions
- Subdivision D, section 17K of the PGPA Rule applies for miscellaneous reporting.
Financial reporting requirements for implementing and reflecting MoG changes are set out in:
- paragraphs 54-59 of the Australian Accounting Standards Board (AASB) 1004 Contributions
- paragraphs 216-218 of AASB 1060 General Purpose Financial Statements – Simplified Disclosures for For-Profit and Not-for-Profit Tier 2 Entities (Appendix C)
- section 26 of the FRR.
Agreements between entities on the transfer of revenues, expenses, assets and liabilities should be documented in a Memorandum of Understanding (MoU). Documentation of agreements is important for clarifying accountability, preventing misinterpretations and as supporting evidence. An MoU may also deal with the transfer of other rights and responsibilities which are not recorded as assets and liabilities (for example, obligations under legal agreements or responsibility for intellectual property).
Where possible, when entities advise the Government on the MoG change date of effect (commencement date), it is recommended entities consider the start of a month or financial year.
Additional information on financial reporting in respect of restructures is available in the following:
- section 26 of the FRR relating to ‘Restructures of administrative arrangements’
- RMG-118 Accounting for Machinery of Government Changes
- RMG-119 Reporting requirements following Machinery of Government Changes.
Please contact Finance for more information.
Grants
Affected entities should have regard to the mandatory requirements and key principles of the Commonwealth Grants Rules and Principles 2024 when considering the implications of MoG changes for grant programs. In particular, entities should have regard to the key principles of partnership and collaboration, consistency with grant guidelines and established processes, governance and accountability, and probity and transparency.
Appropriations for grant programs transfer with responsibilities, including, if applicable, funding associated with administering grant programs via one of the grant hubs (see below).
The transferring entity should agree with the receiving entity the date of the transfer of grants and associated information. The receiving entity should consider whether existing grant agreements require updating, noting that where there is a change in an entity’s name, contracts will typically continue without any immediate action as section 19C of the Acts Interpretation Act 1901 allows references to departments and APS entities to be read as the new name(s).
Updates to published grant information may be required. Affected entities should contact the GrantConnect Team in Finance to discuss. Changes to open, published grant opportunity guidelines to reflect MoG changes do not generally require review by Finance. Please contact the Grant Guidelines Team in Finance to discuss.
Receiving entities should consider whether existing delegations, policies and processes are appropriate and consistent with published grant opportunity guidelines. They should also consider whether measures are required to manage potential conflicts of interest arising from the transfer of responsibility, noting the requirements for officials, ministers and ministerial staff to declare and manage actual and potential conflicts of interest associated with grants administration activities.
Where transferring grant programs are delivered through a grants hub, the programs must continue to be delivered by a hub on behalf of the receiving entity. Please contact the Grants Administration team in Finance for further information if required.
Holding a function for less than a year
The ‘finances follow function’ protocol provides that annual appropriations devoted to a function at the point of the MoG change be transferred to the receiving entity.
If an entity holds a function for less than a year that is transferred to another entity before the end of the financial year, there should be a clear relationship between the funding that was received by the entity for the function and the funding that is transferred to the receiving entity.
However, entities can structure themselves differently and an entity may quickly integrate the function into the organisation. This could influence the funding transferred and this should be a consideration in negotiating funding.
Insurance
Both the transferring and receiving entities should contact Comcover to discuss the details of the MoG change, to ensure appropriate insurance coverage is maintained. Comcover will actively support each entity throughout the MoG change, however it remains the obligation of each entity to ensure their Comcover records (including asset and expatriate schedules) are kept up-to-date throughout the MoG change, have their risk profiles reassessed and arrange adjustment of their insurance premiums and coverage.
Any current claim(s) or litigation(s) that will be transferred to the receiving entity must be considered in implementing the MoG change.
Outcome statements & program structures
Receiving entities may need to create new or amend existing outcome statements where the transferring function does not fit within its current outcome statements. In a MoG context, entire outcome statements may be copied from the transferring entity to the receiving entity through section 75 determinations.
Any new outcome statements for the receiving entity or amendments to the receiving entity’s existing outcome statements must be approved by the Minister for Finance, and will need to be supported by legal advice.
If you are considering a new outcome statement, please contact the Annual Appropriations Team in Finance.
When assessing the requirement for outcome statement changes, entities should also consider whether changes are necessary to the list of programs in CBMS, resulting from changes either to program structures or because of movement of programs between outcomes and/or entities. See Changes to Reference Data Set under Central Budget Management System above.
Portfolio Budget Statements
Entities who receive an annual appropriation impacted by MoG changes should ensure they report their new structure and current information in their Portfolio Budget Statements (PBS) or Portfolio Additional Estimates Statements (PAES). Depending on when section 75 transfers are agreed, the change should be reflected in either the next PBS or PAES publication, whichever is the earlier.
Where section 75 determinations have not been made in time to be reported in the next PBS or PAES, entities should add a note clarifying that further details of their MoG change will be reported in the next published PBS or PAES, whichever is the earlier.
Entities need to ensure they reflect the correct structures and splits in their:
- entity resource statement
- outcome, program and performance information
- budgeted financial statements.
For further information, entities should refer to the relevant guidance on the PBS and/or PAES issued prior to each Budget update. This guidance includes a preparation guide that contains a section on reflecting MoG changes.
Procurement
There may be implications for an entity's procurement agreements, including contracts, deeds, MoUs or other form of agreements.
In the first instance, contact your entity's central procurement unit for assistance regarding receiving or transferring procurements.
Further information regarding procurements, including whole-of-government arrangements, is available from Procurement.
Any queries relating to AusTender transition for approaches to market and/or reporting standing offers and contracts, including transfers of responsibility to the receiving entity, should be directed to the AusTender Help Desk. For information on reporting requirements following a MoG change, see RMG-119 Reporting requirements following machinery of government changes.
Any queries relating to ICT procurement should be directed to the Digital Transformation Agency's (DTA's) ICT Procurement team.
A new or a receiving entity should consider the application of any whole-of-government delegations and relevant internal sub-delegations for the transferring employees.
Where there is a change in an entity’s name, contracts will typically continue without any immediate action as section 19C of the Acts Interpretation Act 1901 allows references to departments and APS entities to be read as the new name(s).
Finance’s Procurement Policy Team can also provide advice to entities undertaking procurement processes that are affected by a MoG change.
Entities should approach the APSC to discuss implications for reporting on core work and targets under the Strategic Commissioning Framework.
Property
Property and Construction Division (PCD) in Finance is responsible for property policy, including management of the Commonwealth Property Management Framework, which includes property related policies, supporting processes and guidance.
Compliance with the Commonwealth Property Management Framework is mandatory for NCEs and supports best practice by other entities. It establishes the broad government policy framework within which NCEs manage their property portfolio and seeks to enhance good property management practice across entities, providing increased efficiency and effectiveness of property use in the course of government business. It provides guidance to entities on their responsibilities across a broad range of property matters including planning, funding, leasing, ownership, management, disposal and reporting.
The whole-of-Australian-Government Property Services Coordinated Procurement (PSCP) Arrangements have been established to support the Commonwealth Property Management Framework and include Property Service Providers (PSPs) assigned to entities and a Strategic Property Adviser (SPA) for the Commonwealth that provide property related leasing and facilities management services, including strategic leasing advice to assist with future lease planning.
Finance maintains the Australian Government Property Register (AGPR) which records the Commonwealth’s leased office accommodation and owned property. This information is used for, but not limited to, the annually published Office Occupancy Report, the Commonwealth Leasing Strategy (CLS), and to support Treasury in the calculation of Mirror Tax. NCEs are required to participate in these property data collections. The AGPR contains:
- Property Marketplace which enables entities to advertise excess Commonwealth leased or owned office space
- reporting capabilities for entities to analyse their reported data
- Property Management Plan repository.
PCD in Finance can assist entities requiring advice on implications of MoG changes on property.
The general operational protocol that ‘employees, finances and obligations follow functions’ in MoG changes also applies to property. This means that the starting position should be that the property that is occupied by employees in the transferring entity is transferred to the receiving entity, with employees not expected to physically relocate in the short term. This outcome can be supported through the use of mechanisms such as lease assignment, subleasing or MoUs. As with other MoG matters, it is expected that affected entities will cooperatively negotiate and resolve property matters, and there may be readily available options that more fully meet the needs of all affected entities.
Adopting this whole-of-government approach supports cost effective outcomes by avoiding the need for entities to add space to the Commonwealth's leased property estate in an attempt to co-locate employees following MoG changes. Arrangements such as flexible and hybrid work can help to drive more efficient property management practices and utilisation whilst maintaining continuity of service.
As per the requirements outlined earlier in this Guide, transferring entities have obligations to share information and establish plans in relation to property within specified timeframes.
Affected entities should consider the following as part of their immediate and short-term actions, and when a MoG change occurs entities should engage with their PSP as early as possible, where applicable, on matters such as:
- timing, including key milestones and deadlines
- number of staff to be transitioned
- location of staff to be transitioned and any security implications
- anticipated accommodation requirements or changes
- financial impacts
- key points of contact
- PSP participation in project governance and/or management meetings
- anticipated change in service requirements
- data and information required to support entity decision making and planning.
When a MoG change occurs that has impacts across PSPs, entities should work with Finance and their PSP to agree a transition-out and transition-in plan to ensure the continuity of services and contracts for all entities.
Affected entities should provide their PSP with regular updates on key decisions and notice of any planning changes.
Affected entities are responsible for ensuring that the service requirements are agreed internally and communicated to PSPs appropriately, including leasing and accommodation requirements.
Concurrent to engaging with PSPs, affected entities should engage with PCD in Finance for advice on:
- property utilisation and planning, which includes accessing the SPA for strategic property advice, and advice on how options such as subleasing, MoUs, flexible working and other approaches can be used by entities to maintain an efficient property footprint
- the PSP scope of services related to MoG changes
- whether MoG changes impact the PSCP Arrangements, particularly if the function or entity moves from non-APS to APS or vice versa.
Newly formed entities should contact PCD to determine if there is existing suitable Commonwealth property available to facilitate the entity’s establishment. PCD can also assist these entities to understand their legislative and policy responsibilities in relation to the acquisition of property, including through leasing, and the requirement to transition to the PSCP Arrangements.
Entities that cease to exist because of a MoG change should contact PCD to work through any implications on existing property-related contracts.
All entities must update their Property Management Plan (PMP) as necessary to address changing business requirements, including to reflect changed property holdings and their future property strategy following MoG changes. Entities submit their PMP to Finance on an annual basis to inform whole-of-government planning. PSPs can develop these plans as an additional service under the PSCP Arrangements.
When entities are considering future property needs following MoG changes, entities should consider the requirements under the Commonwealth Property Management Framework, including that where consistent with an NCE’s business needs and the CLS, NCEs must occupy existing Commonwealth leased or owned office space as a priority over sourcing new accommodation in the market.
Additionally, entities should consider the necessity and/or scale of physical relocations of employees in line with value for money considerations.
The SPA considers entities’ long-term property requirements in the annual development of the CLS. This strategic planning includes changes to property footprint requirements (including following a MoG change), such as consolidating space or relinquishing leases. The SPA can consider specific revisions to the CLS on an as-needed basis, including those related to a MoG change. Early engagement with other entities affected by the MoG changes is important for understanding property requirements, while engagement with the SPA and PCD can also help entities understand the impact of the MoG changes on property strategies.
Where an entity has excess Commonwealth leased or owned office space resulting from MoG changes, they can use the Property Marketplace (within the AGPR) to advertise this space.
The general expectation is that entities should bear their own relocation costs.
It is reasonable to expect that a transferring entity would pay for:
- physical movement of employees, furniture, equipment and files
- downloading of information and other ICT activities relating to the move, including Freedom of Information (FOI) and Information Publication Scheme obligations (such as the proactive publication of public sector information)
- updating internal records.
Receiving entities would be expected to pay for the costs of establishing the transferred employees in their new premises, including reloading information, setting up access to the network, security arrangements, and updating internal records.
The receiving entity should also comply with any Public Works Committeee's notification or referral requirements applying to the relocation project (in accordance with the thresholds) prior to commencing any fit out works.
Security clearances
Security clearances are governed by the Protective Security Policy Framework administered by the Department of Home Affairs.
Transferring entities must provide receiving entities with information on, and arrange for the transfer of, current security clearances held by affected employees.
Where the receiving entity requires a higher clearance for transferring employees as a condition of employment, the receiving entity is responsible for discussing and arranging the upgrade with the employees.
For more information on transferring security clearances, please see the Australian Government Security Vetting Agency.
Superannuation
Where MoG changes occur, entities will need to contact the Electoral and Superannuation Policy Branch in Finance about the implications for membership of the civilian defined benefit schemes (CSS and PSS) and the defined contribution scheme PSSap.
Taxation
MoG changes will have implications for entities’ Pay as You Go (PAYG) withholding, Fringe Benefits Tax (FBT), Goods and Services Tax (GST) and Business Activity Statement (BAS) returns, as well as funding agreements and contracts. Entities may also need to consider updates to Single Touch Payroll (STP) reporting – either setting up STP reporting for the new entity and/or transitioning employees between entities.
Entities may also need to update business and legal names in addition to updating authorised contacts for Australian Business Numbers (ABNs).
Entities should contact the Australian Securities and Investments Commission and the Australian Taxation Office (ATO) for advice on how to update these details.
Government entities are unable to apply for a new ABN online. Entities must complete and return form ‘NAT 2946’ available from the ATO’s publication ordering service. For more information, visit the Australian Business Register's Apply for a government ABN.
Government entities are able to apply for an ABN in advance of the entity’s start date. However, the ABN will not be shown in the public ABN Lookup portal prior to this time.
For further information, please refer to the following: