The Standard organises around a few discrete legal and reporting concepts that drive obligations and implementation choices.

Reporting forms and versions: The core reporting vehicle is ARF 330.1, which exists in at least two designated versions: a Licensed ADI form for stand‑alone ADI operations, and a Consolidated Group form for highest parent entities reporting group-wide operations (paragraphs 5-6). The forms and their instructions are attached and form part of the Standard (objective and information required).

Reporting period and frequency: The default cadence is quarterly, aligned to the ADI’s financial year as defined in the Corporations Act 2001 (paragraph 8). APRA may change the reporting period for a particular ADI, increasing or decreasing frequency, by written notice with regard to the ADI’s circumstances, prudential needs, or RBA/ABS requirements (paragraph 9).

Timing by class: The Standard classifies ADIs into six classes (Australian‑owned bank, foreign subsidiary bank, branch of a foreign bank, building society, credit union, other ADI) and sets submission timeframes: 25 business days for most classes, 15 business days for building societies, credit unions and Cairns Penny Savings & Loans Limited specifically referenced in definitions (paragraph 10 and definitions in paragraph 17).

Quality assurance and audit: Most reported information (explicitly excepting the information required under paragraph 6, i.e. the consolidated group return) must derive from systems, processes and controls reviewed and tested by the ADI’s external auditor under Prudential Standard APS 310 Audit and Related Matters. The external auditor’s review and testing must be at least annual or more frequently if necessary to enable an auditor opinion on accuracy and reliability (paragraph 12). Separately, ADIs must implement internal review and authorisation processes to assure completeness and reliability (paragraph 13).

Submission mechanics and authorisation: APRA prescribes electronic submission via D2A or by another APRA-notified method and requires digital signing of submissions using an APRA‑acceptable digital certificate where D2A or a notified method is used (paragraphs 7 and 14).

Securitisation treatment and consolidation rules (instructions): The Instruction Guide annexed to the Standard sets a “securitisation deconsolidation principle” that, where an ADI participates in a securitisation meeting APS 120 operational requirements for capital relief, special purpose vehicles (SPVs) may be treated as non‑consolidated third parties for regulatory reporting and their assets, liabilities, revenues and expenses may be excluded from APRA regulatory reporting returns (Instruction Guide, Securitisation deconsolidation principle). The instructions also require retained securitisation exposures to be reported in ARF 120.1 and associated RWAs in ARF 110.0.1 and ARF 110.0.2. Consolidation exists otherwise in accordance with AASB 127 and AASB 3 (Instruction Guide, Consolidated ADI group).

Currency translation and accounting standards: The Instruction Guide directs conversion of foreign currency amounts to AUD per AASB 121 The Effects of Changes in Foreign Exchange Rates and references treatment of foreign currency derivatives under AASB 139. It also directs that the accounting consolidated group be determined per AASB 127 and AASB 3 and that the basis of preparation should follow Australian accounting standards except where specifically stated (Instruction Guide, Unit of measurement and Basis of preparation).

Authority and cross‑references: The Standard is explicitly made under the Financial Sector (Collection of Data) Act 2001 s13 (paragraph 1), and it cross‑references the Corporations Act 2001 (financial year definition), the Banking Act 1959 (ADI definition and foreign ADI), Prudential Standards APS 310 and APS 120, AASB accounting standards (AASB 3, 121, 127, 139) and the Financial Sector (Shareholdings) Act 1998 for the definition of “stake” used in the Standard’s definitions (paragraphs 17-18 and instruction notes).

Permitted form changes and notification: APRA may make minor variations to forms or instructions to correct technical or programming errors or to clarify instructions without changing substantive requirements, but must notify each affected ADI in writing of such variations (paragraphs 15-16).

These concepts collectively determine the content to be collected, the parties that must report, the timetable and delivery mechanism, the audit and internal control framework, and how accounting treatments such as consolidation, securitisation and currency translation are to be applied for APRA reporting purposes.

Primary affected entities: The Standard applies to all authorised deposit‑taking institutions (ADIs) within the meaning of the Banking Act 1959 (paragraph 3 and definitions in paragraph 17). That includes locally incorporated ADIs that call themselves banks, building societies or credit unions, branches of foreign banks (foreign ADIs), foreign subsidiary banks and “other ADIs” as defined (paragraph 17 and table at paragraph 10).

Differentiation by class: The Standard treats classes of ADI differently for timing and some procedural elements. The table in paragraph 10 sets shorter submission timeframes (15 business days) for building societies and credit unions (and Cairns Penny Savings & Loans is explicitly included in the credit union definition in paragraph 17); and 25 business days for Australian‑owned banks, foreign subsidiary banks, branches of foreign banks and other ADIs. Therefore smaller or mutual ADIs (building societies and credit unions) have materially tighter filing deadlines.

Group-level reporting: An ADI that is a highest parent entity in relation to a consolidated ADI group must submit the Consolidated Group ARF 330.1 in addition to the Licensed ADI return (paragraph 6). The highest parent entity is defined narrowly (locally incorporated, has at least one subsidiary, and is not itself a subsidiary of a locally‑incorporated ADI) in paragraph 17. The Instruction Guide elaborates that consolidated reporting is to follow accounting consolidation under AASB 127 and AASB 3, subject to securitisation deconsolidation rules (Instruction Guide, Consolidated ADI group).

Internal stakeholders affected: Inside reporting ADIs, the following functions will be materially involved: finance and accounting (preparing interest income/expense items, applying AASB translation rules), risk and regulatory reporting (mapping to ARF 330.1 and cross‑reporting to ARF 110/120 where securitisation exposures retained), internal audit and control (internal authorisation processes per paragraph 13), external auditors (annual review and testing under APS 310 as required by paragraph 12), and IT/operations (submission via D2A and management of digital certificates per paragraph 14).

External users and third parties: APRA is the data recipient and decision‑maker in respect of submission method, reporting frequency alterations and minor form changes (paragraphs 7, 9, 15). The RBA and ABS may also use collected data for their purposes (paragraph 2). External auditors and accountants are implicated by the mandatory auditor assurance requirement for most reported information (paragraph 12). Entities engaging in securitisation, SPVs and retained exposures will be affected by the deconsolidation and reporting cross‑references (Instruction Guide).

Who bears the cost: The compliance burden falls on reporting ADIs. Costs will include systems and process design to capture ARF 330.1 data, auditor fees necessary for the external auditor review under APS 310, internal control and authorisation processes, currency translation and consolidation accounting work, and operational costs for timely electronic submission and digital certificate management. APRA bears the cost of running the D2A service and managing submissions and notices, but those operational costs are not detailed in the Standard.

Who decides: APRA decides reporting methods, timing adjustments for individual ADIs, and may vary forms and instructions for technical reasons (paragraphs 7, 9, 15). The ADI’s external auditor decides the necessary scope and frequency of review required to form an opinion under APS 310 (paragraph 12).

In sum, the Standard imposes recurring, audited reporting obligations on the entire population of ADIs, with specific operational differentials by class and additional consolidated reporting for highest parent entities.

Statutory basis and primary duty: The primary statutory duty under this instrument is for each ADI to provide APRA with the information required by ARF 330.1 for each reporting period, via the designated version applicable to that ADI (Licensed ADI and, where applicable, Consolidated Group) (paragraphs 5-6). The duty arises under the Reporting Standard made pursuant to s13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1).

Submission method duty: ADIs must submit the required information in electronic format using APRA’s D2A application or another method that APRA has notified in writing prior to submission (paragraph 7). Where submission occurs by D2A or other APRA‑notified method, the submitting officer must digitally sign the information using a digital certificate acceptable to APRA (paragraph 14).

Timing duties: ADIs must report quarterly by reference to their financial year (paragraph 8). The Standard sets class‑based due dates measured in business days after the reporting period (paragraph 10 and the table). APRA may change reporting periods for particular ADIs by written notice if it considers the ADI’s circumstances or supervisory needs require more or less frequent reporting (paragraph 9). APRA may grant extensions to due dates in writing; the extension’s date becomes the new due date (paragraph 11).

Quality, audit and internal control duties: Most information (explicit exception: the consolidated group information required under paragraph 6) must be produced from systems, processes and controls reviewed and tested by the ADI’s external auditor under Prudential Standard APS 310; the auditor’s review must be annual or more frequent if required to enable an auditor opinion on accuracy and reliability (paragraph 12). All information must also be subject to the ADI’s internal review and authorisation processes to assure completeness and reliability (paragraph 13).

Duties linked to other regulatory instruments and accounting standards: ADIs must follow accounting consolidation rules per AASB 127 and AASB 3 when preparing consolidated returns (Instruction Guide). For securitisations meeting APS 120 operational requirements, SPVs may be deconsolidated for regulatory reporting while retained securitisation exposures must be reported in ARF 120.1 and related RWA items in ARF 110.0.1 and ARF 110.0.2 (Instruction Guide, Securitisation deconsolidation principle). Foreign currency reporting must follow AASB 121 and derivative treatment per AASB 139 (Instruction Guide, Unit of measurement).

Rights and APRA discretions: The Standard grants APRA multiple administrative discretions that affect reporting ADIs. APRA may:

• change reporting frequency for specified ADIs by written notice (paragraph 9);
• grant written extensions to due dates (paragraph 11);
• make minor variations to forms or instructions for technical or clarifying reasons without changing substantive requirements, with written notification to ADIs (paragraphs 15-16);
• notify the method of submission and accept alternatives (paragraph 7).

These provisions give APRA operational flexibility and provide ADIs with procedural rights to be notified of changes, and to seek or receive extensions in writing. The Standard explicitly states that references to Acts, Prudential Standards and Australian Accounting or Auditing Standards are to instruments “as in force from time to time”, which means ADIs must monitor changes in referenced standards (paragraph 18).

Duty exceptions and nuances: Paragraph 12 explicitly excludes the information required under paragraph 6 (the consolidated group return) from the external auditor review requirement referenced in paragraph 12. The Instruction Guide provides further nuance regarding securitisation deconsolidation and the treatment of SPVs for reporting purposes, which may alter what is included in an ADI’s regulatory reporting returns versus accounting consolidation.

Record‑keeping and basis of preparation: The Instruction Guide directs ADIs to follow AASB rules for translation, recognition of exchange differences, and basis of consolidation, and recommends following Australian accounting standards for interpretation, measurement and netting of interest income and expense unless otherwise stated (Instruction Guide, Unit of measurement and Basis of preparation). That places a de facto duty on ADIs to maintain records enabling these accounting treatments to be applied to the reporting dataset.

In short, the Standard imposes precise duties to submit ARF 330.1 data electronically, within class‑dependent timeframes, under audited controls, and aligned to specified accounting standards; it also sets out APRA’s administrative discretions and the ADI’s procedural rights to written notice or extensions.

The Reporting Standard itself does not set out specific penalties, fines or sanctions for non-compliance within the text provided. It is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1), and therefore its legal force and any enforcement mechanisms would operate in that statutory context. The Standard directs substantive reporting, quality control and procedural requirements, but does not include express enforcement powers or penalty schedules within its own provisions.

Operational enforcement levers evident from the instrument:

• APRA controls submission mechanics, timing, and may require changed frequency or alternative methods for particular ADIs (paragraphs 7 and 9). Those discretions provide administrative leverage to require more frequent reporting or to impose particular submission pathways appropriate to supervisory intensity.
• APRA may grant time extensions in writing (paragraph 11) and may make minor variations to forms or instructions with written notice (paragraphs 15-16). These are administrative tools rather than punitive measures.

Absence of expressed sanctions: Because the Standard as supplied does not state civil or criminal penalties, suspension or other sanctions, a compliance officer or external adviser should treat enforcement as falling outside the Standard itself and instead arising from the enabling Act and other prudential instruments. The Standard references Prudential Standard APS 310 for external auditor review obligations (paragraph 12), which could implicate supervisory action under APRA’s broader prudential regime if significant control failures are identified, but the Standard does not specify that outcome. The Standard also references the Banking Act 1959 and Corporations Act 2001 via definitions and cross‑references (paragraphs 17-18), and those Acts contain separate regulatory regimes and potential enforcement mechanisms.

Practical implication: Entities should not infer from the Standard alone that non‑compliance carries no consequences. The proper compliance approach is to assume that failure to satisfy the reporting requirements may expose the ADI to supervisory action under the Financial Sector (Collection of Data) Act 2001 and other prudential legislation, and to remedial action via APRA’s existing supervisory toolkit. The Standard, however, requires written notices for key administrative actions (paragraphs 9, 11, 15-16), meaning APRA is required to give written notice when exercising those discretions.

For a complete account of enforcement powers, penalties and sanctions that may flow from non‑compliance with reporting obligations, a reader must consult the Financial Sector (Collection of Data) Act 2001 and APRA’s broader prudential and enforcement policies; those instruments are not reproduced in this Reporting Standard.

This Reporting Standard expressly cross‑references and relies on multiple statutes, prudential standards and Australian Accounting and Auditing Standards. The Standard should be read and applied in that networked context.

Primary statutory nexus: The Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1). The definition of financial year used for reporting periods is drawn from the Corporations Act 2001 (paragraph 8). The Standard also uses the Banking Act 1959 for certain definitions, notably ADI and foreign ADI under section 5 of that Act (paragraph 17). The Financial Sector (Shareholdings) Act 1998 is used to define “stake” in paragraph 17 by reference to specified schedule provisions.

Prudential standards interplay: The Standard requires external auditor review and testing “as set out in Prudential Standard APS 310 Audit and Related Matters” (paragraph 12). It also references Prudential Standard APS 120 Securitisation in the Instruction Guide for the securitisation deconsolidation principle: securitisations that meet APS 120 operational requirements for regulatory capital relief permit SPVs to be treated as non‑consolidated for APRA reporting purposes; exposures retained or acquired by the ADI must still be reported in ARF 120.1 and corresponding RWAs reported in ARF 110.0.1 and ARF 110.0.2 (Instruction Guide, Securitisation deconsolidation principle). These cross‑references mean ADIs must map ARF 330.1 reporting not only to accounting standards but also to APS 310 and APS 120 operational rules.

Accounting standards: The Instruction Guide mandates use of Australian accounting standards for consolidation (AASB 127 and AASB 3) in determining the consolidated ADI group (Instruction Guide, Consolidated ADI group). Foreign currency conversion is to follow AASB 121 and treatment of foreign currency derivative contracts at the reporting date must follow AASB 139 (Instruction Guide, Unit of measurement). The Standard also states that references to AASB and other instruments are to be read as in force from time to time (paragraph 18). The basis of preparation recommends following Australian accounting standards for interpretation/definition, measurement and netting of interest income and expense (Instruction Guide, Basis of preparation).

Other reporting instruments: The Instruction Guide explicitly requires retained securitisation exposures to be reported in Reporting Form ARF 120.1 and risk‑weighted assets to be reported in Reporting Forms ARF 110.0.1 and ARF 110.0.2 (Instruction Guide, Securitisation deconsolidation principle). ARF 330.1 therefore interlocks with APRA’s capital adequacy and securitisation reporting frameworks.

Administrative law and procedural interaction: APRA’s abilities to change reporting frequency, methods and to make minor variations come with written notice requirements (paragraphs 9, 11, 15-16). That procedural detail places administrative obligations on APRA and creates a trail of documentary decisions that ADIs can monitor and, where appropriate, contest under administrative law remedies in the Courts or tribunals, though the Standard itself does not set out appeal processes.

Interpretive hierarchy and dynamic references: Paragraph 18 provides that references to Acts, Prudential Standards, Reporting Standards and Australian Accounting or Auditing Standards are to the instruments as in force from time to time. That establishes an updating mechanism: changes to underlying accounting standards or prudential standards will alter interpretation and application of ARF 330.1 in practice without formal amendment to this Reporting Standard. ADIs should therefore monitor changes to AASB standards, APS standards and the cited Acts.

Net effect: The Standard operates as part of APRA’s broader prudential reporting ecosystem, requiring ADIs to align ARF 330.1 reporting with accounting consolidation rules, securitisation capital relief rules, auditor assurance under APS 310, and cross‑reporting into APRA’s capital and securitisation returns. Compliance therefore requires coordination across the accounting, audit, regulatory reporting and treasury functions, and active monitoring of changes to the referenced laws and standards.

Commencement: The Standard states that it commences on 1 April 2018 (paragraph 4). That is the only explicit commencement or date‑of‑effect provided within the text supplied.

Power for minor variations: The Standard provides a mechanism for APRA to make “minor variations” to any form that is part of the Standard and to their instructions to correct technical, programming or logical errors, inconsistencies or anomalies, or to clarify instructions (paragraph 15). APRA may make such variations “without changing any substantive requirement in the form or instructions” and must notify each ADI required to report in writing if such a variation is made (paragraph 16). This gives APRA an in‑instrument administrative amendment pathway that does not require formal re‑making of the Standard for technical fixes.

Dynamic references to other instruments: Paragraph 18 makes clear that references to Acts, Prudential Standards, Reporting Standards and Australian Accounting or Auditing Standards are references to those instruments “as in force from time to time.” That language means the Reporting Standard’s interpretive content will shift as the referenced instruments change, without an express amendment to the Reporting Standard itself.

Absence of a redlined amendment list: The text supplied contains no schedule listing prior amendments, no consolidated amending instrument text, and no history of prior re‑issuance. There is no express record here of any changes after commencement. The only mechanism expressly preserved for change within this Standard is the minor variation power for forms and instructions (paragraph 15) and the dynamic reference clause (paragraph 18) that imports future changes in referenced instruments.

Practical consequence: Practitioners should track:

• APRA notifications under paragraph 16 for any minor variations to forms or instructions;
• changes to referenced Prudential Standards (notably APS 310 and APS 120) and AASB standards, because paragraph 18 imports future versions;
• any separate amending instrument published by APRA that republishes or amends the Reporting Standard outside the minor variations route, as none are listed here.

If an ADI needs a full legislative amendment history for compliance, it must obtain APRA’s consolidated version of the Standard and consult APRA’s Register of legislative instruments and notices, as this text alone does not contain an amendment log beyond the commencement date and the minor‑variations mechanism.

The text of Reporting Standard ARS 330.1 provided here contains no references to litigation, judicial determinations, tribunal decisions or disputes concerning the Standard. It does not cite any cases, nor does it include summaries of enforcement or contested decisions.

Implication for readers: There is no litigation history internal to this instrument to analyse. Where questions of interpretation, enforcement, or the validity of APRA’s exercise of discretions under this Standard arise in practice, those matters would be litigated under or in relation to the enabling legislation (for example, the Financial Sector (Collection of Data) Act 2001), the Banking Act 1959 or APRA’s prudential regime. Those materials and relevant case law would need to be examined separately because the Reporting Standard itself does not recount or reference any judicial decisions.

Research steps for practitioners: To determine whether any litigation has arisen concerning ARF 330.1 or its application, a practitioner should:

• search judicial and tribunal databases for decisions referencing APRA reporting obligations or ARF 330.1 specifically;
• check APRA announcements and decisions frameworks for any published enforcement actions or determinations relating to reporting compliance;
• examine the Financial Sector (Collection of Data) Act 2001 for any case citations or precedent that interpret APRA’s powers to require data or enforce reporting obligations.

Because the Standard cross‑references other instruments (APS 310, APS 120, AASB standards), litigation that affects interpretation of those instruments could indirectly affect how ARF 330.1 is applied; that potential indirect litigation history is not included in this text and must be sourced from the texts and case law on those instruments.

Several practical and technical pitfalls are embedded in the Standard and the annexed instructions; these are concrete items that create compliance or implementation risk.

Dual returns requirement: A highest parent ADI must submit both the Licensed ADI and the Consolidated Group versions of ARF 330.1 (paragraphs 5-6). Failure to identify the ADI’s status as a highest parent entity (per the definition in paragraph 17) can lead to an omitted consolidated return. The highest parent entity test is technical: locally incorporated, has at least one subsidiary per AASB 127, and is not itself a subsidiary of a locally incorporated ADI (paragraph 17).

Different timing by class and specific inclusion of a single entity: The submission timetable differentiates building societies and credit unions (15 business days) from most other ADIs (25 business days) (paragraph 10). Cairns Penny Savings & Loans Limited is specifically included in the credit union definition (paragraph 17). Small ADIs and mutuals therefore face a compressed deadline; systems and auditor timelines must be calibrated accordingly.

External auditor testing exception: Paragraph 12 requires external auditor review and testing for all information “except for the information required under paragraph 6.” Paragraph 6 covers the consolidated group return. That means the consolidated return is not subject to the same explicit external auditor review requirement under paragraph 12. Practitioners must therefore be clear which elements of the return are subject to external auditor assurance and which are not, and ensure internal controls compensate where necessary.

Securitisation deconsolidation nuance: The Instruction Guide permits SPVs that satisfy APS 120 operational requirements for regulatory capital relief to be treated as non‑consolidated independent third parties for regulatory reporting purposes and to have their assets, liabilities, revenues and expenses excluded from APRA reporting returns (Instruction Guide, Securitisation deconsolidation principle). However, the ADI must still report retained securitisation exposures in ARF 120.1 and related RWAs in the ARF 110.0 series. Misapplication of the deconsolidation principle can therefore cause double counting omissions or capital reporting gaps across ARF 330.1, ARF 120.1 and ARF 110.0.x.

Dynamic references: Paragraph 18 makes references to Acts, Prudential Standards and accounting/auditing standards operate “as in force from time to time.” That creates a moving target: changes in AASB standards or in Prudential Standards (notably APS 310 and APS 120) will alter reporting interpretation without amendment to this Standard. ADIs must actively track changes to those instruments.

Form changes without substantive amendment: APRA may make minor variations to forms or instructions to fix technical/programming errors or clarify application without changing substantive requirements (paragraph 15). While APRA must notify ADIs in writing (paragraph 16), practitioners should be aware that such changes can alter data‑mapping or submission field semantics and may require rapid technical fixes in reporting systems.

Foreign currency measurement traps: The Instruction Guide directs translation of foreign currency monetary and non‑monetary items and sets out specific AASB 121 rules for translation and recognition of exchange differences, distinguishing fair value measurement and historical cost measurement, and prescribing translation treatments for equity items and derivatives (Instruction Guide, Unit of measurement). Errors in exchange rate choice or hedge accounting treatment (AASB 139 interlink) will affect reported interest income and expense.

Dependence on D2A and digital certificates: Paragraphs 7 and 14 require the use of D2A or an APRA-notified method and, where D2A or another notified method is used, the digital signature of an officer using a certificate acceptable to APRA. Operational failure to obtain or maintain an acceptable digital certificate, or to have functioning D2A interface and validation, risks late or invalid submissions.

Scope ambiguity around “other ADI” and excluded entities: The definition of “other ADI” in paragraph 17 excludes Cairns Penny Savings & Loans Limited and certain other categories. Practitioners must properly classify an ADI to determine applicable timing and obligations; misclassification can change submission deadlines by 10 business days.

Reliance on external auditor judgment: Paragraph 12 allows the external auditor to require more frequent review and testing “if required by the external auditor to enable the external auditor to form an opinion.” That places judgement with the auditor; ADIs must budget for variable audit resource demands and potential additional cost and timing impacts.

Cross‑reporting obligations: The Instruction Guide directs reporting of retained securitisation exposures and RWAs in other ARFs (ARF 120.1; ARF 110.0.1 and ARF 110.0.2). Practitioners must ensure consistent definitions and data feeds across multiple APRA returns to avoid inconsistencies and reconciliation issues.

No enforcement specifics in the Standard: The Reporting Standard does not set out penalties or enforcement steps (see Penalties and enforcement). Practitioners should not interpret that absence as an absence of enforcement risk; APRA’s enforcement powers reside outside this instrument and non‑compliance can still trigger supervisory action under enabling legislation.

These “gotchas” mean ADIs should align legal classification, accounting consolidation, securitisation treatment, audit plans, IT submission architecture, and internal sign‑off procedures before the quarterly reporting deadlines.

A compliance roadmap, mapped directly to the Standard and instruction text, organised as discrete implementation tasks.

1. Identify reporting scope and entity classification

   • Confirm the ADI’s status: Licensed ADI (stand‑alone) and whether it is a highest parent entity requiring Consolidated Group reporting (paragraphs 5-6; definition of highest parent entity in paragraph 17).
   • Classify your ADI among the classes in paragraph 10 (Australian‑owned bank, foreign subsidiary bank, branch of a foreign bank, building society, credit union, other ADI) to determine applicable due dates.

2. Establish reporting calendar and deadlines

   • Set quarterly reporting aligned to the ADI’s financial year (paragraph 8).
   • Apply the relevant submission deadline: 25 business days for most ADIs, 15 business days for building societies and credit unions (paragraph 10).
   • Build calendar triggers for APRA notifications of changed reporting frequency (paragraph 9) and for seeking written extensions where necessary (paragraph 11).

3. Align accounting and consolidation treatments

   • Prepare ARF 330.1 data consistent with the accounting consolidated group determined under AASB 127 and AASB 3 unless an SPV meets APS 120 deconsolidation operational requirements (Instruction Guide, Consolidated ADI group; Securitisation deconsolidation principle).
   • For securitisations that meet APS 120 requirements, exclude SPV assets/liabilities from the reporting universe as permitted, but ensure retained securitisation exposures are reported in ARF 120.1 and RWAs in ARF 110.0.1 and ARF 110.0.2 (Instruction Guide).
   • Follow AASB 121 for foreign currency translation rules and AASB 139 for derivative measurement where applicable (Instruction Guide, Unit of measurement).

4. Prepare systems, processes and controls for audit testing

   • Design systems and control frameworks so that most reporting information is the product of processes amenable to external auditor review and testing as required by Prudential Standard APS 310 (paragraph 12). Note the consolidated group return under paragraph 6 is excluded from the audit testing requirement set out in paragraph 12.
   • Coordinate with your external auditor early to establish the scope, frequency and timing of their review and testing; the auditor may require more frequent testing to form an opinion (paragraph 12).

5. Implement internal review and authorisation

   • Establish internal review and authorisation processes to assure completeness and reliability of reported information (paragraph 13). Maintain an audit trail of approvals and reconciliations linking source ledgers to ARF 330.1 fields.

6. Map data and validate against ARF 330.1 form and instructions

   • Obtain the versions of Reporting Form ARF 330.1 designated for Licensed ADI and Consolidated Group and the attached instructions (Objective and Information required). Map source data to each ARF field and document any adjustments, assumptions or eliminations (e.g. securitisation deconsolidation adjustments).

7. Ensure electronic submission capability and digital certificate

   • Register for APRA’s Direct to APRA (D2A) application or confirm APRA‑notified alternative submission methods (paragraph 7).
   • Obtain and manage a digital certificate acceptable to APRA for the digitally signed submission by an authorised officer (paragraph 14). Test D2A submissions end‑to‑end well ahead of the first due date.

8. Currency conversion and measurement

   • Convert foreign currency amounts to AUD in line with AASB 121 and the detailed instructions on monetary/non‑monetary item translation, measurement date choices, and treatment of derivatives (Instruction Guide, Unit of measurement). Document exchange rates and the basis for choice of spot or transaction dates.

9. Reconcile cross‑reporting requirements

   • Reconcile ARF 330.1 figures with other APRA returns where overlaps exist (e.g. retained securitisation exposures to ARF 120.1; RWA items to ARF 110.0.1/110.0.2). Ensure that deconsolidation choices are consistently applied across returns and justified by APS 120 operational requirements where relevant.

10. Monitor APRA notices and instrument changes

    • Track APRA written notices that change reporting frequency, deadlines or submission methods for your ADI (paragraph 9). Track APRA notices of minor variations to forms/instructions (paragraphs 15-16).
    • Monitor changes to referenced Prudential Standards (APS 310, APS 120) and Australian Accounting standards (AASB 127, 3, 121, 139) because paragraph 18 imports “as in force from time to time” updates.

11. Establish an exception and escalation framework

    • Build procedures to identify late submission risk, data anomalies, and auditor findings. Use paragraph 11 (APRA may grant extensions in writing) as the channel to apply for relief where necessary.
    • Maintain contemporaneous correspondence records with APRA regarding frequency changes, extensions, and minor variations (paragraphs 9, 11, 15-16).

12. Documentation and record retention

    • Maintain documentation evidencing the design of systems/controls, the external auditor’s review and testing work papers, internal authorisations, reconciliation schedules and any APRA communications. This will assist in demonstrating compliance and responding to any supervisory queries.

13. Test end‑to‑end run

    • Conduct a full dress rehearsal of the quarterly reporting process well before the filing deadline: data extraction, accounting adjustments (consolidation/securitisation), auditor review workflow, internal approvals and D2A submission including digital signature validation.

14. Resource and cost planning

    • Budget for external auditor testing per APS 310, system development for data extraction and mapping to ARF fields, D2A integration and digital certificate procurement, and staff time for internal review and reconciliation, noting the shorter timelines for building societies and credit unions.

Following these concrete steps, tied to the specific paragraphs and instruction guidance in the Reporting Standard, should deliver a defensible compliance posture for ARF 330.1 submissions. If uncertain on legal interpretation, refer to the enabling Financial Sector (Collection of Data) Act 2001 and consult APRA for written clarification or the external auditor for assurance scope decisions.