Guest Registration in Germany, Austria, and Switzerland

Guest registration does not end with a completed form. Vacation rentals in Germany, Austria, and Switzerland need local reporting procedures, clear responsibilities, and appropriate retention periods. This guide follows the workflow from booking to check-out and explains the role of digital tools.

View across a village of vacation chalets, green mountain slopes and snow-covered peaks.

Anyone who commercially rents out vacation apartments, a vacation home, or serviced apartments will generally need to register their guests. Requirements differ across Germany, Austria, and Switzerland. Depending on the country and location, registration serves legal, statistical, and tax purposes.

Which information does your location require, which reporting procedures apply, and how can you control the administrative workload across several properties?

Within the agreed scope, Oprivia helps organize stay-related information, tasks, and supporting records. The registration forms, tourism levies, guest cards, and external reporting connections covered by a workflow are assessed separately for each location. Reservations and availability remain in the systems designated for them.

Legal Requirements for Guest Registration in Vacation Apartments and Vacation Homes

Sections 29 and 30 of Germany’s Federal Registration Act govern the special registration requirement in accommodation establishments. For standard short stays, it applies to foreign guests. Local levies and other registration procedures must be checked separately.

In Austria, Section 5 of the Registration Act governs the recording of guest information. In Switzerland, Article 16 of the Foreign Nationals and Integration Act (AIG) requires the registration of foreign vacation guests. Guest registration legislation varies by canton and municipality. The guide to guest registration in Switzerland explains how required guest information, cantonal reporting procedures, and tourism levies relate to one another.

These guests generally need to sign a special registration form on arrival. With their consent, confirmation may instead use an electronic procedure permitted by law.

When registering, they present a recognized, valid passport or passport substitute. The accommodation provider checks the information against the document. This special registration requirement has been abolished for German guests. However, local registration and tax obligations, such as visitor or resort taxes, may continue to apply independently.

Under Section 30(2) BMG, the special registration form for foreign guests contains the following information:

  • The guest's name and address
  • Date of birth
  • Nationality
  • Arrival and departure dates
  • Serial number of the recognized, valid passport or passport substitute document
  • Number of accompanying foreign travelers and their respective nationalities

Additional registration, permit, and tax obligations may apply regionally. In Berlin, vacation rentals generally have to be advertised with a publicly visible registration number. In Basel-Stadt, accommodation businesses with more than six beds require an operating license.

Depending on local rules, recorded overnight stays may also provide the basis for calculating and settling visitor or resort taxes. For rental operators, this means that, depending on the location, collecting personal data is only part of the process. Further administrative steps may be required.

Structured data collection helps ensure that the different requirements are not overlooked in day-to-day rental operations.

From Booking to Check-out: The Guest Registration Workflow in Practice

The typical workflow for professionally managed vacation rentals can be divided into several steps:

  1. A booking comes in through the operator's own website, platforms such as Booking.com or Airbnb, or an email inquiry.
  2. Pre-arrival communication: Before arrival, rental operators often use digital pre-check-in tools to collect guest information in advance. Digital guest registration also enables automatic reminders for guests.
  3. Check-in: Collection and verification of required information, identity document checks for foreign guests, and handover of the accommodation. Digital tools can simplify the check-in process and save time when entering information.
  4. Timely guest registration and settlement: Guest information is collected in accordance with local regulations and, depending on the procedure, confirmed, submitted to the responsible authority, or kept available for inspection by authorities. Any applicable visitor tax is calculated and remitted separately in accordance with local requirements.
  5. Check-out: Deregistration, damage inspection, and archiving.

Modern booking systems enable centralized management of occupancy calendars and integrate digital guest registration directly into the booking process. They can be used on a PC, smartphone, or tablet.

Common vacation rental management software such as Fewo-Verwalter supports anything from individual units to many thousands of vacation accommodations and offers connections to more than 60 portals through the Feondi channel manager. According to its provider, fungiwo transfers occupancy calendars to 945 portals.

A channel manager synchronizes prices, rates, and occupancy calendars across portals. Which additional stay-specific functions for registration forms, guest cards, and service cases are covered depends on the system and its extensions.

This is where Oprivia manages and documents registration processes and supporting records across the entire portfolio.

Examples:

  • Vacation rental in Davos: Guest information is collected and the data needed for the visitor tax and Premium Card is prepared in accordance with municipal regulations. Reporting and card issuance use the designated destination procedure; an Oprivia integration is assessed and agreed separately.
  • Business apartment in Zurich: Required information is collected for police reporting and stay verification, including identity verification.

Oprivia maps responsibilities within the system:

  • Who collects guest information?
  • Who verifies it?
  • Who reports it to the municipality?
  • Who archives it?

This makes it clear who is responsible for each task during every stay.

Fictional guest registration responsibilities: The guest enters details, the front office checks them, the reporting owner completes the local step, and the operations manager organizes retention and deletion.
Fictional responsibility assignment: Collection, verification, local reporting, and retention each have an owner. The actual arrangement depends on the location and the business.

Digital guest registration: From paper forms to a standardized process

Many businesses still use a mix of paper registration forms, Excel spreadsheets, and email attachments. Separate municipal portals for visitor taxes add to the administrative workload.

Anyone managing several vacation accommodations is familiar with searching for the right form, questions about correct calculations, and the desire for a consistent solution.

In Germany, special guest registration forms must be retained for one year from the date of departure and destroyed within three months after that period ends. The same storage and deletion periods apply when these requirements are fulfilled electronically.

Bavaria has no uniform statewide requirement for electronic guest reporting. Municipalities can set their own reporting procedures and deadlines for tourism levies and guest cards and make electronic submission mandatory.

Digital solutions and software offer several practical advantages:

  • Guests complete the registration form before arrival, reducing wait times at check-in. Depending on the jurisdiction, legally permitted electronic confirmation or signature procedures can replace a handwritten signature.
  • Automatic plausibility checks reduce errors.
  • Less manual follow-up at check-out and when handling invoices.

Automating guest registration: Check each handoff

A workflow configured for this purpose can link information to a stay, identify missing required fields, and trigger reminders. Before implementation, the operator decides which source holds the authoritative information and who handles discrepancies.

Suppose a corporate reservation names the person who made the booking, while someone else arrives. A successful identity check does not resolve that person's connection to the reservation. An accountable role reviews the discrepancy and records the decision before the relevant next steps proceed.

For each location, track four separate results: information collected, identity checked to the required extent, local reporting step completed, and operational approval granted. A completed form does not confirm receipt by the responsible authority. Digital submission requires an available, agreed reporting channel. If that channel is unavailable or fails, the responsible person records the fallback used and its outcome.

During Oprivia onboarding, the operator establishes which steps the released functionality supports, which rules will be configured, and which connections are available. The article on digital guest identity explains these distinctions. Measure the benefit using the business's own figures: manual handling time per stay, follow-ups for missing information, and the share of cases completed on time.

Data protection, retention, and internal governance in guest registration

Digital guest registration must comply with the applicable data protection rules. The GDPR applies in the EU; Switzerland applies the revised Federal Act on Data Protection (FADP). The GDPR may also be relevant where its territorial scope is met.

Under the GDPR or the Swiss FADP, electronic guest data must be protected through technical and organizational measures appropriate to the risk. These include suitable encryption and access restrictions; logging must be provided according to the nature, scope, and risk of the processing.

Dos and don'ts for guest data

Dos

  • Use data only for legally permitted purposes
  • Observe retention periods for registration forms or guest registers (Germany: 1 year from departure; Austria: 7 years from entry)
  • Allow access only to authorized individuals
  • Keep accurate records of payments and tourist taxes

Don'ts

  • Use guest data for marketing without consent
  • Retain registration forms indefinitely
  • Store passport numbers in Excel without encryption
  • Disclose data to third parties without a valid legal basis or outside the permitted purpose

Guest data may be disclosed only on a valid legal basis and for a specified purpose, for example to fulfill a statutory reporting obligation or as part of properly governed processing by a data processor.

Oprivia implements governance through its system and separates data collection, review, and approval. Role-based access ensures that site managers, front office staff, and external service partners see only the information they need. The reminders and escalations used depend on the release, agreed scope, and operating configuration. A missed deadline needs an accountable role and a verifiable next action. The guide to vacation rental audit trails shows how timestamps, status changes, and corrections remain traceable.

Special rules apply to corporate stays and longer stays: in Austria, additional registration duties arise when a stay exceeds two months. In Germany, the general registration obligation applies to stays in an accommodation establishment lasting longer than six months. Anyone who is not registered for a home in Germany must register within two weeks once the stay exceeds three months.

Managing guest registration across your portfolio with Oprivia

Suitable tools for bookings and reach, such as channel managers, PMS platforms, and review platforms, have long been available. Stay-related administration often presents a different picture: it is spread across paper, email, and various standalone solutions.

  • Oprivia brings together the key processes to close this gap:
  • A shared operational status view for all vacation rentals and property locations
  • Clear responsibilities for every stay so that no tasks are left unattended
  • Traceable processes: registration form completed, guest card issued, tourist tax reported, with every step documented
  • An overview across the portfolio of properties, damage, open questions, and ongoing processes

The implementation process consists of four steps:

  • Analysis of existing processes
  • Configuration of rules for each destination and vacation rental
  • A pilot with selected properties
  • A final evaluation followed by expansion across the entire portfolio

Oprivia is designed for professional rental operators, hosts, and service partners who already use a PMS or channel manager and now want to digitize the compliance side of their rental operations in a controlled way.

Your next step

Discuss your workflow with Oprivia in a no-obligation consultation. Together, we can review the systems involved, local reporting procedures, and a suitable starting point.

Sources and Notes

Editorial and professional context

Sources checked: September 28, 2026. This article explains guest registration in Germany, Austria, and Switzerland. Legal information is based on legislation and official guidance; product information is based on the manufacturers' websites listed below. Recommendations on workflows and responsibilities are editorial guidance for operational practice.

External professional sources

Oprivia sources

Scope and limitations

This article provides general professional guidance and does not replace an assessment of an individual case. Applicable local laws and procedures remain decisive. Digital data collection must be distinguished from successful reporting to an authority; transmission methods and integrations must match the local procedure and the agreed scope of service.

From insight to implementation

Expertise Alone Does Not Run an Operation

Oprivia combines operational expertise with clear responsibilities, digital workflows, evidence, and escalation paths. Together, we determine which recurring processes can be meaningfully digitized and automated while retaining human control wherever responsibility and judgment remain essential.