Financial Sector (Collection of Data) (reporting standard) determination No. 9 of 2022

Reporting Standard ARS 720.1 organises its requirements around two reporting instruments and a set of operational rules. The principal concepts are:

• Two reporting forms and what they collect: ARF 720.1A (Standard) and ARF 720.1B (Reduced). The Standard (ARF 720.1A) is more granular: it collects loans and finance leases by counterparty (residents/non‑residents), currency (including a column for amounts denominated in foreign currency in AUD equivalent), residual maturity (maturing in one year or less), and separate columns for individual and collective provisions (see ARF 720.1A form and specific instructions under Item 1). It also collects securitised balances on- and off-balance sheet and a breakdown of non‑performing exposures (Items 4, 5 and 6). The Reduced form (ARF 720.1B) collects a narrower set of items, with fewer columns and less granularity (see ARF 720.1B form and instructions).

• Scope: applies to ADIs and RFCs as set out in the application table (paragraph 4). Whether an ADI or RFC completes the Standard or Reduced form depends on reporting category and asset thresholds. The table in paragraph 4 determines which class files which form; the text and notes in paragraph 9 set out how “total assets” are to be measured for those thresholds.

• Reporting basis and conventions: all data are to be reported on a domestic books consolidation basis, as at the end of the reporting period (paragraph 7; instructions). Loans and finance leases must be reported gross of collective and individual provisions (explicitly different from Australian Accounting Standards treatment, see Values sections and multiple instructions). Foreign currency amounts must be converted to Australian dollars in accordance with AASB 121 (Values sections). Exclusions include intra‑group loans and non‑resident loans unless otherwise directed (Repeated across instructions for both ARFs).

• Frequency and due dates: monthly reporting applies for ADIs in ADI Reporting Category B, ADIs in Category A with total assets ≥ $200 million, and RFCs with total assets ≥ $400 million (paragraph 9(a)). RFCs with total assets < $400 million report annually to their financial year (paragraph 9(b)). All returns are due within 10 business days of each reporting period (paragraph 10). APRA may change frequencies for particular institutions (paragraph 11) and may grant extensions (paragraph 12).

• Quality assurance: external auditor review and testing are mandated by paragraph 13 (referencing Prudential Standard APS 310 for ADIs and Reporting Standard RRS 710.0 for RFCs). Internal systems, processes and controls for authorisation and completeness are required (paragraph 14). Digital signing using an APRA‑acceptable certificate or digital identity is mandated when using notified electronic methods (paragraph 15).

• APRA discretion: APRA may prescribe alternative thresholds, require different frequencies, grant exemptions (footnote and paragraph 5), or require provision of the Reduced form instead of the Standard form under an exemption condition (final footnote). APRA determines method of electronic submission by notice (paragraph 8).

• Derived fields and reconciliation: many items are derived (form instructions repeatedly instruct that certain items equal sums of other items or must reconcile to items reported on ARF 720.0A/B and ARF 323.0). The instructions require consistency across the EFS suite, for example Item 1.1 on ARF 720.1A equals certain items on ARF 720.0A (see Item 1.1 instructions).

These concepts combine to create a system that standardises detailed loan and lease data flows into APRA/ABS/RBA statistical and prudential datasets. The Standard sets the data model (items, columns, derived fields), the submission model (electronic, digitally signed, SBR accounting types), and governance (auditor review, internal controls), while APRA retains discretion to adapt thresholds and frequency to institution‑specific circumstances (paragraphs 5 and 11).

The Reporting Standard identifies affected entities narrowly: authorised deposit‑taking institutions (ADIs) and registered financial corporations (RFCs) as those terms are used under the Financial Sector (Collection of Data) Act 2001 and defined in ARS 701.0 (paragraph 4 and the Interpretation note at the start of the Determination). Which form an institution must complete depends on reporting category and measured total assets.

• ADIs: The table at paragraph 4 distinguishes ADI Reporting Category A and ADI Reporting Category B. ADI Reporting Category B institutions must complete ARF 720.1A (Standard). ADI Reporting Category A institutions do not complete ARF 720.1A; they complete ARF 720.1B (Reduced) only if total assets are at or above $200 million (paragraph 4 table and the footnote linked at the end). The measurement of an ADI’s ‘total assets’ is specified (paragraph 9 note): use item 13 (column 1) on ARF 720.0A/B or item 11 (column 1) on ARF 323.0 as at 31 December of the prior calendar year.

• RFCs: The table in paragraph 4 states RFCs do not complete ARF 720.1A and must complete ARF 720.1B (Reduced) if total assets ≥ $50 million. However the frequency of reporting for RFCs is stratified in paragraph 9: RFCs with total assets ≥ $400 million report monthly, while RFCs with total assets < $400 million may report annually to their financial year (paragraph 9). The ‘total assets’ for an RFC is measured by the value reported in item 13 (column 1) on ARF 720.0A as at the last day of the RFC’s prior financial year (paragraph 9 note 2).

• Officers and agents submitting data: paragraph 15 requires that an officer or agent submitting data by an APRA‑notified method digitally sign the information using an APRA‑acceptable digital certificate or identity, so authorised signatories and their systems are directly affected.

• External auditors and internal control functions: paragraph 13 mandates that reported information must be the product of systems, processes and controls reviewed and tested by the external auditor in accordance with Prudential Standard APS 310 (for ADIs) or Reporting Standard RRS 710.0 (for RFCs). This imposes obligations on auditors and on the firm’s internal control teams to ensure accuracy and to schedule reviews at least annually or more frequently if the auditor requires it.

• ABS/RBA/APRA: while not “affected” in the compliance sense, these agencies are the intended users. Paragraph 2 explicitly states the ABS and RBA use the data for National Accounts and credit aggregates, and APRA may use the same information for prudential and publication uses.

Who pays: the direct burdens fall on the ADIs and RFCs specified by the application table and the asset thresholds in paragraph 4 and paragraph 9 notes. Costs will include systems development to produce the granular items (currency conversion, maturity buckets, securitisation tags, NPE classification), external auditor fees to perform the required review and testing (paragraph 13), staff time for data extraction and sign‑off, and possible upgrades to digital identity infrastructure for digital signing (paragraph 15).

Who decides: APRA decides (a) the institution classes to which the Standard applies via paragraph 4, (b) asset measurement conventions and whether an institution meets thresholds via paragraph 9 and its notes, (c) the electronic submission method via paragraph 8, and (d) may alter frequency or thresholds in writing to a particular ADI or RFC (paragraphs 5 and 11). The original Determination is made by an APRA delegate under s13 of the Act and declared to commence under s15 (opening recital; Schedule Authority 1).

Geographical and reporting perimeter: the Reporting Standard requires reporting on a domestic books consolidation (paragraph 7), and repeatedly instructs exclusion of intra‑group loans (to be reported separately on ARF 720.3) and exclusion of loans to non‑residents unless otherwise directed (instructions across both ARFs). These perimeter rules affect which balances are captured in the data delivery.

Duties imposed by the Reporting Standard are administrative, data‑reporting and quality assurance duties. Rights (where the instrument creates them) are mainly procedural, such as the right to seek an extension or receive APRA notice of changed reporting frequency.

Key duties

• Provision of required information: An ADI or RFC to which the Standard applies must provide APRA with the information required by the Reporting Standard for each reporting period on a domestic books consolidation (paragraph 7). The content and structure are prescribed in ARF 720.1A and ARF 720.1B and their instructions (Schedule).

• Submission method and format: The information must be given electronically, using an electronic method available on APRA’s website or another method notified by APRA prior to submission (paragraph 8). The submitting officer or agent must digitally sign the data with a digital certificate or identity credential acceptable to APRA when using a notified method (paragraph 15).

• Timing and frequency: Provide monthly or annual returns depending on class and asset thresholds (paragraph 9), and deliver the information within 10 business days after the end of the reporting period (paragraph 10). APRA may change an individual institution’s reporting periods in writing to require more or less frequent reporting (paragraph 11).

• Quality control and audit testing: Ensure all information is the product of systems, processes and controls reviewed and tested by the external auditor as set out in Prudential Standard APS 310 (ADIs) or Reporting Standard RRS 710.0 (RFCs). This review must be done at least annually or more frequently if the external auditor requires (paragraph 13). Additionally, establish internal systems, processes and controls for internal review and authorisation to assure completeness and reliability (paragraph 14).

• Data conventions and exclusions: Follow the form instructions: report on an end‑of‑period basis, report monetary amounts in AUD or AUD equivalent (convert per AASB 121), report balances gross of provisions (even if accounting standards net them), exclude deferred tax assets from provisions, exclude intra‑group loans (report via ARF 720.3), exclude written‑off loans, and follow the classification rules (report by purpose at the lowest identifiable level) (form instructions throughout).

• Reconciliation: Where items are defined as derived fields, ensure internal reconciliation so that derived items equal the sums required and match ARF 720.0A/B items where the form instructions require equality (see Item 1.1 and other derived item instructions).

Procedural rights and APRA discretions

• Extension right (procedural): APRA may grant an ADI or RFC an extension of a due date in writing, producing a new due date on the notice of extension (paragraph 12). The right is subject to APRA’s discretion.

• APRA may change reporting periods or frequency for a particular institution in writing, taking into account the institution’s circumstances and the needs of the ABS or RBA (paragraph 11). That is, institutions have a procedural expectation that APRA will notify them in writing of any change.

• Exemption and substitution: APRA may determine that a higher threshold or a different threshold applies to a particular ADI or RFC (paragraph 5) and may exempt an ADI from providing information under ARF 720.1A on condition that it provides other information required by the Reporting Standard (footnote linked to paragraph 4 and the explanatory note at the end referencing paragraph 16(1)(b) of the Act). The footnote gives an explicit example: APRA may exempt an ADI from ARF 720.1A provided it provides ARF 720.1B.

Rights not created by the instrument

• The Determination does not itself create rights to confidentiality, appeal rights or statutory penalty provisions in the text of the instrument. Any such rights or penalties would derive from the Financial Sector (Collection of Data) Act 2001 and other statutes or APRA policies rather than from this Determination; those are not set out in the text of this Reporting Standard.

Practical duties that generate compliance tasks

• Systems must produce the specified SBR accounting types (debit/credit) for each column and item (instructions under SBR notes).

• Preparation of exchange rate conversions per AASB 121 and reporting in whole dollars.

• Ensure external auditor engagement covers the APRA‑required scope and supports the auditor’s review and testing of systems and controls annually or as required (paragraph 13).

• Domestic books consolidation must be the reporting consolidation perimeter (paragraph 7), so corporate finance and group consolidation teams must ensure correct consolidation mapping.

These duties create both operational and governance obligations: firms must map product and borrower classifications to the specific item codes, ensure reconciliations with ARF 720.0A/B, and maintain a governance trail for auditor review and digital sign‑off.

The Reporting Standard itself sets out procedural compliance requirements, APO controls and APRA discretions, but it does not include express monetary penalties or criminal sanctions in the text of the Standard. The instrument repeatedly refers to APRA’s administrative powers to notify, require, exempt, change reporting frequency or grant extensions (paragraphs 5, 8, 11 and 12). Those are the principal enforcement mechanisms provided in the Standard.

Administrative enforcement mechanisms referenced in the text

• APRA notification and direction: APRA may notify an ADI or RFC of different thresholds or reporting frequencies in writing (paragraphs 5 and 11). Non‑compliance with a written direction is likely actionable under the FS (Collection of Data) Act, but the Standard itself only records the ability for APRA to change requirements and notify institutions.

• Extensions: APRA may grant written extensions of due dates (paragraph 12). The ability to extend is an administrative control that mitigates immediate breach risk when exercised.

• Exemptions and conditional substitution: APRA may exempt an ADI from ARF 720.1A on a conditional basis (footnote and paragraph 5) so exemptions can be used as an enforcement/administrative tool to manage burdens and ensure comparable information is provided.

• External audit and control requirements: Paragraph 13 links external auditor review obligations to Prudential Standard APS 310 for ADIs and Reporting Standard RRS 710.0 for RFCs. External auditor findings and required remediation are standard supervisory levers; the Standard requires that data must be the product of systems reviewed and tested by the external auditor.

What the instrument does not specify

• The Standard does not itself set statutory penalties or enforcement procedures (for example, monetary fines, court actions or formal notices under particular sections of the Act) within its text. It is anchored to the Financial Sector (Collection of Data) Act 2001 and is made under that Act (opening recital; Schedule Authority 1). Any specified penalties for non‑compliance, or enforcement powers such as notices to produce data, would come from the Act or APRA’s broader toolkit, none of which are reproduced in this Determination.

Compliance risk and where enforcement is likely to arise

• The immediate enforcement levers available to APRA under this Standard are administrative: specifying frequency, issuing written notices, granting extensions, accepting or refusing electronic submission methods, requiring auditor involvement and using exemption powers. Given the Standard’s short 10 business day lodgement window (paragraph 10), operational non‑compliance (late or absent lodgement) is the most likely supervisory trigger.

• External auditor reporting of material weaknesses in systems, processes and controls (paragraph 13) would create a remediation pathway and supervisory oversight; the Standard ties the data quality duty to auditor review, which shifts enforcement into the prudential supervisory domain.

For practitioners, the practical implication is to treat enforcement as a combination of administrative supervision (APRA notices, remediation requirements, possible exemption negotiations) and auditor scrutiny rather than a self‑contained schedule of statutory fines in the Reporting Standard itself. Those statutory enforcement tools, if required, will be sourced from the parent Act and APRA’s usual supervisory processes rather than from the Reporting Standard text.

The Reporting Standard is explicitly situated within a network of other APRA reporting standards, prudential instruments and Australian Accounting Standards; the Schedule references a number of other instruments and statutes and requires consistency with them.

Statutory and instrument links in the Reporting Standard

• Financial Sector (Collection of Data) Act 2001: The Reporting Standard is made under section 13 of that Act (Schedule, Authority 1) and commencement is declared under section 15 (opening recital). The Determination further cites paragraph 13(1)(a) of the Act as the delegate’s power in the recitals.

• Acts Interpretation Act 1901: Delegation is exercised in accordance with subsection 33(3) (opening recital).

APRA and internal instruments

• ARS 701.0 ABS/RBA Definitions for the EFS Collection: The Reporting Standard is an EFS Reporting Standard for the purposes of ARS 701.0 (paragraph 3). The Schedule instructs that terms defined in ARS 701.0 appear in bold italics and that definitions in ARS 701.0 are authoritative for the reporting standard (paragraph 16). Practitioners must therefore map definitions in ARS 701.0 to the data items here.

• ARF 720.0A/B ABS/RBA Statement of Financial Position (Standard)/(Reduced): Item definitions and several derived items on ARF 720.1A/B expressly reconcile to items on ARF 720.0A/B (e.g., Item 1.1 for ARF 720.1A equals loans and finance leases - total gross of collective and individual provisions reported in item 6, column 1 on ARF 720.0A). The Reporting Standard requires consistency between these forms, so institutions must operate reconciliations across their reporting suite.

• ARF 720.3 ABS/RBA Intra‑group Assets and Liabilities: The forms instruct exclusion of intra‑group loans and finance leases from ARF 720.1A/B and require that such intra‑group items be reported on ARF 720.3 (ARF instructions on Counterparties).

• ARF 323.0 Statement of Financial Position (Licensed ADI): The measurement of an ADI’s total assets for threshold purposes may rely on item 11 (column 1) on ARF 323.0, as noted in paragraph 9.

Prudential and auditing instruments

• Prudential Standard APS 310 Audit and Related Matters: Paragraph 13 requires the external auditor review and testing for ADIs to be conducted as set out in APS 310. That standard governs auditor responsibilities and shapes the scope of audit testing that supports the ARF 720.1 filings.

• Reporting Standard RRS 710.0 ABS/RBA Audit Requirements for Registered Financial Corporations: For RFCs, the equivalent external auditor review obligations are set out in RRS 710.0 (paragraph 13).

Australian Accounting and Auditing Standards

• AASB 121 The Effects of Changes in Foreign Exchange Rates: The Reporting Standard mandates the conversion of foreign currency amounts to AUD in accordance with AASB 121 (Value instructions for both ARFs).

• Australian Accounting Standards generally: Items are to be reported in accordance with Australian Accounting Standards unless specified otherwise (Value sections). However the Reporting Standard explicitly requires reporting credit outstanding gross of collective and individual provisions, noting that this differs from the reporting of loans and finance leases under Australian Accounting Standards (multiple statements in the Values and Specific instructions).

Corporations Act 2001

• The Reporting Standard uses the Corporations Act definition of financial year to determine reporting for RFCs with total assets < $400 million (paragraph 9(b) cross‑referencing "financial year (within the meaning of the Corporations Act 2001)").

Practical interactions and compliance mapping

• Reconciliation and derived fields: Multiple items are derived from or must reconcile to items reported on ARF 720.0A/B and ARF 323.0. Institutions must ensure chart of accounts, ledger mappings and consolidation processes align with APRA item definitions and with ARS 701.0 definitions. This creates an operational interaction between accounting standards, consolidation rules and APRA reporting taxonomy.

• Auditor standard interplay: External auditors must perform review and testing consistent with APS 310 or RRS 710.0; those prudential instruments define scope and methodology that interact with general auditing standards and APRA’s supervisory expectations. Auditors will therefore need to align their audit workpapers to both APRA reporting items and to the auditing standards recognised by the Auditing and Assurance Standards Board, which the Reporting Standard references as relevant guidance (paragraph 13).

• Domestic consolidation perimeter: The Reporting Standard’s emphasis on domestic books consolidation interacts with other statutory consolidation and regulatory reporting perimeters. Firms must maintain and document the mapping between their financial statements, domestic consolidation submissions and any off‑balance sheet securitisation reporting (Items 4 and 5).

• Data exchange standards: The use of Standard Business Reporting (SBR) accounting types and an APRA‑specified electronic submission method requires system interfaces that reconcile ledger data to SBR schemas and that support APRA’s transmission protocol.

The Reporting Standard is therefore a node connecting APRA reporting law, prudential audit requirements and accounting standards. Compliance requires mapping and reconciliation across those instruments, each of which supplies definitional or procedural details cited directly in the Reporting Standard (paragraphs 13, 16 and the AASB and Corporations Act references).

This Determination (Financial Sector (Collection of Data) (reporting standard) determination No. 9 of 2022) expressly revokes Financial Sector (Collection of Data) (reporting standard) determination No. 3 of 2019 and replaces Reporting Standard ARS 720.1 ABS/RBA Loans and Finance Leases with the version published in the Schedule (opening recital: "(a) revoke ... No. 3 of 2019 ... and (b) determine Reporting Standard ARS 720.1 ... in the form set out in the Schedule"). The instrument is dated 23 February 2022 and commences on registration (opening recital: "This instrument commences upon registration on the Federal Register of Legislation"; and declaration under section 15 is recorded in the recitals).

What the text records about change:

• Revocation and replacement: The instrument explicitly revokes the 2019 Determination and sets out the new Reporting Standard in full in the Schedule. The Schedule includes both the full ARF 720.1A and ARF 720.1B forms and their instructions.

• Commencement: APRA has declared (under s15 of the Act) that the new Reporting Standard shall begin to apply to the specified entities and that the revoked reporting standard shall cease to apply on the day the instrument is registered on the Federal Register of Legislation. The Schedule then specifies that the Standard applies for reporting periods ending on or after 31 March 2022 (paragraph 6), making the effective reporting change concrete for institutions.

• Discretion to vary thresholds: Paragraphs 5 and the footnote indicate APRA retains discretion to determine different thresholds for a particular ADI or RFC and to exempt ADIs from ARF 720.1A on condition they supply alternate information (the example referencing paragraph 16(1)(b) of the Financial Sector (Collection of Data) Act 2001). This provision continues a pattern in APRA reporting where blanket thresholds can be varied in institution‑specific determinations.

Limitations of the amendment history in the instrument

• The Determination records only the revocation of an immediately prior Determination (No. 3 of 2019) and its own making and commencement dates. It does not record a broader legislative amendment history, iterations of the form across multiple years, or the policy evolution that produced the changes. The instrument does not include an explanatory memorandum in the text provided here; paragraph 2 does record the purpose (ABS/RBA uses) but does not give a policy rationale for specific item changes.

• The footnote at the end indicates APRA’s ongoing discretion to adapt the scope of reporting (e.g., an ADI may be exempted from ARF 720.1A if it provides ARF 720.1B), which shows how the regime allows future operational amendments through individual determinations rather than through amendment of the Standard’s core text.

For practitioners reconciling historic datasets, the instrument signals a formal change point: the prior Reporting Standard ceased on registration and the new ARS 720.1 applies to reporting periods ending on or after 31 March 2022. Systems and reconciliation procedures must therefore be adjusted from that effective period, and prior reports should be archived and reconciled to the new item definitions and derived fields. The Standard’s numerous cross‑references to ARF 720.0A/B and ARF 323.0 will require particular attention where earlier versions of those forms differ.

The Schedule and the Determination text do not reference any litigation, judicial decisions or tribunal findings concerning ARS 720.1, its predecessor or APRA’s reporting requirements. The instrument records only the statutory basis for its making (paragraph 13 of the Act and the delegate’s exercise of power) and administrative commencement under section 15. No cases, disputes, or decisions are cited in the text provided.

What is present in the source

• The Determination indicates it is a statutory administrative instrument made by APRA’s delegate and does not purport to alter criminal or civil law beyond the reporting obligations; it does not contain a section summarising litigation history or judicial interpretation.

How to treat litigation risk in practice (procedural note, source‑bounded)

• The Reporting Standard imposes administrative obligations (reporting, auditor review, digital sign‑off). Non‑compliance could give rise to APRA supervisory action under the Financial Sector (Collection of Data) Act 2001 or other legislation, although the Reporting Standard itself does not list statutory penalties. Where supervisory action leads to litigation (for example, judicial review of an APRA direction or enforcement action), that litigation would be in the domain of the parent Act and applicable administrative law. The Reporting Standard does not identify any precedent.

• Practitioners should therefore treat the absence of litigation references as the instrument simply not recording any litigation history. It is silent on prior legal contestation. Any judicial interpretation of APRA’s exercise of collection powers or of the content of reporting standards would appear in case law external to this instrument and is not provided in the text.

Given the absence of any recorded litigation within the source text, there is no reportable litigation history to summarise from the instrument itself.

The Reporting Standard contains numerous technical and operational features that can catch reporting entities out if they are not carefully implemented. The following items flag precise traps that the instrument itself sets up.

1. Thresholds and measurement of ‘total assets’ produce discontinuities (paragraphs 4 and 9 notes). The table in paragraph 4 pairs institution class with the relevant form (ARF 720.1A or ARF 720.1B) but the frequency of reporting depends on different numeric thresholds in paragraph 9. For example, an ADI in Reporting Category A may be required to submit the Reduced form only if total assets ≥ $200 million (paragraph 4 table), but paragraph 9 then treats ADI Category A with total assets ≥ $200 million as required to report monthly. The instrument further specifies how to measure ‘total assets’ (note under paragraph 9: use item 13 column 1 on ARF 720.0A/B or item 11 on ARF 323.0 as at 31 December prior year). Practitioners must follow those precise measurement points for threshold determination; rounding or using an alternate balance date can change whether an organisation files monthly or annually and which form it must file.

2. Differences from ARF 720.0A/B in resident/non‑resident treatment (multiple places). ARF 720.1A/B repeatedly note that loans and finance leases to non‑residents are excluded unless directed, and that this differs from ARF 720.0A where non‑residents are not separately identified. It is therefore essential to check which returns require resident/non‑resident breakdowns and which do not: failing to apply these exclusions or including non‑residents when the instruction says to exclude them will create misaligned totals and reconciliation issues.

3. Gross reporting of loans and finance leases (Values and repeated statements). The Standard instructs reporting credit outstanding gross of individual and collective provisions even if accounting standards might present a net figure. The forms, however, also require separate reporting of individual and collective provisions in their own columns. Practitioners who rely on accounting ledgers or financial statement aggregates may mistake net reporting for required gross reporting.

4. Currency conversion and derived fields (Values and Item instructions). The Standard requires conversion of foreign currency amounts to AUD using AASB 121, and many entries are derived items or must reconcile to items on ARF 720.0A/B. A mismatch in the exchange rate date or method can produce derived item inconsistencies and reconciliation differences. The forms also require a separate column for amounts denominated in foreign currency expressed in AUD equivalent, so dual handling of source currency and converted AUD is needed.

5. Exclusion of intra‑group loans and securitisation perimeter issues (Counterparties; Items 4 and 5). Intra‑group loans are excluded and reported on ARF 720.3. Securitised loans are split between on‑balance sheet (Item 4) and off‑balance sheet (Item 5) reporting. Distinguishing self‑securitised from other securitised exposures and determining whether an exposure is on‑balance sheet or off‑balance sheet can be operationally complex. The Instrument notes that loans reported in item 5 are outside the domestic books consolidation and will not be reported on ARF 720.0A. Misclassification across these buckets will produce inconsistencies.

6. Auditor review scope and timing (paragraph 13). The Standard requires that information be the product of systems and controls reviewed and tested by the external auditor as set out in APS 310 or RRS 710.0 and that the review be done annually or more frequently if required by the external auditor. This means institutions cannot postpone establishing audit‑supporting evidence until after first submission; auditors must be engaged early to scope their testing against APRA’s expectations.

7. Tight lodgement window and digital signing (paragraphs 10 and 15). All returns are due within 10 business days after the end of the reporting period. For monthly reporters this gives a short turnaround. In addition, APRA requires digital signing using an APRA‑acceptable certificate when using a notified method. Failure to have an acceptable digital credential configured will prevent valid submission within the deadline.

8. APRA discretion to vary thresholds and frequency (paragraphs 5 and 11). APRA may set different thresholds or require more frequent reporting for particular ADIs/RFCs. An institution cannot assume the table in paragraph 4 is immutable for its specific circumstances; APRA can notify a higher threshold or alternative frequency in writing.

9. SBR and accounting type mapping. The forms require SBR codes and an accounting type (debit/credit) for each column. Mapping the firm’s internal chart of accounts and SBR taxonomies to APRA’s required accounting types is a non‑trivial data transformation task.

10. Derived items that equal items on other ARFs. Many items are explicitly derived and must match items on ARF 720.0A/B. Where an institution files both ARF 720.0A/B and ARF 720.1A/B, the forms must reconcile. Failures here will trigger queries and potentially supervisory follow up.

In short, the gotchas are operational: thresholds and their measurement dates; resident/non‑resident treatment; gross reporting versus accounting net presentation; exchange rate treatment and derived field reconciliation; securitisation and off/on balance sheet classification; auditor engagement timing; tight lodgement schedules with digital signature requirements; and mapping to SBR/accounting types. Each of these matters is directly specified in the Reporting Standard and its instructions.

This section sets out a practical compliance checklist aligned to the Reporting Standard’s text and instructions. Each task ties back to specific paragraphs or instructions in the Schedule.

1. Determine applicability and form to file (paragraph 4; paragraph 9 notes)

   • Identify whether you are an ADI (Category A or B) or RFC and confirm the reporting category classification used by APRA.
   • Measure ‘total assets’ using the specified source:
     • For ADIs, use the value reported in item 13 (column 1) on ARF 720.0A/B or item 11 (column 1) on ARF 323.0 as at 31 December of the prior calendar year (paragraph 9 note).
     • For RFCs, use item 13 (column 1) on ARF 720.0A as at the last day of the RFC’s prior financial year (paragraph 9 note 2).
   • Use those measures to determine whether you file ARF 720.1A (Standard) or ARF 720.1B (Reduced) and whether monthly or annual frequency applies (paragraphs 4 and 9).

2. Establish domestic books consolidation and perimeter mappings (paragraph 7)

   • Confirm the domestic books consolidation perimeter for your firm and document the mapping from statutory financial statements to the APRA reporting consolidation.
   • Identify and exclude intra‑group (related party) loans and finance leases from ARF 720.1 submissions; plan to report those on ARF 720.3 as instructed in the forms and counterparty notes.

3. Data extraction and item mapping (form instructions, Items 1-6)

   • Map ledger/product codes to APRA item codes for:
     • Counterparty categories: households, non‑financial businesses (with sub‑categories), financial institutions (specific sub‑classes), general government, community service organisations, residents vs non‑residents (and confirm treatment per form).
     • Product categories: housing loans (owner‑occupied vs investment), personal loans (credit cards, finance leases, margin loans, fixed‑term loans, other revolving), business product types, securitisation on/off balance sheet, and non‑performing exposures by days past due and security.
   • Ensure reporting is at end-of-period balances and in whole dollars (forms: Reporting basis and unit of measurement).

4. Reconcile gross reporting and provisions (Values and Item 1 instructions)

   • Prepare credit outstanding gross of collective and individual provisions for reporting columns and separately supply individual and collective provisions columns where required (forms state gross reporting even if accounting treatment nets provisions).
   • Exclude associated deferred tax assets from the amounts reported for collective and individual provisions (instructions).

5. Foreign currency conversion (Values)

   • Convert foreign currency amounts to AUD in accordance with AASB 121. Maintain exchange rate source, date and method documentation because ARF 720.1A includes a column for amounts denominated in foreign currency (AUD equivalent).

6. SBR and accounting type setup (SBR notes)

   • Ensure data submissions use the correct Standard Business Reporting (SBR) accounting types (debit for assets, credit for provisions/liabilities where specified).
   • Validate SBR file formats, schemas and tags with APRA submission requirements.

7. Electronic transmission and digital signing (paragraphs 8 and 15)

   • Register for the APRA electronic submission method published on APRA’s website or seek notice of any alternative method APRA may notify (paragraph 8).
   • Obtain and configure an APRA‑acceptable digital certificate or digital identity credential for authorised officers/agents to use when submitting (paragraph 15). Test the end‑to‑end upload and digital signing process ahead of the first live submission.

8. External auditor engagement and internal controls (paragraph 13-14)

   • Engage the external auditor early so the auditor can review and test systems, processes and controls as required under APS 310 (ADIs) or RRS 710.0 (RFCs). Schedule auditor work to complete at least annually and earlier if auditors require more frequent testing.
   • Document internal systems, processes and authorisation controls for the internal review and authorisation of reported information. Ensure audit trails and supporting evidence are retained.

9. Reconciliations and derived items (form instructions)

   • Implement automated reconciliations for derived items that must equal sums of other items or that must reconcile to items on ARF 720.0A/B and ARF 323.0.
   • Produce a reconciliation schedule between financial statements, ARF 720.0A/B, ARF 720.1A/B and ARF 720.3 as applicable to facilitate audit review and APRA queries.

10. Timing, schedules and contingency (paragraphs 9-12)

    • Build operational timelines aligned to the 10 business day lodgement deadline (paragraph 10). For monthly reporters, set internal close timetables that allow for data extraction, validation, auditor sign‑off (where required) and authorised digital signature.
    • Prepare a process for seeking an extension from APRA if late circumstances arise and keep records of any written extension notices (paragraph 12).
    • Monitor APRA communications in case APRA changes reporting periods or applies specific thresholds to a particular institution (paragraph 11 and paragraph 5).

11. Securitisation and off‑balance sheet reporting (Items 4 and 5)

    • Identify securitisation pipelines and determine whether loans are self‑securitised, other securitised on‑balance sheet, or off‑balance sheet securitised exposures and map them to the appropriate Item 4 or 5 fields.
    • Ensure off‑balance sheet securitisations outside of the domestic books consolidation are handled per Item 5 instructions and do not duplicate balances reported on ARF 720.0A.

12. Non‑performing exposures (Item 6)

    • Implement classification rules for NPEs in the Item 6 structure (>=30 to <90 days past due and well‑secured; non‑performing and well‑secured; 90+ days past due and well‑secured; non‑performing and not well‑secured).
    • Maintain supporting collateral valuation and ageing schedules to substantiate NPE classifications for audit and APRA queries.

13. Ongoing monitoring and change management

    • Assign a reporting owner accountable for liaison with APRA and for monitoring APRA notifications, including any institution‑specific determinations under paragraph 5 or paragraph 11.
    • Maintain a document control regime for APRA items, transformation logic, and mappings to accounting and ledger codes to preserve continuity across reporting cycles and to support audit and supervisory review.

14. Consider operational burden and resource planning

    • Budget for ongoing recurring costs: data engineering for SBR feeds, exchange rate handling, periodic external audit testing under APS 310/RRS 710.0, and governance resources for sign‑off and APRA liaison.

15. Test, validate and pre‑submission checks

    • Execute a formal set of pre‑submission validations that include SBR schema checks, accounting type validation, derived item reconciliation checks, foreign currency conversion verification, and confirmation that the designated officer can apply the APRA acceptable digital signature method.

Following these steps implements the specific duties and conventions set out in ARS 720.1 and its ARF forms and their instructions (paragraphs 7-15 and the itemised instructions and columns in the Schedule). Document everything: APRA and auditors will require documentation of the accounting logic, consolidation perimeter, exchange rate policy and the mapping used to produce each ARF item.