Cross-Border Hosting: One Listing, Many Rulebooks

A host who learns hosting in one country often carries its habits into the next: the same listing template, the same house rules, the same assumption about nights, taxes and permissions. In the EU, that habit is the main risk. Regulation (EU) 2024/1028 standardises registration numbers, display and reporting, but it deliberately leaves planning, caps and taxes to member states and cities. Two units that look identical on a platform can therefore sit under entirely different legal conditions.

The remedy is to treat each unit as its own compliance file. A file per unit, per country, with its own registration, planning position, cap, tax treatment and contact details, prevents a rule learned in one place being applied in another. It also makes handover easier: a manager, accountant or buyer can see each unit's position without untangling a single blended file.

A registration number issued in one member state has no effect in another. A host with a flat in France and a flat in Ireland needs a French number for the French flat under the French scheme and an Irish number for the Irish unit under the Irish scheme, once that scheme is in force. The same applies to display: the French listing shows the French number, the Irish listing shows the Irish number, and neither number should appear on the other's listing.

Language and documents add friction. Application forms, supporting evidence and renewal notices arrive in the local language and on local timetables. A host who relies on machine translation alone for a legal form should have key terms checked, especially around unit type, operator identity and permitted use. A mistranslated unit type can produce a registration that does not cover the actual use, which verification may not catch until an authority inspects.

Night caps illustrate local divergence clearly. The EU sets no cap, so one city may cap principal-residence lets at 90 nights while a neighbouring country imposes no cap at all but restricts whole-home lets through planning. A host who assumes the stricter cap applies everywhere loses income unnecessarily; a host who assumes the looser rule applies everywhere risks enforcement. For each unit, record the cap, how nights are counted, whether hosted and unhosted nights count differently, and when the counting year starts.

Tax follows the same logic. Rental income, tourist taxes and VAT-adjacent duties are national and often local, with different collection points: some collected by platforms, some declared by hosts, some both. A cross-border host needs a tax note per country, prepared with local advice where the sums justify it, rather than a single tax assumption carried across borders. This guide gives general information only and is not tax advice for any country.

Using one platform across countries does not unify the rules, and using one manager does not transfer accountability. The host remains responsible for registration and for the accuracy of listings, even when a manager creates them. A good management agreement therefore names who registers, who updates listings, who keeps stay logs and who responds to authority queries, per unit. Without that clarity, a manager change can leave listings live with outdated numbers and nobody responsible for updating them.

Platform verification helps but does not replace host diligence. A platform that verifies a number confirms the number exists in a scheme; it does not confirm planning permission, lease permission or tax compliance. Hosts should keep a separate planning note and lease note per unit, and should not treat a verified listing badge as a general approval to host.

Cross-border hosting also means different guest and neighbour expectations. Check-in rules, noise rules, waste rules and emergency contacts are often set locally, and a house manual copied from one country may breach a rule in another, such as a quiet-hours period or a waste-sorting requirement. Localising the manual per unit, even briefly, reduces complaints, and complaints are a common trigger for inspections.

Emergency information deserves particular care. A guest in an unfamiliar city needs a local emergency number, a local contact and clear exit information for that building, not the host's home-country equivalents. Keep that information in the unit as well as in messages, since guests may not have connectivity on arrival.

Start with a register of units: country, city, address, registration number, planning position, cap, tax note and manager, one row per unit. Review it quarterly and before each season. Keep a separate folder per unit for registrations, listings, stay logs and authority correspondence. When adding a unit in a new country, create its file before listing, not after the first booking. That sequence, file first, listing second, is the single habit that prevents most cross-border errors.

Recheck each country's official portal at least annually, and sooner when a law changes. Ireland is the clearest current example of why: a Bill published in October 2026, a register planned for December 2026, and planning guidance still being finalised mean the Irish file for a new unit will change several times in a few months. Treat every country's file as living, and date every note you add to it.