The Reporting Standard organises three core concepts: coverage, data granularity, and submission governance.

Coverage: Paragraph 3 defines who must report. Responsibility falls to ADIs and RFCs that receive a Scheme guarantee under section 5 of the Guarantee of Lending to Small and Medium Enterprises (Coronavirus Economic Response Package) Act 2020, limited to loans written in the Scheme’s loan writing period (explicitly from 1 October 2021 to 31 December 2021 in the instrument, or another date specified in the Scheme rules). The instrument distinguishes ordinary Scheme loans from those affected by flood events: where a primary borrower was also adversely affected by the March 2021 floods, the lender must report under ARS 920.10 (this instrument) and not ARS 920.8 (paragraphs 3 and 5).

Data granularity and definitions: The standard prescribes two complementary forms. ARF 920.10 collects portfolio aggregates to date (Item 1), portfolio state at period end (Item 2), and refinanced portfolio detail from earlier Guarantee Scheme phases (Item 3). ARF 920.11 gathers loan‑level detail for each approved borrower in the reporting period (Table 1). Both forms are governed by precise measurement rules: whole Australian dollars for monetary amounts, percentages to two decimal places (instruction guides). Many key terms are defined or cross‑referenced to Reporting Standard ARS 701.0 (e.g. credit limit, credit outstanding, domestic books) and to lender policies (e.g. "impaired" is defined by lender policies) (definitions sections). The portfolio form explicitly requires inclusion of securitised loans and excludes facilities entered and cancelled due to error (Item 1 instructions).

Submission governance: Paragraph 6 prescribes electronic submission via an APRA method. Paragraphs 7-10 set reporting cadence (monthly by default, due within 10 business days after the period, subject to APRA adjustment or written extension). Paragraph 11 demands internal systems, processes and controls to assure completeness and reliability; paragraph 12 requires digital signing using an APRA‑acceptable certificate. Paragraph 15 requires any APRA exercise of discretion under the Standard to be exercised in writing.

Other organisational concepts: The instrument links to accounting practice , written-off loans must be those deducted as a loss per relevant Australian Accounting Standards (Item 1.4) , and to prior Guarantee Scheme phases (Phase 1 and Phase 2 definitions and Item 3 for refinancing). The loan‑level form includes fields (borrower ABN, guarantor names) that create personal data obligations for reporting entities. The standard also includes instructions for treatment of mixed interest/repayment types and apportionment rules when reporting values versus counts (Treatment of facilities section).

Together these elements form an operational template for APRA to gather scheme administration and prudential monitoring metrics in standardised form across covered lenders.

Primary reporting entities: The text specifies in paragraph 3 and the ARF instruction guides that all ADIs and RFCs to which the Standard applies must complete the reporting forms. Paragraph 13 defines ADI by reference to the Banking Act 1959 and APRA by reference to the APRA Act 1998. The immediate legal requirement therefore affects entities that have been granted the Scheme guarantee under the referenced Guarantee Act and engaged in qualifying lending during the Scheme loan writing period.

Internal stakeholders at reporting entities: The Standard triggers obligations across operations, credit, risk, accounting and compliance teams. Paragraph 11 obliges entities to operate processes and controls for internal review and authorisation of the information. Paragraph 12 requires an officer or agent to digitally sign submissions using an APRA‑acceptable digital certificate; this allocates responsibility to authorised signatories and necessitates IT and security arrangements to hold and use such certificates.

Customers and guarantors: ARF 920.11 requires borrower names, ABNs, and guarantor names (Table 1 columns 2, 3 and 6). Those data fields draw on personal and business identifiers and therefore affect borrowers and guarantors by exposing their names and ABNs in data submissions. The instrument requires reporting of whether a loan has director or personal guarantees (ARF 920.10 Item 1.2) and whether a scheme‑backed loan has security in addition to personal or director guarantees (ARF 920.11 Column 10). The inclusion of these data elements affects what information about a borrower or guarantor will be transmitted to APRA and, per paragraph 2, potentially to the Commonwealth Government for Scheme administration.

Third parties and the Commonwealth: The stated purpose in paragraph 2 expressly contemplates APRA using the collected information to assist the Commonwealth Government in administering the Scheme. The instrument therefore affects Commonwealth administrators who will receive outputs or analyses based on this data. It also enables APRA to use the information for prudential purposes, with potential knock‑on effects for supervisory assessments of reporting entities.

Systems and vendors: The electronic submission requirement in paragraph 6 and the requirement for digital certificates in paragraph 12 will involve a lender’s IT vendors or in‑house systems teams. Entities securitising exposures must nevertheless include those loans in the reporting (ARF instructions), meaning data must be consolidated across retained and transferred exposures.

Excluded categories: Paragraph 5 makes an explicit exclusion: where the primary borrower was both adversely economically affected by COVID‑19 and the March 2021 floods, reporting must be under ARS 920.8 (Flood) rather than this instrument. This allocates a discrete subset of loans to a different reporting channel.

In sum, the instrument imposes data collection and submission duties on covered lenders, assigns internal signatory and quality control responsibilities, compels transmission of borrower and guarantor identifiers to APRA (and indirectly the Commonwealth), and implicates IT suppliers and securitisation processes in data consolidation.

Key duties , who must do what, and how:

• Identify covered loans and apply the Standard. Paragraph 3 places the primary duty on ADIs and RFCs granted a Scheme guarantee for loans written in the Scheme’s loan writing period. The instruction guides further specify that scheme‑backed loans include loans where the primary borrower is adversely economically affected by the Coronavirus pandemic (definitions).

• Provide the two reporting forms. Paragraph 4 obliges entities to provide the information required by ARF 920.10 and ARF 920.11 for each reporting period on a domestic books consolidation. The ARF guides specify the fields and aggregation rules.

• Submit electronically and in the required format. Paragraph 6 requires electronic submission using an APRA method available on APRA’s website or other notified methods.

• Comply with reporting cadence and due dates. Paragraph 7 sets reporting periods as calendar months, and paragraph 8 sets the default due date: within 10 business days after the end of the reporting period for periods ending on or after 30 September 2021. Paragraph 9 allows APRA to change frequency for a particular entity; paragraph 10 allows APRA to grant written extensions.

• Maintain internal quality controls. Paragraph 11 requires entities to implement systems, processes and controls for internal review and authorisation of the information to assure completeness and reliability.

• Digitally sign submissions. Paragraph 12 requires the officer or agent submitting data to digitally sign the information using a digital certificate acceptable to APRA.

• Observe the measurement and reporting rules. The forms’ instruction guides specify units (whole Australian dollars, percentages to two decimal places), inclusion/exclusion rules (include securitised loans; exclude cancelled facilities raised in error), apportionment rules for mixed facilities, and specific items and columns to be completed (Items 1-3 in ARF 920.10; Table 1 columns 1-15 in ARF 920.11).

Rights and discretions:

• APRA’s discretionary powers. Paragraph 9 gives APRA the right to change reporting periods for a particular ADI or RFC, increasing or decreasing frequency having regard to the entity’s circumstances and Commonwealth requirements. Paragraph 10 gives APRA the right to grant written extensions. Paragraph 15 requires APRA to exercise any discretion conferred by the Standard in writing, which provides a procedural entitlement for the recipient to obtain written reasons or directions.

• Use of data for multiple purposes. Paragraph 2 expressly authorises APRA to use the information to assist the Commonwealth Government in administering the Scheme and also "for prudential purposes". That dual use is stated as a right of APRA in the instrument.

• Reliance on auxiliary definitions and policies. The instrument delegates definitional work and certain operational determinations to external instruments and lender policies. Paragraph 13 and the ARF instruction guides refer reporting entities to ARS 701.0 for many definitions (credit outstanding, credit limit, domestic books, loan types). The "impaired" definition is left to the reporting entity’s lender policies. This creates a right for banks to rely on their own lender policies and ARS 701.0 consistent definitions when completing submissions.

What the Standard does not do in this text:

• It does not set out enforcement penalties or explicit remedies within the text supplied here. The Standard is made under the Financial Sector (Collection of Data) Act 2001 (paragraph 1), but no penalty provisions are specified in the instrument as provided. Any enforcement or sanctioning power would arise from the enabling Act or other supervisory regimes, not from the Standard text itself.

These duties and rights allocate to reporting institutions the principal operational burden (data collection, quality control, timely electronic submission, and authorised digital sign-off) while granting APRA procedural discretion to change frequency or grant relief in writing and to use the data for scheme administration and prudential supervision.

The Reporting Standard text, as provided, does not specify civil or criminal penalties, monetary fines, or explicit enforcement mechanisms within its own wording. Paragraph 1 records that the Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001; however, the Standard itself does not include penalty clauses or a sanctions schedule. Consequently, the instrument requires careful reading together with the enabling legislation and APRA’s broader supervisory powers to identify any statutory penalties, enforcement measures or compliance directions that may attach to failure to comply. The Standard does specify procedural obligations that imply enforceability: mandatory electronic submission (paragraph 6), reporting cadences and due dates (paragraphs 7-10), internal quality controls (paragraph 11), and digital authorisation (paragraph 12).

APRA’s role and discretionary powers: Paragraph 9 gives APRA authority to change reporting periods (either more or less frequently) for particular entities, having regard to entity circumstances and Commonwealth requirements. Paragraph 10 permits APRA to grant extensions in writing. Paragraph 15 requires that where the Standard provides for APRA to exercise a power or discretion, that exercise must be in writing. These provisions create an administrative structure in which APRA has supervisory discretion to monitor compliance and tailor reporting obligations, and to provide entity‑specific relief in writing. While the Standard does not state the consequences of non‑submission, APRA’s written directions and the enabling legislation are the natural locus of enforcement.

Practical enforcement implications implied by the text:

• Timeliness monitoring: The 10 business day due date (paragraph 8) and the requirement that submissions be digitally signed (paragraph 12) provide APRA with discrete timestamps and authenticated submissions, simplifying detection of late or unauthorised filings.

• Data completeness and quality: Paragraph 11’s requirement for internal review and authorisation implies that APRA can assess the sufficiency and consistency of submissions against those controls. The Standard gives APRA the ability to vary reporting frequency (paragraph 9) where a lender’s circumstances indicate heightened supervisory interest.

• Written discretion: Paragraph 15’s requirement that APRA exercise discretion in writing creates a record trail and gives entities administrative rights to rely on written APRA communications (for example, changes to frequency or extensions). That procedural requirement can limit ambiguity but does not define sanctions.

Because the Standard does not state penalties itself, users of this analysis should consult the Financial Sector (Collection of Data) Act 2001 and APRA’s compliance frameworks to identify specific enforcement powers and sanctions that may be applied in the event of non‑compliance.

The Reporting Standard cross‑references, depends upon, and interacts with several statutory instruments, reporting standards and lender policies. The instrument itself repeatedly points to external instruments for definitions and authority.

Foundational statutes and instruments:

• Financial Sector (Collection of Data) Act 2001. The Standard is made under section 13 of that Act (paragraph 1). That Act is the enabling legislation; any statutory enforcement, confidentiality rules, or powers related to data collection will derive from it rather than from the Standard text.

• Guarantee of Lending to Small and Medium Enterprises (Coronavirus Economic Response Package) Act 2020. Paragraph 3 and paragraph 13 tie coverage to guarantees granted under section 5 of that Act and to the Scheme’s rules governing the loan writing period. The Standard therefore operates as an administrative reporting adjunct to the Guarantee Act and Scheme rules: eligibility, guarantee scope and the loan writing period are functions of the Scheme rules and the Guarantee Act.

Cross‑reference to other Reporting Standards and definitions:

• ARS 701.0. The Standard repeatedly cross‑references Reporting Standard ARS 701.0 (ABS/RBA Definitions for the EFS Collection) for core definitions such as credit limit, credit outstanding, facility, domestic books consolidation and loan types. Paragraph 13 explicitly states that "domestic books has the meaning given by Reporting Standard ARS 701.0" and the ARF instruction guides instruct reporters to use ARS 701.0 definitions for numerous items. This creates a dependency: reporting entities must reconcile their data definitions and systems to ARS 701.0 to ensure consistency.

• ARS 920.8 (SME Recovery Loan Scheme - Flood). Paragraph 5 instructs entities that where the primary borrower is both COVID‑affected and flood‑affected in March 2021, reporting must be under ARS 920.8 rather than this Standard. That assigns discrete reporting channels for distinct overlapping adverse events.

Accounting standards and entity lender policies:

• Australian Accounting Standards. Item 1.4 of ARF 920.10 requires reporting of scheme‑backed loans "that have been written off and deducted as a loss per relevant Australian Accounting Standards." This ties portfolio reporting to accounting determinations and introduces an interaction where accounting judgments (write‑offs) affect reported portfolio loss amounts.

• Lender policies. Several definitions in the instruction guides rely on lender policies. For example, "impaired" is defined by the entity’s lender policies. The Standard thus accepts heterogeneity across entity credit policies for certain qualitative determinations, producing potential inconsistencies in impairment reporting unless lender policies adhere to common supervisory expectations.

Privacy, data sharing and administrative use:

• Paragraph 2 expressly authorises APRA to use the information to assist the Commonwealth Government administer the Scheme, and also for prudential purposes. That dual purpose implies data sharing between APRA and Commonwealth administrators and internal APRA use for supervision. The Standard does not itself set out privacy regimes or data sharing protocols; those will be governed by APRA’s statutory powers and relevant privacy laws and internal APRA arrangements.

Operational interactions:

• Securitisation: The Standard requires inclusion of securitised loans in reporting (Instruction Guides). Where loans have been securitised and ownership or servicing has changed, reporting obligations still fall on the entity required to submit on a domestic books consolidation basis per ARS 701.0. Reporting entities must therefore map off‑balance or transferred exposures back into their reporting consolidation.

In practice, compliance with ARS 920.10 requires harmonisation across the Guarantee Act, ARS 701.0 definitions, the entity’s accounting policies, lender policies, APRA’s electronic submission processes, and the privacy/data‑sharing architecture that governs information flows to the Commonwealth.

The text provided contains no formal amendment log, commencement dates for the Reporting Standard itself, or recorded prior versions. The instrument states the legal authority under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1) but does not include footnoted revision dates or a visible version history within the text supplied.

The Standard does, however, embed temporal limits and references that indicate its operational window and relationship to Scheme timing:

• The Standard applies to guarantees for loans made "from 1 October 2021 to 31 December 2021 or such date specified in the rules governing the Australian Government SME Recovery Loan Scheme" (paragraph 3). That clause implies the reporting obligation is tied to the Scheme’s loan writing period and therefore may cease or be superseded when the Scheme rules change.

• Paragraph 8 sets the effective due date rule for reporting periods ending on or after 30 September 2021, with a ten business day submission deadline. That gives an operational commencement marker for reporting cadence.

• The ARF instruction guides reference prior Guarantee Scheme phases (Phase 1: loans up to 30 September 2020; Phase 2: loans from 1 October 2020 to 30 June 2021), and Items 3.1-3.2 in ARF 920.10 gather refinanced funds that relate to those earlier phases. Those cross references show the Standard has been designed to operate alongside an earlier set of Scheme phases and their related reporting.

The absence of an explicit amendment schedule or dates in the provided instrument means users must look to APRA’s website or the Federal Register of Legislation to trace the Standard’s issuance date, amendment history, and any superseding instruments. Paragraph 14 confirms that references to Acts, Prudential Standards, Australian Accounting Standards or Reporting Standards are to be read "as in force or existing from time to time," which signals that the Standard expects to operate alongside evolving external instruments.

For practical purposes, entities should assume the Standard is linked to Scheme timing (paragraph 3), monitor APRA notifications for changes to reporting periods or methods (paragraphs 6 and 9), and consult APRA’s public registers for version‑control and amendment notices, because the instrument itself does not include a built‑in amendment log.

The Reporting Standard as supplied contains no litigation history, case citations, or references to judicial decisions. It does not name any court decisions, and there are no footnotes or annexes referencing litigation. The instruction guides and the Standard text are administrative in nature and focus on data collection, definitions and procedural requirements.

Given there is no litigation material in the text, practitioners wishing to understand any past legal challenges to APRA reporting instruments or to the Scheme’s reporting requirements must consult external sources: judicial decisions, tribunal records, or administrative appeals under the enabling legislation. The text does not provide such material, and therefore there is no litigation history to report from this instrument alone.

The Standard contains several operational and interpretative traps that could create compliance risk or surprising obligations if misunderstood. Each of the following is grounded in the text and instruction guides.

1. Inclusion of securitised loans. The ARF instruction guides explicitly require lenders to include loans that have been securitised in both ARF 920.10 and ARF 920.11 reporting (see multiple places in the instruction guides). Entities must therefore consolidate securitised exposures into the domestic books consolidation rather than excluding them because they were sold or transferred. Failing to map securitised loans back into reporting could cause under‑reporting.

2. Domestic books consolidation requirement. Paragraph 4 requires reporting "on a domestic books consolidation." The definition of "domestic books" is given by ARS 701.0. Entities with foreign branches or cross‑border group structures must ensure they understand ARS 701.0 consolidation rules to avoid misallocating loans to non‑domestic ledgers.

3. Flood‑affected loans routed elsewhere. Paragraph 5 requires that loans where the primary borrower was also adversely affected by March 2021 floods be reported under ARS 920.8 (Flood), not under this Standard. Lenders must therefore apply a dual‑screen to identify whether a loan is COVID‑only or COVID+flood affected and route records accordingly. Misclassification could cause duplicate reporting or omission.

4. Mixed interest and repayment types: count vs value. The Treatment of facilities instructions require counts to be allocated by predominant interest/repayment type by value, whereas the value of finance is apportioned across relevant dimensions. That difference means a single facility may be counted once under a predominant type while its monetary value is split across types. Data extraction logic needs to implement these rules precisely to match APRA's intended tabulation.

5. Measurement units and rounding. The forms require whole Australian dollars (no decimal) and percentages to two decimal places (e.g. 7.50). Inconsistent rounding or currency conversion rules can lead to formatting rejections or data quality queries.

6. Personal and business identifiers transmitted. ARF 920.11 Table 1 requires borrower names and ABNs (columns 2 and 3) and guarantor names (column 6). These are personal identifiers and, in the case of guarantors, may be natural persons. Entities must ensure privacy and data protection compliance in collecting, storing and transmitting these identifiers.

7. Impairment is entity‑defined. The instruction guide defines "Impaired" as "an impaired facility as defined by the entity’s lender policies." That creates heterogeneity across reporters: different internal credit policies can produce different impairment statuses, complicating cross‑entity comparability unless lenders’ policies are broadly aligned.

8. Refinancing and exclusion rules. Several items require exclusion of refinanced loans from some counts (e.g. Item 1.1 excludes loans refinanced). At the same time, Section Item 3 captures amounts refinanced from Phase 1 and Phase 2. Entities must track lifecycle events (approval, refinancing, termination, write‑off) to allocate amounts to the correct items and avoid double counting.

9. APRA discretion to change frequency. Paragraph 9 permits APRA to change reporting periods for particular entities. Lenders must maintain the ability to scale up reporting frequency quickly; IT systems and staffing plans should cater for that possibility.

10. Digital certificate requirement. Paragraph 12 requires digital signing "using a digital certificate acceptable to APRA." Entities must enrol in APRA’s digital certificate arrangements in advance and ensure continuity (certificate renewal, key management) to avoid submission failures.

11. Requirement for written exercise of APRA discretion. Paragraph 15 requires APRA to exercise powers or discretion in writing. Entities should seek written confirmations of any bespoke arrangements (frequency changes, extensions) and retain them for audit and compliance records.

12. Reliance on external definitions. Many core definitions are undefined in this instrument and deferred to ARS 701.0 or lender policies. Entities must ensure consistency with ARS 701.0 to avoid misinterpretation of terms such as "credit outstanding," "facility," "loan types," and "domestic books."

These "gotchas" create predictable points of failure: incomplete consolidation across securitisations, misrouted flood loans, inconsistent impairment definitions, formatting mismatches, and failure to secure a compliant digital certificate. Each arises directly from a clause or instruction in the text.

This section sets out an operational checklist and practical steps, grounded in the Standard and ARF instruction guides, to establish compliance practices.

1. Confirm coverage and inventory affected loans (paragraph 3; ARF definitions). Identify whether your entity is an ADI or RFC that received a Scheme guarantee under section 5 of the Guarantee Act, and list all loans written in the Scheme loan writing period (1 October 2021 to 31 December 2021, or the date in Scheme rules). Include loans previously securitised.

2. Segregate flood‑affected cases (paragraph 5). Implement a screening rule to detect primary borrowers who were both COVID‑affected and adversely affected by the March 2021 floods, and route those accounts to ARS 920.8 rather than ARS 920.10.

3. Map data fields to ARF 920.10 and ARF 920.11. Using the ARF instruction guides, create a data dictionary matching internal fields to ARF columns/items:

   • Portfolio aggregates: Items 1.1-1.7, 2.1-2.5, 3.1-3.2 (ARF 920.10).
   • Loan‑level fields: loan identifier, borrower name, ABN, loan value, interest rate, guarantor names, approval and final repayment dates, prior relationship flag, security/guarantee flag, refinancing flags and identifiers, loan type, repayment holiday length (ARF 920.11 Table 1). Respect unit rules: whole AUD, percentages to two decimal places.

4. Apply ARS 701.0 and lender policy definitions. Reconcile your internal definitions of credit limit, credit outstanding, facility, loan types, domestic books consolidation and past‑due definitions to ARS 701.0. For impairment, ensure your lender policy’s impairment definition is documented and consistently applied to ARF reporting.

5. Build extraction and apportionment logic. Implement logic to:

   • Count facilities once for number-of‑facilities columns, assign each facility to the predominant interest/repayment type by value for counts, and apportion amounts across types when reporting value.
   • Include securitised loans in totals and active account counts.
   • Exclude facilities entered and subsequently cancelled due to error.
   • Report loans refinanced separately per Item 1.3 and Items 3.1/3.2 as applicable.

6. Operationalise quality control and authorisation (paragraph 11). Put in place review workflows, reconciliations, change controls and authorisation steps that validate completeness and accuracy before submission. Maintain documentation of controls as evidence for APRA queries.

7. Implement digital signing and APRA submission method (paragraph 6; paragraph 12). Register for APRA’s electronic submission channel and obtain a digital certificate acceptable to APRA. Establish certificate lifecycle management (renewals, backups), and authorised signatory lists for digital signing.

8. Schedule reporting cadence and monitor for APRA changes (paragraphs 7-10). Configure monthly extraction runs aligned to calendar months. Build in a 10 business day turnaround for validation and submission for reporting periods ending on or after 30 September 2021. Maintain responsiveness for potential APRA requests to change frequency or grant extensions; any such directions should be in writing (paragraph 15).

9. Privacy, data security and record retention. Because ARF 920.11 contains borrower names, ABNs and guarantor names, align data handling with privacy obligations and internal data retention policies. Ensure secure transmission channels and access controls for staff preparing the reports.

10. Reconciliation to accounting records. Ensure that amounts reported as written‑off correspond to write‑offs taken under relevant Australian Accounting Standards (ARF 920.10 Item 1.4). Maintain reconciliation between ledger balances, credit outstanding (ARS 701.0), and reported values.

11. Documentation for APRA interactions. Keep copies of all submissions, internal sign‑offs, APRA communications (frequency changes, extensions), and any written exercises of discretion by APRA (paragraph 15). These form the compliance audit trail.

12. Test and audit. Conduct a pre‑submission dry run and post‑submission reconciliation. Maintain capability to answer APRA queries on specific loans using the loan identifier field (ARF 920.11 Column 1). Where loan identifiers or refinanced loan identifiers include multiple entries, ensure consistent delimiter usage (semicolon as instructed).

13. Prepare for supervisory follow‑up. Given paragraph 2’s statement that APRA may use the data for prudential purposes, include risk and capital reporting teams in the process so any anomalies can be quickly investigated and explained.

14. Contingency planning. Because APRA can change reporting frequency (paragraph 9), ensure resourcing flexibility and system scalability to move to more frequent submissions on request. Similarly, maintain the ability to respond to APRA data quality or completeness inquiries within short notice.

Following these steps maps the Standard’s prescriptions into an operational compliance programme: identify covered loans; align definitions to ARS 701.0 and lender policies; extract, apportion and reconcile portfolio and loan‑level fields; secure electronic transmission and digital sign‑off; and retain documentation of submissions and any APRA discretion exercised in writing.