This Reporting Standard (ARS 920.4) prescribes the data ADIs must provide to APRA to support administration of the Australian Government Arts Sector Show Starter Loan (SSL) Guarantee Scheme and to permit APRA’s prudential use of that data. The Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (Authority, paragraph 1). It requires ADIs that have been granted a guarantee under section 5 of the Guarantee of Lending to Small and Medium Enterprises (Coronavirus Economic Response Package) Act 2020 in relation to the Arts Sector SSL Guarantee Scheme to submit two specific forms: ARF 920.4 (Portfolio Information) and ARF 920.5 (Loan Level Details) for each reporting period (Application, paragraph 3; Information required, paragraph 5).

Mechanically, the Standard imposes the following main operational duties. First, reporting frequency: subject to APRA’s discretion, reporting is weekly, defined as each business week (paragraphs 7 and the Interpretation at paragraph 15 that defines business week as Monday to Friday). Second, timing: data for a reporting period must be provided within 10 business days after the end of that period unless APRA has granted an extension in writing (paragraphs 8 and 10). Third, format and transmission: submissions must be electronic, using APRA’s Direct to APRA (D2A) application or another APRA-notified method (paragraph 6). Fourth, scope and consolidation: reporting is required on a domestic books consolidation (paragraph 5; Interpretation paragraph 15 referring to ARS 701.0 for the meaning of domestic books). Fifth, content: ARF 920.4 requires portfolio-level counts and values (portfolio to date and portfolio as at period end, including items such as loans approved, loans cancelled or refinanced, written‑offs, recoveries, guarantee claims, past‑due and impaired loans, and a weighted average customer rate) and ARF 920.5 requires loan‑level data for each approved loan in the reporting period (loan identifier, borrower name and ABN, loan value, interest rate, guarantor names, approval and final repayment dates, prior relationship indicator and security indicator) (see the specific items and table instructions within the ARF guides).

The Standard also sets governance and control obligations: ADIs must subject all reported information to internal review and authorisation processes and ensure completeness and reliability (Quality control, paragraph 11), and the officer submitting the data must digitally sign using a certificate acceptable to APRA (Authorisation, paragraph 12). APRA may make minor, non‑substantive variations to forms or instructions to correct technical errors or clarify application, and must notify reporting ADIs if it does so (paragraphs 13-14). APRA’s discretions under the Standard are to be exercised in writing (paragraph 17). The Standard commenced for reporting periods ending on or after 18 December 2020 (Commencement, paragraph 4).

The Standard organises reporting around two complementary concepts: portfolio-level reporting (ARF 920.4) and loan-level reporting (ARF 920.5). The portfolio concept separates cumulative “portfolio to date” metrics (items 1.1-1.7) from snapshot-of-period-end metrics (items 2.1-2.5). The loan-level concept captures transactional and identity fields for every approved loan in the reporting period (Table 1 for ARF 920.5).

Key definitional anchors are borrowed from Reporting Standard ARS 701.0 (ARS 701.0 ABS/RBA Definitions for the EFS Collection). The Standard imports definitions for “credit limit”, “credit outstanding”, “facility”, “interest rate”, “loans approved” (borrower-accepted commitments), “past due”, “recoveries” and “securitised” exposures by reference to ARS 701.0 (ARF 920.4 definitions table; ARF 920.5 definition references). The Standard therefore depends on consistent interpretation of those baseline data concepts by reference to ARS 701.0.

Several reporting rules and measurement treatments are emphasised:

• Treatment of mixed facilities: where a finance facility mixes interest rate or repayment types, the number of facilities is reported according to the predominant interest rate or repayment type by value, while the value of finance is apportioned across relevant dimensions (ARF 920.4, Treatment of facilities).

• Inclusion of securitised loans: both portfolio and loan-level instructions explicitly require inclusion of loans that have been securitised (Item 1 and Item 2 instructions in ARF 920.4; Item 1 and Table 1 notes in ARF 920.5).

• Inclusion/exclusion rules for particular counts: Item 1.1 (loans approved) instructs inclusion of terminated or matured loans but exclusion of loans cancelled or refinanced; Item 1.3 separately captures loans cancelled or refinanced (ARF 920.4 Item 1 instructions).

• Measurement of rates: Item 2.5 requires a weighted average customer rate calculated as “the sum of all drawn amounts multiplied by their respective interest rates, divided by the sum of all drawn amounts for all loans approved at the end of the relevant period” (ARF 920.4, Item 2.5).

• Personal data fields: ARF 920.5 requires primary borrower full name, ABN and guarantor names (or “Nil” if none), with granular indicators about prior relationship and security beyond director/personal guarantees (ARF 920.5 Table 1 columns and definitions).

Administrative and legal scaffolding includes: authority under the Financial Sector (Collection of Data) Act 2001 (paragraph 1); APRA’s identity as the recipient and processor of the data (Interpretation paragraph 15 defining APRA as the body established under the APRA Act 1998); and the stated policy purpose that APF 920.4/920.5 data “is used for the purpose of enabling APRA to assist the Commonwealth Government administer the Australian Government SSL Guarantee Scheme” and “may also be used by APRA for prudential purposes” (Purpose, paragraph 2).

The Standard applies only to a defined class of financial institutions: authorised deposit‑taking institutions (ADIs) that have been granted a guarantee under section 5 of the Guarantee of Lending to Small and Medium Enterprises (Coronavirus Economic Response Package) Act 2020 in relation to the Australian Government Arts Sector SSL Guarantee Scheme (Application, paragraph 3; Interpretation paragraph 15 defining ADI as within the meaning of the Banking Act 1959). The term ADI is interpreted by reference to the Banking Act 1959; the Reporting Standard does not extend reporting obligations beyond that statutory class.

Within each covered ADI, operational responsibility is placed on the officers who prepare and submit the returns. Submissions must be digitally signed by an officer using a digital certificate acceptable to APRA (Authorisation, paragraph 12). The Standard therefore implicates front-line credit operations, data/reporting teams, risk and compliance functions (which must design and operate internal review and authorisation processes), IT teams responsible for D2A integration, and legal/privacy offices given the loan‑level personal data required (ARF 920.5 Table 1).

The Standard also indirectly affects borrowers and guarantors to the extent their personal or entity details (full names, ABN, guarantor names) and loan terms (interest rate, approval and repayment dates, security status) will be transmitted to APRA (ARF 920.5 definitions and Table 1 columns). Borrower-focused impacts are not addressed in the Standard text beyond specification that those fields must be reported; there are no instructions in the Standard concerning borrower notification or consent.

APRA is the recipient and user of the information. The Purpose clause (paragraph 2) makes explicit that APRA will use the data to assist Commonwealth administration of the Scheme and may retain/use the data for prudential purposes. APRA also reserves the ability to change reporting cadence for a particular ADI in writing (paragraph 9), to grant extensions (paragraph 10), and to make minor non‑substantive variations to forms/instructions with notification to ADIs (paragraphs 13-14). Where APRA exercises discretion under the Standard it must do so in writing (paragraph 17). Those provisions allocate decision-making authority and administrative control to APRA.

Finally, other regulators or agencies are implicated only by cross-references: the Standard refers to ARS 701.0 definitions and to the Guarantee Act; the APRA Act is referenced in the Interpretation (APRA definition). The Standard does not itself create duties for non-ADI lenders or for the Commonwealth minister; it operates as a data collection instrument targeted at ADIs that participate in the Scheme.

Duties imposed on reporting ADIs are concrete, documentable and recurring:

• Duty to report specified data each reporting period on a domestic books consolidation, using ARF 920.4 and ARF 920.5 (Information required, paragraph 5).

• Duty to submit electronically via D2A or another APRA‑notified method (Form and method of submission, paragraph 6).

• Duty to report on the stated cadence (each business week), unless APRA alters the reporting frequency for the particular ADI (Reporting periods and due dates, paragraphs 7-9).

• Duty to deliver submissions within 10 business days of the period end, unless APRA grants a written extension (paragraphs 8 and 10). Note: a specific clarification states that if the due date falls on a day other than a usual business day, the ADI is nonetheless required to submit no later than the due date (paragraph 10 Note).

• Duty to operate internal review and authorisation processes to assure completeness and reliability of reported information (Quality control, paragraph 11).

• Duty for the submitting officer to digitally sign the information using a digital certificate acceptable to APRA (Authorisation, paragraph 12).

• Duty to adopt the measurement and inclusion/exclusion rules set out in the ARF instruction guides (treatment of mixed facilities; inclusion of securitised loans; definitions for past‑due, impaired, loans approved, recoveries etc., referencing ARS 701.0).

Rights and administrative remedies available to ADIs under the Standard are limited but defined:

• APRA may change reporting periods for a particular ADI to require different frequencies, but must have regard to the ADI’s particular circumstances and Commonwealth requirements (paragraph 9). This provides an ADI with the right to have its specific circumstances considered, although the Standard vests the ultimate decision with APRA.

• APRA may grant extensions of due dates in writing; where granted, the extension date becomes the new due date (paragraph 10). This is an operational right ADIs can seek when they cannot meet the 10 business day deadline.

• Where APRA makes minor variations to forms/instructions, it must notify each ADI required to report (paragraph 14). This provides transparency of non‑substantive changes.

The Reporting Standard text does not set out specific penalties, sanctions or administrative monetary fines. It records its statutory authority (made under section 13 of the Financial Sector (Collection of Data) Act 2001) (paragraph 1) and prescribes procedural obligations, but it does not include express enforcement provisions within its own terms.

Because the Standard is made under the Financial Sector (Collection of Data) Act 2001, ADIs’ obligations and APRA’s enforcement powers may be framed more fully in that parent Act; however, this Reporting Standard does not reproduce or summarise those enforcement provisions. The Standard does make procedural requirements enforceable in practice by APRA (for example, submission format, digital signature and weekly timing) and creates duties (internal controls, digital authorisation) that APRA can review, but it does not itself state sanctions for non‑compliance, nor does it prescribe processes for contesting APRA decisions.

The Standard does bind APRA’s exercise of discretion to writing (paragraph 17), and limits APRA’s ability to alter substantive reporting requirements by permitting only “minor variations” to forms and instructions that do not change substantive requirements (paragraph 13). APRA must notify each ADI of such minor variations (paragraph 14). Those internal constraints are procedural rather than punitive.

Practically, enforcement and penalties in relation to data collection obligations in the Australian prudential framework are typically governed by the enabling statute and APRA’s broader regulatory powers. If a receiver or legal practitioner needs the specific enforcement powers, the Reporting Standard requires that the relevant statutory texts be consulted directly; the Standard itself offers no litigation, penalty or sanction clauses. For purposes of operational compliance planning, reporting ADIs should assume that APRA can take supervisory action if submissions are materially deficient, but the Standard does not define what actions APRA may take nor the thresholds for such action.

The Reporting Standard expressly cross‑references several external instruments and legal authorities:

• Financial Sector (Collection of Data) Act 2001: the Standard is made under section 13 of that Act (Authority, paragraph 1). That Act is the statutory basis for APRA’s data collection powers; any broader enforcement, privacy protections, or limits on APRA’s use of data may be set out in that Act rather than in this Standard.

• Guarantee of Lending to Small and Medium Enterprises (Coronavirus Economic Response Package) Act 2020: the Standard applies to ADIs granted guarantees under section 5 of that Act in relation to the Arts Sector SSL Guarantee Scheme (Application, paragraph 3). The Guarantee Act defines who may receive guarantees and the legal terms of those guarantees; the Reporting Standard supports the administration of that scheme via data collection.

• APRA Act 1998: APRA is defined in the Reporting Standard with reference to its establishment under the Australian Prudential Regulation Authority Act 1998 (Interpretation, paragraph 15). APRA’s prudential functions and data use policies are governed by that Act and other APRA standards.

• Reporting Standard ARS 701.0: the Standard relies heavily on ARS 701.0 for core definitional material (credit limit, credit outstanding, facility, loans approved, past due, securitised, etc.). Where ARF 920.4/920.5 refer to these terms, they adopt ARS 701.0 meanings (see the definitions table in ARF 920.4 and the Interpretation paragraph 15).

• Australian Accounting Standards: Item 1.4 of ARF 920.4 requires reporting of scheme-backed loans that have been written off and deducted as a loss per relevant Australian Accounting Standards. Thus accounting recognition under Australian Accounting Standards will affect what is reported as a write-off in the portfolio-to-date figures.

• Digital certificate/IT standards: the Authorisation paragraph (12) requires a digital certificate acceptable to APRA for the submitting officer. The Standard does not set technical specifications for that certificate here; those technical requirements will be set by APRA elsewhere (for example, in D2A technical documentation).

The Reporting Standard also declares that references to Acts, Prudential Standards, Australian Accounting Standards or Reporting Standards are references to those instruments as in force from time to time (paragraph 16). That clause keeps the reporting obligations dynamically linked to amendments in the referenced instruments, so changes in ARS 701.0, the Guarantee Act or accounting standards may alter how fields are interpreted without changing ARF 920.4/920.5 text.

The text supplied contains an explicit commencement statement: the Reporting Standard applies to reporting periods ending on or after 18 December 2020 (Commencement, paragraph 4). Beyond that commencement date, the document as presented does not include a chronological amendment table, notes of legislative amendments, or repeal/replacement history.

The Standard does, however, authorise APRA to make minor variations to the forms and instructions to correct technical, programming or logical errors, inconsistencies or anomalies, or to clarify application to the form, without changing any substantive requirement (Minor alterations to forms and instructions, paragraph 13). If APRA adopts such a variation it must notify each ADI required to report (paragraph 14). Those provisions create an operational route for iterative, non‑substantive changes to the reporting instruments without formal amendment of the Standard itself.

Paragraph 16 provides that references to Acts, Prudential Standards, Australian Accounting Standards and Reporting Standards are to be read as references to those instruments “as in force or existing from time to time.” This keeps ARF 920.4/920.5 responsive to changes in external instruments without an on‑the‑face amendment to the Standard.

No other amendment notices, history entries, version numbers or dates of later change are present in the source text provided. If a practitioner requires a formal amendment chronology, they must consult APRA’s legislative instruments register or the Federal Register of Legislation for consolidated versions and amendment histories; the Reporting Standard as supplied contains no further amendment metadata.

The Reporting Standard text contains no references to litigation, judicial review, administrative appeals, or cases. It does not cite any decisions or any disputes relating to its operation. The Standard should therefore be treated, from the supplied source, as an administrative data collection instrument without an indicated litigation track record.

If an ADI or other party sought to challenge APRA’s exercise of discretion under this Standard (for example, to challenge a decision altering reporting frequency under paragraph 9, or a refusal to grant an extension under paragraph 10), any legal challenge would need to be grounded in the parent statutory scheme (the Financial Sector (Collection of Data) Act 2001, the APRA Act 1998, or administrative law principles). The Standard itself does not articulate appeal routes, remedies or a prior administrative decisions registry. The absence of litigation references in the text supplied means there is no litigation history to summarise from this source.

Practitioners seeking precedent or litigation experience in similar APRA reporting standard disputes will need to search external case law and APRA decisions, bearing in mind that the Reporting Standard requires APRA to exercise discretionary powers in writing (paragraph 17), which can be relevant evidence in any judicial review or administrative law proceeding.

The Standard contains several operational details that can create unexpected compliance risk or implementation complexity if missed:

• Weekly cadence and 10-business-day deadline: under the default rule an ADI must provide the information in respect of each business week (paragraph 7) and submit within 10 business days after the end of the reporting period (paragraph 8). Weekly extracts plus a ten-business-day turnaround can impose sustained operational load on data extraction, validation and authorisation processes. APRA may vary the frequency for a particular ADI (paragraph 9), but the default is frequent.

• Inclusion of securitised loans: both portfolio and loan-level instructions explicitly require inclusion of securitised loans (ARF 920.4 Item 1 and Item 2 guidance; ARF 920.5 Item 1/Table 1). Some ADIs may have separate systems for securitised exposures; ensuring these are included in the domestic books consolidation will require mapping and reconciliation.

• Domestic books consolidation requirement: reporting must be on a domestic books consolidation (paragraph 5; Interpretation paragraph 15 referring to ARS 701.0). If an ADI’s systems are organised by legal entity or regional books, producing a domestic books consolidation consistent with ARS 701.0 can be non-trivial.

• Mixed facility reporting rules: when a facility mixes interest rate or repayment types, counts are to be made according to predominant type by value but the value itself must be apportioned across dimensions (ARF 920.4, Treatment of facilities). This creates additional logic and potentially rounding/aggregation issues in extraction code.

• Exclusion/inclusion rules for loan counts: “loans approved” (Item 1.1) includes borrower‑accepted commitments including those that have terminated or matured but specifically excludes loans cancelled or refinanced (Item 1.3 is used to capture those). ADIs must have clear lifecycle definitions in their loan systems to allocate facilities correctly.

• Weighted average customer rate calculation: the formula for Item 2.5 is explicit and requires correct use of “drawn amounts” and the interest rate applied when drawn (ARF 920.4 Item 2.5). ADIs that report contractual rates rather than customer rates or that include fees in rate measures must adjust to the definition “weighted average customer rate” as provided.

• Personal data fields and privacy: ARF 920.5 requires full primary borrower names and guarantor names and the primary borrower ABN (Table 1 columns and definitions). This is identifiable information which ADIs will need to handle in accordance with privacy laws and with APRA’s confidentiality arrangements. The Standard does not set out APRA’s data retention, disclosure or information security policies in this document.

This section sets out a practical compliance checklist mapped to the Standard’s paragraphs and the ARFs. It is procedural, aimed at internal teams (reporting, credit operations, IT, risk and legal).

1. Identify applicability and scope

   • Confirm the ADI has been granted a guarantee under section 5 of the Guarantee of Lending to SMEs Act 2020 in relation to the Arts Sector SSL Guarantee Scheme (Application, paragraph 3).
   • If covered, identify which legal entities and books feed the domestic books consolidation per ARS 701.0 (Information required, paragraph 5; Interpretation paragraph 15).

2. Agree definitions and data model

   • Adopt ARS 701.0 definitions for credit limit, credit outstanding, loans approved, past due, recoveries and securitised exposures (ARF 920.4 definitions table and Interpretation).
   • Define internal mappings of “loans approved” vs “loans cancelled or refinanced” vs “loans written off” consistent with ARF 920.4 Item 1 guidance and Australian Accounting Standards (Item 1.4).

3. Data extraction and transformation

   • Build extraction routines to capture portfolio-to-date metrics (ARF 920.4 Items 1.1-1.7) and period-end snapshots (Items 2.1-2.5), ensuring securitised loans are included where required.
   • Implement logic for mixed facilities: facility counts to be assigned by predominant interest/repayment type by value; values to be apportioned across types (Treatment of facilities).
   • Implement weighted average customer rate computation per the ARF 920.4 Item 2.5 formula (drawn amounts × their respective interest rates divided by sum of drawn amounts).

4. Loan-level data capture

   • For each loan approved in the reporting period, assemble the fields in ARF 920.5 Table 1: loan identifier, primary borrower name and ABN, loan value approved, interest rate (annual at origination, exclusive of fees), guarantor names or “Nil”, approval date, final repayment date, prior banking relationship indicator, and indicator whether there is security beyond director/personal guarantee (ARF 920.5 Table 1 columns and definitions).
   • Ensure guarantor names are full names for individuals and legal entity names for companies (ARF 920.5 Guarantor names definition).

5. Systems integration and format