Real Estate

The Sign at Reception Does Nothing: A Montenegrin Hotel's Liability for Guests' Property

Article 820 makes the reception disclaimer legally worthless, and Article 816(3) removes the cap the moment you accept an item for safekeeping.

Rohat Kahraman· 5 September 2026Updated · 5 September 2026
Montenegro hotel liability for guests' property: the cap, the safekeeping exception and the void notice

Every hotel in Montenegro has the notice. It sits behind the desk or inside the wardrobe door, and it says the establishment accepts no responsibility for valuables not deposited in the safe. Operators treat it as the first line of defence, and buyers of hotel assets rarely ask about it during diligence.

The Obligations Act disposes of it in one sentence. Notices posted on the premises that exclude, limit or condition the operator's liability for things guests have brought in have no legal effect at all. And the arrangement most operators regard as their protection — inviting the guest to hand valuables to reception — is the arrangement that converts a capped liability into an unlimited one.

Article numbers below are from the Zakon o obligacionim odnosima, chain "Službeni list Crne Gore" br. 047/08 of 07.08.2008, 004/11, 022/17 of 03.04.2017 and 123/24, read on 5 September 2026. General information about Montenegrin law, not advice on a particular business.

The operator is a depositary by operation of law

Article 816(1) states the basic position without requiring any contract about it: the hospitality operator is treated as a depositary in respect of things the guests have brought in, and is liable for their disappearance or damage up to the amount established by a special regulation.

Two things follow immediately. The liability does not depend on the guest agreeing to it, asking for it, or paying for it — it attaches to the accommodation relationship itself. And it is capped, but the cap is not in the Act.

That last point is the first practical item for an operator or a buyer. The ceiling in Article 816(1) is set by secondary legislation rather than by the Obligations Act, so the figure has to be obtained from the applicable regulation and checked for its current version. An operator who does not know the number cannot know its exposure, and a buyer running diligence on a hotel cannot quantify a standing liability without it.

What counts as "brought in"

Article 817(1) defines the property covered, and the definition is wider than the room.

The regime applies to things in the establishment for the whole time the guest has accommodation there. It applies to things outside the establishment, at a place the operator has designated or taken under its supervision, or under the supervision of persons for whom it answers, for the whole of the accommodation period. And it applies to things over which the operator or those persons take supervision, inside or outside the establishment, within a reasonable time before or after the period of accommodation.

The third limb is the one that catches resorts. Luggage taken by a porter before check-in, or held after check-out while the guest has lunch, is inside the regime — the accommodation period is not the boundary; supervision within a reasonable time around it is.

Article 817(2) then carves out a significant category: the provisions on liability for things brought in do not apply to vehicles, things inside them, or animals — unless otherwise agreed.

A hotel car park is therefore not governed by this chapter by default. Whether the operator has liability for a vehicle or its contents is a matter of the contract it makes, which means it is also a matter of what its own terms say. An operator that has quietly assumed the statutory regime covers the car park has assumed the opposite of the position.

When the cap disappears

Article 816(3) contains the provision that inverts the usual operational instinct.

The operator owes full compensation — not the capped amount — in two situations: where the guest handed the item over for safekeeping, and where the damage arose through the operator's fault or the fault of persons for whom it answers.

The first of those is the safe-deposit arrangement itself. The moment reception accepts a watch, a laptop or an envelope for safekeeping, the relationship stops being the capped statutory deposit under Article 816(1) and becomes an ordinary one in which the operator owes the full value. The notice inviting guests to deposit valuables at reception, read against Article 816(3), is an invitation to convert a limited exposure into an unlimited one.

That is not an argument for refusing. Article 818(1) requires the operator to accept for safekeeping things guests bring and wish to hand over — unless it does not have suitable premises for storing them, or their safekeeping exceeds its capacity for some other reason. And Article 818(2) makes an unjustified refusal expensive: the operator then owes full compensation for the loss the guest suffers as a result.

So the operator is required to accept, and accepting removes the cap. What the Act leaves to the operator is the narrow ground in Article 818(1) — suitability of premises and capacity — and the record it keeps of what was accepted, from whom, and in what condition.

What excuses the operator

Article 816(2) excludes liability where the things were lost or damaged:

  • as a result of circumstances that could not be avoided or removed;
  • as a result of a cause in the thing itself; or
  • through the conduct of the guest, or of a person the guest brought in or who came to visit them.

The third limb is worth noting because it covers a common factual pattern: loss caused by the guest's own visitor is outside the operator's liability, without the operator having to prove anything about its own security arrangements.

Article 819 places a duty on the guest that is easy for an operator to overlook when handling a complaint. The guest must report the disappearance or damage as soon as they learn of it. A guest who does not has a right to compensation only if they prove that the damage arose through the fault of the operator or of persons for whom it answers.

That is a shift in the burden of proof rather than a bar. Late reporting does not extinguish the claim; it moves the claim from the near-strict regime of Article 816(1) to one where the guest must establish fault. For the operator, the operational consequence is that the time of the report should be recorded — because it decides which of two very different tests the claim is measured by.

The notice that does nothing

Article 820 is one sentence, and it is unqualified.

Notices displayed in the operator's premises by which liability for things brought in by guests is excluded, limited or made conditional have no legal effect whatsoever.

It does not matter where the notice is, how prominently it is displayed, or whether the guest read it. The Act does not treat it as a term that fails for want of agreement; it treats it as having no effect at all.

This does not mean an operator cannot contract about the subject. Article 817(2) expressly contemplates agreement about vehicles and animals, which is a contract rather than a notice. What Article 820 removes is the unilateral disclaimer posted on a wall.

For a buyer of a Montenegrin hotel, that makes the wall notice a diligence red flag rather than a mitigant. An operator relying on it has, in practice, been running an uninsured or under-insured exposure and believing otherwise.

The remedy the operator does have

Article 821 gives the operator something the disclaimer never did.

An operator that receives guests for the night has the right to retain the things the guests have brought in, until full payment of its claims for accommodation and other services.

That is a statutory right of retention over the guest's property, arising by law and not requiring a term in the booking conditions. It is limited in two ways worth noting: it belongs to an operator that receives guests for the night — so it attaches to accommodation rather than to a restaurant bill on its own — and it secures claims for accommodation and other services, which is the hotel's own account rather than damage claims at large.

Used carelessly it creates its own exposure, since retention of the wrong items or beyond the secured amount is not protected by the article. Used properly it is the operator's principal self-help against a departing guest with an unpaid bill.

The position in one table

SituationThe operator's liabilityProvision
Things brought in, ordinary caseLiable, capped at the amount set by the special regulationArt. 816(1)
The guest handed the item over for safekeepingFull compensation — no capArt. 816(3)
Damage through the operator's fault, or that of persons it answers forFull compensation — no capArt. 816(3)
Circumstances that could not be avoided or removed; a cause in the thing itself; conduct of the guest or of someone the guest brought in or who visited themExcludedArt. 816(2)
Operator unjustifiably refuses to accept an item for safekeepingFull compensation for the resulting lossArt. 818(2)
Guest fails to report the loss as soon as they learn of itCompensation only if the guest proves faultArt. 819
Vehicles, things inside them, and animalsOutside the regime, unless otherwise agreedArt. 817(2)
Notice on the premises excluding or limiting liabilityNo legal effect at allArt. 820

Where else the chapter applies

Article 822 extends the whole regime beyond hotels. The provisions on the hospitality deposit apply mutatis mutandis to hospitals, public garages, sleeping cars, organised camps and similar.

For a Montenegrin resort operation, the reference to public garages and organised camps is not incidental. A resort that runs a paid public garage, or a campsite alongside the hotel, is running an operation to which the same rules apply — including Article 820's rule about notices, which is precisely where garage and campsite operators tend to rely on signage most heavily.

What this changes for an owner or a buyer

The chapter is short, and almost all of its practical weight sits in four points.

The liability exists whether or not anyone agreed to it, and is capped by a figure that is not in the Act — so establishing the current regulated amount is the first step, and the only way to size the exposure.

Accepting an item at reception removes the cap under Article 816(3), while refusing without a good reason creates full liability under Article 818(2). The operator's discretion sits in the narrow space between them, and the record of what was accepted is what evidences it.

The wall notice is legally inert under Article 820, so any real limitation has to come from insurance, from the operational controls, and from the exclusions in Article 816(2) — not from the sign.

And vehicles are outside the regime unless agreed under Article 817(2), which means car park liability is decided by what the operator's own terms say rather than by this chapter.

For a condo-hotel or a rental-pool structure, one further question sits underneath all of this: which entity is the ugostitelj. The liability in Article 816 attaches to the hospitality operator, not to the unit owner — so the allocation of that exposure between the operating company and the owners, and the insurance behind it, belongs in the management agreement rather than in the assumption that it follows the title.

If you own, operate or are acquiring a hotel or resort in Montenegro, our hotel investment work covers the operating structure and this exposure, and compensation claims covers the claims themselves.