You submit a guest communication to SES.HOSPEDAJES and the interface says “sent”. Hours later, the guest still isn’t registered. Or the platform hands you a cryptic numeric code with no explanation in sight.
The problem is almost never that you made a serious mistake. It’s that SES can reject a communication at two completely different moments, and most property managers don’t know both exist.
(If the trouble is that the portal won’t load or won’t let you in, not a data rejection, that’s a different problem: see SES.HOSPEDAJES not working. And to understand the platform end to end, there’s the complete SES.HOSPEDAJES guide.)
The two moments SES can reject you
First moment: rejection on submission
This rejection happens within seconds, before the Ministry has even looked at the guest’s data. SES returns a numeric error code immediately on submission. If you see one of these, the entire submission was rejected and no guest was registered.
| Code | What SES says | Common cause | Fix |
|---|---|---|---|
10103 | Lessor code not registered | The landlord code entered doesn’t match the one registered in SES | Copy it exactly from the SES portal; one extra space is enough to fail |
10107 | Incorrect user | SES web service username or password is wrong | The web service username ends in _WS; don’t confuse it with your web portal login |
10119 | No permissions | Account doesn’t have permission to submit communications | Contact SES.HOSPEDAJES support |
10120 | Web service not enabled | Web service access hasn’t been activated for your account | Must be explicitly requested in the portal; it is not enabled by default when you register |
10121 | Duplicate communication | The Ministry already received this communication | See the section below: do not resubmit |
Code 0 means the submission was accepted for review. It does not mean the data is correct: you’ll find that out at the second moment.
Second moment: silent rejection hours later
This is the rejection that catches most operators off guard. When the first moment raises no error, the Ministry reviews each guest’s data separately. That process can take minutes or several hours. To know the real outcome, you have to check the submission status later.
Each guest can come back as successfully registered, or as rejected with a message describing which piece of data was wrong. The submission as a whole can show “accepted” even if several individual guests were rejected.
This means “sent” is not the same as “registered”. A submission accepted at the first moment can have guests rejected at the second, with nothing on the submission screen indicating this.
Common second-moment errors, at a glance
SES doesn’t publish a full catalogue of codes. Most second-moment rejections arrive as a text message inside the response, or as an email to the property’s owner. These are the ones we see most often:
| What goes wrong | Message you see | How to fix it |
|---|---|---|
| Support number read incorrectly | ”Número de soporte inválido” | It’s on the back of the DNI or NIE. No spaces or hyphens |
| Second surname missing | ”Segundo apellido obligatorio” | Always ask for it with DNI or NIE |
| Document doesn’t fit the nationality | ”Tipo de documento no permitido para esta nacionalidad” | DNI/NIE only for those who hold one; passport for the rest |
Phone with + prefix | ”Formato de teléfono incorrecto” | Use 0034 instead of +34 |
| Two-letter nationality code | ”Código de país inválido” | The Ministry wants three letters (DEU, GBR, USA) |
| Property code doesn’t exist | ”Establecimiento no encontrado” | Copy it again from your SES property record |
| Reservation left half-filled | ”Reserva con estado «Incompleto»“ | Check that no mandatory field is blank |
| Postal code mismatch | ”Código postal inválido” | Five digits, consistent with the province |
| Payment data missing on a vacation rental | ”Falta información del medio de pago” | Payment type, holder and, if a card, the last four digits |
| Dates don’t add up | ”Fecha de entrada/salida inválida” | Check the time zone and that check-out is after check-in |
Each second-moment error, and how to fix it
Invalid support number
The single most common reason for rejection, according to the platform itself.
The support number is the character string on the reverse of the Spanish DNI (for Spanish identity documents) or in the lower strip of the NIE. It is mandatory for all Spanish identity documents.
What usually goes wrong: reading it from the front of the document, confusing it with the document’s serial number, or typing it with spaces or hyphens.
Second surname required
When the guest holds a DNI or NIE, the second surname is mandatory even if the guest habitually uses only one. If it is missing, the communication will be rejected with the message “Segundo apellido obligatorio”.
Document type doesn’t match nationality
SES checks that the document type fits the guest’s nationality. Submitting a DNI for a foreign national, or a foreign passport for a Spanish resident, triggers this error.
The practical rule: DNI and NIE only for guests who hold those documents. For everyone else, passport or national identity card.
Incorrect phone number format
SES requires the international prefix in 0034 format, never with the + symbol. A valid phone number for the Ministry:
0034612345678 ✓
+34612345678 ✗
Nationality in the wrong format
The Ministry requires the three-letter country code (not two letters). The most common mistakes:
| Country | Wrong | Correct |
|---|---|---|
| United Kingdom | GB | GBR |
| Germany | DE | DEU |
| France | FR | FRA |
| United States | US | USA |
Establishment code not found
The property’s establishment code doesn’t exist in SES under that lessor account. Common causes:
- Copied with errors from the portal
- Property registered recently and not yet active
- Property linked to a different lessor account
Verify it in the property record inside the SES.HOSPEDAJES portal.
Reservation in “Incomplete” state
Happens when a mandatory field is missing or blank. SES marks the reservation as “Incomplete” and never even processes the associated guests. The typical case is a vacation rental missing one of the lodging-reservation fields (contract type, number of beds, payment data).
Go through the form field by field. And if the submission came from another tool or a booking file, make sure that tool fills in everything SES expects.
Invalid postal code
SES validates the postal code against the official Correos list. Common mistakes: four digits instead of five, a foreign postal code entered as if it were Spanish, or a code that doesn’t match the declared province.
Missing payment information
Applies to the lodging reservation for vacation rentals. SES asks for the payment method (card, bank transfer, cash…), the holder, and the last 4 digits if it’s a card. It does not ask for the full number, CVV, or expiry date: collecting more would be a GDPR minimisation issue.
Inconsistent dates
Cases we’ve seen: check-out before check-in, dates in MM/DD/YYYY format when DD/MM/YYYY is expected, zero-night stays, time-zone mismatch between PMS and SES.
Code 10121: do not resubmit
Error 10121 (Duplicate communication) is the only first-moment code that does not require resubmission. It means the Ministry already has that communication. Resubmit the same form and you’ll get another 10121, in a loop.
The right move is to check the status of the original submission to find out whether the guests were registered.
How to tell which moment the problem is at
| Symptom | Where to look |
|---|---|
| Error code at the moment of submission | Table in the previous section |
| Submission confirmed but guests not registered | Check the individual result for each guest |
| Some guests registered, others not | Check the error message for the rejected guests |
| No response after more than 30 seconds | Connectivity issue; retry without duplicating the original form |
What RegistroViajero does for you
RegistroViajero handles both moments for you: it checks the submission status after each communication, spots which guests were rejected, and tells you the specific reason.
If you have questions about SES.HOSPEDAJES credentials, that article explains in detail the difference between portal credentials and web service credentials, and how to configure the lessor code correctly.