Who Exactly Has to Be Registered: Minors, Groups and Guests Who Never Signed the Booking

Most check-in mistakes in Spain are not platform problems. They are counting problems. And almost all of them come from one confusion worth clearing up before anything else: fourteen is the age at which a guest has to sign the entry form, not the age at which a guest starts to exist for the register.

Article 4.2 of Royal Decree 933/2021 says the *parte de entrada* must be signed by every person over fourteen, and that for children under fourteen "sus datos serán proporcionados por la persona mayor de edad de la que vayan acompañados" — their data is supplied by the accompanying adult. A three-month-old baby has no document and signs nothing. The baby still goes in the register.

Try it right now — free, no signup →

That distinction has a price tag. Not having the required registers is a serious infraction under article 36.20 of Organic Law 4/2015, punishable with 601 to 30,000 €. Irregularities in filling them in, or communications sent late, fall under article 37.9 as a minor infraction, 100 to 600 €. So a family of four where you only registered the two adults is not a rounding error: depending on how an inspector reads it, you are in one bracket or the other, and both are worse than the ninety seconds it would have taken to add the kids.

Below is the decision test I'd keep taped inside the office door.

The one-line rule: a bed, not a signature

The obligation attaches to the person who spends the night in the accommodation, not to the person who booked it, paid for it or signed the rental contract. Ask yourself one question per human being who walks through the door:

> Is this person sleeping here tonight as part of a paid stay?

If yes, they belong in the register — regardless of age, nationality, whether they appear on the booking, whether they paid a cent, or whether they can hold a pen. Everything else (who signs, which document number goes in, what fields you can fill) is a downstream question about *how* you record them, not *whether* you record them.

That framing kills the three most common failure modes at once.

Minors: three different cases, one obligation

All minors are registered. What changes is the paperwork around them.

Under 14, with their own document. Increasingly common — many Spanish children have a DNI before 14, and foreign minors routinely travel on their own passport. Register them with their own document. They do not sign; the accompanying adult provides and signs for the data.

Under 14, no document at all. Register them with their identifying data and link them to the responsible adult. Annex I of the decree explicitly asks for the *"relación de parentesco entre los viajeros (en el caso de que alguno sea menor de edad)"* — the relationship between travellers when one of them is a minor. That field is not decoration: it is the thing that makes a child's record coherent when the child has no ID number of their own.

Fourteen or over. They are, for these purposes, a normal traveller: their own document, their own signature on the entry form. A sixteen-year-old travelling with their parents is not "a child on the booking" — they sign like everyone else.

The edge case nobody plans for: a guest who turns 14 during the stay. The obligation is fixed at check-in, when the entry form is generated, so you record them as they were on arrival. If the stay is long and the record is later amended, do it in the platform rather than editing paper after the fact.

Groups: one booking, many entry forms

A booking is a commercial object. An entry form is a personal one. Eight people arriving on one reservation produce eight records, not one record with a note saying "+7".

This is where large groups quietly go wrong, and the pattern is always the same: the lead guest sends a photo of their own ID, the manager registers that, and the other seven are handled "at arrival" — which in practice means never, or at 11 p.m. by someone who then forgets to submit. The decree gives you 24 hours from the start of the stay to transmit the data (article 6.3: "de manera inmediata, y en todo caso en un plazo no superior a 24 horas"), and that clock does not restart for the stragglers.

For group-heavy properties, two habits fix it:

Collect before arrival, not at arrival. Ask for every ID at booking confirmation, not at the door with suitcases in the corridor.
Count the beds against the register. If the booking says 8 pax and the register shows 5 records, the stay is not checked in. Make that comparison the definition of "done", not the fact that someone got the keys.

If you already collect IDs over WhatsApp, the mechanics of turning those photos into fielded data are covered in register guests in SES.Hospedajes by scanning their ID over WhatsApp.

The guest who never signed anything

Three real situations, one answer.

The partner who shows up on day three. They are sleeping there, on a paid stay. Register them, and communicate within 24 hours of their entry — not within 24 hours of the original booking.

The substitution. Someone in the group cancels and a friend takes their place. This is not an amendment to the booking as far as the register is concerned: it is one person who never stayed and one person who did. The register has to reflect the people who actually slept there.

The visitor who stays over. A friend who comes for dinner and leaves is not a traveller. A friend who sleeps on the sofa is. The line is the overnight stay, not the invoice.

What all three have in common is that the contract signature tells you nothing useful. Which is exactly why the "who signed?" reflex is the wrong one — and why a group of eight can be perfectly documented commercially and still be half-registered legally.

When you are outside the rules altogether

One genuine exclusion is worth knowing, because plenty of managers over-comply out of nervousness. The decree applies to accommodation activity — providing lodging or overnight space in exchange for a price. Property let as someone's actual home falls outside it. A twelve-month residential lease is not a hospedaje; you do not file entry forms for a tenant and their family.

The grey zone is seasonal rental. A three-month let to a student or a posted worker is not automatically tourist accommodation — but if the same flat is marketed through tourist channels and used like a hotel, even only in summer, the obligations apply. The test is how the property is actually being used and marketed, not what the contract is titled. If your portfolio mixes both, decide the classification per property and write it down, because the person doing check-ins should not be improvising that call at 8 p.m.

What this looks like as a procedure

The compliance part is easy. The data-entry part is what actually fails, because it lands on whoever is free, at the worst moment of the day, with a phone full of blurry ID photos.

A workable sequence:

At booking: request an ID image for every guest aged 14+, plus first name, surname, date of birth and relationship for each minor.
Before arrival: turn each image into fields — document type and number, names, date of birth, nationality — and check the count against the number of pax.
At check-in: signature from everyone 14 and over.
Within 24 hours of entry: transmit. Set the reminder against the *entry* date of each person, not the reservation.
Keep it: records must be retained for three years (article 5.3).

Step 2 is the bottleneck, and it is pure transcription: reading a document and typing what it says. It is also the step where errors get created — a transposed document number turns a correct submission into an "irregularity". Extracting the fields automatically from the ID photo removes both the time and most of the typos; the check-in data model and which fields are actually mandatory are broken down in guest check-in: exactly which ID fields the law requires you to collect, and the full platform workflow in the 2026 guide to traveller registration in SES.Hospedajes.

One last thing, because it is the other half of the same job: collecting a pile of ID images creates a data-protection obligation of its own. Don't leave them living in a WhatsApp gallery forever — see how to store client ID copies without breaking GDPR.

The short version

Register everyone who sleeps there, including newborns.
14+ sign the entry form; under 14 have their data supplied by the accompanying adult, with the relationship recorded.
One booking of eight people equals eight records.
A guest added mid-stay starts their own 24-hour clock.
Missing register: 601–30,000 €. Sloppy or late register: 100–600 €.

If the slow part for you is turning ID photos into clean fields, you can test that in half a minute: upload a document and get the data back, free and with no account.

Frequently asked questions

Do babies and toddlers really have to be registered?

Yes. RD 933/2021 requires the register to include the data of persons under fourteen; article 4.2 only exempts them from signing, and their data is provided by the accompanying adult. Age affects the signature and the document number, never the existence of the record.

A guest joins the group on day three. When is the deadline?

Within 24 hours of that person's own entry into the accommodation, under article 6.3. The deadline is per traveller, not per reservation, so a mid-stay arrival opens a fresh clock.

Does a long-term residential tenant have to be registered?

No. The decree covers accommodation activity — providing lodging or overnight space for a price. A property used as the occupant's home falls outside it. Seasonal lets are judged on how the property is actually used and marketed: if it works like tourist accommodation, the obligations apply.

What is the fine for forgetting to register part of a group?

Lacking the required registers or omitting the mandatory communications is a serious infraction under article 36.20 of Organic Law 4/2015, fined 601 to 30,000 €. Filling them in incorrectly or communicating late is a minor infraction under article 37.9, fined 100 to 600 €.

How long do I have to keep the records?

Three years, under article 5.3 of RD 933/2021. Storing ID images for that long is itself a data-protection decision: keep them in a controlled system with access limits, not in a shared phone gallery.