Guest registration in Catalonia: the file for the Mossos d'Esquadra

Accommodation in Catalonia reports its guest register to the Mossos d'Esquadra, through the Generalitat's own portal, not to the national SES Hospedajes system. So for these properties BookCheckin does not file automatically: it prepares a text file (.txt) in the Mossos' official format, you download it and upload it to the portal with your own login, and then you note in BookCheckin that you uploaded it. Everything else — the check-in link, the document scan, the signature, the dashboard — is unchanged.

You don't switch this mode on yourself: BookCheckin's support team switches it with you, once your establishment is registered with the Mossos. If your property is in Catalonia and you don't see the card this manual describes, it is still set up for SES Hospedajes — write to us before doing anything else.

One thing to be clear about from the start: BookCheckin never signs in to the Mossos portal, never asks for your portal username or password, and cannot tell whether a file was uploaded or not. All it knows is what you tell it. This manual is, above all, the routine that keeps that record true.

Open the property and go to the Legal tab. Below the SES codes and credentials cards you'll find the card "Mossos d'Esquadra filing (Catalonia)". The SES cards are still there, but this property doesn't need them: a note says so, and "Test Connection" will do nothing useful for it.

The only thing the card asks for is the "Mossos establishment identifier": the 9- or 10-character code (letters and digits) the Mossos d'Esquadra assigned to your establishment when you registered it with form PI-15. That identifier names every file and goes inside it, so until it is on file no check-in links can be created for the property and no file can be prepared — the Info tab reminds you with an amber notice.

Watch out for two common mix-ups. It is not your SES Hospedajes establishment code: they look alike, but they are different registrations, and the Mossos portal will reject a file with the wrong one. And it is not a password: BookCheckin stores no portal credential of any kind, only this identifier of your establishment.

Inside the card, one line sums up the queue: "N guests ready · N blocked · N not yet arrived". A guest enters the queue once they have a name in BookCheckin — because they completed their check-in, or because you entered them by hand — and shows as "ready" on the day of their arrival. Before that date they count as "not yet arrived", so that an empty queue never reads as "nothing to do". By default the queue looks at arrivals from the last 30 days.

A guest whose arrival date has passed and who is not yet in any file is flagged "overdue". That is the one to deal with today.

The list "Blocked — the portal would reject these" holds guests who are missing something the official file requires, with the reason written next to each one. BookCheckin never fills anything in on its own and never trims data to make it fit: it blocks rather than invents. The most frequent reasons: missing first name, first surname or date of birth; a guest aged 14 or over with no identity document; a DNI without a second surname; a DNI or NIE without its support number (3 letters and 6 digits on a DNI, the letter E and 8 digits on a NIE/TIE); neither a phone number nor an email; a guest under 18 without their relationship to the responsible adult; no residence address, or an unrecognised country; a Spanish postal code that isn't 5 digits, or a municipality that postal code doesn't identify on its own; a foreign address without a city.

To unblock one, click the guest's name: it takes you to their reservation in Submissions, where you can correct the data or ask the guest to complete it. Once the data is right, the guest moves to "ready" the next time the card loads.

With at least one guest ready, click "Generate file for Mossos (.txt)". BookCheckin builds the file with every guest ready at that moment — never the blocked ones — and the download starts immediately. The file name is your identifier, a dot and a three-digit number: for example, 08043AAR02.017.txt. Numbering starts at 001 and wraps around after 999; that is the format the portal requires.

If a guest has stopped being valid by the time you generate (say, someone edited their details in between), nothing is generated: the card shows you the updated blocked list so you can fix it and try again.

Every generated file is listed under "Generated files" with its name, how many guests it holds and its status — "Ready to download" at first. From there you can download it again as many times as you need. That list is your register: the Mossos portal keeps no history of what you have uploaded, so this list and the receipts you download from the portal are the only things that document your filings.

Sign in with your own user at the Mossos guest-register portal (registreviatgers.mossos.gencat.cat). The first time, check that your establishment is set up for file submission: under "Mantenimiento de establecimientos" → "Datos establecimientos", the submission type must be "Archivos masivos de viajeros". From then on, every time you sign in the portal opens the file-submission screen directly.

On that screen, click "Elige un fichero", select the .txt you just downloaded and click "Aceptar". The portal checks the format: if something is invalid it shows you the list of errors; if everything is fine you'll see "Operación realizada con éxito" and the option "Descargar comprobante de envío".

Download that receipt and keep it with your records. The Mossos' own manual notes that the receipt does not itself count as a register, and the portal keeps no history of what you have sent and will not hand your guests' data back to you later — so the receipt and BookCheckin's file list are all you have to document that you reported on time, and that documentary record has to be kept for three years.

Remember that each file must contain only guests you have not reported before. BookCheckin already takes care of that: a guest who is in a file never reappears in the queue, unless you discard that file.

Back in the card, on the file you just uploaded, click "Mark as uploaded". BookCheckin asks you to confirm, and the text says it plainly: only confirm once the portal has accepted the file, because BookCheckin never contacts the portal and cannot verify it. On confirming, the file becomes "Uploaded by host" with the date and time of your confirmation, and its guests count as reported in your reports.

If the portal rejected the file — or you generated it by mistake — click "Discard…". You can write the reason (for example, "the portal rejected it — a guest's document number was wrong"). On confirming, every guest in that file goes back to the queue so you can fix what's wrong and generate a new file. The discarded file stays in the list, struck through, as a record; it can no longer be downloaded, so nobody uploads by mistake guests who will go in another file.

Discarding a file you had already marked as uploaded is also possible — for instance, if you realise you confirmed it by mistake — but then the reason is required: that note will be the only record left of a file that, by your account, reached the portal.

Submissions still lists every reservation for the property with each guest's details, and it is where you fix what the queue flags as blocked. What it doesn't show is the status of the Mossos file: its filing pipeline describes the SES Hospedajes process, so for these guests it stays on the first step, with no "Validated" or "Accepted". That is not an error — the truth about each guest lives in the Mossos card and in Reports.

For the same reason, the "Retry Ministry", "Cancel submission" and "Re-file corrected submission" buttons don't apply to this property: if you click them, BookCheckin refuses with a message explaining that this property reports to its regional police, not to SES.

There is one exception: guests who had already been reported to SES Hospedajes before the property switched modes. They are not in the Mossos queue — putting them in a file would register them twice — and the card tells you so, with the link "See them in Submissions". They remain SES records, with their SES actions. If one of them has to move to the Mossos (for instance, because you cancelled its SES filing), cancel first and then use "Re-file corrected submission": since the property now reports to the Mossos, the re-file doesn't go to SES — it places those guests in the card's queue.

In compliance reports the property appears with "Mossos d'Esquadra" under its name and with its own vocabulary, distinct from SES's: the row's indicator reads "N overdue", "N awaiting upload" or "All in uploaded files". Expand it and you'll see how many guests are waiting for a file, in a generated file or in uploaded files, the period's list of files (discarded ones included) and a direct link "Open the file builder →". There is no on-time percentage: there is no filing timestamp BookCheckin could measure, only your confirmation.

Every past arrival with a guest who is in no file raises an item under "Needs attention", reading "Arrival passed, guest not yet in a file for the regional authority". It is the same rule as the card's "overdue" flag, so the report and the queue never disagree.

On the main dashboard, if all your properties report to the Mossos, the getting-started checklist is adapted: the first step talks about the identifier from your regional police registry instead of SES credentials, and the last step — uploading your first guest file — ticks itself the first time you mark a file as uploaded.