NZ: Depositor Compensation Scheme (DCS) Standard 2027¶


Regulator	RBNZ
Jurisdiction	NZ
Status	Draft — not yet in force
Applicability	Platform

The Depositor Compensation Scheme (DCS) Standard is one of the core standards issued under the Deposit Takers Act 2023. It requires deposit takers to maintain a Single Depositor View (SDV) — a system capability that aggregates each depositor's eligible deposits across all accounts in real time and supports a fast payout to covered depositors in a resolution event. The covered-deposit cap is NZD 100,000 per depositor per deposit taker.

RBNZ published final DCS policy decisions in May 2025. The standard takes effect 1 December 2028, alongside the other DTA core standards. A transitional DCS levy arrangement operates in the interim.

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

Single Depositor View (SDV)¶

Ref	Obligation	Scope	Policy	Platform controls	Build
SDV-1	Maintain a system capable of aggregating all eligible deposits per depositor across all accounts in real time	🤖 Automated	REP-007	MOD-142 (CALC) — the deposit guarantee scheme disclosure module calculates each customer's total protected deposit balance across all eligible accounts; MOD-125 (CALC) — joint account proportional share is calculated per holder and available for the SDV file	🔨
SDV-2	Apply the NZD 100,000 per-depositor compensation cap correctly in the SDV calculation	🤖 Automated	REP-007	MOD-142 (CALC) — covered and uncovered portions computed and displayed in-app; cap logic is configuration, not hardcoded, to support RBNZ-directed cap changes	🔨
SDV-3	Tag each deposit account with a depositor identifier consistent with SDV requirements	🤖 Automated	REP-007	MOD-142 (CALC) — eligible account flag and depositor identifier written at account opening; MOD-125 (CALC) — joint account holder proportional share persisted as `balance_share_pct` on each holder record	🔨
SDV-4	Extract and submit the SDV file to RBNZ within the required timeframe in a resolution or compensation event	🤖 Automated	REP-007, REP-001	MOD-036 (AUTO) — prudential return builder produces RBNZ-format SDV extract automatically; MOD-143 (LOG) — OBR activation events are logged as regulatory records for RBNZ examination	🔨
SDV-5	Participate in RBNZ-directed SDV readiness exercises and testing	🏛 Institutional	REP-007	RBNZ-directed testing is managed by the Chief Financial Officer and Head of Technology. MOD-036 provides the SDV extract capability that is exercised in testing; test outcomes are recorded institutionally.	—

Disclosure obligations¶

Ref	Obligation	Scope	Policy	Platform controls	Build
DCS-D1	Disclose DCS coverage eligibility to depositors at account opening and in periodic statements	🤖 Automated	REP-007, CON-005	MOD-142 (GATE) — DCS disclosure delivered and acknowledged at account opening before the account activates; coverage statement included in every account statement	🔨
DCS-D2	Disclose the NZD 100,000 per-depositor cap and which accounts are eligible	🤖 Automated	REP-007	MOD-142 (CALC) — covered amount and eligible account flags displayed in-app, updated in real time as balances change	🔨

Levy and reporting¶

Ref	Obligation	Scope	Policy	Platform controls	Build
DCS-L1	Report covered-deposit balances to RBNZ for DCS levy assessment on the prescribed schedule	🤖 Automated	REP-007, REP-001	MOD-036 (AUTO) — regulatory returns builder produces covered-deposit reporting automatically from the SDV data	🔨
DCS-L2	DCS levy calculation and payment to RBNZ	🏛 Institutional	REP-007	Levy calculation is an RBNZ-administered process. The platform provides the covered-deposit balance data that feeds the levy base. Finance (CFO) owns the levy payment obligation.	—

Institutional obligations (not platform scope)¶

Obligation	Owner	Platform evidence input
DCS levy payment to RBNZ	Chief Financial Officer	MOD-036 provides the covered-deposit reporting data that forms the levy base
RBNZ-directed SDV readiness testing	Chief Financial Officer / Head of Technology	MOD-036 SDV extract capability exercised in testing; MOD-143 OBR logs provide supporting evidence
Board oversight of DCS compliance programme	Board / CEO	MOD-150 risk dashboard provides compliance programme visibility
Maintaining depositor identification data in a form compatible with the DCS payout process	Chief Technology Officer	MOD-142 and MOD-125 generate the SDV-compatible identifiers; data architecture governance is institutional

Coverage summary¶

Area	Total obligations	Platform automated 🤖	Platform evidenced 📊	Institutional 🏛	N/A
Single Depositor View	5	4	0	1	0
Disclosure	2	2	0	0	0
Levy and reporting	2	1	0	1	0
Total	9	7 (78%)	0 (0%)	2 (22%)	0 (0%)

All attributed modules are currently build_status: Not started — the compliance position will update as modules are built and deployed.

Policy	Title
REP-007	DCS & Depositor Reporting Policy
REP-001	Regulatory Reporting Policy

Official documentation¶

Policies referencing this standard¶

REP-001 — Regulatory Reporting Policy
REP-007 — DCS & Depositor Reporting Policy

Compiled 2026-05-22 from source/entities/regulations/nz-dta-dcs.yaml