SIBA explained: the practical guide for alojamento local hosts

SIBA — the Sistema de Informação de Boletins de Alojamento — is one of those obligations that most hosts ignore until the moment they really shouldn't. Not out of bad faith, but because nobody ever explains clearly what it is, what it demands, and what happens when it goes wrong.

This article does exactly that.

What SIBA is and why it exists

SIBA is the platform managed by SEF (now operating under AIMA — the Agency for Integration, Migration and Asylum) where accommodation establishments, including alojamento local, must register guest identification data. The purpose is straightforward: the state wants to know who is sleeping where, particularly in the context of border control and internal security.

This isn't new. The obligation to report guest data has existed for a long time for hotels and tourist units. AL properties are subject to the same rules — and enforcement has been tightening.

What you need to report

For every guest aged 16 or over, you must register a set of identification details in SIBA: full name, nationality, date of birth, type and number of identity document, check-in date, and — where applicable — check-out date.

That means a photo of the passport sitting in your downloads folder doesn't cut it. The data must be entered into the platform in a structured way, within the legally required timeframe.

When you need to report

Contrary to what many hosts assume, you're not required to submit the registration at the exact moment of check-in. The law allows three days from the guest's arrival to complete the submission — which gives you some operational breathing room, especially when guests arrive late at night.

That said, three days is not an invitation to let things pile up. The window exists to give you flexibility, not to encourage indefinite delay. In practice, the best habit is still to register as soon as possible after check-in — ideally the same day or the day after — so you don't risk quietly missing the deadline.

The key point: the clock starts from the guest's arrival, not the end of their stay. There's no scope for leaving everything until check-out.

The most common mistakes

After speaking with hosts from north to south, the same patterns keep coming up:

• Late submissions — the guest arrived, the registration got pushed back, and "later" ended up past the deadline.
• Incomplete or incorrect data — document number copied wrong, date of birth transposed, nationality missing.
• Forgotten guests — reporting the lead booker and overlooking the rest of the group.
• Never having accessed SIBA — hosts who don't even know they have login credentials.
• Process not updated when rules change — the platform or requirements shift, but the host keeps doing what they've always done.

None of these mistakes is catastrophic on its own. The problem is that they accumulate — and when an inspection happens, the track record matters.

What happens if you don't comply

Failing to report guest data, or reporting it incorrectly, constitutes an administrative offence. Fines vary depending on severity and whether there's a history of non-compliance, and can be applied to both the AL licence holder and the person responsible for managing the property.

Beyond the fine itself, a non-compliance record can complicate licence renewals and, in more serious cases, provide grounds for AL registration cancellation proceedings. It's not the most common outcome — but it happens, and it's entirely avoidable.

How to make this painless

The key is turning SIBA into an automatic part of check-in, not a standalone task. A few approaches that actually work:

Collect data before arrival

Ask guests, via a pre-arrival message, to send their identification details in advance. That way, at check-in you're just confirming and registering — not chasing information under pressure.

Build a check-in checklist

Simple and effective. For every booking: data collected ✓, SIBA submitted ✓. Two fields, no ambiguity.

Centralise everything in one place

If you manage more than one property, or if someone helps you run things, it's essential that the process is documented and accessible to everyone involved. When rules change — and they do — updating a centralised process is far easier than correcting habits scattered across multiple people.

Don't let it pile up

Even with the three-day window the law provides, the best system is one that doesn't rely on you remembering later. Make it a habit to submit the registration right after each arrival — before you close the tablet or laptop.

When the rules change

The SIBA platform has already gone through updates, and the legislation governing guest data reporting can be revised. That's not a reason for anxiety — it's a reason to have a system that doesn't rely on you remembering to check for news.

Hosts with documented, centralised processes adapt in hours. Hosts who carry everything in their heads discover they've been doing it wrong for months.

The short version

SIBA isn't complicated — it just requires consistency. Collect the right data, report it within three days of each arrival, and keep a record of what you've done. Everything else is routine.

The most expensive mistake isn't not knowing the rules. It's knowing them and not having a system that ensures you follow them every time — even when you're tired, even when the guest arrived late, even when you have three check-ins on the same day.

If you'd rather stop tracking this manually, ALerta was built for exactly that: it monitors your SIBA deadlines and alerts you before anything slips through.