Monthly Reporting to EU Entry Points: What Hosts Should Know

Monthly reporting under Regulation (EU) 2024/1028 gives authorities a current picture instead of an annual snapshot. A yearly return would let an unregistered unit operate for months before appearing in any dataset; a monthly flow surfaces it quickly. For hosts, the consequence is that record keeping must also be monthly in practice. A host who reconciles records only at tax time will discover discrepancies far too late to explain them easily.

Monthly also means seasonal patterns become visible. A unit let heavily in summer and empty in winter looks different from a unit let steadily all year, and both look different from a unit whose reported nights exceed a local cap in a single month. Authorities can therefore ask focused questions about a specific month rather than opening a general investigation, which is faster for everyone when the host's own records are in order.

Platforms report activity for listed units to the entry point of the member state where the unit is located. In general terms, that activity includes which units were let and when, tied to registration numbers. Platforms do not report a host's private finances, guest identities beyond what the scheme requires, or activity on other platforms. Hosts should not expect one platform's report to cover stays booked elsewhere, which is why a combined personal log matters.

Cancellations, alterations and refunds are the usual source of confusion. A booking made in one month, altered in the next and cancelled in a third can appear in reports in ways that do not match a simple calendar view. Keeping booking references, alteration messages and refund records alongside the stay log lets a host explain those movements without guessing months later.

A practical monthly routine takes under half an hour for a single unit: list stays that started or ended in the month, note the platform and booking reference for each, compare the list with payout statements, and file any cancellation or alteration evidence with that month's folder. For several units, repeat the routine per unit, not per platform, so that a unit let through two platforms appears once in your records with both channels noted.

Small mismatches are normal and explainable. A stay spanning a month boundary, a guest who extends by a night, or a platform that records check-in and check-out dates differently can all create a one-night difference. Large or repeated mismatches deserve investigation: a missing registration number, a duplicate listing, or a unit let under another host's account. Investigate while messages and statements are fresh, not at year end.

Direct bookings sit outside platform reporting by definition, since no platform intermediates them. That gap does not make direct stays invisible to other duties: registration, planning, tax and any national declaration for direct stays still apply. Some hosts mistakenly believe that moving bookings off platform removes them from the framework entirely. It removes one reporting channel; it does not remove the registration number, the display duty where it applies to advertisements, or the tax return.

Hosts who mix channels should keep the clearest records of all. One log with a channel column, direct or named platform, prevents double counting and prevents a direct stay being mistaken for an unreported platform stay. If national law requires a separate direct-booking declaration, file it on its own timetable and keep the filing receipt with the same month's records.

An authority query usually names a unit, a month and a discrepancy, such as reported nights above a cap or a listing without a matching registration. Answer with documents, not explanations alone: the registration confirmation, the stay log for that month, platform statements and any alteration or cancellation evidence. A concise, dated reply that attaches the relevant month's file resolves most queries faster than a long general letter about hosting in general.

If the query reveals a genuine error, correct it at source: update the registration, correct the listing, or amend the relevant return where the system allows it. Then keep a note of the correction date and method. Authorities distinguish between an error found and fixed by the host and an error found only after repeated queries, so prompt correction is worth more than a perfect first record.

Busy seasons are when records slip, so design the routine for the busiest week, not the quietest. Use one folder per unit per year, with a subfolder per month, and file statements the day they arrive rather than in a batch. Automate what you can: download statements monthly, photograph paper receipts, and keep a single running log instead of several notebooks. The goal is not perfect bookkeeping; it is a file that lets you answer a question about any month within a day.

Finally, recheck the national reporting position at least once a year. Entry point arrangements, field requirements and direct-booking declarations are still bedding in during 2026, and a change in one country does not automatically change another. This guide was last verified on 26 October 2026; confirm the current position on the official portal before relying on it for a new season.