Financial Sector (Collection of Data) (reporting standard) determination No. 34 of 2021

The Reporting Standard organises several legal and technical concepts that determine scope, content, and process.

Authority and purpose: The Standard is an Economic and Financial Statistics (EFS) Reporting Standard under ARS 701.0 (paragraph 3) and is made under s 13 of the Financial Sector (Collection of Data) Act 2001 (paragraph 1). The stated objective is to collect information on ADIs’ and RFCs’ provision of business finance to private and public sector businesses for use by the ABS and RBA, and possibly APRA (paragraphs 2-3).

Application threshold and measurement: The reporting population is defined by reference to an entity’s “business credit”, measured as the sum of specified items on a different reporting form (ARF 720.1A/B): items 1.1.1.2, 1.1.1.3 and 1.1.1.5 (paragraph 4). The default threshold is $2 billion; APRA can set a higher threshold for a specified institution and will notify that ADI or RFC in writing (paragraph 5).

Reporting basis and consolidation: The Standard requires reporting on a domestic books consolidation (paragraph 7). Where borrower-accepted commitments or bill acceptances are reported, they must be for contracts where the legal lender (or legal tender) is an entity included in the domestic books consolidation (form instructions and item 1 definitions).

Data content and classification: ARF 741.0 collects monthly counts and values of new borrower-accepted commitments, cancellations and reductions of credit limits, total credit limits and outstanding balances, by product (credit cards, margin lending, other revolving credit, fixed-term loans), by business size (small/medium/large) and by purpose (construction finance broken down by state and sub-purpose; purchase of property; wholesale, plant and equipment, working capital, acquisitions, refinancing, general business) and by industry (ANZSIC-style breakdowns, items 3.1.1-3.1.19). It also collects new finance lease commitments by purpose (item 4). Certain fields are derived, and the form enforces specific reconciling relationships (for example, item 1.4.1 must reconcile to specified items on ARF 720.1A/B; see item 1.4.1 instructions).

Types of finance included and excluded: The instructions define “finance” to include loans, finance leases and bill acceptances (Instructions, Types of finance). Specific parts of the form exclude some types (for example, item 1 includes only loans, excludes bill acceptances and finance leases; item 4 includes only finance leases).

Quality and audit controls: All information must arise from systems and controls reviewed and tested by the external auditor in line with Prudential Standard APS 310 for ADIs or Reporting Standard RRS 710.0 for RFCs; those reviews must be at least annual or more frequent if the external auditor requires it (paragraph 13). The data also must be subject to the entity’s internal review and authorisation systems and controls (paragraph 14).

Submission mechanics and format: Submission is electronic, using D2A or another APRA-notified method, and the submitter must digitally sign using a digital certificate or other APRA-acceptable digital identity (paragraphs 8 and 15). Reporting uses Standard Business Reporting conventions and Australian Accounting Standards (AASB 121 for foreign currency conversions where applicable), monetary amounts in AUD or AUD equivalent, whole dollars and unscaled whole numbers (Reporting basis, Values, Numbers, Standard Business Reporting sections).

Administrative discretions: APRA can change reporting periods or frequency for an individual institution (paragraph 11), can grant extensions of due dates (paragraph 12), and can determine a higher threshold for particular institutions (paragraph 5). References to Acts, Prudential Standards and Reporting Standards are to those instruments as in force (paragraph 18), which enables updating by reference.

Information use and publication: The Schedule explicitly says the ABS and RBA are primary users for statistical publications and policy work; APRA may use the information “for prudential and publication purposes” (paragraphs 2-3). That creates a channel for data to move from supervisory use to public statistical outputs.

Together, these concepts establish a technical reporting regime: eligibility determined by a defined threshold on other APRA returns, monthly electronic delivery, prescribed data taxonomy and reconciliations, mandatory audit testing of reporting systems, and administrative levers for APRA to tighten, relax or re-scope reporting by institution.

The Reporting Standard targets two categories of regulated entities: authorised deposit-taking institutions (ADIs) and registered financial corporations (RFCs). However, it does not apply to every ADI or RFC by default. The statutory rule is that an ADI or RFC is subject to ARS 741.0 if its “business credit” is at least $2 billion, where “business credit” is calculated as the sum of the values reported in items 1.1.1.2, 1.1.1.3 and 1.1.1.5 on Reporting Form ARF 720.1A/B ABS/RBA Loans and Finance Leases (Standard)/(Reduced) (paragraph 4). The Reporting Standard thus ties coverage to an entity’s position on a separate reporting return. That measurement rule is internal to APRA returns and requires affected firms to map their ARF 720.1A/B submissions into the eligibility test.

APRA retains discretion to alter which institutions are captured. Paragraph 5 expressly allows APRA to determine that a higher threshold applies to a particular ADI or RFC and requires APRA to notify the affected institution in writing. Paragraph 11 allows APRA to change reporting periods or frequencies for particular institutions. These clauses mean that an institution that would otherwise be outside the default $2 billion band may be brought in (or temporarily assigned higher thresholds or different periodicity) by administrative decision and written notice.

Coverage is also bounded by the consolidation basis. Paragraph 7 requires reporting on a domestic books consolidation. The form instructions clarify that borrower-accepted commitments and bill acceptances must relate to contracts where the legal lender or legal tender is an entity included in that domestic books consolidation. That means foreign branches or legal lenders outside the domestic consolidation are excluded from the reporting population for ARF 741.0, even if the consolidated group is large elsewhere.

Who actually bears the costs: ADIs and RFCs that meet the threshold will be the ones to operate mapping, data extraction, reconciliation and audit processes, and to deliver monthly submissions within the 10-business-day window (paragraphs 9-10). Smaller ADIs and RFCs below the threshold will not have reporting obligations under this Standard unless APRA issues a written determination otherwise (paragraph 5). The Standard also affects auditors (external auditors are required to review systems and testing per paragraph 13) and internal control and reporting teams that must maintain procedures for internal review and authorisation (paragraph 14). Finally, data consumers , ABS, RBA and APRA , are affected as recipients and users of a new or updated dataset (paragraphs 2-3).

Practical implications for affected entities include ongoing monthly operational cost (data extraction, mapping, and audit testing), one-off configuration costs (mapping ledger/product codes to the specific ARF 741.0 categories and state-level breakdowns), and potential compliance costs if APRA adjusts thresholds or frequency for particular entities. The domestic consolidation and legal-lender conditions mean entities must be able to identify legal lending entity on each contract and appropriately include or exclude items from their reports.

Duties established by the Reporting Standard are concrete and procedural. Primary duties include:

• Duty to report: An ADI or RFC to which the Standard applies must provide APRA with the information required by ARF 741.0 for each reporting period on a domestic books consolidation basis (paragraph 7). This duty is mandatory for entities meeting the threshold or otherwise designated by APRA in writing.

• Timing and frequency: The default reporting frequency is monthly; information must be provided in respect of each calendar month (paragraph 9). The due date is within 10 business days after the end of the reporting period (paragraph 10). APRA can change those periods for particular institutions, requiring more or less frequent reporting, by written notice (paragraph 11). APRA can also grant written extensions of due dates (paragraph 12).

• Method and authorisation: Submissions must be electronic via D2A or another APRA-notified electronic method (paragraph 8). When using D2A or another APRA-notified method, the submitting officer or agent must digitally sign the information using a digital certificate or other APRA-acceptable digital identity (paragraph 15).

• Data quality and audit: All information must be the product of systems, processes and controls reviewed and tested by the external auditor in accordance with Prudential Standard APS 310 (for ADIs) or Reporting Standard RRS 710.0 (for RFCs) (paragraph 13). This review and testing must be annual or more frequent if the external auditor requires it. Separately, entities must maintain internal systems, processes and controls for internal review and authorisation to assure completeness and reliability (paragraph 14).

• Reporting content and conformity: Entities must comply with the detailed form instructions: report only specified finance types in the specified items, classify by predominant purpose, use Australian Accounting Standards for valuation and currency conversion (AASB 121 where applicable), report monetary amounts in AUD (or AUD equivalent), whole dollars, and submit numbers unscaled (Reporting basis and Values sections; AASB 121 citation). Certain reconciliations are required between ARF 741.0 and ARF 720.1A/B (item 1.4.1 instructions).

Rights, discretions and procedural protections in the Standard include:

• APRA’s discretion to change treatment: APRA may notify a higher threshold for a particular ADI or RFC (paragraph 5), can alter reporting frequency for a particular institution (paragraph 11), and can grant extensions of due dates (paragraph 12). These are administrative rights exercised by APRA that can ease or tighten obligations.

• Procedural notice: Decisions by APRA that affect an entity’s reporting obligations (higher threshold or altered reporting frequency) must be notified in writing (paragraphs 5 and 11). Extensions are given in writing (paragraph 12). That creates a paper trail.

• Use of data: The Schedule specifies how collected data will be used: primarily by ABS and RBA and potentially by APRA for prudential and publication purposes (paragraphs 2-3). Entities therefore have notice that some information will feed public statistical outputs as well as APRA prudential analysis.

What the Standard does not specify in its text: it does not include express statutory rights of appeal or internal review of APRA decisions within the instrument itself (nor does it set out penalties or enforcement processes in the text of the Standard). It does, however, anchor some duties to other prudential and auditing instruments (APS 310 and RRS 710.0) and to Australian Accounting Standards, which themselves contain norms about audits and accounting mechanics.

Collectively, the duties require entities to build and maintain month-by-month reporting capability, to permit external auditor testing of the underlying systems and controls, and to submit validated and digitally authorised returns through APRA’s electronic channels within a tight timetable unless APRA agrees otherwise in writing.

The Reporting Standard text does not set out statutory penalties or enforcement mechanisms within its own provisions. The instrument prescribes reporting obligations, submission mechanics, quality-control processes and APRA’s administrative discretions (for example to set higher thresholds, to change reporting frequency and to grant extensions; see paragraphs 5, 11 and 12), but it does not itself specify fines, criminal offences or civil penalties for failure to comply.

What the Standard does provide in relation to enforcement-adjacent measures:

• APRA controls procedural levers: it must notify institutions in writing when it imposes a different application threshold (paragraph 5) and may change reporting frequency or periods for a particular institution by written notice (paragraph 11). APRA may grant written extensions of due dates (paragraph 12). These are administrative mechanisms that can mitigate or amplify reporting obligations for specific entities.

• Audit and control obligations: Entities must have reporting produced from systems, processes and controls reviewed and tested by the external auditor under APS 310 or RRS 710.0 (paragraph 13). That places an obligation on auditors to inspect and test reporting processes and on entities to remedy deficiencies identified by auditors. The Standard’s reliance on established prudential audit frameworks creates a channel by which issues with reporting systems can be escalated to APRA via auditor findings under those separate instruments.

Because the Determination is made under the Financial Sector (Collection of Data) Act 2001, enforcement mechanisms, remedies and penalties for non-compliance with reporting obligations are contained in the Act itself and related instruments, not repeated in the Reporting Standard. The Reporting Standard therefore must be read alongside the Act for an understanding of statutory enforcement powers, penalty regimes and compliance obligations that apply if an entity fails to lodge required information, lodges incorrect information, or refuses to permit auditor review. The Determination explicitly references section 13 of the Act as its authority and invokes section 15 to declare commencement (headnote and opening statements).

Given the Reporting Standard’s silence on express penalties, affected institutions should consult the Financial Sector (Collection of Data) Act 2001 and related APRA enforcement and compliance guidance to determine the precise legal consequences of non-compliance. They should also note that auditor findings under APS 310 or RRS 710.0 may trigger supervisory action by APRA under prudential frameworks, even if the Reporting Standard itself does not specify a separate penalty.

The Reporting Standard cross-references and depends on multiple other regulatory and accounting instruments, connecting APRA’s data collection remit to prudential, accounting and statistical authorities.

Primary statutory basis: The Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 and references section 15 in the commencement declaration (headnote and paragraph 1). The Act supplies the enabling powers for APRA to require data; any enforcement or penalty powers that apply to failures to comply with reporting obligations will be located in the Act rather than in the Standard itself.

Inter-report linkages: Coverage is defined by reference to values reported on ARF 720.1A/B ABS/RBA Loans and Finance Leases (Standard)/(Reduced) , specifically items 1.1.1.2, 1.1.1.3 and 1.1.1.5 determine whether an ADI or RFC meets the $2 billion business-credit threshold (paragraph 4). Item-level reconciliation requirements also reference ARF 720.1A/B: item 1.4.1’s credit outstanding amounts must equal particular items on ARF 720.1A or ARF 720.1B depending on whether the institution reports the standard or reduced ARF 720.1 (item 1.4.1 instructions). That creates an operational dependency,entities must manage mapping and consistency across multiple APRA reporting forms.

Prudential standards and audit rules: Paragraph 13 requires the external auditor review and testing to be carried out as set out in Prudential Standard APS 310 Audit and Related Matters for ADIs or Reporting Standard RRS 710.0 ABS/RBA Audit Requirements for RFCs. Those instruments govern scope and nature of auditor work and are part of the prudential architecture; deficiencies or findings under those standards could engage supervisory actions under APRA’s broader prudential regime.

Accounting and auditing standards: The Standard requires compliance with Australian Accounting Standards for valuation and instructs conversion of foreign-currency amounts to AUD in accordance with AASB 121 The Effects of Changes in Foreign Exchange Rates (Values section). It also points to relevant Auditing and Assurance Standards Board guidance for auditors’ scope (paragraph 13). Paragraph 18 states 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, indicating the Reporting Standard operates in a live regulatory eco-system where changes to referenced instruments may alter how ARF 741.0 is implemented.

Statistical authorities and use: The form is designed primarily to supply the ABS and RBA for statistical outputs and policy work (paragraph 2). APRA’s own stated uses are prudential and publication purposes (paragraph 3). That means collected information may feed public aggregate statistics and central-bank research, implicating data confidentiality and publication rules both within APRA and ABS/RBA frameworks.

Standard Business Reporting (SBR) and digital identity: The form utilises SBR conventions (Numbers and SBR sections) and mandates electronic submission via D2A or another APRA-notified method, with digital signing (paragraphs 8 and 15). This interacts with digital identity frameworks and with APRA’s D2A infrastructure, potentially engaging other regulatory or technical guidance concerning electronic signatures and security.

Interplay with other returns and exclusions: The instruction to exclude related parties and to include only contracts where the legal lender or legal tender is included in the domestic books consolidation means that corporate law and group-structure realities (for example, intra-group lending, foreign branches) affect report content. The Standard also distinguishes between on-balance-sheet stocks and other items (stock items reported only if held on-balance-sheet unless otherwise directed), tying into accounting recognition rules.

Finally, paragraph 18’s “as in force from time to time” clause means the Reporting Standard is dynamically linked to changes in the referenced prudential and accounting instruments; amendments to APS 310, RRS 710.0, ARF 720.1A/B, AASB 121 or SBR rules will affect compliance obligations for ARF 741.0 reporters.

Affected entities must therefore manage ARF 741.0 compliance in a multi-instrument context: APRA reporting forms, prudential audit standards, accounting standards, and APRA’s electronic submission and notification practices.

This Determination (No. 34 of 2021) expressly revokes Financial Sector (Collection of Data) (reporting standard) determination No. 10 of 2019 and replaces Reporting Standard ARS 741.0 ABS/RBA Business Finance with the version set out in the Schedule (opening paragraphs). The Determination is dated 30 July 2021, signed by Alison Bliss as delegate of APRA, and commences on registration on the Federal Register of Legislation (headnote and commencement statement).

Specific amendment mechanics and routes identified in the text:

• Replacement: The Determination revokes a prior APRA reporting-standard Determination (No. 10 of 2019) and issues a new ARS 741.0 (headnote and Schedule). That is the immediate historical change recorded in the instrument.
• Prospective adjustment by APRA: The Standard contains built-in mechanisms for APRA to vary the application of the Standard to particular entities without amending the Standard text itself. Paragraph 5 allows APRA to determine a higher threshold for a particular ADI or RFC and to notify that entity in writing. Paragraph 11 allows APRA, by notice in writing, to change reporting periods or specified reporting periods for a particular ADI or RFC, increasing or decreasing reporting frequency. Paragraph 12 allows APRA to grant extensions of a due date in writing. These provisions operate administratively and do not require a formal amendment to the Determination published on the Federal Register; they provide APRA with tools to change who reports and how frequently via written notices to the individual reporting entities.
• Ongoing cross-references: Paragraph 18 states that any reference to an Act, Prudential Standard, Reporting Standard, or Australian Accounting or Auditing Standard is a reference to the instrument “as in force or existing from time to time”. That language permits the practical effect of amendment by amendment: when a referenced instrument is amended, ARF 741.0’s requirements (for example auditors’ obligations under APS 310) follow those changes without ARS 741.0 itself being formally amended.

Recorded effective dates: The Standard applies for reporting periods ending on or after 30 September 2021 (paragraph 6). The Determination’s date is 30 July 2021; the commencement trigger is registration on the Federal Register.

No other historical amendments, variations or side-by-side tracked changes are recorded in the text provided. The instrument does not catalogue prior versions beyond the single revocation, nor does it note transitional arrangements beyond the commencement date and the reference to the prior Determination being revoked. Any subsequent legislative or regulatory amendments post-dating this Determination are not included in the instrument; paragraph 18’s “as in force from time to time” indicates that future changes to referenced instruments (for example APS 310 or ARF 720.1A/B) will affect operation of ARF 741.0.

Entities should therefore track:

• APRA written notices under paragraphs 5, 11 and 12 as operational amendments affecting their obligations;
• amendments to referenced prudential standards, reporting standards and accounting standards, which flow through by reference under paragraph 18; and
• any later APRA Determinations that explicitly amend or revoke ARS 741.0 (as this Determination did to the earlier No.10 of 2019).

The text of the Determination and the Schedule contains no mention of litigation, court decisions, judicial review, or prior cases concerning ARS 741.0 or the revocation of the earlier Determination. It does not record any judicial challenges, settled disputes, or case law relating to the Reporting Standard. Nor does the instrument reference any specific legal precedents.

Because the Determination is administrative and statutory in character, any legal challenges to APRA’s exercise of powers under the Financial Sector (Collection of Data) Act 2001 (for example, claims of procedural unfairness, jurisdictional error or unreasonable exercise of discretion in applying paragraph 5 or paragraph 11 to a particular entity) would proceed in the appropriate forum under administrative law. The Reporting Standard itself contains no procedural appeal or review mechanism, and it does not state whether APRA provides internal merits review of threshold or period-change decisions; it requires APRA to notify institutions in writing of particular decisions (paragraphs 5 and 11) and to provide extensions in writing (paragraph 12).

Because the instrument does not reproduce the enforcement or review provisions of the Financial Sector (Collection of Data) Act 2001, interested readers should consult the Act directly for standing, remedies and avenues of review (judicial review, merits review or statutory appeal rights may be set out there). The absence of any litigation history in the instrument means practitioners should seek the Act and APRA’s public guidance, or public records of litigation, to assess whether any challenges to ARS 741.0 have been commenced or determined.

In short, the schedule and Determination do not supply litigation history and do not identify any contested legal interpretations; they provide a regulatory text and administrative mechanisms that could, in principle, be the subject of litigation under broader administrative law, but no such history is recorded in the source.

The Reporting Standard is detailed and contains several technical traps that can generate compliance and reconciliation issues if not anticipated. The main practical “gotchas” are as follows, grounded in the instrument’s specific wording:

1. Eligibility is not measured by total assets or group size but by a calculated “business credit” number drawn from ARF 720.1A/B (paragraph 4). The Standard makes the threshold depend on the sum of three specific ARF 720.1A/B items (1.1.1.2, 1.1.1.3 and 1.1.1.5). Reporting entities must therefore maintain accurate cross-form mapping. Misunderstanding which ARF 720.1 items to sum will misclassify institutions as in or out of scope.

2. Domestic books consolidation matters for inclusion. Paragraph 7 requires reporting on a domestic books consolidation, and the form instructions require that borrower-accepted commitments and bill acceptances be contracts where the legal lender/legal tender is an entity included in that domestic consolidation. Loans in foreign branches or intra-group loans where the legal lender is offshore may be excluded even if the parent entity has large global exposures. Entities must be able to identify the legal lending entity at contract level.

3. Product and purpose classification is granular and state-specific in parts (for example, construction finance is split across states and by sub-purpose such as construction of dwellings vs non-residential buildings; see item 2.1.1 and sub-items). Mapping system codes to the form’s taxonomy requires careful coding and may require jurisdictional mapping for projects crossing state lines.

4. Reconciliation requirements create hard constraints. Item 1.4.1’s credit outstanding values must reconcile to specific items on ARF 720.1A/B (item 1.4.1 instructions). If an entity reports on both ARF 720.1A and ARF 741.0, discrepancies will trigger queries and audit focus. Derived fields are common; mis-implemented derivations will result in internal inconsistencies.

5. Types of finance are selectively included/excluded per item. For example, item 1 only includes loans and excludes bill acceptances and finance leases (item 1 instructions). Item 4 includes only finance leases. Item 3 includes all finance types including bill acceptances but excludes borrower-accepted commitments for bill facilities (item 3 instructions). Entities must apply these inclusions and exclusions at an item-by-item level.

6. “Borrower-accepted commitments” has a specific meaning: agreements to increase credit limits (including internal refinances). For stock reporting, the credit limit is the maximum available without additional lender authorisation and includes outstanding balances and capitalised interest/fees (item 1 definitions). Practitioners must distinguish between used balance, committed limit, and temporary over-advances.

7. Related parties are excluded. The form instructs to exclude positions with related parties (Counterparties section). Firms must correctly apply related-party definitions across corporate groups and associate relationships when producing the form.

8. Stock vs flow reporting: Some items are “during the reporting period” (flows) and others are “as at end of reporting period” (stocks) , see reporting basis notes for item 1 versus other items. Confusion between flow and stock measurement will produce errors.

9. Currency conversion and accounting standards: Values must be in AUD or AUD equivalent, using AASB 121 for conversion (Values section). Entities with foreign-currency lending must apply correct translation rules and ensure consistency with financial statements.

10. Audit testing frequency: Paragraph 13 requires external auditor review and testing at least annually or more frequently if required by the auditor. If auditors require more frequent testing, the entity’s governance and data processes must support that cadence.

11. Tight deadlines and electronic signing: The reporting due date is 10 business days after month-end (paragraph 10) and submissions must be digitally signed using an APRA-acceptable credential (paragraph 15). That tight window may be operationally challenging, particularly where reconciliation to ARF 720.1A/B is required or where month-end systems are slow. APRA can grant written extensions (paragraph 12), but entities must plan to meet the default cadence.

12. Derived fields and SBR types: Several items are described as derived or aggregated from other items (for example item 2.1.1 is the sum of sub-items; item 2.1.9 is derived as an arithmetic residual). The form requires SBR accounting-type flags (debit/credit) for monetary items. Entities must ensure technical submission files carry the correct SBR attributes and derived values align with component submissions.

13. Use and publication risk: The Schedule states that ABS and RBA use the data for statistical publications and that APRA may also use it for publication (paragraphs 2-3). Institutions should therefore expect that some aggregated statistics may enter the public domain and consider data confidentiality and reputational considerations when structuring internal controls.

14. APRA’s ability to alter thresholds or frequency for an individual institution means compliance burdens can change administratively and with short notice (paragraphs 5 and 11). Entities should monitor written notices from APRA and maintain flexibility in reporting pipelines.

Addressing these “gotchas” requires coordinated mapping between general ledger/product code dictionaries and ARF 741.0 categories, well-documented definitions of legal lender and related parties, month-end reconciliation procedures, currency translation policies consistent with AASB 121, robust external-auditor liaison, digital signature readiness, and contingency plans to apply for extensions when operational bottlenecks arise.

Compliance with ARS 741.0 requires technical mapping, governance controls, audit coordination and operational delivery. The following steps, anchored in the Reporting Standard text, outline a practical compliance programme:

1. Confirm applicability using ARF 720.1A/B items. Use the prescribed test in paragraph 4: sum the values reported in ARF 720.1A/B items 1.1.1.2, 1.1.1.3 and 1.1.1.5 to determine whether business credit is ≥ $2 billion. If APRA has notified a different threshold in writing, use that value (paragraph 5). Document the calculation and retain evidence of the ARF 720.1A/B submissions used.

2. Establish domestic books consolidation practice. Paragraph 7 requires reporting on a domestic books consolidation. Identify legal lenders and legal tender at contract level so you can include only contracts where the legal lender/legal tender is an entity in the domestic consolidation (form instructions). Maintain a register mapping each loan, finance lease and bill acceptance to the legal lending entity and consolidation category.

3. Map systems to the ARF 741.0 taxonomy. Perform a full mapping of product codes, purpose codes, industry codes and geography to ARF 741.0 items (items 1-4 and sub-items). For construction and purchase-of-property items, map projects by location of physical construction/purchase rather than headquarters or booking location (item 2 instruction). Flag derived items and build automated calculations for sums and residuals as specified (e.g. item 2.1.1 is the sum of sub-items; item 2.1.9 is a derived residual).

4. Define inclusion/exclusion rules by item. Implement rules: item 1 includes only loans and excludes finance leases and bill acceptances; item 3 includes loans, finance leases and bill acceptances but excludes borrower-accepted commitments for bill facilities; item 4 includes only finance leases (see item instructions). Exclude related-party positions (Counterparties section). For borrower-accepted commitments, apply the definition of credit limit that includes outstanding balances and funds immediately available without additional approval.

5. Set accounting and valuation rules. Ensure monetary values comply with Australian Accounting Standards and convert foreign currency amounts to AUD per AASB 121 (Values section). Report whole-dollar AUD equivalents and submit numbers unscaled, as whole numbers for ADIs and RFCs (Values and Numbers sections). Ensure SBR attributes (debit/credit accounting type) are correctly set for monetary fields per the form instructions.

6. Build reconciliation controls. Implement reconciliation between ARF 741.0 and ARF 720.1A/B where required (item 1.4.1 instructions). Reconcile derived items to components, and reconcile flow vs stock items. Maintain a month-end reconciliation pack to support auditor testing and APRA queries.

7. Prepare systems for audit testing. Paragraph 13 mandates external-auditor review and testing of systems, processes and controls in accordance with APS 310 (for ADIs) or RRS 710.0 (for RFCs). Engage the external auditor early to agree scope and timing, and to support at least annual testing; be prepared for more frequent testing if the auditor requires. Maintain documentation evidencing internal controls (paragraph 14) and auditor test results.

8. Establish submission processes and digital identity. Use APRA’s D2A application or another APRA-notified web-based submission method (paragraph 8). Obtain and manage digital certificates or other APRA-approved digital identity credentials for officers/agents authorised to sign submissions (paragraph 15). Build access control and change-management for the credentials.

9. Operational calendar and governance. The default reporting frequency is monthly, with returns due within 10 business days after month-end (paragraphs 9-10). Create an operational calendar that accounts for data extraction, validation, auditor testing (as required), reconciliation, internal sign-off and digital submission. If the 10-business-day window is infeasible in a given month, apply to APRA in writing for an extension (paragraph 12) and preserve evidence of the request and any grant.

10. Monitor APRA notices and adapt. APRA can set a higher threshold or adjust reporting frequency for a particular institution by written notice (paragraphs 5 and 11). Monitor APRA communications and maintain flexibility in pipelines for either increased or decreased reporting frequency and scope.

11. Data governance and confidentiality. Because ABS, RBA and APRA use the data for statistical and prudential purposes and may publish aggregate statistics (paragraphs 2-3), implement data governance policies for data quality, confidentiality, and publication control. Retain audit trails for data transformations and forensic logs for submissions, and be ready to explain methodology to APRA, the external auditor, ABS or RBA if requested.

12. Training and change management. Train staff in the specific definitions and the nuanced inclusion/exclusion rules (for example, borrower-accepted commitments, legal lender, related parties, and on-balance-sheet only for stocks). Document procedures and update process documents when referenced instruments change (paragraph 18).

13. Test end-to-end submission. Run mock submissions on D2A or equivalent to confirm technical SBR attributes, derived-item calculations and that item-level files pass APRA validation (include SBR accounting types as required). Maintain a technical submission guide and version control for the mapping logic.

By following these steps and paying attention to the detailed item-level instructions, entities can build a repeatable monthly reporting process that satisfies ARS 741.0’s requirements for timing, form, quality control and reconciliation. The critical operational controls are accurate eligibility calculation via ARF 720.1A/B, robust mapping to the ARF 741.0 taxonomy, audited systems and a tight month-end process that supports the 10-business-day submission deadline.