Your withholding-tax system is bought. Now it has to work in daily operations.

• Licensed, but not in production

  The licence has been running for months, but not a single reclaim goes through the system in production. The business unit is waiting for the interface, IT for the functional concept, the vendor for feedback.

• The back-office interface blocks everything

  The back office or fund accounting does not deliver positions and payments the way the reclaim process needs them. Nobody translates between business unit, development and vendor, and every query costs a week.

• Deadlines and missing documents in Excel

  Certificates of residence, powers of attorney and tax vouchers are tracked in a parallel list because the system does not show status, deadline and next step. The list is the real expert system — without four-eyes approval or audit trail.

• Reporting obligation with a fixed date, process without shape

  MiKaDiv applies to capital income received after 31 December 2026. The date is fixed, but who delivers which data from which level of the custody chain is still unresolved in-house — and the reporting module has not arrived in daily work.

• Key users left alone after training

  Two days of training in a meeting room, then go-live. The key users know the functions but not the exceptions: partial refunds, expired certificates, corrections after submission.

• Nobody understands the new module without an explanation

  On the vendor side: a new reporting or reclaim module is technically correct, but customers need long onboarding and report questions instead of bugs.

• Withholding-tax reclaim (tax reclaim, standard refund)
• Relief at source (Vorabbefreiung) and quick refund
• Double taxation treaty (DTT) and treaty rate
• Certificate of residence and digital eTRC
• Tax voucher (Steuerbescheinigung) and reference number
• Power of attorney and deadlines per source country
• Custody chain, places of safekeeping and sub-custodians
• Four-eyes principle and approval workflow
• MiKaDiv, reporting obligation and BZSt
• Sections 45b, 45c and 50c EStG, AbzStEntModG
• FASTER — Directive (EU) 2025/50
• Fund accounting, master KVG and custodian
• As-is analysis, functional concept, UAT, go-live, hypercare
• Key users and training at the desk

Withholding-tax reclaim (tax reclaim)

Recovery of tax withheld in excess in the source country on dividends or interest, where the double taxation treaty provides a lower rate. The claim follows the payment and usually requires a certificate of residence, proof of tax withheld and a power of attorney.

Relief at source (Vorabbefreiung)

The reduced treaty rate is applied at the time of payment, so no refund is needed. Precondition: the documentation is available in the custody chain on time and in full.

Double taxation treaty (DTT / DBA)

Bilateral agreement that caps the withholding-tax rate between two states. The difference between the domestic rate and the treaty rate is the refundable amount.

Certificate of residence

Confirmation by the tax authority of the investor’s tax residence; precondition for every treaty relief. FASTER introduces a digital form from 2030 (eTRC).

Tax voucher (Steuerbescheinigung)

Proof issued by the paying agent of capital gains tax withheld. Under MiKaDiv it receives a reference number and its data is reported electronically to the BZSt (Section 45b EStG).

Custody chain and places of safekeeping

Chain from depositary bank through sub-custodians to the place of safekeeping and the issuer. Each level has its own deadlines and formats; if documentation is missing at one point, the claim fails at the end of the chain.

MiKaDiv

Reporting procedure for capital gains tax on dividends from shares and depositary receipts (Sections 45b, 45c EStG). Electronic reporting to the BZSt for capital income received after 31 December 2026.

Section 50c EStG and AbzStEntModG

The Withholding Tax Relief Modernisation Act of 2 June 2021 (Federal Law Gazette I p. 1259) moved the relief procedure into Section 50c EStG. Since 2024 the electronic application to the BZSt has been the rule.

FASTER — Directive (EU) 2025/50

Council Directive of 10 December 2024 on faster and safer relief of excess withholding taxes: eTRC, relief at source, quick refund and a register of certified financial intermediaries. Transposition by 31 December 2028, application from 1 January 2030.

1. 01

   Shared language first, screens second

   In an engineering-led organisation, domain knowledge sat with developers, product owner and management — implicit and unprioritised. Only a glossary, taxonomy and regulatory mapping made personas possible; personas made business processes visible; processes revealed critical moments.

2. 02

   Make complexity manageable, do not hide it

   Expert users in withholding tax and reporting are specialists, not casual users. They need validation logic, audit trails and evidence visible — not an interface that smooths everything over. The goal is auditable and safe, not “simple”.

3. 03

   Processes as end-to-end workflows, not feature lists

   As long as a reporting module is discussed as a collection of screens, it stays unclear what it is optimising for. Only the whole path — find, validate, correct, approve, track — shows where the system must not fail.

4. 04

   Observation at the desk beats any process description

   In steam-turbine manufacturing the core problems were not found in a workshop but after months next to the engineers: printed parts lists, highlighters, copy-paste of old documents. In withholding tax the paper list is called Excel — just as invisible until you sit next to it.

5. 05

   A prototype with real data replaces ten presentations

   Stakeholders at tier-1 banks took a TypeScript prototype with realistic data for a finished product — because it showed filters, validation, bulk actions and audit trail the way daily work needs them. Conversely, the business unit only believes the system once it finds its own case in it.

6. 06

   The parallel list is a symptom, not a discipline problem

   Teams keep Excel next to the system because the system does not show status, deadline or next step — not out of defiance. Ban the list and you get a hidden list. Take it seriously and you get the most precise requirements list there is.

Frequently asked questions

Do you work for the vendor or for us?

Only ever for one side per project. If your bank, KVG or custodian hires us for the rollout, we work for you — not for the vendor; if a vendor hires us, we work for the vendor. Information from one engagement never flows into another.

Do you need access to our data?

No. For implementation support, observation in the business unit, anonymised sample cases and test data in UAT are enough. We do not need access to production data; an NDA and your information-security requirements are standard.

How quickly will we see results?

The as-is analysis usually delivers robust findings within a few weeks. Measurable improvements follow once priorities are set and we support the team in daily operations. We estimate the timeframe together in the initial call.

Which role do you take on the project?

Depending on the phase, UX Consultant, Business Analyst with a UX focus or rollout support: requirements analysis and functional concept, process design (in BPMN if desired), user stories and test cases, key-user concept and training — from as-is analysis to hypercare. We replace neither project management nor tax advice; we make both faster.

How do we prepare the business unit for MiKaDiv?

By looking at data and process, not just the module: which tax-voucher data comes from which level of the custody chain, who checks, who approves, what happens with corrections. The BZSt communication handbook sets the format; the workflows behind it are defined by your institution — and that is where we support you.

Implementation support or change management — which do we need first?

If the software does not yet fit the process as it is actually run, change communication achieves little: then as-is analysis, functional concept and UX adjustments come first. If the system fits but acceptance is missing, key users, training and visible sponsorship take priority. Usually it is both — which is why we combine UX and rollout in one role.

Do you run key-user training?

Yes, at the desk with real cases, not in a meeting room. Key users learn not only functions but exceptions: expired certificates of residence, partial refunds, rejections, corrections after submission.

Do you work remotely?

Yes, mostly remote, based in Munich. On-site work in Frankfurt and across the DACH region is possible by arrangement — for process capture and training it is often the better way.

How does the engagement work contractually?

As a service or work contract with clearly described results per phase, directly or through your staffing partner.