Before letting you generate the traveller registration report, aiGuest checks the register data by data: DNI check letter, country codes, phone prefix, coherent dates, minors with their responsible adult. If something doesn't add up, it tells you in plain language.
A poorly completed traveller registration report isn't discovered when you submit it: it's discovered days later, when the guest has already left and the deadline has passed.
aiGuest's validator is a layer of centralized and versioned rules alongside the official catalogues, and it runs on the complete set before generating anything: the booking, the accommodation, the payment method and each traveller's form. It's not a "required field" in red: it's a list of specific problems, each one with the traveller's name and the exact field you need to go to.
It checks what actually causes a registration to go wrong. It calculates the DNI and NIE check letter from the number, instead of taking it at face value. It accepts passports with a loose format, but warns you when it looks unusual. It requires that nationality and country of residence come from the closed list of ISO codes in the catalogue, never free text. It asks for the phone with international prefix, or a valid email, because at least one contact method is needed. It checks that dates make sense with each other: birth date not in the future or more than 120 years ago, document issue date not after today, departure after arrival. It requires every minor to have indicated which adult on the trip they're travelling with and what family relationship they have, and won't let you register a group made up only of minors. It counts registered travellers against those declared in the booking, flags two travellers with the same document and warns of unusual characters in names that may not be accepted later.
And it distinguishes two levels, which is the difference between a useful validation and an annoying one. Blocking issues prevent generation, and the button tells you with a number: "Fix 3 data items to generate". What's only a warning—an unusual passport, an uncommon character, an extra traveller—you can accept with an "I know, continue", and then it's recorded in the report itself: there's proof that you saw it and decided to proceed. The same validation runs again on the server at the moment of generation, so it's not just a screen decoration: if there are blocking issues, the report isn't issued. One case has its own nuance: without a SES establishment code the XML can't be built, but the PDF and the guest copy are generated anyway.
The validator is part of aiGuest, the mini app for traveller registration and SES.HOSPEDAJES report from AIsToHire: https://aistohire.com/aiguest-guest-registration-report-ses-hospedajes-178
It tells you what to correct, not "validation error"
Each problem comes with the traveller's name, the specific field and a phrase in plain language. You click and go straight to the missing data, without reviewing forms one by one.
The DNI and NIE letter, calculated
aiGuest derives the check letter from the number instead of accepting it as is. A wrongly copied digit from the document fails there, on your screen, and not on the official platform.
Nationality and residence from closed lists
Countries come from the catalogue with their ISO code, never free text. There's no way to send "United Kingdom" spelled five different ways across five different reports.
Minors always with guardian and relationship
No minor can be registered without indicating which adult from the trip they're travelling with and their relationship, as required by RD 933/2021. And a group with only minors cannot be registered.
Counts travellers for you
Compares those registered against those declared in the booking and alerts you if any are missing, if there are extras, or if two forms carry the same document number. The classic "there were four of us but only three are here" will no longer slip past you.
Two levels
what blocks and what you can accept: Critical issues prevent generation; questionable ones you dismiss with "I know, continue" and it's recorded in the report. It won't stop you over an unusual accent, but it won't forget it either.
Also validates on the server, not just on screen
When generating, the rules are applied again in the backend. If there's anything blocking, the report simply isn't issued, even if someone bypasses the screen.
Without SES code, the PDF is still generated
If the accommodation lacks the establishment code, the validator flags it for the XML but still lets you generate the PDF and the guest copy. You're never left without a document.

Create your free account, register your accommodation and let aiGuest review the register before anyone else does.