The schedule operates through a small set of concepts and mappings that determine who pays, what they pay for, and when payment must be made.

• Services and recipients. Each charge line pairs a defined service with a named recipient: "Provision to the ABS ... of the statistical information specified in Attachment 1" (first line) and "Provision to the RBA ... of the statistical information specified in Attachment 2" (second line). Two additional lines expressly recover EFS collection system development costs from each of ABS and RBA; a final line recovers maintenance and support costs of data sharing APIs used by the RBA. The phrasing in each line identifies what is being recovered and designates the recipient who is charged. The schedule therefore maps services to the financial obligations of named government entities.

• Fixed monetary amounts for a single financial year. Each item has a single dollar figure stated in Column 2 described as the "Amount of the charge." The amounts are specified for the 2023-24 financial year only; there are no multi-year schedules or indexing mechanisms included. The charges are therefore nominal, single-year recoveries rather than ongoing levies.

• Invoicing and payment timing. Column 4 uniformly states that the charge is payable "28 days after receipt of APRA’s invoice for the charge." The schedule thus sets APRA as the party that issues the invoice and fixes a 28-day payment window from the date the invoice is received.

• Attachment-based specification of data content. The schedule does not attempt to describe the content of the "statistical information" in free text. Instead, it incorporates that content by reference to Attachment 1 (for ABS) and Attachment 2 (for RBA). Attachments list form codes (for example ARF 720.0A, ARF 721.0A) and form names (for example "ABS/RBA Statement of Financial Position (Standard)") which specify the exact reporting series to be provided during the covered financial year.

• Distinct form sets for each recipient. Attachment 1 and Attachment 2 are largely overlapping but contain differences. Attachment 1 includes some SRF codes (for example SRF 720.0, SRF 721.0, SRF722.0) that are labelled "ABS" forms; Attachment 2 includes ARF 723.0 "ABS/RBA Margin Lending" which is present in the RBA list but not the ABS list. The schedule therefore distinguishes the precise outputs to be delivered to each recipient.

• Cost categories. The schedule distinguishes between (a) the direct provision of statistical outputs and (b) recoveries for technology development and ongoing maintenance/support of data exchange infrastructure (EFS collection system development costs and data sharing APIs). Those line items indicate that both information products and enabling IT services are subject to recovery under the schedule.

Taken together, those concepts implement an inter-agency cost-recovery mechanism for a limited set of statistical and IT services in 2023-24, with APRA as the invoice issuer and ABS/RBA as payers, using attachments to specify the exact data forms covered.

This schedule expressly affects three named parties within the instrument: APRA (by implication, because APRA issues the invoice), the Australian Bureau of Statistics (ABS) and the Reserve Bank of Australia (RBA). The schedule sets financial obligations on ABS and RBA and sets APRA as the entity that will invoice them for the specified amounts.

• ABS. The schedule requires ABS to pay two specified amounts: $292,098 for the provision to ABS of the statistical information specified in Attachment 1, and $45,521 as ABS's share of the development cost of the EFS collection system for 2023-24. In aggregate the ABS is charged $337,619 for 2023-24 under the five-line schedule (sum of the two ABS lines).

• RBA. The schedule requires the RBA to pay three specified amounts: $495,217 for provision to the RBA of the statistical information specified in Attachment 2; $57,936 as the RBA's share of the EFS collection system development costs for 2023-24; and $120,720 to recover the maintenance and support costs of the data sharing APIs used by the RBA during 2023-24. In aggregate the RBA is charged $673,873 for 2023-24 under the five-line schedule (sum of the three RBA lines).

• APRA. While the schedule lists APRA only in the context of "APRA’s invoice for the charge," that wording makes APRA the invoicing/charging agent: APRA will issue invoices to ABS and RBA and thereby seeks payment of the listed amounts. The schedule does not include express language creating additional obligations on APRA beyond issuing invoices; nevertheless, APRA is the operational counterparty for collection.

• Downstream or third parties. The instrument does not list any private entities, regulated entities, or other Commonwealth agencies as subject to charges under this schedule. The services described are the "provision" of statistical information to ABS and RBA and the recovery of specified development and maintenance costs from ABS/RBA. No third-party compliance duties, penalties, or reporting obligations are stated in the schedule.

The explicit consequence is that ABS and RBA are budgetary payers for the enumerated services in 2023-24. The schedule does not state whether those charges are sourced from existing inter-agency appropriations, require new appropriation action, or are to be met from the recipients' operating budgets; it simply identifies the payer and the invoice/payment timing. The schedule thereby imposes a concrete, numerically-specified cash obligation on ABS and RBA for the 2023-24 year.

The instrument creates specific monetary payment duties and an invoicing right, and defines the content basis for the recoverable services. It does not create broader operational duties, enforcement mechanisms or performance standards beyond what is set out in the schedule and attachments.

• Duty to pay. For each charge line the "Person required to pay the charge" is explicitly named in Column 3. The ABS is required to pay $292,098 for the statistical information listed in Attachment 1 and $45,521 as its share of EFS collection system development costs. The RBA is required to pay $495,217 for the statistical information listed in Attachment 2, $57,936 for its share of the EFS collection system development costs, and $120,720 for maintenance and support of data sharing APIs used by the RBA. Payment timing is uniform: each charge is due "28 days after receipt of APRA’s invoice for the charge." The schedule therefore imposes an express, time-bound payment duty on the named recipient entities.

• APRA’s invoicing right. The schedule repeatedly references "APRA’s invoice for the charge" as the trigger for the 28‑day payment obligation. Implicitly, APRA has the procedural right to issue invoices to collect the stated amounts. The schedule does not specify invoicing frequency (single invoice per charge line or consolidated invoice), other invoicing particulars (GST treatment, remittance instructions), or dispute resolution procedures tied to invoicing.

• Specification of deliverables. The schedule ties the recoverable amounts for statistical information to the forms listed in the relevant attachment: Attachment 1 for ABS, Attachment 2 for RBA. The attachments therefore operate as the content specification for what is being provided. The schedule does not include service-level descriptions, delivery dates for each form, or quality standards; it confines itself to form names and codes as the definitional boundary of the service.

• No express rights to withhold payment or dispute. The schedule sets a payment period linked to APRA’s invoice but does not contain wording that explicitly permits the payer to withhold or dispute the invoice, nor does it set a mechanism for resolving disputes over amounts or the content of deliverables. The absence of such procedural protections in the text supplied means that, within the schedule itself, the payer’s duty is time‑based and the invoice is the relevant charging instrument.

• No operational duties on ABS/RBA to produce or deliver data. The schedule describes "provision to the ABS ... of the statistical information" and "provision to the RBA ..."; it does not impose duties on ABS or RBA to provide data to APRA or to other parties. The only duties specified relate to payment; the deliverables are specified by reference to attachments.

• Form-level content as contractual specification. The attachments list numerous ARF and SRF form codes and names (for example ARF 720.0A "ABS/RBA Statement of Financial Position (Standard)" in both attachments, ARF 723.0 "ABS/RBA Margin Lending" in Attachment 2 only). For practical compliance, the attachments define the scope of the deliverable service for which the payer is charged.

In short, the core duties are: APRA may issue invoices for the listed sums; ABS and RBA must pay those invoices within 28 days of receipt. The schedule’s rights and duties are narrowly financial and informational: it fixes what is recoverable, who pays, how much, and when payment is due.

The schedule itself contains no express penalties, enforcement mechanisms, interest provisions for late payment, administrative sanctions, or references to recovery remedies. The only procedural enforcement-like detail is the payment timing: each charge is "to be paid 28 days after receipt of APRA’s invoice for the charge." From the text supplied, the following points are evident and relevant for compliance risk assessment:

• No statutory penalty clauses in the schedule. The schedule does not set out consequences for non-payment, no late-payment interest, and no specified offset or withholding rights for the payer. There are no references within the schedule to suspension of service, referral to debt-recovery processes, or escalation protocols.

• Invoice as the trigger. The schedule makes APRA’s issuance of an invoice the single operational trigger for the payer’s 28‑day duty to pay. Any enforcement action (if available under other law or contractual arrangements) would presumably follow from a failure to pay an invoice, but the schedule itself does not describe those downstream steps.

• Implication of external enforcement mechanisms not in the text. Because the schedule is silent on enforcement, any real-world consequences for non-payment would depend on other instruments or governance arrangements outside the schedule (for example, general public finance rules, inter-agency Memoranda of Understanding, or APRA's internal debt collection procedures). The schedule does not identify, authorise or specify those external mechanisms.

• No compliance reporting or audit languages tied to non‑payment. The schedule does not tie payment to audit outcomes, nor does it require reporting on whether the forms listed in the attachments were delivered in full or partly. The absence of such linkage means the schedule separates the recoverable charge from any contemporaneous certification of delivery within its own text.

For legal and compliance teams at the ABS and RBA, the practical inference from the schedule is that the principal operational enforcement mechanism is the invoice: pay by the 28‑day deadline, or face consequences that lie outside the schedule and will be determined by other governance or legal mechanisms. The schedule itself establishes the financial obligation but leaves the enforcement architecture unspecified.

The schedule is narrowly self-contained in the text provided. It does not reference other Acts, regulations, inter-agency memoranda, appropriation instruments, taxation treatment, or data-sharing instruments within its own text. The following interaction points can be identified strictly from the schedule language and attachments, without bringing in external laws or presumed protocols.

• Inter-agency financial flows. The schedule documents that APRA will invoice ABS and RBA for specific recoveries. That establishes an inter-agency financial flow: APRA as creditor, ABS/RBA as debtors. Practical interaction with Commonwealth financial rules (for example, appropriation rules, departmental accounting procedures, consolidated revenue guidance) is likely necessary in practice for payment and budget recognition, but none of those instruments are referenced in the schedule text. The schedule therefore relies on existing institutional arrangements (not stated here) for payment execution.

• Data specification and supply. Attachments enumerate ARF and SRF forms, which function as the definitional specification for what is to be "provided" to ABS and RBA. The schedule does not define legal data-sharing authorities or privacy constraints in relation to those forms; it simply lists the forms as the content basis for the charge. Any legal constraints on data exchange, confidentiality, or statutory authority for providing the data are not addressed within this schedule and would be governed by other instruments outside the schedule.

• IT development and support costs. Two lines recover EFS collection system development costs from ABS and RBA and one line recovers maintenance and support of data sharing APIs used by the RBA. The schedule therefore connects financial recovery to specific IT components. How those costs were incurred, whether procurement rules applied, and whether those costs interact with Commonwealth ICT policies or multi-year capital budgeting requirements is not addressed in the schedule text.

• Absence of cross-reference. The schedule contains no express cross-reference to other statutes, regulations, or instruments that create APRA’s charging power, obligate the ABS or RBA to pay, or require the production or receipt of the attachments' forms. Any legal basis for APRA to make charges or for ABS/RBA to be charged must be found in the enabling instrument(s) outside the schedule; the schedule itself only fixes the amounts, recipients and payment timing.

Practitioners should note that the schedule sets an operational financial relationship between APRA, ABS and RBA for 2023-24, but it does not, within its own text, state how it sits within the broader legal regime governing inter‑agency cost recovery, data sharing or public sector procurement. Those interactions exist in practice but are not specified here.

The supplied text contains no amendment history, transitional provisions, or prior versions. The schedule is presented as the operative document for the 2023-24 financial year without notes about prior or subsequent amendments.

• No historical notes included. The schedule does not include marginal notes, "as amended" notations, repeals, commencement dates other than the financial year reference, or references to predecessor schedules.

• Single-year scope. Because the amounts are framed explicitly for the 2023-24 financial year, the schedule appears to be a single-year instrument. There is no express provision for renewal, indexation, or automatic carry-forward of the same amounts into subsequent financial years.

• Attachments tied to the financial year. Attachments 1 and 2 are headed "Statistical information provided to the ABS during the 2023-24 financial year" and "Statistical information provided to the RBA during the 2023-24 financial year" respectively. This dating supports the interpretation that the schedule is a year‑specific schedule rather than a standing multi-year instrument.

• No express savings or transitional clauses. The schedule contains no language preserving prior entitlements, grandfathering previous charging arrangements, or indicating that amounts have been adjusted from prior years. It therefore reads as a discrete schedule for the stated year.

For users requiring a legislative timeline or amendment history, the schedule supplies none. Any historical comparison, prior-year figures, or subsequent modifications must be sourced from other records or instruments outside the text provided.

The schedule itself contains no references to case law, disputes, litigation, or adjudicative decisions. It does not record any past or pending legal challenges to the charges, the invoicing mechanism, the content of the attachments, or the inter-agency cost recovery practice it embodies.

• No cases named or cited. The text lists no judicial or administrative decisions, and it does not provide any background on contested payments, disagreements about the forms delivered, or disputes over APRA’s right to charge.

• No dispute-resolution mechanism in the text. The absence of an internal dispute-resolution process linked to these charges in the schedule suggests that any litigation or dispute would be governed by general administrative law, contract principles, or other statutory regimes external to this document. The schedule itself does not attempt to create or document a panel or process to handle disagreements.

• Practical effect for risk management. Because the schedule does not document litigation or dispute pathways, entities expecting to contest an invoice (for amount, scope, or delivery) would need to rely on other procedures (internal governance processes or statutory dispute mechanisms) not described in the schedule.

If a reader requires litigation history related to these charges, they must seek external records. The schedule provides no litigation references or historical dispute annotations.

The schedule is compact, but it contains a number of features and absences that create operational, budgeting, and interpretive risks. The following are concrete points to watch for, grounded only in the text provided.

• The invoice is the trigger; payment deadline is short. Each charge is payable "28 days after receipt of APRA’s invoice." That single sentence controls procedural timing. If an agency’s internal payment cycles, appropriation approvals or interdepartmental clearance take longer than 28 days, the payer must manage those timing risks. There is no grace period or staged payment arrangement included.

• APRA named but its procedural obligations are not specified. The schedule references "APRA’s invoice for the charge" but does not specify issuance dates, consolidation of multiple charges into a single invoice, or the expected timing of invoice dispatch. The lack of invoice-frequency detail can create uncertainty about cashflow planning.

• Single-year, fixed nominal amounts. The amounts are fixed for 2023-24. There is no indexation, no contingency for overruns in development costs, and no express provision for adjustments or reconciliations. If actual development or maintenance costs differ from the amounts recovered, the schedule does not present a mechanism for mid‑year adjustment.

• Differences between Attachment 1 and Attachment 2. The two attachments largely overlap but are not identical. For example:

  • Attachment 1 includes SRF codes (SRF 720.0, SRF 721.0, SRF722.0) labelled as ABS forms; Attachment 2 lists ARF 723.0 "ABS/RBA Margin Lending" which is not present in Attachment 1.
  • ARF 730.0 "ABS/RBA Statement of Financial Performance" appears in Attachment 1 but not in Attachment 2 (Attachment 2 includes ARF 730.1 "ABS/RBA Fees Charged" but not ARF 730.0).
  • ARF 723.0 (Margin Lending) appears only in Attachment 2.

  These differences mean practitioners must check which specific forms are the basis for each charge and not assume full parity between ABS and RBA deliverables.

• Ambiguous labelling and formatting. Attachment 1 lists "SRF722.0 | ABS Derivatives Schedule" with a different spacing/format compared to other SRF entries. Practitioners should verify that form codes and titles correspond to operational reporting templates; typographical inconsistencies can lead to misinterpretation about which form is intended.

• Multiple cost categories and allocation. Development costs for the EFS collection system are recovered separately from maintenance and support costs of the data sharing APIs. The schedule splits development recovery between ABS ($45,521) and RBA ($57,936), and assigns $120,720 for RBA API maintenance/support. There is no explanatory allocation formula in the schedule explaining how development costs were apportioned between ABS and RBA; the schedule simply states the amounts to be recovered. That may complicate internal budget justifications for the payer.

• No express linkage between delivery and payment. The schedule charges for the "provision" of listed statistical information but does not state that payment is conditional on delivery, or that non-delivery relieves the payer of an obligation. Payment is linked to APRA’s invoice, not explicitly to a delivery certification.

• No GST, tax or appropriation clarifications. The schedule provides dollar amounts but does not state whether the amounts are GST-inclusive or exclusive, or how the payments should be accounted for within appropriation frameworks. That absence can lead to different interpretations in accounting practice.

• Absence of enforcement, dispute or amendment provisions. As noted previously, the schedule contains no enforcement or amendment mechanisms. That raises the risk that practical disputes will default to general administrative processes not described here.

• Aggregate amounts and budgeting. The five lines aggregate to $1,011,492. Individual payers should reconcile the per‑payer totals against their internal budgets: ABS $337,619; RBA $673,873. Failure to do so could create unexpected budget exposures.

Each of these items is directly traceable to wording or omissions in the schedule and attachments. Operational teams should plan to close these gaps by confirming invoice timing, confirming whether amounts are inclusive of GST, reconciling form lists with actual reporting templates, and establishing internal workflows to meet the 28‑day payment deadline.

Compliance under this schedule is operationally narrow: receive APRA’s invoice for a listed charge and pay the specified amount within 28 days. The schedule’s attachments also create an implicit compliance need to reconcile the forms listed with actual data exchange expectations. The following practical checklist follows directly from the schedule text and attachments.

1. Budget recognition and internal approvals

   • Record the specific amounts assigned to the agency in internal budgets for the 2023-24 financial year: ABS $337,619 (comprised of $292,098 and $45,521); RBA $673,873 (comprised of $495,217, $57,936 and $120,720).
   • Ensure appropriation lines or internal cost‑centre allocations are in place so payment can be made promptly upon receipt of APRA’s invoice.

2. Invoicing tracking and payment workflow

   • Designate a finance contact to receive and acknowledge APRA invoices as invoices will be the trigger for the 28‑day payment clock.
   • Establish a payment timeline that accommodates internal controls and ensures remittance within 28 days of invoice receipt.
   • Decide whether to request consolidated invoicing from APRA (the schedule does not specify invoice frequency), and confirm the preferred invoicing format and remittance instructions with APRA.

3. Reconcile payable amounts to the schedule

   • On receipt of an invoice, compare the invoiced amount and description to the corresponding line in the schedule to ensure the amount invoiced matches the schedule figure.
   • Verify that the invoice references the correct attachment (Attachment 1 for ABS-related data, Attachment 2 for RBA-related data) and the stated service line (development, maintenance, or statistical provision).

4. Verify form lists and operational scope

   • Cross‑check the ARF and SRF form codes and names in the applicable attachment with the agency’s internal data collection and receipt templates to confirm that the listed forms are the actual deliverables.
   • For any ambiguity in form codes or titles (for example SRF722.0 formatting anomalies), request clarification from APRA to avoid disputes about scope.

5. Clarify tax and accounting treatment

   • Confirm whether the dollar amounts are GST-inclusive or exclusive and record them appropriately in the agency’s accounts. The schedule is silent on GST treatment.
   • Confirm with internal accounting how the payment should be processed against appropriations and whether any special ledger entries are required.

6. Manage disputes and recordkeeping

   • Although the schedule lacks an express dispute-resolution mechanism, maintain contemporaneous records of invoices received, payment approvals, and any communications with APRA concerning the invoice.
   • If there is a question about whether a particular form was provided or the service was delivered, document the delivery evidence and raise the query promptly with APRA, noting that the payment clock begins on receipt of the invoice.

7. IT and procurement follow-up

   • For the development cost allocation and API maintenance/support charges, retain procurement or project documentation that explains the cost basis (for internal audit and budget justification), even though the schedule does not require it.
   • If there are ongoing maintenance or development obligations beyond 2023-24, plan to seek visibility about future schedules because this instrument is limited to the 2023-24 year.

8. Internal audit and controls

   • Ensure the internal audit or financial compliance teams are aware of the schedule amounts and payment timing so that 28‑day compliance is monitored.
   • Keep a register or ledger showing the schedule line, invoice date, invoice number, receipt date, payment due date and actual payment date to demonstrate compliance.

Following these steps aligns operations with the text’s clear duty: pay the specified sum within 28 days of APRA’s invoice. Where the schedule is silent (for example on GST treatment, invoice frequency, dispute mechanisms or delivery certification), seek confirmation from APRA and retain documentary evidence of communications and payments to reduce the risk of future queries.