ED17 - Transparency Register: Carrying out the notification via transparenzregister.de

Problem

The determination is complete (ED04, ED12) — but the transmission to the Transparency Register is a separate procedural step with pitfalls of its own:

Core message

Execution is a second, separate step after the determination — with its own artifact and its own proof:

  1. Electronic transmission: All details (ED04: name, date of birth, place of residence, all nationalities, nature and extent of the economic interest, validity date) are transmitted via the portal of the Transparency Register to the register-maintaining body.
  2. Pre-incorporation company (i. Gr.): notification under "Sonstige Rechtsgestaltungen" with the name suffix "i. Gr."; after the commercial register entry, the entry (commercial register number, register court) is subsequently submitted as an amendment notification — the beneficial owner data is carried over automatically.
  3. Changes: Any change to the details or the ownership structure must be submitted as a follow-up filing without being prompted (ED18 for the triggers in detail).
  4. Fees: Annual register fee (§ 24 GwG, fee ordinance) — track it as a recurring burden in the repo's deadline calendar (ED09), not as a surprise.
  5. Proof: The transmission is documented in the repo — with case number, date, and reference to the determination. This makes the notification obligation (§ 20 Abs. 1 GwG) demonstrably fulfilled.

Compliance by Design: Two artifacts, one chain: wb_ermittlung.json (ED12) substantiates what is reported; wb_meldung.json documents that and when it was reported — including the case number. The pre-commit hook can check: Does a new determination have a notification? Does the notification have a determination as its source? The chain is thus machine-checkable.

Process: from determination to entry

%%{init: {'theme':'base','themeVariables':{'primaryColor':'#FBFAF7','primaryTextColor':'#0F1B33','primaryBorderColor':'#6B7280','lineColor':'#6B7280'}}}%% flowchart LR E["wb_ermittlung.json
(ED12)
Ergebnis steht"] E --> P["Portal
www.transparenzregister.de
Organisationszugang (ED14)"] P --> U["Übermittlung
Angaben je wB
(§ 19 Abs. 1 GwG)"] U --> V["Vorgangsnummer
der Übermittlung"] V --> R["Eintragung
durch registerführende Stelle"] R --> N["wb_meldung.json
Vorgangsnr. + Datum
+ Bezug zur Ermittlung"] N --> F["Fristen-Kalender
Gebühr jährlich
(§ 24 GwG)"] style E fill:#DBEAFE,stroke:#1D4ED8,color:#0F1B33 style P fill:#DBEAFE,stroke:#1D4ED8,color:#0F1B33 style U fill:#FDBA74,stroke:#C2410C,color:#0F1B33 style V fill:#0F1B33,stroke:#0F1B33,color:#FBFAF7 style R fill:#D1FAE5,stroke:#0A7F5C,color:#0F1B33 style N fill:#D1FAE5,stroke:#0A7F5C,color:#0F1B33 style F fill:#FDBA74,stroke:#C2410C,color:#0F1B33

The notification artifact

{
  "$schema": "https://gitcover.org/schemas/wb-meldung-1.0.schema.json",
  "V7GUID": "WB_MELDUNG",
  "uuidV7": "01a065f3-dbbd-7000-8000-000000000003",
  "tenant": "ORG-1",
  "art": "erstmeldung",
  "grundlage": {
    "ermittlung_uuidV7": "01a065f3-dbbd-7000-8000-000000000001",
    "ermittlung_sha256": "…"
  },
  "gueltig_ab": "260901",
  "uebermittelt_am": "260920",
  "vorgangsnummer": "TR-2026-XXXXXXX",
  "weg": "portal",
  "gemeldete_wb": [
    { "person": "E1", "typ": "mittelbar",
      "art_interesse": "mittelbare Kontrolle über ORG-5",
      "umfang": "100 % an ORG-5" }
  ],
  "obsolescence": { "status": "active", "superseded_by": null, "superseded_at": null }
}

Field discipline: uebermittelt_am and gueltig_ab are domain data (transmission date, start of the constellation) — the capture time of the artifact is embedded in the uuidV7 (ED03).

Linkage with the series

Article Relationship to ED17
ED04 Legal foundations: who, beneficial owner definition, fiction, pre-incorporation company
ED12 The determination as the basis of the notification — before the transmission
ED14 The organizational access — set up early
ED18 What happens after the initial notification: changes, discrepancies, fines
ED09 Annual fee burden in the repo's deadline management

Risk leverage

Today (cheap) Tomorrow (audit-proof) Risk mitigated
Notification documented with case number Notification demonstrably fulfilled Fine for "failure to notify"
Follow-up filing discipline (no corrections) History in the register remains gap-free Loss of the time series
Validity date carefully determined Gap-free coverage since 10/2017 Follow-up request for earlier constellations
Fee in the deadline calendar No unexpected costs Default on the fee

Harness requirement (preview)

ID Requirement Priority
FA-17.1 Notification artifact with case number and determination reference (schema wb-meldung-1.0) MUST
FA-17.2 Rule set: new determination ⇒ notification within the deadline; notification references the determination MUST
FA-17.3 Annual fee burden as a recurring deadline entry SHOULD

The complete requirements list in Harness-Anforderungen.md.

Sources

Role Location Purpose
Primary / SSoT git.gitcover.org/GCC Canonical storage (GPG-signed, versioned)
Public OSS Mirror / CDN codeberg.org/gitcover-commons Read-only mirror; FLOSS discovery
Community Hub github.com/gitcover-commons Issues & Discussions; source code reference to Codeberg

Note: This assignment of sources, mirror, and community hub reflects the current state and may change. Please check the respective canonical source on gitcover.org for the current state.