ED14 - Bundesanzeiger account and E-Bilanz: set up early

Problem

The obligation to deposit the annual financial statements (§ 325 HGB) affects every corporation: The annual financial statements must be deposited electronically with the Bundesanzeiger-Verlag within twelve months of the balance sheet date (and published there, with extended disclosure and exemption rules for small companies). The classic trap:

• The entrepreneur thinks of everything - accounts, receipts, tax advisor - but not of the account for the deposit itself
• Creating an account with the Bundesanzeiger is a multi-stage process for organizations: setting up the organizational account, authorization signature or legitimation check - and this can involve postal correspondence
• Postal procedures take their time: days to weeks. Anyone who approaches the deposit "at the last minute" and does not have an activated account cannot meet the deadline - with the consequences of § 335 HGB (administrative fine proceedings by the Federal Office of Justice)
• The same pattern repeats with E-Bilanz/E-Rechnung and other ELSTER-based procedures: without an organizational certificate set up early (and tested access routes), time pressure arises exactly when deadlines are running

Core message

Digital procedures are only fast if the access is already in place. Therefore, the following principle applies to the authority visits in Part III:

Account first, obligation later: ELSTER organizational certificate, Bundesanzeiger organizational account and Transparenzregister access are set up in parallel with the classic registrations (ED13, ED15, ED16) - not only when the respective obligation (deposit, annual financial statements, notification) forces it.

1. Bundesanzeiger organizational account: The account through which the deposit under § 325 HGB runs is an organizational account (not the private access). The assignment to the organization via proofs of authorization can include postal steps (signature, legitimation) - factor in the processing time.
2. ELSTER organizational certificate: Basis for tax filings and E-Bilanz. Applied for early (ED13, ED19), even if the first use case is still a long way off.
3. Transparenzregister access: The access for notifications under §§ 20, 21 GwG (ED04, ED17) runs via the operator network of the Bundesanzeiger-Verlag - same identity logic, same authorization pitfalls.
4. E-Bilanz: Transmitting the balance sheet via ELSTER to the tax office (XBRL, tax taxonomy) requires software and practiced processes - both are built up before the first real run (test run, process documentation).
5. Documentation as artifact: Every access route set up is documented in the Git repo: purpose, account holder, activation date, authorization path (incl. postal proof with SHA-256). This makes the obligation to maintain the access routes provable - and the managing director knows which access routes exist and who holds them.

Compliance by Design: The access routes are part of the process documentation (ED07): Who can do what via which access? The repo knows the path to the answer: zugaenge.json per organization with purpose, status (applied for/activated), receipt references. When a deadline falls due, the associated access is not "somewhere", but available as a verified artifact.

The access landscape by way of example

Timeline: Account setup vs. deposit obligation

Risk lever: The account costs 30 minutes of effort today plus waiting time in the background. Without an account, the same situation later costs administrative fine proceedings (§ 335 HGB) plus reputational stress. That is exactly the "risk leverage" of the series: cheap today, audit-proof tomorrow.

The access artifact

{
  "$schema": "https://gitcover.org/schemas/zugaenge-1.0.schema.json",
  "V7GUID": "ZUGANG_VERFAHREN",
  "uuidV7": "01a065f3-dbbd-7000-8000-000000000002",
  "tenant": "ORG-1",
  "zugang": {
    "verfahren": "bundesanzeiger_hinterlegung",
    "konto_typ": "organisation",
    "zweck": "Hinterlegung und Offenlegung Jahresabschluss § 325 HGB",
    "status": "freigeschaltet",
    "beantragt_am": "260915",
    "freigeschaltet_am": "261012",
    "berechtigungsweg": "postalisch",
    "belege": [
      { "art": "unterschreibung_berechtigung", "sha256": "…" }
    ],
    "verantwortlich": { "person": "E1", "role": "GF" }
  }
}

No datetime field - capture time in the uuidV7 (ED03); beantragt_am/freigeschaltet_am are domain data of the procedure.

Connection to the series

• ED13 (tax office): ELSTER organizational certificate as the first exercise; note on parallel account setup
• ED17 (Transparenzregister implementation): same operator logic, the access is part of the authority visits
• ED19 (authority interface practice): ELSTER, DE-Mail, eXTra as an intermediation problem - provided the access routes are in place
• Annual financial statements article (Part V, planned): the deposit as a use case of the prepared access

Risk leverage

Harness requirement (preview)

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

Sources

• Handelsgesetzbuch: § 325 (deposit and disclosure), § 335 (administrative fine proceedings) - see gesetze-im-internet.de for the full text
• ELSTER procedure: organizational certificate for legal entities (registration, authority number) - www.elster.de
• Bundesanzeiger-Verlag: procedure for electronic deposit (organizational account, proofs of authorization) - www.bundesanzeiger.de
• E-Bilanz: tax taxonomy (GCD), ELSTER transmission
• GwG §§ 20, 21 (Transparenzregister access via operator)

Source topology and CDN reference links

Note: This mapping 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.