> For the complete documentation index, see [llms.txt](https://support.holidayhero.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.holidayhero.com/guides/ses-hospedajes/correcting-errors-in-ses-hospedajes.md).

# Correcting Errors in Ses Hospedajes

## Correcting Errors in Ses Hospedajes

If you've submitted a guest communication through SES.Hospedajes and received an error notification — or spotted a mistake after submission — this guide explains how to locate the affected record and correct it directly in the platform.

The correction workflow differs slightly depending on whether the communication was submitted individually or as part of a batch (lote). Both paths are covered below.

***

<a href="https://accounts.holidayhero.com/signup?utm_medium=support&#x26;utm_source=ses-hospedajes-corrections" class="button primary">Try HolidayHero's Ses Hospedajes integration free</a>

<a href="https://accounts.holidayhero.com/signup?utm_medium=support&#x26;utm_source=ses-hospedajes-corrections" class="button primary">Prueba la integración con Ses Hospedajes gratis</a>

***

#### What You'll Need

* Access to the [Sede Electrónica del Ministerio del Interior](https://sede.mir.gob.es/opencms/export/sites/default/es/procedimientos-y-servicios/hospedajes-y-alquiler-de-vehiculos/) with your digital certificate or DNIe.
* The approximate date of the submission containing the error.
* The error description from the Ministry's notification email (if applicable).

***

### Finding the Code for an Individual Communication

Before you can correct a record, you need to locate it. Use these steps whether the communication was submitted on its own or inside a batch.

{% stepper %}
{% step %}

#### Open Mis Comunicaciones

* Navigate to the [Sede Electrónica](https://sede.mir.gob.es/opencms/export/sites/default/es/procedimientos-y-servicios/hospedajes-y-alquiler-de-vehiculos/) and go to **Mis comunicaciones → Consulta y Gestión de mis comunicaciones**.
* Select your entity or establishment from the list.
  {% endstep %}

{% step %}

#### Search for the Communication

* Click **Comunicaciones**.
* Use the search fields to filter by date range, communication type, or communication code.
* Press **Buscar**. The record will appear in the results table.
  {% endstep %}

{% step %}

#### If the Communication Was Part of a Batch

* Instead of clicking **Comunicaciones**, click **Lotes**.
* Filter by operation type, request type, and date range, then press **Buscar**.
* Click the **eye icon** on the batch to expand it and view all individual communications.
* Locate the specific row and note the individual communication code in the **Acciones** column.
  {% endstep %}
  {% endstepper %}

***

### Finding the Code for a Batch (Lote)

Use this if you need to check the overall status of a batch submission, or before drilling into individual records within it.

{% stepper %}
{% step %}

#### Open Mis Comunicaciones

* Go to **Mis comunicaciones → Consulta y Gestión de mis comunicaciones**.
* Select your entity or establishment.
  {% endstep %}

{% step %}

#### View Batch Records

* Click **Lotes** (next to "Comunicaciones").
* Filter by operation type, request type, and date range.
* Press **Buscar**.

The results table displays each batch with its **batch code (código de lote)**, the submitting user, submission date, and current status.
{% endstep %}
{% endstepper %}

***

### Correcting an Error in a Batch Communication

This is the most common scenario: your property management system submitted a batch overnight and the Ministry has flagged one or more records with errors. The error email describes what needs to be fixed (for example, an invalid document number or missing nationality code).

{% stepper %}
{% step %}

#### Access the Platform

* Log into the [Sede Electrónica](https://sede.mir.gob.es/opencms/export/sites/default/es/procedimientos-y-servicios/hospedajes-y-alquiler-de-vehiculos/).
* Go to **"Acceso a la consulta y envío de comunicaciones de actividades de hospedajes o alquiler de vehículos"**.
* Navigate to **Mis comunicaciones → Consulta y Gestión de mis comunicaciones**.
  {% endstep %}

{% step %}

#### Find the Batch

* Select your entity or establishment.
* Click **Lotes**.
* Filter by date range and operation type, then press **Buscar**.
  {% endstep %}

{% step %}

#### Open the Batch

* Click the **eye icon** on the relevant batch to see all communications inside it.
* Identify the record with an error — it will be flagged in red, for example: *"Lote tramitado, pero hay errores en algunas comunicaciones"*.
  {% endstep %}

{% step %}

#### View the Error Details

* In the **Acciones** column next to the problematic communication, click the **eye icon** (view).
* The full record opens, showing the specific field or fields that triggered the error.
  {% endstep %}

{% step %}

#### Edit and Correct the Record

* Click the **pencil icon** (edit) to open the record for editing.
* Fix the field(s) described in the error notification.
  {% endstep %}

{% step %}

#### Resubmit

* Click **Finalizar** to resubmit the corrected communication.

The system logs the correction as an amendment to the original record. Your original communication code is preserved, so your compliance audit trail remains intact.
{% endstep %}
{% endstepper %}

***

### Common Error Types

| Error                            | Likely Cause                                                                    |
| -------------------------------- | ------------------------------------------------------------------------------- |
| Invalid document number format   | Document type and number don't match (e.g. NIE format submitted as passport)    |
| Unknown nationality/country code | System is sending full country names instead of ISO 3166-1 alpha-2 codes        |
| Invalid date format              | System is sending dates as `YYYY-MM-DD` instead of `DD/MM/YYYY`                 |
| Missing mandatory field          | Required field (e.g. date of birth, address) left blank at check-in             |
| Duplicate communication          | Same record submitted twice; use the **anular** (annul) action on the duplicate |

***

### Preventing Errors Automatically

The most reliable way to avoid corrections is to validate guest data *before* it reaches the Sede Electrónica. HolidayHero's native SES.Hospedajes integration checks all guest fields against Ministry requirements at the point of check-in and flags issues to your team immediately — so problems are caught before submission, not after.

<a href="https://accounts.holidayhero.com/signup?utm_medium=support&#x26;utm_source=ses-hospedajes-corrections" class="button primary">Try HolidayHero free — no corrections needed</a>

***

### Related Guides

* [Registering on Ses Hospedajes](/guides/ses-hospedajes.md)
* [Setting up the HolidayHero Ses Hospedajes integration](/integrations/guest-registration/ses-hospedajes-guardia-civil.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.holidayhero.com/guides/ses-hospedajes/correcting-errors-in-ses-hospedajes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.