SES.HOSPEDAJES Error Codes: Rejections and Fixes

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 bare five-digit number with no explanation in sight.

The problem is almost never a serious mistake: one space too many when copying a code, a phone prefix written with +, a permission nobody ever switched on. What changes everything is when SES tells you.

One rejection arrives in seconds and makes noise. The other says nothing at all, and it is the one that costs reports to anyone who treats the job as finished the moment the confirmation appears on screen.

(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.HOSPEDAJES 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 code and the entire submission is rejected: no guest is registered.

The second column reproduces the Ministry’s own wording, in Spanish as the service returns it. The full catalogue sits in section 5 of the web service specification, which you download from inside the portal¹.

With a 10103 or a 10107, check the three values together. Both codes point at the same trio: web service username, password and lessor code. In our submissions, the 10107 also shows up when what fails is the password or the code, not only the username.

1. Check that the username ends in _WS. The login you use for the web portal does not work for the web service.
2. Copy the lessor code from the portal and paste it untouched. One trailing space is enough to trigger the 10103.
3. Type the password by hand into your submission tool, without copying and pasting.
4. Resubmit. If the 10107 is still there, the value at fault is one of the other two.

With a 10119, the fix is not yours to make. Write to SES.HOSPEDAJES support with your lessor code and the type of communication you are trying to send, and ask them to enable that permission.

With a 10120, the channel is switched off. Web service submission is not on by default:

1. Sign in to the SES.HOSPEDAJES portal with the portal credentials, which are not the web service ones.
2. Switch on the option to operate through the web service in your lessor configuration.
3. Save the change and submit the report again.

Code 0 is the one the Ministry describes as “Ok”¹. It means the submission was accepted for review, not that the data is correct: that gets decided at the second moment.

Second moment: silent rejection hours later

When the first moment raises no error, the Ministry reviews each guest’s data separately. That process can take minutes or several hours, and its outcome never returns to the submission screen: you have to go and check the status.

Each guest can come back as 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 guests were rejected one by one.

That is why “sent” is not the same as “registered”. And the difference matters, because the legal clock does not stop when you press submit:

“This communication shall be made immediately, and in any case within a period no longer than 24 hours, respectively, from the following moments: a) On making the booking or formalising the contract or, where applicable, its annulment. b) On the start of the contracted services.”

Those are two separate deadlines and each opens 24 hours of its own: one starts with the booking, the other with the guest’s arrival. Neither starts with your submission.

A rejected report has not been communicated, so that clock keeps running while you treat it as done. And the corrected report counts as a fresh communication, not as a continuation of the first:

“Yes, the modification of any of the data shall give rise to the obligation of a fresh communication.”

Article 8 of the royal decree splits what happens at the end of the deadline into two boxes. As a serious infringement, by reference to Article 36.20 of Organic Law 4/2015:

“b) The omission of the mandatory communications.”

As a minor infringement, by reference to Article 37.9 of the same law:

“b) Making the mandatory communications outside the established deadline.”

The amounts are set by Organic Law 4/2015: 601 to 30,000 euros for serious infringements, 100 to 600 euros for minor ones⁵. Applied to a silent rejection:

• You resubmit the corrected report inside the 24 hours: no breach.
• You resubmit it later: communication outside the deadline, minor, 100 to 600 euros.
• You never resubmit it: there is no communication at all, and our reading is that this falls into the omission of Article 8.2.b), serious, 601 to 30,000 euros.

SES.HOSPEDAJES silent rejections, at a glance

The field formats are written down. The Instrucciones para el alta masiva de comunicaciones, which the platform serves from its own site, carry the field-by-field table with each field’s type, length and when it is mandatory⁶. You do have to go to the portal for them: the Ministry’s sede carries only the Guía visual and the FAQ⁷.

The messages the platform uses to reject an individual guest at this second moment appear in no published document. They arrive as text inside the response, or as an email to the property’s owner. The table below is what the platform returns on our own submissions, ordered by frequency.

Each silent rejection, and how to fix it

Invalid support number

It is the rejection the platform returns to us most often.

The support number is on the front of the DNI, the photo side: in the right-hand data block, next to the expiry date, and repeated in laser engraving in the transparent window at the top right. It is not on the back, which carries the address, place of birth and the machine-readable strip.

Annex I asks for it as a field of its own, separate from the document number⁸, and the Ministry devotes an FAQ entry to where to find it³. In the field table it is soporteDocumento, nine characters long, mandatory whenever the document type is NIF or NIE⁶. Nine characters is exactly what three letters and six digits take up.

Before typing, check you are not looking at a different number:

• The CAN is also on the front, but in the bottom right corner, and exists for NFC reading.
• The DNI number is eight digits and a control letter, and it moves position with the document version.
• The support number is three letters and six digits, and never has the shape of the previous one.

And to enter it:

1. Type the three letters and the six digits in one run, with no spaces or hyphens.
2. If the label isn’t where you expect, compare it against the three document versions covered in where the DNI support number is.

Second surname required

Annex I asks for the first name, the first surname and the second surname as three separate fields⁸. The platform also makes it conditional: the field table marks apellido2 as mandatory when the document type is NIF⁶, and the web service specification records a validation change that extended the requirement to the NIE¹.

It makes no difference that the guest habitually uses only one surname. If the field arrives empty, the report is rejected.

Ask for it at check-in whenever the document is a DNI or a NIE, and leave it empty only with a passport or another document.

Document type doesn’t match nationality

SES accepts exactly four document types and requires the number submitted to correspond to the declared type, with a valid format in the case of a NIF or a NIE⁶:

• NIF: Spanish tax identification number.
• NIE: foreigner’s identity number.
• PAS: passport number.
• OTRO: any other document.

The Ministry itself sets out how they are shared out:

“The DNI for Spanish citizens (mandatory for persons over 14 years of age), an Identity Document for EU citizens and a PASSPORT for foreign nationals.”

Submitting a DNI for a foreign national, or a foreign passport for a Spanish resident, triggers this error. Pick the type from the document the guest hands you, not from their country.

Incorrect phone number format

All that is documented is that the phone is a 20-character field and that you must fill in at least one of these three: telefono, telefono2 or correo⁶. There is no written rule about the prefix, and the sample request in the web service specification carries a bare national number, with no prefix at all¹.

In our submissions, by contrast, the + symbol produces rejections that disappear when the prefix is written with zeros:

0034612345678   ✓
+34612345678    ✗

Store the number with no spaces, no parentheses and the prefix in zeros. That is the practice that works for us, not a published rule.

Nationality in the wrong format

This one is written down: nationality is encoded per the ISO 3166-1 Alpha-3 standard, in a three-character field⁶. Three letters, not two. The most common mistakes:

Convert two-letter codes before submitting. The same three-letter format applies to the country of the guest’s home address, so a PMS that works in two letters fails in both fields at once.

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.

How to get out of it:

1. Open the property record in the SES.HOSPEDAJES portal and copy the code from there.
2. Check that the record hangs off the same lessor code you are submitting with.
3. If the registration is recent and the error persists, wait until the property shows as active before retrying.

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: they are not half registered, none of them is registered.

In the contract block the mandatory fields are the reference, the contract date, the check-in date and time, the check-out date, the number of people and the payment block. The number of rooms and the internet connection are not⁶.

1. Open the reservation and go through those six fields one by one.
2. Fill in the blanks, starting with the payment block, which is the one most often forgotten.
3. Save and check that the reservation is no longer “Incomplete”.
4. Only then submit the guests’ reports.

If the submission came from another tool or a booking file, make sure that tool fills in everything SES expects. This is where channel-imported bookings almost always land: when the reservation arrives from Airbnb, Booking or Vrbo, nobody typed the contract reference or the payment block, the platform supplies them in its own format and on its own criteria, and the PMS carries them through to the submission without you ever seeing them. If the channel sends neither, or your software does not put it in the field SES expects, the reservation sits in “Incomplete” with all its guests behind it. Before reviewing bookings one by one, check the channel mapping: what is failing is not one reservation, it is every one from that source.

Invalid postal code

Here the Ministry fixes no format: codigoPostal is mandatory and takes up to 20 characters, with no list of values attached, while the municipality in the same table is encoded with the INE’s five digits⁶. The 20 characters are there for foreign postal codes, not because anything goes.

The rejections we see are always the same ones:

• Four digits instead of five on a Spanish address.
• A foreign postal code entered as if it were Spanish.
• A code that doesn’t belong to the establishment’s province.

Five digits for Spain, with the first two consistent with the province.

Missing payment information

It applies to the guest report and to the reserva de hospedaje (lodging booking) alike: in both the pago block is mandatory, though inside it only the tipoPago is. The date, the identification of the means, the holder and the expiry date are listed as not mandatory⁶.

Annex I of RD 933/2021, by contrast, asks for five items under “Datos del pago”⁸:

• Type of means: cash, credit card, payment platform, transfer and others.
• Identification of the means of payment: card type and number, account IBAN, mobile payment solution or others.
• Holder of the means of payment.
• Card expiry date.
• Date of payment.

The CVV does not appear on that list and is never reported. The annex names four means, but the platform accepts eight codes: EFECT (cash), TARJT (credit card), PLATF (payment platform), TRANS (transfer), MOVIL (mobile payment), TREG (gift card), DESTI (payment on arrival) and OTRO⁶.

This is the other place a channel-imported booking runs aground, and for the same reason: the guest paid Airbnb or Booking, not you, so the means of payment to report is the one the platform recorded, not one you entered. Our reading is that the code that fits such a charge is PLATF, payment platform, rather than any of the direct-payment ones. If your PMS leaves the block empty because the money never went through your card terminal, the submission is rejected however faultless the rest of the reservation is.

Always fill in the payment type, and the rest of the block when you have it.

Inconsistent dates

The contract dates don’t go in the form’s format, they go in the web service’s: the contract date as YYYY-MM-DD, and check-in and check-out as YYYY-MM-DDThh:mm:ss. If you don’t know the time, the Instrucciones say to send YYYY-MM-DDT00:00:00⁶.

Cases we’ve seen: check-out before check-in, zero-night stays, day and month swapped when converting from a slash format, time-zone mismatch between the PMS and SES.

1. Convert the dates to YYYY-MM-DD at source, before the value enters the submission.
2. Add the time to check-in and check-out (Thh:mm:ss), or use T00:00:00 if you don’t have it.
3. Check that check-out is after check-in, not equal to it.

Code 10121: fix the data and resubmit

Error 10121 (Validation error) means the communication fails the system’s validation: some field doesn’t have the expected format or value, so it is not stored.

It usually comes with more specific codes, and these two carry the field’s name embedded in the message itself¹:

• 10130: “Valor incorrecto para el campo: $NOMBRE_CAMPO” (invalid value for the field).
• 10131: “Es obligatorio indicar un valor en el campo: $NOMBRE_CAMPO” (a value is required in the field).

Where the Ministry writes $NOMBRE_CAMPO you will see the real field name, so the response is telling you exactly what to fix.

1. Find the 10130 or the 10131 in the response and keep the field name.
2. Look that name up in the field table of the Instrucciones and check its type, its length and when it is mandatory.
3. Fix the value at source, in the PMS or in the form, not just in the submission.
4. Resubmit the whole communication: the 10121 kills the entire submission, not a single guest.
5. If the message arrives without a field name, start with the usual suspects: support number, date format and postal code.

How to tell if the failure came on submission or hours later

Frequently asked questions

What does SES.HOSPEDAJES error 10121 mean? SES.HOSPEDAJES error 10121 means the communication did not pass the system’s validation: some field does not carry the format or the value the platform expects, so nothing is recorded. It usually arrives alongside 10130 or 10131, which carry the name of the offending field inside the message itself. When it comes without a field name, the usual suspects are the support number, the date format and the postal code.

Why does SES.HOSPEDAJES accept the submission while the guest stays unregistered? SES.HOSPEDAJES accepts the submission and leaves the guest unregistered because it validates in two separate moments. Code 0 only confirms the communication was taken in for review; the Ministry then checks each guest’s data separately and can reject some of them hours later, with nothing showing on the submission screen. That is why the status is worth checking again after a while, guest by guest.

How long do I have to fix a report SES.HOSPEDAJES rejected? The time you have to fix a report SES.HOSPEDAJES rejected is whatever is left of the 24 hours in Article 6.3 of Royal Decree 933/2021, counted from the booking or from the guest’s arrival, not from your first submission. A rejected report has not been communicated, so that deadline keeps running, and the rule does not suspend it because the portal is down.

What is the most common reason a guest report is rejected in Spain? The most common reason a guest report is rejected is a misread support number. It sits on the front of the DNI, the photo side, and has a format of three letters and six digits, so it is rejected if it is typed with spaces or hyphens, looked for on the back, or confused with the document number or with the CAN.

What is the difference between SES.HOSPEDAJES errors 10103 and 10107? The difference between SES.HOSPEDAJES errors 10103 and 10107 is which credential the Ministry rejects. 10103 says the lessor code does not exist in the system, almost always because of an extra space when copying it from the portal. 10107 shows up as an incorrect username, but it covers the username, the password and the lessor code at once, and the web service username is not the one used to sign in to the portal.

Where is the official SES.HOSPEDAJES error code catalogue? The official SES.HOSPEDAJES error code catalogue is in section 5 of the web service specification, a document downloaded from the portal itself rather than from the Ministry’s electronic office. The messages from the second moment, the ones that reject an individual guest, are not published in any document: they arrive as text inside the response or by email to the accommodation holder.

How RegistroViajero catches the silent rejections

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.

The three values that travel with every submission are broken down one by one in SES.HOSPEDAJES credentials.

Prefer not to watch the codes by hand? See how RegistroViajero works.

The error codes and the per-field formats come from the Ministry’s own technical documentation. The messages the platform uses to reject an individual guest in the later review are documented nowhere: they come from the responses we receive on our own submissions and can change without notice. The underlying obligations come from Real Decreto 933/2021.

This article is for informational purposes and does not replace professional legal advice.