The Schedule is built on a small set of operational concepts. Each concept is explicit in the table and attachments.

• Recoverable charge and invoicing trigger. Each row in the Schedule defines a recoverable charge in Column 2 and names the person required to pay in Column 3. Column 4 ties the timing of payment to receipt of an invoice from APRA, namely payment 28 days after APRA’s invoice is received. The Schedule therefore implements a creditor-debtor relationship where APRA is the creditor and the ABS or RBA is the debtor for the listed amounts.

• Scope of services as defined by attachments. The Schedule does not describe the statistical outputs in narrative form; instead it refers to Attachment 1 and Attachment 2 for the detailed list of forms that constitute "the statistical information" provided to each receiving agency during 2022-23. Attachment 1 lists a set of ARF and SRF form codes and names supplied to the ABS. Attachment 2 lists a partly overlapping but not identical set of ARF form codes and names supplied to the RBA. The attachments therefore constitute the operative catalogue of deliverables for the recoverable charges.

• System development and maintenance costs. Two items label the cost as "the development cost of the EFS collection system" to be recovered from ABS and RBA respectively. A separate item is the "maintenance and support costs of the data sharing APIs used by the RBA" to be recovered from the RBA. Those line items separate upfront development cost recovery from ongoing maintenance and support cost recovery and allocate them to the two agencies differently.

• Financial year specificity. Each charge is explicitly tied to the 2022-23 financial year. The Schedule thereby limits itself temporally to that year; it does not purport to create repeating annual charges or to set a multi-year cost-recovery framework.

• Agency-to-agency cost recovery. The Schedule concerns intergovernmental/intra‑Commonwealth financial flows: APRA recovers cost from ABS and RBA. It does not impose charges on private financial sector entities directly; instead it documents the amounts those two agencies must pay APRA for the statistical information and system costs provided.

• Fixed-dollar approach. The Schedule states precise dollar amounts for each listed charge (for example $188,424 and $311,977), rather than percentages, cost-allocation formulas or contingent recoveries. That yields immediate budget certainty for APRA and for the named payers, subject only to invoice timing.

Taken together, these concepts define a narrow administrative instrument: pre-determined, invoice-triggered inter-agency recoveries for a specified set of statistical outputs and system work during the 2022-23 financial year.

Primary parties named in the Schedule are APRA (the invoicing party), the ABS and the RBA (the payers). The Schedule directs payment obligations only to those named agencies. For the 2022-23 financial year, ABS is required to pay $188,424 for the statistical information listed in Attachment 1 and $45,521 as its share of EFS collection system development costs, with payments due 28 days after receipt of APRA’s invoice for each charge. The RBA is required to pay $311,977 for statistical information listed in Attachment 2, $57,936 as its share of EFS collection system development costs, and $86,293 for maintenance and support costs of data sharing APIs used by the RBA. Those RBA payments are also due 28 days after receipt of APRA’s invoice for each charge.

Indirectly affected parties are the staff and programs within ABS and RBA responsible for budgeting, accounts payable and statistical intake. Those internal units must process APRA invoices and allocate funds from their budgets to meet the 28-day payment requirement. APRA staff responsible for invoicing and delivering the specified forms are also operationally affected because the Schedule fixes APRA’s recoverable amounts and sets the payment trigger.

Financial sector entities appear only as the subject matter of the statistical information. The Attachments list form codes such as ARF 720.0A and ARF 743.0 which describe types of financial statistics about loans, deposits, derivatives, housing finance and other categories. Those private entities that supply data to APRA (if any) are not identified as payers or recipients under this Schedule. The Schedule therefore does not impose any new direct financial obligation on private financial sector participants.

Budgetary and public‑finance stakeholders are also affected in a practical sense. ABS and RBA will need to accommodate these recoveries within their 2022-23 financial statements and cashflow management. That may influence which items appear in their departmental financial accounts and require internal budget reallocation. Public accounts staff, auditors and parliamentary appropriation monitors are therefore likely to interact with the Schedule by way of reflecting the transactions in government financial reporting.

Because the Schedule fixes amounts and payment timing, it also affects short-term cash positions for ABS and RBA. The Schedule does not allocate any enforcement rights beyond APRA issuing an invoice and a 28‑day payment deadline. No private party rights are created by the Schedule; its legal effect is confined to the named Commonwealth agencies and the records that attach to the listed statistical deliverables.

The Schedule imposes a concise set of duties and exposes a small set of rights. They are explicit in the tables.

Duties:

• Payment duty. The ABS and RBA are required to pay the amounts listed in Column 2 of the Schedule, as assigned in Column 3. For example, ABS must pay $188,424 for the statistical information item listed in the first row and $45,521 for EFS development cost recovery. RBA must pay $311,977 for its listed statistical information item, $57,936 for EFS development cost recovery, and $86,293 for maintenance and support of data sharing APIs. Each of those payment duties is tied to the receipt of APRA’s invoice and is due 28 days after that receipt. The Schedule therefore creates a clear payable obligation for the named Commonwealth agencies.

• Receipt and acceptance duty by APRA. APRA, by issuing invoices and providing the specified statistical products and system work, carries an implied duty to produce the deliverables listed in Attachment 1 and Attachment 2. The Schedule references those attachments as the statistical information "provided" to ABS and RBA during the 2022-23 financial year. Although delivery mechanisms are not detailed, APRA’s performance is the basis for its right to invoice.

Rights:

• APRA’s invoicing and recovery right. APRA has the right to recover the specific dollar amounts listed by issuing an invoice that triggers payment within 28 days by the named agency. The Schedule operates as the authorising instrument for APRA to invoice those amounts to ABS and RBA for the 2022-23 year.

• Recipient’s receipt of statistical information. ABS and RBA have the right to receive the specified statistical forms enumerated in Attachments 1 and 2 respectively. The Schedule identifies those forms as the statistical information provided during the financial year. That is the quid pro quo for the recoverable charges.

Procedural mechanics:

• The payment timing is strictly invoice-based; the Schedule directs each payer to pay "28 days after receipt of APRA’s invoice for the charge." The Schedule therefore places procedural priority on APRA issuing an invoice, rather than, for example, setting a statutory due date or monthly instalment schedule.

What the Schedule does not specify and therefore does not create:

• It does not set interest on late payments, dispute resolution processes, offsets, or credit notes. The Schedule contains no penalty, enforcement mechanism or remediation route for non-payment beyond the invoice-and-payment linkage. Those matters are not addressed in the text.

• It does not grant private entities any right to challenge the recoverable amounts or the forms listed. The Schedule contracts only among Commonwealth agencies.

In short, the Schedule confers on APRA a defined right to be paid set sums and imposes on ABS and RBA a corresponding duty to pay those sums within 28 days of APRA issuing an invoice. It also fixes the content of the statistical deliverables by reference to the attachments.

The Schedule contains no express penalties, sanctions, or statutory enforcement provisions for non-payment. The table's Column 4 sets the payment trigger and due date, "28 days after receipt of APRA’s invoice for the charge." Beyond that due-date prescription, the Schedule does not specify remedies for late payment, interest on overdue amounts, methods of dispute resolution, offsets, or administrative consequences for failure to pay.

Given the absence of penalty clauses, the Schedule must be read as an authorising instrument for APRA to invoice the named agencies for the listed amounts, leaving enforcement to the normal financial-management and inter-agency processes that apply to Commonwealth agencies. Those processes are not described in this Schedule. The Schedule therefore does not create additional statutory enforcement powers for APRA such as garnishee, lien, or statutory debt-collection powers in the event of non-payment.

Practically, non-payment by ABS or RBA would raise standard public finance questions about appropriation, internal accounts payable, and inter-agency debt management. Those mechanisms are external to this Schedule. Similarly, commercial recovery mechanisms that private creditors might use are not mentioned. The Schedule does not convert the sums into recoverable debts with additional statutory penalties; it only records amounts payable and a payment timing requirement.

Readers should therefore note the following concrete points from the Schedule itself:

• Payment timing is precise. The payer must pay "28 days after receipt of APRA’s invoice for the charge." The Schedule is explicit about timing but silent about consequences for late or disputed payments.

• APRA’s recovery right is procedural. APRA’s right to recover the amounts is exercised by issuing an invoice. The Schedule does not set a fixed payment date independent of APRA invoicing.

• No penalties or interest. The Schedule contains no lines or text that impose penalty rates, late fees, compounding interest, or other statutory enforcement consequences for the payer.

Because the Schedule is silent on enforcement, any enforcement or remedial action in the event of dispute or non-payment would have to rely on either separate inter-agency agreements, administrative remedies, or the general legal framework governing financial management of Commonwealth agencies. Those frameworks are not set out in this Schedule.

The Schedule itself is a narrow administrative instrument and does not cite other statutes, regulations, or specific legal frameworks. Within the four corners of the Schedule, there is no express cross-reference to other statutory provisions, appropriation law, financial-management legislation, or data-sharing statutes. The text therefore neither amends nor disapplies other laws on its face.

Nevertheless, the Schedule operates in an existing intergovernmental and legal environment. The Schedule makes APRA the invoicing party and ABS and RBA the payers for specified services and system costs provided during 2022-23. Those transactions will interact operationally with the legal and financial-management regimes that govern Commonwealth agencies, including appropriation rules, departmental financial statements, and inter-agency charging policies. The Schedule does not, however, state how those interactions are to be resolved or implemented. In particular:

• Appropriation and budget treatment. The Schedule requires ABS and RBA to pay set amounts. How those payments are treated under appropriation law is not addressed in the Schedule. The payer agencies will need to identify the appropriation head, program or internal budget line that funds each payment and reflect the transaction in their financial accounts in accordance with governing public‑sector accounting standards and appropriation rules. The Schedule does not specify an appropriation source.

• Data‑sharing and confidentiality regimes. The Schedule specifies the statistical forms provided to ABS and RBA. It does not set out or modify legal obligations regarding confidentiality, handling, or publication of the statistical information. Any obligations that arise from data-sharing, privacy or confidentiality law are not described in the Schedule.

• Contractual and procurement frameworks. The Schedule includes development costs for the EFS collection system and maintenance and support of data-sharing APIs. It does not indicate procurement or contractual arrangements used to procure those services, nor does it state whether the development and maintenance were carried out by APRA internal teams or third-party contractors. Procurement and contracting rules that normally apply to government IT development and support would remain relevant but are not referenced.

• Inter-agency charging policies. The Schedule implements charges between agencies for specified goods and services but does not identify whether the recovery approach is consistent with any broader Commonwealth charging policy or cost-recovery guidelines. There is no text addressing cost-allocation methodology, competitive neutrality, or business-case compliance.

Because the Schedule is silent on these interaction points, the operational interplay with other laws and policies will depend on the agencies’ internal application of general Commonwealth financial-management rules, procurement law, data-handling statutes and any separate memoranda of understanding among the agencies. The Schedule itself neither creates nor limits those other legal frameworks; it records a set of amounts payable and the deliverables that underpin them for the 2022-23 financial year.

The Schedule as provided contains no internal amendment history, version identifiers, commencement dates or references to amending instruments. It is expressed as a standalone schedule of charges for the 2022-23 financial year and includes the relevant dollar amounts and attachments for that year. There are no marked additions, deletions, marginal notes, or footnotes indicating earlier versions or subsequent amendments.

Because the document does not include any historical notes or legislative references, the Schedule does not itself disclose whether it replaced an earlier schedule or has been superseded. The reader must therefore treat the Schedule as an isolated statement of recoverable charges for the specified financial year. Any prior or subsequent revisions, if they exist, are not recorded in this text.

Where an analyst or practitioner requires an explicit amendment trail, that trail will need to be sought in the instrument that enacts the Schedule (for example the parent legislation or an amending instrument), or in parliamentary records and legislative registers. This Schedule contains no such meta-data. The Schedule does not provide commencement dates beyond the temporal qualifier "during the 2022 - 23 financial year" and hence does not itself indicate when an obligation crystallises beyond being tied to APRA invoicing in that financial year.

In short, the Schedule lists recoverable amounts and attachments for 2022-23 and contains no explicit amendment history or version control information. Any inquiry about past or future schedules or whether the same items recur in other financial years will need to consult the parent legislative or administrative instruments that authorised this Schedule or subsequent schedules published by the relevant agencies.

The Schedule contains no reference to litigation, legal proceedings, or judicial interpretation. It does not cite any cases, does not include any contested determinations, and does not record any disputes between APRA, ABS or RBA regarding the amounts or the deliverables enumerated. There is therefore no litigation history contained within this Schedule.

Because the Schedule is an administrative charging instrument limited to intra‑Commonwealth recoveries and does not create private rights or impose obligations on private parties, it is unsurprising that the Schedule does not foreshadow case law. Any litigation that might arise from non-payment, disputes about the deliverables, misunderstandings about invoice timing, or disagreements about the scope of the statistical information would have to be brought in separate proceedings. The Schedule itself does not identify dispute resolution mechanisms, arbitration clauses, or administrative appeal routes.

Practitioners seeking litigation history or precedent relevant to these charges must therefore look outside this text to other sources: administrative decisions, inter-agency agreements, or court records. Those sources are not present in the Schedule and are not summarised here.

The Schedule is compact, but it contains operational details and asymmetries that merit close attention. The following are concrete items drawn directly from the text that a practitioner should note.

Payment trigger and timing:

• Every listed charge is payable 28 days after receipt of APRA’s invoice. The Schedule conditions payment on APRA issuing an invoice rather than on a fixed calendar date. That means budget managers must watch for invoice receipt rather than relying on a statutory date such as the end of a quarter. Missing an APRA invoice could affect cashflow planning.

Agency-specific allocations:

• ABS and RBA pay different items and different totals. ABS pays two items totalling $233,945 ($188,424 + $45,521). The RBA pays three items totalling $456,206 ($311,977 + $57,936 + $86,293). Practitioners must not assume symmetry. The RBA is charged both the larger statistical-information recovery and the API maintenance and support costs, which the ABS is not charged.

Scope differences in deliverables:

• Attachments 1 and 2 are not identical. Attachment 1 (ABS) includes form codes not present in Attachment 2 (RBA), for example ARF 720.5 "ABS/RBA Equity Securities Held" and several SRF forms (SRF 720.0, SRF 721.0, SRF722.0). Attachment 2 (RBA) includes ARF 723.0 "ABS/RBA Margin Lending" which Attachment 1 does not list. These divergences mean the statistical information provided to each agency differs. If a payer questions the pertinence of a particular line item, the attachments should be consulted to determine the precise deliverables underlying the charge.

Precise dollar amounts:

• The Schedule fixes amounts to the dollar. There is no rounding clause, no contingent adjustments and no clause allowing APRA to vary amounts retrospectively. Practically, that creates clarity but also rigidity. If an error is discovered post-issuance, the Schedule provides no mechanism within its text for correction.

No penalties, no dispute process:

• The Schedule contains no late-payment interest or penalty clause, nor any formal dispute-resolution clause. If a payer wishes to withhold payment because of a dispute about deliverables, the Schedule does not specify the consequences or an administrative pathway. That may give rise to procedural friction between agencies unless a separate MOU exists.

Invoice-based liability crystallisation:

• Because the payment obligation is tied to APRA’s invoice, the timing of APRA’s invoicing will determine when the payer must make the payment. Payers cannot treat the sums as payable until APRA invoices, but once invoiced the 28-day countdown applies.

Single-year scope:

• The Schedule is explicitly for the 2022-23 financial year. Practitioners should not assume these charges automatically recur in subsequent years. Any future-year cost recovery would need separate documentation.

Statistical content labels:

• The attachments use coded form identifiers (ARF and SRF codes) and short form names. Users unfamiliar with those codes should not assume the content or granularity of the forms beyond the short names listed. For operational clarity, agencies should map each ARF/SRF code to the internal product specification to verify what was delivered.

Separation of development and maintenance costs:

• The Schedule separates EFS system development costs and API maintenance/support costs, and it allocates them asymmetrically. Development costs are recoverable from both ABS and RBA in different amounts. API maintenance and support costs are recoverable only from the RBA. This allocation can matter for future accounting and cost-recovery debates about shared infrastructure.

No mention of procurement or contractors:

• The Schedule notes development and maintenance costs but does not say whether those costs were incurred internally by APRA or through third-party contracts. That lack of specification can complicate audit trail reviews if an agency wants to trace the underlying invoices.

In sum, the Schedule is precise on amounts, payers and deliverable codes, but silent on corrections, disputes and enforcement. Practitioners should verify invoice receipt timing, the exact deliverable mappings for each ARF/SRF code, and the agency budget lines to be charged. They should also check for any separate inter-agency agreements that set out dispute and enforcement procedures not included in this Schedule.

Compliance under this Schedule is procedural and straightforward, because the obligations are limited and explicit. The following steps reflect the obligations and operational risks set out in the Schedule.

1. Monitor for APRA invoices

• APRA’s invoice is the payment trigger. ABS and RBA must implement accounts-payable processes to ensure prompt receipt, logging and actioning of any invoice from APRA that relates to the Schedule. Because the due date is calculated from invoice receipt, time-stamping and records of receipt are essential to avoid late payment.

2. Verify invoice scope against the Schedule

• Upon receiving an invoice, the payer should confirm that the invoice amount and the description correspond exactly with the Schedule line items. For statistical information recoveries, confirm which attachment (Attachment 1 or Attachment 2) applies and that the deliverables on the invoice map to the ARF/SRF codes listed therein. For EFS development and API maintenance costs, verify that amounts match $45,521 and $57,936 for development cost recovery allocated to ABS and RBA respectively, and $86,293 for RBA API maintenance and support.

3. Allocate appropriation / budget lines

• Identify and document the appropriation head or internal budget line to be charged. Because the Schedule does not designate an appropriation source, each payer must ensure it has available funds under its appropriation or internal budget to meet the payment within 28 days.

4. Process payment within 28 days

• Ensure systems are in place to effect payment no later than 28 days after APRA’s invoice receipt. Maintain sufficient cashflow to avoid oversights. Retain records showing invoice receipt date, approval, and payment execution to evidence compliance with the Schedule’s timing requirement.

5. Maintain audit trail and product mapping

• Keep a record that maps each ARF/SRF code listed in the relevant attachment to the actual statistical product delivered. This will support internal audit queries and any discussion about whether the deliverable was supplied as invoiced. For the EFS system development and API maintenance items, retain any supporting documentation that traces the costs back to the work performed, such as project deliverables, change requests or maintenance logs.

6. If a dispute arises, document and escalate

• The Schedule does not set out a dispute mechanism. If the payer considers that the invoice is incorrect, maintain contemporaneous written records of the dispute and promptly raise the issue with APRA’s invoicing contact. While the Schedule does not specify remedies, documentation will assist in any separate administrative or inter-agency process that addresses the dispute.

7. Verify deliverables differ by recipient

• Do not assume that the statistical information provided to ABS and RBA is identical. Before disputing or accepting invoices, confirm which ARF/SRF codes were provided to the payer by APRA during 2022-23 as listed in Attachments 1 and 2. For example, if the RBA receives an invoice for margin-lending data it did not receive, the RBA should cross-check with Attachment 2 which lists ARF 723.0 "ABS/RBA Margin Lending."

8. Coordinate with internal stakeholders

• Coordinate with statistics, IT and finance teams to confirm that the development and maintenance costs charged align with internal expectations and accounting treatment. For API maintenance charges recoverable only from RBA, the RBA’s IT procurement and operations teams should confirm that the APIs in question were used and request supporting maintenance reports if needed.

9. Keep a record of any corrective actions

• If an invoice requires adjustment, document any credit note, revised invoice, or officer approval to withhold or delay payment. Because the Schedule is silent on corrections, such records will be the primary basis for resolving any subsequent question about compliance.

10. Seek wider governance documents if needed

• If uncertainty remains about enforcement, dispute resolution, or the origin of the costs, request any underlying memoranda of understanding, service-level agreements or inter-agency cost-recovery policies that relate to the items in this Schedule. These documents, if they exist, will govern the practical resolution of questions not addressed by the Schedule itself.

Following these steps will implement the duties the Schedule imposes: receipt of APRA invoices, verification against the Schedule and attachments, budget allocation, and payment within the invoice-based 28-day timeframe. The Schedule does not create further procedural steps; prudent agencies will nevertheless maintain audit and product mapping documentation to reduce the risk of later contention.