ED18 - Transparency Register in Ongoing Operations: Changes, Discrepancies, Fines

Problem

The initial notification (ED17) is done - now the real compliance work begins, and this is precisely where the typical violations arise:

• Changes go undetected: A share deal, a capital increase, a voting pooling agreement, a change of managing director for fictitious beneficial owners - each of these events changes the reportable constellation, and none of them carries a sign saying "Transparency Register change due".
• Discrepancy reports underestimated: Obligated entities under § 2 Abs. 1 GwG - banks, notaries, tax advisors, auditors - must report without delay if their findings deviate from the register entry (§ 23a GwG). The affected legal entity receives a request to submit a statement with a deadline set - and resolving it regularly requires evidence: identity documents, articles of association, organizational charts, shareholder lists. Without properly kept records, this becomes expensive and time-consuming.
• Fines with side effects: Violations of the transparency obligations are administrative offenses (§ 56 Abs. 1 S. 1 Nr. 54-66 GwG) - fines of up to 150,000 EUR, and up to 1 million EUR for serious, systematic or repeated violations (or twice the economic benefit). Legally binding decisions can be made public - the reputational risk often exceeds the fine itself.
• KYC downstream damage: In financings, M&A transactions and account openings, banks check the Transparency Register (CDD diligence). An incorrect or missing entry becomes a dealbreaker there - regardless of the fine.

Key Message

Ongoing operations are a trigger-driven process - and that is exactly what the Git-native journal is built for:

1. Duty to report changes (without delay): Any change to the information named in § 19 Abs. 1 GwG - ownership structure (thresholds exceeded/ fallen below), voting rights arrangements, control agreements, changes of managing director for fictitious beneficial owners, personal data of beneficial owners (name, place of residence, nationality) - must be reported without prompting and without delay as a follow-up order (ED17: not a correction order!).
2. Trigger catalog as trigger rule: The repo harness knows the triggering events and enforces the review: Every notary appointment (transfer of shares), every capital measure, every organizational change generates a journal entry that poses the beneficial owner question - before the deadline starts to run.
3. The discrepancy case as a process: Receipt of the request → statement within the deadline → evidence attached (Sidecar-secured shareholder list, articles of association, organizational chart) → report corrected (follow-up order) → case documented in the repo. Those who can produce the records from ED12 in seconds resolve the discrepancy in days instead of weeks.
4. Fine avoidance is process quality: The examiner assesses the organization (§ 30 OWiG: absence of the required supervision). Demonstrable processes - trigger rules, documented investigations, reports submitted within deadlines - are the defense.

Compliance by Design: The Transparency Register is the proof that trigger control works: No event in the life of the company that touches the ownership or control structure may pass by "silently". The repo enforces visibility - the rest is procedural discipline.

Trigger Catalog and Notification Response

The silent case: Even the review result "no reportable change" is documented - as an artifact with rationale. Only then is it traceable later that a trigger was recognized and reviewed.

Discrepancy Procedure (§ 23a GwG)

Note: Discrepancy reports are free of charge (unlike register inspections) - but resolving them costs the legal entity time. The evidence from ED12 (investigation, records with SHA-256) is the accelerating resource here: anything stored in the repo with a Sidecar can be produced within minutes.

Fine Landscape (§ 56 Abs. 1 S. 1 Nr. 54-66 GwG)

Defense is organization (§ 130 OWiG): The entrepreneur demonstrates that the obligations were organized: trigger rules take effect, investigations are documented, reports were submitted within deadlines, responsibilities were assigned. Precisely this organization is the content of this series - the repo is the proof of organization.

The Discrepancy/Fine Case Artifact

{
  "$schema": "https://gitcover.org/schemas/wb-unstimmigkeit-1.0.schema.json",
  "V7GUID": "WB_UNSTIMMIGKEIT",
  "uuidV7": "01a065f3-dbbd-7000-8000-000000000004",
  "tenant": "ORG-1",
  "art": "unstimmigkeitsaufforderung",
  "eingang": "261105",
  "frist": "261120",
  "veranlasst_durch": "Verpflichteter (anonymisiert)",
  "nachweise": [
    { "art": "gesellschafterliste", "sha256": "…" },
    { "art": "organisationigramm", "sha256": "…" }
  ],
  "stellungnahme": { "datum": "261112", "sha256": "…" },
  "reaktion": { "art": "folgeauftrag", "vorgangsnummer": "TR-2026-YYYYYYY" },
  "ergebnis": "ausgeraeumt"
}

Connection with the Series

Risk Leverage

Harness Requirement (Preview)

The complete list of requirements in Harness-Anforderungen.md.

Sources

• Geldwäschegesetz (GwG): § 23a (discrepancy reports), § 20 Abs. 1 (continuous updating), § 56 Abs. 1 S. 1 Nr. 54-66 (fines)
• OWiG: § 30 (acting for organs), § 130 (violation of the supervisory duty in businesses)
• Federal Office of Administration: procedural practice on discrepancies and fines (www.transparenzregister.de)
• KYC/CDD practice of the obligated entities (§ 2 Abs. 1 GwG) as a downstream risk of incorrect register entries

Source Topology and CDN Reference Links

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.