The Reporting Standard and its instruction guides establish a taxonomy and reporting framework for JobKeeper scheme-backed loans. The main concepts are the reporting population, the two forms, data scope and definitions, submission mechanics, timing, quality controls and APRA’s exercise of discretion.

Reporting population and legal authority

• The Standard applies to ADIs and RFCs that are granted a guarantee under s 5 of the Guarantee of Lending to SMEs (Coronavirus Economic Response Package) Act 2020 in relation to the Australian Government SME Recovery Loan Scheme, and specifically for loans where the primary borrower received JobKeeper payments between 4 January 2021 and 28 March 2021 (para 3; definition at para 14). The Standard is made under s 13 of the Financial Sector (Collection of Data) Act 2001 (para 1).

Forms and data coverage

• Two separate reporting forms are mandated: ARF 920.6 captures portfolio-level information (Portfolio Information) and ARF 920.7 captures loan-level details (Loan Level Details) (para 2 and Instruction Guides). Paragraph 4 requires the provision of both forms in respect of each reporting period on a domestic books consolidation.
• The instruction guides specify precise items. ARF 920.6 requires portfolio-to-date counts and values (items 1.1-1.7), end-of-period portfolio metrics including credit outstanding, unused credit available, 30-days past due and impaired balances (items 2.1-2.4), weighted average customer rate (item 2.5), and refinancing amounts from Phase 1 or Phase 2 Guarantee scheme-backed loans (items 3.1-3.2). ARF 920.7 requires loan-level fields including borrower ABN, loan identifier, loan value approved, interest rate, guarantor names, approval and final repayment dates, loan type and repayment holiday length; and indicators such as prior relationship, security beyond personal guarantees, and whether the loan refinances a Phase 1 or 2 loan.

Definitions and reference standards

• The instrument references ARS 701.0 for core definitions including credit limit, credit outstanding, past due and securitised (para 14 and ARF instruction guides). It also refers to Australian Accounting Standards in relation to write-offs (ARF item 1.4) and makes definitions for terms specific to the Scheme such as JobKeeper scheme-backed loan, Guarantee Scheme, Phase 1 and Phase 2, and repayment holiday.

Timing, submission and authorisation

• Reporting periods are each calendar month unless APRA specifies otherwise (para 7). The initial set of reporting periods (ending 31 May, 30 June and 31 July 2021) have a single due date of 31 August 2021 (para 8). Thereafter, due dates are within 10 business days after the end of the reporting period (para 9). APRA may alter frequency for a particular entity or grant written extensions (paras 10-11). Submission must be electronic by APRA’s specified method (para 6), and submissions must be digitally signed by an officer or agent using a certificate acceptable to APRA (para 13).

Quality control and APRA discretion

• Entities must maintain processes and controls for internal review and authorisation of reported information to assure completeness and reliability (para 12). Where the Standard provides for APRA to exercise a power or discretion, that power is to be exercised in writing (para 16).

Special scope rules

• Loans securitised must be included where indicated in the forms and instructions (ARF 920.6 Item 1 and Item 2 instructions; ARF 920.7 also notes inclusion of securitised loans). Loans refinanced after approval and no longer covered by the Scheme have special treatment: “Loans refinanced” are defined and must be reported in specified items, and entities must exclude refinanced loans from certain counts (see ARF 920.6 Item 1 and definitions).

Cross-references to other reporting standards

• The Standard cross-references Reporting Standard ARS 920.8 in respect of loans where the primary borrower was adversely affected by March 2021 floods; those borrowers must be reported under ARS 920.8 rather than ARS 920.6 (para 5 and repeated in instruction guides). ARF instruction guides rely on ARS 701.0 for a number of definitions (see ARF definitions).

Purpose statement

• The stated purpose is to enable APRA to assist the Commonwealth to administer the SME Recovery Loan Scheme; APRA may also use the information for prudential purposes (para 2). That frames both an administrative use and a prudential oversight use.

Taken together, the framework creates a granular dataset linking guaranteed lending flows to borrower identifiers, contractual terms and performance metrics, with explicit rules for inclusion and exclusion, a defined electronic submission method and required internal controls and authorisation.

Primary reporting entities

• The Standard applies directly to all ADIs and RFCs that were granted a guarantee under s 5 of the Guarantee of Lending to Small and Medium Enterprises (Coronavirus Economic Response Package) Act 2020 for loans to businesses that received JobKeeper payments in the specified period (para 3). The term ADI is defined by reference to the Banking Act 1959 and APRA is defined by its establishing Act (para 14).

Affected loans and borrowers

• The data collection targets loans made under the Australian Government SME Recovery Loan Scheme where the primary borrower was a recipient of JobKeeper payments between 4 January 2021 and 28 March 2021 (para 14). The Scheme definition in the Standard limits the Scheme to loans made between 1 April 2021 and 31 December 2021 under section 5 of the Guarantee Act; the forms then further limit the reporting population by JobKeeper receipt dates (para 14). Loans securitised are explicitly included where the instruction guides indicate inclusion (ARF 920.6 Item 1 and Item 2 instructions; ARF 920.7).

Employees and officers responsible for reporting

• Officers or agents who submit information must digitally sign the relevant information using a digital certificate acceptable to APRA (para 13). The Standard therefore imposes a duty on an identifiable officer or agent within the reporting entity to authorise submissions.

Internal functions and controls

• The Standard requires entities to have processes and controls for internal review and authorisation to assure completeness and reliability of the data (para 12). This affects compliance, finance, loan operations and data teams that must map systems to the ARF field definitions.

Third-party service providers and securitisation trustees

• The requirement to report securitised loans indicates that entities using special purpose vehicles, trustees or third-party servicers remain within scope for the reporting obligation (instruction guides note securitised loans must be included). Where institutions outsource data extraction or submission, those third parties will be engaged to deliver the electronically signed and APRA-certified submission.

Borrowers and guarantors indirectly affected

• The loan-level form (ARF 920.7) requires borrower names and ABNs, guarantor names, and loan identifiers (instruction guide Table 1, Columns 1-6, Column 3 and Column 6). That produces direct reporting of identifiable borrower and guarantor data to APRA; borrowers and personal guarantors are therefore the subjects of data collection even though they are not parties to the Reporting Standard.

Other APRA and Commonwealth stakeholders

• APRA is the data recipient and may use the data for prudential purposes; the Commonwealth is a stated beneficiary for scheme administration (para 2). The Commonwealth’s administrative processes for the Scheme will therefore be directly affected by the availability of these data.

Entities excluded or redirected

• Borrowers who were adversely affected by the March 2021 floods and received JobKeeper payments between 4 January 2021 and 28 March 2021 must be reported under ARS 920.8 instead of ARS 920.6 (para 5 and instruction guides). This redirects reporting obligations for a subset of borrowers to a separate reporting standard.

Practical scale and operational impact

• The practical burden depends on the number of JobKeeper scheme-backed loans held by an entity, their operational ability to extract fields such as ABN, guarantor names, original loan identifiers for refinanced loans, interest rates at origination, and whether loans are securitised. Entities with wholesale or retail operational footprints will need to allocate compliance, data and IT resources to deliver monthly or more frequent extracts consistent with APRA’s electronic submission route.

In short, the Standard binds lenders who participated in the Recovery Loan Scheme to frequent, granular reporting, implicating multiple internal business units and producing identifiable borrower and guarantor data for APRA and the Commonwealth.

Key duties placed on reporting entities

Provide two specific forms each reporting period

• An ADI or RFC to which the Standard applies must provide ARF 920.6 (Portfolio Information) and ARF 920.7 (Loan Level Details) for each reporting period on a domestic books consolidation (para 4). The instruction guides specify exact items and fields.

Submit electronically and sign

• All information must be submitted in electronic format using an APRA-available electronic method or another method notified by APRA prior to submission (para 6). Submissions must be digitally signed by an officer or agent using a digital certificate acceptable to APRA (para 13).

Adhere to timing and reporting cadences

• Default reporting periods are calendar months (para 7). For reporting periods ending 31 May, 30 June and 31 July 2021, information had to be provided to APRA by 31 August 2021 (para 8). For reporting periods ending on or after 31 August 2021, submissions are due within 10 business days after the end of the reporting period (para 9). APRA may change reporting periods or require different frequencies for particular entities, having regard to the entity’s circumstances and Commonwealth requirements (para 10). APRA may grant written extensions (para 11).

Maintain quality control systems

• Entities must have internal processes and controls for review and authorisation to assure completeness and reliability of the information provided (para 12). This is an explicit operational duty.

Follow inclusion and exclusion rules

• Include securitised loans where the instruction guides require it. Exclude facilities entered into and subsequently cancelled due to being raised in error (instruction guides). Report loans refinanced and specify whether refinanced loans are no longer covered by the Scheme (definitions and Item 1).

Specific reporting content duties

• ARF 920.6 requires portfolio totals to date (items 1.1-1.7), end-of-period portfolio metrics (2.1-2.4), weighted average customer rate (2.5), and refinancing splits for Phase 1 and Phase 2 (3.1-3.2). ARF 920.7 requires loan-level fields such as loan identifier, borrower name, ABN, value approved, interest rate at origination, guarantors, approval and final repayment dates, security beyond director guarantees, refinement indicators, loan type and repayment holiday length (ARF 920.7 Table 1).

Special reporting paths

• If the primary borrower was adversely affected by the March 2021 floods and received JobKeeper payments in the stipulated period, that loan must be reported under ARS 920.8, not this standard (para 5).

Key procedural rights and discretions belonging to APRA

• APRA can change reporting periods or specified 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 10). APRA can also grant extensions of due dates in writing (para 11). The Standard requires APRA to exercise any power or discretion in writing (para 16).

No penalties set out in the Standard

• The Reporting Standard itself does not specify civil or criminal penalties, fines, or enforcement mechanisms. It establishes reporting obligations, and prescribes procedural and data quality requirements, but does not include explicit sanctions in the text provided. The authority for the Standard is s 13 of the Financial Sector (Collection of Data) Act 2001 (para 1). Users should therefore consult the enabling Act for any enforcement framework; the Standard itself is silent on penalties.

Rights of entities to receive modifications or extensions

• Entities have a procedural right to apply for extensions or request changes implicitly by interacting with APRA; APRA may grant extensions in writing (para 11) and may unilaterally change reporting frequency for an entity in writing (para 10). The Standard requires APRA to give such directions in writing (para 16).

Documentation and auditability duties

• The digital signature requirement (para 13) and the internal controls requirement (para 12) create an audit trail obligation. Entities must maintain systems and processes to produce reliable and authorised submissions.

Interaction with accounting standards

• ARF 920.6 Item 1.4 requires reporting of loans written off and deducted as a loss per relevant Australian Accounting Standards, linking reporting duties to entities’ accounting treatments.

In sum, the Standard creates detailed data collection duties, procedural requirements for submission and sign-off, internal quality control duties, plus APRA discretion to alter reporting requirements in writing. It does not articulate enforcement sanctions within its own text.

Reporting Standard text: no explicit penalties

• The text of ARS 920.6, as provided, does not set out penalties, financial sanctions, civil remedies, or criminal offences for non-compliance. The Standard prescribes obligations , who must report, what to report, timing and format, quality control and authorisation , but does not itself describe enforcement steps, punishments, or infringement frameworks.

Authority and implied enforcement mechanisms

• The Standard is made under s 13 of the Financial Sector (Collection of Data) Act 2001 (para 1). That Act is the enabling statutory authority; enforcement or penalty regimes for failure to comply with a reporting standard are typically located in the enabling Act. Because ARS 920.6 does not repeat or restate enforcement provisions, an entity seeking to understand sanctions should consult the Financial Sector (Collection of Data) Act 2001 directly for the statutory enforcement power that APRA may exercise when an entity fails to comply with a reporting obligation made under that Act. The Standard itself is silent on the point.

APRA’s operational levers set out in the Standard

• APRA’s immediate levers within this Standard are administrative and procedural rather than punitive: it may change reporting periods (para 10) and it may grant an extension of a due date in writing (para 11). The Standard also prescribes the method of submission and requires a digital signature (paras 6, 13). Failure to comply with these requirements will be identifiable through APRA’s receipt systems and may lead APRA to exercise statutory powers under its enabling legislation.

Auditability and internal control expectations as preventive measures

• The Standard requires that all information provided must be subject to internal processes and controls for review and authorisation to assure completeness and reliability (para 12). While this is a preventive administrative duty, it also creates an evidentiary posture APRA can examine if it questions a submission’s integrity.

Practical enforcement and follow-up risks

• In practice, non-submission, late submission, or materially inaccurate submission will place an entity at risk of APRA follow-up. APRA’s capacity to follow up will derive from the enabling Act and from its general supervisory and prudential functions. The Standard also requires APRA to exercise any discretionary power in writing (para 16), which creates procedural formality for APRA’s instructions, alterations and sanctions.

No prescribed review or appeal pathway in the Standard

• The Reporting Standard does not create a separate review or internal appeal mechanism against APRA’s decisions under the Standard. Rights to review APRA decisions, or to challenge enforcement action, will derive from the enabling statutes and administrative law principles rather than from the Standard itself.

Data confidentiality and onward sharing

• The Standard states that the information is used to enable APRA to assist the Commonwealth in administering the Scheme and that APRA may also use the information for prudential purposes (para 2). It does not set out rules about data sharing, retention, confidentiality protections or data security standards. Those matters will be addressed by APRA’s general policies and applicable law, not within this text.

Action items for entities with compliance concerns

• Entities requiring clarity on enforcement consequences should consult: the Financial Sector (Collection of Data) Act 2001 for enforcement provisions; APRA’s published data submission guidance and terms of use for its electronic submission services; and APRA’s general supervisory and enforcement policies. The Standard does not displace those documents but operates in tandem with them.

In summary, ARS 920.6 defines detailed reporting duties, timing and data fields but does not itself set penalties. Enforcement pathways and sanctions should be sought in the enabling Act and in APRA’s wider supervisory framework.

Primary statutory linkage and enabling power

• ARS 920.6 is made under section 13 of the Financial Sector (Collection of Data) Act 2001, which is the enabling statute referenced in the Standard (para 1). The Report Standard therefore sits as an instrument under that Act. Any statutory powers to require information and to enforce non-compliance derive from the enabling Act rather than from the Standard itself.

Interaction with the Guarantee of Lending to SMEs Act

• The Standard applies only to ADIs and RFCs granted a guarantee under section 5 of the Guarantee of Lending to Small and Medium Enterprises (Coronavirus Economic Response Package) Act 2020, as that guarantee relates to the Australian Government SME Recovery Loan Scheme; the Standard therefore ties reporting scope to the operation of that guarantee regime (para 3). The definitions of the Scheme include the period for eligible loans under section 5 (para 14).

Cross-references to other APRA Reporting Standards and definitions

• ARS 920.6 refers to, and depends on, Reporting Standard ARS 701.0 ABS/RBA Definitions for the EFS Collection for a number of fundamental definitions including credit limit, credit outstanding, past due and securitised exposures (para 14 and instruction guides). ARS 920.8 (SME Recovery Loan Scheme , Flood) is explicitly cross-referenced as the alternative reporting path for loans where the primary borrower was adversely affected by March 2021 floods and was a recipient of JobKeeper payments; those must be reported under ARS 920.8 and not ARS 920.6 (para 5, repeated in the instructions). The Standard also refers to Australian Accounting Standards for the reporting of write-offs (ARF 920.6 Item 1.4).

Administrative law and procedural formality

• The Standard requires APRA to exercise powers and discretions in writing (para 16). That procedural requirement aligns with administrative law expectations about formal directions and provides an evidential record for any changes APRA makes to reporting periods or due dates under paras 10 and 11.

Privacy and data protection law , absence of substantive regime in the text

• The Standard mandates the reporting of identifiable data such as primary borrower names, ABNs and guarantor names (ARF 920.7 Table 1 Columns 2, 3 and 6). However, the Standard does not set out privacy safeguards or specify interaction with the Privacy Act 1988 or other data protection regimes. Those interactions are therefore governed by the general law and APRA’s data handling and confidentiality policies rather than by the Reporting Standard itself. Entities must therefore reconcile their submission duties with their obligations under privacy law and internal privacy policies.

Securitisation, trustee and consolidated reporting regimes

• The Standard requires reporting on securitised loans where indicated, and requires reporting on a domestic books consolidation (para 4; ARF instruction guides). The meaning of domestic books is given by ARS 701.0. Entities that use special purpose vehicles, securitisation structures or operate across jurisdictions will need to map their consolidated reporting boundaries accordingly, and consult other regulatory reporting requirements about how securitised exposures are treated in both prudential and statistical returns.

Accounting standards and financial reporting

• The Standard links to Australian Accounting Standards for recognition of write-offs and loss deductions (ARF 920.6 Item 1.4). Entities must reconcile their accounting treatments with the values reported to APRA.

Interactions with APRA’s other supervisory powers

• The Standard makes clear that APRA may use the data for prudential purposes in addition to Commonwealth Scheme administration (para 2). That creates an operational interaction: data collected for an administrative policy purpose may also inform supervisory assessments, capital or provisioning consideration under APRA’s prudential remit.

Electronic submission and certificate standards

• The Standard requires electronic submission via APRA’s website or another method notified by APRA (para 6) and a digital certificate acceptable to APRA for signing (para 13). Those requirements interact with statutory frameworks for electronic signatures and electronic service of documents. The Standard, however, does not specify the cryptographic or certification standards , those are operationalised by APRA.

In sum, ARS 920.6 operates in a network of laws and standards: it is an APRA instrument under the Financial Sector (Collection of Data) Act 2001; it links the reporting obligation to the Guarantee Act’s section 5 guarantees; it relies on ARS 701.0 for definitions and other APRA reporting standards (including ARS 920.8) for related cohorts; and it requires entities to reconcile identifiable data reporting with external privacy and accounting regimes that are not detailed within the Standard.

Text of the Standard: no formal amendment chronology provided

• The provided text for ARS 920.6 and the accompanying instruction guides does not include an express amendment history section, italics, effective date block or schedule of versions. Paragraph 15 provides a general interpretive rule that references to an Act, Prudential Standard, Australian Accounting Standard or Reporting Standard are references to the instrument “as in force or existing from time to time” (para 15). That establishes a dynamic interpretive approach but does not substitute for a formal amendment history.

Internal duplication and formatting repetition in the provided text

• The material supplied contains repeated blocks of the same provisions, duplicated headings and instruction guides. This duplication appears to be a drafting or consolidation artifact in the document provided rather than an explicit amendment record. The repetition does not alter the substantive provisions identified at paras 1-16 and the ARF instruction content; however, it does increase the risk that an operational reader might overlook or misapply a single canonical clause. Entities should ensure they consult the authoritative version on APRA’s website for the correct, non-duplicative instrument.

No recorded prior versions or repeal entries present

• The document does not list prior versions of ARS 920.6, nor does it list a commencement date or a schedule of amendments. Where an instrument is subject to updates, APRA commonly publishes a version history online; absent such a log in the provided text, readers should check APRA’s legislative instruments repository or the Federal Register of Legislation for formal amendment records.

General interpretive clause pointing to instruments “as in force”

• Paragraph 15 establishes that cross-references to Acts, Prudential Standards, Australian Accounting Standards or Reporting Standards are to the instruments "as in force or existing from time to time" (para 15). This clause means that if an external instrument referenced by ARS 920.6 is amended, the reference within ARS 920.6 operates dynamically without the need to amend ARS 920.6 for every outside change. That affects amendment practice: ARS 920.6 will automatically reflect future changes to those external instruments insofar as those changes are relevant to interpretation.

APRA’s exercise of discretion and written variations

• Paras 10, 11 and 16 give APRA the ability to change reporting periods for particular entities and to grant extensions in writing, and require the exercise of power in writing. These operationally allow APRA to vary the requirements for an entity without amending the standard formally. From a governance perspective, that reduces the need for frequent instrument amendment to accommodate entity-specific operational realities.

Practical implication for checking amendments

• Given absence of an in-text amendment log, controlled entities should confirm they hold the current authoritative instrument from APRA’s website or the Federal Register of Legislation, track APRA notices that may change reporting frequency or due dates for particular entities, and record any written variations APRA supplies under paras 10-11.

In short, the provided document does not include a formal amendment history; the instrument relies on dynamic cross-references and enables APRA to make written variations for particular entities, which in practice means operational variations may appear outside a formal amendment track. Entities should consult APRA’s authoritative publication channels for version control.

No litigation or case references in the text

• The Reporting Standard and its instruction guides, as provided, do not cite any litigation, decisions, or judicial interpretations. They do not identify any cases or disputes bearing on the interpretation or enforcement of the Standard.

No scheme-specific precedent identified

• The instrument is administrative and technical in nature. It does not record court decisions, settled interpretations, or dispute outcomes. It also does not identify any internal APRA dispute resolution or review decisions that have been challenged in courts or tribunals.

Implication for legal advisors

• Because the text contains no litigation history, legal analysis of compliance risk, enforcement exposure, or interpretive disputes will need to be predictive and based on the enabling statute, APRA’s supervisory practice and general administrative law. Practitioners should search the Federal Court, AAT, and other relevant court and tribunal records if they need to identify any disputes involving APRA reporting standards generally, or the Financial Sector (Collection of Data) Act 2001, as the Standard itself does not provide such a record.

Where to look for disputes

• To identify any litigation connected to this Standard or its enforcement, check:
  • Decisions under the Financial Sector (Collection of Data) Act 2001 in administrative and federal courts.
  • APRA enforcement actions and press releases that may record negotiated outcomes or sanctions.
  • Published decisions from the Administrative Appeals Tribunal if any internal APRA decisions were appealed.

Conclusion on litigation

• The instrument itself contains no litigation history. Any dispute history must be researched externally against APRA’s enforcement record and general case law on APRA’s data collection powers and the Financial Sector (Collection of Data) Act 2001.

Scope-by-date constraints and overlapping definitions

• The Standard applies only to loans where the primary borrower was a recipient of JobKeeper payments between 4 January 2021 and 28 March 2021 (para 3; definition in para 14). That is a narrower cohort than the Scheme’s loan-eligibility window (the Scheme definition references loans written between 1 April 2021 and 31 December 2021 under the Guarantee Act). Entities must reconcile these two date dimensions when determining which loans are reportable: the Scheme’s loan date and the borrower’s JobKeeper receipt date interact to determine inclusion.

Flood-affected borrowers redirected to ARS 920.8

• If the primary borrower was adversely affected by the March 2021 floods and was a JobKeeper recipient in the stated period, the loan must be reported under ARS 920.8, not ARS 920.6 (para 5 and repeated in instructions). Entities must implement rules to route such accounts to the correct return to avoid double-reporting or misreporting.

Securitised loans must be included

• The instruction guides repeatedly state that securitised loans must be included in the counts and values (ARF 920.6 Item 1 & Item 2 instructions; ARF 920.7). Entities that have transferred exposures to special purpose entities or securitisation vehicles must ensure their submission logic captures the exposures in the domestic books consolidation as defined by ARS 701.0.

Domestic books consolidation requirement

• Paragraph 4 requires reporting on a domestic books consolidation. Entities operating across jurisdictions must ensure they use the ARS 701.0 definition of domestic books when consolidating and may need to adjust internal reporting boundaries accordingly.

Refinanced loans: inclusion and exclusion nuances

• “Loans refinanced” are defined in the instruction guides and are to be reported in specific items (ARF 920.6 Item 1.3 and items dealing with refinancing). The instruction guides also specify that loans refinanced after approval that are no longer covered by the Scheme are treated differently. Entities must accurately flag original and refinanced loan identifiers (ARF 920.7 Column 13) and report values appropriately (Columns 11-12). Failure to capture refinanced loans correctly can misstate Scheme exposure and guarantee claim metrics.

Initial catch-up due date anomaly

• Reporting periods ending 31 May, 30 June and 31 July 2021 were due by 31 August 2021 (para 8). This front-loaded reporting schedule is an anomaly relative to the standard 10-business-day cadence (para 9). Entities that missed that catch-up due date would be late for those specific periods. Historical submissions must be checked to ensure those initial reports were delivered by the specified date.

Precision and unit-of-measure traps

• ARF instruction guides specify whole Australian dollars for amounts (no decimals), and percentages must be expressed as a whole number to 2 decimal places (for example 7.5 per cent as 7.50) (several instruction notes). Data feeds and rounding procedures must be aligned to these formatting rules to avoid rejection or misinterpretation.

Identifiable data and privacy risk

• ARF 920.7 requires primary borrower names, ABNs, and guarantor names (Columns 2, 3 and 6). The Standard itself does not set privacy safeguards. Entities must therefore ensure that disclosing personally identifiable information and ABNs to APRA is consistent with privacy obligations under other law and their internal privacy policies. The reporting obligation does not absolve entities of any separate statutory privacy duties.

Digital signature and certificate acceptance

• Submissions must be digitally signed using a certificate acceptable to APRA (para 13). Entities relying on third-party submission platforms or new digital signing processes must validate their certificate against APRA’s requirements before the submission deadline or risk rejection.

Quality control expectation is explicit

• Para 12 requires systems, processes and controls developed by the entity to assure completeness and reliability. This is not optional boilerplate: APRA expects internal review and authorisation. An ad-hoc spreadsheet extract without internal sign-off and documented controls may not meet this requirement.

APRA discretion and written directions

• APRA may change reporting periods for particular entities to require more or less frequent reporting, considering the entity’s circumstances and Commonwealth requirements (para 10). Entities should monitor written notifications from APRA; oral instructions are not compliant authority under para 16 which requires APRA’s exercise of power to be in writing.

Ambiguity in “predominant” allocation rules

• The instruction guide states that where a facility has mixed interest rate or repayment types, the number of facilities should be reported according to the predominant interest rate type or repayment type by value. “Predominant” and the aggregation method may introduce judgement calls that should be documented and consistently applied to satisfy para 12’s quality control requirement.

Multiple duplications in the instruction guides

• The provided text contains repeated instruction blocks and tables. Entities should consult APRA’s authoritative copy to avoid following an incorrect or draft paragraph from the duplicated content. The duplication increases the chance of misreading one set of instructions as superseding another.

No penalty text , enforcement uncertainty

• The Standard does not specify penalties within its text. Entities must check the Financial Sector (Collection of Data) Act 2001 and APRA’s supervisory materials to understand enforcement risk and remediation pathways.

In short, practical “gotchas” focus on date windows, securitisation inclusions, refinanced loan treatment, precise formatting rules, privacy considerations for identifiable data, digital signature acceptance, and APRA’s capacity to vary reporting rules in writing.

Governance and project setup

• Assign a responsible owner: designate a senior officer or agent who will execute the digital sign-off required by para 13. That officer should be empowered to attest to completeness and reliability under the internal quality controls required by para 12.
• Map stakeholders: involve credit operations, data/IT, legal (privacy), finance/accounting and compliance. Responsibilities should include data extraction, validation, reconciliations to accounting records, privacy sign-off and final authorisation.

Data mapping and extraction

• Identify the population: extract all loans where the primary borrower received JobKeeper payments between 4 January 2021 and 28 March 2021 and where the lender was granted a guarantee under s 5 of the Guarantee Act (para 3; para 14 definitions).
• Use the domestic books consolidation boundary: apply the meaning given by ARS 701.0 for domestic books when consolidating data (para 14).
• Capture required portfolio fields for ARF 920.6: totals to date (items 1.1-1.7), end-of-period metrics (2.1-2.4), weighted average customer rate (2.5), and refinancing split amounts for Phase 1 and Phase 2 (3.1-3.2) as described in the instruction guide.
• Capture loan-level fields for ARF 920.7: loan identifier, primary borrower name, primary borrower ABN, loan value approved, interest rate at origination, guarantor names (semicolon separated or “Nil”), approval date, final repayment date, indicator of prior relationship, indicator of security beyond director/personal guarantees, refinancing indicator and original loan identifiers for refinanced loans, loan type (fixed term, revolving, margin lending, other), repayment holiday months (rounded) (ARF 920.7 Table 1).
• Ensure securitised exposures are included where the instruction guides require (ARF instructions for Items 1 and 2 and ARF 920.7 note on securitised exposures).

Formatting and unit conventions

• Dollar amounts must be whole Australian dollars no decimals. Percentages must be formatted to two decimal places as a whole number (for example 7.50) per instruction guides. Implement rounding rules and format conversions in extraction scripts and test with sample records.

Reconciliation and quality control

• Implement the internal review and authorisation systems required by para 12. Document data lineage, reconciliations to general ledger and loan servicing systems, and exception lists covering securitisation, refunds, cancelled facilities, and refinanced loans.
• Reconcile write-offs and recoveries to accounting treatments. ARF 920.6 Item 1.4 requires reporting of loans written off and deducted as a loss per relevant Australian Accounting Standards.

Privacy and legal clearance

• Because ARF 920.7 requires borrower names, ABNs and guarantor names, coordinate with privacy and legal teams to document legal bases for disclosure. While the Standard mandates submission, entities should confirm internal privacy notices, data sharing schedules and retention policies align with this disclosure. Record the legal justification for sharing personally identifiable information with APRA.

Submission mechanics and sign-off

• Use APRA’s electronic submission method as described on APRA’s website or another method notified by APRA (para 6). Ensure the entity has a digital certificate acceptable to APRA and test the signing and submission process well before the due date (para 13).
• Maintain an auditable trail of who signed the submission and when; document any internal sign-off checklists required under para 12.

Timing and calendar management

• Default reporting periods are calendar months (para 7). For any periods ending on or after 31 August 2021, submissions are due within 10 business days after the end of the reporting period (para 9). For the initial three periods (31 May, 30 June, 31 July 2021) the due date was 31 August 2021 (para 8); organisations should confirm that historical submissions were made and documented.
• Monitor APRA communications for entity-specific changes to reporting cadence or extensions granted in writing under paras 10-11.

Special-case routing

• Implement a rule to route loans where the primary borrower was adversely affected by March 2021 floods and received JobKeeper payments between 4 January and 28 March 2021 to ARS 920.8 rather than ARS 920.6 (para 5 and instruction guides).

Exception handling and documentation

• Document and retain evidence for any excluded facilities, for example facilities entered into and subsequently cancelled due to being raised in error, per instruction guide exclusions.
• For mixed-rate or mixed-repayment facilities, implement a documented methodology for determining the “predominant” interest or repayment type by value and use consistent apportionment for value reporting.

Test submissions and data validation

• Run end-to-end tests: from source-system extract to formatted ARF files, digital signing and transmission via APRA’s portal. Validate sample submissions against the instruction guide expectations and ensure acceptance by APRA.
• Where possible, use APRA test environments or pre-submission validations to catch formatting or completeness rejections.

Monitoring and post-submission processes

• Retain copies of submissions and the APRA acknowledgement. Maintain post-submission reconciliation processes to detect and correct any subsequent reporting errors.
• Implement quarterly or periodic reviews of mapping rules, especially for refinanced loans, securitisations and write-offs, to keep reporting consistent with accounting and legal positions.

Engage with APRA early if unclear

• If any interpretation or operational question arises (for example how to treat a complex securitisation or a loan refinanced across phases), seek written clarification from APRA. Para 16 requires APRA to exercise powers or discretion in writing, and written responses create an evidentiary record.

Audit readiness

• Prepare documentation for internal or external auditors showing data lineage, control checks, reconciliations, APRA communications and signatory authority. The digital certificate and internal controls provide the audit trail APRA will expect to see.

In short, compliance requires cross-functional project management, rigorous data mapping to the prescribed fields and units, documented quality controls, privacy clearance for identifiable data, tested electronic submission and signed authorisation, and a proactive approach to APRA communications and written directions.