The instrument organises the reporting task around a small set of concepts that materially shape what must be collected, how it is measured, and which loans are in-scope.

• Scheme-specific scope: The concept of a "Flood scheme-backed loan" is central and defined in both ARF 920.8 and ARF 920.9 instruction guides. A Flood scheme-backed loan is one where the primary borrower (a) was adversely affected by the March 2021 floods; (b) was not a recipient of the JobKeeper payment between 4 January 2021 and 28 March 2021; and (c) is not adversely economically affected by the Coronavirus pandemic (definition repeated across the forms). This three-part definition narrows the universe of loans to those tied specifically to the flood event and not to overlapping federal pandemic support measures (see ARF 920.8 definitions and ARF 920.9 definitions).

• Dual-level reporting: The Standard requires both portfolio-level and loan-level reporting. ARF 920.8 collects portfolio aggregates "to date" (Item 1), period-end positions and ratios (Item 2), and refinancings from earlier Guarantee Scheme phases (Item 3). ARF 920.9 collects loan-level details for each approved borrower in the last reporting period, with 15 explicit columns covering identifiers, ABNs, guarantor names, loan values, interest rates, repayment schedules and security/refinance flags (ARF 920.9 Table 1).

• Treatment of securitisation and refinanced loans: Securitised loans are explicitly to be included in counts and values (e.g., “Include loans that have been securitised,” multiple places in the instruction guides). Refinanced loans are treated differently depending on context: Item 1.3 records loans refinanced, while Item 1.1 and 1.2 exclude loans refinanced after approval. Item 3 specifically requests amounts refinanced from Phase 1 and Phase 2 of the Guarantee Scheme (see ARF 920.8 Items 1-3).

• Measurement and reporting rules: Units and rounding are prescribed , whole Australian dollars for monetary amounts, and percentages expressed as whole numbers to two decimal places (instruction guides). When counting facilities the instruction guides require reporting each facility once; where a facility contains mixed interest rate or repayment types, the number is reported according to the predominant type by value while values are apportioned across dimensions.

• Governance and controls: The Standard requires internal processes and controls for internal review and authorisation of reported information (para 14), and mandates digital signing by an officer or agent using an APRA-acceptable digital certificate (para 15). APRA retains authority to alter reporting cadence for a particular entity in writing (para 12) and to grant extensions (para 13). APRA’s powers and discretions under the Standard are to be exercised in writing (para 18).

• Interaction with other reporting requirements: The Standard sets out cross-references to ARS 920.6 (JobKeeper) and ARS 920.10 (broader SME Recovery Loan Scheme where borrower is COVID-affected), and to Reporting Standard ARS 701.0 for definitions such as domestic books and credit outstanding (paras 6-7 and para 16). It also treats the previous incarnation of ARS 920.8 (Determination No. 43 of 2021) as having satisfied reporting obligations for certain earlier periods (para 8).

These concepts define how lenders must identify in-scope loans, what data to extract, how to measure and format the data, the internal governance required prior to lodgement, and the conditions under which APRA may demand a different cadence or grant extensions. The definitions ensure that overlapping federal assistance (JobKeeper, pandemic-affected classification) does not cause duplicate or misdirected reporting by funneling those loans to other ARS instruments.

ARS 920.8 applies to a specific subset of financial institutions and loans. Paragraph 3 makes the application clear: it applies to "all authorised deposit-taking institutions (ADIs) and registered financial corporations (RFCs) who are granted a guarantee under section 60 of the Public Governance, Performance and Accountability Act 2013 in relation to the Australian Government SME Recovery Loan Scheme, for lending to businesses that are located or operating in eligible Local Government Areas (LGAs) impacted by the floods in March 2021." In short, the instrument affects:

• Lenders: Only ADIs and RFCs that have actually been granted a government guarantee under the Scheme. Entities that did not receive such a guarantee are not captured by the Standard. The definition of ADI is incorporated by reference to the Banking Act 1959 (para 16).

• Loans: Only loans meeting the Flood scheme-backed loan definition are in-scope , primary borrower adversely affected by the March 2021 floods, not JobKeeper recipients in the specified window, and not loans where the primary borrower is primarily identified as being adversely economically affected by the Coronavirus pandemic (definitions in ARF 920.8 and ARF 920.9).

• Internal teams and functions within lenders: Operationally, the reporting requirement will involve credit origination and portfolio systems (to identify Flood scheme-backed loans, approval dates, final repayment dates, interest rates, securitisation status, and refinanced loans), risk and provisioning teams (to report impaired and past-due amounts per Item 2), legal/compliance (to verify guarantor names, security arrangements, and to ensure digital-authorisation processes), and IT/data teams (to prepare the electronic submission in APRA’s format and to apply the unit-of-measurement and apportionment rules in the instruction guides).

• External counterparties indirectly affected: Borrowers do not have duties in the Standard, but ARF 920.9 requires borrower-identifying data , primary borrower name and ABN, and guarantor names , to be reported (ARF 920.9 Table 1 columns 2-3 and 6), meaning that lenders will need to process and transmit personally identifying business information and possibly personal guarantor details as part of the submission.

• Regulators and the Commonwealth Government: APRA receives the data and may use it both to assist Commonwealth administration of the Scheme and for APRA’s prudential purposes (para 2). The Commonwealth, as guarantor under the Scheme, is an intended recipient of the aggregated and loan-level information via APRA to support Scheme administration.

Geographic and temporal limits are also material: the loans must relate to LGAs impacted by the March 2021 floods, and the Standard applies to reporting periods ending on or after 31 October 2021 (para 4). Additionally, lending that overlaps with JobKeeper status or broader pandemic-affected status is redirected to other ARS instruments for particular time windows (paras 6-7), so lenders must be able to map loans to the correct reporting instrument.

Finally, APRA’s discretion to change reporting frequency (para 12) and to grant extensions (para 13) means that specific lenders may face higher or lower reporting cadence depending on their circumstances and Commonwealth requirements. That discretion can expand or reduce the practical burden on individual institutions beyond the monthly default.

The instrument imposes procedural duties on in-scope reporting entities and confers operational discretions on APRA; it does not itself set out substantive borrower or lender rights under the Scheme.

Duties imposed on ADIs and RFCs

• Identification and submission duty: An ADI or RFC to which the Standard applies must provide APRA with the information required by ARF 920.8 and ARF 920.9 for each reporting period on a domestic books consolidation (para 5). The obligation is to report both portfolio-level and loan-level information as specified in the instruction guides.

• Scope-mapping duties: Lenders must determine whether each loan is a "Flood scheme-backed loan" (instruction guides) and whether other ARS instruments apply , e.g., ARS 920.6 for JobKeeper recipients between 4 Jan and 28 Mar 2021 for lending up to and including 30 Sep 2021, and ARS 920.10 for borrowers adversely economically affected by the pandemic from 1 Oct 2021 (paras 6-7). This requires lenders to map borrower status against JobKeeper and pandemic-affected criteria to select the correct reporting path.

• Timing duty: By default reporting periods are calendar months (para 10) and returns must be made within 10 business days after period end (para 11). If a stated due date falls on a non-business day, the due date nonetheless applies (note after para 13). APRA can change reporting frequency for particular entities (para 12), in which event the lender must comply with that revised cadence.

• Form and method duty: Submissions must be electronic via APRA’s website or a method notified by APRA (para 9). All returned information must be digitally signed by an officer or agent using a digital certificate acceptable to APRA (para 15).

• Data governance duty: All reported information must be subject to the reporting entity’s internal review and authorisation processes to assure completeness and reliability (para 14). The instruction guides add explicit measurement, rounding and treatment rules (e.g., whole dollars, 2-decimal percentages, apportionment rules, inclusion/exclusion of securitised and cancelled facilities, etc.).

APRA’s discretions and rights

• Variability of reporting frequency: APRA may change reporting periods for a particular ADI or RFC, to require more frequent or less frequent reporting, having regard to the particular circumstances of the ADI or RFC and the requirements of the Commonwealth Government (para 12). The practical effect is that APRA can tailor the burden and granularity of data collection to entity-specific or policy needs.

• Extension of due dates: APRA may, in writing, grant an ADI or RFC an extension of a due date (para 13). The new due date is what the written notice specifies.

• Exercise of powers in writing: Where the Standard provides for APRA to exercise a power or discretion, that exercise is to be in writing (para 18). This creates an administrative record and a degree of procedural formality.

Rights and limitations explicit in the instrument

• Use of information: The Standard states that information is used to enable APRA to assist the Commonwealth Government administer the Scheme and may also be used by APRA for prudential purposes (para 2). The instrument therefore authorises APRA to use submitted data beyond Scheme administration for prudential supervision.

• Scope limitation: Paragraph 3 limits the Standard’s applicability to ADIs and RFCs that are guaranteed under s 60 of the PGPA Act for Scheme lending in eligible LGAs impacted by the March 2021 floods. Entities outside this class are not required to report under ARS 920.8.

• No express penalty clauses in the Standard text: The Standard itself does not set out civil or criminal penalties or enforcement mechanics in the text provided. The instrument is made under the Financial Sector (Collection of Data) Act 2001; enforcement mechanisms and possible sanctions relating to data collection will be enacted under that parent statute and APRA’s statutory framework rather than within the Standard’s text (the Standard does not include penalty paragraphs).

Operational implications of these duties and rights

• The reporting duties impose recurring operational tasks (monthly by default) and require systems that can extract both portfolio aggregates and loan-level PII/data (primary borrower name, ABN, guarantor names). Entities must also implement internal review processes and manage digital certificates for authorised submission sign-off.

• APRA’s discretion to require different frequencies or grant extensions creates variability in the compliance burden and the need for systems capable of more frequent extracts where demanded.

• APRA’s explicit authorisation to use data for prudential purposes means that submitted information is not limited to Scheme administration and could inform APRA supervisory work.

The Reporting Standard text does not contain express penalty provisions or specify enforcement mechanics for non-compliance within its paragraphs. The Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (para 1), which is the statutory head of power for the instrument. Enforcement and penalty mechanisms for failure to comply with reporting standards are generally governed by the parent legislation and APRA’s statutory and administrative enforcement framework rather than within the content of a reporting standard; the Standard itself imposes duties (for example, to submit by a due date and to apply internal quality-control processes) but does not describe sanctions in the printed text.

Relevant enforcement and procedural features evident in the Standard

• Formality of APRA discretion: APRA must exercise powers or discretions under the Standard in writing (para 18). APRA must also grant extensions or change reporting frequency in writing (paras 12-13). These procedural requirements produce an administrative record for any enforcement or supervisory follow-up.

• Requirements that create audit trail: The Standard requires digital signing of submissions by an officer or agent using a digital certificate acceptable to APRA (para 15) and requires that all reported information be subject to the entity’s internal review and authorisation processes (para 14). These requirements enable APRA to audit the provenance and authorisation of returns and to follow up on data quality issues.

• Deemed prior reporting: The Standard deems reporting made under the former ARS 920.8 for several earlier reporting periods to have satisfied the current Standard (para 8). This reduces the risk of enforcement action for those historical periods because APRA has effectively recognised prior compliance.

What the instrument does not set out

• The Standard does not set out monetary fines, civil penalties, criminal offences, or specific enforcement tools (e.g., directions powers, administrative penalties) within its own text. For those mechanisms, practitioners must consult the Financial Sector (Collection of Data) Act 2001 and other relevant statutes (for example, the APRA Act and the Banking Act) and APRA policy and enforcement statements to identify the practical consequences of non-compliance.

Practical takeaway for compliance teams

• Because the Standard itself lacks internal enforcement detail, compliance teams should map the Standard’s duties to the enforcement regime in the parent legislation (Financial Sector (Collection of Data) Act 2001) and APRA’s broader supervisory and enforcement policies. In practice, APRA’s ability to change reporting frequency (para 12) and to require written extensions (para 13) means the regulator can escalate scrutiny by increasing reporting granularity, and the formal signing requirements (para 15) create traceability for supervisory action if data quality or timely submission issues arise.

The Reporting Standard is not standalone; it embeds references and cross-links to other reporting standards, to APRA and sectoral statutes, and to definitions in ARS 701.0. The instrument itself makes a number of legal incorporations and interaction points.

Statutory basis and institutional context

• Parent statute: ARS 920.8 is made under s 13 of the Financial Sector (Collection of Data) Act 2001 (para 1). That Act is the statutory foundation for APRA’s data-collection powers. Therefore, the enforcement and legal effect of a failure to report will be determined by the parent Act and APRA’s statutory powers as developed under that Act.

• APRA and ADI definitions: The instrument defines "APRA" as the Australian Prudential Regulation Authority established under the Australian Prudential Regulation Authority Act 1998 and defines "ADI" by reference to the Banking Act 1959 (para 16). Those cross-references import the statutory meanings and obligations from those Acts into the identification of reporting entities.

Cross-references to other Reporting Standards and instruments

• ARS 701.0: The Standard repeatedly cites Reporting Standard ARS 701.0 for key definitions including "domestic books", "credit outstanding", "facility", "past due", "recoveries", and "securitised" (see para 16 and the instruction guides). Thus, practitioners must refer to ARS 701.0 to interpret measurement concepts and to ensure consistency with APRA’s broader collections.

• ARS 920.6 and ARS 920.10: ARS 920.8 specifically directs lenders to use ARS 920.6 for loans where the primary borrower was a recipient of JobKeeper in the specified period (4 Jan-28 Mar 2021) for lending up to and including 30 Sep 2021 (para 6). It also directs lenders to use ARS 920.10 for loans from 1 Oct 2021 where the primary borrower is adversely economically affected by the Coronavirus pandemic (para 7). These cross-references create a partitioning ruleset to avoid duplicate reporting and to ensure loans connected to pandemic relief are made to the appropriate data collection instrument.

• Guarantee mechanics: ARS 920.8 applies to lenders "who are granted a guarantee under section 60 of the Public Governance, Performance and Accountability Act 2013 in relation to the Australian Government SME Recovery Loan Scheme" (para 3). The Scheme’s guarantee therefore originates from a different statutory framework (the PGPA Act), and the Standard presumes that lenders participating under that guarantee will be the reporting population. The Standard does not itself create guarantees or define their legal effect; it relies on the PGPA Act’s guarantee-granting mechanics.

Administrative interactions

• APRA discretion and Commonwealth requirements: APRA may change reporting frequency having regard to "the particular circumstances of the ADI or RFC" and "the requirements of the Commonwealth Government of Australia" (para 12). This creates an explicit administrative linkage between APRA’s prudential collection and Commonwealth policy needs. APRA’s reporting requirements, therefore, can be adjusted to satisfy external policy requirements.

• Use of data: The Standard authorises APRA to use the information both to assist the Commonwealth Government administer the Scheme and for APRA’s prudential purposes (para 2). That dual-use characterises the law’s interaction: data flow from regulated entities to APRA becomes an input both for Scheme administration policy and for prudential supervision.

Practical reading across instruments

• Definitions and consistency: Because many terms are defined by reference to ARS 701.0, any changes to ARS 701.0’s definitions would affect the meaning of items in ARF 920.8 and ARF 920.9. Paragraph 17 confirms that references to Acts, Prudential Standards, Australian Accounting Standards or Reporting Standards are references "as in force or existing from time to time", meaning the reporting Standard updates dynamically with amendments to referenced instruments.

• Former ARS 920.8: The Standard deems reporting made under the former ARS 920.8 (determination No. 43 of 2021) for reporting periods ending 31 May-30 Sep 2021 as having satisfied the current Standard (para 8). Practically this prevents duplication and aligns historical reporting across versions.

Limits of the instrument’s interactions

• Confidentiality and privacy: The Standard requires transmission of named and identifiable borrower data (primary borrower names, ABNs, guarantor names) in ARF 920.9 (instruction guide Table 1). While the Standard does not explicitly address privacy statutes or specify confidentiality protections in its text, institutions should be aware that reporting will involve personal and business identifiers and should therefore map submissions against privacy and confidentiality obligations under separate laws and internal policies. The Standard itself does not set privacy rules or exemptions; it simply requires the data be submitted to APRA.

• Enforcement cross-reference: Because the Standard is made under the Financial Sector (Collection of Data) Act 2001, enforcement mechanisms will be found in that Act and APRA’s enforcement instruments. The Standard does not include specific enforcement provisions, penalties or administrative penalty regimes in its own text.

The Reporting Standard document explicitly records some prior instruments and the treatment of earlier reporting periods. The text repeatedly refers to a "former ARS 920.8" and to a Financial Sector (Collection of Data) (reporting standard) determination No. 43 of 2021 (the former ARS 920.8) (paras 8 and 16). Paragraph 8 specifically states that information reported to APRA under the former ARS 920.8 for reporting periods ending on 31 May 2021, 30 June 2021, 31 July 2021, 31 August 2021 and 30 September 2021 is "deemed to have been reported, and not required to be resubmitted, under this Reporting Standard." This is an administrative consolidation: rather than asking ADIs and RFCs to resubmit previously-filed data to this new standard, APRA accepts the prior filings as fulfilling comparable obligations.

Key dated items

• Commencement date: The Standard applies to reporting periods ending on or after 31 October 2021 (para 4). This anchors the operational start for the new instrument.

• Deemed reporting window: The instrument treats the former ARS 920.8 coverage for reporting periods ending 31 May-30 Sep 2021 as already satisfied (para 8). That provides continuity across versions and avoids duplicative work for institutions that complied with the earlier determination.

References to earlier determinations

• The Standard identifies the former ARS 920.8 as Financial Sector (Collection of Data) (reporting standard) determination No. 43 of 2021 (para 16, definition of "former ARS 920.8"). That explicit numbering permits practitioners to locate the predecessor instrument for comparison or audit.

Dynamic reference to other standards

• Paragraph 17 provides that references to Acts, Prudential Standards, Australian Accounting Standards or Reporting Standards are to those instruments "as in force or existing from time to time." That means the Standard is not frozen to the definitions in place at the time of promulgation; it implicitly accepts that definitions in documents such as ARS 701.0 or accounting standards may change and that the reporting Standard will track those changes through reference.

No further amendment log within the text

• The text supplied does not include a formal amendment schedule or a legislative history beyond the references to the former ARS 920.8 and the commencement date. If subsequent amendments are made to ARS 920.8, those will be recorded in later determinations or consolidated versions posted by APRA. Practitioners should check APRA’s instrument registers for updated determinations or explanatory materials.

Operational effect of the amendment approach

• By deeming particular historical reports as already submitted and by cross-referencing current definitions to ARS 701.0 and other standards "from time to time," the instrument is structured to ensure continuity of reporting and to reduce the need for repeated submissions. However, it requires institutions to be attentive to versions of referenced standards because changes in ARS 701.0 or related instruments will affect interpretation and compliance going forward (para 17).

The text of ARS 920.8 and its instruction guides, as supplied, do not reference any litigation, cases, or adjudicated disputes. No judicial or tribunal decisions are cited in the instrument. The Standard contains procedural and definitional material and makes no mention of court actions, appeals, or precedent. Therefore, based on the instrument itself, there is no litigation history recorded or referred to in the text.

Practitioner note

• Because the Standard does not list litigation, practitioners who require litigation context (for example, challenges to APRA data-collection powers, disputes about the scope of reporting, or cases about the use of collected data) will need to search for judicial decisions involving the Financial Sector (Collection of Data) Act 2001, APRA’s data-collection powers, and the PGPA Act’s guarantee instruments. Those searches are outside the contents of this Reporting Standard and are not included in the instrument’s text.

The Standard and its instruction guides contain numerous specific rules and cross-checks that are easy to misapply. The following are concrete pitfalls and areas that commonly cause issues in practice, with direct references to the instrument where appropriate.

1. Scope misclassification (JobKeeper and pandemic-affected borrowers): The definition of "Flood scheme-backed loan" excludes borrowers who received JobKeeper between 4 Jan and 28 Mar 2021, directing those loans to ARS 920.6 for lending up to and including 30 Sep 2021 (para 6). Separately, where the borrower is adversely economically affected by the Coronavirus pandemic and also affected by the floods, reporting must be under ARS 920.10 from 1 Oct 2021 (para 7). Practically, lenders must have accurate attribution logic to determine whether a given loan is flood-only in scope, flood + JobKeeper, or flood + pandemic-affected, because the reporting destination differs materially.

2. Inclusion of securitised exposures: Instruction guides explicitly require inclusion of loans that have been securitised in counts and values (multiple places in ARF 920.8 and ARF 920.9 instruction guides). Some internal systems segregate securitised exposures from on-balance-sheet portfolios; those pipelines must be reconciled to ensure securitised scheme-backed loans are included in the returns.

3. Treatment of refinanced loans: The instruction guides distinguish loans refinanced after approval (exclude from Item 1.1/1.2) and also request explicit reporting of loans refinanced from Phase 1 and Phase 2 in Item 3 (ARF 920.8 Items 1.3 and 3.1-3.2). Entities must track whether a loan has been refinanced out of the Scheme and how to treat it in the various items.

4. Measurement and rounding rules: Monetary amounts must be in whole Australian dollars with no decimal places and percentages must be a whole number to two decimal places (instruction guides). Inconsistent rounding or decimal handling will produce validation errors in APRA’s submission platforms and can produce material reconciliation discrepancies (for example, weighted average customer rate Item 2.5).

5. Each facility reported once and apportionment of mixed facilities: Where a facility contains mixed 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 must be apportioned across the relevant dimensions (instruction guides). This requires decision logic to decide the "predominant" type and an apportionment algorithm.

6. Digital signature and authorised officer: Paragraph 15 mandates digital signing using a digital certificate acceptable to APRA. Entities must ensure they have an APRA-acceptable digital certificate infrastructure and documented delegation of authority for the officers or agents who will sign submissions.

7. Tight default deadlines and business-day rule: By default reports are monthly with a due date within 10 business days after period-end (paras 10-11). Importantly, if a due date falls on a non-usual business day, the return remains due on that date (note following para 13). Institutions must build processes that can produce and validate data quickly and be prepared to file on tight timelines.

8. Data contains PII and guarantor names: ARF 920.9 Table 1 requires primary borrower name, ABN, and guarantor names (columns 2-3 and 6). Reporting PII/identifiers introduces privacy and data-protection handling requirements; while the Standard does not itself specify privacy measures, entities should be aware of the need to handle those data elements securely during extraction, transmission and storage.

9. Domestic books consolidation: Paragraph 5 requires reporting on a "domestic books consolidation" with "domestic books" defined in ARS 701.0. Entities with complex international structures must ensure they understand the "domestic books" boundary to avoid under- or over-reporting.

10. APRA discretion to change frequency: APRA can require more frequent or less frequent reporting for particular ADIs or RFCs based on entity circumstances and Commonwealth requirements (para 12). Lenders must maintain scalable extraction capabilities so they can provide more granular data if APRA requests it.

11. Deemed prior reporting does not relieve reconciliation: Paragraph 8 deems some prior reports as submitted, but institutions should reconcile prior data to the current standard’s fields to ensure consistency and to be able to respond to APRA queries. The deemed reporting provision reduces resubmission burden but does not prevent APRA from requesting clarifications.

12. Unit-of-measurement errors: Failure to adhere to the specific formatting requirements (whole dollars, two-decimal percentage representation) will likely result in submission rejects. The instruction guides provide the exact format and must be followed.

13. Repayment holiday rounding: ARF 920.9 Column 15 requires the repayment holiday length in whole months, rounded to the nearest month. Calculate and document rounding rules consistently.

14. Security reporting nuance: Column 10 of ARF 920.9 asks whether the loan has security in addition to a personal or director guarantee. Entities must be precise about what they classify as "security in addition" and ensure the answer reflects their internal security registries.

These "gotchas" are not hypothetical; each arises directly from specific provisions in the Standard and instruction guides. Entities should document internal mapping of each data item to system fields, run reconciliation reports, and maintain an audit trail for digital signatures and authorised submissions.

Compliance requires a programme that maps the Standard’s requirements into operational processes, data extracts, controls and governance. Below is a practical compliance checklist, matched to the Standard’s provisions.

1. Entity scope confirmation

   • Confirm whether your entity is an ADI or an RFC that was granted a guarantee under s 60 of the PGPA Act for the SME Recovery Loan Scheme (para 3). If not, the Standard does not apply.

2. Loan identification and classification logic

   • Implement a rule to identify "Flood scheme-backed loans" per the instruction guides: primary borrower adversely affected by March 2021 floods; not a JobKeeper recipient between 4 Jan and 28 Mar 2021 (if so, use ARS 920.6 for lending up to 30 Sep 2021); and not a borrower identified as adversely economically affected by the Coronavirus pandemic (para 6-7 and definitions). Maintain audit trails for each loan’s classification decision.
   • Build mapping logic to direct loans to ARF 920.8, ARF 920.9, ARS 920.6 or ARS 920.10 as appropriate.

3. Data extraction and systems

   • Inventory all data items required by ARF 920.8 (Items 1-3) and ARF 920.9 (Table 1 columns 1-15). Ensure system fields capture: loan identifier, primary borrower name and ABN, loan value approved, interest rate, guarantor names, approval and final repayment dates, pre-existing lender relationship indicator, presence of additional security, refinance indicators and amounts, original loan identifiers where refinanced, loan type, and repayment holiday duration (ARF 920.9 instruction guide).
   • Include securitised loans in extracts (instruction guides), and implement apportionment logic for mixed facilities (instruction guides).

4. Domestic books consolidation

   • Perform reporting on a domestic books consolidation basis (para 5). Consult ARS 701.0 for the definition of domestic books and implement the consolidation boundary in reporting queries.

5. Measurement, rounding and formatting

   • Monetary values in whole Australian dollars (no decimals); percentages as whole numbers with two decimal places (e.g., 7.50) per instruction guides. Implement formatting controls and validation checks.

6. Portfolio calculations

   • Implement the weighted average customer rate calculation for Item 2.5 as specified (sum of all drawn amounts multiplied by respective interest rates divided by sum of all drawn amounts for loans approved at period end , instruction guide).

7. Quality control and governance

   • Design and document internal review and authorisation processes to assure completeness and reliability of the data (para 14). Include reconciliation between ledger systems, credit systems and the reporting extract. Maintain evidence of review sign-off.

8. Digital signing and submission method

   • Obtain and deploy a digital certificate acceptable to APRA for authorised officers/agents to sign submissions (para 15). Identify and document the authorised signatory list with delegation of authority.
   • Submit data electronically via APRA’s website or via a method notified by APRA prior to submission (para 9). Register and test submissions in APRA’s collection platform well in advance of the first due date.

9. Scheduling and cadence

   • Default cadence: calendar-month reporting periods (para 10) with returns due within 10 business days after period end (para 11). Build repeatable extract, validation and sign-off workflows to meet this timeframe. Plan for business-day edge cases since due dates falling on non-business days remain due (note after para 13).
   • Prepare for APRA’s discretion to change reporting frequency for the entity (para 12) by designing scalable extract and validation processes.

10. Documentation and audit trail

    • Keep logs of each submission, digital signatures, internal review artefacts, reconciliations, and APRA correspondence (including any written extensions or frequency changes from APRA per paras 12-13 and para 18). Store copies of submitted files and validation reports.

11. Privacy and secure handling

    • Implement secure data-handling and transmission processes for borrower identifiers, ABNs and guarantor names required in ARF 920.9 Table 1 columns 2-3 and 6. Although the Standard does not set privacy rules, prudent practice is to align handling with applicable privacy frameworks and internal security controls.

12. Exception handling and resubmission

    • Document a process for handling data errors, including corrective submissions if APRA rejects a return or requests further detail. Note that data reported under the former ARS 920.8 for specified periods is deemed reported under this Standard (para 8), but maintain reconciliation evidence.

13. Staff training and responsibilities

    • Train credit origination, data, risk and compliance staff on the mapping, rounding and apportionment rules, on the classification tests for scheme eligibility, and on the submission process with digital-signature requirements.

14. Reconciliation with Scheme administration and guarantee claims

    • Reconcile reported guarantee claims (ARF 920.8 Item 1.6) and amounts paid (Item 1.7) with Scheme claim records and internal accounting to ensure consistency between reported items, actual guarantee claims lodged, and receipts.

15. Liaison with APRA

    • Maintain a contact point for APRA requests and be prepared to accept written changes to reporting cadence or extensions. Ensure the institution can produce requested ad hoc extracts if APRA exercises its discretion under para 12.

By translating the Standard’s definitions, items and formatting rules into concrete queries, validation rules, authority processes and scheduled runs, a reporting programme can achieve consistent compliance. The key control points are accurate loan classification (to the correct ARS instrument), precise unit and rounding handling, inclusion of securitised exposures, and a documented digital signing and internal authorisation process.