The hard part of MiKaDiv isn't the submission.It's the custody chain.

It's reconstructing the custody chain across institutions with data no single institution fully controls.

If you treat MiKaDiv like a reporting task, you will build the wrong system.

Book a MiKaDiv Readiness Session

One-time implementation. Fixed annual pricing. Optional customizations.

Custody chain (reconstruction)

MiKaDiv succeeds or fails before XML: across institutions, across systems.

Context

MiKaDiv at a glance

Germany’s mandatory digital reporting for investment income (e.g. dividends and interest) along the custody chain—replacing paper tax certificates with standardized, authority-facing submissions.

Legal basis & start. Introduced under the Withholding Tax Relief Modernisation Act (2021). The new procedure applies from 1 January 2027 to income received after 31 December 2026.
Who is in scope. German custodian banks and paying agents report dividend and related data to the Federal Central Tax Office (BZSt). Foreign financial institutions must supply detailed custody-chain data to German counterparties.
What must be reported. Beneficial owners and accounts, the custody chain with legal entity identifiers (LEIs), securities and income details, relevant transaction activity, a UUID for each submission and corrections, and exemption reporting where applicable.
Tax reclaims need the UUID. From 1 January 2027, to get German withholding tax back, investors need a UUID from an accepted MiKaDiv report. It replaces the old paper proof. If a bank outside Germany does not send its German custodian the data needed for that report, customers never get that UUID. They would then face a significant tax disadvantage on their German dividends.
Policy direction. Digitize and simplify withholding-tax reporting, strengthen transparency across the chain, and align with the EU FASTER initiative so national regimes do not duplicate each other indefinitely.

Problem

If you frame MiKaDiv as reporting, you’ll build the wrong thing.

XML is a last-mile output. The real work is establishing custody-chain truth across institutions.

What teams think

Reporting

XML
mapping
last-mile delivery

What it actually is

Custody-chain truth

cross-institution data
validation across systems
reconstruction & auditability

The last mile is easy. The hard part is everything before it.

Scope reality

Upstream complexity is where systems break. XML is a small, final step.

You don’t control the data

Positions and events are split across custodians, registers, and internal books.

You can’t validate locally

Truth is established across institutions—not inside one database.

You will rebuild for FASTER

The same coordination problem expands; point fixes don’t compound.

This fails because the problem is not inside your institution.

System boundary

The problem is mostly outside your institution.

Solution

Turn fragmentation into control.

Divizend is the system layer that connects ingestion, normalization, validation, reconstruction, reporting, and audit—across systems and institutions.

Divizend connects:

ingestion
normalization
validation
custody chain reconstruction
reporting
audit

Across systems. Across institutions.

System layer

One operational pipeline from ingestion to audit.

Capabilities

Built to prove truth—not just produce files.

Every capability exists to make custody-chain reconstruction operational: explainable validation, monitoring, and auditability.

Cross-system ingestion

Bring fragmented inputs into one operational model.

Custody-chain reconstruction

Rebuild the chain institutions only see in pieces.

Rule validation

Validate across systems with explainable checks.

Monitoring

See breakage early—before submission deadlines.

Audit trail

Trace decisions from source data to transmitted output.

Built for real-world transmission.

If you’re not a German institution, you typically won’t transmit to the BZSt directly. You transmit via your German custodian (most often Clearstream)—and Divizend is built to connect that chain end-to-end.

Direct, secure, real-time integration with Clearstream Xact enables institutional-grade data transmission.

Transmission is not an afterthought. It is part of the system.

Transmission path

Direct, secure, real-time integration via Xact.

Pricing built for control.

Internal builds hide cost in engineering and redesign. Divizend gives clarity.

One-time implementation
Fixed annual pricing
Optional customization

Internal

unclear cost
ongoing engineering
rebuild risk

Divizend

defined scope
predictable cost
controlled expansion

Cost clarity

Predictable scope beats hidden engineering cost.

Build once. Extend forward.

MiKaDiv is the start. FASTER expands the same custody-chain problem—so what you ship now has to extend, not restart.

OpenFASTER is the vendor-independent protocol and data-exchange format certified financial intermediaries can use for indirect reporting under MiKaDiv and FASTER: industry-standard, internationalized semantics, pull and push modes, and clearly defined exchange formats between CFIs. That is the interoperability layer a serious platform plans for from the beginning.

Divizend is spearheading OpenFASTER development—working with the industry so the standard matches how custody chains actually operate.

Future-proofing

Same custody-chain core—extend toward FASTER with open CFI exchange (OpenFASTER).

Comparison

Make the decision obvious.

Internal builds fail where the data lives. Services and vendors help—but don’t create a reusable operating system.

Data control

Internal: Low
Services: Mixed
Vendors: Mixed
Divizend: High

Coordination

Internal: Hard
Services: Variable
Vendors: Variable
Divizend: Systematized

Reusability

Internal: Low
Services: Low/Med
Vendors: Med
Divizend: High

Cost

Internal: Hidden
Services: Hourly
Vendors: License + ?
Divizend: Defined

Future-proofing

Internal: Risky
Services: Mixed
Vendors: Mixed
Divizend: Platform path

Comparison of Internal, Services, Vendors, and Divizend
	Internal	Services	Vendors	Divizend
Data control	Low	Mixed	Mixed	High
Coordination	Hard	Variable	Variable	Systematized
Reusability	Low	Low/Med	Med	High
Cost	Hidden	Hourly	License + ?	Defined
Future-proofing	Risky	Mixed	Mixed	Platform path

FAQ

Short answers. No ambiguity.

If you’re evaluating MiKaDiv as “reporting”, start here.

Can we solve this with an internal build?

You can build software internally—but you still won’t own the cross-institution data. That’s where the failure mode lives.

Is MiKaDiv “just XML”?

XML is an output shape. The hard part is proving the custody chain and validating across systems before you ever serialize a file.

What do you mean by custody chain reconstruction?

Assembling a consistent chain of custody from partial records held by different institutions—so reporting reflects reality, not local assumptions.

How does pricing work?

One-time implementation, fixed annual pricing, and optional customization—so cost stays legible as scope evolves.

What about FASTER?

FASTER widens the same coordination problem. Divizend is designed to extend forward without rebuilding the core model.

Not convinced yet? These customers already trust Divizend with their withholding tax reclaims

Build something that works once. Or something that lasts.

Request a MiKaDiv readiness session. We’ll respond with next steps.

What you get: A focused readout on scope, data dependencies, and what “custody chain” implies for implementation.
No noise: Short, direct, and grounded in the operational workflow—not slides.