Guest Registration & Police Reporting in Europe: the Country-by-Country Guide

Why this obligation exists everywhere

Guest registration laws descend from two sources: police records of foreign nationals (many countries implement Article 45 of the Schengen Convention, which obliges lodging providers to have foreigners fill in declaration forms) and tourism statistics plus tourist tax collection. That's why in several countries a single submission feeds both the police and the statistics office — and calculates the city tax you owe per guest-night.

The practical consequence for a hotelier: for every guest (in some countries only foreign guests, in most — everyone), you must capture identity document data and submit it to a government portal, usually within 12–24 hours of arrival. Manually, that means retyping passport fields into a web form every single day of the season.

The systems, country by country

Names, portals and deadlines as commonly applied in 2026. Rules change and some regions add local requirements — always confirm with the official registry for your property.

What data you must capture

Across systems the required fields are remarkably consistent — which is exactly what makes automation feasible:

• Full name, date of birth, nationality, gender
• Identity document type and number (passport or national ID)
• Arrival and departure dates, number of nights
• Sometimes: place of birth, address, visa number, or the exemption category for tourist tax (children, disabled guests, etc.)

This is precisely the data an online check-in flow with document scanning collects anyway. When a guest scans their passport during self check-in, the MRZ is machine-read — no typos, no misread handwriting — and every field the registry needs is already structured.

The real cost of doing it by hand

Take a 12-unit apartment property on the Adriatic with a 70% summer occupancy and average 2.4 guests per booking. That's roughly 400–500 individual guest registrations over a season. At three to four minutes each (find the passport photo, open the portal, log in with the certificate, type, submit), registration alone consumes 25–35 hours of pure clerical work — compressed into evenings, because guests arrive in the afternoon and the clock is ticking.

Then there's the downside risk. Fines for late or missing registrations vary widely but are material everywhere: typically hundreds of euros per violation, and in some jurisdictions thousands for repeat offences — with inspections often triggered by tourist tax audits. One missed batch of registrations can cost more than a year of automation software.

How automated reporting works

1. Booking sync. The reservation arrives from Booking.com, Airbnb, Expedia or your channel manager with dates and guest count.
2. Identity capture. Each guest verifies their ID in the online check-in flow before arrival — including every member of a group, not just the booker.
3. Validation. The software checks the data against the registry's format rules (document types, country codes, tax exemption categories) while the guest is still in the flow, so errors are fixed by the guest, not by you.
4. Submission. The report is filed to the national system automatically, and the confirmation is stored with the booking.
5. Tourist tax. Where applicable, the per-person-per-night tax is calculated, charged to the guest during check-in, and reflected in the monthly reconciliation.

The property owner's involvement drops to reviewing a dashboard — and handling the occasional guest whose document fails verification, which the system flags before arrival rather than after.

Frequently asked questions

Do I need to report children?

In most all-guest systems (Slovenia, Croatia, Italy, Austria), yes — minors are registered, typically under a parent's booking, and are usually exempt from or discounted on tourist tax. Spain's SES.HOSPEDAJES reports guests 14 and older.

Can I let guests check in before the report is filed?

The safest design is the reverse: the door code is released only after every guest in the party has completed ID verification. That single gate makes "unregistered guest inside" structurally impossible — and it's how ReceptionGO's flow works by default.

What if a guest refuses to provide ID?

You are legally entitled — in fact required — to insist; a guest who won't identify themselves cannot lawfully be accommodated in these jurisdictions. In practice refusal is extremely rare when verification happens in a normal online flow before arrival.