The Standard organises reporting around a small set of structural concepts that determine scope, granularity, measurement and the mechanics of submission.

• Reporting levels: Two distinct reporting levels are mandated. Every ADI completes the Licensed ADI version of ARF 220.0 for each reporting period (paragraph 5). A highest parent entity must additionally submit the Consolidated Group version (paragraph 6). The Standard’s instructions restate that the form is to be completed on both a licensed ADI and consolidated ADI group basis where applicable (Instructions, Reporting level).

• Reporting periods and cadence: The default frequency is quarterly aligned to the ADI’s financial year (paragraph 8). APRA may vary frequency for a particular ADI in writing, to either more or less frequent reporting, based on the ADI’s circumstances, supervisory needs, or RBA/ABS requirements (paragraph 9).

• Submission mechanics: Electronic format via APRA’s online method is required, or other APRA‑notified method (paragraph 7). An authorised officer or agent must digitally sign submissions using an APRA‑acceptable digital certificate (paragraph 14). APRA may extend a due date in writing (paragraph 11) and may make minor variations to the forms or instructions to correct technical errors or clarify instruction without changing substantive requirements (paragraphs 15-16).

• Quality and assurance: Reported information (except consolidated group information required under paragraph 6) must derive from systems, processes and controls that have been reviewed and tested by the ADI’s external auditor in accordance with APS 310 (paragraph 12). The Standard requires internal review and authorisation systems and controls to assure completeness and reliability (paragraph 13).

• Measurement and definitions: The instructions embed a taxonomy of credit concepts used throughout the form: non‑performing, past‑due, restructured, Stage 2 (AASB 9 lifetime expected credit loss but not credit‑impaired), well‑secured vs not well‑secured (definition depends on discounted fair value of security), sector classifications (households, CSOs, private trading corporations, RFCs, etc.) and treatment of particular facility types (housing, credit cards, revolving credit). The instructions require amounts to include on‑balance claims and credit equivalent amounts of off‑balance sheet exposures, and set rules for off‑balance measurement , e.g. include direct credit substitutes and commitments when there is reasonable doubt about collectability and report amounts without adjustment for credit conversion factors except for market‑related off‑balance sheet transactions (Scope and Off‑balance measurement).

• Securitisation deconsolidation: Where an ADI participates in a securitisation that meets APRA’s operational requirements under APS 120, special purpose vehicles (SPVs) may be treated as non‑consolidated independent third parties for reporting purposes and the SPV assets may be excluded from the ADI’s regulatory reporting (Instructions, Securitisation deconsolidation). However retained securitisation exposures must still be reported in ARF 120.1 and associated RWA in ARF 110.0.1/110.0.2.

• Interactions with accounting and prudential standards: The Standard explicitly cross‑references AASB standards (AASB 9, AASB 121) and APRA prudential standards (APS 220, APS 112, APS 120, APS 310). For example, currency conversion is per AASB 121, provisioning totals include all provisions measured in accordance with AASB 9 (Scope), and netting/offsetting follows APS 112 (Scope).

• Derived items and disaggregation: Many items in the ARF 220.0 are derived sums of sub‑items (for example Item 2.1.1 is the sum of 2.1.1.1-2.1.1.4; Item 2.3 is the sum of 2.1.1-2.1.5 and 2.2). The instructions repeatedly identify derived items and require separate reporting for Australian and overseas books where asked (Section A instructions and many item blocks).

Those concepts define the unit of reporting, which exposures must be counted, the form of those counts, the assurance that must underlie them, and how APRA may change reporting frequency or adjust forms without changing substantive requirements.

Primary obligated entities

• All authorised deposit‑taking institutions (ADIs) are caught by the Standard: paragraph 3 states that ARS 220.0 applies to all ADIs. The term ADI has the meaning in the Banking Act 1959 (Interpretation, paragraph 17).

• Highest parent entities of consolidated ADI groups have additional obligations: if an ADI is a highest parent entity it must provide the Consolidated Group version of ARF 220.0 in addition to the Licensed ADI version (paragraph 6; see definition of highest parent entity in paragraph 17).

Branches and foreign ADIs

• Foreign ADIs operating via Australian branches are required to complete the form for the Australian branch only (Instructions, Reporting level). The Standard’s definition of foreign ADI references section 5 of the Banking Act 1959 (Interpretation, paragraph 17).

Internal actors within ADIs

• Officers or agents who submit the return must digitally sign the submission (paragraph 14). Senior management and the compliance, finance and risk teams will need to manage the internal review and authorisation systems that the Standard requires (paragraph 13).

External parties

• The ADI’s external auditor is directly implicated: information provided under the Standard (except that required under paragraph 6) must be the product of systems, processes and controls reviewed and tested by the external auditor in accordance with Prudential Standard APS 310 (paragraph 12). The Auditing and Assurance Standards Board guidance is explicitly referenced for the scope and nature of the review (paragraph 12).

Other agencies using the data

• The data are used by APRA for prudential supervision and may also be used by the RBA and ABS (paragraph 2). Those agencies thereby have a stake in the form and timing of the returns.

Operational and functional responsibilities

• Reporting Category A and B classification affects the numeric format and measurement units required (Instructions, Reporting basis and units of measurement). This affects reporting teams and systems that must output numbers in different rounding and unit conventions.

Who is not explicitly targeted

• The Standard does not require non‑ADI entities to report under ARF 220.0; it is focused on ADIs and consolidated ADI groups as defined (paragraphs 3, 5-6, and Interpretation in paragraph 17). Other financial corporations are defined for categorisation of counterparties but are not the reporting entities for ARF 220.0.

Geographic scope

• The requirement to report separately Australian and overseas book amounts where requested (Scope and Section A instructions) means entities with cross‑border operations must establish collection and aggregation processes for both local and foreign books. The Standard applies to reporting periods ending on or after 31 March 2022 (paragraph 4).

In summary, the Standard places recurring reporting, assurance and sign‑off obligations on every ADI and adds consolidation reporting for highest parent entities. It pulls external auditors into the verification loop and supplies data to APRA and, potentially, other official agencies.

Duties imposed on ADIs

• Provide ARF 220.0 for each reporting period: Each ADI must provide the information required by the version of ARF 220.0 designated for a Licensed ADI for each reporting period (paragraph 5).

• Additional consolidated reporting: A highest parent entity of a consolidated ADI group must also provide the Consolidated Group version for each reporting period (paragraph 6).

• Electronic submission and signature: Information must be given to APRA in electronic format using APRA’s electronic method (paragraph 7). The submitting officer or agent must digitally sign the information with a digital certificate acceptable to APRA (paragraph 14).

• Timing obligations: Standard due date is within 35 calendar days of quarter end (paragraph 10). APRA may extend the due date in writing if it chooses (paragraph 11).

• Quality, systems and audit testing: All information provided (other than that required under paragraph 6) must be the product of systems, processes and controls reviewed and tested by the external auditor, in accordance with APS 310 (paragraph 12). Reporting must also be subject to internal review and authorisation processes (paragraph 13).

• Measurement and content duties: ADIs must include on‑balance claims and credit equivalent amounts of off‑balance sheet claims and commitments and follow the measurement policies for off‑balance sheet items as set out (Scope). Specific reporting items, disaggregations and derived calculations must be performed exactly as instructed in ARF 220.0 (Sections A-D and instructions).

• Apply relevant prudential and accounting rules: Currency conversion must follow AASB 121; total provisions must include provisions measured in accordance with AASB 9; netting must comply with APS 112 where eligible; and ADIs must refer to APS 220 and APS 120 where the instructions say so (Instructions, Scope and Definitions).

Rights and discretions retained by APRA

• APRA may change reporting periods for particular ADIs: it can alter reporting periods, including increasing or decreasing frequency, by written notice having regard to the ADI’s circumstances, supervisory need and RBA/ABS requirements (paragraph 9).

• APRA may extend due dates and vary forms: APRA may extend due dates in writing (paragraph 11) and make minor variations to the forms and instructions to correct technical errors or clarify application without changing substantive requirements; it must notify each ADI in writing if it does so (paragraphs 15-16).

• APRA determines acceptable digital certificates and submission methods: paragraph 7 requires submission via an electronic method available on APRA’s website or otherwise notified by APRA; paragraph 14 requires a digital certificate “acceptable to APRA”.

Reporting obligations that impose calculation and data governance duties

• Derived items and sectoral breakdowns are required throughout (e.g. Item 2.3 is the sum of 2.1.1 to 2.1.5 and 2.2). ADIs must operationalise the calculation rules exactly as set out in the form instructions.

• Specific treatment of securitisations: where an ADI participates in a securitisation meeting APS 120 operational requirements, SPV assets may be treated as non‑consolidated for reporting, but retained securitisation exposures and associated RWA must still be reported in ARF 120.1 and ARF 110.0.1/110.0.2 respectively (Instructions, Securitisation deconsolidation).

Duties APRA does not state in this Standard

• The Standard itself does not enumerate penalties or enforcement mechanisms. It is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1), and so enforcement would be a matter of the enabling legislation and APRA’s general powers, but the Standard text does not set out specific sanctions or administrative penalties.

Obligations that create cross‑functional duties inside an ADI

• The combined effect of the reporting content, auditor testing (paragraph 12), and internal authorisation (paragraph 13) means finance, credit risk, compliance, IT and audit functions will all have discrete duties to deliver accurate, timely and auditable data for ARF 220.0 returns.

In short, the Standard imposes recurring and precisely specified reporting duties, requires audit‑tested systems and internal authorisation, confers notice and extension rights to APRA, and delegates certain definitional and measurement obligations to APRA’s prudential and accounting standards.

What the Standard itself says

• The ARS 220.0 text does not specify penalties, enforcement procedures, or sanctions for non‑compliance within the Standard’s own provisions. It sets out reporting, submission, and assurance obligations but is silent on direct penalties or enforcement steps (the text contains no fines, civil penalty regimes, or criminal sanctions).

Implicit enforcement framework and where enforcement would arise

• The Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1). That Act is the statutory source of APRA’s data‑collection authority; any enforcement mechanisms would therefore be found in the enabling Act and in APRA’s general statutory powers rather than inside this Reporting Standard. The Standard itself does not describe that enforcement machinery.

Operational levers APRA retains that bear on compliance

• APRA’s capacity to vary reporting frequency and due dates by written notice (paragraphs 9 and 11) is an operational lever that can increase supervisory intensity for a particular ADI; escalation of supervisory requirements can be an indirect enforcement mechanism because more frequent reporting raises the compliance burden and supervisory attention.

• APRA may make minor variations to forms and instructions (paragraphs 15-16). While this is not an enforcement sanction, the ability to adjust forms quickly is an administrative tool that can change reporting requirements and thereby require ADIs to adapt systems and processes rapidly.

Practical enforcement risk to ADIs

• Because the Standard requires systems and controls to be reviewed and tested by external auditors in accordance with APS 310 (paragraph 12), a negative auditor finding or qualification around the reliability of reported information is likely to have regulatory consequences in practice. The Standard ties reporting to audit evidence, so failing audit tests will increase supervisory scrutiny even if the Standard itself does not set out explicit fines.

• The Standard’s requirement for digital signatures and APRA‑acceptable digital certificates (paragraph 14) creates a formal chain of responsibility for signatories; misuse or misrepresentation of signed returns could give rise to other regulatory or legal consequences under the broader legislative framework.

What is not in the Standard

• No schedule of penalties, no administrative monetary penalty amounts, no procedural directions for enforcement, and no internal APRA compliance escalation table are included in the ARS 220.0 text itself. Users must look to the Financial Sector (Collection of Data) Act 2001 and APRA’s broader enforcement policies for that material.

For compliance officers and in‑house counsel the practical takeaway is this: ARS 220.0 sets binding reporting duties and audit/authorisation requirements but does not itself contain a penalty regime; enforcement will be exercised via the statutory framework that empowers APRA and through supervisory consequences triggered by audit findings or failure to meet reporting obligations.

Explicit cross‑references in the Standard

• Financial Sector (Collection of Data) Act 2001: ARS 220.0 is made under s 13 of that Act (paragraph 1). The Act is therefore the statutory source of authority for the Standard.

• Corporations Act 2001: The term financial year is used with the meaning given by the Corporations Act 2001 for the purpose of determining reporting quarters (paragraph 8). AASB is given the meaning in section 9 of the Corporations Act (Interpretation, paragraph 17).

• Banking Act 1959: The term ADI is defined with reference to the Banking Act 1959 (Interpretation, paragraph 17). The term foreign ADI references section 5 of the Banking Act (Interpretation, paragraph 17).

• Australian Prudential Regulation Authority Act 1998: APRA is referenced as the authority established under that Act (Interpretation, paragraph 17).

• APRA Prudential Standards: The Standard explicitly references several APRA prudential standards:

  • APS 220 Credit Risk Management: the definition of non‑performing and instructions for completing the form refer to APS 220 (Definitions and Specific instructions).
  • APS 120 Securitisation: the securitisation deconsolidation principle in the instructions depends on APRA’s operational requirements under APS 120 and links to reporting in ARF 120.1, ARF 120.2 and RWA reporting in ARF 110.0.1/110.0.2 (Instructions, Securitisation deconsolidation).
  • APS 310 Audit and Related Matters: external auditor review and testing should be done as set out in APS 310 (paragraph 12).
  • APS 112 Capital Adequacy: Standardised Approach to Credit Risk: netting and offsetting amounts under legally eligible netting arrangements should be handled as outlined in APS 112 (Scope).

• Australian Accounting Standards Board (AASB) standards:

  • AASB 9 Financial Instruments: provisions reported must include all provisions measured in accordance with AASB 9 (Scope).
  • AASB 121 The Effects of Changes in Foreign Exchange Rates: foreign currency amounts are to be converted to AUD in accordance with AASB 121 (Instructions, Reporting basis and units of measurement).
  • AASB 127 is used in the definition of consolidated ADI group and subsidiary (Interpretation, paragraph 17).

• ARS 701.0 ABS/RBA Definitions for the EFS Collection: Reporting Category A and B are defined by Reporting Standard ARS 701.0 (Interpretation, paragraph 17).

Interactions and practical consequences

• Measurement alignment: By requiring AASB 9 and AASB 121 treatment, and pointing to APS prudential rules for netting and securitisation, the Standard ensures reported credit quality metrics align with accounting recognition and APRA prudential treatments. Reporting units that prepare accounting provisions per AASB 9 will include those amounts in the ARF 220.0 provisions totals (Scope).

• Capital reporting linkages: The securitisation deconsolidation principle permits excluding SPV assets from some APRA returns, but retained securitisation exposures must still be reported in ARF 120.1 and risk‑weighted assets in ARF 110.0.1/110.0.2. That couples ARF 220.0 reporting with capital adequacy and securitisation returns (Instructions). Firms must therefore coordinate credit quality reporting with capital returns to ensure consistency.

• Auditor and supervisory alignment: External auditor review required under APS 310 ties the Standard directly into the audit regime; audit scope and timing will influence internal control testing and may create audit‑report dependencies between financial statement auditors and regulatory reporting teams (paragraph 12).

• Netting and off‑balance exposures: APS 112 netting rules must be applied for offsets where legally eligible (Scope). Off‑balance items are otherwise to be reported without adjustment for credit conversion factors (except market‑related off‑balance transactions). This produces a reporting treatment that may differ from some capital or accounting approaches, so reconciliation processes are required.

• Hierarchy of instruments and instruments‑by‑regime: The Standard explicitly defers to other Prudential Standards for several definitional and operational matters (APS 220 for non‑performing and restructured definitions, APS 120 for securitisation operational requirements). That creates an operational dependency: changes in those Prudential Standards will change how ARF 220.0 is completed even if ARS 220.0 itself is unchanged (Interpretation, paragraph 18).

Limits of the Standard’s coverage

• Enforcement and penalties are not specified within ARS 220.0; enforcement would rest with the broader legislative framework (see Penalties and enforcement above). The Standard does not set capital requirements or supervisory thresholds itself; it is a data‑collection instrument that interfaces with the rules that set those requirements (e.g. APS 110 series for capital).

To comply, ADIs must treat ARS 220.0 as a node in a network of prudential and accounting instruments: the Standard specifies the data and format, but the precise content and treatment of many items is governed by other APRA prudential standards and AASB accounting standards that the form cross‑references.

What the text records

• Effective date: The Standard applies to reporting periods ending on or after 31 March 2022 (paragraph 4). The text therefore contains a clear commencement boundary.

• Authority: The Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1). That identifies the statutory source but does not itself record prior versions or amendment dates.

APRA’s capacity to vary the form

• Minor variations: APRA may make minor variations to a form that is part of the Reporting Standard and to the instructions to correct technical, programming or logical errors, inconsistencies or anomalies or to clarify instruction application, provided APRA does not change any substantive requirement in the form or instructions (paragraph 15). When APRA makes such a variation it must notify in writing each ADI required to report under the Standard (paragraph 16). Those paragraphs allow limited administrative amendments without a formal reissuance of the Standard.

• Frequency and due date changes: APRA may change reporting periods for a particular ADI or extend due dates by written notice (paragraphs 9 and 11). Those are not textual amendments to the Standard, but they are operational changes APRA may make in relation to particular ADIs.

What is not recorded in the text

• No chronological amendment log is provided in the copied text; no prior version dates, amendment items, or historical notes are present in the attached material. There is no list of previous edits or a version control trail embedded in the Standard text as provided.

Practical inference for users

• Users should treat the Standard as current as of its stated commencement (31 March 2022) and monitor APRA notices for any minor variations or instructions as APRA must notify ADIs in writing when it makes changes under paragraph 15-16. Because the Standard defers to other instruments (APS 220, APS 120, APS 310, APS 112, AASB standards), ADIs must also track changes to those instruments, since changes to them will alter how ARF 220.0 is to be completed even if ARS 220.0 is unchanged (Interpretation, paragraph 18).

• The Standard’s text explicitly contemplates administrative updates without substantive change to form content. ADIs should therefore maintain a change‑control process for regulatory reporting that captures APRA notifications under paragraphs 9, 11, 15 and 16 and coordinates updates to internal systems.

In short, the Standard itself records a commencement date and delegates limited amendment powers to APRA for minor corrections and administratively altering frequency or due dates; it does not supply a version history in the provided text.

What the Standard says

• The Reporting Standard text does not mention any litigation, judicial review, or case law. There are no cases named in the Standard, and no litigation record is provided.

What can be concluded from the absence of litigation material

• The Standard is an APRA administrative instrument made under s 13 of the Financial Sector (Collection of Data) Act 2001. The text as provided contains no information about challenges to the Standard, judicial interpretations of its provisions, or legal disputes arising under it.

Implication for practitioners

• Because the document contains no litigation history, practitioners seeking judicial interpretation of any provision would need to search case law and administrative decisions external to the Standard text. The Standard does cross‑reference other instruments (for definitions and methodology), so litigation about those instruments (for example disputes about APS 220 treatment) may indirectly affect how ARF 220.0 is completed. However, the Reporting Standard text supplied contains no litigation particulars to cite.

Practical note

• Where legal certainty is required on a particular reporting treatment (e.g. whether a securitisation meets APRA’s operational requirements under APS 120, or the correct netting treatment under APS 112), practitioners should consider seeking APRA guidance or legal advice because the Standard itself does not provide precedential or adjudicative material.

This section flags technical features and traps in the Standard and Instructions that commonly cause operational or compliance surprises. Each item is grounded in the text.

1. Audit requirement excludes consolidated group information required under paragraph 6

• Paragraph 12 requires external auditor review and testing of reported systems, processes and controls, but explicitly excepts the information required under paragraph 6 (the consolidated group submission). That means the Licensed ADI returns are audit‑tested annually under APS 310, but the consolidated group return is not covered by that external auditor testing requirement within ARS 220.0. This is a non‑intuitive carve‑out that affects assurance planning.

2. Securitisation treatment can remove pools from ADI reporting yet leave retained exposures to be reported elsewhere

• The Securitisation deconsolidation principle in the Instructions allows SPVs that meet APS 120 operational requirements to be treated as non‑consolidated for APRA reporting and to have their assets excluded (Instructions, Securitisation deconsolidation). However retained securitisation exposures remain reportable in ARF 120.1 and associated RWA in ARF 110.0.1/110.0.2. ADIs must therefore reconcile what disappears from ARF 220.0 portfolio totals with what remains reportable in other returns. Incorrect reconciliation will cause inconsistent reporting across returns.

3. Off‑balance sheet measurement rules are specific and not always intuitive

• The Scope requires inclusion of direct credit substitutes, certain commitments, and that off‑balance items be reported without adjustment for credit conversion factors (except for market‑related off‑balance transactions), risk weights, provisions, or collateral arrangements (Scope). That produces reporting figures that may differ materially from risk‑weighted capital metrics or expected loss calculations. ADIs need translation logic between accounting/capital views and ARF 220.0 presentation.

4. Overdrafts and unauthorised overdrafts trigger specific days‑past‑due and default rules

• The definition of >=90 days past‑due explicitly addresses overdrafts: overdrafts are past‑due once the borrower breaches an advised limit or is advised of a smaller limit; non‑authorised overdrafts are considered to have a zero limit for regulatory capital purposes and days past‑due commence once credit is granted to an unauthorised borrower and not repaid within 90 days, at which point the exposure must be treated as in default (Definitions). That can accelerate default classification for overdrafts versus other facility types.

5. Units and rounding differ by Reporting Category

• Reporting Category B ADIs report in millions of AUD rounded to one decimal place, while Reporting Category A ADIs report in whole AUD without decimals (Instructions, Reporting basis and units of measurement). This affects aggregation, rounding, and reconciliation between entities of different reporting categories.

6. Derived items and many disaggregations create numerous reconciliation points

• Many items are derived sums of sub‑items (e.g. Item 2.3, Item 6.3). Operationally this creates many reconciliation checkpoints and increases the risk of arithmetic or mapping errors. Systems must ensure the derived items in the return are consistent with the underlying reported sub‑items.

7. Definitions depend on other standards

• Terms such as Non‑performing, Past‑due, Restructured, Stage 2 and Prescribed provisioning ADIs are defined by APS 220 or AASB 9, or elsewhere. The Standard tells the reporter to refer to those instruments (Definitions and Specific instructions). Failing to track changes in those instruments will produce inconsistent reporting even if ARS 220.0 itself is unchanged.

8. Netting and eligible offsets are governed by APS 112, not by the Standard itself

• The Scope instructs amounts net of legal netting arrangements as outlined in APS 112. That means ADIs must build APS 112 compliance into ARF 220.0 calculations; applying different netting logic will misstate exposures.

9. Digital certificate and signature requirements are APRA‑specified and may change

• Paragraph 14 requires signatures via a digital certificate acceptable to APRA. The Standard does not specify certificate standards, so ADIs must monitor APRA notifications and test their signing infrastructure against APRA‑accepted options.

10. The Standard permits APRA to change frequency or due dates for a particular ADI

• Paragraph 9 gives APRA the written‑notice power to require more or less frequent reporting for a particular ADI, having regard to circumstances and supervisory need. That creates uncertainty and potential sudden operational burden if APRA increases reporting frequency.

11. Provisions must include AASB 9 measured amounts , potential timing mismatches

• Scope requires total provisions to include all provisions measured in accordance with AASB 9. Timing mismatches between forward‑looking expected credit loss provisioning (AASB 9) and operational provisioning practices can lead to volatility in reported provisions.

12. Separate reporting for Australian and overseas books where requested

• The Standard repeatedly requires separate Australian and overseas reporting (Scope, Section A and many items). ADIs must be able to segregate exposures by jurisdiction for the same instrument set.

These “gotchas” are features embedded in the Standard and Instructions; they create specific operational, systems and governance tasks that must be handled explicitly to avoid inconsistent or incorrect reporting.

A practical, source‑grounded checklist for ADIs and their reporting, risk and finance teams. Each step ties back to the Standard text.

1. Establish governance and responsibilities

• Assign clear ownership of the ARF 220.0 production cycle across credit risk, regulatory reporting, finance and IT. The Standard requires internal review and authorisation systems (paragraph 13) and digital signature by an officer or agent (paragraph 14), so define signatory authority and internal authorisation workflows.

2. Map the reporting scope and taxonomy

• Use the ARF 220.0 instructions to map each item to source systems. The form contains Sections A-D with detailed line items and derived items; ensure your mapping covers households, CSOs, private trading corporations, RFCs, financial corporations and other counterparts per the Definitions (instructions tables). Map how on‑balance and off‑balance exposures are included (Scope).

3. Implement measurement policies consistent with referenced standards

• Confirm that currency conversions follow AASB 121 (Instructions), that provisions reported include AASB 9 measured amounts (Scope), and that netting is applied only where legally eligible per APS 112 (Scope). For securitisation positions, apply APS 120 operational requirements and ensure retained exposures are reported in ARF 120.1 and RWA in ARF 110.0.1/110.0.2 (Instructions).

4. Prepare systems to calculate off‑balance and credit‑equivalent amounts

• The Standard requires inclusion of credit equivalent amounts for off‑balance sheet claims and commitments (Scope). Build logic to include direct credit substitutes, commitments when there is reasonable doubt about collectability, and to report off‑balance items without credit conversion factor adjustments except market‑related transactions (Scope).

5. Establish external audit coordination

• Paragraph 12 requires external auditor review and testing of the systems, processes and controls that generate the returns (except consolidated group info under paragraph 6). Coordinate annual audit testing under APS 310 and engage auditors early to define scope and timing aligned with the reporting calendar.

6. Build reconciliations across returns and internal records

• Because securitisation deconsolidation may remove SPV pools from ARF 220.0 while leaving retained exposures in ARF 120.1 and RWA in ARF 110.0.1/110.0.2, build reconciliations linking ARF 220.0 to ARF 120.x and ARF 110.x. Also reconcile ARF 220.0 figures to balance sheet and provisioning figures derived under AASB 9 to ensure consistency.

7. Implement digital submission and signature process

• Ensure the electronic submission method required by APRA (paragraph 7) is implemented and tested. Obtain and maintain a digital certificate “acceptable to APRA” for the authorised signatory (paragraph 14) and test end‑to‑end submission well before due dates.

8. Prepare for disaggregation and derived items

• Many items are derived sums. Automate the arithmetic where possible and implement checks to ensure Item totals equal the sums of their sub‑items (e.g. Item 2.3 = Items 2.1.1-2.1.5 + Item 2.2). Implement edit checks for internal sign‑off.

9. Handle reporting categories and rounding rules

• Identify whether the ADI is Reporting Category A or B for unit conventions (Instructions). Category B reports in millions of AUD to one decimal; Category A reports whole AUD. Confirm how external and internal reports will present the numbers for internal users.

10. Plan for frequency changes or special notices

• Paragraph 9 allows APRA to change reporting frequency by notice and paragraph 11 allows APRA to extend due dates. Establish a change‑control process to respond to APRA notices, update implementation plans and reassign resources where APRA increases reporting frequency.

11. Document definitions and decision rules

• Create an internal reporting manual that records treatment rules for >=90 days past‑due, overdrafts, well‑secured vs not well‑secured (including the requirement for prescribed provisioning ADIs to refer to Attachment B of APS 220), Stage 2, non‑performing and restructured exposures per APS 220 and AASB 9. Evidence of consistent application will be essential for both audit and supervisory review.

12. Test and validate with dry runs and reconciliation cycles

• Run end‑to‑end dry runs that cover data extraction, conversion (AASB 121), aggregation, derived calculations, audit evidence capture and electronic submission. Validate against prior returns and against related ARF returns to detect mapping inconsistencies.

13. Maintain an APRA notification and monitoring log

• Because APRA may notify minor variations to forms and instructions (paragraph 15-16) and because referenced instruments may change (Interpretation, paragraph 18), maintain a formal log of APRA notifications and changes to other prudential or accounting standards that affect ARF 220.0 completion.

14. Coordinate with external accounting and audit teams

• Align timing with financial statement audit and auditor testing required under APS 310 (paragraph 12). Ensure auditors understand the regulatory reporting scope and evidence requirements so audit testing can be scheduled and scoped effectively.

15. Keep supervisory and regulatory liaison ready

• Be prepared to respond to APRA queries on definitions, securitisation operational compliance (APS 120) and netting under APS 112. Have documentation and reconciliations ready to support supervisory discussion.

Following these steps implements the Standard’s explicit requirements (paragraphs 5-15, Scope, Instructions and Definitions) and builds an operational environment that supports accurate, auditable and timely ARF 220.0 submissions.