The schedule relies on a small set of operational concepts, each expressed in table columns and attachments. Those concepts and their mechanical content are:

• Charge description, scope and recipient. Each row in Column 1 describes "Provision to the ABS" or "Provision to the RBA" during the 2018-19 financial year of specified statistical information. That links a provider/recipient relationship between APRA (the invoicing body identified in Column 4) and ABS or RBA as the paying entity (Schedule, Column 1; Column 3).

• Monetary amount. Column 2 records the fixed numeric amount for each specified provision: $283,788; $68,276; $15,529; and $28,840. These amounts are expressed with a dollar sign but the schedule contains no textual definition of currency, nor any indexation or formula for calculation (Schedule, Column 2).

• Person required to pay. Column 3 explicitly names the body required to pay for each charge. Two bodies are listed: the ABS and the RBA, assigned to specific entries. The schedule therefore assigns the financial obligation to central agencies rather than to the private firms that supply statistical data (Schedule, Column 3).

• Payment trigger and timing. Column 4 fixes the payment term as "28 days after receipt of APRA’s invoice for the charge." This establishes APRA as the invoicing authority and the payment timing as a fixed period from the commercial event of invoice receipt (Schedule, Column 4).

• Attachments as definitional annexes. Attachments 1-4 list the form codes and form names of the statistical information to which each charge relates. Attachment 1 (ABS, non‑EFS) contains a long list of ARF, GRF, RRF and SRF forms covering statements of financial position, debt and equity securities, state‑by‑state commercial, housing and personal finance forms, selected revenues and expenses, and RFC schedules. Attachment 2 (RBA) contains a partly overlapping but not identical set of ARF and RRF forms and some WRF items; it is provided in an embedded HTML table in the source. Attachments 3 and 4 define the EFS (Expanded Financial Statistics) package identified by ARS 720.0 to ARS 720.7 (Schedule, Attachments 1-4).

• Temporal limitation. Each description is expressly limited to provision "during the 2018-19 financial year." That situates the schedule as a historic, year‑specific charging item rather than as a standing recurring schedule in its own words (Schedule, Column 1).

• Scope of datasets. The attachments identify precise return codes, for example ARF_320_0 "Statement of Financial Position (Domestic Books)", ARF_392_0_1 "Housing Finance in NSW", RRF_320_6 "Financial Derivatives (RFCs)", SRF_720_0 "ABS Statement of Financial Position", and ARS 720.1 "Loans and Finance Leases" for EFS reporting. The form codes link the charge to identifiable statistical returns rather than generic data categories (Attachments 1-4).

These concepts combine to make the schedule a transactional allocation: APRA provides a package of statistical outputs, APRA issues an invoice to ABS or RBA, and the named agency must pay the specified amount within 28 days. The schedule does not present an explicit methodology for apportioning costs among contributors, does not describe how the amounts were calculated, and does not set out obligations on APRA beyond issuing invoices. Any treatment of indexing, recurring application beyond 2018-19, or sanctioning for non‑payment is not contained within the schedule as supplied.

The schedule directly identifies three institutional actors by role and name: APRA as invoicing party (through the timing language referencing "APRA's invoice"), the ABS as a named payer for two entries, and the RBA as a named payer for two entries (Schedule, Columns 3-4). The schedule also indirectly affects the administrative units within those agencies that handle budgeting, invoices and data reconciliation. For the ABS and the RBA the schedule imposes an explicit budgetary outflow for the 2018-19 reporting package; ABS is charged for two packages totalling $299,317 ($283,788 + $15,529) and the RBA is charged $97,116 ($68,276 + $28,840) (Schedule, Column 2).

The schedule does not name any private sector entities as payers. It lists numerous statistical form codes and form names that refer to "financial sector entities", "RFCs", "WSF", "EFS" and other reporting categories (Attachments 1-4). Those codes indicate which data were provided and thus which classes of private reporters likely supplied raw data to APRA; however the schedule does not create any obligation stated in the text on those private reporters to pay these charges. Consequently the immediate financial consequences are borne by the ABS and RBA, not by the private reporting entities, at least according to the schedule’s text (Schedule, Column 3).

Operationally affected functions inside the named agencies include finance and procurement teams, who must process APRA invoices and pay within 28 days of receipt (Schedule, Column 4). Statistical and data teams will be affected insofar as the attachments define the datasets for which charges were levied; those teams have an interest in the scope and quality of the delivered datasets (Attachments 1-4). APRA’s finance and data operations are affected in that it is the agency which issues invoices and presumably bears the costs of producing and distributing the datasets; the schedule implicitly authorises APRA to invoice ABS and RBA (Schedule, Column 4).

Beyond those three institutions, the schedule may have second‑order effects on end users of the datasets, such as financial sector firms, researchers and market participants. The data sets listed include state‑by‑state housing and commercial finance breakdowns, derivatives schedules, and statements of financial position; access to those datasets shapes statistical outputs used in analysis. The schedule does not assign user fees to private users, nor does it indicate that the amounts will be recovered from other budget lines. Any downstream effect on private enterprise, competition or prices would depend on the accounting treatment inside ABS and RBA and on how those agencies reallocate funds in their budgets; the schedule itself sets out only the immediate payer and the dollar amount.

Finally, because the schedule is restricted to 2018-19, any institution tasked with forecasting or budgeting for future years cannot rely on this schedule for subsequent year charges. Entities with duties to audit or review inter‑agency cost allocations, such as parliamentary budget offices or audit offices, will be interested in the schedule as a discrete historical cost allocation for 2018-19. The schedule does not contain exemptions, concessions, or alternative payment arrangements for the named payers.

The schedule sets a narrowly framed duty: the ABS and RBA are each required to pay the listed amounts for the specified data provision (Schedule, Column 3). The timing duty is explicit: payment is due 28 days after receipt of APRA’s invoice for the charge (Schedule, Column 4). The schedule also imposes a definitional duty by reference to attachments: the charge applies specifically to the statistical information detailed in the relevant attachment, for the 2018-19 financial year (Schedule, Column 1; Attachments 1-4).

Rights that the schedule implies are limited. The named payers have the right to receive an APRA invoice, because the payment obligation is triggered by "receipt of APRA's invoice" (Schedule, Column 4). The payers therefore have the practical right to documentary evidence of the amount and the basis for the charge before the payment timeframe commences. The schedule does not expressly grant a right to dispute the invoice or to withhold payment, nor does it set a dispute resolution process. Consequently any such rights for ABS or RBA to query, seek documentation, or withhold payment must arise from the parent instrument authorising this schedule or from inter‑agency protocols, not from the schedule text itself.

The schedule does not set rights for third parties. It does not, for example, create a right for private reporters to be reimbursed, nor does it create a right to access the underlying datasets as a condition of payment. The attachments list the specific form codes delivered, which gives the payer a definitional basis to check that the invoiced charge corresponds to a discrete bundle of outputs, but the schedule does not provide a mechanism for verification or acceptance testing.

There are implied administrative duties for APRA, though they are only referenced indirectly. APRA must issue an invoice; the invoice date or the date of receipt will be determinative of the 28‑day payment window (Schedule, Column 4). The schedule does not state how APRA should calculate or justify the amount on the invoice, whether the invoice must be accompanied by delivery confirmation, nor whether partial deliveries would trigger partial invoicing.

The schedule is silent on remedies for non‑payment, late payment interest, or recovery procedures. Because the schedule itself contains no penalty clause, rights to enforce payment or obligations to apply sanctions will depend on other provisions of the instrument that adopted this schedule or on separate financial management laws. The lack of enforcement language in the schedule means the payers’ duties and APRA's collection rights are partly expressed but not operationalised within this schedule alone.

The Schedule of charges contains no express penalty provisions, enforcement mechanisms, or interest rates for late payment. The only enforcement‑adjacent provision is the fixed payment term, "28 days after receipt of APRA’s invoice for the charge" (Schedule, Column 4). The schedule therefore establishes a point in time when payment becomes due, but it does not specify consequences for failing to pay by that date.

Because the schedule does not set out remedies or sanctions, any recovery or enforcement action would need to rest on the broader statutory instrument, regulation or funding agreement that incorporates this schedule, or on general public sector financial management legislation. The schedule alone does not identify an agency or office responsible for pursuing non‑payment beyond APRA issuing an invoice. It therefore leaves open the question whether APRA can take administrative steps such as charging interest, suspending data access, commencing legal action, or seeking set‑offs under other laws. No provision in the schedule authorises APRA to suspend future data provision to ABS or RBA in the event of non‑payment, nor does the schedule provide for referral to a debt recovery body.

The absence of penalty detail creates practical enforcement risks. For example, if the invoiced agency disputes the amount, the schedule contains no built‑in dispute escalation or suspension mechanism for the payment obligation. Similarly, without a stated interest or late penalty, APRA’s commercial incentive to pursue timely payment may be limited to standard departmental debt recovery procedures, if any, found outside this schedule.

For practitioners seeking enforcement options or remedies the schedule is therefore incomplete. To identify legal enforcement routes one must consult the enabling legislation or instrument under which the schedule operates, or general statutes applicable to government debts and inter‑agency billing. The schedule’s silence on enforcement increases reliance on external frameworks that are not included in the text provided. That creates a factual uncertainty about the real legal consequences of late or non‑payment that cannot be resolved from the schedule itself.

The schedule is an annexary instrument listing charges and datasets; it does not contain cross‑references to other statutes, regulations, or clauses that would authorise APRA to levy or collect these charges. It therefore sits as a definitional and transactional attachment which must, in practice, be embedded in a parent legislative or administrative instrument to have legal effect. The schedule itself references APRA’s invoice as the payment trigger, which links it operationally to APRA’s authority to invoice; that authority and any procedural constraints are not contained in the schedule itself (Schedule, Column 4).

Because the schedule identifies ABS and RBA as payers, there will be interaction with public financial management rules that govern intra‑governmental payments, such as appropriation law, departmental accounting standards, and inter‑agency charging arrangements. The schedule does not address appropriation availability, whether the ABS or RBA require explicit budget appropriation to make the payments, or whether payments are to be treated as agency recoveries. Those questions are answered by broader public sector financial frameworks and by the parent instrument, neither of which are present in the schedule.

The schedule also interacts functionally with statistical and privacy rules insofar as it describes the delivery of specific datasets. Attachments list detailed forms,some state‑level, some RFC‑specific, some derivatives schedules,which will have been compiled under reporting requirements applicable to financial sector entities. The schedule does not itself alter reporting obligations on private entities, nor does it purport to create or modify privacy protections; those remain governed by the reporting regime and privacy laws that actually require the original data returns. The schedule therefore sits downstream of data collection rules.

For lawyers and compliance professionals, an important interaction is with procurement and invoicing norms. The instruction "28 days after receipt of APRA's invoice" will interact with agencies' payment card policies, invoice validation procedures, and audit requirements. The schedule does not reconcile these payment terms with any statutory prompt payment regimes or with government interest on late payments. It therefore requires an implementing agency to reconcile the timing and documentary triggers with existing statutory payment frameworks.

Finally, where the schedule lists forms that reference "RFCs", "WSF", "EFS" or other specialist classifications, it will interact with sectoral supervision law and regulatory reporting standards. The schedule defines what bundle of outputs is being charged for, but it does not change reporting content, nor does it purport to authorise access to confidential data beyond what the parent instrument or reporting rules permit. To fully map the legal interactions, one must place the schedule within its enabling statute and operational protocols; the schedule itself contains no standalone cross‑references.

The document supplied presents a single schedule marked for the 2018-19 financial year and does not contain an explicit amendment history, revision date or version control metadata. It does not record prior or subsequent changes, nor does it contain marginal notes indicating that any row has been inserted, amended or repealed. The schedule therefore appears as a static, year‑specific annex without an embedded chronology.

Because the schedule itself lacks amendment annotations, to trace any changes, rescissions or reapplications for other years the reader must consult the parent legislative instrument, the statute book or the official register where the instrument is published. The schedule gives no indication whether these charges were novel for 2018-19, whether they replaced prior arrangements, or whether they were repeated in subsequent years. There is no textual provision for rolling application to future financial years or for indexation of the amounts listed.

Internally, Attachments exhibit formatting differences that could reflect drafting or versioning steps. Attachment 2 is included in the supplied text as an HTML table fragment, whereas Attachments 1, 3 and 4 are formatted as Markdown style tables. This difference in presentation may be an artifact of how the schedule was compiled or converted, rather than substantive amendment. The content of the two EFS attachments (3 and 4) are identical in the forms listed; the non‑EFS attachments differ between ABS and RBA, which could reflect negotiated differences or separate service packages rather than amendments (Attachments 1-4).

Practitioners looking for authoritative amendment history should therefore search for the instrument in the consolidated legislation database, consult official legislative amends and explanatory materials, and check agency records for any internal memoranda that authorised or updated the schedule. The supplied schedule does not, by itself, document any amendment history.

The schedule contains no references to judicial decisions, challenges, or ongoing litigation. It does not list cases, determinations, or dispute outcomes. There is no internal language indicating that the amounts or the charging arrangement were subject to litigation, nor are there cross‑references to dispute panels or tribunals.

For legal researchers seeking litigation history connected to these charges, the schedule provides only the core facts necessary to frame a search: the parties involved (APRA as invoicer, ABS and RBA as payers), the time period (2018-19), and the datasets (the detailed forms in Attachments 1-4). Any litigation arising from non‑payment, disputes over delivery or the content of the datasets would therefore need to be located by searching public court records, tribunal databases, or agency annual reports for references to contested invoices or inter‑agency disputes. The schedule itself supplies no narrative or record of disputes.

Because the schedule is silent on enforcement, penalties and dispute resolution processes, litigation could in theory be an avenue to enforce payment obligations or contest invoices. However, absent external records, no litigation history can be derived from this schedule alone. Researchers should check APRA, ABS and RBA annual reports and consolidated legal proceedings registers for 2018-19 and thereafter for any mention of contested billing between these agencies.

Several practical and legal "gotchas" arise from reading the schedule carefully.

• Payer identification simple but counter‑intuitive. Column 3 expressly names ABS and RBA as "Person required to pay the charge." Some readers might expect the private reporting entities that supply the raw data to bear the cost; the schedule does not do that. The budgetary obligation sits with ABS and RBA, not with the private sector reporters (Schedule, Column 3).

• Invoice receipt is the trigger. The 28‑day payment window begins on "receipt of APRA's invoice" and not on the date of supply, acceptance or completion of a reconciliation process (Schedule, Column 4). Organisations must therefore have invoice management procedures that capture the actual date of receipt, because that date fixes the statutory timetable for payment.

• No currency defined. Amounts are shown with a dollar sign. The schedule does not define the relevant currency unit. In most Commonwealth schedules the dollar sign denotes Australian dollars, but that assumption is not contained in this text. For high‑stakes accounting treatment a confirming cross‑reference to the parent instrument or to agency accounting rules will be necessary.

• No enforcement mechanics included. The schedule sets no penalties for late payment, no interest rates, and no collection steps (Schedule, Column 4). APRA’s practical ability to enforce or withhold services is not stated here; one must check the authorising instrument for enforcement mechanisms.

• Year‑specific scope. Each entry is limited to "during the 2018-19 financial year" (Schedule, Column 1). If an agency assumes continuity, it should not rely on the schedule alone; it must locate a recurring schedule or new instrument for subsequent years.

• Attachments may not be identical across recipients. Attachment 1 and Attachment 2 contain overlapping but not identical sets of form codes. For example Attachment 2 (RBA) contains ARF_118_0 and ARF_118_1 which do not appear in Attachment 1 as supplied; Attachment 1 lists RRF_320_6 (Financial Derivatives (RFCs)), SRF_721_0 and SRF_722_0; Attachment 2 includes ARF_320_8 "Housing Loan Reconciliation" and ARF_395_0 "Business Finance Statistics" which are not identically placed in Attachment 1. That means the two agencies were charged for different bundles of outputs despite both dealing with APRA. Practitioners should reconcile the attachments carefully when matching invoices (Attachments 1-2).

• Form code complexity. The attachments use several form code families: ARF, RRF, GRF, SRF, WRF, RRF and ARS. Misreading a code could result in mismatched reconciliation, especially where names differ slightly between domestic/licensed/RFC variants. Accounting teams must map the codes to spreadsheets or internal cost centres before payment.

• No stated deliverable acceptance test. The schedule defines the dataset by reference to form codes but does not define delivery acceptance criteria, data quality thresholds, or the documentation that must accompany the invoice to demonstrate delivery. That omission can create disputes over whether the invoiced amount corresponds to fully delivered and accepted outputs.

• Aggregation of charges. ABS and RBA are each charged two line items. It is not specified whether APRA will invoice those charges together or separately; the payment term is tied to receipt of "APRA's invoice" and therefore the treatment of multiple invoices should be coordinated in accounts payable.

• Possible internal budget implications. The schedule imposes an unbroken obligation to pay particular sums. Depending on how ABS and RBA classify these as departmental or administered items, there may be appropriation and internal authorisation requirements which are not addressed in the schedule.

These "gotchas" create operational and audit risks if invoice processing teams do not align their procedures to the schedule’s structure and the attachments’ specificity.

For a payer agency (ABS or RBA) or for APRA as invoicer, practical compliance steps drawn from the schedule are straightforward but require discipline in inter‑agency administration.

For APRA (invoicer):

• Issue clear, dated invoices that reference the schedule line item and the relevant attachment by FORM_CDE codes. Because payment is due "28 days after receipt of APRA's invoice", the invoice should state the delivery period (2018-19), the FORM_CDE codes, the total amount and the date of dispatch to create an unambiguous receipt trigger (Schedule, Column 4; Attachments 1-4).
• Include delivery evidence with the invoice. Although the schedule does not require it, attaching a delivery confirmation or a manifest listing the forms supplied will reduce disputes and facilitate timely payment.
• Consolidate billing where appropriate. If APRA intends one invoice per payer covering both the non‑EFS and EFS items, state that clearly; if APRA issues separate invoices, be consistent to avoid confusion over the 28‑day timing.
• Retain records of invoice transmission and, if delivered electronically, delivery/read receipts to evidence the "receipt" date.

For ABS/RBA (payer):

• Establish an invoice receipt log. Capture the exact date the APRA invoice is received, because that date starts the 28‑day countdown to payment (Schedule, Column 4).
• Match invoices to attachments. Reconcile the invoice amount to the specific FORM_CDE codes listed in the applicable attachment to confirm that what was invoiced corresponds to the defined bundle of outputs (Schedule, Column 1; Attachments 1-4).
• Check appropriation and internal approvals. Confirm that the required budget appropriation is available for the amounts ($283,788; $68,276; $15,529; $28,840) and follow internal delegation and procurement rules for inter‑agency payments.
• Document acceptance. While the schedule does not mandate an acceptance test, it is good practice to record internal sign‑off by data owners confirming receipt and satisfactory content of the datasets corresponding to the FORM_CDEs. This reduces late‑payment disputes and provides audit evidence.
• Maintain audit trail. Retain copies of invoices, delivery proofs, reconciliation spreadsheets, approval emails and payment confirmations for audit and for potential enquiries by parliamentary or audit offices.
• Plan cashflow. Treat these as discrete one‑off payments for 2018-19 unless there is a broader schedule or a standing arrangement. Budget managers should not assume recurrence without a formal replacement schedule.
• Establish a dispute pathway. Negotiate and document an internal procedure with APRA for any invoice queries, including expected response times and escalation points, because the schedule contains no formal dispute mechanism.

For APRA, ABS and RBA jointly:

• Agree a protocol for invoice disputes. A short memorandum of understanding or a delivery certificate template will materially reduce friction. Although the schedule does not require it, agencies often formalise expectations to support timely payment.
• Map FORM_CDE codes into accounting systems. Translate the ARF, RRF, GRF, SRF, WRF and ARS codes into accounting cost centres and internal object codes so that invoices post cleanly.
• Clarify currency and GST treatment. The schedule uses "$" and does not mention tax treatment. Confirm with internal tax advisers whether GST or other tax treatments apply, and whether the charges are treated as intra‑government transactions exempt from GST, if that is relevant under tax law and accounting policy.

For auditors and legal advisers:

• Seek the enabling instrument. To advise on enforcement, waiver powers, or authority to demand payment from ABS/RBA, obtain the parent legislation or instrument which adopts this schedule.
• Test the procurement/appropriation nexus. Confirm that payments are consistent with appropriation law and departmental accounting standards.

Following these steps will align day‑to‑day operations with the mechanical obligations in the schedule: pay the specified amount, for the specified bundle of forms, within 28 days of APRA’s invoice. The schedule itself supplies the critical data but leaves ancillary implementation detail to ordinary inter‑agency financial controls and to the parent instrument that authorises the schedule.