A late-arriving booking is not usually the problem. The problem is discovering, the next morning, that the guest details were due to a police portal, local authority or tourism register before the guest checked in. The question, “when must hosts report guests?”, has no single UK or Europe-wide answer. It depends on where the accommodation is located, which authority governs it and whether the stay falls within a regulated category.
For hosts and property managers, the practical rule is simple: treat guest reporting as a time-sensitive part of every reservation, not an admin task to catch up on at the end of the week. That approach protects your business when bookings arrive through multiple channels, guests check in late, or local rules change.
When must hosts report guests?
Hosts must report guests whenever the law or a local registration scheme requires accommodation providers to submit visitor details to a public authority. In many European destinations, this applies to short-term lets, holiday homes, serviced flats, guesthouses and hotels. The authority may be the police, municipality, tourism office, statistical body or tax authority.
The reporting deadline is set locally. Common requirements include submission before check-in, on the day of arrival, within 24 hours of arrival, or by a scheduled daily deadline. Some locations also require a departure update, a periodic occupancy declaration or separate tourist-tax reporting.
This is why “I only rent one property” is rarely a reliable exemption. A registration duty may apply regardless of portfolio size, booking volume or whether the reservation came from a platform, a direct website or a phone enquiry. Professional managers face an extra layer of complexity because each property can sit in a different municipality or country with different deadlines and submission methods.
Your first task is to identify the rule that applies to the property itself, rather than relying on the guest’s nationality or the channel used to book. A flat in one town may require same-day reporting through a police system, while a nearby property may require a municipal guest book and monthly declaration.
The deadlines that matter in practice
A reporting obligation usually begins at arrival, but the operational work begins much earlier. You need complete, validated guest information before the deadline, which means collecting it during booking or through a secure pre-arrival form.
Before check-in
Some authorities require information to be submitted before a guest receives access to the property. This is particularly relevant for self check-in accommodation, where there may be no reception desk to inspect documents on arrival. If the local process requires identity verification, make sure your check-in workflow accounts for it rather than assuming an online form alone is enough.
For direct bookings, build the data request into confirmation messages. For OTA and property-management-system bookings, check exactly which guest fields are passed through and which details still need to be collected. A booking containing only a lead guest name and email address may not meet the reporting standard.
On the day of arrival
Same-day reporting is common. In these areas, a late-night arrival does not remove the duty – it simply makes manual administration more fragile. Hosts need a clear cut-off process for arrivals, amendments and no-shows.
A cancelled booking should not be reported as an occupied stay. Equally, a guest who arrives a day later than planned may need an updated arrival date. Reporting the original reservation without checking actual occupancy can create a mismatch between your guest book and the authority record.
Within 24 hours of arrival
A 24-hour deadline can sound generous until you manage several properties, receive weekend bookings and have guests who do not complete their details promptly. The risk is not the deadline itself; it is the chain of hand-offs between booking source, guest communication, document collection and submission.
Use the most conservative interpretation where the published rule is unclear. If an authority says “within 24 hours”, establish whether that means 24 hours from check-in time, midnight on the arrival date or the next calendar day. Government portals often enforce their own cut-off logic, which may differ from how the rule is described.
At departure or on a regular schedule
Arrival reporting is only one part of compliance in certain areas. Departure dates, length of stay, occupancy figures and tourist-tax information may need separate reporting. Some systems require daily transmissions; others allow a monthly return, provided each guest registration is recorded correctly.
Keep these duties separate in your workflow. A guest record submitted to a police portal does not automatically fulfil a municipal occupancy return or tourism-tax declaration. The same data may support both processes, but the deadlines, fields and responsible authority can differ.
What guest information do hosts normally need?
Requirements vary, but authorities commonly request the lead guest’s full name, date of birth, nationality, document type and document number. They may also require place of birth, gender, address, date of arrival, departure date, number of guests and the accommodation identifier.
Do not collect every possible field simply because it may be useful later. Guest data is sensitive, and GDPR principles still apply. Collect the information required for the legal purpose, explain why you need it, restrict staff access and retain it only for the applicable period.
The practical challenge is completeness. A single missing document number or an invalid date format can prevent submission, especially where government systems reject records rather than flagging them for later correction. Validate fields at the point of collection and retain an auditable record of what was submitted, when it was submitted and whether the authority accepted it.
Who is responsible: the owner, host or manager?
Responsibility usually sits with the registered accommodation operator or the person legally operating the property. However, management contracts can allocate the day-to-day work to a property manager. That does not necessarily transfer legal accountability.
If you manage properties for owners, document who holds the registration, who has access to the official portal or digital certificate, who collects guest data and who resolves rejected submissions. This matters most when an owner changes manager or a new property joins your portfolio mid-season.
A strong operating model gives owners visibility without asking them to chase every arrival. Managers need permissions that reflect their role, while the business needs a consistent guest book and evidence trail across all properties.
Common reporting mistakes that create avoidable risk
The most frequent failure is assuming booking data equals registration data. Booking platforms often provide partial information, and names entered at reservation stage may not match the documents presented by arriving guests.
Another common mistake is relying on a single staff member to submit records manually. This works until they are on leave, a portal password expires or a busy Friday produces a queue of incomplete check-ins. Manual entry also increases transcription errors, particularly for document numbers and non-Latin names.
Managers should also watch for duplicate reservations, property changes, extensions and split stays. If a guest moves from one property to another, each stay may need its own record. If a booking is extended, the departure date may need updating. A clean calendar is not enough – the compliance record must follow the actual stay.
Finally, do not confuse record retention with reporting. Keeping a spreadsheet or copy of a passport after the deadline has passed does not correct a missed submission. It may even create unnecessary data-protection exposure if it is stored insecurely or kept longer than required.
Build a reporting workflow that can cope with real bookings
The most reliable approach is to connect guest reporting to the reservation lifecycle. New bookings should trigger data collection. Completed guest details should be checked against the relevant property rules. Records should then be submitted on the required schedule, with exceptions visible to the person responsible for resolving them.
Automation is especially valuable where you receive bookings from direct channels, OTAs, PMS tools, iCal calendars, APIs and webhooks. Without it, every new channel creates another place where guest details can be lost or copied incorrectly.
GuestAdmin centralises booking intake, guest registration and scheduled authority submissions so hosts do not have to rebuild the process for every reservation. It also provides securely archived guest books, real-time booking visibility and support for multi-property and digital-certificate workflows. For an independent host, that means less repetitive entry. For a manager, it means a clearer view of which properties, arrivals and submissions need attention.
Before relying on any system, test it against a small set of real scenarios: a same-day booking, a late arrival, a cancellation, a change of dates and a booking with incomplete guest details. The right workflow should show what happened at every stage without forcing you to search across inboxes, portals and spreadsheets.
A practical compliance check for every property
For each accommodation, confirm the registering authority, required guest fields, submission deadline, accepted submission route and record-retention period. Also check whether tourist-tax, statistical or occupancy reports are separate from guest registration.
Review this information whenever you add a property, enter a new municipality, change your legal operating structure or adopt a new booking channel. Regulations and government portals can change, and an old checklist may be less reliable than no checklist at all.
Where the rule is unclear, obtain confirmation from the relevant authority or a qualified local adviser. The cost of checking is usually small compared with correcting a missed deadline, an incomplete guest book or a failed inspection.
Good compliance should not depend on remembering what happened after a busy weekend. Once reporting is built into every booking from the start, you can spend less time chasing documents and more time running the accommodation your guests came to enjoy.