How to Correct Errors in SES.Hospedajes: A Complete Guide for Spanish Accommodation Providers

If you've ever submitted a guest communication to Spain's SES.Hospedajes platform only to receive an error notification — or worse, discovered a mistake after the fact — you're not alone. The platform, mandated by Royal Decree 933/2021, processes millions of traveller communications every year across hotels, vacation rentals, hostels, and every other type of registered accommodation in Spain. Mistakes happen, and the Ministry of Interior has built a correction workflow into the Sede Electrónica. Knowing how to navigate it quickly is the difference between a minor administrative hiccup and a compliance headache.

This guide walks through the full correction process: finding the communication code you need to amend, working with batch submissions, and resubmitting corrected records — all without losing your mind in the platform's menus.

Why Corrections Matter Under RD 933/2021

Royal Decree 933/2021 requires accommodation operators to submit traveller data within strict timeframes — in most cases before or at the moment of check-in. The regulation doesn't just demand timely submission; it demands accurate submission. Errors in document numbers, nationality fields, date of birth, or check-in/check-out dates are not treated as a technicality. They can constitute a non-compliance event, and the Ministerio del Interior's inspection system can flag them.

The good news: the platform distinguishes between communications that were rejected outright and those that were accepted with errors in a batch. Each scenario has a slightly different correction path, and understanding both keeps your compliance record clean.

Understanding Individual Communications vs. Batches

Before diving into the steps, it helps to understand how SES.Hospedajes structures submissions:

• Individual communications are single guest records submitted one at a time — common for properties with low occupancy or platforms doing real-time API pushes.

• Batch submissions (lotes) are groups of communications submitted together — typical for property management systems and channel managers that aggregate overnight data and push it in bulk.

Each communication, whether individual or part of a batch, receives a unique communication code. Each batch also receives its own batch code (código de lote). You'll need the right code before you can do anything else.

Step 1: Locating the Code for an Individual Communication

To correct something, you first need to find it. Here's how to locate the code for a specific individual communication:

1. Go to the Sede Electrónica del Ministerio del Interior and navigate to Mis comunicaciones → Consulta y Gestión de mis comunicaciones.

2. Select your entity or establishment from the list.

3. Click Comunicaciones.

4. Use the search filters — date range, communication type, or communication code — and press Buscar.

5. Your record will appear in the results table.

If the communication was submitted as part of a batch, you need one extra step to find its individual code:

1. From the same screen, click Lotes (next to "Comunicaciones").

2. Filter by operation type, request type, and date range, then press Buscar.

3. The batch record appears in the results table.

4. Click the eye icon to expand the batch and view all individual communications within it.

5. Find the row for the specific communication and note its individual code.

Step 2: Locating a Batch Code

If you need to work at the batch level — for instance, to check the status of a whole night's worth of submissions — the process is slightly different:

1. Head to Mis comunicaciones → Consulta y Gestión de mis comunicaciones.

2. Select your entity or establishment.

3. Click Lotes.

4. Filter by operation type, request type, and date range, then press Buscar.

5. The results table shows each batch with its batch code (código de lote), the submitting user, submission date, and current status.

This view is your first diagnostic screen. If a batch shows a warning state, that's your cue to drill down.

Step 3: Correcting an Error in a Batch Communication

This is the most common scenario: your PMS or channel manager pushed a batch overnight, and in the morning you receive an email from the Ministry flagging one or more records with errors. The email typically contains a description of the problem (for example, an invalid document number format or a missing nationality code). Here's the full correction workflow:

1. Log into the Sede Electrónica and go to "Acceso a la consulta y envío de comunicaciones de actividades de hospedajes o alquiler de vehículos".

2. Navigate to Mis comunicaciones → Consulta y Gestión de mis comunicaciones.

3. Select your entity/establishment and click Lotes.

4. Filter to find the relevant batch and press Buscar.

5. Click the eye icon on the batch to see all communications in it.

6. Identify the problematic communication — it will be flagged with a red error message, such as "Lote tramitado, pero hay errores en algunas comunicaciones".

7. In the Acciones column, click the eye icon (view) on that communication to see the full details and the specific error.

8. Click the pencil icon (edit) to open the record for correction.

9. Fix the field(s) flagged in the error notification.

10. Click Finalizar to resubmit the corrected communication.

The resubmission is logged as an amendment to the original record — the original communication code is preserved, so your audit trail remains intact.

Common Errors and What They Usually Mean

Based on the patterns seen across the industry, most correction requests fall into a handful of categories:

Document number format errors — The NIE, passport, or DNI number doesn't match the expected format for that document type. Double-check that the document type field and the number field are aligned.

Nationality/country code mismatches — The platform uses ISO 3166-1 alpha-2 codes. If your system is sending full country names or three-letter codes, they won't validate.

Date format issues — The platform expects dates in DD/MM/YYYY format. Systems sending ISO 8601 (YYYY-MM-DD) without format conversion will fail.

Missing mandatory fields — For travellers over 14, all core fields are mandatory. If a field was left blank due to incomplete check-in data, it will return an error.

Duplicate submissions — If the same communication was submitted twice (common during batch retries), the second one may be flagged. Use the annul (anular) action on the duplicate rather than the edit action.

Automating Submissions to Prevent Errors

The most effective way to reduce correction frequency is to ensure that data leaves your property management system in the correct format in the first place. Platforms with a native SES.Hospedajes integration — including HolidayHero — validate guest data against the Ministry's requirements before submission, catching format issues at the source. When a guest record fails validation, the error is surfaced to the property manager before it ever reaches the Sede Electrónica, eliminating the need for post-submission corrections in most cases.

For properties still submitting manually or via CSV upload, a pre-submission checklist aligned with the field requirements of RD 933/2021 can significantly reduce error rates.

Key Takeaways

Correcting submissions in SES.Hospedajes is not as complicated as it might seem once you understand the platform's structure. The key points to remember:

• Every communication has a unique code; every batch has a batch code. Find the right one before attempting any correction.

• Batch errors show up with red flags in the lote detail view — they don't always surface at the batch level itself.

• The correction workflow preserves your original communication code, so amendments don't disrupt your compliance record.

• Resubmission is completed by clicking Finalizar after editing — there is no separate "submit" button.

• The best long-term strategy is to prevent errors at the source through integrated, validated submissions.

If you're managing multiple properties across Spain and want to eliminate the manual correction cycle entirely, HolidayHero's SES.Hospedajes integration handles submissions, validation, and error handling automatically — so your team can focus on guests, not government portals.