The Municipality of Amsterdam runs an algorithm against your address.
This is not a figure of speech. The city operates a risk-scoring system that cross-references rental listings against the population register and the buildings register to estimate the likelihood that a given address is being let illegally. It is publicly documented in the Dutch government's Algorithm Register. Scored addresses are prioritised for a dedicated enforcement team, Team Vakantieverhuur, which conducts physical inspections.
Now consider what you are being scored against. In Amsterdam a holiday rental requires an annual permit, is capped at a limited number of nights per calendar year, allows a maximum of four people at a time including children, and must be notified to the municipality in advance of every single rental period. Administrative fines have been issued in the range of several thousand euros up to figures north of twenty thousand.
And the burden falls on you. Dutch courts have held that a host's own screenshots do not constitute evidence.
That combination, machine-driven detection plus an evidence burden you cannot meet with a phone gallery, makes Amsterdam the market in this series where documentation is not a benefit of good operations. It is the operation.
The rules you are being measured against
The specifics matter here more than usual, because the algorithm is checking specifics.
The night cap. Amsterdam has operated one of Europe's tightest annual limits on letting a primary residence. From 1 April 2026 the city moved to reduce the permitted nights in central districts including Centrum and De Pijp, with the practical effect that operators in those areas who reach the lower threshold early in the year cannot host again for the remainder of it. Confirm the current figure for your specific district with the municipality before you take a single booking, because this has changed and may change again.
Four people, no exceptions. The occupancy limit counts everyone, children included. A family of two adults and three children exceeds it. This is the sort of detail that produces fines.
Notification before every stay. You report each rental period to the municipality in advance, using your permit number and DigiD. Missing a notification is a violation in its own right, independent of whether you were within your nights.
An annual permit. Valid for one calendar year and reapplied for each year.
Building rules. A VvE, the Dutch owners association, may prohibit or restrict holiday letting in its own rules, separately from anything the municipality permits.
Tax. Dutch VAT treatment for short-stay accommodation moved to the higher rate in January 2026, on top of the city's tourist tax.
Each of those is a discrete, checkable fact. Nights are countable. Occupancy is countable. Notifications either exist in the system or they do not. This is a regime designed to be audited by software, and it is.
What you can actually prove
Put yourself in the position most Amsterdam hosts eventually find themselves in. A letter arrives asserting a violation on specific dates. You believe you were compliant. What can you produce?
Your booking platform's records show a reservation for a number of guests. That is a statement of what was booked, not of what happened. If six people turned up to a booking for four, the platform record says four.
Your notifications to the municipality show what you declared. Also a statement of intent.
Your own photographs, messages and calendar entries have been held not to constitute evidence.
What is missing is an independent, contemporaneous record of what physically occurred at the property, generated by a system that has no interest in the outcome.
An access system produces exactly that. When a key is collected, the record captures which key, which person, and the moment it happened. Same on return. Because access is issued to individuals rather than as a shared code, the record distinguishes between one guest collecting a key and four separate people collecting four.
That gives you three things Amsterdam specifically asks about:
Occupancy evidence. How many distinct individuals were granted and used access for a given stay.
Date evidence. Precisely which nights the property was actually occupied by guests, independent of what a platform calendar says, which supports your own night count against the cap.
Third-party provenance. The record is generated and held by a system you do not author, timestamped at the moment of the event, and exportable. That is a materially different category of evidence from a screenshot taken afterwards.
To be clear about the limit: this does not file your notifications, hold your permit, or count your nights for regulatory purposes. Those are your obligations and you should run them properly. What it does is give you something to put on the table when your version of events is challenged.
Canal houses, stairs, and where hardware fits
Amsterdam's physical stock is its own constraint.
The canal-belt houses are narrow, deep, tall and old. Staircases in the older stock are famously steep, often closer to a ladder than a stair. Many buildings lean. Frontages within the protected historic centre carry heritage restrictions on what may be attached, and hoisting furniture through a window is a normal Amsterdam activity rather than an unusual one.
Realistic placements:
Inside the front door. The entrance hall or the base of the stair, past the street door. Private, sheltered, and out of the heritage frontage question. Needs the VvE's agreement where the hall is shared.
Ground-floor commercial space. For operators with several properties across the Grachtengordel, Jordaan or De Pijp, a small leased space gives you a street-level address available at any hour and removes the VvE from the equation. Amsterdam's centre is small and everyone cycles or walks, so a cluster point genuinely serves a wide area.
Newer developments. Buildings in IJburg, the Zuidas and the eastern docklands have lobbies and service areas with power and connectivity and none of the heritage complications.
The unit fixes flat to a wall, projects about four inches, and is rated IP52, which suits interior and sheltered positions. In a city with Amsterdam's weather and building stock, indoors is the default.
The VvE conversation
Where the entrance hall is common property, you need the owners association on side, and Amsterdam VvEs have generally grown less patient with holiday letting rather than more.
The argument that works is the one about control. What a VvE dislikes is unidentified people arriving at all hours with a code from an email, keys left under mats, boxes appearing on the railing outside a listed frontage, and no way to establish who was in the building. A system where access is issued to named individuals, logged, and revocable answers each of those, and the association can be offered visibility of the record.
Go in with the specifics written down: exact position, fixing method, dimensions, power and network, maintenance responsibility, and what happens on removal.
Be the operator with the record
Amsterdam has built one of the most data-driven enforcement regimes in Europe. It scores addresses algorithmically, inspects physically, requires a declaration before every stay, and does not accept your screenshots.
The response is not to hope the algorithm looks elsewhere. It is to run an operation that generates its own independent, timestamped, exportable account of who entered your property and when, so that when the letter arrives you are producing a record rather than assembling a story.
Configure a SmartBox deployment or talk to our team about an Amsterdam installation.
Regulatory details in this article reflect publicly available information at the time of writing and are provided for general guidance only. Amsterdam's night caps, permit requirements, notification obligations and fine levels have changed repeatedly and continue to change by district. Confirm current requirements with the Gemeente Amsterdam, your VvE, and qualified Dutch advisers before making operational decisions.
