What really changed on 20 May 2026

Regulation (EU) 2024/1028 was adopted on 11 April 2024 and published in the Official Journal on 29 April 2024. It entered into force on 20 May 2024, with most obligations applying from 20 May 2026, when the two-year runway has closed.

The regulation harmonises three things that used to be fragmented across 27 different national approaches.

• Registration. Where a Member State or local authority runs a registration scheme, each short-term rental unit must have a unique registration number. The regulation doesn't force every country to create a scheme, it standardises how schemes work where they exist.
• Verification. Platforms including Airbnb, Booking.com, and Vrbo must systematically verify the registration number before a listing is published. Random self-declaration is no longer enough.
• Data sharing. Platforms transmit activity data (listing address, number of nights rented, guest counts) to the competent authority through a Single Digital Entry Point in each Member State. For larger platforms the reporting cadence is monthly.

The framework covers an estimated 4 million short-term rental properties across the EU. For scale: guests booked 854.1 million nights in EU short-term rentals during 2024, an 18.8% increase over the prior year, rising to 951.6 million nights in 2025, up 11.4% year over year (Eurostat).

What the regulation explicitly doesn't do: ban short-term rentals anywhere, cap nights, or override local zoning. Member States keep full control over those decisions. What changed is that the decisions are now enforceable at scale.

The three checks

Check 1: does your registration number match everywhere?

This is the check that most commonly fails, and the failure is automated.

Your registration number as entered in the platform's regulatory field has to match your entry in the relevant national or regional registry exactly. Not approximately. Not with a typo. Not a number that was valid two years ago under a scheme that has since changed.

Where hosts get this wrong:

• Reusing one number across multiple listings. The regulation assigns a registration number per rental unit. If you run three apartments in the same building and enter the same number for all three, two of them are non-compliant even if the number itself is valid.
• Using an outdated number after a national scheme changed. This isn't theoretical. In Spain, Royal Decree 1312/2024 entered into force on 2 January 2025 and made the NRUA number mandatory from 1 July 2025. Then on 21 May 2026, Spanish Supreme Court ruling STS 620/2026 annulled the national NRUA registration layer entirely. The number Spanish hosts must now display is the regional tourist-register code: VFT in Andalusia, HUT in Catalonia, ETV in the Balearics, or VUT, VV, or VT depending on the region. Hosts who entered an NRUA number and haven't updated it are now displaying an annulled identifier. The data-sharing obligations and the EU-level requirements were unaffected by the ruling.
• "Pending" or "applied for" entries. A pending application isn't a registration number. Platforms verify against the registry, and a pending status returns no match.

What to do this week: open your listing's regulatory information field on every platform you use (Airbnb, Booking.com, Vrbo, your direct site) and compare each entry character by character against your registry record. If you manage several units, do it per unit, not per account.

Check 2: can you evidence house rules, capacity, and safety information?

Registration is the visible layer. Underneath it, enforcement is decentralised: each Member State sets its own penalties, and local authorities inspect against local rules. What they inspect for is broadly consistent across EU jurisdictions.

• Maximum occupancy. Your listing capacity must match what your registration permits. A property registered for four guests that sleeps six on the listing is a discrepancy an authority can now see, because the platform reports booking data including guest counts.
• House rules that reflect local ordinances. Quiet hours, party prohibitions, and noise limits are set by the municipality, not by you. In cities running noise complaint schemes, documented house rules are part of what a host is expected to demonstrate. Written rules that guests have actually seen are stronger evidence than rules that exist only in the listing description.
• Safety information. Emergency exit route, fire extinguisher location, and the European emergency number 112 are standard expectations across EU jurisdictions. Requirements vary by country and property type, and some Member States require documented evacuation information for properties above a certain floor or capacity.
• Waste separation. Mandatory in most EU cities and increasingly enforced with fines that land on the property owner, not the guest who put glass in the wrong container.

The practical question isn't whether you have these rules. It's whether you can show that guests received them. Rules buried in a listing description that a guest scrolled past at the moment of booking are weaker evidence than rules delivered in a guest-facing document that's timestamped, accessible, and version-controlled.

Check 3: can guests access critical information without you messaging it?

This check exists because of a second, unrelated enforcement layer: platform message monitoring.

Airbnb uses automated systems to detect off-platform communication attempts: email addresses, external links, and requests to move a booking off the platform. Listings can be suspended for AI-detected policy breaches including sharing contact information or promoting off-platform bookings. This is a separate risk from the EU regulation, but it lands on the same host at the same time.

The result is a squeeze. Regulatory pressure requires you to document more information for guests. Platform policy makes messaging that information riskier. Sending a PDF manual, a Google Drive link, or your direct email through platform chat is exactly the pattern automated detection is built to catch.

The workable answer is a guest-facing document that lives outside the message thread and doesn't need a link that triggers detection: a QR code in the property, a link shared through the platform's own approved channels, or a guidebook link included in your listing where platform rules permit it. See also our guide on reducing guest questions.

Where a digital guidebook fits

A digital guidebook isn't a compliance product, and no guidebook makes an unregistered property legal. What it does is solve the documentation and delivery problem that sits underneath compliance.

• One source of truth for your legal and operational information. Registration number, maximum occupancy, house rules, safety information, waste separation instructions, and emergency contacts live in one place rather than scattered across a listing description, a PDF, three WhatsApp threads, and a laminated sheet on the fridge.
• Guests actually receive it. A QR code in the property means guests get the information at the moment they need it. No message thread, no attachment, no external link sent through platform chat.
• One update propagates everywhere. When a local rule changes, and in the current EU environment they do, you edit once. Every guest with the link sees the current version. This matters more than it sounds: the alternative is discovering that eight of your ten properties still display the pre-May house rules.
• Language coverage. Guests from 27 Member States don't all read English house rules with the same comprehension. Rules that weren't understood are functionally rules that weren't communicated.

PlacePilot was built as a mobile-first for European hosts: one guidebook, a QR code guests scan on arrival, and expiring access links that make sensitive information visible only during the booking window. It's operated by Novi Labs SRL, a Romanian company, with guest data handled under EU jurisdiction, which is its own compliance consideration when the information you collect includes guest details.