SIBA Report Portugal
Every accommodation establishment in Portugal has to file an accommodation bulletin for each guest with SEF/SSI through SIBA, within three business days of check-in. This app builds those bulletins from your reservations, validates each one against what SIBA actually requires, and submits them: automatically, or when you press Send. Every row carries its own deadline, badged Urgent as the window closes and Overdue if it has passed.
- Live
- Per guest, 3 business days
- Portugal
A deadline that starts again with every arrival
- 3Business days from check-in
- 6Fields SIBA wants per guest
- 0Known-bad submissions sent
- AutoOr on demand
The SIBA Portugal app, end to end
The dashboard, the deadline column, fixing a flagged bulletin by hand, and what a transmission response looks like.
Watch the walkthroughOpens in a new tab.Three values, then check the connection state
- 1
Enter your SIBA credentials
Your establishment code, your accommodation unit's NIF as registered with SEF/SSI, and your activation key. There is an endpoint URL as well, which you normally should not touch.
- 2
Read the connection state carefully
The app reports one of three: configured correctly, connected in test mode, or not configured. Test mode matters: nothing sent from it counts as a real submission, so do not use it for actual reporting.
- 3
Import, review, send
Choose a period, import the reservations, and work through anything under View errors. Then let the automatic submission carry it, or press Send to get ahead of the deadline.
Validated first, corrected by hand if it has to be
Document types and nationalities, converted
SIBA wants its own codes. The app converts document type and nationality into the format required, and when a nationality cannot be recognised it flags the bulletin instead of sending it with a wrong code. A wrong code is worse than a late one.
Fix it in the app, and the fix sticks
Missing surname, no document, no date of birth. Edit bulletin lets you correct a guest by hand, and once you have, re-importing the period will not overwrite your correction. Your edit is treated as the better data, because it is.
A rejection reaches a human
If SIBA rejects a submission, both you and Starfish support get an email with the errors SIBA returned, and the app shows them too. The full response is expandable in the transmission history, so nothing is guessed at.
Two things this app is not
It is not INE. SIBA is a per-guest bulletin to SEF/SSI; IPCAMP is a monthly statistical return to INE. Different agencies, different deadlines, and most Portuguese campsites owe both. The INE Portugal app handles the other one.
It is not a ruling on who must be reported. The app reports every guest booked as a registered traveller on a reservation. Whether an exception applies to your establishment, or to a particular guest or situation, is a question for SEF/SSI or your accountant. Please ask them rather than inferring it from what the app does.
Frequently asked
What exactly is the deadline?
Three business days from check-in, counted Monday to Friday. The Deadline column tracks it per bulletin, badging Urgent as the window closes and Overdue once it has passed.
Do I have to use automatic submission?
No. Download the XML and upload it through SEF/SSI's own channels, or use the dashboard's Send button to submit on demand. Automatic is the default most establishments settle on.
I corrected a guest's details by hand. Will a re-import undo it?
No. A manually edited bulletin is marked as such and is protected from being replaced when that period is re-imported.
My connection says "test mode". Is that a problem?
Yes, if you think you are reporting. Test mode points at SEF/SSI's test environment and nothing sent from it counts. Check with support before submitting real guest data.
Why can't I press Send?
Either the period has no bulletins, or at least one is still invalid. Open View errors: the specific problem is named per row, and the app deliberately refuses to send a submission it knows is bad.
A guest's nationality is not recognised. What happens?
That bulletin is flagged rather than sent with a wrong code. Fix the nationality on the guest or in the bulletin, and it goes with the next submission.