NZ: Deposit Takers (Disclosure) Standard 2027
|
|
| Regulator |
RBNZ |
| Jurisdiction |
NZ |
| Status |
Draft — not yet in force |
| Applicability |
Platform |
DRAFT — under RBNZ consultation. Expected finalisation 2026–2027.
The DTA Disclosure Standard is issued under the Deposit Takers Act 2023. It prescribes
the format and content of the Key Information Summary (KIS) — a standardised pre-sale
disclosure document that deposit takers must deliver to customers before opening a
deposit product. The KIS replaces the previous BS33 disclosure format and is designed
to enable informed comparison across deposit takers.
Key KIS content requirements (proposed): product name and type, interest rate and
basis (variable/fixed), key fees, minimum and maximum balance conditions, access
restrictions and notice periods, DCS coverage eligibility, and the complaints pathway.
The KIS must be delivered before account opening. When a material change occurs, an
updated KIS must be delivered within 30 days.
The standard also prescribes the format for quarterly prudential disclosure statements
covering capital adequacy, credit quality, liquidity, and risk management — aligning
with Basel III Pillar 3 requirements as implemented in Australia under APS 330.
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, product, 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 |
| Ref |
Obligation |
Scope |
Policy |
Platform controls |
Build |
| KIS-1 |
Generate KIS in the RBNZ-prescribed format from live product configuration before account opening |
🤖 Automated |
CON-009 |
MOD-050 (AUTO) — KIS generated automatically from product config in RBNZ-prescribed format; product configuration is the single source of truth for all KIS content fields |
🔨 |
| KIS-2 |
Deposit account cannot activate without KIS delivery and customer acknowledgement |
🤖 Automated |
CON-009 |
MOD-050 (GATE) — account cannot activate without KIS acknowledgement on record; acknowledgement is recorded with timestamp and KIS version; no bypass path exists |
🔨 |
| KIS-3 |
KIS must include: product name/type, interest rate and basis, key fees, min/max balance, access restrictions, DCS eligibility, complaints pathway |
🤖 Automated |
CON-009 |
MOD-050 (AUTO) — all required fields populated from product config; missing mandatory fields fail KIS generation validation; DCS eligibility populated from MOD-142 |
🔨 |
| KIS-4 |
Updated KIS delivered to affected customers within 30 days of a material product change |
🤖 Automated |
CON-009, REP-001 |
MOD-050 (AUTO) — product config change triggers automatic re-generation of KIS and queues delivery to affected customers; material change flag is set by the product team in the product config system |
🔨 |
| KIS-5 |
KIS version and acknowledgement timestamp retained as a regulatory record |
📊 Evidenced |
CON-009 |
MOD-050 (LOG) — every KIS acknowledgement event is written as an immutable record with the KIS version, content hash, customer ID, and acknowledgement timestamp |
🔨 |
Prudential disclosure statements
| Ref |
Obligation |
Scope |
Policy |
Platform controls |
Build |
| PDS-1 |
Publish quarterly prudential disclosure statement within 30 days of period end |
🤖 Automated |
REP-002, CLQ-006 |
MOD-036 (AUTO) — prudential return builder produces disclosure statement data automatically on schedule; MOD-033 (CALC) — capital ratios sourced from the RWA engine |
🔨 |
| PDS-2 |
Disclose capital ratios (CET1, Tier 1, Total Capital, RWA by risk type) |
🤖 Automated |
CLQ-006, REP-002 |
MOD-033 (CALC) — Pillar 3 disclosure figures sourced from the same RWA engine as internal monitoring — no reconciliation gap; MOD-036 (AUTO) — return builder populates the prescribed template |
🔨 |
| PDS-3 |
Disclose liquidity ratios (LCR, NSFR) |
🤖 Automated |
REP-002 |
MOD-032 (CALC) — LCR and NSFR calculated from real data continuously and sourced into the quarterly disclosure; MOD-036 (AUTO) — liquidity figures included in return |
🔨 |
| PDS-4 |
Disclose credit quality (loan portfolio classification, impaired assets, provisions) |
🤖 Automated |
REP-002 |
MOD-036 (AUTO) — credit quality data sourced from the reporting layer; MOD-031 (LOG) — ECL model provision entries in GL sourced from validated model |
🔨 |
| PDS-5 |
Disclose material risk exposures and risk management approach |
🏛 Institutional |
REP-002 |
Qualitative risk narrative is drafted by the Chief Risk Officer. MOD-150 (CALC) provides the risk appetite dashboard and quantitative risk data inputs; MOD-036 (AUTO) assembles the quantitative portions. |
— |
| Obligation |
Owner |
Platform evidence input |
| KIS template design and approval (pending standard finalisation) |
Chief Compliance Officer / Product |
MOD-050 implements the approved template once finalised |
| Material change determination for KIS update trigger |
Product team |
MOD-050 queues re-delivery once the material change flag is set in product config |
| Board approval of prudential disclosure statements |
Board / CFO |
MOD-036 provides the data; board sign-off is an institutional governance process |
| Regulatory examination responses on disclosure adequacy |
Chief Compliance Officer |
MOD-050 KIS acknowledgement logs and MOD-036 return history provide examination evidence |
Coverage summary
| Area |
Total obligations |
Platform automated 🤖 |
Platform evidenced 📊 |
Institutional 🏛 |
N/A |
| Key Information Summary |
5 |
4 |
1 |
0 |
0 |
| Prudential disclosure |
5 |
4 |
0 |
1 |
0 |
| Total |
10 |
8 (80%) |
1 (10%) |
1 (10%) |
0 (0%) |
All attributed modules are currently build_status: Not started — the compliance position
will update as modules are built and deployed. Controls are designed against the proposed
standard and are contingent on finalisation.
| Policy |
Title |
| CON-009 |
NZ DTA Key Information Summary Disclosure Policy |
| REP-001 |
Regulatory Reporting Policy |
| REP-002 |
Prudential Reporting Policy |
| CLQ-006 |
Capital Disclosure & Reporting Policy |
Official documentation
Policies referencing this standard
- CLQ-006 — Capital Disclosure & Reporting Policy
- CON-009 — NZ DTA Key Information Summary Disclosure Policy
- REP-001 — Regulatory Reporting Policy
- REP-002 — Prudential Reporting Policy
Compiled 2026-05-22 from source/entities/regulations/nz-dta-disclosure.yaml