Regulation 2024/1028: What It Changes for Hosts and Platforms

From 20 May 2026, Regulation (EU) 2024/1028 gives the EU a shared vocabulary and a shared data pipeline for short-term rentals. Registration procedures, where a member state has one, gain a common shape: an identifier for each unit, display on listings, verification by platforms and monthly reporting to a Single Digital Entry Point. Before this regulation, a platform operating in ten countries faced ten unrelated information regimes; after it, the information flow follows a recognisable pattern even though national conditions still differ.

What does not change is equally important. The regulation sets no EU night cap, no EU tax rate and no EU planning permission. A city that capped principal-residence lets at 90 nights keeps that cap. A country that taxes short-let income keeps its tax code. Hosts who read the regulation as deregulation, or as a single EU licence, will misunderstand both its purpose and its limits.

The regulation works through roles rather than brand names. A host offers a unit for short-term accommodation, a platform intermediates the booking, and a unit is the property offered. Those roles matter because duties attach to the role: verification and reporting sit with platforms, registration sits with hosts, and receiving and using the data sits with authorities through the entry point. A person who both owns and lists directly may still need to follow host duties even without a platform in the middle, depending on national implementation.

Edge cases deserve care. A room in an occupied home, a whole flat, a rural cottage and a serviced apartment may all be units, but national schemes can treat them differently, for example by exempting some forms of hosting or by imposing extra conditions on others. The regulation supplies the framework; the member state scheme decides the exact boundary. Check the national scheme for the property type, not just the EU text.

A host usually meets the duties in this order: register the unit where required, receive a number, add that number to listings, keep the listing details consistent with the registration, and keep records that match reported activity. A platform meets its duties in a parallel order: ask for the number, verify it, display it, monitor listings, and report monthly. When either side skips a step, the other side feels it quickly, either as a blocked listing or as an authority enquiry.

Timing is part of compliance. Registration should come before the first advertised night in a scheme that requires it, not after the first booking arrives. Verification delays, document requests and portal outages are foreseeable, so starting early protects the launch date. A host who lists first and registers later risks a period in which the listing is visible without a valid number, which is exactly the situation the framework is designed to prevent.

When a number cannot be verified, a platform cannot simply display it and hope. Under the framework, platforms must take steps that can include asking the host to correct the number, suspending the listing until verification succeeds, and, where national law requires it, removing listings that remain unverified. Hosts should treat a verification failure as a registration problem to fix at source, by checking the number character by character, confirming the unit matches the registration, and contacting the registration authority if the record itself is wrong.

Delisting is not the only consequence. Repeated or systematic failures can draw authority attention to a host or a platform, and reported activity data gives authorities a way to compare what was advertised with what was registered. Keeping listings accurate, removing sold or withdrawn units promptly, and updating a registration when a unit changes hands or changes use all reduce the chance of a mismatch turning into a formal case.

Monthly reporting creates a dataset that authorities can use for enforcement and for policy, such as understanding how many nights are let in a neighbourhood. That dataset is powerful, which is why the regulation also sets boundaries on what is collected and how it is used. Hosts do not need to master data protection law to comply, but they should understand that reported nights, listing details and registration numbers are now linked in official systems in a way that informal hosting never was.

For practical purposes, the lesson is consistency. Use the same address format, unit description and operator details across registration, listings and tax records wherever the forms allow it. Inconsistency is usually innocent, caused by abbreviations or old addresses, but it is also the most common trigger for a query. A short annual check that all three records still agree is cheap insurance against a long correspondence later.

Because member states implement the framework through their own laws and portals, the EU text alone is never the final word for a specific property. Before acting, confirm whether the member state has a registration procedure in force, whether the property type is covered, what the entry point is, and what local planning or tax rules add. Official sources are listed below; a platform help page or a forum post is not a substitute for the registration portal itself.

Date labels matter here. Rules described as applying from 20 May 2026 may still be rolling out in a particular state in late 2026, and a national law published in October 2026 may not yet be in force. Note the date you checked, keep a screenshot or confirmation of the portal page, and recheck before a new season or a new unit. This guide was last verified on 26 October 2026, and later changes should be expected.