The EU Data-Sharing Rule Behind Every New Register

Registers are multiplying across Europe, and one EU rule explains why the same fields keep appearing in all of them.

Last updated: October 24, 2026

Open three new short-let registers in three European countries and you'll find the same questions: the property, the host, the registration number, the nights sold, the guests. That isn't copying. One EU rule set the reporting template, and national registers were built to receive what the template sends. Once you know the shape, you can prepare for a register before your own market has finished publishing its forms.

Key Takeaways

• The rule is about data, not permission. It obliges platforms to report activity; it doesn't grant anyone the right to let a unit.
• The template explains the sameness. Fields are defined once, and registers are built to receive them in that shape.
• The registration number is the hinge. Where a local rule requires one, a platform has to collect and check it before it keeps selling.
• Local law still decides the licence. Zoning, building rules and safety requirements sit outside this rule and stay local.
• What you control is the file. Property identity, capacity, who's responsible and a number that matches exactly.

What the rule asks of platforms

The duty at the centre of the rule falls on the platforms that facilitate short lets, not on the host. They have to report activity to the competent authorities: which host, which property, at what address, how many nights were sold and to how many guests, and the registration number where one has been issued. It's periodic and it's per property, as published by the EU institutions.

That distinction matters when you're trying to work out who owes what. You aren't being asked to file the report. But the report is assembled from what you entered into the listing, so an address typed slightly differently three years ago becomes a reported field three years later.

The second duty is the one hosts feel directly. Where a local rule requires a registration number, the platform has to collect it and check it, and it can't keep a listing selling without one. That's the mechanism behind the empty field that stops a listing, and it's why the number needs to be right on the listing, not just right in your folder.

There's a plain way to test your own setup against this. Ask what a report built from your listings would say about one property: the address, who's responsible for it, how many nights it sold, and whether a number sits on every channel. If those answers disagree depending on which channel you open, the report inherits the disagreement, and fixing it afterwards means editing each listing one at a time.

Why the registers look alike

A register is built to receive a report, so it inherits the report's fields. When the reporting template is common, the registers converge: the same identifiers, the same capacity question, the same number field, the same period. A country can add requirements on top, but it rarely invents a different core.

This is the part that's easy to misread as harmonisation. Two registers asking identical questions doesn't mean two countries applying identical rules — one can require a licence the other doesn't, and one can cap nights where the other is silent. The data layer is shared. The permission layer isn't.

That's the split worth keeping in your head. localsbnb.com sits on the letting side of it: Airbnb, Booking.com, Agoda and Trip.com connected in one calendar, with each channel's source rate and status beside the dates. It doesn't register a unit, report activity or verify a number, and it can't tell you what your municipality will require. What it does is keep the selling side visible while the compliance side is being sorted out.

What hosts are asked to supply

The field list is shorter than the paperwork around it suggests. A property needs an identity: the address as the register holds it, the unit, and the capacity in guests and in bedrooms. A host needs an identity and, in most registers, a person who is responsible for the unit day to day.

Then the number. This is where small errors get expensive, because the number is a string that has to match. Prefixes, spacing and letter case are all part of it, and a register that receives a near-match records a mismatch. Copy it from the document that issued it rather than retyping it from memory.

Two more fields appear often enough to plan for: the period the unit was available, and the number of nights actually sold in it. Both come out of your own calendar, which means the calendar is now a compliance source as well as an operations tool. If your records can't answer "how many nights did this unit sell last quarter", that's the gap to close first.

Multi-unit hosts carry a second version of the same problem. A number belongs to a property, so a list that sorts units by nickname works well for operations and badly for a register, which knows addresses. Keep one line per property, keyed to the address the register uses, with the responsible person beside it. When a unit changes hands or a co-host takes over, that line is what you edit.

Confirm the current text and local implementation with the competent authority before you build a file around any of this. The rule sets a frame; the forms in your market decide the details.

What it does not change

It doesn't create a right to let. A registered unit in a building that prohibits short lets is still a unit that can't be let, and a number on a listing doesn't override a lease, a co-ownership rule or a planning decision.

It doesn't set tax. Tourist tax, income treatment and filing cycles belong to other rules, and they don't move because the reporting template is shared.

It doesn't make one registration cover several units. Each property gets its own entry and its own number, which is the practical reason multi-unit hosts end up with a stack of them.

And it doesn't standardise enforcement. Two markets with the same form can check it at completely different intensities, and the pace of that is a national decision. Confirm the current text and local implementation rather than assuming your market will behave like the one next door.

What that leaves you is a preparation list, not a compliance verdict. Know which of your units are registered, keep each number where you can find it in ten seconds, and make sure the address on every listing matches the address on the paperwork. None of those is a legal question, and all of them are why a routine check turns into a week of correspondence.

FAQ

Does the rule mean I can let a unit anywhere in the EU?

No. It governs how activity data moves between platforms and authorities. Whether a specific unit may be let short-term is still decided by local licensing, building rules and whatever the property's own documents allow.

Is the registration number the same format everywhere?

No. The rule doesn't impose one numbering scheme, so each register issues its own. That's why the number has to be copied exactly and stored per property rather than remembered as a pattern.

Do I have to report anything myself?

The reporting duty sits with the platforms. Your side is supplying accurate data and keeping it current, which is less work but easier to get wrong, because a stale address in a listing travels into the report without anyone checking it.

The rule is boring in the way that infrastructure is boring: it changes who holds which field, and then it stops being news while still shaping every form you fill in. localsbnb.com is where the four channels and their source rates already share a calendar, which is the half of this that keeps changing while the paperwork catches up.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Which fields a platform must report, which register applies to a unit and when each duty starts depend on the current text and on national implementation. Confirm the current text and local implementation with the competent authority and the terms of each platform you use before you act.