EU Single Digital Entry Points: How Each Country Receives Rental Data

A Single Digital Entry Point is the single official channel in each member state through which platforms send their monthly short-term rental activity data under Regulation (EU) 2024/1028. Hosts generally do not file monthly returns to the entry point themselves; platforms do the reporting, while hosts register separately and keep records that match what is reported. The entry point exists so that authorities receive standardised data through one door instead of chasing separate reports from every platform.

Think of it as a post room rather than a regulator. It receives, checks and routes data to the authorities that need it, such as tourism, housing or tax bodies. It does not grant hosting permission, set night caps or decide tax. Confusing the entry point with the registration authority is a common early mistake, and it leads hosts to send the wrong form to the wrong body.

Before a common channel, an authority that wanted a picture of short lets in its area might need data in different formats from different platforms, with different identifiers for the same property. A single entry point standardises the format and ties reports to registration numbers, so the same unit can be recognised across platforms. That makes enforcement more targeted: authorities can focus on units with no number, numbers that do not verify, or reported nights far above a local cap.

Standardisation also helps honest hosts indirectly. When data is consistent, a host whose platform reports correctly is less likely to be confused with a neighbour whose listing carries a wrong number. The entry point does not judge hosts; it makes the underlying data reliable enough that judgements made elsewhere rest on firmer ground.

Monthly platform reports cover activity for listed units: which registered units were let, for which periods, and through which platform. The exact fields follow the regulation and national implementation, and hosts should not try to reconstruct the technical schema from this guide. What matters practically is that the reporting period is monthly, the unit is identified by its registration number, and the receiving body is the entry point of the member state where the unit sits, not the country where the platform is based or the guest lives.

Hosts can prepare for this flow without seeing it. Keep a simple monthly log of your own: unit, guest stay dates, platform, payout reference and any cancellation. If an authority later queries a month, that log lets you answer in minutes. If you host through several platforms, keep one combined log rather than relying on each platform dashboard alone, since dashboards change and old data can become hard to retrieve.

Registration portals collect host applications and issue numbers. Entry points collect platform activity data. In some countries the same public body may run both, but the functions remain distinct, and a host who has registered has not thereby filed any activity report. Conversely, a platform reporting activity for a unit does not register that unit. Both halves must be in place: a registered unit with reported activity, or, where direct booking bypasses platforms, whatever national arrangement covers non-platform stays.

Direct bookings deserve a separate check. A host who takes bookings only through their own website may fall outside platform reporting, but that does not remove registration, planning or tax duties. National law may impose a separate declaration for direct stays. Never assume that avoiding a platform avoids the framework; check the national scheme for direct-booking hosts before relying on that route.

A host with units in two member states deals with two entry points through their platforms, one per country. A platform reports French activity to the French entry point and Spanish activity to the Spanish entry point, even if the host lives in a third country. Hosts should therefore organise records by country and by unit, not by host or by platform alone. A single spreadsheet with a country column, a unit column and a registration number column prevents the most common cross-border mix-up: applying one country's number to another country's listing.

Guests and intermediaries add further edges. A property manager acting for several owners still needs a number per unit, and a host who changes manager should confirm that listings and registrations were updated, not merely handed over. The entry point sees units and numbers, not management arrangements, so administrative handovers that forget the registration layer create visible gaps in the data.

If a platform tells you a report failed or a number did not match, start with the registration record: is the number correct, is the unit address identical, is the registration still valid? Then check the listing: does it show the same number, for the same unit, without typos? Only then ask the platform what it sent and to which entry point. Working in that order avoids blaming the entry point for a typo made at listing time.

Keep evidence of corrections. Save the corrected registration confirmation, the updated listing view and any platform message confirming verification. If an authority later asks about an earlier month, that file shows when the error was found and fixed. As with the rest of this cluster, verify the current entry point arrangements on the official portal for the country concerned, since implementation details are still settling in late 2026.