Purpose and dual use. The Standard expressly states that the collected information is used to enable APRA to assist the Commonwealth Government to administer the Scheme, and “may also be used by APRA for prudential purposes” (para 2). That sets a dual administrative/prudential rationale: Commonwealth Scheme administration (claims, guarantee monitoring) and APRA’s supervisory information needs.

Reporting population and eligibility window. The reporting obligation applies only to ADIs and RFCs that are granted a guarantee under s 5 of the Guarantee Act for loans originated in Phase 2, defined as loans written from 1 October 2020 to 30 June 2021 (para 3; definitions in para 15). The Standard commences for reporting periods ending on or after 1 October 2020 (para 4).

Consolidation basis and coverage. All information must be provided “on a domestic books consolidation” (para 5). The meaning of “domestic books” is not restated in ARS 920.2; the Standard references Reporting Standard ARS 701.0 ABS/RBA Definitions for the EFS Collection for that definition (para 15). The instruction guides for the forms stress inclusion of loans that have been securitised (ARF 920.2: Item 1 and Item 2 instructions; ARF 920.3: include securitised loans).

Form hierarchy and granularity. Two distinct but linked returns are required:

• ARF 920.2 (portfolio information): portfolio totals from commencement to date (Item 1), positions at period end (Item 2), and the subset of Phase 2 approvals that refinance Phase 1 loans (Item 3). It asks for count and dollar value columns, write‑offs, recoveries, guarantee claims and paid claims, credit outstanding, unused credit, 30‑day past due counts/values, impaired exposures, and a weighted average customer rate (instructions govern calculation).
• ARF 920.3 (loan level details): one record per approved Phase 2 borrower in the reporting period, with 12 columns capturing identifiers, borrower ABN, approval and maturity dates, interest rate on origination, guarantor names, whether borrower had prior relationship with lender, security beyond guarantees, amount used to refinance Phase 1 loans, and original Phase 1 loan identifier where applicable (ARF 920.3 Table 1).

Data quality and authorisation. The Standard mandates internal systems, processes and controls developed by the ADI/RFC to assure completeness and reliability of reported information (para 11). Additionally, submissions require a digital signature via a certificate acceptable to APRA (para 12).

Flexibilities and APRA discretion. APRA may change reporting frequency up or down for particular institutions having regard to their circumstances and Commonwealth requirements (para 9); it may grant written extensions to due dates (para 10); and it may make minor variations to forms and instructions to correct technical or clarify application without changing substantive requirements (paras 13-14). Any exercise of APRA discretion under the Standard is to be made in writing (para 17).

Cross‑references. The Standard incorporates definitions and methodological references to ARS 701.0 for terms such as credit outstanding, credit limit, facility, securitised exposures and loans approved (para 15). It also references Australian Accounting Standards for write‑off treatment (ARF 920.2 Item 1.4 instruction) and requires use of specified measurement units and rounding (instruction guides).

Temporal scope. Phase 2 reporting covers loans written between 1 October 2020 and 30 June 2021 (para 15). For ARF 920.3, the first reporting period must include all loans originated from the start of Phase 2 (ARF 920.3, Reporting period instruction).

Interpretation principle. The Standard provides that references to Acts, Prudential Standards, Australian Accounting Standards or Reporting Standards are to be read as references to those instruments “as in force or existing from time to time” unless a contrary intention appears (para 16).

Directly affected entities. Paragraph 3 identifies the class of obliged reporters: all ADIs (as defined in the Banking Act 1959) and RFCs that are granted a guarantee under s 5 of the Guarantee of Lending to Small and Medium Enterprises (Coronavirus Economic Response Package) Act 2020 for loans in the Phase 2 period. The instrument does not impose obligations on entities that have not been granted a guarantee under s 5, nor on lenders outside the ADI/RFC definitions.

Internal stakeholders inside reporting entities. Compliance, credit operations, loan servicing, data management, IT, and legal teams will bear the operational burden of extracting portfolio totals and loan‑level fields, validating against definitions (many of which are defined in ARS 701.0 or the instruction guides), ensuring inclusion of securitised loans, and mapping internal identifiers to the required loan identifier field in ARF 920.3.

APRA and the Commonwealth. APRA is the recipient and processor of the data (paras 2 and 6). APRA will use the data to assist the Commonwealth administer the Scheme, per the stated purpose (para 2). APRA may also use the data for prudential supervision (para 2). The Commonwealth Government is a secondary intended beneficiary of the data for Scheme administration (para 2).

Borrowers and third parties. The loan‑level form (ARF 920.3) requires borrower identifiers (name and ABN), guarantor names, and information about security, prior relationships and refinancing of Phase 1 loans (columns 2-6, 9-12). While the Standard does not itself state downstream sharing arrangements, the collection of this granular borrower and guarantor data means institutions will transmit personally identifiable and business identifiers to APRA and, indirectly, the Commonwealth for Scheme purposes (see ARF 920.3 Table 1).

Securitisation counterparties and secondary markets. The instructions explicitly require inclusion of securitised loans in the returns (ARF 920.2 Item 1 and Item 2 instructions; ARF 920.3 specific definitions). For lenders that have securitised Scheme‑backed exposures, trustees, servicers and data teams must ensure securitised assets are represented in the domestic books consolidation provided to APRA.

Other regulatory interfaces. The Standard cross‑refers to ARS 701.0 for many definitions (para 15) and to Australian Accounting Standards for write‑off treatment (ARF 920.2 Item 1.4). Entities must reconcile reporting definitions with accounting, prudential and data definitions used elsewhere in their regulatory reporting to avoid inconsistency.

Who pays. Reporting costs are borne by the reporting ADIs and RFCs. The Standard requires electronic submission, secured digital certificate signatures and internal validation processes (paras 6, 11, 12; forms instructions set rounding/unit rules). The document gives APRA administrative tools to change reporting frequency (para 9) and to require more frequent reporting for particular entities; that can increase operational costs for targeted reporters.

Who decides. APRA decides the technical submission method (para 6) and can determine reporting frequency and extensions in writing (paras 9-10). APRA can also make minor, non‑substantive changes to forms and instructions and must notify reporters of those changes (paras 13-14). The Standard requires that any APRA discretion under the instrument be in writing (para 17).

Duties placed on reporting entities

• To report the data items specified in ARF 920.2 (portfolio information) and ARF 920.3 (loan level details) in respect of each reporting period, on a domestic books consolidation (para 5; ARF 920.2 and ARF 920.3 instruction guides).
• To submit the required information in electronic format via APRA’s Direct to APRA (D2A) application or another APRA‑notified method, and, when using D2A or other notified methods, to digitally sign the submission using a digital certificate acceptable to APRA (paras 6 and 12).
• To meet the baseline reporting cadence (each business week) and to submit returns within 10 business days after the end of the reporting period (paras 7-8). If the due date falls on a non‑business day, the due date stands (note in para 10).
• To maintain internal systems, processes and controls for the internal review and authorisation of information, to assure completeness and reliability before submission (para 11).
• To report in the specified units and formats: whole Australian dollars (no decimals) and percentages to two decimal places (ARF 920.2 and 920.3 unit of measurement instructions).
• To include securitised loans in the returns (ARF 920.2 Item 1 and Item 2 instructions; ARF 920.3 statement that securitised loans are included).
• To use the definitions provided (including those from ARS 701.0 and the instruction guides) for items such as credit outstanding, loans approved, credit limit, past due, impaired, recoveries, securitised, and Phase 1/Phase 2 classification (para 15 and forms).

APRA’s rights and discretions under the Standard

• To alter reporting periods for a particular ADI or RFC to require more frequent or less frequent reporting, having regard to the particular circumstances of the entity and Commonwealth requirements (para 9).
• To grant written extensions to due dates, with the new due date specified in the notice of extension (para 10).
• To make minor variations to forms and instructions to correct technical/errors or clarify instruction without changing substantive requirements, and to notify reporters of such variations (paras 13-14).
• To specify submission methods (para 6) and to require digital certification (para 12).
• To use the received information to assist the Commonwealth administer the Scheme and for prudential purposes (para 2).
• APRA must exercise any power or discretion conferred by the Standard in writing (para 17).

Specific content duties (examples drawn from forms)

• ARF 920.2 Item 1 requires cumulative portfolio totals for Phase 2 loans since Scheme commencement, including loans securitised; data to include counts and values for loans approved (1.1), loans with director/personal guarantee (1.2), loans cancelled/refinanced (1.3), write‑offs (1.4), recoveries (1.5), guarantee claims made (1.6), and guarantee claims paid (1.7).
• ARF 920.2 Item 2 requires period‑end snapshots for active Phase 2 accounts including credit outstanding (2.1), unused credit available (2.2), 30 days past due (2.3), impaired exposures (2.4) and weighted average customer rate (2.5 with explicit calculation).
• ARF 920.3 Table 1 requires per‑loan records for approved Phase 2 borrowers: loan identifier, borrower name and ABN, loan amount approved, interest rate at origination, guarantor names, approval and final repayment dates, indicators for prior lender relationship and security beyond guarantees, refinancing values and original Phase 1 loan identifiers (ARF 920.3 Table 1 columns 1-12).

Limits in the instrument

• The Standard does not itself prescribe civil or criminal penalties within the text provided; it operates as an APRA reporting instrument made under s 13 of the enabling Act (para 1). Enforcement, penalties or sanctions (if any) sit in the broader statutory framework and APRA’s administrative arrangements rather than in the Standard’s text.

Procedural rights for reporting entities

• Right to be notified where APRA makes minor variations to forms and instructions (para 14).
• Right to receive a written extension if APRA grants one (para 10).
• The Standard requires APRA to exercise discretion in writing (para 17), giving reporters a written record of any change in reporting frequency or requirements.

Instrument text on penalties. The Reporting Standard as provided does not contain explicit penalty, infringement, or sanction clauses. It states its statutory basis (made under s 13 of the Financial Sector (Collection of Data) Act 2001) but does not itself set out enforcement mechanisms or penalties (para 1). Accordingly, the Standard prescribes procedural and technical obligations (what to report, how, when and in what format), but is silent in its text as to the consequences for non‑compliance.

Administrative enforcement levers present in the Standard. The instrument builds in administrative controls that can function as levers over compliance:

• APRA’s control over submission method and authentication: the Standard requires electronic submission using D2A or another APRA‑notified electronic method, and requires digital signing using a certificate acceptable to APRA (paras 6 and 12). Control of the technical channel and certificate control are practical compliance gates for APRA.
• APRA’s discretion to change reporting frequency and to require more frequent reporting of a particular ADI or RFC where circumstances warrant (para 9). This permits APRA to increase intensity of oversight for entities of concern or to align reporting with Commonwealth needs.
• APRA’s ability to grant written extensions (para 10) provides a controlled administrative remedy to accommodate genuine reporting constraints.
• The Standard requires internal quality control systems in the reporting entity (para 11). APRA can reasonably expect documentation of these systems and may follow up in supervisory engagement.

Where to look for sanctions. Because the Standard does not specify penalties, entities should treat the Standard as a mandated regulatory return that sits within the broader legal framework under which APRA operates. Practitioners should check the enabling legislation (the Financial Sector (Collection of Data) Act 2001), and any APRA enforcement or compliance manuals, for the statutory or administrative consequences of non‑compliance with reporting obligations. The Standard’s paragraph 1 makes clear the instrument is issued under s 13 of that Act; the Act itself may contain enforcement provisions not reproduced here.

Operational accountability. The requirement for internal authorisation, quality controls, and a digitally signed submission creates an audit trail and allocates internal responsibility to an officer who signs the return (para 11-12). That allocation supports APRA’s ability to seek explanations and documentary evidence in supervisory engagement.

Notification and change control as soft enforcement. APRA’s ability to make minor variations to forms or instructions and notify reporters (paras 13-14) is a compliance management tool: it allows APRA to refine the reporting specification without reissuing a new Standard or declaring new substantive obligations, while preserving the obligation to notify affected reporters.

Practical implication for reporting entities. Even though the Standard does not set out explicit fines, the combination of statutory backing (para 1), APRA’s technical controls, the requirement for written exercise of discretion (para 17), and usual supervisory practices means that non‑compliance is likely to trigger supervisory follow‑up. Entities should therefore assume that failure to meet the Standard’s obligations will attract APRA engagement and potential statutory remedies available to APRA under its enabling statutes (the Standard itself does not enumerate those remedies).

Cross‑references and incorporated definitions. The Standard explicitly imports definitions from other instruments and refers to external statutes:

• ADI is defined by reference to the Banking Act 1959 (para 15).
• APRA is defined by reference to the Australian Prudential Regulation Authority Act 1998 (para 15).
• The Scheme is the guarantee under the Guarantee of Lending to Small and Medium Enterprises (Coronavirus Economic Response Package) Act 2020; the reporting obligation attaches only to lenders who are granted a guarantee under s 5 of that Act (para 3 and para 15).
• Several technical terms such as credit limit, credit outstanding, facility, securitised, loans approved, past due, recoveries are defined by reference to Reporting Standard ARS 701.0 ABS/RBA Definitions for the EFS Collection (para 15 and repeated in form instructions).
• ARF 920.2 Item 1.4 expressly refers to Australian Accounting Standards for the treatment of write‑offs and losses.

Interpretation clause. Paragraph 16 provides that references to Acts, Prudential Standards, Australian Accounting Standards or Reporting Standards are to be read as references to the instruments “as in force or existing from time to time”, unless a contrary intention appears. That means changes to the referenced external instruments will affect the operation and interpretation of definitions and reporting expectations in ARS 920.2.

Data Privacy and other regulatory interfaces. The Standard requires the submission of borrower names, ABNs and guarantor names in ARF 920.3 (Table 1 columns 2-3 and 6), which are personal and business identifiers. While the Standard does not itself discuss privacy law or data sharing arrangements, entities should be aware that collecting and transmitting personally identifiable information to APRA and the Commonwealth will interact with privacy and data protection obligations under Commonwealth privacy laws and any internal privacy policies. The Standard does not map or limit such interactions in its text; practitioners should therefore reconcile this reporting requirement with obligations under the Privacy Act and internal privacy governance (note: the Standard itself does not cite the Privacy Act).

Accounting and prudential reporting alignment. The instrument explicitly requires conformant treatment of write‑offs “as a loss per relevant Australian Accounting Standards” (ARF 920.2 Item 1.4). Other items (e.g. impaired, past due, credit outstanding) reference ARS 701.0 and lender policies. Entities must reconcile these definitions with accounting and prudential reporting rules used in other statutory returns.

Securitisation and consolidation. The Standard instructs reporters to include securitised loans in their domestic books consolidation for the returns (ARF 920.2 items and ARF 920.3 statements). That interacts with any accounting or prudential treatment of securitised exposures elsewhere; entities will need to map how securitised exposures are represented in their domestic books and include them accordingly.

Scheme administration and sub‑national interactions. The Standard’s explicit purpose includes assisting the Commonwealth administer the Scheme (para 2). The Standard does not purport to change substantive Scheme eligibility or guarantee mechanics; it is a data collection tool to support administration. Any decisions under the Guarantee Act remain subject to the Guarantee Act itself. The Standard’s reporting may feed administrative decisions about guarantee claims, but the Standard does not itself modify Scheme rights or obligations under the Guarantee Act.

Discretion and written exercise. Paragraphs 9 and 17 require APRA to consider particular circumstances when varying reporting frequency and to exercise discretion in writing. That creates a documented interaction between APRA’s administrative discretion and entities’ operational requirements, and means that where reporting obligations change, institutions should receive written APRA directions reflecting altered obligations.

No express interaction with criminal or civil enforcement in the text. The Standard does not detail how breaches are enforced under criminal or civil law, so for any enforcement mechanism practitioners must look to the enabling statute (the Financial Sector (Collection of Data) Act 2001) and APRA’s enforcement powers under its governing legislation and policies, none of which are set out in the Standard itself.

What the instrument itself records. The provided text does not include an explicit amendment history table, version log, or dates of amendment other than the commencement statement in paragraph 4: the Standard “applies to reporting periods ending on or after 1 October 2020” (para 4). The text repeatedly labels the instrument as “Reporting Standard ARS 920.2” and includes the instruction guides for ARF 920.2 and ARF 920.3. There is no internal record in the provided extract of prior versions or amendment dates.

How changes are authorised. The Standard is made under s 13 of the Financial Sector (Collection of Data) Act 2001 (para 1). Paragraph 13 gives APRA power to make minor variations to forms and instructions to correct technical, programming, logical errors or clarify instructions without changing substantive requirements; paragraph 14 requires APRA to notify each ADI or RFC if it makes such a variation. Paragraph 16 provides the interpretative rule that references to Acts, Prudential Standards and Reporting Standards are to be read as referring to those instruments “as in force or existing from time to time”. Paragraph 17 requires that where the Standard provides for APRA to exercise a power or discretion, that exercise is to be in writing.

Practical reading. In the absence of an amendment log in the provided text, practitioners should treat the document as current for reporting periods ending on or after 1 October 2020 and should expect any non‑substantive tweaks to forms or clarifications to be communicated directly by APRA (paras 13-14). For substantive amendments to reporting requirements, the enabling Act and APRA processes would dictate the route; the Standard does not lay out a multilayer amendment schedule or version history within its own text.

Recommended step for practitioners. Because the Standard references other instruments “as in force or existing from time to time” (para 16) and expressly allows APRA to make minor variations (para 13), firms should maintain an APRA‑notifications monitoring process and retain written APRA communications about any changes to reporting frequency, extensions or form clarifications (paras 9-10, 13-14, 17). Also check APRA’s D2A release notes and the public APRA website for any updated instruction guides or errata.

Documented litigation. The text provided contains no record of litigation arising from, or about, ARS 920.2, ARF 920.2, or ARF 920.3. There are no cases named in the instrument, and no judicial commentary or administrative tribunal decisions referenced.

Implication for practice. Because the Standard is an administrative reporting instrument without recorded litigation in the provided text, legal risk around interpretation is primarily operational and contractual rather than litigated. However, the absence of litigation history in this document does not preclude disputes arising in the future regarding interpretation of definitions (for example, what constitutes “domestic books” under ARS 701.0) or the boundaries of APRA’s discretionary powers (paras 9 and 17). Where statutory enforcement or sanction questions arise, those will be determined by reference to APRA’s enabling legislation and any relevant administrative law or judicial review principles not canvassed in the Standard itself.

What to do if a dispute arises. The Standard requires APRA to exercise its discretion in writing (para 17) and to notify reporters of minor variations (para 14), which creates a paper trail. If a dispute occurs over reporting requirements or an APRA direction, the written record contemplated by the Standard will be relevant in any administrative review or legal challenge. Practitioners should preserve written correspondence, extension notices (para 10), and forms/instruction change notices (para 14).

Weekly baseline cadence and tight deadline. The Standard sets a default reporting cadence of each business week (Monday to Friday) (para 7) and a general due date of within 10 business days after the end of the reporting period (para 8). For many institutions this is a rapid turnaround for loan‑level extraction, validation, quality control and D2A submission. APRA can require more frequent or less frequent reporting for particular ADIs/RFCs (para 9), and any change will be in writing (para 17), but the baseline remains weekly.

Domestic books consolidation requirement. Paragraph 5 requires submissions “on a domestic books consolidation”. The meaning of domestic books is provided in ARS 701.0 (para 15). Reporting entities must ensure that their mapping to the domestic books consolidation used for other EFS/ARS reporting is consistent; mis‑alignment between different statutory returns can create reconciliation issues.

Inclusion of securitised loans. The instruction guides explicitly require inclusion of securitised loans in both ARF 920.2 and ARF 920.3 (ARF 920.2 Item 1 and Item 2 instructions; ARF 920.3 directive to include securitised loans). For banks that have transferred loans off‑balance‑sheet through securitisation structures, this will require cross‑functional work to identify and report those exposures on a domestic books basis.

Loan‑level personal and business identifiers in ARF 920.3. The loan‑level form requires primary borrower name, primary borrower ABN, guarantor names and loan identifiers (ARF 920.3 Table 1, columns 2-3 and 6). Institutions should confirm internal privacy, consent and disclosure obligations before transmitting personally identifiable information to APRA and the Commonwealth, and should record the legal basis for transmission. The Standard itself does not address privacy law interactions.

Treatment of cancelled or refinanced loans and inclusion/exclusion rules. The instruction guides set rules that can be counter‑intuitive:

• Item 1.1 (ARF 920.2) requires reporting loans approved as borrower‑accepted commitments, and to include loans that have terminated or matured but to exclude loans that are cancelled or refinanced (ARF 920.2 Item 1.1 instruction).
• Item 1.3 requires reporting loans cancelled or refinanced (ARF 920.2 Item 1.3).
• ARF 920.3 columns 11-12 require reporting the value of the Phase 2 loan amount used to refinance an existing Phase 1 loan and the loan identifier of the original Phase 1 loan (ARF 920.3 Table 1 columns 11-12).

Those cross‑references mean that the same economic event (a Phase 2 approval that refinances a Phase 1 loan) will appear in portfolio counts both as an approval and be flagged as a refinance; careful mapping is required to avoid double counting across items where the instructions demand inclusion or exclusion depending on the specific item.

Weighted average customer rate calculation. ARF 920.2 Item 2.5 gives an explicit formula: sum of 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. Mis‑application (for example using balances rather than drawn amounts, or including cancelled loans) will produce inconsistent results. The instruction emphasises loans approved in the current portfolio; practitioners must ensure the population of “loans approved” aligns with ARS 701.0 definitions.

Unit of measurement rounding rules. Both forms require whole Australian dollars (no decimals) and percentages to two decimal places (forms’ Unit of measurement instruction). That may create rounding and aggregation differences when reconciling with internal FRY or accounting systems that use cents and floating‑point percentages; mapping must normalise rounding rules.

Digital certificate requirements and authentication. Paragraph 12 requires the officer submitting to digitally sign with a digital certificate acceptable to APRA. Firms must have the right digital certificate, ensure expiry dates are managed, and confirm technical compatibility with D2A or the APRA‑notified submission method. APRA offers the D2A application (note in para 6), but alternate web methods may be notified in writing by APRA.

APRA’s ability to make minor variations without substantive change. Paragraph 13 allows APRA to make minor variations to forms and instructions to correct technical or logical errors or to clarify application without changing substantive requirements. Paragraph 14 requires APRA to notify reporters of such changes. However, “minor” is not defined; reporters should expect that some clarifications could affect parsing or ETL processes and plan for rapid technical patches.

The “as in force from time to time” interpretation clause. Paragraph 16 means that referenced definitions and standards can change over time and will affect interpretation. For example, if ARS 701.0 definitions were amended after a reporting period, questions may arise about historical reporting. Entities should maintain a versioned mapping of definitions used in each reporting period.

Inclusion of loans that “have terminated or matured”. ARF 920.2 Item 1.1 requires inclusion of loans that have terminated or matured, which means the portfolio totals are cumulative from commencement and not limited to active loans (Item 1 vs Item 2 distinction). Practitioners must understand the difference between “portfolio to date” and “portfolio as at end of period” items.

APRA discretion to change frequency upwards. Paragraph 9 permits APRA to require more frequent reporting for particular entities. Firms should assume that APRA could demand daily or multi‑weekly reporting in exceptional cases; the Standard provides that power and thus firms should design data pipelines with some scalability in mind.

No penalties specified in the Standard itself. The absence of stated penalties in the provided text is a practical gotcha: institutions should not interpret silence as an absence of consequences. The Standard is made under statutory authority (para 1), and APRA retains administrative options to pursue non‑compliance through the broader legal framework.

Operational checklist (minimum actions to be ready)

1. Confirm applicability:

   • Verify whether the entity is an ADI within the Banking Act 1959 definition or an RFC, and whether it was granted a guarantee under s 5 of the Guarantee Act for Phase 2 loans (para 3; para 15 definitions).

2. Determine consolidation base:

   • Map the domestic books consolidation to be used for the returns. Use Reporting Standard ARS 701.0 for the definition of “domestic books” (para 5 and para 15).

3. Data extraction and mapping:

   • Establish extraction logic for ARF 920.2 items: cumulative portfolio totals (Item 1), period‑end positions (Item 2), and refinances of Phase 1 by Phase 2 approvals (Item 3). Align each item with the definitions in the instruction guide and ARS 701.0 (ARF 920.2 Item instructions; para 15).
   • For ARF 920.3, prepare one row per approved Phase 2 borrower per reporting period containing the 12 required columns (loan identifier; borrower name and ABN; loan value approved; interest rate; guarantor names; approval/final repayment dates; prior relationship flag; security beyond guarantee flag; Phase 2 refinancing amount; Phase 1 loan identifier) (ARF 920.3 Table 1).
   • Ensure securitised loans are included in both portfolio and loan‑level returns (ARF 920.2 Item 1/2 instructions and ARF 920.3 statements).

4. Quality control and authorisation:

   • Implement internal systems, processes and controls for review and authorisation of returned information per paragraph 11.
   • Assign responsible officers who can digitally sign returns and maintain a signatory register and certificate lifecycle management (digital certificates must be acceptable to APRA; para 12).

5. Electronic submission capability:

   • Install and validate the Direct to APRA (D2A) application or confirm readiness for any APRA‑notified web submission method (para 6). Coordinate IT and security teams to manage certificates and submit test files where APRA provides test environments.

6. Scheduling and timelines:

   • Configure weekly data runs to capture each business week (Monday to Friday) as the default reporting period (para 7) and to deliver submissions within 10 business days after period end (para 8).
   • Build capacity to respond to an APRA direction for alternative reporting frequency (para 9) and to process APRA extension notices (para 10).

7. Data formatting and rounding:

   • Ensure monetary values are in whole Australian dollars (no decimal places) and percentages are expressed to two decimal places as required by the instruction guides (Unit of measurement instructions).

8. Definitions and reconciliations:

   • Reconcile ARF 920.2 and ARF 920.3 populations with internal accounting and regulatory reporting data, using ARS 701.0 and relevant Australian Accounting Standards for consistent definitions of credit outstanding, credit limit, loans approved, past due, impaired, recoveries, and write‑offs (para 15; ARF 920.2 Item 1.4).

9. Recordkeeping:

   • Retain written records of APRA notifications about reporting frequency changes, extensions, or form instruction variations (paras 9-10, 13-14, 17). Keep copies of signed submissions and evidence of internal authorisation steps referred to in para 11.

10. Privacy and governance checks:

    • Where ARF 920.3 requires borrower and guarantor names and ABNs, run privacy impact assessments and ensure transmission to APRA aligns with internal privacy policies and legal obligations. Document legal bases for sharing personally identifiable information.

11. Testing and exception handling:

    • Test file submissions and the D2A workflow in advance. Prepare exception processes for rows failing validation, and for APRA feedback loops. Identify who within the organisation will liaise with APRA on data quality queries.

12. Monitoring APRA communications:

    • Establish a monitoring process for APRA notifications about minor variations to forms and instructions (para 13-14). Record and implement any clarifications quickly, given the weekly cadence.

Specific mapping notes and examples drawn from the instruction guides

• Loans approved vs loans cancelled/refinanced: ARF 920.2 Item 1.1 instructs inclusion of loans approved (borrower‑accepted commitments) and to include loans that have terminated or matured but to exclude loans that are cancelled or refinanced (Item 1.1 instruction). Item 1.3 requires reporting loans cancelled or refinanced. Ensure logic categorises each facility into exactly one of these buckets as the form intends.
• Weighted average customer rate: Implement the formula exactly as given in ARF 920.2 Item 2.5 instructions: sum(drawn amount × interest rate) / sum(drawn amounts) for all loans approved at the end of the relevant period. Confirm that “drawn amounts” are defined consistently with ARS 701.0.
• Guarantor names formatting: ARF 920.3 Column 6 requires guarantor names separated by semicolons and “Nil” if there are none. Build extraction rules to produce the exact text format APRA expects.
• Prior relationship indicator: ARF 920.3 Column 9 requires “Yes” if the customer had an active lending relationship with the entity before the Scheme loan’s commencement, and “No” otherwise; transactional deposit‑only relationships should be coded as “No”. That requires cross‑checking CRM and loan origination data.
• Security beyond guarantees: ARF 920.3 Column 10 requires a yes/no indicator for security in addition to a personal/director guarantee.
• Refinancing linkage: ARF 920.3 Columns 11-12 require reporting Phase 2 amounts used to refinance Phase 1 loans and the original Phase 1 loan identifier. A robust mapping between legacy loan identifiers and new Phase 2 loans is necessary to populate this linkage.

Governance and audit trail

• Document the internal review and authorisation rules required under para 11, including roles and responsibilities, validation checks, reconciliation procedures and escalation protocols for data disagreements.
• Maintain the digital signing certificate lifecycle: issuance, location, rotation and expiry, to prevent last‑minute submission failures under para 12.
• Keep a versioned audit trail of reporting logic and ETL scripts aligned to the reporting period definitions, including which ARS 701.0 definitions were used for each reporting period (para 16 implication).

Contingency planning

• Be ready to scale up reporting frequency if APRA exercises para 9 discretion, and have contingency staff for weeks with high data volumes or reconciliation issues.
• Prepare a fast‑response process to implement minor form or instruction clarifications from APRA (paras 13-14), bearing in mind that even “minor” clarifications can require code changes.

Record retention and evidence for future queries

• Given that APRA may use the information for prudential purposes (para 2), retain source data, reconciliations and authorisation logs for a period consistent with APRA’s usual supervisory records expectations (note: retention periods and supervisory document requirements should be checked against APRA guidance and the enabling statutes; the Standard itself does not set a retention period).

Final practical note. The Standard creates a recurring, operational data obligation that is technical and granular. Build a repeatable, auditable pipeline that covers the data capture, transformation, validation and signed D2A submission steps, and institute a governance loop to record APRA communications about frequency changes, extensions and instruction clarifications.