The determination operates through several basic legal and administrative concepts set out in its operative clauses and schedule.

Payments directed by instrument: Clause 4 is the legal command. It states that specified amounts are to be paid to specific States as identified in the Schedule. This is the central authoritative act: an instrument directing money to specified recipients for defined purposes. The Schedule is therefore the primary source of operative detail.

Purpose categories: The text identifies three discrete stated purposes for the payments: support the delivery by the States of specified outputs or projects; facilitate the reforms by the States specified in Schedule 1; or reward the States for nationally significant reforms specified in Schedule 1 (cl 4(a)-(c)). These purposes are expressed in the language of grant-making and reform facilitation and reward. The determination uses the phrase “for the purpose of making a grant of financial assistance to” followed by the three purposes. The phrasing ties the Commonwealth payment to the function of grants and reform incentives.

Schedule structure and line items: Schedule 1 organises payments into topical program headings (for example, Health; Community Services; Affordable Housing; Infrastructure; Environment; Contingent Payments). Under those headings, specific projects or program components are listed (for example, “Health Infrastructure Projects”, “Specialist disability services”, “Homelessness”, “Investment Rail”, “SA River Murray Sustainability Program - Irrigation Industry Assistance Component”, “Natural disaster relief”). The schedule records, for each line, allocations per jurisdiction and totals. Entries in the table include monetary amounts, column marks such as “x” and symbols like dashes. Those marks appear to be part of the tabular presentation: they flag items but the instrument text does not define the marks within the clauses, leaving the table itself as the operative record.

Date and payment occasion: The schedule is explicitly captioned as amounts “for payment on 9 October 2017.” The instrument’s commencement clause fixes legal effect from 4 October 2017 (cl 2). The combination of those dates means that the instrument came into force shortly before the scheduled payment date. The schedule therefore functions as a dated allocation instruction for a specific payment sweep.

Revocation and replacement: Clause 3 revokes Determination No. 125 (October 2017). The revocation mechanism is a conventional administrative law means of replacing one legislative instrument with another. The revocation indicates that No. 126 supersedes No. 125 as the scheduling and allocation instrument for the relevant payment occasion.

Aggregate totals and distributional profile: The schedule sets out both per‑line and per‑jurisdiction totals. The final total of $333,947,612.27 is the aggregate amount allocated under this determination. The distribution is uneven across programs and States: for example, NSW receives $152,014,149.49, about 45.5% of the aggregate; QLD receives $96,965,014.65, about 29.0%; smaller jurisdictions receive correspondingly lower totals (for example, ACT $504,014.22).

Absence of detailed conditions in the instrument: The clauses of the instrument are concise and primarily allocative. Clause 4 describes purposes but does not append express conditions, milestones, reporting requirements, matching fund obligations, or enforcement provisions within this short statutory text. The schedule contains descriptive programme labels and monetary allocations but does not expand those labels into detailed program rules or performance measures. The legal core therefore is an allocation instrument tied to schedule descriptions and totals.

Taken together, the main concepts are: an administrative determination that fixes Commonwealth payments to States, tied to a schedule of program‑labelled allocations, dated for a discrete payment occasion, and revoking the prior instrument. The schedule is the operative detail; the clauses provide the legal authority and purposes.

Primary payers and recipients: The determination directs the payment of sums set out in Schedule 1 to the States specified in that table (cl 4). The instrument therefore directly affects two institutional groups: the payer (the Commonwealth entity responsible for making payments under federal financial relations instruments) and the State and Territory governments that receive those sums. The determination’s title and form identify it as a Commonwealth instrument, and clause 4’s wording makes the obligation to pay explicit. Schedule 1 itemises who receives what, including NSW, VIC, QLD, WA, SA, TAS, ACT and NT with amounts for each program line and a final total by jurisdiction.

State agencies and program administrators: Although not named in the determination, the program headings and project descriptions in Schedule 1 imply specific State agencies and program administrators will be the practical managers of the funds once received. For example, line items such as “Health Infrastructure Projects”, “Specialist disability services”, and “Investment Rail” will be administered by State health departments, disability services agencies, and transport/infrastructure departments respectively. The determination itself does not name administering agencies, so the immediate effect is on the State governments as recipients, which must allocate internally to relevant agencies.

Indirect recipients and service delivery stakeholders: The stated purposes (supporting the delivery by the States of specified outputs or projects, facilitating reforms, rewarding reforms) mean that third‑party recipients , such as hospitals, community service providers, housing services, contractors, and ultimately service users , are affected indirectly. The instrument allocates money to States so they can support projects and reforms that change service delivery. For example, the schedule includes “Home and community care” with $15,862,324.62 allocated to WA (Schedule 1), and “Homelessness” with allocations across jurisdictions. Those funds will be used by States to fund service delivery, procurement and contracting arrangements with private and non‑government providers.

Budgeting and accounting: The table provides precise dollar figures for each State and program. These figures affect State budgetary planning and accounting for the financial year in which the payment is made. For example, NSW’s receipt of $152,014,149.49, and the NT’s receipt of $1,394,038.35 (Schedule 1 totals), are line items States must incorporate into their financial statements and planning. The schedule’s caption indicating payment on 9 October 2017 suggests short lead times between instrument commencement (4 October 2017) and actual cash transfer.

Concentrated and program‑specific effects: The distribution shows concentrated payments that will cause particular effects in certain jurisdictions and program sectors. A prominent example is the “Natural disaster relief” allocation of $101,675,795.00 to NSW (Schedule 1, Contingent Payments), which represents a substantial single‑line inflow to a single State. Infrastructure allocations are large in some jurisdictions , e.g. QLD’s “Infrastructure Investment Programme - Investment Road” entry of $79,990,000.00 and a total infrastructure allocation to QLD of $82,990,000.00 (Schedule 1). These concentrated flows will direct State administrative focus and capital program activity.

Legal and compliance staff: Legal advisers in both Commonwealth and State agencies, internal audit units, and program compliance officers are affected in that they must interpret, implement and monitor the payments. The schedule’s specific labelling of payments requires administrative decisions about matching to projects, procurement, and internal recordkeeping.

Finally, because the determination revokes Determination No. 125 (cl 3), those who tracked the previous instrument should account for any differences , practitioners advising States, auditors, and stakeholders in previously scheduled projects will need to identify whether amounts or allocations changed as a result of the revocation and replacement.

Express duties created by the instrument are narrowly drawn and primarily allocative. Clause 4 imposes the principal duty by stipulating that the amounts specified in the table are to be paid to the States named in Schedule 1 in order to make grants of financial assistance towards the three stated purposes: supporting State delivery of outputs or projects, facilitating State reforms, or rewarding nationally significant reforms (cl 4). The payment instruction is the primary duty incumbent on the payer. Clause 2 sets the commencement date (4 October 2017), which fixes when these duties take legal effect for the instrumental regime. Clause 3 revokes the prior instrument, thereby terminating any payment flow or legal effect that was dependent on Determination No. 125 (October 2017).

Rights of States: The principal right conferred on the States by this instrument is the right to receive the specified sums. Schedule 1 itemises per‑State allocations; the State with a listed allocation has a corresponding entitlement under the determination to the monetary amount shown for the payment occasion indicated (“for payment on 9 October 2017”). The instrument therefore creates a legal entitlement to receive funds on the date and in the amounts identified.

No express obligation on States set out in the clauses: The determination’s clauses do not impose express substantive duties upon recipient States within the text provided. Clause 4 frames the payments as “for the purpose of making a grant of financial assistance to” specified ends, but the instrument does not itself set out conditions, performance milestones, reporting obligations, matching requirements, times for expenditure, or clawback mechanisms within the clauses included. That means the determination, on its face, is an allocation instrument rather than a conditional funding agreement. Any obligations States must satisfy may instead be contained in accompanying instruments, intergovernmental agreements, separate schedules, or administrative guidelines not reproduced in this document. Practitioners should therefore treat the instrument as confirming payment entitlements and purposes while seeking the detailed terms that operationalise the purpose and compliance obligations elsewhere.

Practical duties inherent in administration: Although the text does not spell out operational duties, the nature of the allocation creates practical responsibilities for State finance and program managers. States must (a) accept and account for the payment; (b) allocate funds internally to relevant agencies and projects matching the programme labels in Schedule 1; (c) ensure public sector and procurement controls apply to expenditure; and (d) retain documentation showing that funds were applied to the designated programme goals. Those practical duties arise from the States’ internal legal and administrative requirements and from the description of the payments’ purposes in clause 4 and Schedule 1.

Revocation effect on duties and rights: Clause 3’s revocation of Determination No. 125 changes the governing instrument and thus can alter the extent or timing of rights and duties that flowed under the previous instrument. If No. 125 conferred different amounts or conditions for the same payment occasion, the revocation replaced those arrangements with the No. 126 schedule; the practical effect is that the rights to receive the sums and the Commonwealth’s duty to pay are governed by No. 126 as of its commencement date.

Absence of enforcement provisions: The instrument does not specify enforcement mechanisms or penalties against States should funds be misapplied, nor does it create express rights of action in third parties. Any enforcement rights or breach remedies would therefore need to be traced to other legal instruments or administrative processes beyond the text of this determination.

The determination itself does not establish penalties, sanctions or enforcement mechanisms within the clauses or the schedule provided. Clause 4 sets purposes and allocates amounts but makes no provision for clawback, suspension, repayment obligations, or penalty regimes should funds be misused, nor does it specify compliance reporting requirements or audit triggers. Clause 5 indicates Schedule 1 contains further information on the payments, but that “further information” in the schedule is limited to item descriptions, jurisdictional allocations and totals; it does not include express enforcement provisions or sanctioning mechanisms within the text presented.

Consequently, the instrument is an allocation order rather than a fulsome contractual or regulatory funding agreement. The practical enforcement of proper use of funds, if any, must therefore rely on external mechanisms: administrative oversight by the Commonwealth’s finance agency, bilateral or multilateral intergovernmental agreements, general Commonwealth financial accountability frameworks, State internal controls, and ordinary public sector audit and anti‑fraud processes. Those external mechanisms are not set out in this determination; the instrument is silent on which entity monitors compliance, what standards must be met to retain funds, or how disputes over entitlement are to be resolved.

Because the determination revokes Determination No. 125 (cl 3) and replaces it, any enforcement or penalty provisions that might have been present in the earlier instrument would not apply after revocation unless expressly preserved. The text provided does not indicate preservation clauses or transitional rules that carry across enforcement provisions from the revoked instrument.

For practitioners advising States or providers, the practical implication is that questions about enforcement, auditability and penalties must be resolved through documents and protocols outside the instrument itself. Those might include the Commonwealth’s internal payments policy, separate National Partnership Agreements or Project Agreements, public sector audit arrangements, or other legal instruments that allocate duties and enforcement rights. Because none of those are included in the text provided, the determination cannot be relied upon to supply enforcement detail.

Finally, the label “Contingent Payments” appears in the schedule and includes a “Natural disaster relief” entry; contingency labels typically imply an external trigger or condition for payment. However, the schedule records the contingent payment amount ($101,675,795.00 to NSW) as a line item for payment on 9 October 2017. The determination does not supply the triggering mechanism within its text, nor does it set out penalties for ineligible contingency claims. Practitioners should therefore assume the document does not itself provide enforcement or conditionality detail for contingent items.

The text of this determination interacts with other elements of the Commonwealth’s administrative and financial architecture by operation of being a scheduled payment instrument, but the determination itself is compact and contains limited cross‑references. The instrument explicitly revokes the earlier Federal Financial Relations (National Partnership Payments) Determination No. 125 (October 2017) (cl 3). That revocation is a direct legal interaction: No. 126 replaces No. 125 as the operative instrument governing payments scheduled for the relevant occasion.

As an allocation instrument, this determination sits within the broader federal financial relations framework in which the Commonwealth periodically issues determinations to allocate National Partnership Payments to States. The determination’s purpose language (cl 4) frames the payments as grants of financial assistance to support State delivery, to facilitate reforms, or to reward nationally significant reforms. Those policy objectives indicate interaction with programmatic, budgetary and reform processes within the Commonwealth-State fiscal architecture, albeit the determination does not itself set out the detailed architecture of those interactions.

The schedule’s program headings (Health; Community Services; Affordable Housing; Infrastructure; Environment; Contingent Payments) indicate that the payments are intended to be applied in areas often regulated or funded by State law and administered by State agencies. Therefore, on a practical level, the determination’s payments will interact with State statutory regimes governing health services, disability services, housing supports, infrastructure approvals, environmental regulation and disaster response. The determination does not append or alter State statutes; it merely supplies money to States for specified labelled purposes. The legal effect is to authorise Commonwealth expenditure in a way that affects State budgeting and program delivery.

Because the instrument does not itself specify performance conditions or reporting requirements, interactions with other legal instruments that impose those duties are likely. For example, detailed project agreements, intergovernmental agreements or policy guidelines not reproduced in the text may impose compliance obligations, auditing regimes, or reporting lines that connect the payment to legal requirements elsewhere. The determination’s silence on those matters suggests it should be read in combination with such external documents to understand the full legal regime that actually governs expenditure, oversight and accountability.

The instrument also has temporal interactions with other determinations and budgets: it replaces No. 125 and takes effect from 4 October 2017 (cl 2-3), and it identifies a payment occasion of 9 October 2017. That timing interacts with Commonwealth and State fiscal years and with any other legislative or administrative instruments controlling appropriation, drawdown, and cash management for that period. Where contingent payments are listed (for example, the Natural disaster relief line), the planned payment may be subject to triggers or contingencies recognised in other instruments or disaster relief frameworks; those triggers are not specified in this determination.

Finally, because the determination fixes allocations by State and program, it will be a primary document auditors use in checking whether funds were received and properly accounted for. It interacts with public sector auditing standards and financial reporting obligations, which are legal and administrative regimes external to the determination but practically engaged when the funds are expended and reported in State financial statements.

In sum, the determination is an allocative instrument that replaces a prior instrument, supplies a schedule of payments and labels their intended purposes; the detailed legal obligations, compliance mechanisms and operational interactions are likely to be located in other instruments and administrative arrangements not reproduced here. Practitioners should therefore treat this determination as the allocative node within a wider legal and administrative network.

This determination contains a concise recorded amendment history confined to the immediate substitution of instruments. Clause 2 provides the commencement: “This determination is taken to have commenced on 4 October 2017.” Clause 3 expressly revokes the earlier Federal Financial Relations (National Partnership Payments) Determination No. 125 (October 2017). There are no other amendment provisions or historical entries included in the text provided.

Implications of the recorded items are the following. First, the instrument’s commencement clause fixes the legal moment from which its provisions should be read as effective. Payments scheduled for 9 October 2017 therefore fall within the operational window of the instrument. Second, the revocation clause (cl 3) replaces the prior instrument No. 125; the determination operates as the current legal authority for the allocations listed in Schedule 1 as from its commencement date. There is no transitional clause recorded that preserves any provisions of the earlier instrument; the revocation is stated simply and without qualification.

No subsequent amendments to Determination No. 126 are recorded in the text provided. The schedule itself repeats its itemisation (the document contains duplicate blocks of the table) but both sets present the same allocation totals and line entries, culminating in the same aggregate total of $333,947,612.27. The document does not show any later amending instruments, variations to amounts, or reclassifications within the text reproduced.

Because the revocation of No. 125 is the only amendment‑type action recorded, an analyst seeking amendment history beyond that single replacement will need to consult the Federal Register of Legislation or the administrative records of the Commonwealth for any later variations, revocations or consequential instruments affecting these payments. The determination as presented is static: it commences on 4 October 2017, revokes No. 125, and sets out the Schedule for the payment occasion on 9 October 2017.

For practical purposes, practitioners should confirm whether any subsequent determinations, legislative changes, or administrative directions altered the allocations, imposed conditions, or created consequential obligations after the date of this instrument. The determination itself does not record further amendments, nor does it supply an internal mechanism for future amendment.

The determination text contains no record of litigation and does not reference any judicial decisions, declaratory statements from courts, or disputes concerning its content. There are no named cases, challenges, or judgments attached to or noted within the text of the instrument. The instrument is an administrative funding schedule and, as presented, includes only the statutory allocation language (clauses 2-5) and the detailed Schedule 1 table of payments.

Given its nature as an allocative administrative instrument, potential litigation connected to it could theoretically arise in a range of contexts: disputes over entitlement to funds, questions about whether funds were used for the stated purposes, judicial review of administrative decisions about payment timing, or contract and procurement disputes arising from State expenditure decisions. None of those scenarios are evidenced in the text provided.

Practitioners requiring information on whether this determination has been the subject of judicial scrutiny, controversial administrative review, or dispute resolution proceedings will need to search court records, tribunal decisions, and administrative appeals beyond the determination text. The instrument does not contain cross‑references to dispute resolution procedures or specify the forum for any disputes arising under it.

In the absence of recorded litigation within the instrument, advisers should proceed on the basis that the determination is an administrative funding direction. Where contentious issues relating to its operation emerge , for example, where States and the Commonwealth disagree about interpretation, timing, or conditionality of payments , those matters would be litigated or otherwise resolved under general federal administrative law, contractual remedies or through intergovernmental processes, none of which are recorded inside this determination.

1. Allocation versus condition. The instrument allocates sums and declares high‑level purposes (cl 4) but does not set out detailed conditions, reporting obligations or eligibility criteria within the clauses or the schedule. That matters because a State that treats the determination as a conditional funding agreement may find no express conditions in the instrument itself: the detailed conditions may be elsewhere. Practitioners should not assume that the presence of a programme label in Schedule 1 = an embedded set of detailed funding rules.

2. Revocation replaces earlier instrument. Clause 3 revokes Determination No. 125. If an adviser is working from No. 125, they must check for any shifts in amounts, recipients or labels. The replacement could change entitlements or program descriptors; the determination does not explain differences between No. 126 and No. 125.

3. Table notation and presentation idiosyncrasies. The schedule uses dashes “-” and an “x” notation in the table cells. The instrument text does not define those marks. In practice, a dash likely indicates no allocation in that cell and “x” marks the line as a National Partnership Payment; however, the document itself does not include a legend defining those marks. Accountants and legal advisers should confirm reading conventions with the payments agency rather than rely on assumption.

4. Contingent Payments label. The schedule includes a “Contingent Payments” heading and a “Natural disaster relief” entry for NSW of $101,675,795.00. The use of the word “contingent” commonly implies a trigger; however, the schedule simultaneously lists the contingent payment for payment on 9 October 2017. The instrument does not provide the contingency trigger, the conditions for claiming, or the mechanism by which contingency status was resolved. Practitioners should investigate the underlying policy or agreements that created the contingency to understand whether any post hoc conditions attach.

5. Concentration of single‑item large sums. Some line items are highly concentrated (for example, NSW’s $101,675,795.00 under Natural disaster relief, or QLD’s $79,990,000.00 under Investment Road). Such concentrated flows create political and audit focus and therefore greater administrative oversight risk. States should expect that large single‑item allocations will attract scrutiny from auditors and the Commonwealth.

6. Tiny versus large entries in the same program. The “Essential vaccines” line lists very small amounts for most jurisdictions (for example NSW $456.49; VIC $107.11; TAS $53.84) but $444,038.35 for NT (Schedule 1). The presence of these minute figures alongside larger sums suggests a specific allocation logic not explained in the instrument; advisers should confirm the basis for these allocations with the responsible Commonwealth agency to prevent misapplication.

7. Duplicate table blocks. The document reproduces the Schedule 1 table more than once. While the numbers are consistent, duplication can cause confusion in drafting or archival contexts. Practitioners should cross‑check the final totals row which shows the aggregate payment amount of $333,947,612.27 and use that figure as authoritative for accounting purposes.

8. No payment mechanics. The instrument tells who gets paid and for what purpose, but does not specify payment method, timing beyond the 9 October 2017 label, or cash management processes. Treasury and State finance directors will need to coordinate the payment mechanics.

9. Lack of enforcement and audit clauses. The determination contains no explicit enforcement provisions or audit regimes. If a practitioner needs to understand recoupment, suspension, or remedial steps for misuse of funds, the instrument is not the correct source; they must look to other intergovernmental agreements, administrative guidelines or appropriation law for those mechanisms.

10. Classification and internal accounting risk. The program labels in Schedule 1 are high level and may not map neatly to State internal classifications. States must determine how to code the receipts to assist auditability and to ensure funds are allocated to matching projects. Failure to do so can complicate compliance reporting and external audit.

11. Timing and fiscal year effects. The commencement date (4 October 2017) and the payment date indicated in the schedule (9 October 2017) mean funds fall at the start of the Commonwealth and State fiscal year. That timing can have cash management and budget‑paper presentation impacts that need early coordination.

12. No express rights for third parties. Service providers or beneficiaries do not acquire enforceable legal rights to Commonwealth funding through this instrument; funds are paid to States who then administer programs. Contractors should therefore treat payment expectations as at the State’s discretion subject to any State contractual commitments, not as direct Commonwealth entitlements.

In short, the key “gotchas” arise from the instrument’s narrow allocative focus combined with the absence of detailed operational, conditionality and enforcement text; practitioners need to locate the ancillary instruments and administrative arrangements that operationalise the schedule.

For States and their program agencies

1. Record receipt and reconcile to Schedule 1: When funds are paid on the occasion indicated (Schedule 1 caption: “for payment on 9 October 2017”), State finance teams should immediately reconcile cash receipts against the schedule entries and the total shown ($333,947,612.27) and the per‑jurisdiction total recorded in the schedule (for example NSW $152,014,149.49). Maintain an auditable reconciliation showing the date of receipt, the amount, the Schedule 1 line item code and the internal ledger code.

2. Establish project mapping and internal coding: Map each Schedule 1 line item to a State project or program budget line. Because the schedule provides high‑level labels (for example “Specialist disability services”, “Investment Road”, “Homelessness”), allocate the funds to the appropriate State agency and internal project numbers so that the expenditure traceably matches programme intent described in the schedule. Create a ledger coding guide that ties each schedule line to a project manager and a unique chart of accounts code.

3. Internal governance and control: Apply standard governance controls for grant receipt and expenditure: (a) approve project plans; (b) require business cases or project briefs where capital or structural investment is involved (e.g. infrastructure projects); (c) institute procurement controls in accordance with State procurement rules; (d) set up regular internal reporting and variance explanations for program managers to ensure funds are used for the declared purposes in clause 4 and Schedule 1.

4. Audit trail and recordkeeping: Maintain documentation showing how funds were applied to the specified outputs or projects. Although the determination itself does not specify reporting, States should assume that auditors, both internal and external, will want to verify appropriate application of funds. Retain contracts, invoices, approvals, minutes and project progress reports linking expenditure to the Schedule 1 line item.

5. Seek clarity on missing operational terms: Because the instrument does not include detailed conditions, seek from the Commonwealth any supplemental documentation, project agreements, or intergovernmental arrangements that describe reporting expectations, performance milestones, contingency triggers (notably for contingent payments such as “Natural disaster relief”), or audit access rights. Obtain written confirmation of any additional terms that the Commonwealth expects to apply to these payments.

6. Manage contingencies and large single‑item inflows: For large concentrated inflows (for example NSW’s natural disaster relief amount), create a separate project account, tighten approvals, and consider risk management plans to ensure rapid disbursement with controls. Document the contingency that gave rise to the payment and any requirements for the use or reporting of those funds.

For Commonwealth administrators (practical steps)

1. Confirm payment mechanics and communications: Ensure that the finance unit coordinates bank transfer mechanics and informs State counterparts of the payment timings and account details. Provide a receiving advice that references Schedule 1 line items and the determination number to assist reconciliation.

2. Provide accompanying guidance: Where the determination does not specify conditions, releasing an accompanying payment advice or guidance note that sets out reporting expectations, contact points, and whether other agreements apply will reduce ambiguity and administrative friction.

For auditors and compliance officers

1. Use the determination as the primary receipt authority: For financial audit, record the instrument number, commencement date (4 October 2017), and the payment date as the formal source authorising the inflow. Test that the amounts received match Schedule 1 and verify whether State records show the same mapping to program outputs.

2. Test purpose alignment: Sample expenditures against the schedule line descriptions. Evidence that expenditure aligns with the programme labels (for example, health infrastructure expenditure against “Health Infrastructure Projects” entries) will be central to audit opinion.

3. Investigate contingent items: For contingent payments, verify documentation demonstrating that any contingency triggers were met,or that the Commonwealth intended the payment in the form taken. If contingencies are not documented, record findings and ask agencies to obtain written clarification from the Commonwealth.

For contractors and providers expecting State funding

1. Treat payment as a State entitlement: Do not rely on this determination to create a direct enforceable right against the Commonwealth for service delivery payments. Contracts for service delivery should be secured with the State and should include clear payment terms, timing and termination arrangements enforceable against the State, not against the Commonwealth.

2. Confirm State procurement steps: Ensure your contract with a State references the relevant program line and project code for auditability. Keep your own documentation to demonstrate how your work delivered outputs aligned with the schedule line.

Finally, where ambiguity exists between the schedule labels and operational practice, seek written clarifications from the relevant Commonwealth contact or the State’s finance department. Because the determination contains no penalty or enforcement provisions and is chiefly allocative, compliance in practice turns on sound project governance, clear internal accounting, and obtaining any supplemental agreements or guidance that detail reporting and conditions.