How Can I Resolve Common Errors When Submitting Reservations to the AADE Registry via Hosthub?

Submitting reservations to the AADE (myDATA) registry via Hosthub is an essential step in keeping your compliance records accurate. Occasionally, users may encounter errors during this process. This article outlines common issues and their solutions to streamline your AADE submission experience.

Introduction

The AADE registry handles important compliance data like financial statements linked to reservations. Errors in submissions can occur due to technical issues, duplicate entries, or timing restrictions. Use this guide to resolve these challenges promptly.

Common Error Scenarios and Solutions

1. Temporary System Errors

If an error message appears while registering a reservation in the AADE registry, it could be due to a temporary issue with the AADE system:

• What to Do: Wait for a few minutes and try submitting the reservation again. Temporary glitches often resolve themselves when retried later.

2. Duplicate Entry Errors

Duplicate errors occur when a declaration for the same reservation dates is already present in the AADE registry. Hosthub blocks subsequent submissions to avoid duplication:

• Verify Existing Entries: Check the AADE registry (Μητρώο) for an entry matching the reservation dates.
• Action if Duplicate Exists: If the entry is already recorded correctly, no further action is required in Hosthub. Ignore the error message reported by Hosthub.

3. Timing Restrictions on Submissions

Reservations cannot be submitted to the AADE registry until after the guest’s check-out date, as these reservations are editable before check-out:

• Submission Timing: Ensure the check-out date has passed before attempting to submit the reservation to AADE.
• Why This Happens: Pre-check-out reservations might still change (e.g., cancellations or extensions), and submitting too early could result in inaccuracies.

4. Submission Stuck "In Progress"

If a declaration remains stuck showing "still in progress" or "check and send" while other declarations submit successfully, the AADE registry page is likely experiencing a temporary issue:

• What to Do: No action is needed. The submission will complete on its own. If it actually fails, the status will change to a failure message and you can resubmit or correct it then.
• Note: The AADE registry declaration is separate from MyDATA. Documents can go through to MyDATA correctly even if the registry declaration is still in progress.

5. Status "Incomplete" (Ημιτελές)

The "Incomplete" (Ημιτελές) status reflects a message returned directly by AADE. Common cases:

• AMA discontinued (error #32): The message indicates the AMA (Property Registration Number) has been terminated based on a submitted Lease Dissolution Declaration. If you have re-issued the AMA under the same VAT number, AADE may need some time to synchronize — wait a while and check again. If the problem persists, contact support. Changes to the AMA itself should be handled with your accountant.
• Another declaration exists for the same property/dates: AADE rejects the booking because a declaration already exists covering days of the same stay period. Log in to your Taxisnet account to check the existing declaration and declare the specific booking there. Also verify the property is connected to the correct AMA at Integrations > AADE (partnership settings); if it is linked to the wrong AMA, disconnect and reconnect with the correct one.

Best Practices for Submission

• Always verify the AADE registry before resubmitting if an error message appears.
• Avoid submitting reservations prematurely (i.e., before the check-out date).
• Document error messages in case the issue does not resolve, and contact support if necessary for further assistance.

Updated on: 29/07/2026