Skip to content
DivizendDivizend
Loading saved progress.
Back to MiKaDiv overview

Readiness instrument

MiKaDiv Readiness Checklist

10 questions every bank, broker, custodian, and intermediary must answer before 2027.

Use this checklist in executive readiness reviews, steering committees, and operating-model workshops. Progress saves locally in your browser—nothing is transmitted until you choose to engage Divizend.

Book a MiKaDiv Readiness SessionJump to first open question

How to use this checklist

  1. Assign a single accountable owner per question (name them in notes).
  2. Mark each criterion only when you can point to evidence—not intent.
  3. Select a maturity level that would survive scrutiny from Tax, Operations, and Internal Audit.
  4. Escalate any question at At risk or Not started after Q2 2026.

Legal disclaimer: This checklist is operational guidance, not legal advice. Confirm obligations with qualified counsel and applicable regulatory guidance.

Board, General Counsel, Tax, Operations

Have you defined your MiKaDiv role—and every obligation that follows?

Mis-scoped programs build the wrong controls, contracts, and systems.

MiKaDiv obligations differ materially for German custodian banks, paying agents, foreign certified financial intermediaries (CFIs), and intermediaries in the chain. A single institution may hold multiple roles across products and legal entities. Readiness starts with a defensible role map—not a reporting workstream label.

Evidence criteria

Red flags

  • “Reporting project” with no General Counsel or Operations executive sponsor.
  • Scope limited to XML without a custody-chain operating model.
Maturity assessment

Program Management, Tax Operations, Product

Is your 2027 cutover plan tied to income events—not project milestones?

The law keys off income received after 31 December 2026—not your go-live party.

From 1 January 2027, MiKaDiv applies to income received after 31 December 2026. Programs that optimize for a software release date without modeling dividend calendars, record dates, and exception paths will miss the first production failure mode: the first in-scope payment.

Evidence criteria

Red flags

  • No named “first production event” before Q3 2026.
  • Testing ends at schema validation without end-to-end chain proof.
Maturity assessment

Operations, Securities Services, Enterprise Architecture

Can you name who owns each segment of the custody chain—inside and outside your walls?

MiKaDiv fails where no institution holds end-to-end truth.

Custody-chain reconstruction is the operational core of MiKaDiv. Positions, sub-custody, omnibus structures, and corporate actions fragment across books, registers, and counterparties. Readiness means explicit data ownership and reconciliation design—not assuming a single golden record exists internally.

Evidence criteria

Red flags

  • Data sourcing stops at the custodian boundary.
  • No metric for “unreconstructable” chains before submission.
Maturity assessment

Reference Data, KYC/Legal Entity, Operations

Are LEIs and legal entity identifiers reliable at every node you must report?

Invalid identifiers invalidate submissions and stall corrections.

MiKaDiv requires consistent legal entity identification across the chain. LEI quality, dormant entities, branch vs. head-office mapping, and issuer vs. holder distinctions are recurring failure points. Identifier governance is a readiness discipline, not a one-time enrichment exercise.

Evidence criteria

Red flags

  • Manual LEI lookup at month-end without ownership.
  • No linkage between client master data and chain reconstruction.
Maturity assessment

Relationship Management, Legal, Vendor Management, Operations

Do you have enforceable paths to obtain upstream custody-chain data on time?

You cannot report what counterparties never send—or send too late.

Foreign CFIs and intermediaries must supply detailed custody-chain data to German counterparties. Readiness requires contractual clauses, SLAs, technical interfaces, and escalation paths—not informal email chains before ex-date.

Evidence criteria

Red flags

  • Assumption that “the global custodian will figure it out.”
  • No testing with top 10 upstream institutions by volume.
Maturity assessment

Client Coverage, Tax, Risk, Product

Have you quantified client harm if upstream data prevents UUID issuance?

From 2027, tax reclaims depend on UUIDs from accepted MiKaDiv reports.

Investors need a UUID from an accepted MiKaDiv report to reclaim German withholding tax. If an institution in the chain fails to deliver required data, downstream customers may face a structural tax disadvantage on German dividends. This is a franchise risk, not a back-office detail.

Evidence criteria

Red flags

  • No client-facing narrative for UUID-dependent reclaims.
  • Impact analysis deferred until “after go-live.”
Maturity assessment

Tax Technology, Operations Control, Internal Audit

Do you validate custody-chain truth—not only XML schema conformance?

Schema-valid files can still encode impossible or inconsistent chains.

XML is a last-mile output. Readiness requires cross-system validation: positions vs. events, chain completeness, exemption logic, and business rules that reflect how securities actually move. Internal audit and regulators will ask for explainability, not just successful transmission.

Evidence criteria

Red flags

  • Testing equals XSD validation.
  • Operations discovers breaks only after BZSt rejection.
Maturity assessment

Operations Control, Service Management, Tax Operations

Can you see chain breaks early enough to act before submission windows close?

Late discovery converts data problems into regulatory and client incidents.

MiKaDiv introduces recurring operational cadence tied to income events and reporting cycles. Mature institutions instrument completeness, latency, and exception aging—not monthly heroics. Monitoring is part of the control framework, not a project deliverable.

Evidence criteria

Red flags

  • No operational KPIs until production.
  • Exception queues staffed only during peak season.
Maturity assessment

Securities Services, Technology, Vendor Management

Is your transmission path to the German reporting node defined, contracted, and tested?

Non-German institutions typically transmit via German custodians—not directly to BZSt.

Most foreign institutions do not transmit to the Federal Central Tax Office (BZSt) directly. They transmit via their German custodian—often through institutional channels such as Clearstream Xact. Readiness includes connectivity, security, message handling, and joint testing with the custodian—not assuming file drop alone.

Evidence criteria

Red flags

  • Transmission treated as “phase 2” after mapping.
  • No signed test schedule with the German custodian.
Maturity assessment

Enterprise Architecture, Strategy, Tax Leadership

Will your MiKaDiv architecture extend to FASTER without rebuilding the custody-chain core?

Point solutions for MiKaDiv become stranded cost when FASTER expands the same problem.

MiKaDiv is the near-term mandate; the EU FASTER initiative widens the same custody-chain coordination challenge across jurisdictions. Readiness in 2026 means choosing a platform path—industry protocols such as OpenFASTER, reusable data models, and interoperable exchange—not a one-country XML factory.

Evidence criteria

Red flags

  • Vendor selection based only on German XSD templates.
  • No executive forum linking MiKaDiv program to EU withholding-tax strategy.
Maturity assessment

Turn assessment into an operating plan

If three or more questions are At risk or Not started, your critical path is likely custody-chain coordination—not XML mapping. Divizend runs focused readiness sessions grounded in your chain, counterparties, and transmission path.

Book a MiKaDiv Readiness SessionRFP simulatorReturn to overview