The Standard’s core concepts are the reportable categories of points of presence, the forms that capture them, the scope and timing of reporting, and the procedural safeguards APRA requires for submission.

Reportable categories:

• Face‑to‑face point of presence: any location that provides face‑to‑face services and maintains a fixed address. These are sub‑categorised as branches or other face‑to‑face points of presence depending on whether minimum branch services are provided (instructions, Face‑to‑face point of presence; Branch; Other face‑to‑face point of presence).
• Branch: a face‑to‑face point that meets all minimum services listed by APRA: accepting cash and deposits and providing change; facilitating account maintenance including balances; opening and closing accounts; facilitating or arranging credit risk assessment; and offering additional services in the one establishment such as financial services, business banking and specialist lending if generally available from the ADI (instructions, Branch, items (a)-(e)).
• ATM point of presence: terminals that allow authorised cardholders to withdraw cash from cheque/savings or credit accounts, including ATMs and cash dispensers, with authorisation via PIN and unassisted access. APRA requires the ADI that owns the ATM and exchanges ATM transaction messages to report the terminal; ADIs must not report third‑party owned ATMs even if the ADI’s customers can access them (instructions, ATM point of presence).
• EFTPOS point of presence: terminals located at retail outlets enabling purchase using deposit or credit funds, possibly cash out, authorised via PIN or contactless, and operated with retailer assistance (instructions, EFTPOS point of presence). The owner reports, or where a non‑ADI owner delegates key management or switching responsibility to an ADI, the ADI responsible for key management reports (instructions).

Forms and measurement:

• ARF 796.1 captures latitude and longitude (to four decimal places) for each face‑to‑face point and a Y/N indicator of whether it is a branch (form instructions).
• ARF 796.2 captures latitude, longitude and number of ATMs at those coordinates (to four decimal places for coordinates; ATM counts as whole numbers) (form instructions).
• ARF 796.3 captures state or territory and number of EFTPOS terminals in each jurisdiction (form instructions).

Scope and timing:

• Only points of presence located within Australia, including offshore territories, are reportable (Interpretation, paragraph 16; Reporting basis in Instructions).
• Reporting level is Level 1 for all ADIs except PPF providers (Instructions, Reporting level).
• The reference date for the data is the last day of the reporting period, i.e. 30 June each year (Instructions, Reporting basis).

Procedural concepts:

• Mandatory use of D2A for electronic submission unless APRA advises another method (paragraph 6).
• Digital signing, authorisation and encryption by an officer using APRA‑issued digital certificates (paragraph 12).
• Internal quality assurance processes and controls (paragraph 11).
• APRA’s ability to alter reporting frequency, grant extensions, and make minor non‑substantive variations to forms and instructions with written notice (paragraphs 8-10, 13-14).
• Transitional arrangements requiring ADIs to report under the revoked standard for certain transitional reporting periods (paragraph 15).

Finally, the declared purpose is publication of the collected information (paragraph 2), which directly links reporting to APRA’s public disclosure activities.

Primary duty‑holders:

• All authorised deposit‑taking institutions (ADIs) defined as bodies corporate authorised under section 9 of the Banking Act 1959 to carry on banking business in Australia, except purchased payment facility (PPF) providers (paragraph 3; Interpretation, paragraph 16). The Standard expressly excludes PPF providers from its application.

Secondary and internal actors within ADIs:

• Officers authorised by their ADI who will digitally sign, authorise and encrypt reports using APRA‑issued digital certificates (paragraph 12). The ADI must nominate officers with the authority to transmit data and will receive digital certificates from APRA’s certificate authority.

Reporting recipients and decision‑makers:

• APRA is the recipient and the decision‑maker for procedural matters under the Standard. APRA issues D2A software, notifies alternate submission methods when necessary (paragraph 6), issues digital certificates (paragraph 12), may change reporting periods or frequencies by written notice (paragraph 8), can grant due date extensions in writing (paragraph 10), and may make minor non‑substantive variations to forms or instructions, subject to written notification to ADIs (paragraphs 13-14). APRA is also the party that will publish the reported information (paragraph 2).

Third parties affected indirectly:

• Retailers and non‑ADI terminal owners: the Standard requires that EFTPOS terminals be reported by their owner or by the ADI responsible for key management and message switching (instructions, EFTPOS point of presence). This creates an indirect reporting interaction where non‑ADI owners who delegate key management to ADIs may influence which entity reports a terminal.
• Australia Post: Bank@Post outlets will not be reported by ADIs because APRA will obtain Bank@Post data directly from Australia Post (instructions, Bank@Post).

Who pays:

• The compliance costs fall on the reporting ADIs. Costs include assembling geospatial data, ensuring internal quality control processes are in place, producing the forms in the specified format, obtaining and managing APRA‑issued digital certificates, and submitting the data within the prescribed times. The Standard itself does not assign external fees or charges within the text; it mandates actions and formats that ADIs must follow (paragraphs 5-12).

Who decides:

• APRA retains discretion over submission method availability, reporting frequency and procedural variations (paragraphs 6, 8, 10, 13-14). ADIs decide how to implement internal review and authorisation systems to satisfy the quality control requirement (paragraph 11) and which officer(s) will be authorised to sign and submit the data (paragraph 12).

Behavioural effects:

• ADIs must identify and classify each point of presence according to APRA’s definitions, decide whether a location is a branch under APRA’s criteria, determine terminal ownership and key‑management responsibility for reporting, and maintain coordinate precision to four decimal places. These are recorded as at 30 June each year and submitted within 28 days unless APRA instructs otherwise (Instructions; paragraphs 7-10).

Reporting duties:

• ADIs (excluding PPF providers) must provide APRA with the information required by ARF 796.1, ARF 796.2 and ARF 796.3 for points of presence located in Australia for each reporting period (paragraph 5). The forms capture specific items: latitude and longitude (four decimal places) and branch indicator for face‑to‑face locations (ARF 796.1); latitude, longitude and number of ATMs at those coordinates (ARF 796.2); and state/territory counts of EFTPOS terminals (ARF 796.3 and Instructions).

Temporal and submission duties:

• Submit on an annual basis for years ending 30 June, reporting as at the last day of the reporting period (Instructions; paragraph 7). Submit within 28 calendar days after the period end (paragraph 9). If D2A is unavailable, use a method notified in writing by APRA prior to submission (paragraph 6). If a due date falls on a non‑business day, the ADI must nonetheless submit by that date (paragraph 10 Note).

Data integrity and authentication duties:

• Maintain internal processes and controls for internal review and authorisation of reported information to assure completeness and reliability (paragraph 11). Digitally sign, authorise and encrypt submissions using APRA‑issued digital certificates held by authorised officers (paragraph 12).

Classification duties:

• Apply APRA’s definitions for face‑to‑face points, branches and other face‑to‑face points; ensure branches meet all minimum service conditions set out in the instructions (Branch definition). For ATMs, report only those owned by the ADI and where the ADI exchanges transaction messages; do not report third‑party owned ATMs even if the ADI’s customers can access them (ATM point of presence instructions). For EFTPOS, report terminals owned by the ADI or, where a non‑ADI owns the terminal but an ADI manages key management or switching, the ADI responsible must report (EFTPOS point of presence instructions). Do not report Bank@Post outlets; APRA will obtain these from Australia Post (instructions, Bank@Post).

APRA’s rights and discretions:

• APRA may change reporting periods for a particular ADI by written notice, to require more or less frequent reporting as it considers necessary given the ADI’s circumstances (paragraph 8). APRA may grant extensions to due dates in writing (paragraph 10). APRA may make minor variations to forms or instructions to correct technical or programming errors or to clarify application, provided such changes do not alter substantive requirements; APRA must notify each ADI in writing if it makes such variations (paragraphs 13-14). APRA will use the collected information for publication (paragraph 2).

Transitional duty:

• Where a transitional reporting period exists under the old reporting standard revoked by the new determination, the ADI must report under the old reporting standard for that transitional period (paragraph 15).

Rights implicit and not stated:

• The Standard does not expressly provide rights of review, appeal or access to APRA’s published use of the data within its text. The Standard is silent on penalties or enforcement provisions within its own wording; those matters fall to the enabling legislation and APRA’s administrative processes (paragraph 1; see further under Penalties and enforcement and How it interacts with other laws).

The Reporting Standard itself does not specify sanctions, fines or criminal liability. It is a data‑collection instrument made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1). The Standard prescribes what must be reported, by whom and how, and APRA’s procedural discretions, but it does not set out enforcement mechanisms or penalty amounts within its text.

Practical enforcement pathways and implications that follow from the structure of the Standard:

• APRA’s authority to collect data is derived from the enabling Act, as stated at the outset of the Standard (paragraph 1). Where compliance and enforcement measures apply they will be those available under the Financial Sector (Collection of Data) Act 2001 and any other enabling provisions referenced or used by APRA; the Standard itself does not enumerate them. Practitioners must therefore consult the Financial Sector (Collection of Data) Act 2001 and relevant APRA enforcement policies for details of mandatory powers, potential administrative penalties, criminal offences, or other compliance mechanisms that could be applied when a covered ADI fails to comply.

APRA’s administrative powers indicated by the Standard:

• APRA can change reporting frequencies (paragraph 8), grant due‑date extensions in writing (paragraph 10) and make minor variations to forms and instructions while notifying ADIs in writing (paragraphs 13-14). These operational discretions create administrative mechanisms for tolerance, correction and procedural management of reporting but fall short of stating enforcement outcomes.

Limits in the instrument:

• Because the Standard focuses on definitions, form content and submission procedures it leaves unspecified the remedial or disciplinary steps APRA may take in the event of late, incomplete or inaccurate returns. The Standard’s requirements for internal quality control (paragraph 11) and authorised digital submission (paragraph 12) indicate expectations of accuracy and traceability, which could be relevant if APRA invokes enforcement powers under the enabling Act.

Implication for risk management:

• ADIs should assume that failure to comply may expose them to compliance action under the Financial Sector (Collection of Data) Act 2001 or other applicable law and should plan operational controls accordingly. The Standard obliges ADIs to implement quality assurance and authorised submission processes (paragraphs 11-12); those processes will be material evidence of an ADI’s compliance posture if APRA raises concerns.

For concrete advice on penalties, enforcement procedures and appeals, practitioners must refer to the Financial Sector (Collection of Data) Act 2001 and APRA’s published guidance on enforcement, as such material sets out the statutory and administrative remedies and consequences that this Reporting Standard does not itself include.

Direct statutory linkages:

• The Reporting Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1). Its definitions cross‑reference other statutes: the term ADI is defined by reference to section 9 of the Banking Act 1959 (Interpretation, paragraph 16), and APRA is identified as the authority established under the Australian Prudential Regulation Authority Act 1998 (Interpretation, paragraph 16). The standard therefore operates as an instrument within the broader statutory framework constituted by the Financial Sector (Collection of Data) Act, the Banking Act and the APRA Act.

Administrative and publication interaction:

• Paragraph 2 states that information collected is used by APRA for publication. That use raises interfaces with any legal obligations governing publication and disclosure by APRA, and potentially with privacy and confidentiality regimes applicable to data held by APRA. The Reporting Standard itself does not address privacy, confidentiality carve‑outs or exemptions from publication; practitioners should therefore consider how APRA’s publication of the data interacts with the Privacy Act 1988 and any statutory confidentiality protections that may attach to prudential returns under the enabling Act. The Standard does not supply those details.

Operational interactions with other regulatory arrangements:

• The definitions draw upon operational banking concepts in the Banking Act (e.g. the ADI concept at s 9), which makes the Standard part of the compliance ecosystem for regulated banking entities. Terminology such as branches, face‑to‑face services, ATM and EFTPOS are defined specifically for data‑collection purposes in the Standard’s instructions and may differ from other definitions used in licensing, consumer disclosure or tax reporting contexts. Where another statute or regulator relies on different thresholds or definitions for a “branch” or “ATM”, ADIs must be attentive to which definition governs each statutory obligation.

Data sharing and sourcing:

• The Standard instructs ADIs not to report Bank@Post outlets because APRA will obtain that information directly from Australia Post (instructions, Bank@Post). This is an explicit interaction where APRA relies on another statutory or contractual data source rather than duplicate reporting by ADIs.

Transitional arrangements and repeals:

• Paragraph 15 requires ADIs to report under the old reporting standard for specified transitional reporting periods, indicating that the Standard is part of a sequence of statutory instruments and that revocation of the old instrument triggers transitional duties. Practitioners must therefore track determinations revoking or making reporting standards to understand which instrument applies for any given period.

Limits and gaps:

• The Standard does not specify enforcement mechanics, interactions with privacy law, or cross‑border data transfer rules; such interactions will be governed by the enabling legislation, APRA operational policy, and other relevant statutes. Likewise, the Standard’s requirement that APRA publish the data suggests an interaction with administrative law principles around information accuracy and process, but the Standard contains no procedural rights of review or appeal in relation to APRA’s use or publication of reported data.

Practical consequence:

• ADIs should treat this Reporting Standard as a component of their overall regulatory compliance architecture, referencing the Financial Sector (Collection of Data) Act 2001 for enforcement and procedural detail, the Banking Act 1959 for ADI status, and APRA’s broader regulatory guidance for data handling, cyber security, confidentiality and publication obligations.

Dates and transitional change:

• The Standard states that it applies for reporting periods ending on or after 30 June 2017 (paragraph 4). It also contains a transitional provision requiring ADIs to report under the old reporting standard for specific transitional reporting periods defined in paragraph 15. Those transitional provisions indicate that the current Standard replaced an earlier reporting standard by a revocation determination; the Standard directs ADIs on how to treat returns where the reporting period ended before revocation but the reporting due date post‑dated revocation (paragraph 15).

Authority for minor amendments:

• APRA is expressly empowered within the Standard to make minor variations to the forms and the instructions to correct technical, programming or logical errors or to clarify their application, provided that such variations do not change any substantive requirement in the form or instructions (paragraph 13). APRA must notify in writing each ADI required to report under the Standard when it makes such a variation (paragraph 14). This is the only internal amendment mechanism articulated within the Standard itself.

Content that has changed or is subject to change:

• The Standard includes updated reporting forms ARF 796.1‑3 and accompanying instructions. The inclusion of precise reporting format requirements such as latitude/longitude to four decimal places, whole number reporting for counts, and the explicit exclusion of Bank@Post from ADI reporting (because APRA will obtain that data directly from Australia Post) are elements that reflect design choices that likely differ from any preceding instrument. The Standard’s published effective date (reporting periods ending on or after 30 June 2017) is the anchor for those changes (paragraph 4).

What is not in the text:

• The Standard does not include a schedule of prior amendments or an amendment ledger within its text. It does not list the date of revocation of the old reporting standard or the instrument that effected that revocation. For practitioners tracking legislative history, reliance will be required on APRA determinations, the Commonwealth Gazette notices, or APRA’s repository of reporting standards to obtain a formal amendment history and the precise revocation instrument.

Recommended practitioner actions for tracking amendments:

• Monitor APRA notifications for any written notices under paragraphs 8, 10, 13 and 14 since those are the mechanisms the Standard uses to effect procedural changes or grant extensions. Maintain records of communications from APRA on variations to the forms or instructions because the Standard requires APRA to notify ADIs in writing when it makes minor variations (paragraph 14). For substantive changes, consult APRA’s public instrument register or the Federal Register of Legislation for determinations revoking or making reporting standards to identify the dates and textual changes.

In summary, the Standard went into effect for reporting periods ending 30 June 2017 and allows APRA to make limited, non‑substantive adjustments by written notification; a full amendment history is not contained in the Standard itself and must be assembled from APRA publications and statutory registers.

The Reporting Standard text contains no litigation history, case references or judicial decisions. It is a regulatory instrument focused on data collection, definitions and procedural requirements and does not purport to summarise litigation or disputes concerning it (the document includes no case citations).

What that absence means for practitioners:

• Because the Standard does not reference case law, there is no reported judicial construction or challenge recorded within this instrument. If disputes arise about interpretation, classification of points of presence, or the scope of APRA’s discretions under this Standard, such litigation or administrative review would engage the enabling legislation (the Financial Sector (Collection of Data) Act 2001), APRA’s determinations and administrative law principles. Those potential proceedings and precedents would be found outside the Standard in decisions of courts or tribunals and in APRA correspondence and decisions.

Potential areas likely to generate contestation, given the text:

• Classification questions: whether a given face‑to‑face location satisfies the branch criteria in the instructions (for example, whether certain services are “provided” in sufficient form to meet the five branch minimums) could be a point of interpretive dispute.
• Ownership and reporting responsibility: disagreements about whether an ADI “owns” an ATM or is the party that exchanges ATM transaction messages, or whether an ADI is responsible for key management of an EFTPOS terminal owned by a third party, could trigger regulatory queries and, potentially, review if APRA challenges a report’s completeness.
• Publication issues: because APRA will use the information for publication (paragraph 2), disputes might arise about accuracy or the consequences of publication, potentially giving rise to administrative law challenges or requests for correction.

How to find relevant decisions:

• Any litigation or tribunal decisions addressing ARS 796.0, or disputes over APRA’s use of the information, would be reported in court databases and APRA’s public communications. Practitioners searching for precedent should query judicial and tribunal records for decisions involving APRA and reporting standards under the Financial Sector (Collection of Data) Act 2001, alongside APRA’s published responses and determinations.

Practical takeaway:

• The Standard itself provides no litigation record. Where legal or factual disputes occur, practitioners must locate and analyse external judicial or administrative decisions interpreting the enabling legislation and APRA’s exercise of its powers.

Precise items in the Standard that commonly cause compliance friction:

1. Scope exclusions and Bank@Post:

   • ADIs must not report Bank@Post outlets because APRA will obtain this information directly from Australia Post (instructions, Bank@Post). Firms that duplicate Bank@Post reporting risk inconsistent submissions and should remove such outlets from their returns.

2. Definition of branch is conjunctive:

   • A location qualifies as a branch only if it provides all listed minimum services (accepts cash and deposits and provides change; facilitates account access and balances; opens and closes accounts; facilitates or arranges credit risk assessment; and offers additional services in the one establishment where generally available) (instructions, Branch). Failure to satisfy any one of these requirements means the location must be reported as “other face‑to‑face”. Misclassifying a mini‑branch or agency as a branch due to partial service offerings will produce incorrect published data.

3. ATM ownership and message exchange:

   • Only report ATMs the ADI owns and exchanges transaction messages for; do not report third‑party owned ATMs even if ADI cards access them via third‑party switches (instructions, ATM point of presence). ADIs that operate via switch providers must determine whether message exchange is performed by the ADI or by a third party; ambivalence here can lead to over‑reporting or under‑reporting.

4. EFTPOS key management responsibility:

   • For non‑ADI owned EFTPOS terminals, the party responsible for key management (securing transaction messages at capture) reports the terminal. If an ADI “drives” transactions or handles switching, the ADI reports (instructions, EFTPOS point of presence). ADIs must document key management arrangements with merchants and third parties to determine reporting responsibility.

5. Coordinate precision and format:

   • Latitude and longitude must be reported to four decimal places (Instructions, Reporting basis). Small differences in coordinate rounding can shift reported locations across local government boundaries and affect public presentation. ATMs and face‑to‑face points require coordinates to four decimals; EFTPOS is reported by state/territory only.

6. Timing is strict and calendar‑based:

   • Data are as at 30 June and due within 28 calendar days. The Standard expressly requires submission by the due date even if it falls on a non‑business day (paragraph 10 Note). ADIs must align internal cutoffs and reconciliation cycles with this calendar requirement.

7. Digital certificate management:

   • APRA will issue digital certificates to authorised officers who have authority from the ADI to transmit information (paragraph 12). ADIs must maintain certificate lifecycle controls, including delegation of authority, revocation processes when officers leave, and secure storage. Failure to maintain these controls may disrupt submission ability.

8. Quality control expectation:

   • The Standard requires internal systems, processes and controls to assure completeness and reliability (paragraph 11). APRA does not prescribe a particular assurance standard, but the absence of documented, repeatable QA processes will leave ADIs exposed to queries about data integrity.

9. Transitional reporting complexity:

   • Where reporting periods straddle the revocation of the old standard, ADIs must report under the old standard for specified transitional periods (paragraph 15). Firms must keep records of which standard applied to each reporting period to avoid late corrections.

10. APRA’s minor variation power:

    • APRA may make minor, non‑substantive variations to forms and instructions to correct technical or programming errors (paragraph 13). ADIs may receive altered templates in the lead‑up to submission that look different but do not change substantive obligations. Careful version control is necessary to avoid submission in an old, now‑superseded template.

11. Reporting level and unit definitions:

    • Reporting is Level 1 (Instructions, Reporting level) and counts are to be reported as whole numbers for terminals. Misunderstanding reporting level (consolidated, group or entity) or unit types can cause materially incorrect returns.

12. Publication consequence:

    • APRA will publish the collected information (paragraph 2). Practitioners should anticipate reputational effects of published footprints, which places a premium on accuracy and timely reviews before submission.

Operationally, these “gotchas” require ADIs to maintain accurate inventories, contract records regarding ownership and key management, coordinate rounding protocols, robust internal controls, certificate administration, and version control for APRA templates.

A practical, stepwise compliance checklist based on the Standard:

1. Confirm applicability:

   • Determine whether your entity is an ADI under section 9 of the Banking Act 1959 and not a purchased payment facility (PPF) provider (paragraph 3; Interpretation, paragraph 16). PPF providers are excluded.

2. Establish reporting level and reference date:

   • Report on a Level 1 basis as at the last day of the reporting period, 30 June (Instructions, Reporting level and Reporting basis). Prepare to submit within 28 calendar days after 30 June unless APRA grants an extension in writing (paragraphs 7 and 9-10).

3. Inventory and classification:

   • Compile a master inventory of all Australian points of presence, segregating:
     • Face‑to‑face locations and classifying each as branch or other face‑to‑face according to APRA’s five minimum branch criteria (instructions, Branch).
     • ATMs: identify ownership and whether the ADI exchanges ATM transaction messages for each terminal. Exclude third‑party owned ATMs where the ADI does not exchange messages (instructions, ATM point of presence).
     • EFTPOS terminals: identify those owned by the ADI and those where a third party owns the terminal but the ADI is responsible for key management or switching (instructions, EFTPOS point of presence).
   • Ensure Bank@Post outlets are excluded from ADI submissions because APRA obtains these directly from Australia Post (instructions, Bank@Post).

4. Geospatial and numeric preparation:

   • For face‑to‑face and ATM points, capture latitude and longitude to four decimal places for each location (Instructions). For ARF 796.2, record the number of ATMs at each coordinate as a whole number. For ARF 796.3, tabulate the number of EFTPOS terminals by state or territory.

5. Internal controls and QA:

   • Implement or document processes and controls to review and authorise the data prior to submission, ensuring completeness and reliability as required by paragraph 11. This should include reconciliation steps, version control of templates, and sign‑off checklists.

6. Digital authorisation and certificate management:

   • Identify officer(s) authorised to sign and transmit reports and engage with APRA to obtain digital certificates as required for D2A submissions (paragraph 12). Establish internal policies for certificate issuance, revocation and transfer when personnel change roles.

7. Submission mechanics:

   • Obtain and install the D2A software (or follow APRA’s written instruction if D2A is not available) and format reports according to ARF 796.1‑3 as instructed (paragraph 6 and form instructions). Submit within 28 days of 30 June or secure a written extension from APRA if necessary (paragraph 10).

8. Recordkeeping and audit trail:

   • Retain copies of submitted forms, digital authorisations, certificates used, QA sign‑offs and any communications with APRA regarding reporting frequency changes, extensions, or template variations (paragraphs 8, 10, 13-14). These records will support compliance inquiries or audits.

9. Monitor APRA notifications:

   • Watch for written notices from APRA altering reporting frequency for your ADI (paragraph 8), granting extensions (paragraph 10), or notifying minor non‑substantive variations to forms and instructions (paragraphs 13-14). Update internal procedures and templates promptly on receipt of APRA notifications.

10. Reconciliation with publication:

• Because APRA intends to publish the information (paragraph 2), coordinate internal review timelines with business units that may be sensitive to public presentation of branch and terminal footprints. Ensure the data you submit is defensible and backed by documentation.

11. Transitional reporting and historical comparability:

• Where reporting periods overlap a revocation of a prior standard, follow paragraph 15 and report under the old standard for transitional periods. Maintain mapping between old and new standard variables for historical comparability.

12. Legal and governance oversight:

• Engage legal and compliance teams to ensure that reporting and publication by APRA do not conflict with other statutory obligations. While the Standard does not address privacy or enforcement, coordinate with privacy officers and legal advisers as necessary to manage data sharing or potential public disclosure implications.

13. Contracts and third‑party arrangements:

• Ensure written agreements with ATM providers, merchants and terminal owners clearly define ownership, switching responsibilities and key management duties so that reporting responsibility is unambiguous. Where responsibility is shared or changes over time, document effective dates and update the inventory prior to the 30 June reference date.

14. Test submissions and contingency:

• If possible, perform dress rehearsals of data extraction, D2A formatting and digital signing before the reporting window. Prepare contingency plans for D2A unavailability, including APRA’s alternative written methods and procedures for expedited communications to obtain extensions if needed.

By following this structured checklist and mapping each reporting obligation to internal processes, ADIs can align operational delivery to the Standard’s requirements: accurate location data, appropriate classification, authenticated electronic submission, internal QA and retention of audit evidence.