This instrument turns the defined technical constructs of APS 112 into a mandatory reporting dataset, specifying the granular fields APRA requires to oversee capital adequacy under the standardised approach. Core concepts in the Standard are:

• Scope of reporting: the Standard applies to exposures subject to the standardised approach to credit risk (Application and commencement). It excludes items explicitly carved out, such as assets required to be deducted under APS 111, securitisation exposures governed by APS 120, and exposures of certain overseas banking subsidiaries (Table 1: Scope).

• Level structure and NOHC filing: reporting is required at Level 1 (the ADI) and, if the ADI is part of a Level 2 consolidated group, at Level 2 as well; where the ADI is a subsidiary of an authorised non-operating holding company (NOHC) the immediate parent NOHC must provide the Level 2 information and must comply with this Reporting Standard other than specified paragraphs (Information required, para 2).

• Data model and primary key: Table 1 lists a fixed set of fields that must be populated for each exposure class and row; certain fields form the table’s primary key (Unique identifier). Any given combination of primary key fields must be unique in the reported dataset (Reporting tables description).

• Exposure granularity and attributes: Table 1 requires exposure classification (an exhaustive list of exposure classes aligned with APS 112), an exposure subclass where applicable, on/off-balance sheet flag, nature of off-balance transaction types, LVR bands for property and commercial exposures, LMI flag for certain residential loans, default category and provisioning bands, government guarantee flag, credit rating grades for rated exposures, exposure before/after credit risk mitigation and CCF, the risk weight applied and the derived RWA (Table 1 fields 1-13 and their descriptions).

• Special handling for market-related and securitisation exposures: market-related off-balance sheet exposures are reported using a specific approach: populate certain columns as Not Applicable or 0 and report total RWA (including credit valuation adjustment and default fund capital charges as calculated under APS 180) in the exposure-after-CRM/CCF field (Table 1 description). For securitisations that meet APS 120 operational requirements, APRA permits a deconsolidation principle for regulatory reporting (SPVs may be treated as non-consolidated third parties) and underlying assets may be excluded from regulatory capital, but retained or acquired securitisation exposures must be reported in ARF 120.1 and their RWA included in ARS 110.0 (Securitisation deconsolidation principle).

• Quality and assurance: reported information (except that required under paragraph 7) must be subject to external auditor review and testing consistent with APS 310 and relevant Auditing and Assurance Standards, at least annually or more often if required by the auditor; internal review and authorisation controls are also mandated (Quality control).

• Submission mechanics and authentication: APRA sets the electronic submission method and requires a digitally signed submission using a certificate acceptable to APRA (Method of submission; Authorisation). Reporting frequency defaults to quarterly aligned to the ADI’s financial year and submissions are due within 35 calendar days of period end, subject to APRA variation or extension (Reporting periods and due dates).

• Transitional and interpretative rules: transitional reporting is required for certain reporting periods under the old standard, and the Standard explicitly states interpretative definitions for key terms, cross-referencing APS 001 and other prudential instruments where applicable (Transition; Interpretation).

These concepts convert prudential rules about risk weights and capital into a stable, machine‑readable reporting form. The Standard therefore operates at the interface between regulatory capital methodology (APS 112, APS 113, APS 120, APS 180) and APRA’s data collection, imposing both content and assurance obligations on reporting entities.

Primary obliged parties: the Standard applies to any authorised deposit-taking institution (ADI) that applies the standardised approach to credit risk to all or part of its exposures for capital adequacy purposes (Application and commencement). This includes ADIs that are wholly standardised ADIs and ADIs that use the standardised approach partially (for example, where some portfolios remain standardised while others are on the IRB approach).

Group-level and NOHC interactions: where an ADI is part of a Level 2 consolidated group, reporting is required at both Level 1 and Level 2. If the ADI is a subsidiary of an authorised non-operating holding company (NOHC), the immediate parent NOHC must provide the Level 2 information and must comply with the Reporting Standard (other than specified paragraphs). The Standard therefore affects parent NOHCs that are required to make group reporting submissions on behalf of subsidiaries (Information required, para 2).

Excluded and special-case entities: foreign ADIs and providers of purchased payment facilities are excluded from some Table 1 reporting obligations (Table 1: Reporting basis). Exposures of an overseas banking subsidiary prudentially regulated by specified New Zealand authorities are explicitly excluded from the scope of Table 1 (Table 1: Scope). The Standard therefore imposes differential coverage depending on an ADI’s corporate form, group membership and regulatory jurisdiction.

Internal and third-party actors: the Standard directly involves the ADI’s data, risk, finance and audit functions because it requires systems, processes and controls assuring reported information and external auditor review under APS 310 (Quality control). External auditors have a defined role , the Standard requires their review and testing of systems and controls underpinning reported data (Quality control). Where securitisation structures meet APS 120, SPVs and third-party entities (special purpose vehicles) are treated in a specific way for reporting and capital calculations (Securitisation deconsolidation principle).

Regulatory and statistical users: APRA is the principal recipient of the data, using it for prudential supervision and capital adequacy assessment (Purpose). The RBA and ABS may also use the information, so APRA’s data collection has bilateral consequences for other official agencies (Purpose).

Operational suppliers: whatever electronic submission mechanism APRA specifies (its website or method notified by APRA) must be used; ADIs need to maintain compatible electronic systems and a digital certificate acceptable to APRA for signing (Method of submission; Authorisation). Third-party providers of data conversion, validation and reporting systems will be implicated where an ADI outsources reporting functions.

Who bears the cost and responsibility: the ADI bears the reporting burden , collecting, transforming and assuring the data, securing the digital certificate, submitting on time and accommodating APRA’s variations and notices. Immediate parent NOHCs carry the obligation to submit Level 2 returns where applicable. External auditors bear the cost of reviews and testing required by APS 310 as part of the assurance regime.

Duties imposed by the Standard are precise, with a short list of formal rights reserved to APRA:

Primary duties of ADIs

• Submit required information designated for an ADI at Level 1 for each reporting period and, where appropriate, Level 2 data for Level 2 groups (Information required). The dataset is Table 1 and its instructions.
• Submit electronically using APRA’s electronic method (Method of submission) and digitally sign submissions with an APRA-acceptable digital certificate (Authorisation).
• Meet the reporting timetable: quarterly by default, aligned to the ADI’s financial year, with submissions due within 35 calendar days after the end of the reporting period (Reporting periods and due dates).
• Ensure reported data (except information required under paragraph 7) are the product of systems, processes and controls that have been reviewed and tested by the external auditor under APS 310; maintain internal review and authorisation processes for data completeness and reliability (Quality control).
• For exposure classification and measurement, follow the definitions and calculation bases in APS 112 (Table 1 description), including LVR calculation rules in Attachment A of APS 112 and risk weighting rules in Attachment B, and follow APS 180 for market-related exposures where indicated (Table 1 notes).
• Report amounts in whole Australian dollars and convert foreign currency amounts in accordance with Australian Accounting Standards (Units of measurement).

Duties for NOHCs and group reporting

• Where an ADI is a subsidiary of an authorised NOHC, the immediate parent NOHC must provide Level 2 information and comply with this Reporting Standard as if it were the ADI, except for the reporting obligations expressly excluded (Information required, para 2).

APRA’s rights and discretions

• APRA may change reporting periods or frequency by written notice for a particular ADI, having regard to the ADI’s circumstances and the needs of APRA, RBA or ABS (Reporting periods and due dates).
• APRA may, by written notice, vary the reporting requirements in relation to a particular ADI (Variations).
• APRA may grant extensions of due dates in writing for submissions, setting a new due date on the notice (Reporting periods and due dates).
• APRA determines the acceptable electronic submission method and the form of digital certificate for authorisation (Method of submission; Authorisation).

Assurance and quality duties

• External auditor review and testing are required to be done at least annually or more frequently if the external auditor deems it necessary to form an opinion on the accuracy and reliability of the information (Quality control).
• Internal systems and controls must exist to authorise and review reported information and to assure completeness and reliability (Quality control).

Transitional duty

• For transitional reporting periods (periods that ended before 30 September 2024 but were required to be reported after revocation of the old standard), ADIs must report under the old reporting standard (Transition).

Notably absent as an express right or duty in the Standard

• The Reporting Standard itself does not set out penalties, sanctions or enforcement procedures for non-compliance within its text; instead it establishes the reporting obligations and APRA’s powers to vary, require and receive data (Authority). Any enforcement powers arising from non-compliance would derive from the enabling legislation and APRA’s broader regulatory powers rather than from specific penalty clauses inside this Reporting Standard.

Procedural duties for special cases

• Securitisation: where securitisations meet APS 120 operational requirements, SPVs may be treated as non-consolidated third parties for regulatory reporting; however, the ADI must still hold regulatory capital for retained or acquired securitisation exposures and report these exposures in ARF 120.1 with the related RWA reported in ARS 110.0 (Securitisation deconsolidation principle).
• IRB applicants and partial IRB use: ADIs with partial IRB approval must report under this form for operations that remain under the standardised approach; ADIs operating under APS 112 but that have applied for IRB must continue to meet this Reporting Standard for all exposures while separately reporting IRB candidate exposures under ARS 113 (Application to an IRB or an applicant IRB ADI).

These duties create specific operational obligations (data capture, validation, audit review, digital signing, and timely electronic submission) and confer discretion to APRA to vary reporting requirements where it reasonably considers it necessary for prudential supervision or for RBA/ABS requirements.

The Reporting Standard itself does not contain express penalty provisions. The instrument is made under section 13 of the Financial Sector (Collection of Data) Act 2001, which is identified as the Authority for making the Standard (Authority). The Standard repeatedly records APRA’s powers to vary reporting requirements, to change reporting periods for a particular ADI, and to grant extensions in writing (Reporting periods and due dates; Variations). It also prescribes the mandatory procedures for submission (electronic method and digital signature) and mandatory assurance requirements (external auditor review under APS 310 and internal controls) (Method of submission; Authorisation; Quality control).

What the text does state about enforcement-related mechanisms

• APRA may vary reporting obligations for an ADI by written notice and may change reporting frequency having regard to the ADI’s circumstances and the needs of APRA, RBA or ABS (Reporting periods and due dates).
• APRA may grant an extension of a due date in writing (Reporting periods and due dates).
• APRA may, by written notice to the ADI, vary the reporting requirements of this Reporting Standard in relation to that ADI (Variations).

Absence of specified sanctions in the Standard

• The Reporting Standard does not itself specify fines, criminal penalties, or administrative sanctions for failure to comply with the reporting obligations. It likewise does not specify notice and review procedures for disputed APRA directions within the text provided. Given that the instrument is made under the Financial Sector (Collection of Data) Act 2001, any enforcement mechanisms, penalties or compliance powers available to APRA would need to be located in the enabling Act or other relevant prudential legislation and policy instruments; such mechanisms are not included in the text of this Reporting Standard.

Practical effect for supervised entities

• Because the Standard establishes clear duties (what to report, how, when and with what assurance), non-compliance will be straightforward for APRA to identify (missing submissions, unsigned submissions, failure to provide auditor-assured systems). APRA’s stated powers to vary requirements and to require different frequencies provide it with administrative levers to require correction or additional reporting. The Standard’s requirement that data be digitally signed and be the product of audited systems sets a high bar for authenticated, auditable reporting.

Implementation and compliance risk therefore involve both the operational risk (meeting the specified submission, assurance and data-specification obligations) and the legal/regulatory risk (consequences of failing to meet APRA’s notices or directions), but the detailed legal enforcement procedures and penalties are not specified in this Reporting Standard and must be located in the enabling legislation or other APRA instruments.

The Reporting Standard explicitly cross-references a set of prudential standards, accounting standards and the enabling Act; its operation is therefore interdependent with other regulatory instruments.

Enabling legislation

• The Standard is made under section 13 of the Financial Sector (Collection of Data) Act 2001 (Authority). This locates the legal power for APRA to require data collection; any legal enforcement powers for non-compliance are to be located in that Act or other statutory instruments rather than in the Reporting Standard itself (Authority).

Cross-references to prudential standards

• The Standard is intended to be read in conjunction with Prudential Standard APS 112 Capital Adequacy: Standardised Approach to Credit Risk (APS 112) and, where appropriate, Prudential Standard APS 113 Capital Adequacy: Internal Ratings-based Approach to Credit Risk (APS 113) (Objective; Application and commencement). Many definitions in the Reporting Standard are those used in APS 112 and the Standard directs reporters to attachments and prudential practice guidance (APG 112).
• For external auditor assurance, the Standard requires testing as set out in Prudential Standard APS 310 Audit and Related Matters (Quality control).
• For market-related off-balance sheet exposures, the Reporting Standard requires RWA and CVA capital charge calculations as determined in APS 180 (Table 1 notes).
• For securitisation treatment, the Reporting Standard references Prudential Standard APS 120 Securitisation and requires reporting in ARF 120.1 and ARS 110.0 for securitisation exposures and associated RWA (Securitisation deconsolidation principle).

Accounting and auditing standards

• The Reporting Standard references Australian Accounting Standards (AASB) for currency conversion and units of measurement (Units of measurement). It also references Auditing and Assurance Standards Board publications to inform the scope and nature of external auditor review and testing (Quality control).

Group and regulatory reporting architecture

• The document establishes reporting at Level 1 and Level 2 consistent with definitions in APS 001 (Interpretation; APS 001). It interacts with other APRA reporting forms such as ARF 120.1 (securitisation capital) and ARS 110.0 (RWA reporting), creating dependencies across APRA’s reporting suite (Securitisation deconsolidation principle; Table 1 notes).

Transitional and revocation interaction

• The Standard contains transitional provisions which require ADIs to report under the old reporting standard for specified transitional reporting periods (Transition). The transitional rule interacts with the revocation of the old standard by the determination that made ARS 112.0; the Standard therefore relies on the administrative action of revocation and replacement.

Interpretation and definitions

• The Reporting Standard imports defined terms from APS 001 or CPS 001 as they apply to ADIs and authorised NOHCs and clarifies that references to Acts, Prudential Standards and Reporting Standards are to be read as references to the instruments as in force from time to time (Interpretation). This creates a dynamic interaction: as APS 112, APS 113, APS 120, APS 180 or APS 310 are updated, the referential content of ARS 112.0 will change accordingly.

Operational interactions

• The requirement to report market-related off-balance sheet exposures and CVA capital charges invokes APS 180 calculations performed either by standardised ADIs or by IRB ADIs for non-IRB exposures (Table 1 notes). The Standard therefore presupposes that ADIs have implemented the relevant capital calculation methodologies in the referenced prudential standards and that those calculations feed into the reporting dataset.

In short, ARS 112.0 sits within a network of prudential standards and statutory powers. It does not stand alone: compliance requires ADIs to operate in accordance with APS 112 for exposure definitions and risk-weighting rules, APS 310 for auditor assurance, APS 120 for securitisation treatment, APS 180 for market-related exposures and APS 001 for level definitions, and to follow the Financial Sector (Collection of Data) Act 2001 for legal authorisation and any enforcement consequences.

The Reporting Standard includes several textual markers that indicate it replaces an earlier reporting standard and contains transitional rules for periods straddling the revocation. The instrument explicitly defines "old reporting standard" as the reporting standard revoked by the determination that makes this Reporting Standard (Transition). The Standard applies for reporting periods ending on or after 30 September 2024 (Application and commencement, para 3), which establishes the commencement date for the new reporting obligations.

Transitional arrangements

• For reporting periods that ended before 30 September 2024 but for which an ADI would have been required to report by a date on or after the date of revocation of the old reporting standard, the ADI must report under the old reporting standard (Transition). The Standard includes a note to clarify that, if an ADI was required to report under the old standard and the reporting documents were due before the date of revocation, any overdue reporting documents remain required under the old reporting standard (Transition Note).

Replacement and revocation mechanics

• The Standard’s transitional rules define the scope of continuity and clarify that the determination making ARS 112.0 revokes the earlier reporting standard. It expressly defines "old reporting standard" to avoid ambiguity in transitional reporting obligations (Transition).

No historical amendments recorded within the text

• The text provided does not include a change log or history of prior amendments to ARS 112.0 itself; it presents the Standard as the instrument that takes effect from the stated commencement date and replaces a prior reporting standard. The document also repeatedly contains duplicated sections (likely editorial duplication in the source), but these duplications do not constitute formal amendments.

Cross-references to other instruments likely to be amended separately

• Because the Reporting Standard imports definitions and computational rules from APS 112, APS 113, APS 120, APS 180 and APS 310, any amendments to those instruments will affect the operation of ARS 112.0 by reference. The Standard anticipates this dynamic by providing that references to Acts, Prudential Standards, Reporting Standards and Australian Accounting or Auditing and Assurance Standards are references to the instrument as in force from time to time (Interpretation).

Practical consequence for compliance programmes

• ADIs must be prepared for the possibility that APRA or related prudential standards will be amended and that those amendments may change definitions, attachment rules (Attachment A-F referenced in APS 112), risk weights, or procedural requirements that feed into ARS 112.0 reporting. The Standard’s own transitional provision ensures continuity where reporting periods straddle the revocation of the old standard.

If an ADI needs a definitive statutory amendment history or consolidated text including any later variations, it must consult APRA’s determinations, the Financial Sector (Collection of Data) Act 2001 notices, and the consolidated versions of the referenced prudential standards; such source documents are outside the text of ARS 112.0 itself.

The text of this Reporting Standard contains no references to judicial decisions, disputes, or litigation history. It does not cite or summarise cases, nor does it record precedents or contested interpretations. The instrument is an administrative data collection standard rather than a document that sets out legal principles likely to have attracted reported litigation in its own text.

What the Standard does provide on legal footing

• It cites its enabling provision (section 13 of the Financial Sector (Collection of Data) Act 2001) as the legal authority for APRA to make the Reporting Standard (Authority). Any judicial challenge to APRA’s exercise of powers under that Act would be governed by the Act and general administrative law principles; the Reporting Standard itself does not contain or report on any litigation.

Implication for practitioners

• For legal advisers, compliance officers and risk teams, absence of litigation references in the Standard means that interpretive or compliance disputes will need to be resolved by reference to the enabling Act, APRA’s broader suite of prudential standards (APS 112, APS 113, APS 120, APS 180, APS 310, APS 001), APRA’s policy and supervisory guidance, and, where contestation arises, administrative law remedies or tribunals. The Standard neither predicts nor summarises any such challenges.

If a regulated entity seeks precedent or case law about disputes with APRA over reporting obligations, that material will be found outside ARS 112.0 in decisions and cases involving APRA’s enforcement or data-collection powers; such material is not provided in this Reporting Standard.

The Standard contains several specific features and drafting choices that create practical risks or traps for reporting entities. These are matters practitioners should flag and address in compliance and operational plans.

1. Multiple level reporting and NOHC quirks

• If an ADI is part of a Level 2 group, reporting is required at both Level 1 and Level 2 (Table 1: Reporting basis). If the ADI is a subsidiary of an authorised NOHC, the immediate parent NOHC must provide the Level 2 information and must comply with this Reporting Standard "other than paragraphs 6 and 13" (Information required, para 2). The Standard does not set out what paragraphs 6 and 13 contain in the provided text; practitioners must check the authoritative numbering in APRA’s consolidated instrument to identify the exceptions and plan group-level workflows accordingly.

2. External auditor review exception

• Quality control requires external auditor review and testing for all information provided under this Reporting Standard except "the information required under paragraph 7" (Quality control, para 1). The location and substantive scope of paragraph 7 in the consolidated standard matters , the exemption could mean particular fields or a NOHC-related submission are outside audit scope. Firms must identify exactly which reporting items are excepted from the external auditor requirement to avoid mistakenly omitting review for fields that do require it.

3. Market-related exposures and APS 180 linkage

• Market-related off-balance sheet exposures are treated specially: many columns must be populated as Not Applicable or 0, and total RWA must include CVA and default fund capital charges as determined in APS 180 (Table 1 notes). Incorrectly treating market-related exposures as standard off-balance sheet items will misstate RWA and capital metrics. Practically, this requires reliable mapping from front-office and market risk systems into the credit reporting dataset.

4. Securitisation deconsolidation principle

• Where securitisations meet APS 120 operational requirements, SPVs may be treated as non-consolidated third parties and the underlying pool may be excluded from regulatory capital. However, the ADI must still hold capital for any retained or acquired securitisation exposure and report those exposures in ARF 120.1 with RWA in ARS 110.0. This creates a disaggregation requirement across reporting forms; failure to coordinate across ARF 120.1, ARS 110.0 and ARS 112.0 can lead to inconsistency in APRA’s datasets.

5. Data model primary key uniqueness

• Table 1 specifies which fields are part of the primary key. Any duplicate combinations of primary key values across rows are not permitted. When transforming portfolio data into the reporting format, firms must ensure their ETL (extract-transform-load) processes manage uniqueness, aggregation and deduplication rules correctly; otherwise APRA’s schema validation will reject submissions.

6. LVR banding and LMI application

• LVR bands are highly granular (multiple 5% bands up to >100%). LVR must be calculated in accordance with Attachment A of APS 112. Lenders mortgage insurance (LMI) is only applicable to specific residential exposure types. Misclassification of exposure classes, incorrect LVR calculation methods or incorrect LMI flags will change the risk weight applied and materially affect RWA.

7. Credit rating grade mapping and unrated exposures

• For certain non-defaulted exposures (e.g. banks, sovereigns, covered bonds, general corporate, specialised lending), Table 1 requires credit rating grades 1-6 where rated, and a set of "unrated exposure subject to X% risk weight" categories where unrated. Entities must implement a consistent mapping from external ratings and issue-specific ratings to the grading scheme specified in Attachment F of APS 112. Incorrect mapping can lead to incorrectly applied risk weights.

8. Units, currency conversion and rounding

• Values must be reported in whole Australian dollars (no decimals) and foreign currencies converted according to Australian Accounting Standards. Conversion and rounding practices can cause reconciliation differences between accounting ledgers and reported figures; firms should document and reconcile the conversion approach.

9. Digital certificate requirement

• Submissions must be digitally signed using a digital certificate acceptable to APRA. Firms must ensure they possess and maintain an APRA-acceptable certificate and that signing processes are robust and auditable. A failure in the signing process could delay submission acceptance or trigger follow-up by APRA.

10. Transitional-period reporting confusion

• The transitional rule requires ADIs to report certain late reporting periods under the old reporting standard. This introduces a two-standard coexistence window for reporting teams and may require parallel report production for different periods. Firms must track which reporting periods fall under the old standard and which under ARS 112.0, and ensure consistent reconciliation where necessary.

11. Frequent duplication and editorial inconsistency in the source

• The provided source contains repeated blocks and duplications; practitioners must consult APRA’s authoritative published instrument to avoid relying on draft or duplicated text in secondary copies. Cross-checking APRA’s official repository is necessary to resolve any inconsistency.

12. Implicit dependencies on other prudential standards

• Many computation rules (LVRs, risk weights, CVA, securitisation treatment) are defined in other prudential standards (APS 112, APS 120, APS 180, APS 310). Firms that fail to align data and calculation engines to those underlying standards risk reporting misstatements.

Fixes and mitigations for these gotchas require mapping responsibilities across finance, credit risk, market risk, data engineering and external audit teams and maintaining an authoritative compliance matrix that links each Table 1 field to its calculation and assurance source.

Compliance with ARS 112.0 requires coordinated changes across data architecture, controls, audit planning and reporting operations. Below is a practical, source-mapped compliance checklist aligned to the Standard’s explicit requirements.

1. Confirm scope and level reporting obligations

• Determine whether the ADI applies the standardised approach to any portion of its exposures (Application and commencement). If yes, the ADI must report Table 1 at Level 1. If the entity is part of a Level 2 consolidated group, prepare to report Level 2 data or coordinate with the immediate parent NOHC if the ADI is a subsidiary of an authorised NOHC (Information required, para 2). Identify excluded exposures (assets deducted under APS 111, securitisation exposures covered by APS 120, and specified overseas subsidiaries).

2. Map exposures to Table 1 exposure classes and subclasses

• Map internal product and counterparty classifications to the exposure classes listed in Table 1 (Exposure classification and Exposure subclass columns). For commercial and lease exposures, map the exposure subclass (sovereign, domestic PSE, bank long-term/short-term, etc.) consistent with Attachment B and Attachment F of APS 112.

3. Implement field-level calculation rules

• LVR: calculate loan-to-value ratios per Attachment A of APS 112 and allocate exposures to the required LVR bands (Loan-to-valuation-ratio field).
• LMI: identify eligibility for lenders mortgage insurance and populate the Yes/No/Not Applicable flag only for the specified residential exposure types (Lenders Mortgage Insurance field).
• Default and provisioning: implement logic to classify exposures into the defaulted/reserved bands and to identify residential property defaults as defined in APS 112 (Defaulted field).
• Government guarantees: identify government guarantees as per APS 112 paragraph 17 and populate the Government guarantee flag for applicable residential standard exposures (Government guarantee field).
• Credit ratings: map external ratings and issue-specific ratings into credit rating grades 1-6 or the appropriate "unrated subject to X% risk weight" categories per Attachment F and Attachment B of APS 112 (Credit rating grade field).
• CRM and CCF: establish rules for exposure before and after credit risk mitigation and credit conversion factors as defined in APS 112, and ensure the exposure-before and exposure-after columns are populated correctly (Exposure before/after CRM and CCF).
• Risk weight and derived RWA: ensure risk weights applied reflect APS 112 rules and that RWA is derived according to APS 112; note that market-related exposures require special RWA aggregation including CVA/default fund charges as per APS 180 (Risk weight; RWA).

4. Data validation, primary keys and reporting format

• Implement database/ETL logic to enforce the Table 1 primary key uniqueness constraints and validation rules described in the Reporting tables section. Convert all monetary amounts to whole Australian dollars, using AASB-prescribed conversion rules where relevant, and ensure consistent rounding/truncation rules (Units of measurement).

5. External audit assurance and internal controls

• Engage external auditors to review and test the systems, processes and controls that generate the reported information in accordance with Prudential Standard APS 310. Plan for at least annual auditor testing and more frequent work if required by the external auditor to form an opinion on accuracy and reliability (Quality control).
• Document and implement internal review and authorisation processes for approving the reported dataset prior to electronic submission, including sign‑off matrices linking officers to the digital certificate signatory (Quality control; Authorisation).

6. Electronic submission and digital signing

• Register for APRA’s electronic reporting method and confirm the technical format APRA requires (Method of submission). Obtain or maintain a digital certificate acceptable to APRA and implement a controlled digital signing process for submissions (Authorisation).

7. Reporting calendar and extension management

• Align reporting cycles to the ADI’s financial year as required and calendar 35-day submission deadlines from period end (Reporting periods and due dates). Build calendar reminders and contingency plans for APRA variation notices and for the possibility of APRA granting extensions; track any written extension notices from APRA as the new due date.

8. Special cases: market-related exposures, securitisation and IRB interfaces

• Market-related off-balance sheet exposures: implement separate aggregation logic to calculate total RWA for market-related exposures including CVA and default fund capital charges under APS 180; populate Table 1 columns as instructed (Table 1 notes).
• Securitisation: determine whether securitisations meet APS 120 operational requirements; where they do, treat SPVs/underlying assets in reporting as permitted by the Standard but ensure that retained or acquired securitisation exposures are reported in ARF 120.1 and RWA in ARS 110.0 (Securitisation deconsolidation principle).
• IRB or partial IRB: if the ADI has partial IRB approval, ensure parallel reporting under ARS 113 for the IRB-expectant exposures and ARS 112.0 for exposures remaining under the standardised approach (Application to an IRB or an applicant IRB ADI).

9. Reconciliation, governance and documentation

• Reconcile Table 1 outputs to internal capital calculation systems and to other APRA returns (ARS 110.0, ARF 120.1 etc.). Maintain an audit trail linking source transactions to reported rows and the business rules applied.
• Document governance, including roles (data owner, approver, auditor contact), control matrices, standard operating procedures for submission, escalation paths for data issues and a post-submission review process to handle APRA queries or variation notices.

10. Transitional reporting and legacy submissions

• Identify any reporting periods that fall under the transitional rule (periods that ended before 30 September 2024 but had reports due after revocation of the old standard) and ensure those reporting periods are prepared under the old reporting standard, as required (Transition Note).

11. Testing and dry runs

• Conduct validation and schema-validation tests against APRA’s electronic submission interface well before the first live submission date. Perform parallel runs producing both legacy and ARS 112.0 outputs for the first reporting cycles, and involve the external auditor early to confirm the audit scope and timing.

12. Ongoing monitoring

• Monitor updates to APS 112, APS 113, APS 120, APS 180, APS 310 and APS 001, since ARS 112.0 explicitly incorporates definitions and calculation rules from those standards and states that references are to instruments "as in force from time to time" (Interpretation). Build a regulatory change process to capture and implement updates.

This compliance recipe is directly traceable to the Reporting Standard’s operational provisions: scope and timing (Application and commencement; Reporting periods and due dates), data definitions and table structure (Table 1), assurance (Quality control; APS 310), submission mechanics (Method of submission; Authorisation), special-case rules (Securitisation deconsolidation principle; Table 1 notes on market-related exposures) and transitional rules (Transition). Practitioners should consult the consolidated APRA instrument and the referenced prudential attachments to map every Table 1 field to its precise calculation and policy source before finalising systems and audit schedules.