Registration details come from the stay, and STRYK shows which registrations are still open.

STRYK connects registration data per traveller with booking, check-in, submission state and export history. The property sees the complete verifiable process rather than isolated fields.

They can be prepared during online check-in or completed at front desk check-in. They are stored only in connection with the correct stay.

Yes. Adults and children are maintained as structured registrations for the stay. This shows which person is complete and which still needs attention.

Check-in settings control standard and custom fields, required state and guidance. The property adapts the process to its actual registration and service requirements.

Document type, number, issuing country and expiry can be required depending on nationality and property rules. Missing required data visibly stops completion.

Yes. The public flow accepts registration data only after explicit confirmation of the details and consent to processing for check-in, registration and stay.

No. It stores prepared guest data and marks the online step complete. Front desk reviews the stay and deliberately performs the actual check-in.

The registration overview filters by date range, completeness and reported state. Open cases can therefore be resolved deliberately before the next export.

Yes. A count independent of the current date filter shows how many registrations remain unresolved overall. Older cases do not disappear behind a narrow daily view.

Yes. The booking receives a summary of existing, complete and reported registrations, including the most recently used format.

CSV provides a clear, processable dataset for review and agreed handoffs. The property decides according to local requirements whether and how the file is submitted.

MBS is a standardised Austrian registration authority file format. STRYK generates it from selected registrations; the property verifies municipal requirements and configuration before use.

Feratel is technically connected to STRYK. Direct transmission to Feratel Deskline in live operation will only be enabled after acceptance; until then, STRYK provides registrations as an export, for example in MBS format. We clarify which registration route applies in your region before you start.

It requires property and access details supplied by the partner plus valid activation. STRYK encrypts sensitive credentials; the contract and possible partner fees remain with the external provider.

Yes. A dedicated connection test checks the entered Feratel configuration. Only a successful test provides a reliable basis for real submissions.

Yes. STRYK processes accepted and rejected records individually. This shows which traveller was reported and who needs a specific correction.

Yes. Failed Feratel exports can be retried deliberately. Affected registrations can also be reset to open when data must be corrected first.

No. CSV and MBS files remain reviewable after generation. Only deliberate confirmation following actual submission marks the included registrations complete.

Yes. File exports and Feratel submissions have separate schedules with interval and run time. File jobs still require real external submission and subsequent confirmation.

Yes. Format, period, record count, state, creation time and errors remain traceable. Generated files can be downloaded again without pretending a new submission occurred.

Viewing and managing are separate permissions. Registration data, exports and settings remain limited to responsible roles within the property.

No. STRYK supports capture, validation, export and state tracking. Which data must be reported, when and to whom depends on the property location and applicable requirements.

No. Registration list, exports, status and connection workflow are part of the single STRYK offer, with no setup fee and no hidden registration module price. Authorities, Feratel or other external partners may charge their own fees.