At its core the Reporting Standard organises information on two economically similar sets of transactions: repurchase/resale agreements (repos) and securities lending/borrowing. The Specific instructions explain the economic logic and the reporting distinctions the form requires.

Repos and securities lending are characterised in the document as transfers of legal ownership (debt or equity) where the original holder retains market risk, entitlement to holding gains or losses, and income generated by the security (Specific instructions). In both transactions there is a commitment to repurchase the same or similar security at a specified future date or on demand, typically at a fixed price. The Standard highlights a practical distinction: securities lending commonly involves payment of a fee to the lender as an incentive and may not necessarily involve cash exchange or collateral; repo transactions generally involve cash and collateral and generate interest income for the cash provider (Specific instructions). Reverse repos are explicitly included for reporting (Specific instructions).

Reporting mechanics mandated by the Standard include:

• Report all securities held under resale agreements and due for repurchase at the end of the reference period by counterparty (Specific instructions).
• Report all securities borrowed and lent at the end of the reference period by counterparty (Specific instructions).
• Report all such securities at market value (Specific instructions).
• Do not net separate repurchase/resale agreements when they involve different security types, even if the counterparty is the same (Specific instructions).
• Include reverse repos (Specific instructions).

The Standard also directs reporters to use sector definitions in Reporting Form ARF 320.0 (Statement of Financial Position (Domestic Books)) “as a general guide” for sector reporting, and flags the particular classification risk for debt securities that appear to be issued by State, Territory or local government but may in fact be issued by central borrowing authorities (Specific instructions). This guides how securities should be allocated among sectors on the form.

Definitions and cross‑references are a central conceptual device. The Standard’s Interpretation section (paragraph 15) imports meanings from other instruments and statutes: AASB (as in Corporations Act s 9), ADI (Banking Act 1959), foreign ADI (section 5 of the Banking Act), the meaning of “financial year” (Corporations Act reference in paragraph 7), and a technical definition of “stake” tied to the Financial Sector (Shareholdings) Act 1998 (paragraph 15). The Standard also contains a saving clause that references instruments “as in force from time to time” (paragraph 16), meaning that the reporting regime is dynamic with respect to changes in the external statutes and standards it cites.

Administratively, the Standard’s key concepts are data completeness and reliability (quality control, paragraph 11), electronic submission with APRA‑acceptable digital signing (paragraph 12), and APRA’s capacity to adjust reporting frequency for particular ADIs based on prudential necessity, ADI circumstances or third‑party requirements (the RBA or ABS) (paragraph 8). APRA may also make minor, non‑substantive variations to forms and instructions for technical or logical corrections, with notification to reporting ADIs (paragraphs 13-14). These mechanisms define the operational boundaries of the dataset and the institutional responsibilities for producing it.

The Reporting Standard applies to a defined set of ADI classes; the applicability table in paragraph 3 is the operative starting point. The table expressly requires reporting from:

• Australian‑owned banks (Yes),
• Foreign subsidiary banks (Yes),
• Branches of foreign banks (Yes),
• Other ADIs (Yes).

The table expressly excludes building societies and credit unions (both marked No for applicability). The label “other ADI” is also defined in paragraph 15 and includes any ADI that is not an Australian‑owned bank, a branch of a foreign bank, a building society, a credit union or a foreign subsidiary bank, though it explicitly excludes Cairns Penny Savings & Loans Limited from that category (paragraph 15). The definitions in paragraph 15 also specify the legal meaning of “Australian‑owned bank”, “branch of a foreign bank” (a ‘foreign ADI’ per section 5 of the Banking Act 1959) and “foreign subsidiary bank” (a locally incorporated ADI in which a non‑locally incorporated bank has a stake of more than 15 per cent). Consequently, an ADI must identify whether it falls within the applicable classes by reference to the Banking Act and the Financial Sector (Shareholdings) Act 1998 as incorporated in the Standard’s definitions (paragraph 15).

Who pays and who bears the compliance burden: the ADIs required to report (the Yes entries in paragraph 3) are the entities that must collect, validate and submit ARF 320.5 data. Paragraph 5 makes this obligation explicit: “An ADI to which this Reporting Standard applies must provide APRA with the information required by ARF 320.5 for each reporting period.” Practically that means the ADI carries labour costs for data extraction, valuation at market value, reconciliation by counterparty, quality control and authority processes, and transactional documentation to support the reporting.

Who decides: APRA is the decision‑making actor under this Standard. APRA determines acceptable submission methods and can notify alternative methods in writing (paragraph 6), require more or less frequent reporting for any particular ADI by written notice having regard to specified factors (paragraph 8), grant extensions to due dates (paragraph 10), and make minor non‑substantive changes to forms and instructions (paragraph 13). APRA must notify ADIs of such variations (paragraph 14). The Reserve Bank of Australia and the Australian Bureau of Statistics are listed as legitimate secondary users of the collected data (paragraph 2).

Behavioural effects and choices for affected entities: ADIs must implement internal systems and controls to assure completeness and reliability of data (paragraph 11), maintain or obtain a digital certificate acceptable to APRA for signing submissions (paragraph 12), and map their securities‑transactions reporting to the ARF 320.5 fields and the sector guidance of ARF 320.0 as instructed (Specific instructions). They must adopt market value valuation conventions for the securities concerned and report positions by counterparty at reporting date (Specific instructions). APRA’s capacity to alter reporting frequency (paragraph 8) creates a compliance risk for ADIs with limited data capabilities, as they may be required to report more frequently if prudential supervisors deem it necessary.

The Standard does not, within its text, impose criminal or civil penalties, nor does it describe enforcement instruments. It defines obligations, submission expectations, and administrative powers but leaves any sanctions to the enabling legislation and other enforcement frameworks, none of which are specified here.

Duties imposed on applicable ADIs

• Provide the ARF 320.5 dataset for each reporting period (paragraph 5). The ARF 320.5 form and the attached instructions form part of the Reporting Standard, so the duty includes compliance with the field definitions and instructions embedded in those documents (first paragraph).
• Submit the information in electronic format using the Direct to APRA (D2A) application or by another method previously notified by APRA in writing (paragraph 6).
• Meet the default reporting cadence of quarterly reporting aligned to the ADI’s financial year (paragraph 7), unless APRA has given notice under paragraph 8 changing the reporting periods for that ADI.
• Provide data by the due date, which is 20 business days after the end of the reporting period (paragraph 9), unless APRA has granted a written extension (paragraph 10).
• Maintain internal processes and controls for internal review and authorisation to assure completeness and reliability of submitted information (paragraph 11).
• Digitally sign submissions with a digital certificate acceptable to APRA (paragraph 12).
• Apply the Specific instructions when preparing the ARF 320.5 return: report securities under resale agreements and due for repurchase by counterparty, report securities borrowed and lent by counterparty, report all such securities at market value, do not net separate repurchase/resale agreements if they are of different security types, and include reverse repos (Specific instructions).

Rights and administrative flexibilities afforded to ADIs

• APRA must notify in writing any minor variations it makes to forms or instructions that correct technical or programming errors or clarify instructions; ADIs are entitled to receive that notification (paragraph 14).
• APRA may grant extensions of due dates in writing; ADIs can apply for or rely on such extensions where granted (paragraph 10).
• The Standard recognises APRA’s capacity to change reporting periods for particular ADIs based on the ADI’s circumstances, APRA’s prudential supervision needs, or the requirements of the RBA or ABS (paragraph 8). This is framed as a power APRA holds rather than a right of an ADI, but it is a procedural interaction that an ADI may expect to be subject to.

APRA’s duties and powers

• The Standard is made under the statutory authority of the Financial Sector (Collection of Data) Act 2001 (paragraph 1). APRA must implement the Standard as drafted and accept the electronic submissions in the methods prescribed (paragraph 6).
• APRA may change reporting frequency for particular ADIs by written notice when it considers the ADI’s circumstances or prudential needs warrant it (paragraph 8).
• APRA may make minor non‑substantive variations to forms and instructions to correct technical, programming or logical errors, inconsistencies or anomalies, or to clarify application of instructions (paragraph 13). APRA must notify reporting ADIs in writing of such variations (paragraph 14).
• APRA has the administrative discretion to accept alternative submission methods if notified in writing prior to submission (paragraph 6).

Interplay with other obligations

• The Standard instructs reporters to use sector definitions from Reporting Form ARF 320.0 as a guide, and highlights classification issues (Specific instructions). This creates a practical duty for ADIs to reconcile their sector‑classification approaches across reporting instruments.

Procedural controls and auditability

• The requirement for internal review and authorisation processes (paragraph 11) and digital signature with accepted certificate (paragraph 12) establishes an auditable trail for submissions and formalises the officer‑level attestation on data completeness and reliability. Those are duties that require documented procedures and evidence retention by the ADI.

Limitations within the instrument

• The Reporting Standard provides the framework of duties and APRA’s administrative powers but does not specify penalties or enforcement mechanisms within its text. Where legal consequences attach to non‑compliance, they will derive from the enabling statute or other legal instruments, not from this Standard itself.

The Reporting Standard itself does not set out specific penalties, fines or criminal sanctions for non‑compliance. Its text defines obligations, timetables and procedural requirements (for example the obligation to provide ARF 320.5 data for each reporting period, paragraph 5; submission timing, paragraph 9; quality control and authorisation, paragraphs 11-12), and it confers administrative discretions on APRA (to change reporting frequency, paragraph 8; to grant extensions, paragraph 10; and to make minor variations to forms, paragraph 13). The instrument does not provide any explicit enforcement mechanism, nor does it list remedial processes, sanction regimes or civil penalties within its own provisions.

Because the Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1), any statutory enforcement powers and sanctions applicable to non‑compliance with APRA data collection instruments would exist, if at all, in that enabling Act or in related legislation. The Standard itself does not reproduce or describe such powers. Users are therefore left, from the text provided, with two concrete enforcement‑related operational consequences:

• APRA may administratively change reporting parameters for a particular ADI and require more frequent reporting where it deems that necessary for prudential supervision (paragraph 8). This is a supervisory lever rather than a punitive instrument.
• APRA may require digital authorisation of submissions and impose technical submission requirements (paragraphs 6 and 12), which, if not met, would prevent accepted submission under the Standard’s process; the Standard does not state the legal consequence of failure to submit in the prescribed way.

The only enforcement‑adjacent procedural obligation on APRA is a notification duty where APRA makes minor variations to forms or instructions; APRA “must notify in writing each ADI that is required to report under this Reporting Standard” (paragraph 14). There is no parallel statement of ADI remedies for overreach or dispute resolution mechanisms in relation to APRA’s exercise of its variation powers or notices under paragraphs 8-10.

Because the instrument is silent on penalties, practitioners and compliance officers should assume that any sanctioning authority, compliance enforcement timeline or appeal pathway will be located in the Financial Sector (Collection of Data) Act 2001 or other statutes and therefore must be checked in those instruments. The Standard sets out the reporting obligations to be enforced, the mechanics of submission, and APRA’s administrative powers, but it does not itself prescribe the legal consequences of failing to comply.

The Reporting Standard is explicit in its cross‑references and in the way it imports statutory definitions and external instruments to determine scope, reporting cadence and interpretation. These interactions determine classification, timing, and the legal identity of reporting entities.

Key references and interactions specified in the text:

• Financial Sector (Collection of Data) Act 2001: The Standard is made under section 13 of that Act (paragraph 1). That establishes the legal basis for APRA requiring the specified data, although the Standard does not reproduce enforcement provisions from that Act.
• Banking Act 1959: The term ADI is defined “within the meaning of the Banking Act 1959” (paragraph 15). The term “branch of a foreign bank” is tied to the definition of “foreign ADI” in section 5 of the Banking Act 1959 (paragraph 15). Therefore the legal characterisation of reporting entities depends on the Banking Act’s definitions.
• Corporations Act 2001: The Standard ties the reporting quarter cadence to the ADI’s financial year “within the meaning of the Corporations Act 2001” (paragraph 7). The Interpretation section also imports the meaning of AASB from section 9 of the Corporations Act (paragraph 15). This affects fiscal period alignment and accounting standard references used for interpretation.
• Financial Sector (Shareholdings) Act 1998: The definition of “stake” in paragraph 15 explicitly alludes to a technical method of calculation under that Act, with a clarifying modification about which associates are taken into account. That determines whether a locally incorporated ADI is a foreign subsidiary bank for applicability purposes (paragraph 15).
• AASB and Australian Accounting or Auditing Standards: The Standard says that “a reference to an Act, Prudential Standard, Reporting Standard, Australian Accounting or Auditing Standard is a reference to the instrument as in force from time to time” (paragraph 16). That clause imports current and future amendments to accounting and auditing standards into the interpretive framework for the Reporting Standard.
• Reporting Form ARF 320.0 and ARF 320.5: The Standard directs reporters to use sector definitions in ARF 320.0 as a general guide for reporting by sector, and it makes ARF 320.5 and its instructions integral parts of the Standard (first paragraph and Specific instructions). Therefore, form‑level definitions and instructions operate as part of the Standard’s requirements.
• Reserve Bank of Australia and Australian Bureau of Statistics: The Standard explicitly allows APRA to share or permit use of the collected data by the RBA and the ABS for their purposes (paragraph 2). This is an institutional data‑sharing interaction that may affect how ADIs consider confidentiality and data governance.

Functional consequences of these interactions:

• Classification and scope are conditional on statutory definitions in other Acts. For example, whether an entity is an ADI and which class of ADI it is for the table at paragraph 3 depends on definitions in the Banking Act and on shareholding calculations under the Financial Sector (Shareholdings) Act 1998 (paragraph 15).
• Timing is anchored to the Corporations Act definition of financial year (paragraph 7), so ADIs with non‑standard fiscal years must map reporting periods accordingly.
• Valuation and accounting treatment for reported positions are implicitly tied to prevailing accounting standards referenced in paragraph 16; changes to those standards will flow into reporting obligations.
• The Standard’s instruction to consult ARF 320.0 for sector definitions creates an operational dependency: classification decisions made for balance sheet reporting must be consistent across ARF instruments.
• The ability of APRA to change reporting frequency or impose alternative submission methods (paragraphs 6 and 8) gives it the operational flexibility to coordinate with RBA and ABS needs, which may mean ADIs must adapt systems to differing data demands arising from monetary or statistical policy requirements.

What the Standard does not do within its text:

• It does not itself amend or restate the enforcement or sanctioning regimes of the enabling or cross‑referenced statutes. Those provisions, if relevant to enforcement, are outside the text of the Standard.
• It does not specify privacy, secrecy or confidentiality constraints governing APRA’s use or sharing of data beyond the statement that the RBA and ABS may use the data (paragraph 2).

Practitioners need to read the Reporting Standard alongside the enabling statutes and the referenced forms and accounting standards because the Standard is a node within a network of legal instruments that collectively determine who reports, what is reported, how values are determined and what happens to the data once provided.

The text of this Reporting Standard, as supplied, records a single, clear commencement date and contains an internal mechanism for non‑substantive variations to forms and instructions. Specifically:

• Commencement: The Standard “commences on 1 April 2018” (paragraph 4). That is the only explicit temporal marker of when the instrument took effect as contained in the text.
• Minor variations: APRA may make minor variations to a form that is part of the Reporting Standard, and to the instructions to such a form, to correct technical, programming or logical errors, inconsistencies or anomalies, or to clarify their application (paragraph 13). In the event APRA makes such a variation, it must notify each ADI required to report under this Reporting Standard in writing (paragraph 14). The Standard treats these minor variations as not changing substantive requirements.

No other amendments, repeals or revision dates are listed in the provided text. There is no schedule of prior amendments, no history of consultation embedded in the instrument, and no record of versioning included here. The reporting instrument also contains a general interpretive clause that references other instruments “as in force from time to time” (paragraph 16). That clause permits the Standard to operate dynamically with changes to cross‑referenced statutes and standards without requiring textual amendment to the Reporting Standard itself when those external instruments change.

Because the document explicitly allows APRA to make minor variations (paragraph 13) and requires APRA to notify ADIs of such variations in writing (paragraph 14), the practical amendment path for form‑level and instruction‑level technical fixes is administrative rather than legislative. Larger substantive changes would presumably require a formal amendment process, but no procedure or record for substantive amendment is described within the Standard itself.

If a practitioner requires a definitive amendment history for compliance auditing or retrospective analysis, the text supplied here does not contain that record. The only concrete historical fact within the instrument is the 1 April 2018 commencement date and the administrative mechanism for minor, non‑substantive corrections with notification.

The Reporting Standard as provided contains no references to litigation, court decisions, tribunal rulings or administrative reviews. There are no case citations, no summaries of disputes about interpretation, and no recorded challenges to APRA’s application of this Standard within the text supplied.

Because the instrument is silent on litigation, the text does not indicate:

• any judicial interpretation of the Reporting Standard’s provisions;
• any appellate or tribunal determinations relevant to its scope or enforcement; or
• any disputes about APRA’s exercise of powers under paragraphs 8, 10 or 13-14.

For users requiring a litigation history to assess interpretive risk, compliance exposure, or precedent on contested points (for example, whether particular repos must or must not be reported at market value, or whether APRA’s change‑of‑frequency notices are subject to merits review), that information is not contained here and would need to be sought from judicial databases, APRA administrative records or other external sources.

Within the Standard itself, the dispute or review pathways that might apply to APRA’s written notices (for example changing reporting frequency under paragraph 8 or varying forms under paragraph 13) are not described. The instrument therefore provides the obligations and administrative powers but does not document any adjudicative history or precedent on their exercise.

This Reporting Standard contains a number of practical pitfalls and technical details that commonly cause compliance issues if overlooked. Below are the specific “gotchas” that follow directly from the text, together with their operational consequences:

1. Applicability table can be misread

• The table at paragraph 3 plainly lists building societies and credit unions as “No”. Some ADIs operate in hybrid forms or have rebranded; an entity that appears to be a building society or credit union could in legal terms still be an ADI classed differently. The Interpretation definitions in paragraph 15 require one to check statutory identity under the Banking Act 1959 and related instruments before assuming exemption.

2. “Other ADI” exclusions

• The definition of “other ADI” in paragraph 15 expressly excludes Cairns Penny Savings & Loans Limited. That is a very specific carve‑out. If your entity is an unusual or small ADI, check the “other ADI” definition rather than assuming inclusion.

3. Reporting at market value

• The Specific instructions require reporting all such securities “at market value”. This is a valuation convention that may differ from internal accounting or regulatory capital valuation methods used by the ADI (for example, amortised cost). Ensure market valuation process and documentation are in place for all repo and securities lending positions at reporting date.

4. Reporting by counterparty and no netting across security types

• The Standard requires positions to be reported by counterparty and expressly instructs that separate repo/resale agreements with the same counterparty should not be netted if they involve different security types (Specific instructions). Systems that aggregate across security types or that net by counterparty as a matter of course will produce incorrect ARF 320.5 returns.

5. Inclusion of reverse repos

• Reverse repos are explicitly included (Specific instructions). Some internal systems tag repos only in one contractual direction. Confirm that reverse repos (the ADI acting as cash lender or borrower depending on terminology) are captured.

6. Repos versus securities lending distinctions can be fuzzy

• The Specific instructions describe practical differences (e.g. securities lending tends to involve a fee; repo typically involves cash and collateral). But the economic similarity and overlapping contractual forms mean classification choices can be contested. The Standard’s reporting rules require consistency with the attached ARF 320.5 instructions, not solely commercial labels. Reconcile legal documentation to the reporting classification.

7. Sector classification traps

• The Standard warns that debt securities appearing to be issued by State, Territory or local governments may be issued by central borrowing authorities and should be classified accordingly (Specific instructions). Using high‑level issuer names without checking issuing authority can misclassify sectors on ARF 320.5.

8. Digital certificate and authorisation

• Paragraph 12 requires the officer submitting the data to digitally sign using a certificate “acceptable to APRA”. This creates an operational dependency: if you lack an APRA‑acceptable certificate or if certificate management fails, timely submission is not possible. Plan certificate procurement and rotation, and test the signing process in D2A.

9. APRA’s frequency changes and notifications

• APRA can change reporting frequency for particular ADIs (paragraph 8) and make minor variations to forms (paragraph 13). These are exercised by written notice; ADIs must have processes to absorb short‑notice change requests and software update cycles for form changes. APRA’s power to require more frequent reporting is discretionary and predicated on the ADI’s circumstances and prudential needs , prepare for potential short lead times.

10. The Standard does not contain enforcement specifics

• There is no penalty schedule in the document. Do not assume there is no legal consequence for non‑compliance; the enabling Act likely contains enforcement rules. The absence of sanctions in the Standard itself is a compliance blind spot: remedial or punitive consequences may still flow from the broader legislative framework.

11. “As in force from time to time” clause

• Paragraph 16 means definitions and references to Acts and standards are dynamic. Changes to accounting standards, Corporations Act definitions, or the Banking Act may alter reporting obligations without the Standard being redrafted. Compliance teams must monitor external instruments, not just this Standard.

12. Minor variations may nonetheless require programming changes

• Paragraph 13 allows APRA to make minor variations to correct technical or programming errors. Even “minor” corrections to a form’s layout, field names or XML schema can require software updates, testing and remapping. Treat any APRA notification under paragraph 14 as a change control event.

13. Data sharing to RBA and ABS

• Paragraph 2 explicitly permits the RBA and ABS to use the data. This may have practical implications for data confidentiality and governance inside the ADI, particularly where data is sensitive or used for broader statistical purposes.

In short, the gotchas involve classification mismatches, valuation conventions, counterparty and netting rules, digital signature logistics, APRA’s change powers and the dynamic importation of external statutory and accounting changes. Each of these points is grounded in the text quoted above and requires concrete procedural mitigation.

Below is a pragmatic, text‑grounded checklist that an ADI should implement to comply with Reporting Standard ARS 320.5, citing the relevant paragraphs and instructions from the instrument.

1. Confirm applicability

• Check whether your entity is covered by the Standard using the applicability table (paragraph 3) and the Interpretation definitions in paragraph 15. Determine whether you are an “Australian‑owned bank”, “foreign subsidiary bank”, “branch of a foreign bank” or “other ADI”. Note that building societies and credit unions are marked No and that “other ADI” excludes Cairns Penny Savings & Loans Limited (paragraph 15).

2. Obtain and understand ARF 320.5 and associated instructions

• The Standard states ARF 320.5 and its instructions are attached and form part of the Reporting Standard (first paragraph). Acquire the ARF 320.5 form and the specific instructions, and map each required field to internal reporting systems. Also consult Reporting Form ARF 320.0 for sector definitions as a general guide (Specific instructions).

3. Establish valuation procedures

• The Specific instructions require reporting all securities at market value. Implement or confirm market valuation policies for securities subject to repurchase/resale and securities lending/borrowing as at reporting date. Ensure valuation methods are documented and produce audit evidence.

4. Map positions to counterparty

• The instructions require reporting “by counterparty to the agreement” for both resale/repurchase positions and for securities lent/borrowed (Specific instructions). Ensure your position‑keeping system can produce counterparty‑level positions as at the reporting date. Do not net separate repo/resale agreements across security types even if the counterparty is the same (Specific instructions).

5. Capture reverse repos

• Confirm that reverse repo positions are captured and included in the submission (Specific instructions).

6. Classify securities by sector correctly

• Use ARF 320.0 sector definitions as a guide and pay particular attention to debt securities that appear to be issued by a State, Territory or local government but may be issued by central borrowing authorities (Specific instructions). Maintain source documentation to support sector classification.

7. Implement internal controls and authorisation

• Paragraph 11 requires processes and controls for internal review and authorisation to assure completeness and reliability. Document these processes, assign responsible officers, and create checklists and reconciliation routines that confirm position counts, valuation, counterparty mapping and sector classification.

8. Obtain and maintain an APRA‑acceptable digital certificate

• Paragraph 12 requires the officer who submits the information to digitally sign using a digital certificate acceptable to APRA. Contact APRA to confirm certificate requirements, procurement process, renewal cadence and contingency procedures for certificate expiry or compromise.

9. Configure submission method and test D2A integration

• Paragraph 6 requires electronic submission using the Direct to APRA application (D2A) or another method notified by APRA. Register for D2A if not already registered, obtain the necessary software and credentials, and perform end‑to‑end testing, including digital signature flows. Maintain a fallback plan for alternative method notification from APRA.

10. Build calendars and meet timetable

• The default reporting frequency is quarterly aligned to the ADI’s financial year (paragraph 7) and returns are due within 20 business days after the end of the reporting period (paragraph 9). Build a submission calendar anchored to your financial year and validate that key data feeds (trading, settlement, risk, market valuations) are complete before the 20 business‑day deadline. Track APRA notices for changed reporting periods under paragraph 8.

11. Establish procedures for extensions and APRA notices

• APRA may grant written extensions (paragraph 10). Establish a process to request, record and implement such extensions. Assign a mailbox or liaison for APRA written notices about frequency changes or form variations, since APRA must notify ADIs in writing of minor form variations (paragraph 14).

12. Change management for form/instruction variations

• Because APRA may make minor variations to forms or instructions (paragraph 13), put in place a change control process that can rapidly implement non‑substantive schema or instruction changes without disrupting submission timelines. Treat any APRA notification as a mandatory change control input.

13. Data governance and sharing considerations

• The Standard allows the RBA and ABS to use the data (paragraph 2). Incorporate this into your data governance, confidentiality and third‑party disclosure assessment. Prepare internal sign‑offs indicating that submitting data may be used beyond APRA prudential supervision.

14. Documentation and retention

• Keep source documents, valuation workings, counterparty reconciliations, and the submission record, including the digital certificate signature evidence. The Standard’s requirement for internal review and authorisation (paragraph 11) implies a need for auditable records.

15. Monitor external instruments and standards

• Paragraph 16 makes references to other Acts and standards effective “from time to time.” Monitor changes to the Banking Act, Corporations Act definitions of financial year, AASB interpretations, and the Financial Sector (Shareholdings) Act 1998. Update processes where cross‑referenced definitions change.

16. Run periodic compliance reviews and dry runs

• Conduct periodic mock submissions, reconciliation exercises between internal reports and ARF 320.5 outputs, and governance review of the controls specified in paragraph 11. Validate that market valuations, counterparty mappings and sector classification are consistent with ARF 320.0 guidance.

17. Operational resilience and contingency planning

• Because submission requires a digital certificate and the D2A application, plan for certificate expiry, staff turnover in authorised officers, and D2A downtime. Have escalation procedures to request APRA extensions (paragraph 10) if operational disruptions prevent timely submission.

By following the steps above and tying each action back to the Standard’s provisions (paragraphs 3, 5-12, 13-16 and the Specific instructions), an ADI will align operational practice with the Reporting Standard’s requirements and reduce the risk of inaccurate or late returns.