In 2026, APRA requires Australian banks to comply with liquidity standards set out under Prudential Standard APS 210, which mandates minimum Liquidity Coverage Ratio (LCR) and Net Stable Funding Ratio (NSFR) thresholds, along with ongoing stress testing and internal liquidity monitoring obligations. Larger, more complex banks must maintain an LCR of at least 100% and an NSFR of at least 100%, while smaller banks operate under a simplified Minimum Liquidity Holdings (MLH) regime. Below, we unpack each of the key questions Australian banks are asking about APRA liquidity compliance right now.
What specific liquidity ratios does APRA require Australian banks to maintain?
Under APS 210, Australian banks classified as Liquidity Coverage Ratio (LCR) institutions must maintain an LCR of at least 100% and a Net Stable Funding Ratio (NSFR) of at least 100% at all times. The LCR measures whether a bank holds enough High Quality Liquid Assets (HQLA) to survive a 30-day stress scenario. The NSFR measures whether a bank’s long-term funding structure is stable enough to support its assets over a one-year horizon.
Banks that do not meet the LCR institution threshold fall under the MLH regime instead. MLH banks must hold a minimum percentage of their liabilities in liquid assets, but the specific composition and reporting requirements are simpler than those applied to LCR banks.
For LCR institutions, APRA also requires daily monitoring and reporting of the LCR, not just end-of-month snapshots. This means liquidity data needs to be available quickly, accurately, and consistently, which puts real pressure on the quality and speed of underlying data systems.
How does APRA’s liquidity framework differ from Basel III standards?
APRA’s liquidity framework is based on the Basel.NXT international standards but applies a stricter, more locally tailored version. The most notable difference is that APRA does not allow Australian banks to rely on the Committed Liquidity Facility (CLF) to meet their LCR requirements from 1 Jan 2023, a facility that was introduced because Australia historically had a limited supply of government securities qualifying as HQLA. This phaseout was confirmed by APRA in its final policy position published in December 2021, with the CLF reduced to zero for all LCR banks effective 1 January 2023.1 As of 2026, Australian banks must hold genuine HQLA to meet their LCR buffer.
APRA also applies more conservative assumptions in several areas compared to the Basel.NXT baseline. For example, APRA’s stress scenario assumptions around retail deposit outflow rates and the treatment of certain off-balance-sheet exposures are calibrated to Australian market conditions rather than simply adopted from the Basel Committee’s default parameters.
The NSFR treatment under APS 210 also reflects APRA-specific adjustments to the Available Stable Funding (ASF) and Required Stable Funding (RSF) factors for certain asset and liability categories. Banks operating in Australia cannot simply map their Basel.NXT NSFR model directly to APS 210 without reviewing these local calibrations carefully.
In short, APS 210 uses Basel.NXT as its foundation but layers on Australian-specific requirements that make direct comparison or copy-paste compliance from international frameworks unreliable.
What reporting and stress testing obligations apply under APS 210 in 2026?
Under APS 210 in 2026, LCR institutions must report their LCR to APRA daily, while the NSFR is reported monthly. Banks are also required to submit regular reports on their internal liquidity positions, including intraday liquidity monitoring for systemically important institutions. Stress testing is not optional, it is a formal obligation embedded in the standard.
APRA expects banks to run liquidity stress tests that cover at least three scenarios: an institution-specific stress event, a market-wide stress event, and a combination of both. These scenarios must be sufficiently severe and plausible, and the results must inform the bank’s Internal Liquidity Adequacy Assessment Process (ILAAP).
The ILAAP is a core deliverable under APS 210. It requires banks to document their liquidity risk appetite, demonstrate that their liquidity buffer is adequate under stress, and show that management has a credible plan for restoring liquidity in a crisis. APRA reviews ILAAP submissions and uses them to assess whether a bank’s self-assessment is realistic and robust.
Banks must also maintain a Contingency Funding Plan (CFP) that is regularly tested and updated. The CFP needs to identify early warning indicators, escalation triggers, and specific funding actions the bank would take under stress. APRA expects this to be a living document, not a static compliance artifact.
Which Australian banks are most affected by APRA’s 2026 liquidity rules?
The most affected institutions are those classified as LCR banks, which generally include the major banks (ANZ, CBA, NAB, Westpac), the large regional banks, and any bank with a more complex funding profile or significant wholesale funding dependence. These banks face the full weight of daily LCR reporting, NSFR compliance, ILAAP obligations, and intraday liquidity monitoring.
Smaller banks and credit unions operating under the MLH regime face a lighter set of obligations, but they are not exempt from APRA’s broader expectations around sound liquidity risk management and contingency planning.
Foreign bank branches operating in Australia are subject to their own liquidity requirements under APS 210, which differ from those applied to locally incorporated banks. APRA applies a risk-based approach to foreign branches, taking into account the liquidity arrangements of the parent institution and the degree of operational independence of the Australian branch.
Banks with significant exposure to institutional or corporate deposits, heavy reliance on short-term wholesale funding, or large off-balance-sheet commitments tend to face the greatest compliance complexity, because these factors create more volatile LCR and NSFR positions that require more frequent recalculation and closer monitoring.
What are the biggest compliance challenges Australian banks face in meeting APRA liquidity rules?
The biggest compliance challenges under APS 210 in 2026 fall into three broad areas: data quality, calculation speed, and scenario coverage. Banks that still rely on overnight batch processing for liquidity calculations struggle to produce the daily LCR figures APRA requires with enough accuracy and granularity to be genuinely useful for risk management, rather than just a reporting exercise.
Data quality and granularity
APS 210 requires banks to classify assets and liabilities at a contract level, applying the correct HQLA haircuts, outflow rates, and ASF/RSF factors to each position. This demands clean, well-structured source data that maps correctly to APRA’s classification rules. Banks with fragmented data environments, inconsistent product definitions, or manual data transformation steps find this particularly difficult to maintain at the required frequency.
Basel
Pre-configured Basel models, out-of-the-box regulatory scenarios, and liquidity metrics.
Ready in weeks, not months.
Scenario coverage and ILAAP depth
Running multiple stress scenarios across a full balance sheet, and doing so frequently enough to support both daily management decisions and periodic ILAAP submissions, is operationally demanding. Many banks find that their legacy systems were designed for end-of-month reporting, not the kind of continuous, scenario-rich liquidity analysis APRA now expects. Closing that gap without rebuilding the entire technology stack is one of the most common pain points banks raise in 2026.
How can banks run liquidity stress tests faster and more accurately?
Banks can run liquidity stress tests faster and more accurately by moving away from batch-based calculation engines toward real-time, scenario-driven platforms that process contract-level data in minutes rather than hours. The practical steps involve consolidating liquidity data into a single, well-governed source, automating HQLA classification and outflow rate application, and building scenario libraries that can be rerun quickly when assumptions change.
Behavioral modeling is particularly important for liquidity stress testing. Deposit runoff rates, drawdown assumptions on credit facilities, and the stability of wholesale funding all depend on behavioral assumptions that vary by product, customer segment, and stress severity. Banks that hard-code these assumptions into spreadsheets or legacy systems find it slow and error-prone to update them when APRA guidance changes or when internal risk appetite shifts.
A more flexible approach uses a configurable scenario framework where behavioral parameters are defined in the system itself, not in code. This lets risk teams adjust assumptions, rerun calculations, and see the impact on LCR and NSFR positions immediately, without involving IT or waiting for an overnight batch to complete.
Intraday liquidity monitoring adds another layer of complexity. Banks that need to track intraday positions must process transaction-level data in near real-time, which requires an architecture built for streaming data rather than periodic snapshots.
At ElysianNxt, our liquidity risk solution covers LCR, NSFR, intraday and daily liquidity monitoring, and internal ratios, all within the same platform that handles your broader Basel.NXT compliance. LCR results include out-of-the-box HQLA definitions, automatic cap application, and drill-down to individual contract contributions, so you can see exactly what is driving your ratio at any point in time. The liquidity module is designed to go live in weeks, with daily results available in minutes, which means your team spends less time waiting for numbers and more time acting on them.
Related Articles
- How long does it realistically take to implement a Basel IV compliance platform?
- What is APS 210 and how should ADIs approach liquidity compliance?
- 5 things to look for in a modern Basel IV technology platform
- Why do banks struggle with regulatory reporting deadlines?
- Integrated Credit Risk vs Traditional: Which Wins?
This content was generated with the help of AI and it may contain mistakes