help wanted: Germany Meldeschein generate/retain workflow (hotel operator design)

[telivity-otaip]

Why hotels care

German properties need a Meldeschein (guest registration form) workflow: capture, generate, retain. This is on HAIP’s compliance market-entry list as feature-only — generate/retain in product, no free automated authority filing claim (docs/integrations/compliance-market-entry.md).

Sister issue for fiscal signing: #104 (KassenSichV / TSE). Registration is the other half of "can a German indie hotel actually run on HAIP."

Principles

• Do not invent Meldeschein field requirements — source from current German hotel registration practice / official guidance and cite it
• Generate + store + audit access; no fake "submit to police API" theater
• Per-property enablement; non-DE properties unaffected
• Minors/guardian and multi-guest party rules are domain-sensitive — stop and ask if KB/research is thin

Current state (code anchors)

• Guest registrationData JSON + reservation registration signed/submitted fields
• Pre-register DTO (advance check-in data, no status change)
• Compliance catalog row: Germany Meldeschein — feature-only
• Build plan: "Complete guest registration (ID, minors/guardian, per-jurisdiction compliance — deeper than desk card)"

Proposed phases

Phase 0 — this issue (spec + operator input)

• Lock required fields, retention period, who can export/print, multi-guest party behavior
• PDF/print layout requirements from hoteliers

Phase 1 — Product workflow

• Property setting enables DE Meldeschein pack
• Desk capture at check-in / pre-register
• Generate artifact linked to reservation; audit view/print/export
• Tests with fixtures (no real PII)

Phase 2 — Pack siblings (separate issues): AT Gästeverzeichnis, FR fiche de police, etc., reusing the generate/retain pattern

Open questions (German GMs / front office — we need you)

• Exact field set you still collect in 2026 (incl. digital vs paper)
• Retention / export expectations for tax advisor / police inspection
• One form per arriving adult vs per room/party?
• Interaction with online check-in / ID scan providers later

Out of scope

• Claiming automated filing to any authority
• TSE / fiscalization (see German fiscalization (KassenSichV / TSE) — design + Phase 0 spec #104)

Acceptance criteria (Phase 1)

• Phase 0 answers locked in the issue with citations
• Generate/retain/export works for DE-enabled properties
• Audit trail on access; PII follows GDPR erasure rules (help wanted: GDPR erasure must scrub PII across stay artifacts (not only guest row) #305)
• Vitest + desk path documented

How to contribute

Hotel operators in DE: please comment with how you handle Meldeschein today — that unblocks coding.
Engineers: wait for Phase 0 lock on fields, then implement the pack pattern from compliance-market-entry.md.

Search keywords: Meldeschein, Germany hotel registration, guest registration, Gästeverzeichnis, fiche de police, compliance, PMS, help wanted