Financial Sector (Collection of Data) (reporting standard) determination No. 54 of 2023

The instrument organises reporting around recurring liquidity management concepts and defines precise line items to capture them. Key concepts in the source are:

• Unencumbered liquid assets (Item 1). Item 1 collects the stock of liquid assets that are unencumbered, separated into HQLA (high‑quality liquid assets) and other liquid assets, RBA‑eligible securities from self‑securitisation, offshore liquid assets, and MLH‑specific categories. Item 1.1 ties the HQLA definition to APS 210 attachments and ARF 210.1A; Item 1.3 mandates reporting of self‑securitisation RBA‑eligible securities after applicable RBA margins. Item 1.6 is the sum of 1.1 to 1.5, and item 1.6.1 is the offshore portion.

• Net funding outflows over the prior five business days (Item 2). Item 2 captures the funding stock and uses derived columns to compute changes between the reporting date and five business days prior. Items 2.1-2.5 partition funding by customer type and instrument: retail deposits (2.1), wholesale non‑FI deposits (2.2), financial institution deposits (2.3), short‑term wholesale funding <1 year (2.4) and other wholesale including repos and capital instruments (2.5). Repos are explicitly directed to item 2.5 irrespective of tenor, Additional Tier 1 and Tier 2 should be in 2.5, and Common Equity Tier 1 should not be in 2.5. Derived sums (2.6 and 2.6.1) aggregate domestic and offshore components.

• Net contingent and committed outflows (Item 3). Item 3 captures net amounts of contingent and committed outflows across a five business day window. Distinct categories separate principal flows not attached to facilities (3.1) from uncommitted facilities (3.2), committed liquidity facilities (3.3), committed credit facilities (3.4) and other committed facilities (3.5). Column conventions differ: Column 1 is dollar outflow over the last five business days, Column 2 is an outflow as a percentage (with specified denominators), Column 3 reports undrawn facility amounts (for 3.2-3.5 only), and item 3.6 is the derived total of 3.1-3.5. The instrument warns on a concrete implementation risk: additions or extinguishments of facilities can generate implied principal flows and ADIs should take care to avoid creating such implied flows in Column 1.

• Collateral and margin flows (Item 4). Item 4 captures initial and variation margin paid and received over the prior five business days with a sign convention: outflows are positive, inflows negative. If systems cannot distinguish initial from variation margin, amounts should be reported as variation margin.

• LCR/MLH ratios over five business days (Item 5). Item 5 requires reporting of LCR (Liquidity Coverage Ratio) or MLH ratio across the last five business days. Items differentiate Level 1 and Level 2 reporting and AUD versus all currencies. Foreign ADIs report on a domestic books basis. MLH ADIs report zeros where a given item is LCR‑specific. Ratios must be reported as percentages to one decimal point.

• Funding maturities across the next six months (Item 6). Item 6 collects contractual maturities across ten maturity buckets and across funding types (retail, wholesale, FI, secured, unsecured, capital instruments). The instrument clarifies treatment of minimum notice deposits and term deposits with early break penalties. Certain capital instruments are to be reported in specific lines (e.g., Additional Tier 1 and Tier 2 in 6.6).

• Other contractual cash flows (Item 7). Item 7 captures contractual cash flows not reported in funding maturities, split into forecast contractual outflows and forecast contractual inflows with maturity buckets up to six months.

• Withdrawal notification and buyback requests (Item 8). Item 8 counts and values notices and requests over the last five business days, and reports the dollar amount as a percentage of the relevant five‑day average balance for each funding instrument. Items differentiate minimum notice deposit notices, short‑term wholesale early repayment requests and long‑term wholesale early repayment requests, and whether those requests were approved.

Across the form, the instrument uses a consistent approach: a combination of reported balances at reporting date and five business days prior, derived differences in dollars and percentages, and derived sums. The instrument repeatedly distinguishes between LCR ADIs and non‑LCR (MLH) ADIs and between domestic and offshore components. It also imposes explicit classification rules for repos and capital instruments, and ties several definitions back to APS 210 and ARF reporting forms.

The text is addressed to ADIs (authorised deposit‑taking institutions). It uses several sub‑classifications of ADIs that determine specific treatments or whether a line is zero:

• LCR ADIs: Lines and classifications that reference the Liquidity Coverage Ratio apply to these ADIs. The instrument instructs LCR ADIs to report HQLA categories (Item 1.1) consistent with APS 210 Attachment A and ARF 210.1A, and to report RBNZ eligible securities and other APRA‑approved securities in Item 1.4 where applicable.

• Non‑LCR ADIs (MLH ADIs): These ADIs use the Minimum Liquidity Holdings (MLH) framework. Items that are LCR‑specific instruct MLH ADIs to report zero, and other items require MLH ADIs to report MLH asset amounts consistent with ARF 210.2 and ARF 210.3.1. The instrument allows MLH ADIs to report gross amounts where their systems cannot calculate margins (except for item 1.3), but requires consistency in adjustments between ARF 210.2 and ARF 210.5.

• Foreign ADIs: For several items the instrument requires foreign ADIs to report "on a domestic books basis" (Item 5.1 and 5.2). The instrument also notes that for foreign ADIs, funding from any part of the same legal entity (head office or another branch) is entered into the same FI items, and instructs foreign ADIs to report zero in some LCR‑specific items (for example Item 5.3 and 5.4 for foreign ADIs).

• Entities transacting with ADIs: The instrument affects depositors, wholesale counterparties and financial institutions indirectly because their balances, notices and requests are captured across the form. For example, retail deposit balances, wholesale deposits (both short and long term), financial institution deposits, repos, securitisation, covered bonds and capital instruments (Additional Tier 1, Tier 2) are all reportable by the ADI.

• Supervisory and market infrastructure bodies referenced: APRA is the approving authority for certain securities and definitions in APS 210 and ARF forms; the RBA is referenced for settlement funds and margins on RBA‑eligible securities; the RBNZ and "offshore jurisdiction ALA" are referenced in Item 1.4 for eligible securities.

Who pays and who decides: The ADI bears the reporting burden and must make classification and measurement decisions required by the instrument. APRA (by naming ARF and APS instruments) is the supervising or defining authority for taxable classifications and approvals referenced in the instrument. The instrument itself is prescriptive about ADI internal decisions that must be made to produce consistent reports, such as margin adjustments and treatment of maturity/notice products.

The instrument imposes specific reporting duties on ADIs; it does not set out rights. Key duties are:

• Capture and report balances at two time points and derived changes. For Items 1 and 2 the ADI must report balances at the reporting date and five business days prior, and allow the reporting system to derive dollar and percentage changes in Columns 3 and 4 (Item 1 columns; Item 2 columns). For Item 3, Column 1 is the dollar outflow over the last five business days and Column 2 the percentage with specified denominators, and Column 3 for items 3.2-3.5 reports undrawn capacity as at the reporting date (Item 3 instructions).

• Classify assets and liabilities according to prescribed sub‑items. Examples: Item 1.1 requires reporting of HQLA as defined in APS 210 Attachment A and ARF 210.1A; Item 1.3 requires reporting of RBA eligible securities from self‑securitisation after applicable RBA margins; Item 2.5 requires that all repos be reported in item 2.5 regardless of tenor; Items 6.4-6.6 prescribe where unsecured and secured funding and capital instruments should be reported.

• Apply sign and direction conventions. The instrument sets explicit conventions: report outflows as positive numbers and inflows as negative numbers for Item 4 and Item 7, and for some other items the instrument clarifies that loan disbursements are entered as positive numbers and repayments as negative numbers in Item 3.1.

• Use specific denominators for percentage calculations. Item 3 instructs that percentage Column 2 uses denominators specified per subitem: for item 3.1 the denominator is outstanding principal balance five business days prior, for items 3.2-3.5 the denominator is total facility sizes (drawn and undrawn) five business days prior. Item 5 requires ratios reported to one decimal point.

• Report derived totals and offshore breakdowns. Several items are defined as derived sums that the ADI must calculate (items 1.6, 1.6.1, 2.6, 2.6.1, 3.6, 6.7, 6.7.1, 7). Where specified, the offshore portion must be separately reported (for example items 1.6.1, 2.6.1, 6.7.1).

• Follow special maturity and notice rules. For funding maturities (Item 6) minimum notice deposits without penalty are reported according to notice period; minimum term deposits with penalty are reported by expected contractual maturity.

• Ensure internal consistency across ARF forms and APS attachments. The instrument requires that where margins are adjusted, adjustments should be consistent in ARF 210.2 and ARF 210.5.

• Exercise caution to avoid artefacts. The instrument explicitly warns ADIs that Column 3 of Item 3 includes remaining undrawn capacity regardless of additions or subtractions in the previous five business days and that ADIs should take care that implied principal inflows or outflows are not generated in Column 1 due to facility changes.

Rights or permissive exceptions in the text are very limited but concrete:

• Margin calculation exception for MLH ADIs. Where MLH ADI systems do not allow margin calculations, the MLH ADI may report gross amounts except for item 1.3 (Item 1 instructions). This creates a limited, instrument‑level tolerance that recognises legacy system constraints.

The instrument does not state enforcement or appeal rights, nor remedial rights for reporting parties or third parties. It is solely focused on data elements and calculation rules.

The text supplied does not contain any penalty provisions, sanctions, stipulated supervisory actions or explicit enforcement mechanisms. The instrument is a technical reporting instruction; it prescribes the forms and calculations but does not, within this text, define the consequence for non‑compliance, nor identify inspection, audit, or penalty powers.

Because the instrument cross‑references ARF reporting forms and APS 210 and APG 210, practical enforcement and supervisory consequences may exist in the broader APRA regulatory framework; however those provisions are not included in the supplied text and therefore cannot be asserted from this source. The instrument itself provides operational guidance and specific instructions intended to produce consistent, comparable data (for example, requiring consistency in margin adjustments across ARF 210.2 and ARF 210.5). The absence of expressed penalties in the instrument means that, on its face, the text places a compliance design and operational burden on ADIs without specifying the sanctioning provisions in this document.

From a compliance risk perspective, the lack of penalty text within the instrument creates two concrete implementation implications drawn from the instrument itself: (a) ADIs must still implement the technical reporting constructs (derived items, five‑day comparators, classification rules), and (b) ADIs cannot rely on this instrument for a statement of regulatory consequences; they must map these reporting duties into their broader regulatory obligations under the APRA framework and any statutory reporting regime that gives APRA enforcement powers. This mapping is outside the instrument and is not described in the text supplied.

The instrument explicitly cross‑references prudential and reporting instruments and certain market counterparties, which creates direct operational interactions that ADIs must manage:

• APS 210 (Attachment A and Attachment B) and APG 210: Item 1.1 ties HQLA to APS 210 paragraphs 9 and 10 and aligns reporting to ARF 210.1A. Item 1.5 for non‑LCR ADIs references Attachment B of APS 210 for other MLH assets. Item 2.1 instructs that retail deposits be treated under APS 210 and APG 210. These cross‑references bind the definitions and eligible asset classifications in APS 210 and APG 210 into the reporting instrument. In practice, the instrument requires ADIs to ensure that the same asset definitions used for prudential calculations are used to populate the reporting fields.

• ARF Reporting Forms: Multiple items mandate consistency with ARF forms. Item 1.1 refers to ARF 210.1A; items for MLH ADIs refer to ARF 210.2 and ARF 210.3.1; the instrument requires margin adjustments to be consistent in ARF 210.2 and ARF 210.5. These linkages mean the present instrument must be implemented in IT and control environments that reconcile the content of ARF 210‑series submissions to the values reported here.

• RBA margins and RBA‑eligible securities: Item 1.3 requires reporting RBA eligible securities from self‑securitisation after applicable RBA margins. The instrument therefore interacts operationally with the Reserve Bank of Australia’s margining and eligibility rules. It does not, in the supplied text, reproduce RBA rules; it requires ADIs to apply them.

• RBNZ and offshore ALAs: Item 1.4 permits LCR ADIs to include RBNZ eligible securities and offshore jurisdiction ALA and "other securities approved by APRA." That creates a reporting interface to foreign central bank operational facilities and APRA approval processes.

• Internal capital definitions and market instruments: The instrument prescribes where capital instruments are reported (for example Additional Tier 1 and Tier 2 in item 2.5 and 6.6). This interacts with capital standards and instruments classifications set out elsewhere in prudential rules. The instrument does not itself define the capital instruments; it requires ADIs to map their capital structure into the designated reporting buckets.

• Domestic books basis for foreign ADIs: The instrument instructs foreign ADIs to report some ratios on a domestic books basis (Item 5). This creates an interaction with group accounting, branch accounting and internal transfer pricing and may require re‑aggregation of positions into a domestic view that aligns with prudential supervision.

The instrument makes clear that definitions and eligibility are not self‑contained. Implementation requires ADIs to reconcile rules and eligibility lists from APS 210 and ARF forms and to apply operational conventions from the RBA where applicable. The supplied text does not state how conflicts between instruments are to be resolved; it only instructs ADIs to follow the referenced APS and ARF definitions.

The supplied instrument contains no explicit amendment history. There are no version stamps, dates of effect, repeal or amendment notes, transitional provisions, or prior versions included in the text. The form references other instruments (APS 210, ARF 210 series, APG 210) but does not narrate its own amendment chronology. Consequently, based solely on the supplied material, there is no record here of prior changes, temporal sequencing, or transitional arrangements.

For practitioners, the absence of an amendment history in the text has practical consequences: when implementing these reporting requirements, do not assume this document is the latest or that its cross‑references are unchanged; verify current versions of APS 210, ARF 210.x and APG 210 and check for any updated instrument versions or APRA guidance that might alter the item mapping, definitions or calculation rules. That verification is outside the scope of the provided text; the instrument itself gives no timeline or historical trace.

The provided instrument contains no litigation history and does not reference any cases, adjudications or interpretative rulings. There are no judicial or tribunal decisions cited, and no administrative appeals mechanisms are described in the text. Therefore, within the confines of this source, there is no reported litigation or case law that interprets, challenges or enforces the provisions of these reporting instructions.

Practically, this absence means that interpretive disputes about classification, margin treatment or the proper construction of derived items would need to be resolved by reference to APRA guidance, the cross‑referenced APS and ARF materials, or by informal engagement with APRA. None of those avenues or any past rulings are described in the instrument itself.

The instrument contains several embedded operational and measurement pitfalls that will commonly cause errors if not addressed deliberately:

• Margin calculation exception and inconsistency risk (Item 1). MLH ADIs whose systems cannot compute margins may report gross amounts for most of Item 1, but item 1.3 is an exception and must be reported net of applicable RBA margins. The instrument requires consistency in margins adjustments across ARF 210.2 and ARF 210.5. Consequence: unless systems and reconciliations are built to ensure the same gross/net treatment across these ARF forms and this instrument, an ADI may produce inconsistent submissions.

• Repos always in item 2.5. The instrument requires that all repo transactions, including repos with the RBA or related entities, be reported in item 2.5 regardless of tenor. Failure to map repo positions into item 2.5 will mis‑state short‑term wholesale funding (item 2.4) and other funding lines.

• Capital instruments placement. The instrument requires Additional Tier 1 and Tier 2 instruments to be reported in item 2.5 and in funding maturities item 6.6, while Common Equity Tier 1 should not be reported in item 2.5. Misclassification of capital instruments between capital and funding buckets will distort derived totals and LCR/MLH calculations.

• Five‑business‑day comparators and derived item sensitivity. Several items require balances at the reporting date and five business days prior (Items 1 and 2). Derived columns calculate changes in dollars and percentages. Systems must take exact five business‑day snapshots and handle public holidays and non‑business days consistently. Small timing mismatches will generate artificial volatility.

• Different column semantics across items. Column meanings vary across Items. For example, in Items 1 and 2 Column 3 is the dollar change derived between reporting date and five business days prior, while in Item 3 Column 3 is undrawn facility amounts as at the reporting date, and for Item 3 Column 1 is the five‑day dollar outflow. Treating columns as uniform across the form is a frequent implementation error. The instrument’s warnings about implied inflows/outflows (Item 3) underline this risk.

• Implied principal flows from facility changes (Item 3). The instrument explicitly warns that additions or extinguishments of facilities can create implied principal inflows or outflows in Column 1 if the undrawn capacity in Column 3 is not treated consistently with the five‑day comparator. If systems simply take current undrawn capacity without reconciling to the five‑day prior balances, reported net principal outflows may be distorted.

• Sign conventions for flows. Item 4 and Item 7 explicitly require outflows as positive and inflows as negative. Item 3.1 requires loan disbursements (principal outflows) to be positive and repayments negative. Inconsistent sign conventions across feeds or spreadsheets will produce arithmetic errors and misleading derived totals.

• Minimum notice versus contractual maturity (Item 6). Minimum notice deposits without penalty should be reported according to the notice period rather than contractual maturity. Minimum term deposits with early break penalties are to be reported by expected contractual maturity. Misinterpreting these rules can shift amounts across maturity buckets, changing short‑term funding profiles.

• Offshore reporting and domestic books basis. Many lines require offshore components to be reported separately (for example items 1.6.1, 2.6.1, 6.7.1). Foreign ADIs are instructed to report some items on a domestic books basis (Item 5). ADIs that operate globally must ensure consistent definitions of "offshore" and of "domestic books" as applied in other prudential submissions, or risk mismatches.

• Level 1/Level 2 LCR differences and zeroing for non‑applicables. Item 5 separates Level 1 and Level 2 LCR reporting and instructs MLH ADIs and some foreign ADIs to report zero in particular fields. Automatic population of zeros without explicit logic may hide dataset inconsistencies.

• Derived totals and rounding/decimal conventions. Ratios must be reported to one decimal point in Item 5; percent columns in Item 3 must use denominators specified by the instrument. Implementations must apply consistent rounding rules to avoid reconciliation breaks between reported ratio fields and the raw balances.

• Withdrawal notifications and percentage denominators (Item 8). Column 3 requires the percentage amount to be reported as a percentage of the average balance over the last five business days for each funding instrument. Failure to compute the average balance correctly, or to align the denominator with the instrument type, will misstate the relative scale of notifications and requests.

• Non‑distinction of initial and variation margin (Item 4). If an ADI cannot distinguish between initial and variation margin, the instrument instructs to report the whole amount as variation margin. That creates a potential comparability caveat if other ADIs can split margins; analysts should not assume uniformity.

These are concrete mechanical "gotchas" that the instrument itself identifies or implies by its structure. They primarily raise control, system design and reconciliation risks.

This section outlines a practical compliance checklist and controls framework tied to the instrument’s specific requirements. All steps below are grounded in the instrument’s instructions and are intended to produce consistent submissions.

1. Governance, roles and documentation

• Appoint a reporting owner responsible for this form and for ensuring consistency with ARF 210 series and APS 210 definitions referenced in the instrument (Items 1.1, 1.5, and cross‑references).
• Document authoritative data mappings: ledger accounts to report lines, product taxonomies, counterparty types (retail, wholesale, FI), and jurisdiction flags (offshore/domestic).
• Maintain a change control register for any mapping or system changes that affect five‑day snapshot logic, margin calculations, repo classification, and maturity bucketing.

2. Data mapping and classification

• Map HQLA, MLH and other categories to Item 1 sub‑items using APS 210 Attachment A and B definitions and ARF 210.1A/ARF 210.2 mappings (Item 1.1 and Item 1.5 references).
• Ensure repo transactions are always mapped to item 2.5 irrespective of tenor (Item 2.5).
• Map Additional Tier 1 and Tier 2 to item 2.5 and funding maturity item 6.6; ensure Common Equity Tier 1 is excluded from item 2.5 (Item 2.5 and Item 6 guidance).
• Define "offshore" flags and ensure offshore amounts are separately reported in items with .1 suffix (e.g., 1.6.1, 2.6.1, 6.7.1).

3. Time series and snapshot logic

• Implement a robust five business day prior snapshot process for Items 1 and 2 and other areas that require five‑day comparisons. Ensure consistent business day calendars and holiday handling.
• For Item 3, record both the five‑day prior drawn balances and total facility sizes (drawn plus undrawn) five business days prior; Column 3 of items 3.2-3.5 must be current remaining undrawn capacity as at the reporting date. Put controls in place that reconcile Column 1 to actual cash movements to avoid implied flows from facility changes (Item 3 warning).

4. Margin treatment

• Implement margin calculation engines for margins where required. If MLH ADI systems cannot compute margins, use the permitted gross reporting approach except for item 1.3 which must be net of RBA margins (Item 1 instructions). Record a documented rationale for any gross reporting permitted by the instrument and reconcile with ARF 210.2 and ARF 210.5 as required.

5. Sign conventions and flow directions

• Standardise sign conventions across feeds: for Item 4 and Item 7 outflows are positive and inflows negative; for Item 3.1 disbursements are positive and repayments negative. Put validation rules in place to flag inconsistent signs at ingestion.

6. Derived item computations

• Implement derived item calculations exactly as specified: item 1.6 as sum of 1.1-1.5, item 2.6 as sum of 2.1-2.5, item 3.6 as sum of 3.1-3.5, item 6.7 as sum of 6.1-6.6, item 7 as sum of 7.1 and 7.2, and offshore subtotals where required. Define rounding rules for percentage computations to one decimal point for Item 5 and decimal conventions for percentage columns in Item 3.

7. Maturity and notice handling

• For Item 6, build logic to allocate minimum notice deposit products: if there is no penalty for early withdrawal, classify by the notice period bucket; if there is a penalty or fee, class by expected contractual maturity. For term deposit modelling, create early break models to determine expected contractual maturity.

8. Percentage denominators and ratios

• For Item 3 percentages, use the explicit denominators in the instrument: outstanding principal balance five business days prior for item 3.1; total facility sizes (drawn and undrawn) five business days prior for items 3.2-3.5. For Item 5 ratios, report to one decimal point; foreign ADIs should prepare a domestic books basis aggregation where instructed.

9. Collateral and margin reporting

• For Item 4, ensure systems can distinguish initial margin paid/received (4.1 and 4.2) and variation margin paid/received (4.3 and 4.4) where possible. If not possible, aggregate as variation margin per the instrument’s instruction.

10. Notifications and request reporting

• For Item 8, track counts and dollar values of minimum notice deposit notices, short‑term wholesale early repayment requests and long‑term wholesale early repayment requests over the last five business days. For Column 3 percentages, implement calculation of the average balance over the last five business days for the relevant funding instrument and validate denominators.

11. Reconciliation and controls

• Reconcile reported totals back to source systems and to ARF 210 series submissions where the instrument instructs consistency. Implement exception reporting for: large day‑over‑day changes, negative derived totals where unexpected, mismatches between sum of bucketed maturities and derived totals (for example item 6.7), and for any rounding differences in percentage reporting.

12. Audit trail and evidence

• Preserve data extracts for the reporting date and five business days prior, with timestamped snapshots, margin calculation inputs, and approvals for any gross reporting permitted for MLH ADIs. Maintain evidence of mapping decisions for capital instruments and repo classifications.

13. Testing and parallel runs

• Run parallel reporting cycles prior to go‑live to validate derived computations, rounding and denominator rules, and the interaction between facility changes and Column 1 calculations in Item 3. Validate the treatment of repos, RBA margins (item 1.3), and offshore flagging.

14. Engagement with regulator

• Where the instrument requires application of external definitions (APS 210, ARF 210.x) or recognition of APRA approvals (Item 1.4), maintain a point of contact to confirm eligibility of securities and any APRA‑approved exceptions.

15. Reporting error handling

• Design procedures for corrections and restatements consistent with the ADI’s overall reporting governance. Given the instrument does not prescribe a penalty regime, treat restatements as a governance and data quality matter and ensure corrections are documented and reconciled with ARF submissions.

Following these steps will align operational practices with the instrument’s explicit instructions. The instrument’s repeated cross‑references and derived item structure mean that robust system design, careful snapshot logic and tight reconciliations are the primary compliance levers.