Appropriation Act (No. 6) 2025-2026

The Act is organised around a small set of recurring concepts that determine how money authorised by Parliament is to be treated, allocated and interpreted. Understanding these core concepts is essential for applying the Act.

Definitions and item taxonomy (s 3)

• The Act defines five item categories that appear in Schedule 1: State, ACT, NT and local government item; administered item; administered assets and liabilities item; other departmental item; and corporate entity item. Each label ties an amount in Schedule 1 to a purpose‑type and to the class of entity that will apply or receive the money.
• “Administered item” is an amount set out in Schedule 1 opposite an outcome for a non‑corporate entity under the heading “New Administered Outcomes”. “Administered assets and liabilities item” is an amount set out under “Administered Assets and Liabilities” opposite a non‑corporate entity. “Other departmental item” is an amount under “Equity Injections”. “Corporate entity item” is the amount in Schedule 1 in relation to a corporate entity under the heading “Non‑operating”. These textual labels operate as classifications for spending authority.
• The Act distinguishes “corporate entity” and “non‑corporate entity” by reference to the Public Governance, Performance and Accountability Act 2013: corporate entities include corporate Commonwealth entities and Commonwealth companies; non‑corporate entities include non‑corporate Commonwealth entities and the High Court (s 3). The Act therefore assumes the PGPA Act’s entity taxonomy but does not reproduce all details of that Act.

Portfolio statements as interpretive documents (s 3, s 4)

• “Portfolio statements” is defined to include the Portfolio Budget Statements, the Portfolio Additional Estimates Statements and the Portfolio Supplementary Additional Estimates Statements as specified in s 3. Section 4 declares the portfolio statements to be relevant documents for the purposes of section 15AB of the Acts Interpretation Act 1901. The legal effect is that, for statutory interpretation of the Act, the contents of those portfolio statements may be considered as extrinsic material under the Acts Interpretation Act.

Notional transactions (s 5)

• The Act directs that notional transactions between non‑corporate entities that are part of the Commonwealth are to be treated as if they were real transactions. The text gives the example of a “payment” between non‑corporate Commonwealth entities being debited from an appropriation despite no actual payment from the Consolidated Revenue Fund. The Act expressly ties this to section 76 of the PGPA Act by a note, thereby aligning domestic appropriation accounting with the PGPA’s approach to intra‑Commonwealth accounting.

Debit limits and national partnership payments (s 12)

• The Act sets a specific debit limit for the current year for purposes of s 16 of the Federal Financial Relations Act 2009: $40,000,000,000. It also states this debit limit applies despite, and after commencement operates instead of, subsection 13(2) of the Supply Act (No. 2) 2025‑2026. The Act therefore modifies how debit limits operate for national partnership payments within the current year by establishing a fixed numeric cap.

Cross‑Act references and schedule reliance (s 6, s 9)

• The Act repeatedly ties authority to Schedule 1 and references the content of Schedule 1 in other appropriation and supply Acts (for example s 9 lists multiple past and concurrent appropriation and supply Acts whose Schedules may define outcomes that administered assets and liabilities items can be applied to). The omission of Schedule 1 text from this Act’s body means the specific allocations, outcomes and object codes are external to the Act text and must be read in the Schedule to see the precise amounts and outcome descriptions.

Special accounts and the Consolidated Revenue Fund (s 13, s 14)

• The Act authorises amounts to be debited against an appropriation and credited to a special account if the special account’s purposes overlap with an appropriation item (s 13). The Act also expressly appropriates the Consolidated Revenue Fund as necessary for its operation and for the operation of the PGPA nexus (s 14).

Temporal scope (s 2, s 15)

• The Act commences on Royal Assent (s 2) and is expressly repealed at the start of 1 July 2028 (s 15). The Act also defines the “current year” as the financial year ending 30 June 2026 (s 3), which frames certain numeric limits in the context of that financial year.

Interpretive notes and legislative hierarchy

• The Act contains notes that make explicit links to other statutes. For example, the note in s 5 points to section 76 of the PGPA Act, and the note in s 6 references sections 74 to 75 of the PGPA Act for adjustment of appropriations. These notes are part of the Act document and signal intended interplay, but they are not themselves operative text that adds duties beyond what the sections state.

Overall, the main concepts are appropriation item labels, the use of portfolio statements as interpretive material, the treatment of intra‑Commonwealth notional transactions for appropriation accounting, a specified debit limit for national partnership payments, and mechanisms permitting crediting to special accounts. The Act functions primarily as a set of mechanical authorisations and interpretive hooks that operate against the background framework established by the PGPA Act, the Federal Financial Relations Act 2009 and other appropriation and supply Acts.

The Act’s text identifies, directly or by reference, several categories of public actors and financial instruments that will be affected by its provisions. The practical consequences differ by role: payee entities, payer entities or accounting authorities may see direct operational effects; other interested parties are affected indirectly through interpretive and administrative consequences.

Primary affected entities

• Non‑corporate Commonwealth entities: Defined in s 3 by reference to the PGPA Act, non‑corporate entities are the primary focus of administered items, administered assets and liabilities items, State/ACT/NT/local government items and other departmental items. The Act authorises amounts in Schedule 1 that are expressed opposite outcomes for non‑corporate entities (ss 7-10).
• Corporate Commonwealth entities and Commonwealth companies: These are included in the Act’s definition of “corporate entity” (s 3(a) and (b)). Corporate entity items in Schedule 1 labelled “Non‑operating” are payable to corporate entities; s 11(1) provides that such amounts may be paid to the entity to be applied for its purposes. Section 11(2) further states that where another Act provides that a corporate entity must be paid amounts appropriated by Parliament, and Schedule 1 contains a corporate entity item for that entity, the entity must be paid the full amount specified in the item. This creates a financial flow to corporate entities where other statutory obligations coincide with Schedule 1 entries.
• The High Court: Listed as a non‑corporate entity in the definition (s 3), the High Court may show as the recipient for certain administered or departmental items if Schedule 1 includes outcomes opposite it.
• State and Territory governments and local government authorities: The State, ACT, NT and local government items are expressly applied to making payments to or for these governments to contribute to achieving outcomes (s 7). The Act therefore affects intergovernmental financial flows, including national partnership payments, which the Act addresses via a debit limit (s 12).
• The Consolidated Revenue Fund and special accounts: The Act explicitly appropriates the Consolidated Revenue Fund for the operation of the Act (s 14) and allows amounts to be debited against an appropriation and credited to special accounts when special account purposes overlap with an appropriation item (s 13). Financial managers and overseers of special accounts will therefore need to interpret and apply the cross‑account crediting mechanism.

Secondary affected actors and structures

• Portfolio statement authors and users: The Act declares portfolio statements to be relevant documents for statutory interpretation (s 4). Agencies that prepare those statements, parliamentary officers and departments that rely on the statements for planning, and legal advisers interpreting the Act will be affected, as the statements may be referenced when determining what activities correspond to outcomes in Schedule 1.
• Treasury and Finance branches responsible for debit limits and national partnership payments: Section 12 sets the debit limit for the current year and modifies the effect of a subsection in Supply Act (No. 2) 2025‑2026. Those responsible for cash management and administering intergovernmental payments will be required to respect the numeric cap and the change in statutory operation.
• Accountants and auditors: Because the Act directs that notional transactions between non‑corporate entities are to be treated as real for appropriation purposes (s 5), internal accounting systems need to record debits and credits consistent with that direction. Auditors assessing compliance with appropriation law and the PGPA framework must take the Act’s notional transaction provision into account.
• Parliamentary and administrative interpreters: Declaring extrinsic documents relevant under the Acts Interpretation Act 1901 (s 4) affects how Parliament’s appropriation instrument will be read and how administrative agencies can justify certain expenditure as contributing to an outcome.

Who gains and who bears costs

• Beneficiaries of payments: Entities and governments named in Schedule 1 will practically receive appropriation authority for specified purposes. Corporate entities with items in Schedule 1 and an enabling Act may have a secured flow of funds as contemplated by s 11(2).
• Payers and financial managers: Commonwealth accounting officers will bear the administrative cost of applying the Act’s rules: implementing notional transaction accounting, applying crediting to special accounts, ensuring that items are applied only for the specified outcomes and observing the debit limit for national partnerships.
• Budgetary tradeoffs: The total appropriation figure given in s 6, $1,127,824,000, identifies the fiscal envelope in the Schedule. The Act’s note that sections 74 to 75 of the PGPA Act permit adjustment of appropriated amounts indicates that agencies may face subsequent administrative changes to structuring and accounting for these funds.

In short, the Act directly affects the agencies listed in Schedule 1, corporate and non‑corporate Commonwealth entities, State and Territory governments and local authorities receiving payments, and the Commonwealth’s budgetary machinery including Treasury, Finance, accounting officers and auditors. The Act’s interpretive hooks and accounting directives mean that the scope of that effect goes beyond immediate payees to the systems that record, interpret and report Commonwealth expenditure.

This Act sets out a number of operative duties and positive allocations of authority rather than creating a scheme of regulatory duties and sanctions. The duties and rights are principally administrative and financial. Below are the Act’s principal operative obligations and legally significant authorisations, grounded in the text.

Payment and application duties

• Application of item amounts to outcomes: For each item type the Act specifies how the amounts in Schedule 1 may be applied. For example, s 7(1) states that the amount specified in a State, ACT, NT and local government item "may be applied for the purpose of making payments to or for the States, the Australian Capital Territory, the Northern Territory and local government authorities for the purpose of contributing to achieving that outcome." Similarly, s 8(1) states that amounts in an administered item "may be applied for expenditure for the purpose of contributing to achieving that outcome." The language used in those provisions is permissive rather than prescriptive but sets the authorised purpose and permitted use of the appropriation.
• Departmental expenditure: Section 10 provides that an other departmental item may be applied for the departmental expenditure of the non‑corporate entity. That gives an agency the authorised budget head to incur departmental expenditure consistent with the item in Schedule 1.
• Corporate entity payments and mandatory payment condition: Section 11(1) authorises that the amount specified in a corporate entity item "may be paid to the entity to be applied for the purposes of the entity." More consequentially, s 11(2) establishes a more prescriptive duty: where an Act provides that a corporate entity must be paid amounts appropriated by Parliament for the purposes of the entity, and Schedule 1 contains a corporate entity item for that entity, "then the entity must be paid the full amount specified in the item." That text creates a direct statutory obligation to effect the payment in the specified circumstances.
• Administered assets and liabilities item flexibility: Section 9(1) allows an administered assets and liabilities item to be applied for contributing to any outcome specified for the entity in a list of Schedules across multiple appropriation and supply Acts. That gives flexibility to apply such items across a set of outcomes that may be spread across multiple appropriation instruments.

Accounting and interpretive duties

• Notional transactions: Section 5 requires that notional transactions between non‑corporate entities be treated as if they were real transactions for the purposes of this Act. Practically, that is a duty on agencies and accounting officers to record those transactions as debits against appropriations, even where no cash transfer occurs from the Consolidated Revenue Fund. The Act notes this aligns with PGPA Act s 76.
• Portfolio statements as interpretive material: Section 4 declares the portfolio statements to be relevant documents under s 15AB of the Acts Interpretation Act 1901. This is not a duty in itself, but it authorises courts or decision‑makers to consider those statements when interpreting the Act. Agencies will therefore be expected to prepare and rely on portfolio statements consistent with the outcomes identified in Schedule 1, and to ensure that activities indicated in portfolio statements are correspondingly treated as activities in respect of particular outcomes for appropriation application (ss 7(2), 8(2), 9(2)).

Financial management duties

• Debit limit observance: Section 12 sets a specific numeric debit limit of $40,000,000,000 for the current year for the purposes of s 16 of the Federal Financial Relations Act 2009. It also states that this limit applies despite subsection 13(2) of the Supply Act (No. 2) 2025‑2026 and will have effect instead of that subsection after commencement. This places a duty on the agency or Treasury functions responsible for national partnership payments to ensure the aggregate debit does not exceed the specified limit.
• Crediting to special accounts: Section 13 permits amounts to be debited against an appropriation and credited to a special account if any of the purposes of that special account are covered by an item. Agencies with control of special accounts must administer that mechanism in line with the Act’s wording and their own special account rules under the PGPA framework.

Rights and entitlements

• Payment rights for corporate entities in particular circumstances: As noted, s 11(2) obliges payment in the circumstances it identifies. The Act therefore creates a conduit for a corporate entity to receive the full amount specified in a corporate entity item where another Act requires parliamentary appropriations to be paid to that entity.
• Use of appropriations for declared purposes: The item structures in ss 7-11 functionally grant agencies and recipient entities the right to apply the specified amounts for the stated outcome or purpose provided in Schedule 1.

Limitations and temporal obligations

• Temporal limit: The Act is repealed at the start of 1 July 2028 (s 15). This creates a temporal boundary for operation. Any continuing obligations or payment schedules that are dependent on this Act’s appropriations need to be reconciled with this repeal date.
• Adjustments under PGPA: The Act itself notes that sections 74 to 75 of the PGPA Act provide for adjustment of amounts appropriated by this Act (s 6 note). That suggests a further statutory framework that may increase or decrease the effective amounts available, and agencies must observe those PGPA adjustment processes.

Overall, the Act creates administrative duties about how to record and apply appropriations, requires payments under defined conditions, creates interpretive rights for extrinsic documents, and imposes numeric and temporal constraints that agencies and other financial managers must follow. The language of the Act is largely permissive in authorising application of funds, but it creates a mandatory payment duty in the specific corporate entity scenario described in s 11(2).

The Appropriation Act (No. 6) 2025‑2026 is, by its text, primarily a financial authorisation and interpretive instrument. It does not create a standalone enforcement regime or specify criminal or civil penalties within its operative sections. The Act’s enforcement and compliance consequences therefore operate through the Commonwealth’s existing financial management, auditing and statutory frameworks rather than through new sanctions in this Act itself.

Absence of express penal provisions

• The Act contains no sections that establish criminal offences, pecuniary penalties, infringement notices or administrative fines. There are no express penalty provisions tied to breach of the application rules or interpretive declarations set out in ss 4-13.

Mechanisms through which compliance is monitored and enforced

• PGPA Act mechanisms: The Act references the Public Governance, Performance and Accountability Act 2013. The notes to s 5 and s 6 specifically align the Act with the PGPA Act: s 5’s note links the notional transaction treatment to section 76 of the PGPA Act, and s 6’s note identifies sections 74 to 75 of the PGPA Act as providing for adjustment of appropriated amounts. Those references indicate that enforcement and compliance in relation to appropriation adjustments, accounting treatment, and reporting will occur within the PGPA Act framework. The PGPA Act contains duties for accountable authorities and officials, and mechanisms such as financial statements, internal control obligations and audit functions that are the typical means to enforce appropriation law compliance.
• Accounting and administrative controls: Section 5’s direction that notional transactions be treated as real has practical enforcement through accounting practice. Accounting officers must ensure appropriation debits are recorded correctly, and auditors will test for compliance. Failures are likely to be addressed through administrative remedies, audit findings, and management responses rather than new sanctions in this Act.
• Parliamentary oversight: Appropriation Acts are accountable to Parliament. Parliamentary scrutiny, estimates processes, and reporting in Portfolio Budget Statements and supplemental statements (which the Act declares relevant documents in s 4) operate as political and administrative enforcement levers. The Act’s declaration of portfolio statements as relevant for interpretation may increase the evidentiary weight of those documents when Parliament or its committees consider an agency’s use of funds.
• Debit limit enforcement: Section 12 fixes a numeric debit limit for national partnership payments for the current year and sets it in substitution for a subsection in the Supply Act (No. 2) 2025‑2026. Compliance with that limit will be a matter for Treasury and agencies responsible for national partnership payments. Exceeding the cap would trigger administrative constraints, draw scrutiny and potentially require corrective action through the mechanisms available in the Federal Financial Relations Act 2009 or appropriations law, but the Act itself does not prescribe a specific penalty.

Practical investigating and remedial mechanisms

• Auditor‑General and audit reports: While not mentioned explicitly in this Act, the PGPA Act and the Commonwealth’s audit regime are the standard channels through which misapplication of appropriations is exposed. The Act’s references to the PGPA Act make clear that financial reporting and external audit will be the principal enforcement mechanisms.
• Reconciliation and adjustment under PGPA: The note to s 6 that sections 74 to 75 of the PGPA Act provide for adjustment of appropriated amounts signals that misstatements or changes in appropriation usage may be addressed through the PGPA adjustment procedures.

In short, enforcement is procedural and administrative. The Act provides authorising language and interpretive rules; compliance is enforced through the existing framework for Commonwealth financial management, auditing and parliamentary oversight. There are no newly created penalty provisions or private rights of action contained in the Act’s text.

The Act is compact yet explicitly designed to operate within a statutory web. It cross‑references several existing Acts and other appropriation instruments. The interaction mechanics are a salient feature of this Act.

Primary statutory cross‑references within the Act

• Public Governance, Performance and Accountability Act 2013 (PGPA Act): The Act uses the PGPA Act as the definitional backbone for corporate and non‑corporate entities (s 3), aligns the treatment of notional transactions with PGPA Act section 76 (s 5 note), and flags sections 74 to 75 of the PGPA Act as the mechanisms for adjustment of appropriated amounts (s 6 note). It also uses the PGPA Act’s definition of a special account (s 3). These references mean the PGPA Act’s financial management, reporting and adjustment mechanisms are the operational context for this appropriation act.
• Acts Interpretation Act 1901: Section 4 declares the portfolio statements to be relevant documents for the purposes of section 15AB of the Acts Interpretation Act 1901. The effect is interpretive: under s 15AB(2)(g) of the Acts Interpretation Act, documents declared relevant may be considered as extrinsic material in interpreting the Act’s provisions.
• Federal Financial Relations Act 2009: Section 12 ties the debit limit set by this Act to section 16 of the Federal Financial Relations Act 2009. The debit limit is thus not merely a numerical note; it is the operative cap for the purposes of that Federal Financial Relations Act provision.
• Supply and Appropriation Acts: Section 9(1) makes administered assets and liabilities items available for outcomes specified in the Schedules of a list of other appropriation and supply Acts: Supply Act (No. 1) 2025‑2026; Appropriation Act (No. 1) 2025‑2026; Supply Act (No. 2) 2025‑2026; Appropriation Act (No. 2) 2025‑2026; Appropriation Act (No. 3) 2025‑2026; Appropriation Act (No. 4) 2025‑2026; Appropriation Act (No. 5) 2025‑2026. Section 12 further displaces a particular subsection of Supply Act (No. 2) 2025‑2026 by stating the debit limit applies despite subsection 13(2) of that Supply Act and that subsection 13(2) is replaced by s 12(1) after commencement (ss 12(2)‑(3)).

Mechanics of interaction

• Interpretive primacy for extrinsic material: By declaring portfolio statements relevant under the Acts Interpretation Act (s 4), the Act permits extrinsic material to aid interpretation. This formally opens a route for administrative documents to influence the meaning of the outcomes and allowed activities for each appropriation item.
• Accounting alignment: The notional transaction instruction in s 5 is explicitly linked to the PGPA Act’s accounting approach. That aligns appropriation accounting across the PGPA framework and this Act, so that intra‑Commonwealth transactions produce appropriation debits as if actual CRF payments had been made.
• Debit limit substitution: Section 12 is an express legislative override of a subsection in another supply Act. By saying s 12(1) applies despite subsection 13(2) of Supply Act (No. 2) 2025‑2026 and that after commencement it has effect instead of that subsection, the Act directly alters the legal operation of a concurrent or prior supply Act. This is a pointed example of how appropriation instruments can adjust each other’s mechanics by express language.
• Cross‑Schedule flexibility: Section 9(1) lets an administered assets and liabilities item be applied to outcomes described in a range of Schedules across multiple appropriation acts. That creates fungibility subject to the list of Acts in s 9(1)(a)-(h). Administratively this creates a broader pool of outcomes for which certain items may be applied, but the Act’s text requires the application be for the purpose of contributing to achieving any of those specified outcomes.

Consequences of the interactions

• Dependence on extrinsic documents: Interpretation of what counts as an activity “in respect of” an outcome may require reading the portfolio statements and supplementary statements. That increases the legal and evidential importance of those documents and of ensuring they are consistent with the appropriation intent.
• Interplay with PGPA administrative duties: Because the Act delegates adjustment, accounting and special account rules to contexts controlled by the PGPA Act and the relevant supply acts, agencies must comply with both the technical directions in this Act and the procedural requirements under the PGPA system.
• Potential for statutory substitution and override: The use of explicit substitution language in s 12 demonstrates that later appropriation acts can and do modify the operation of earlier supply acts where the Parliament expressly so provides. Agencies must therefore take care when reconciling competing provisions among appropriation or supply instruments.
• Complexity of cross‑Act planning: The list of Acts in s 9(1) means that administrators must track outcomes across multiple schedules, which has implications for planning, reporting, and audit trails.

In summary, the Act is not standalone. It functions as a piece of the Commonwealth appropriations architecture, invoking the PGPA Act for definitions, adjustments and accounting, the Acts Interpretation Act for interpretive materials, the Federal Financial Relations Act for debit limits, and several supply and appropriation acts for the reach of administered assets and liabilities. Anyone using the Act must read it in that statutory context.

The Act’s text contains only a small number of internal statements about commencement, notes on publication, and its own repeal, but no recorded amendments are printed in the text provided. The following points summarise the Act’s internal history and mechanisms that affect future amendments or reprints.

Commencement and published table notes (s 2)

• Section 2 sets out the commencement mechanics via a table. The table indicates that "The whole of this Act" commences on the day this Act receives Royal Assent, which the table records as 26 June 2026. Section 2(2) contains a specific drafting convention: any information in column 3 of the table is not part of the Act and may be edited in any published version of the Act. This is a formal note which preserves the legal effect of the provisions while allowing published or online versions to include editorial or explanatory content that does not change the Act’s operative text.

No in‑text amendment history entries

• The Act as printed contains no schedules of amendments, no recorded history of prior amendments within its text, and no marginal notes indicating prior versions. It is therefore a self‑contained statutory instrument as enacted. The Act does not itself include amending language for earlier Acts beyond subject‑matter cross‑references and substitution language (for example s 12(3) replacing subsection 13(2) of Supply Act (No. 2) 2025‑2026 after commencement).

Repeal provision (s 15)

• Section 15 sets a clear expiry: "This Act is repealed at the start of 1 July 2028." That is an express sunset clause. The practical implication is that no further amendments to the Act are necessary to end its operation; the Act self‑terminates at that date unless another Act intervenes to extend or re‑enact its provisions.

Adjustments under the PGPA Act (s 6 note)

• Although not an amendment per se, the Act notes that sections 74 to 75 of the PGPA Act provide for adjustment of amounts appropriated by this Act. Such adjustments may, in practice, alter the financial effect of specified items after enactment without amending the appropriation Act itself. Those PGPA mechanisms are the normal administrative route for adjusting appropriations rather than by formal amendment of an appropriation Act.

Substitution of provisions in other Acts (s 12)

• Subsection 12(3) indicates that s 12(1) "has effect, after it commences, instead of subsection 13(2) of the Supply Act (No. 2) 2025‑2026." That is a location‑specific substitution rather than an internal amendment to this Act. It shows the Act can be drafted to change the operation of other appropriation or supply Acts upon its commencement.

Implications for tracking amendments

• Users of this Act must be attentive to:
  • Any later Acts that extend or re‑enact provisions after the repeal date.
  • PGPA Part 6 adjustment instruments or Treasury determinations that alter the financial amounts in Schedule 1 through the PGPA adjustment processes referenced in the s 6 note.
  • Any later appropriation or supply Acts that expressly amend or substitute particular subsections of other Acts, analogous to the way s 12 interacts with the Supply Act (No. 2) 2025‑2026.

In short, the Act itself does not contain a visible amendment history in the text provided. It contains a commencement convention that allows published versions to include editorial material, a set of cross‑Act substitution instructions, a reference to PGPA adjustment power, and a statutory sunset at 1 July 2028. Those are the mechanisms by which the Act’s financial effect will change over time rather than through in‑text amendment notations.

The Act as provided does not contain any internal references to judicial decisions or litigation. There are no enumerated cases cited in the text, and no marginal notes referencing previous litigation. Consequently there is no litigation history recorded within the Act document itself to summarise.

Potential litigation and interpretive flashpoints indicated by the Act Although there is no recorded litigation history in the text, the Act contains features that could give rise to legal disputes or administrative review in practice. Below are the issues where litigation or judicial review might conceivably arise, grounded in the statutory text.

1. Interpretation of portfolio statements as extrinsic material (s 4)

• Section 4 declares portfolio statements to be relevant documents under s 15AB of the Acts Interpretation Act 1901. Litigation could arise where there is disagreement between parliamentary appropriation language in Schedule 1 and the representations made in portfolio statements, and a court or tribunal is asked to determine whether particular activities are within the scope of an outcome. Disputes could also focus on the evidentiary weight to be given to portfolio statements under s 15AB.

2. Notional transactions and appropriation debits (s 5)

• Section 5 directs that notional transactions between non‑corporate entities be treated as if they were real transactions. Litigation or audit disputes could arise where an agency records or fails to record such notional transactions and an auditor or the Treasury challenges the appropriateness of the accounting treatment. A legal dispute might focus on whether a particular internal charge qualifies as a notional transaction for the purposes of s 5.

3. Scope of administered assets and liabilities items across multiple Acts (s 9)

• By providing that an administered assets and liabilities item may be applied for outcomes listed in Schedules across multiple appropriation and supply Acts, s 9 creates a multi‑instrument application question. Litigation or review may arise where an agency applies an item to an outcome and another party disputes whether the outcome was properly specified in one of the listed Schedules.

4. Obligatory payment to corporate entities (s 11(2))

• Section 11(2) appears to create a mandatory payment obligation where another Act provides that a corporate entity must be paid appropriated amounts. Litigation could conceivably arise if Treasury or Finance declines or delays a payment, or disputes that an enabling Act requires payment, and the corporate entity seeks judicial review or mandamus-like relief to compel payment. The factual and statutory relationship between the enabling Act and Schedule 1 would be central.

5. Debit limit substitution and inter‑Act conflict (s 12)

• Section 12 expressly displaces subsection 13(2) of the Supply Act (No. 2) 2025‑2026 and substitutes its own debit limit. Litigation might emerge if a party contends that the substitution was invalid, or if the mechanics of applying the debit limit to particular national partnership payments are disputed. Courts may be asked to adjudicate competing statutory interpretations about which numerical cap applies at a particular point in time.

6. Crediting to special accounts (s 13)

• The power to debit appropriations and credit special accounts if the special account’s purposes overlap with an item could be challenged where there is disagreement over whether the special account purpose is indeed covered by the item. A dispute about the lawful application of funds between appropriation items and special accounts could lead to judicial or administrative review.

No cases named in the Act

• The Act names no judicial authorities and cites only other statutes and appropriation instruments. Therefore, any litigation history would have to be developed in court records external to the Act.

Practical note for litigators and researchers

• For anyone investigating possible litigation or precedent, the relevant initial materials would include: the Act’s Schedule 1 and portfolio statements (each declared relevant by the Act), the Supply and Appropriation Acts referenced in s 9 and s 12, and the PGPA Act provisions cited by the notes. Those materials will frame the factual and legal questions that could give rise to litigation. The Act gives several specific interpretive hooks that a litigant or judicial officer would need to address.

In sum, the Act itself contains no litigation history. It does, however, set out structures and interpretive devices that could be the subject of future disputes about interpretation, accounting treatment, or the proper application of appropriations.

The Act’s brevity hides a number of practical traps and interpretive pitfalls for administrators, agency counsel, auditors and recipients. Below are the most salient “gotchas” to watch for, each grounded in the statutory text.

1. Schedule 1 is the operative detail but is not included in the Act text provided

• The Act’s operative allocations and the descriptions of outcomes appear only in Schedule 1, which the Act repeatedly references (for example s 6, s 7, ss 8-11). Not having the Schedule at hand is a major practical gap. Do not assume the act’s line items, amounts or outcome descriptions beyond the single total figure declared in s 6. Agencies must consult Schedule 1 to determine the permitted use of funds.

2. Portfolio statements are extrinsic interpretive material and may alter the practical scope of outcomes (s 4)

• Because s 4 declares portfolio statements to be relevant under s 15AB of the Acts Interpretation Act 1901, there is a risk that activities described in those statements expand or contract what constitutes an activity in respect of a particular outcome. The Act’s sections 7(2), 8(2) and 9(2) say that if portfolio statements indicate activities of a particular kind were intended to be treated as activities for a particular outcome, then expenditure for those activities is taken to be expenditure for contributing to that outcome. Practically, that means the portfolio statements can control whether an expenditure falls within an outcome, which can be surprising to practitioners who expect Schedule items alone to determine scope.

3. Notional transaction accounting can create appropriation debits where no cash moves (s 5)

• Section 5 directs that notional transactions are to be treated as if real. The example in the note warns that a “payment” between non‑corporate entities will be debited from an appropriation even though no payment is made from the Consolidated Revenue Fund. This can create apparent appropriation consumption in departmental ledgers without cash outflow, which affects budget balances and reports. Agencies need to ensure internal charging practices trigger correct appropriation debiting.

4. Crediting to special accounts may mask appropriation flows (s 13)

• Section 13 allows appropriation debits to be credited to special accounts when the special account’s purposes overlap with an item. That mechanism can shift where responsibility for a balance appears in financial statements. Care is needed to ensure that the accounting is transparent and that the special account’s purposes actually match the appropriation item.

5. The corporate entity payment obligation is fact‑sensitive and depends on other Acts (s 11(2))

• Section 11(2) makes the corporate entity payment mandatory only where "an Act provides that a corporate entity must be paid amounts that are appropriated by the Parliament for the purposes of the entity" and where Schedule 1 contains a corporate entity item. The practical risk is misreading this as an automatic entitlement. A corporate entity will need to ensure both conditions are met: an enabling Act that requires parliamentary appropriations to be paid to it and a corporate entity item in Schedule 1. The interplay between enabling Acts and Schedule 1 may be contested.

6. The debit limit substitution can affect national partnership payments unexpectedly (s 12)

• Section 12 sets a $40,000,000,000 debit limit for the current year and expressly displaces subsection 13(2) of the Supply Act (No. 2) 2025‑2026. Practitioners who rely on the mechanics of the Supply Act may find that the operative debit cap has been changed by this Act, which could affect timing and quantum of national partnership payments.

7. The “current year” is the financial year ending 30 June 2026 (s 3)

• The Act’s definition of “current year” is specific. Applying any numerical limits, reporting obligations or cross‑year calculations requires attention to this definitional point. Misapplying the “current year” definition could lead to incorrect debit limit calculation or misapplied accounting periods.

8. The Act has a fixed repeal date (s 15)

• This appropriation Act ceases at the start of 1 July 2028. Any multi‑year commitments or long‑term funding arrangements premised on this Act must be reconciled with that sunset. Expect the need for follow‑on appropriation or legislative reauthorisation for activities extending beyond the repeal date.

9. Notes that are not part of operative text but guide interpretation (s 2(2) and various notes)

• Section 2(2) warns that column 3 information in the commencement table is not part of the Act. Other notes that refer to provisions in other Acts (for example the PGPA references) are informative but non‑operational. Practitioners must be careful to distinguish note material from operative sections.

10. Cross‑Act application increases complexity (s 9)

• Section 9(1) allows administered assets and liabilities items to be applied to outcomes set out across several other Acts. Tracking the correct outcome descriptions and ensuring compliance across those instruments can be administratively cumbersome and legally delicate if outcomes are similarly named or have overlapping descriptions.

These “gotchas” are not exhaustive but highlight areas where practice often diverges from an intuitive reading. They underline the need to consult Schedule 1 and the referenced portfolio statements, to align with PGPA accounting practice, and to confirm cross‑references to supply and appropriation Acts before making or recording payments.

This section sets out the operational steps and controls suggested by the Act’s text to ensure lawful administration of the authorisations it contains. The focus is on actions and systems that agencies, accounting officers and recipients should consider putting in place to align practices with the Act’s mechanics.

1. Locate and align with Schedule 1

• Before any payment or commitment, consult Schedule 1 to identify the precise item descriptions, outcome names and amounts. The Act repeatedly ties authority to Schedule 1 (for example ss 6-11), so the Schedule will define the permitted uses and recipients. Ensure the agency’s internal budget codes map directly to the Schedule 1 entries.

2. Use portfolio statements for interpretive guidance

• Because s 4 declares portfolio statements to be relevant documents for statutory interpretation under the Acts Interpretation Act 1901, ensure that the portfolio budget statements, portfolio additional estimates statements and portfolio supplementary additional estimates statements referenced in s 3 are available, consistent with Schedule 1 and archived. Where an activity is intended to be within an outcome, ensure the portfolio statements clearly describe that intention because ss 7(2), 8(2) and 9(2) treat such portfolio statement indications as determinative for treating certain activities as expenditure for that outcome.

3. Implement notional transaction accounting practices

• Section 5 requires that notional transactions between non‑corporate entities be treated as real transactions for appropriation purposes. Accounting systems and internal guidance must be updated so that intra‑Commonwealth recharges that are not cash transfers are nonetheless recorded as appropriation debits and credits consistent with PGPA section 76 (as the Act notes). Ensure audit trails exist to explain the entries and the economic substance.

4. Observe corporate entity payment conditions

• Where Schedule 1 contains a corporate entity item and another Act requires parliamentary appropriations to be paid to a corporate entity, s 11(2) requires the full amount to be paid. Confirm: (a) whether an enabling Act imposes that payment duty; and (b) whether Schedule 1 contains the appropriate corporate entity item. If both conditions are met, ensure payment processing pipelines can effect the payment in full and that the payment is recorded against the correct corporate entity item.

5. Respect the debit limit for national partnership payments

• Section 12 sets a $40,000,000,000 debit limit for the current year for the purpose of s 16 of the Federal Financial Relations Act 2009. Treasury and agencies making national partnership payments must track cumulative debits for the current year and ensure payments do not cause the cap to be exceeded. Because s 12(2) and (3) displace subsection 13(2) of Supply Act (No. 2) 2025‑2026, do not rely on that subsection for the operative cap.

6. Use special account crediting only where purposes overlap

• Section 13 allows debits to be credited to special accounts if a special account’s purpose is covered by an item. Before effecting such movements, document the basis for concluding that the special account purpose is covered by the item and retain supporting approvals, legal advice and ledger reconciliations. Ensure such credits are consistent with the special account’s rules under the PGPA Act.

7. Maintain audit and reporting documentation aligned with the PGPA Act

• The Act references the PGPA Act for adjustment mechanisms and accounting alignment (s 6 note and s 5 note). Ensure that financial statements, internal control documentation and audit workpapers reflect how appropriations have been applied, how notional transactions have been recorded, and how special account crediting and corporate entity payments were justified.

8. Monitor temporal constraints and repeal date

• The Act repeals itself at the start of 1 July 2028 (s 15). For multi‑year commitments, build contingency plans and budget mapping so that funds and obligations are transitioned to successor appropriation instruments if necessary. Do not assume this appropriation will remain in force beyond that date.

9. Reconcile cross‑Act applications

• Where an administered assets and liabilities item is applied to outcomes listed in other Appropriation or Supply Acts (s 9(1)(a)-(h)), cross‑check the outcome language and any relevant portfolio statements in those Acts to ensure legal alignment. Maintain a cross‑reference register to track which items may be applied to which outcomes across the listed instruments.

10. Ensure internal training and governance

• Provide targeted training for finance, legal and program staff on: (a) the effect of s 5 (notional transactions); (b) the significance of portfolio statements for outcome interpretation; (c) the operational meaning of the corporate entity payment requirement under s 11(2); and (d) the debit limit mechanics under s 12. Update delegations, payment authorisation checklists and program guidance to reflect these rules.

Checklist to operationalise compliance

• Obtain and verify Schedule 1 entries and amounts.
• Locate the portfolio budget and estimates statements referenced in s 3 and ensure they are archived.
• Update accounting system rules to record notional transactions as appropriation debits and retain evidence.
• Confirm any corporate entity payment obligations by checking enabling Acts and ensure payment pipelines can transfer the full scheduled amount where required.
• Monitor cumulative national partnership payment debits against the $40,000,000,000 cap for the current year.
• Document and justify any crediting to special accounts under s 13.
• Prepare reporting and audit workpapers in line with PGPA requirements and the Act’s notes about adjustments.
• Track the repeal date and plan for post‑repeal funding arrangements where necessary.
• Maintain a cross‑Act register for outcomes and administered assets and liabilities applications.

Following these steps will align systems and decision processes with the Act’s operative text. Where interpretation of an outcome or of the overlap between a special account purpose and an item is in doubt, internal legal advice and consultation with Treasury or Finance should be sought.

This information is general legal information only, not legal advice. I can make mistakes. Before you act on, rely on, or use any of the analysis or any draft outcome from this deep dive, get a qualified Australian lawyer to check it.