The Insurance Behind a Rental Licence: The Annual Renewal That Takes Listings Offline
Compliance and Rules

The Insurance Behind a Rental Licence: The Annual Renewal That Takes Listings Offline

Localsbnb Editorial TeamSeptember 27, 20268 min read

In some markets liability cover isn't filed as insurance at all. It's filed as a condition of the registration, and the register closes when it lapses. This guide separates the renewal date you remember from the one that counts, and puts the whole thing on a yearly schedule.

Real photo of a dining area in a furnished rental, with a 'The cover that lapses' headline overlay
In some markets the liability policy is a condition of the registration, not a document filed beside it.

In several markets the liability cover is not filed as insurance. It is filed as a condition of the registration, and the register closes when it lapses.

Last updated: September 28, 2026

Most hosts treat their liability policy as a bill that arrives once a year. In some markets it's also a document the regulator holds, and the registration depends on it staying current. That changes what a missed renewal actually costs, which is why this guide treats the insurance date, the filing date and the registration as one piece of work rather than three.

Key Takeaways

  • Cover can sit inside the licence. In some markets the liability policy is a condition of the registration, so the entry closes when the cover lapses.
  • Two dates decide it. The date your policy renews isn't always the date the register expects the certificate on file.
  • The register reads documents. What arrives is a certificate with dates and a unit number on it, not a statement of intent.
  • Portugal is the worked example. Public reporting describes a €75,000-per-incident cover requirement and a maximum fine of €40,000 for operating without valid registration, both of which are Portugal's.
  • Build it into the year. Put the registration's clock on the same schedule as the policy, not on the anniversary you happen to remember.

Why cover sometimes sits inside the registration, not beside it

In a lot of markets, liability insurance is a private arrangement between you and an insurer. It protects you if something goes wrong, and if you let it lapse the consequence is financial. You carry the risk yourself until the policy is back.

In some markets it isn't only that. The policy is named as a condition of the registration itself, so the authority treats the certificate as part of its own file. The registration is valid while the cover holds, and when the cover lapses the entry stops being supported. The consequence changes character: it stops being a bill you owe and becomes an operational problem, because the listing can no longer sell.

Portugal is the clearest current example. Public reporting describes AL registration as requiring civil liability insurance of at least €75,000 per incident, tied to holding the registration. It puts the maximum fine for operating without a valid registration at €40,000 (public reporting, 2026; confirm the current figures with the Portuguese authority before relying on them). Both numbers are Portugal's. They are a floor and a ceiling set by one country's rules, and they don't transfer to anywhere else.

The distinction is worth holding on to, because it changes what you're maintaining. If cover sits beside the registration, you're managing a premium. If it sits inside it, you're managing a permission.

The renewal date that matters versus the one you remember

Almost every owner remembers one date: the policy anniversary, because that's the date on the invoice and the date the direct debit moves. The register cares about a different one, which is the date by which the certificate has to be on file. Those two dates come from different parties, and they rarely coincide.

The insurer sets the policy's start and end. The authority sets its own filing window. Between the two there's often a gap — a stretch of days or weeks when the old certificate has run out and the new one hasn't reached the register yet. That gap is where a lapse lives, and it's completely invisible if the only date you track is the invoice.

The amount is a second trap, and it fails for a different reason. A policy can renew perfectly on time and still not satisfy the register, if the limit of cover has drifted below the floor the authority requires. The insurer is content because the premium was paid. The register isn't, because the certificate no longer meets its condition. The floor belongs to the authority, not to the policy you chose.

So keep three dates per unit, not one. The policy's start, the policy's end, and the last date on which the register confirmed the entry as valid. The third one is the one that tells you whether the filing, not just the payment, completed.

Card: the two renewal dates behind a rental licence and the gap between them
The date on the invoice isn't always the date the register is working to.
Card: what the register actually receives when a rental licence is renewed
What arrives is a certificate with dates, a cover amount and a property identifier on it.

What the register actually receives when you renew

It's worth being precise about this, because renewing feels like a bigger event than the register experiences. What arrives is a document. It carries dates, a cover amount and an identifier for the property. That's the whole of the transaction from the register's side.

That means the register can only check what the document says. It can see whether the cover runs from a date before the old one expired. It can see whether the limit meets the floor. It can see whether the certificate names the unit that the registration was issued for. It can't see that you meant to file it last month, or that the insurer was slow, or that the certificate is sitting in an email you haven't opened.

The practical consequence is a short checklist before you file anything. Confirm the dates on the new certificate start before the old cover ends. Confirm the limit still meets the authority's floor, not last year's one. Confirm the property on the certificate matches the property on the registration. Then file it, and note the date you filed it, because that date is your evidence if the register hasn't updated yet.

The documents also need somewhere to live that isn't a shared inbox. Where bookings are involved, the same folder tends to collect guest names, phone numbers and ID details, and those deserve more care than a certificate does. LOCALSBNB keeps credentials on the local device only, masks guest names, phone numbers and ID numbers, and grants access by domain, so the paperwork behind a booking isn't sitting in the open. The same account shows each direct channel's source price and source status, which is where a listing that has stopped selling surfaces first — that view is at localsbnb.com.

Building the renewal into the year rather than onto it

Most hosts handle this renewal by bolting it onto the year when the reminder lands. The problem with that method is the reminder's timing, which belongs to the insurer rather than to you, and the register's deadline, which belongs to the authority. Neither of them knows about your busy month.

Building it in works differently. You give the renewal a fixed slot on a schedule you already keep, and you work backwards from the cover's end date to a point where there's still enough room for a new certificate to be issued and filed. The exact buffer is yours to choose; what matters is that the first check happens while there's still time to fix a problem rather than after the cover has already stopped.

Then do the same three confirmations you'd do on any filing: dates, limit, property. A renewal that passes all three is done, and it stays done until the next slot. A renewal that fails one of them is a conversation with the insurer or the authority, and the earlier you have that conversation, the cheaper it is.

Finally, keep last year's certificate alongside this year's. When the register queries a gap, or an insurer asks what was in force on a date, the answer is a document rather than a memory.

LOCALSBNB — start free

FAQ

Is liability insurance required to hold a short-term rental licence?

It depends on the market, and in some places the answer is yes. Public reporting describes Portugal's AL registration as requiring civil liability insurance of at least €75,000 per incident, and it puts the maximum fine for operating without a valid registration at €40,000. Those figures belong to Portugal; check your own authority's current requirement.

Which date should I set my reminder from?

Use the earlier of the two risks, not the date on the invoice. The cover's end date tells you when protection stops, and the authority's filing window tells you when the register expects the document. Track the policy's end date as the one that matters, and leave enough room to get a certificate issued and filed before it.

What happens if the cover lapses while guests are already booked?

In a market where the policy is a condition of the registration, the risk isn't only financial. The entry can stop being valid, and a listing that can't verify its number can stop selling while guests are still on the calendar. That's the case for treating the renewal as a filing with a deadline rather than a payment with a due date.

The insurance behind a rental licence is one of the few annual tasks where the paperwork and the permission are the same thing. Track the dates that belong to the policy and the dates that belong to the authority, file the certificate early enough that a problem has room to be fixed, and keep what you filed. If you want the listing side of that in one view, the calendar at localsbnb.com keeps Airbnb, Booking.com, Agoda and Trip.com together with each channel's own status.


This article is general guidance for hosts and isn't legal or insurance advice. Cover requirements, filing rules and penalties differ by country and change over time; the figures quoted here come from public reporting about Portugal in 2026, and your local authority's current requirements prevail.

Reviewed by

Localsbnb Editorial Team