The Determination is built on a handful of textual concepts it uses repeatedly and which determine legal effect.

• Specified amounts and recipients: Clause 3 operates by reference to “the amounts specified in the following table” and “the States specified in that table.” The table in the Determination and the Schedule 1 table are therefore the primary source of the actual numerical and recipient data (Table 1 and Schedule 1).

• Purposes: Clause 3 identifies three discrete statutory purposes for which these payments are to be made: (a) to support delivery by the States of “specified outputs or projects specified in Schedule 1”; (b) to facilitate “the reforms by the States specified in Schedule 1”; and (c) to reward the States for “the nationally significant reforms specified in Schedule 1.” The Determination therefore ties each payment to one or more of those three purposes, with Schedule 1 intended to contain the further specification.

• Contingent payments: The Schedule labels the line item as “Contingent Payments” and places an “x” in the Schedule row associated with “Disaster recovery funding arrangements.” That labelling in the Schedule is a conceptual attribute of the listed payments and indicates a categorisation used within the instrument, namely that the payments are a form of contingent payment rather than an ongoing entitlement or general purpose payment.

• Temporal specificity: The payments are to be made “for payment on 21 February 2020” as reflected in the Table 1 heading and Schedule 1 title. Clause 2 further fixes commencement: “This determination commences on the day on which it is made.”

• Schedule as operative detail: The Determination text expressly directs readers to Schedule 1 for “further information on these payments.” The Schedule therefore plays an operative role beyond mere illustration; it is the repository of the itemised amounts and the stated program classification (“Disaster recovery funding arrangements”).

These concepts structure how the instrument operates: it is a short, purpose-limited authorisation of defined payments, fixed in amount and date, and categorised as contingent payments directed to disaster recovery funding arrangements. The Determination links the monetary entries to the three purposes in s 3, and leaves the Schedule as the place where the concrete allocation and classification is recorded.

The Determination affects a narrow set of directly named parties and a wider set of indirect stakeholders implied by its stated purposes.

Direct recipients: The instrument identifies States as the parties to receive the payments , the amounts are “to be paid to the States specified in that table” (s 3). The Schedule 1 table names specific States and lists amounts for some of them: New South Wales ($10,533,337), Victoria ($3,466,667), Queensland ($1,425,000), and South Australia ($1,575,000). Western Australia, Tasmania, the Australian Capital Territory and the Northern Territory are listed in the Schedule with a dash, indicating no payment on this schedule. The total for the listed payments is $17,000,004.

State finance and administration actors: The practical effect is on State treasuries and departments that will receive, account for and disburse the funds within the States. Under s 3, the funds are “for the purpose of making a grant of financial assistance” to support State delivery of specified outputs or projects, to facilitate specified reforms, or as rewards for nationally significant reforms specified in Schedule 1. Therefore, State agencies responsible for disaster recovery, emergency management, or the specific outputs or projects that Schedule 1 purports to cover will be the operational users of the grant monies once the State has cause to pay them onward or apply them to projects.

Indirect beneficiaries: The Schedule labels the payments under “Disaster recovery funding arrangements.” That classification identifies an intended substantive area of expenditure , disaster recovery , and therefore suggests that recipients of State-administered disaster recovery grants, or participants in State disaster recovery projects (local government, affected businesses, communities) are the ultimate beneficiaries of the funds as deployed by States. However, the Determination itself lists only the State-level recipients and dollar amounts; it does not list individual end beneficiaries or describe eligibility at the recipient level.

Administrative actors in the Commonwealth: The Determination compels some administrative action on the Commonwealth side , specifically the payment of the amounts listed on the date specified , and therefore engages whatever Commonwealth agency or officer is responsible for executing payments, maintaining records and ensuring that the payments are made in accordance with the Determination. The Determination does not name the Commonwealth officer or department, but the legal effect is to create a payment instruction.

Parties not receiving funds: The States recorded with a dash in Schedule 1 (WA, TAS, ACT, NT) are implicitly not entitled to a payment under this Determination on the date shown. That differential treatment may affect intergovernmental relations or State budgeting, but the instrument itself only records the absence of a payment entry for those jurisdictions.

Other stakeholders: Because the Determination ties payments to “specified outputs or projects,” entities contracted by States to deliver those outputs, auditors, and parliamentary oversight bodies may have an interest in how the funds are applied, although the Determination does not itself set out reporting or compliance pathways.

The Determination creates a discrete set of operative duties and correlative rights centred on payment and purposes; it contains few procedural or compliance prescriptions beyond those.

Duties created by the instrument

• Pay the amounts: Clause 3 imposes the primary duty, expressed in mandatory form: “The amounts specified in the following table are to be paid to the States specified in that table.” The duty is to pay the listed dollar sums to the named States.
• Pay for stated purposes: The clause qualifies the payment duty by specifying permitted purposes: the payments are for making a grant of financial assistance either to support delivery by States of “specified outputs or projects specified in Schedule 1,” to “facilitate the reforms” specified in Schedule 1, or to “reward the States for the nationally significant reforms specified in Schedule 1.” The duty to pay is therefore purpose-limited.

Rights of States

• Right to receive payment: States identified in the table have the right to the amounts specified in their column on the payment date specified in the Table and Schedule. That right is direct in the text: the amounts “are to be paid to the States specified in that table.”
• Right to apply funds to enumerated purposes: The instrument confers a right to have the funds applied for the purposes listed in s 3; a State receiving the funds may apply them in accordance with those stated purposes.

Absence of other duties or conditions in the text

• No express matching contribution requirement: The Determination does not, in its text, require States to contribute matching funds, nor impose conditions of State co-payment. Clause 3 speaks only of purpose-limited grants.
• No reporting, audit or time-for-use obligations specified: The Determination does not include text requiring States to report back, to spend by a particular deadline, to meet performance milestones, or to subject the funds to particular audit or acquittal processes. The only temporal specificity in the text concerns the date of payment (21 February 2020) and commencement (day made).
• No procedural duties for private parties: The Determination does not create obligations for recipients other than States. There is no text in the instrument imposing duties on local government, NGOs, businesses or individuals.

Conditionality labels

• “Contingent Payments” in the Schedule: The Schedule labels the payments “Contingent Payments,” and the particular row is headed “Disaster recovery funding arrangements.” That labelling may signal that the payment type is contingent by category, but the Determination itself directs the amounts be paid on the date specified; it does not set out contingency triggers in text. Therefore, any contingent features remain at the level of classification rather than expressed legal conditions in this instrument.

Who decides

• The instrument itself makes the decisive allocations. It does not in this text assign discretion to ministers or officials to change amounts, withhold payment or reallocate funds. The Determination therefore expresses fixed entitlements to the named States as at the date specified.

In short, the Determination creates a primary duty to pay specific amounts to specified States for the limited purposes in s 3, and a corresponding right for the named States to receive and apply those funds. It contains no express procedural enforcement, reporting, matching or timeline obligations within its own text.

The Determination contains no express penalty regime, sanctioning provisions, or enforcement mechanisms. The instrument is narrowly framed and limited to specifying amounts, recipients and purposes; it does not include provisions that prescribe consequences for non‑compliance by States, or that set out criminal, civil or administrative penalties for misuse or misapplication of the funds.

What the instrument states and what it omits

• No enforcement clauses: There is no section in the Determination or Schedule that prescribes withholding, clawback, repayment obligations, sanctions, or forfeiture if funds are not used for the purposes in s 3. The text confines itself to specifying amounts and purposes.
• No administrative enforcement mechanism: The Determination does not set out monitoring, reporting, audit requirements or oversight structures that would operate to detect or correct non-compliance. There are no procedural steps for the Commonwealth to inspect State expenditure or to require acquittals under the terms of the instrument itself.

Implications for practical enforcement

• Enforcement likely occurs under other instruments or frameworks: Because this Determination lacks express enforcement provisions, any practical enforcement, conditions, monitoring, or dispute resolution concerning the funds would depend on other agreements, administrative rules, or legal frameworks not contained in this instrument. The Determination itself directs payment and purpose only.
• Risk allocation: The absence of enforcement text concentrates uncertainty about recourse and remediation outside the Determination. Those seeking to understand remedies for alleged misspending or misapplication must look to other legal or contractual arrangements beyond this Determination; the present text provides no remedies, timelines, or penalties.

Record-keeping and implied accountability

• While the Determination does not mandate reporting, the allocation of funds to specific purposes (disaster recovery funding arrangements) creates a public expectation of purpose-limited use. Nonetheless, any legal enforcement mechanism to compel compliance or to impose penalties is not set out in this instrument.

Summary: the Determination is directive as to payment and purpose but silent on penalties and on enforcement mechanisms. It neither creates nor specifies sanctions, monitoring procedures, or dispute-resolution steps within its text.

The Determination itself is a standalone instrument in its text and does not expressly cross-reference other statutes, regulations or instruments within the provided document. Its internal cross-reference is to Schedule 1, which it incorporates for “further information on these payments” (clause 3 and the Schedule title). Beyond that, the instrument contains no textual references to other laws, Acts, or legal frameworks.

Internal interaction

• Schedule 1 is part of the instrument: The Determination explicitly directs that the amounts in the following table (visible in the instrument) and the “further information on these payments” in Schedule 1 are operative. Therefore, the principal point of interaction is internal: the main body (clause 3) defines purposes and relies on Schedule 1 to itemise amounts and to label the payments (Schedule 1 shows the payments as “Contingent Payments” related to “Disaster recovery funding arrangements”).

Absence of express cross‑statutory linking

• No statutory citations: The text does not cite or refer to any enabling legislation, appropriation authority, or other statutory provisions. It does not, in its own terms, state the Act or power under which the Determination is made. It likewise does not state that payments are to be sourced from a named appropriation, nor does it reference legal instruments governing Commonwealth-State financial relations by statute.
• No express interaction clauses: The Determination does not contain savings, transitional, inconsistency, or supremacy clauses that specify how it operates in relation to other laws or instruments. It contains no language that disapplies or modifies other legal obligations.

Practical consequence for readers seeking legal force

• Users must look beyond the instrument for the broader legal architecture: Because the Determination itself is silent on enabling law and on interaction with other statutes, any thorough legal analysis of how this instrument integrates into the federal regulatory or fiscal system requires consultation of the enabling statutory framework, appropriation instruments and any intergovernmental agreements that are external to this text. The present document alone records the allocation and purposes but does not set out how or under what statutory power it is made.

Compatibility and conflict risk

• The Determination does not purport to override or displace other laws, nor does it state that it operates subject to other obligations. As drafted, there is no textual mechanism addressing conflicts between the use of funds under this Determination and State or Commonwealth legal obligations; resolving such conflicts would fall to the applicable legal frameworks outside the instrument.

Conclusion on interactions

• In sum, the Determination interacts internally with its Schedule and otherwise is silent about legal relationships with other laws or instruments. Practitioners needing to chart the instrument’s legal effect in a broader statutory context must identify the enabling power, appropriation authority and any intergovernmental arrangements outside this Determination, because those elements are not contained within the text provided.

The text of the Determination contains only two temporal statements: the commencement provision and the specific payment-on date in the Table and Schedule. It does not record any amendments, variations, revocations or previous versions within the document itself.

What the instrument records

• Commencement: Clause 2 states simply: “This determination commences on the day on which it is made.” There is no recorded prior or later amendment in the text.
• Payment date fixed in Table/Schedule: The Table heading and Schedule 1 title state the payment is “for payment on 21 February 2020.” That date fixes the operative payment moment for the amounts listed.

Absence of amendment entries

• No amendment log: The Determination does not include an amendment history section, no marginal notes indicate changes, and no “made on” or “signed” dates beyond the February 2020 naming convention are present in the body provided.
• No saving or transitional amendment clauses: The instrument does not contain clauses addressing retrospective changes, savings, or transitional arrangements that would suggest prior alterations.

Implication for users

• The Determination as provided should be treated as a single, self-contained instrument effective on the date it was made, and effective to require payment on 21 February 2020. There is no internal evidence in the text of subsequent amendment or revocation. Any amendments, revocations or subsequent related Determinations would need to be located in other instruments or records outside this document, because none are recorded herein.

Recommendation for verification

• Practitioners seeking a complete statutory history or amendment chain should consult the issuing repository or official register in which the Determination is published to obtain any subsequent versions, explanatory memoranda or amendment instruments. The instrument itself does not supply that history.

The Determination does not record any litigation history, nor does it reference decisions, disputes, or court orders. The text provided is purely an allocation instrument and contains no material describing challenges, judicial review proceedings, or legal disputes arising from it.

What the document contains

• No litigation references: There are no case citations, no references to ongoing or concluded proceedings, and no description of disputes in the Determination text or in Schedule 1.
• No procedural dispute resolution clauses: The instrument includes no mechanisms for arbitration, dispute resolution between Commonwealth and States, or processes for resolving disagreements over the allocation or use of funds.

What this means in practice

• Absence of recorded litigation does not imply the absence of any disputes in reality, only that none are recorded in this instrument. Any litigation relating to the payments, their timing, the classification as contingent payments, or the application of funds to disaster recovery funding arrangements would be documented outside the Determination text.
• If a reader requires information on judicial interpretation, challenges, or enforcement litigation, those records will not be found in this Determination; searches of court records, tribunal files, or administrative review filings are required to uncover any litigation history.

Practical note for advisers

• Because the Determination contains no litigation history or dispute framework, parties involved in implementing or accepting the funds should assume that any legal disputes will be resolved under applicable external legal frameworks, and should identify relevant statutory, contractual or administrative procedures elsewhere to understand dispute resolution avenues.

This section flags textual features and practical pitfalls in the Determination that can cause misinterpretation or operational friction. Each point is grounded in the instrument’s text.

1. Purpose specificity without operational detail

• The instrument ties payments to purposes in s 3 (support specified outputs or projects, facilitate reforms, or reward nationally significant reforms specified in Schedule 1). However, Schedule 1 contains only a program label (“Disaster recovery funding arrangements”) and amounts; it does not list concrete project names, performance indicators, eligibility criteria, milestones, or expenditure timetables. This disjunction means the Determination limits funds to stated purposes but does not supply operational detail to guide State implementers or to support external audit.

2. “Contingent Payments” label, but no contingency trigger

• The Schedule classifies the line as “Contingent Payments” and marks the “Disaster recovery funding arrangements” row with an “x.” The Determination nevertheless instructs that the amounts “are to be paid” on 21 February 2020. The instrument does not specify what contingency, if any, gives rise to or negates the payment. Practically, the label could be misread as implying that payment is conditional on events not described in the document; the document itself sets the payment date and amounts without conditional language.

3. Temporal precision raises execution risk

• Payments are to be made “on 21 February 2020” (Table/Schedule). If administrative or appropriation processes prevent payment on that exact date, the instrument contains no fallback or cure provision. The absence of a mechanism for delayed payment or adjustment of amounts could create legal or accounting questions about compliance with the Determination if practical impediments arise.

4. Dashes for some jurisdictions

• Several jurisdictions (WA, TAS, ACT, NT) are recorded with a dash in the Schedule row. That formatting indicates no payment listed, but absent an explicit legend the dash can be misinterpreted. Practitioners should treat the dash as a zero allocation on this Determination rather than as missing data.

5. No enforcement or reporting mechanisms

• The Determination has no clauses requiring reporting, acquittal, audits, or sanctions. If the Commonwealth later seeks to require accountability or seek recovery for alleged misuse, such mechanisms would have to be founded on separate agreements or legal authorities; they do not appear here.

6. Narrow scope of the instrument

• The instrument is narrow: it specifies amounts and purposes for a single payment date and does not create an ongoing program architecture. Parties should not assume it establishes recurring payments, eligibility frameworks, or broader program governance.

7. Ambiguity over who must do what administratively

• The Determination directs amounts “are to be paid to the States.” It does not name the Commonwealth officer or agency responsible for making the payment, nor does it set out the State administrative recipient or account. Administrative practitioners should therefore confirm the operational payment instructions in contiguous administrative records.

8. No appropriation text in the instrument

• The Determination does not describe the source of funds, an appropriation reference, or budget line. That absence is a practical gotcha for accountants and auditors who will need to trace the appropriation authority for the transaction in separate budget or appropriation instruments.

9. Potential expectation gap between label and content

• The use of “Disaster recovery funding arrangements” as the program label may create public expectation that the Schedule contains extensive program detail; it does not. This may create transparency or oversight challenges if stakeholders expect clearer allocations to specific recovery projects.

10. Total rounding and arithmetic

• The Schedule total is $17,000,004 and is the arithmetical sum of the listed amounts. Verify arithmetic when transcribing the amounts into accounting records; the instrument provides the total explicitly.

These gotchas derive from the Determination’s brevity and its separation of allocation (amounts and recipients) from operational and enforcement detail. Practitioners should not read operational or conditional detail into the instrument beyond the text.

The Determination creates a small number of concrete compliance steps for payment authorities, State finance officers and those administering disaster recovery programs. The instrument itself contains limited procedural detail, so compliance requires careful documentary practice and coordination with any external authorisations or agreements.

1. Execute the payment as specified

• The primary obligation in the Determination is the payment of the specified amounts to the States listed. The amounts are to be paid “on 21 February 2020” (Table 1 heading; Schedule 1 title) and are enumerated in Schedule 1. The Commonwealth payment authority must ensure that the payments are executed on the date specified, in the specified amounts, and to the State recipients listed (NSW, VIC, QLD, SA for the amounts shown).

2. Record the purpose-limited nature of the funds

• Clause 3 limits the funds to three purposes: supporting delivery of specified outputs or projects specified in Schedule 1; facilitating reforms specified in Schedule 1; or rewarding the States for nationally significant reforms specified in Schedule 1. Even though Schedule 1 contains limited operational detail, account officers should tag the incoming or outgoing entries with the purpose label “Disaster recovery funding arrangements” and ensure internal compliance checks reflect the purpose limitation.

3. Document the payment trail and provenance

• Because the Determination contains no reporting or audit clauses, best practice is to create an auditable paper trail showing (a) the authority to pay (this Determination), (b) the date and amount paid, (c) the bank or transfer details of the State receiving the funds, and (d) internal approvals. Such records will be necessary if an external audit or parliamentary question later examines the transaction.

4. Reconcile with appropriation sources

• The Determination does not specify the appropriation or budget source for the payments. The paying agency must therefore reconcile the amounts with available appropriations and budget instruments outside this Determination to ensure the funds can be lawfully disbursed. Keep appropriation references, project codes, and ledger entries aligned with the Determination’s amounts.

5. For State recipients: allocate funds to disaster recovery purposes and retain evidence

• State finance officers receiving the funds should allocate them within State budgets to disaster recovery funding arrangements or to the relevant outputs/projects contemplated by Schedule 1. Retain records that show how funds were used and which projects or grants were supported. Although the Determination itself does not require reporting, acquiring contemporaneous evidence of application to the stated purposes minimises later risk.

6. Clarify ambiguities before acting

• Where the Schedule uses a dash to indicate no payment for certain jurisdictions, confirm whether that denotes intentional zero allocation. Also clarify any operational details not supplied in the Determination (for example, whether there are internal State program rules setting recipient eligibility or any separate funding agreements that implement the grant on the State side).

7. Coordinate intergovernmentally where necessary

• If there is an expectation of program delivery across Commonwealth and State lines (for instance between State agencies and local councils or emergency services), establish the necessary memoranda, contracts or grant agreements at the State level to formalise allocations to end recipients. The Determination itself does not create those downstream contractual links.

8. Preserve the instrument and Schedule in compliance files

• Keep the Determination and Schedule 1 in the transaction file so auditors and oversight bodies can readily see the authority for the payment and the purposes stated in s 3.

9. Treat the “contingent” label with care

• Although Schedule 1 labels the payment as “Contingent Payments,” the Determination directs a concrete payment on a fixed date. Do not delay payment on the basis that contingency language elsewhere implies a trigger unless there is separate written authority to do so.

10. Seek external legal advice if enforcement or recovery issues arise

• If questions arise later about misuse, alleged misapplication, or the need to recover funds, the Determination contains no recovery or enforcement clauses; legal advice should be sought regarding the appropriate legal basis for any remedial action, using instruments outside this Determination.

In short, compliance is straightforward in form: pay the listed sums on the date specified, tag them to the purposes identified in s 3 and Schedule 1, and maintain robust records. However, because the Determination provides little procedural or enforcement detail, administrative prudence requires reconciling the transaction with appropriation authority and with any downstream State or intergovernmental arrangements that govern program delivery.