Spain's SES.Hospedajes, explained: what every operator must report
If you run accommodation in Spain, SES.Hospedajes is now part of daily operations. Since Royal Decree 933/2021 became enforceable on 2 December 2024, operators have to collect a detailed set of guest data and report it to the Ministry of the Interior through the SES.Hospedajes platform. Get it wrong, and the fines are real.
Here is a clear, practical overview of what the rule asks, who it applies to, and how to keep up without turning your front desk into a data-entry team.
What SES.Hospedajes is
SES.Hospedajes is the digital system run by the Spanish Ministry of the Interior where accommodation providers register their guests and reservations. It replaces the older, lighter reporting obligations with a much broader data set, reported electronically and on a tight clock.
Who has to comply
The obligation is wide. It covers hotels, tourist apartments, campsites, rural accommodation and short-term rentals. Crucially, the booking channel does not matter: whether a guest books through Airbnb, Booking.com or directly with you, you as the operator are responsible for reporting. The platform does not do it for you.
What you have to report
Royal Decree 933/2021 expands the data set well beyond a name and an ID number. In practice you are collecting and submitting information across several categories, including:
- Guest identity: full name, document type and number, nationality, date of birth.
- Contact details: address, phone and email.
- Stay details: property, dates of check-in and check-out, number of guests.
- Reservation and payment details: how the booking was made and how it was paid, including card or account information.
Children are included too, with the data provided by the adult responsible for them. Records generally have to be kept for around three years.
The deadlines that catch people out
There are two reporting moments, and both are time-sensitive:
- Reservation data has to be submitted when the booking is made.
- Check-in (traveller) data has to be submitted within 24 hours of the guest's arrival.
Miss the window, submit incomplete data, or send it late, and it counts as an infringement.
The fines
Penalties scale with severity. Minor infringements, such as late or partial submissions, start at around 100 to 600 euros. More serious breaches of the Decree can run from 601 euros up to 30,000 euros. For a portfolio of properties processing dozens of check-ins a week, the exposure adds up fast.
The common pitfalls
Most compliance problems are not refusals to comply. They are operational:
- Assuming the OTA (Airbnb, Booking) handles the reporting. It does not.
- Re-typing the same guest data into yet another government portal by hand.
- Missing the 24-hour window during busy arrivals or out-of-hours check-ins.
- Inconsistent or incomplete fields that turn into "mild infringements".
In other words, the hard part is not understanding the rule. It is running it, correctly, for every guest, every day, across every channel.
How to stay compliant without the admin overload
The realistic answer is automation. If guest data is captured once, cleanly, at booking and check-in, and then submitted to SES.Hospedajes automatically within the deadline, the obligation stops being a daily risk and becomes a background process.
This is exactly the kind of structural problem Guest OS is designed to solve. We start with the regulation and build the guest flow around it, so legal registration like SES.Hospedajes is handled as part of the journey from booking to key, not bolted on at the desk. Guest OS is designed to map each market's own requirements, including the Spanish SES.Hospedajes and the Dutch Nachtregister, into one automated flow.
If you operate in Spain and want registration to run itself, we would like to talk.
This article is general information, not legal advice. Rules and thresholds can change, so verify the current requirements for your situation with an official source or a qualified advisor.