The Schedule rests on a small set of concrete concepts and terminology, each of which defines a discrete legal and administrative relationship.

• Charge: a specific monetary amount assigned to a named recipient for a particular service. The Schedule lists four charges, each with an amount (Schedule, Column 2). The concept functions as a cost-recovery or service-fee line item that the named person is "required to pay" (Schedule, Column 3). The Schedule does not use the terms "fee", "levy" or "tax"; it uses "charge" and links each charge to a specific service provision.

• Provision of statistical information: described as the service for which the ABS and RBA are charged. The Schedule's first two rows read "Provision to the ABS ... of the statistical information specified in Attachment 1" and "Provision to the RBA ... of the statistical information specified in Attachment 2" (Schedule, Column 1). The attachments list the individual "FORM_CDE" and "FORM_NAME" entries that constitute the delivered statistical information, for example ARF 720.1A Loans and Finance Leases (Standard) (Attachment 1 and Attachment 2).

• Development cost of the EFS collection system: a discrete recoverable development cost identified separately from the charge for provision of statistical information. The Schedule expressly describes these line items as "The development cost of the EFS collection system to be recovered for the 2021 - 22 financial year from the ABS" and from the RBA (Schedule, Column 1). The amounts are $45,521 (ABS) and $57,936 (RBA) (Schedule, Column 2).

• Invoice-triggered due date: payment is due "28 days after receipt of APRA’s invoice for the charge" for each item (Schedule, Column 4). The Schedule therefore makes APRA’s issuance of an invoice the trigger for the payment clock.

• Forms and collections: the Schedule's Attachments 1 and 2 are lists of form codes and names, referenced as the statistical information the ABS and RBA received. Those lists show standard and reduced variants of a number of forms (for example ARF 720.0A Standard and ARF 720.0B Reduced), separate ARF and SRF series entries, and differences between what was provided to ABS and what was provided to RBA (Attachments 1 and 2).

Together, these elements define a cost-recovery exercise for a single financial year tied to specified deliverables, with APRA in the role of creditor and ABS and RBA as payors. The Schedule itself does not define charging methodology, cost allocation rules beyond the four listed amounts, or mechanisms for adjusting charges after invoicing. It does not state the head of statutory power for APRA to impose such charges or the budgetary treatment by ABS and RBA of the amounts charged.

The Schedule identifies three named organisations directly: APRA (implicitly as the invoicing body), the ABS (the Australian Bureau of Statistics) and the RBA (Reserve Bank of Australia). The table's "Person required to pay the charge" column explicitly lists ABS as the payor for two entries and RBA as the payor for the other two entries (Schedule, Column 3). APRA is the entity issuing invoices, as the payment due date is expressed relative to "receipt of APRA's invoice" (Schedule, Column 4). No other statutory entities, private firms, financial institutions, or individual taxpayers are named as payors in the text provided.

Downstream practical effects will be felt by the finance, accounting, and budget teams within the ABS and the RBA because they are obliged to process and discharge the invoices once issued. The ABS’s nominal liability, per the Schedule, is $144,586 for the information service plus $45,521 for EFS development cost, totalling $190,107 for the 2021-22 year as set out on the face of the Schedule (Schedule, Column 2). The RBA’s nominal liability is $234,145 for the information service plus $57,936 for EFS development cost, totalling $292,081 (Schedule, Column 2). Those totals are arithmetic combinations of the listed amounts; the Schedule itself presents each item separately.

Entities that provided data or received the underlying statutory obligations to report to APRA (financial sector entities) are mentioned only indirectly. The Schedule's stated services are "statistical information ... concerning financial sector entities" (Schedule, Column 1), but those financial sector entities are not the payors under this Schedule. Therefore, the immediate legal-payment obligations fall on ABS and RBA, not on the financial sector entities that are the subject of the statistics.

Other affected functions include APRA's billing and accounts-receivable processes because the due date is invoice-contingent, and EFS collection system project accounting because the Schedule identifies recoverable development costs allocated to ABS and RBA. The Attachments identify the exact data products delivered to ABS and RBA; the operational teams that coordinate provision, acceptance, and verification of those datasets will be affected by any matching, reconciliation, or dispute processes tied to an APRA invoice. The Schedule does not state dispute or adjustment mechanisms, so those operational arrangements must be inferred as requiring internal process design by the named organisations.

The Schedule imposes payment duties and creates administrative rights around invoicing. The primary duties are payment obligations that arise on receipt of an APRA invoice. For each of the four listed items, the person required to pay the charge (ABS or RBA) must pay "28 days after receipt of APRA’s invoice for the charge" (Schedule, Column 4). That language establishes a clear duty to make payment within a fixed period after APRA initiates the billing process.

The Schedule confers the administrative right on APRA to issue an invoice that triggers the 28-day payment period. The Schedule does not grant any explicit rights of adjustment, rebate, challenge, or appeal against the invoice within the text shown. It also does not state interest charges for late payment, offset rights, or a process for disagreement about the calculation of the charge. Consequently, the Schedule creates a duty to pay in a specific timeframe and an invoice-triggered administrative right for APRA to require payment, but it is silent on procedural protections or remedies in the Schedule itself.

The Schedule further creates an implicit right to have specific data delivered, in that the charges are phrased as payment for "Provision to the ABS" and "Provision to the RBA" of statistical information, and the attachments specify the forms delivered (Schedule, Column 1; Attachment 1; Attachment 2). For example, Attachment 1 lists ARF 720.0A through ARF 748.0B items and SRF 720.0 series items as the statistical products provided to the ABS. Attachment 2 lists a partly overlapping but not identical set of ARF items provided to the RBA. The Schedule thus ties each charge to a distinct scope of deliverables recorded in the attachments, creating an expectation that payors are charged for those specified outputs.

The Schedule sets out no duty on APRA to provide documentation or supporting detail beyond the invoice itself. It does not mandate disclosure of the methodology used to calculate development-cost recovery or the apportionment between ABS and RBA. There is no stated duty for ABS or RBA to retain records or certify receipt, nor is there a right to deduct amounts from other APRA invoices. Those silences are functionally important because they leave the mechanics of dispute resolution and auditing to existing institutional arrangements or to other instruments not reproduced here.

The Schedule contains no express penalty clauses, interest provisions, or enforcement mechanisms. The only enforcement-related text is the payment timing: "28 days after receipt of APRA’s invoice for the charge" (Schedule, Column 4). The Schedule does not state the consequences of failure to pay within 28 days, nor does it prescribe interest on overdue amounts, debt recovery processes, suspension of services, or referral to courts or tribunals. It therefore establishes a payment obligation and an administrative due date but does not itself specify enforcement steps.

Because enforcement mechanisms are not addressed in the Schedule, any practical enforcement would depend on the surrounding legal or contractual framework under which APRA issues invoices and has collection rights. The Schedule does not identify that framework, nor does it reference a statute or other instrument that sets out penalties, remedies, or administrative recovery procedures. The absence of explicit enforcement terms means that APRA’s standard accounts-receivable and inter-governmental collection practices, and any relevant financial management rules that apply to Commonwealth agencies, will be the default practical avenues for addressing non-payment, unless other legislation or agreements (not included in the document) provide otherwise.

The Schedule also does not state whether payment disputes suspend the 28-day clock, whether interest accrues during disputes, or whether APRA has discretion to waive or amend amounts after invoicing. It does not describe whether a deduction from other Commonwealth payments to ABS or RBA is permissible as a self-help remedy. Those gaps are material for payors because they create uncertainty about the cost of paying late or contesting a charge.

In short, the Schedule sets out amounts and a due date but leaves enforcement and remedial detail outside its text. Any enforcement activity will be governed by other instruments, policies, or administrative practice that are not reproduced here.

The Schedule itself does not cite or reproduce any interaction clauses with statutes, financial management legislation, or appropriation rules. It therefore stands as an isolated table of charges and attachments that references APRA only in relation to invoicing. Because the Schedule is silent on statutory head powers, exemptions, or interaction with appropriation and budgetary frameworks, users must look elsewhere to determine legal interactions. The Schedule does not indicate whether these charges are recorded as intra-governmental transfers, appropriations, or external receipts for any of the named agencies.

A few concrete observations follow from the Schedule's silences and form. First, the persons required to pay are ABS and RBA, both Commonwealth agencies. That raises budgetary interaction questions in practice: ABS and RBA will need to accommodate the payments within their financial frameworks for 2021-22. The Schedule does not state whether the charges are to be funded from existing appropriations, special receipts, or by adjustment to allocated budgets. The Schedule also does not specify whether the charges are subject to the financial management and accountability regimes or special provisions that apply to Commonwealth agencies. Those interactions therefore must be determined by reference to other instruments or internal practices.

Second, the Schedule does not address privacy, confidentiality, or data-sharing legal limits. It records that statistical information "concerning financial sector entities" was provided to ABS and RBA (Schedule, Column 1) and enumerates the specific forms in Attachments 1 and 2. The Schedule does not state whether the data transfers were authorised by specific confidentiality waivers, statutory data-sharing provisions, or memoranda of understanding. Those legal interactions will be relevant to the agencies that provided or received the data, but they are not resolved in the text of the Schedule.

Third, there is no stated interaction with procurement or project accounting law regarding the EFS collection system development costs recovered from ABS and RBA. The Schedule identifies recoverable development costs for EFS but does not explain whether the underlying development was procured under Commonwealth procurement frameworks, nor how cost apportionment was decided. Consequently, the Schedule leaves open how those development costs integrate with procurement law, project reporting requirements, or audit obligations.

Finally, because the Schedule is expressly tied to the 2021-22 financial year, any interaction with multi-year funding, forward estimates, or subsequent budget adjustments is outside the Schedule’s text. Determining the legal effect of these charges on future-year budgets, or on appropriation limits, will require consulting the broader suite of budget and statutory documents that are not part of this Schedule.

The Schedule as provided contains no recorded amendment history. There are no textual markers indicating previous versions, amendment dates, or notes about substitution or repeal within the material supplied. The table is presented as a standalone Schedule of charges for the 2021-22 financial year, and the attachments list the specific forms delivered to ABS and RBA during that year (Attachments 1 and 2).

Because no amendment notes or versioning metadata appear in the text, one cannot, from the Schedule alone, determine whether these amounts replace prior charges, are part of a recurring charging schedule, or represent a one-off allocation for 2021-22. The Schedule does not indicate if the EFS development-cost recovery amounts are the result of a revised apportionment from earlier estimates or whether the APRA billing methodology changed for that year.

The attachments themselves contain lists of form codes and names without editorial marks, deletions, or annotations that would signal additions or removals relative to prior schedules. However, comparing Attachment 1 and Attachment 2 shows differences in scope between the datasets supplied to ABS and RBA. Those differences are internal to the Schedule for 2021-22 rather than evidence of an amendment history.

If a reader requires official amendment history, authorising instruments, or records of previous charging schedules, those will need to be obtained from the issuing authority or consolidated legislative and administrative records. The supplied Schedule does not perform that function.

The Schedule contains no reference to litigation, court decisions, or tribunal proceedings. There are no case citations, references to disputes, or notes indicating contested enforcement action in the text provided. The document therefore contains no internal record or summary of any litigation either challenging the charges or concerning their collection.

Because the Schedule does not include an account of litigation, any inquiry into disputes arising from these charges, contested invoices, or legal questions about APRA’s authority to charge the ABS and RBA must proceed by searching external sources such as court databases, agency records, or consolidated legislative history. The present instrument does not itself report or summarise legal proceedings.

Operationally, the absence of litigation history in the Schedule suggests that either there has been no recorded litigation directly relating to these specific charges, or that any litigation is not documented within the Schedule. For those assessing legal risk, the Schedule therefore provides no direct evidence about past disputes, and does not alter the underlying legal question of whether a payor might have arguable defences or rights of challenge. Those questions must be addressed by reference to other documents and, if necessary, by legal advice that considers statutory powers, contractual arrangements, and factual circumstances outside this Schedule.

Several practical and interpretative pitfalls are visible within the Schedule that users should note precisely because the Schedule is terse and leaves out procedural detail.

1. Invoice-triggered clock. Payment becomes due 28 days after "receipt of APRA’s invoice" (Schedule, Column 4). That places importance on how "receipt" is determined in practice. The Schedule does not specify the form of invoice, the delivery method, or whether electronic receipt counts. Payors should therefore treat the issuance and receipt of APRA's invoice as the operational event that starts the due-date countdown, and ensure internal processes are in place to capture the invoice date and comply with the 28-day term.

2. No stated consequences for late payment. The Schedule does not specify interest or penalties for late payment, nor does it specify whether APRA can suspend further services. That silence may create ambiguity about the cost of late payment and about enforcement. Parties should not assume leniency; they should instead seek clarification from APRA on default arrangements because the Schedule does not provide them.

3. Narrow temporal scope. The charges are expressly "during the 2021 - 22 financial year" and "to be recovered for the 2021 - 22 financial year" (Schedule, Column 1). The Schedule therefore does not on its face impose a recurrent or future-year levy. If a payor expects similar charges in subsequent years, that expectation is not established by this Schedule.

4. Differences between Attachments. The lists of forms provided to ABS and RBA overlap heavily but are not identical. For example, Attachment 1 lists ARF 720.5 "ABS/RBA Equity Securities Held" and SRF items (SRF 720.0, SRF 721.0, SRF722.0), whereas Attachment 2 includes ARF 723.0 "Margin Lending" which Attachment 1 does not list (Attachments 1 and 2). Those differences could matter for reconciliation between what was delivered and what was invoiced. Payors should verify the invoice against the respective attachment.

5. Ambiguity about who provided the data. The Schedule reads "Provision to the ABS ... of the statistical information specified in Attachment 1 concerning financial sector entities." The natural reading is that APRA provided the statistical information to ABS and RBA and is charging for that provision. The Schedule does not explicitly label the provider as APRA, but the invoicing relation implies it. Users should confirm the provider and the scope of deliverables against APRA records if reconciliation is required.

6. No methodology or supporting detail for development-cost apportionment. The Schedule records two EFS development-cost recovery amounts, but does not explain how those amounts were derived or apportioned between ABS and RBA. Payors needing to audit or challenge the development-cost component will need to request supporting documentation because the Schedule itself offers no breakdown.

7. Lack of cross-references to statutory authority. The Schedule does not cite the statutory authorisation or instrument under which charges are levied. For payors or auditors, establishing the legal basis for the charge requires consulting the relevant Acts or administrative instruments, not the Schedule alone.

8. Presentation quirks. The Schedule contains blank table cells and trailing lines in the attachments (for example, blank rows at the end). These formatting items do not affect the charges but can create confusion when extracting machine-readable data. Users should reconcile the amounts and attachments against the issuing agency's version.

9. Aggregation risk. The Schedule separates information-provision charges from development-cost recovery charges. An analyst or auditor aggregating APRA-related expenditures for 2021-22 should include both sets of items to avoid undercounting the total recoverable cost allocated to each payor.

10. No explicit dispute mechanism. There is no stated process for querying the invoice, suspending payment pending resolution, or disputing the quantity or quality of deliverables. That gap is operationally important because practical disagreement over dataset completeness or correctness must be handled outside the Schedule, and payors should document any communications with APRA promptly.

Those "gotchas" are concrete operational and interpretive issues generated by the Schedule’s brevity, absence of procedural detail, and the invoice-triggered due date.

The Schedule imposes limited but firm compliance steps. For ABS and RBA finance and compliance teams, the checklist below captures the immediate actions required and reasonable administrative steps derived from the Schedule’s content.

1. Budget recognition and allocation. Record the expected liabilities for 2021-22 as follows: ABS $144,586 (data provision) plus $45,521 (EFS development-cost recovery) and RBA $234,145 (data provision) plus $57,936 (EFS development-cost recovery) (Schedule, Column 2). Ensure internal accounting captures both items so that when APRA issues invoices the funds are available for payment within the 28-day term.

2. Invoice monitoring and date-stamping. Establish a process to accept and date-stamp APRA invoices on receipt. The payment clock runs for 28 days from the date of receipt of APRA's invoice (Schedule, Column 4). Clearly designate the mailbox or electronic receipt channel that constitutes "receipt" and document the internal workflow for invoice approval and payment.

3. Reconciliation against attachments. When an APRA invoice is received, reconcile the invoiced items against Attachment 1 (for ABS) or Attachment 2 (for RBA). Confirm that the statistical information billed corresponds to the forms and collections listed in the relevant attachment, and document any discrepancies. The attachments specify the exact forms (FORM_CDE and FORM_NAME) that are the basis for the information-charge line items.

4. Seek supporting documentation for development-cost recovery. Because the Schedule does not supply the calculation methodology for the EFS development-cost recovery amounts, request supporting schedules from APRA detailing how the recoverable development costs were computed and apportioned. Keep those records with finance files in case of audit or internal review.

5. Record-keeping and audit trail. Maintain a contemporaneous audit trail: copies of invoices, remittance advices, bank transfer confirmations, and any correspondence with APRA. The Schedule provides no dispute resolution or interest rules; a clear record will assist in any subsequent clarification or inquiry.

6. Clarify dispute processes before withholding payment. The Schedule imposes a strict 28-day payment term but does not address disputes. If a substantive dispute exists, contact APRA immediately to seek a documented stay or agreed resolution timeline. Withholding payment without an agreed arrangement risks becoming an accounts-receivable dispute; the Schedule does not provide a contractual or statutory mechanism to suspend the payment obligation.

7. Internal controls for multi-department coordination. Coordinate between data stewardship teams (who can confirm that the statistical deliverables were provided or accepted), legal counsel (to check any external statutory or policy constraints), and finance (to ensure prompt payment). The attachments identify specific datasets and will require technical confirmation before payment is processed.

8. Verify treatment in financial statements. Consult your agency’s accounting policy as to whether these charges are treated as appropriations, intragovernmental charges, or other accounting categories. The Schedule does not stipulate their financial-statement treatment.

9. Confirm electronic payment instructions. Ensure that APRA’s invoicing contains the correct remittance details and that payments are made to the bank account designated by APRA. The Schedule does not set the payment mechanism; rely on the invoice for payment instructions.

10. Escalation route. If an invoice appears materially inconsistent with the attachments or if supporting documents are not provided on request, escalate to your agency’s CFO or legal counsel for formal correspondence with APRA. Document the escalation steps and any agreed extensions to the payment deadline.

Following those steps will ensure compliance with the Schedule’s explicit duty,payment within 28 days of receipt of APRA’s invoice,while addressing the Schedule’s documented silences on methodology, dispute resolution, and enforcement.