The Schedule of charges uses a simple cost‑allocation model made up of the following concepts as presented in the instrument: services for which a charge is imposed, the amount of the charge, the person required to pay the charge, and the time when the charge must be paid. Each of those four columns is populated for each charge entry. The “service” entries are expressed in terms of provision to the ABS or to the RBA of particular statistical information, with the precise content of that information declared by reference to the two attachments. The Schedule thereby links a monetary charge to a defined package of statistical forms.

Two conceptually distinct categories of charge appear. Category A is for “provision … of the statistical information specified in Attachment 1 [or 2] concerning financial sector entities.” This ties the charge to APRA’s supply of data packages to those agencies for the stated financial year. Category B is for “the development cost of the EFS collection system during the 2020-2021 financial year to be recovered from” each agency. The instrument thus separates recurring data provision from a capital or development cost allocable to those recipients.

The attachments list the specific forms by code and descriptive name. Attachment 1 for the ABS includes ARF and SRF form codes, for example ARF 720.0A, ARF 721.0A and SRF 720.0. Attachment 2 for the RBA lists largely overlapping ARF forms, with some differences such as ARF 723.0 (Margin Lending) appearing for the RBA but not in Attachment 1, and SRF forms appearing only in Attachment 1. The attachment model therefore allows the Schedule to define the content of the charged service precisely by enumerating form codes.

Timing is a standalone concept in the Schedule: all sums are payable “28 days after receipt of APRA’s invoice for the charge.” The Schedule therefore delegates the initiation of the payment clock to APRA issuing an invoice and the recipient's receipt of it. No other billing frequency, instalment schedule or conditionality is specified.

The Schedule is confined to the 2020-21 financial year. The temporal scope functions as an explicit limiting concept in the instrument: the services and development costs charged are those “during the 2020 - 21 financial year.” The Schedule therefore operates as a year-specific cost reconciliation rather than an open-ended fee regime within the text provided.

The Schedule identifies three institutional actors by name in its charging rows: APRA, the ABS and the RBA. APRA is the de facto creditor, because the timing provision is triggered by “receipt of APRA’s invoice for the charge.” The two payers are the ABS and the RBA, each required to pay specific amounts. For 2020-21 the ABS is charged $184,846 for receipt of the ABS-specified statistical information and $29,801 for EFS development costs; the RBA is charged $292,190 for receipt of the RBA-specified statistical information and $37,928 for EFS development costs. Those figures make the ABS’s total liability under the Schedule $214,647 and the RBA’s total liability $330,118 for the single financial year covered.

The Schedule also affects the internal data exchanges and budgetary positions of those agencies. By fixing amounts payable to APRA for the listed data sets and development costs, the Schedule imposes a budgetary outflow on the ABS and on the RBA in the amounts stated. Because the list of forms in Attachments 1 and 2 differs, each recipient receives a distinct bundle of data types and schedules, which will affect the internal value proposition and accounting for the amount charged.

Although the services concern “statistical information … concerning financial sector entities,” the Schedule does not designate the financial sector entities themselves as payers or obligors under this instrument. The Schedule makes APRA’s counterparty the ABS or the RBA, not financial sector entities. To the extent those private entities supplied data to APRA or were the subject of the statistical collection, they are indirectly affected because the Schedule converts APRA’s provision of derived outputs or aggregated packages into costs charged to public agencies. Those indirect effects are not specified in the document.

The Schedule does not identify other actors such as appropriation ministers, accounting officers, or private contractors as payers or enforceable parties. It also does not provide a mechanism for third parties to dispute the charge. Therefore, the direct, named legal effect in the Schedule is constrained to APRA as the invoicing party and the ABS and RBA as the payers of the amounts stated.

The Schedule creates a clear, narrow duty: the named payers, ABS and RBA, must pay the specified amounts within 28 days after they receive APRA’s invoice. That is the only express payment obligation contained in the Schedule. The text therefore imposes four specific monetary obligations, each tied to a service description and a dollar figure. For the ABS the obligations are $184,846 and $29,801; for the RBA they are $292,190 and $37,928. The payment due date rule is identical across all four rows, with the payment window commencing on receipt of APRA’s invoice.

The Schedule implicitly confers APRA a right to invoice those amounts. The timing provision presumes APRA will issue an invoice, since payment is triggered by “receipt of APRA’s invoice for the charge.” The Schedule does not detail how invoices are to be delivered, how receipt is to be determined, or what invoices must contain. Those operational questions will determine when the 28‑day payment clock starts, but they are not answered within the Schedule itself.

The Schedule also specifies the content of the charged services via Attachments 1 and 2. That functions as a right on the recipients’ side to receive a defined package of statistical information for the 2020-21 year, and the reciprocal duty on their part to pay for that package. The attachments enumerate form codes and names, which act as the contractual description of the deliverable linked to each charge.

No other duties or rights are set out. The Schedule does not grant APRA any express ongoing charging power beyond the amounts listed; it does not confer any remedy or enforcement power to APRA in the event of non‑payment; it does not prescribe interest, late fees, or offsets; and it does not set dispute resolution or review processes. Those matters are therefore outside the Schedule, unless provided elsewhere in other instruments or legislation not contained in the text provided.

In practice the immediate rights and duties from the Schedule that recipients must internalise are: verify APRA’s invoice against the Attachments to confirm the services charged, trigger internal payment approvals to satisfy the 28‑day rule, and budget for the fixed amounts for the 2020-21 financial year. The Schedule itself encodes no procedural detail for invoicing, auditing, or challenge of the amounts billed.

The Schedule does not specify any penalties, enforcement mechanisms, interest on overdue amounts, or recovery procedure for non‑payment. Its four entries set the amounts due and the payment timing rule, but they contain no provision that prescribes consequences if the ABS or the RBA does not pay within 28 days of receipt of APRA’s invoice. The instrument therefore leaves enforcement unspecified.

Because the Schedule is silent on penalties and enforcement, any enforcement rights or remedies would have to arise from other instruments or from general legal remedies outside the Schedule text. The Schedule does not invoke or cross‑reference debt recovery provisions, late payment interest, set‑off rights, withholding mechanics, or administrative penalties. It similarly does not provide for suspension of services if payment is not made.

The practical consequence of that silence is material for both creditor and debtor. APRA is granted, in the Schedule, the right to invoice and the expectation of payment within a fixed window, but the Schedule does not embed a statutory sanction that will automatically apply for breach. Conversely, ABS and RBA have the duty to pay within 28 days but are not put on notice in this instrument of statutory interest or other administrative penalties for non‑compliance.

Where a payer disputes an invoice or wishes to delay payment, the Schedule leaves unresolved how the parties should proceed. The parties would need to rely on other contractual or statutory rules, or on negotiation, to determine practical enforcement. The Schedule’s lack of enforcement detail increases reliance on separate debt‑recovery processes or internal government accounting and appropriation procedures to address late or non‑payment. Any legal action arising from non‑payment would have to be brought under general law or any separate statutory charging regime, not under this Schedule itself, because the Schedule contains no enforcement clauses.

The Schedule is internally self-contained in terms of the charges it lists and the attachments that define the statistical information packages. It does not cite other Acts, regulations, or appropriation instruments in the text provided. That absence means the Schedule, as a standalone document, does not explicitly modify, override, or cross‑reference other statutory charging powers or budgeting rules within the text supplied. Any interaction with other laws therefore must be inferred from the institutional context rather than from explicit cross‑references in the Schedule.

Two likely legal interaction vectors arise from the Schedule’s structure. First, the Schedule imposes specific financial obligations on two public agencies, the ABS and the RBA. Those agencies will need to treat the amounts as payable in their financial accounts and appropriation processes, and that will interact with public sector financial management rules, internal appropriation procedures, and potentially Parliamentary appropriation requirements. The Schedule itself does not articulate budgetary authority, so compliance will require each agency to allocate funds or seek appropriation authorisation under whatever public finance rules govern those agencies. The Schedule does not instruct how appropriation compliance is to be achieved, it simply fixes the payable amounts and invoice timing.

Second, the Schedule refers to the “development cost of the EFS collection system” being allocated to the ABS and RBA. The term EFS is not defined in the Schedule, and the Schedule does not provide procurement, asset capitalisation or cost allocation rules. Those matters may be governed by other legislative or administrative instruments, but within the Schedule itself the interaction is limited to cost recovery in a particular year. Any capital accounting, depreciation, or treatment of development costs in the agencies’ financial statements would be handled under their applicable accounting standards and public sector accounting rules rather than this Schedule.

Because the Schedule lacks enforcement detail, interaction with statutory debt‑recovery procedures, commercial law remedies, or administrative disputes will require recourse to broader legal frameworks. The Schedule does not displace or amend any such framework within the text provided. Any party seeking to enforce or to resist enforcement of the amounts set out will need to rely on external legal authorities or contractual arrangements to determine remedies, offsets, or relief.

The Schedule as provided contains no history of amendments, versions, or legislative provenance within its text. It is presented as a single, finalised Schedule of charges for the 2020-21 financial year, without marginal notes, version dates, or references to earlier or later Schedules. There are no amendment clauses, saving provisions, or transitional arrangements contained in the instrument itself.

Because no amendment record is included, the Schedule does not reveal whether its four line items replaced prior charges, whether the dollar figures are increases or decreases from a prior year, or whether the attachments reflect an expansion or contraction of the data packages provided in other years. The absence of an amendment history in the Schedule means that users must treat the instrument as a standalone snapshot of cost allocation for the 2020-21 year.

If stakeholders require a historical comparison or a record of legislative changes, that information is not available in the text supplied and would need to be obtained from the issuing entity’s records, Parliamentary or administrative archives, or from other published instruments. The Schedule does not itself provide an amending instrument, or a schedule of prior amounts, so there is no in‑text method for tracking trend changes over time.

For present purposes the Schedule should be read as the operative statement of charges and attached service definitions for the 2020-21 financial year only. Any subsequent or prior amendments are not recorded in the document provided.

The Schedule contains no reference to any litigation, disputes, determinations, or judicial interpretation. The text does not mention prior legal proceedings involving APRA, ABS, or RBA with respect to these charges, nor does it identify any contested invoices, arbitration outcomes, or court decisions bearing on the amounts, the attachments, or the payment terms.

Because there is no litigation history recorded in the Schedule, there is no internal source in the instrument to indicate how disputes have been handled or adjudicated in practice. Any existing litigation or disputes arising from these charges would therefore need to be identified by consulting external records, case law databases, or agency dispute files, none of which are embedded in the Schedule.

The absence of litigation material in the Schedule also means it contains no precedent or interpretative guidance from courts or tribunals about the operative meaning of the invoice receipt rule, the sufficiency of the attachments as descriptive of the service delivered, or the legitimacy of APRA’s recovery of EFS development costs from the ABS and RBA. Any legal arguments about those matters would need to be developed from general legal principles and external authorities, because the Schedule supplies no litigation context or adjudicative history.

The Schedule’s brevity and specificity create a number of practical issues that recipients and administrators should note, because these are potential risk points arising directly from the text.

1. Invoice receipt ambiguity. Payment is due “28 days after receipt of APRA’s invoice for the charge.” The Schedule does not define “receipt.” There is no prescribed method of delivery, no deemed receipt rule and no specification of when the 28‑day period runs if the invoice is sent by mail, email, or delivered in person. That operational gap can produce disputes about whether payment deadlines were met.

2. No enforcement or late payment terms. The Schedule is silent on interest, penalties, suspension of service, or debt‑recovery mechanics. If a payer misses the 28‑day window, the Schedule does not itself create an automatic statutory consequence or a specified cure period. This leaves both APRA and the payer dependent on external recovery mechanisms or negotiation.

3. Single financial year scope. The Schedule explicitly limits the charges to services “during the 2020 - 21 financial year.” That confines the instrument’s legal and budgetary effect to that year. Agencies must not treat this Schedule as granting recurring charging authority unless they locate separate instruments for later years.

4. Differences between attachments. Attachment 1 and Attachment 2 are not identical. Attachment 1 (ABS) includes SRF form schedules (SRF 720.0, SRF 721.0, SRF722.0) which are not listed in Attachment 2. Attachment 2 (RBA) includes ARF 723.0 (Margin Lending) which is not in Attachment 1. ARF 720.5 (ABS/RBA Equity Securities Held) appears in Attachment 1 but not in Attachment 2. These differences mean the two payers are being charged different bundles of information, which can complicate internal validation of invoice content against the Schedule.

5. “Development cost” label without definition. The Schedule recovers “the development cost of the EFS collection system” from both agencies in specified amounts. It does not define EFS or specify the calculation method for the development cost. Without a breakdown or accompanying methodology, the recipients will need to rely on APRA’s supporting documentation or negotiation to confirm the proper allocation.

6. No procedural detail for invoice content. The Schedule presumes APRA will invoice, but provides no minimum content requirements for invoices that would enable swift reconciliation, such as form lists delivered, dates, or a narrative. That absence can slow payment and increase administrative friction.

7. Potential duplication or overlap. The two charges for data provision could include materially overlapping datasets where both ABS and RBA receive the same ARF forms. The Schedule does not comment on whether duplicate work is being charged twice, nor whether economies of scale or a joint delivery discount were considered.

8. Fixed lump sums. The charges are fixed dollar sums rather than unit‑rate or per‑form charges. That creates a binary compliance point: the payer either pays the fixed amount or disputes it. If the volume of forms or the cost of delivering them is contested, the Schedule provides no mechanism for variation or recalculation.

9. Accounting treatment questions. Because the Schedule includes development cost recovery, agencies must decide accounting treatment for those amounts. The Schedule does not instruct whether the development costs are capitalised or expensed for accounting purposes, leaving interpretation to standard accounting practices and public sector rules.

10. No record of amendment or review. There is no procedural timetable for review, audit or future recalculation in the Schedule. If agency practice requires periodic review of interagency charges, this document supplies no such mechanism.

These are not legal findings about validity, rather they are operational and interpretive risk points that follow from what the Schedule does and does not say.

The Schedule prescribes a narrow compliance pathway built around three practical tasks: verify, invoice and pay within the stated window. To comply with the instrument as written, the ABS and the RBA should take the following concrete steps, each grounded in the Schedule’s content.

1. Verify the invoice against the Schedule and the corresponding Attachment. When APRA issues an invoice, the payer should confirm that the invoice amount and description correspond to one of the four line items: (a) statistical information to ABS $184,846, (b) statistical information to RBA $292,190, (c) EFS development cost recoverable from ABS $29,801, or (d) EFS development cost recoverable from RBA $37,928. The payer should also cross‑check the attachment that purports to define the services invoiced: Attachment 1 for ABS, Attachment 2 for RBA. Because the attachments list specific form codes and names, reconciliation should confirm which form packages were delivered in 2020-21.

2. Establish invoice receipt rules and record the receipt date. The Schedule’s 28‑day payment window runs from “receipt of APRA’s invoice.” The payer must therefore adopt a consistent internal rule for determining the date of receipt, for example recording an APRA invoice number, the date received in the agency’s mailroom or accounts payable inbox, and the method of transmission. This will avoid later disputes about timeliness.

3. Configure internal approvals to meet the 28‑day deadline. The payer should ensure that financial approval workflows and appropriation checks can be completed inside the 28‑day clock. That may require pre‑allocating funds in the 2020-21 accounts, or advancing an internal approval where the invoice arrives near month‑end. Because the Schedule sets a fixed monetary liability, administrative delay will not change the obligation.

4. Seek documentary support if uncertain. For the EFS development cost entries the Schedule does not set out the basis for the calculations. Payers should request supporting documentation from APRA showing the cost breakdown for the EFS development work, dates, and any basis for apportionment. That documentation will assist internal accounting and audit sign‑off.

5. Treat the charge as a one‑off for 2020-21 unless otherwise notified. The instrument is explicitly framed for the 2020-21 financial year only. Absent a subsequent Schedule or an alternative charging instrument, recipients should not assume an ongoing series of identical charges in future years.

6. Document any disputes promptly. If a payer disputes an invoice amount, a delivery, or the characterization of the service charged, the payer should put the dispute in writing to APRA immediately upon receipt and record the facts and supporting documentation. The Schedule itself does not establish a dispute resolution mechanism, so contemporaneous documentation will be needed for negotiation or for any subsequent legal or administrative remedy.

7. Align accounting treatment with public sector rules. The Schedule contains development cost recoveries. Payers should consult their in‑house accounting guidance or the applicable public sector accounting standard to determine whether the transferred development cost is to be capitalised, expensed, or treated in another manner, and ensure their ledger entries reflect the chosen treatment.

8. Retain a record of the forms delivered. Because the attachments enumerate form codes, payers should retain copies of the actual data packages they received, ideally matched to the form codes in the attachments. That will support internal audit and external scrutiny if required.

Following these steps will implement the payment obligations the Schedule creates while addressing the operational lacunae the instrument does not itself fill. Where the Schedule is silent , on invoice content, deemed receipt, enforcement or the accounting basis for development costs , compliance will require administrative agreements, internal controls and documentary evidence to bridge the gaps.