NZ: Deposit Takers (Liquidity) Standard 2027
|
|
| Regulator |
RBNZ |
| Jurisdiction |
NZ |
| Status |
Draft — not yet in force |
| Applicability |
Platform |
RBNZ's liquidity standard under the Deposit Takers Act 2023, replacing BS13. It requires deposit
takers to hold sufficient high-quality liquid assets (HQLA) and maintain stable funding.
Implements LCR (30-day) and NSFR (1-year) metrics aligned with Basel III, plus a NZ-specific
Minimum Core Funding Ratio (MFCR). Locally incorporated banks are subject to all three metrics;
branches are subject to RBNZ-approved liquidity policies.
The standard is currently in force. Monthly reporting to RBNZ is required.
Compliance register
This register maps every material obligation under the standard to the platform control or
institutional process that satisfies it. It is the static traceability layer for the Totara
compliance report — dynamic data (module build status, test evidence, control test dates) is
overlaid at runtime.
Scope legend
| Symbol |
Meaning |
| 🤖 Automated |
Platform enforces or performs the obligation. Primary control mode is GATE, AUTO, CALC, or ALERT. Human action is not required in the normal case. |
| 📊 Evidenced |
Platform captures the evidence trail automatically. Human compliance decision sits on top. Primary control mode is LOG. |
| 🏛 Institutional |
Obligation is met by a process entirely outside the platform — board governance, treasury, legal. Platform may generate evidence inputs but does not own the process. |
| N/A |
Obligation does not apply to this deployment configuration. |
Build legend
| Symbol |
Meaning |
| ✅ |
Module built and deployed |
| 🔨 |
Module planned — not yet built (build_status: Not started) |
| ❌ |
Uncontrolled gap — no module attributed |
LCR, NSFR, and MFCR
| Ref |
Obligation |
Scope |
Policy |
Platform controls |
Build |
| LCR ≥ 100% |
Maintain Liquidity Coverage Ratio at or above 100% at all times — HQLA / net 30-day stress outflows |
🤖 Automated |
REP-001, REP-002, GOV-002 |
MOD-032 (CALC) — LCR calculated from real data continuously; no manual spreadsheet, no T+1 lag; MOD-032 (ALERT) — LCR breach of RAF threshold triggers automatic escalation; MOD-150 (CALC) — intraday payment system exposure computed from the payment event stream, extending MOD-032's end-of-day LCR to cover intraday positions |
🔨 |
| NSFR ≥ 100% |
Maintain Net Stable Funding Ratio at or above 100% — available stable funding / required stable funding over 1 year |
🤖 Automated |
REP-001, REP-002, GOV-002 |
MOD-032 (CALC) — NSFR calculated from real balance data continuously; regulatory returns sourced from the same calculation used for internal monitoring |
🔨 |
| MFCR ≥ 75% |
Maintain Minimum Core Funding Ratio at or above 75% — NZ-specific stable funding metric |
🤖 Automated |
REP-001, REP-002 |
MOD-032 (CALC) — MFCR calculated as part of the liquidity engine alongside LCR and NSFR; single calculation pipeline for all three metrics |
🔨 |
| Monthly reporting |
Report LCR, NSFR, and MFCR to RBNZ monthly |
🤖 Automated |
REP-001, REP-002 |
MOD-032 (CALC) — regulatory liquidity returns sourced from the same calculation used for internal monitoring; no separate data extraction or manual preparation required |
🔨 |
| Intraday liquidity |
Monitor and manage intraday liquidity positions; ensure settlement obligations can be met |
🤖 Automated |
REP-001, GOV-002 |
MOD-150 (CALC) — intraday payment system exposure computed in real time from the payment event stream; MOD-082 (CALC) — nostro balances at correspondent banks included in the liquidity position, covering all accessible liquidity pools |
🔨 |
Contingency funding and board governance
| Ref |
Obligation |
Scope |
Policy |
Platform controls |
Build |
| Contingency Funding Plan |
Maintain a board-approved Contingency Funding Plan; test at least annually |
🏛 Institutional |
REP-001 |
Board approval and annual testing of the CFP are institutional governance processes. MOD-032 provides the liquidity position data used in CFP scenario analysis; MOD-034 (stress scenario engine) models liquidity stress projections using LCR/NSFR as the base. |
— |
| Board liquidity risk appetite |
Document board-approved limits on liquidity risk metrics |
🏛 Institutional |
GOV-002 |
MOD-150 (CALC) — RAF dashboard computed continuously; LCR/NSFR breach of RAF threshold auto-alerts CRO and Board Risk Committee chair. RAF threshold values are configured in the platform; board approval of the RAS is institutional. |
— |
The following obligations under the standard are the responsibility of the institution, not the platform.
| Obligation |
Owner |
Platform evidence input |
| Board approval of Contingency Funding Plan |
Board / Chief Financial Officer |
MOD-032 and MOD-034 provide scenario data inputs for CFP document |
| ALCO oversight and liquidity limit governance |
ALCO / Board Risk Committee |
MOD-032 and MOD-150 provide the liquidity metrics and RAF alerts; committee governance is institutional |
| Annual CFP test execution |
Chief Financial Officer / Chief Risk Officer |
MOD-034 provides stress scenario outputs; exercise execution is institutional |
Coverage summary
| Area |
Total obligations |
Platform automated 🤖 |
Platform evidenced 📊 |
Institutional 🏛 |
N/A |
| LCR, NSFR, and MFCR |
5 |
5 |
0 |
0 |
0 |
| Contingency funding and board governance |
2 |
0 |
0 |
2 |
0 |
| Total |
7 |
5 (71%) |
0 (0%) |
2 (29%) |
0 |
Of the 5 platform obligations, all have attributed controls. All attributed modules are currently
build_status: Not started — the compliance position will update as modules are built and deployed.
| Policy |
Title |
| GOV-002 |
Risk Appetite Statement Policy |
| REP-001 |
Regulatory Reporting Policy |
| REP-002 |
Prudential Reporting Policy |
See D01 Capital & Liquidity for the full risk domain.
Official documentation
Policies referencing this standard
- REP-001 — Regulatory Reporting Policy
- REP-002 — Prudential Reporting Policy
Compiled 2026-05-22 from source/entities/regulations/nz-dta-liquidity.yaml