Managing Multiple Airbnbs and Visitor Levy in Scotland

Managing visitor levy for one Airbnb is an admin task. Managing it across several Scottish properties is a system problem.

The moment you add more properties, you also add more booking channels, more council rules, more expiry dates, more exceptions, and more chances for one quiet mistake to survive until quarter-end.

If you manage multiple short-term lets in Scotland, the aim is to make each property record consistent enough that the portfolio total can be trusted.

Start with property-level records

Do not track visitor levy only in one portfolio-wide total.

Each property should have its own record for:

• Property name.
• Address.
• Council area.
• Licence number.
• Licence expiry date.
• Property type.
• Gas supply.
• EPC position.
• Private water status.
• Planning or control area status.
• Booking channels.
• Visitor levy scheme status.

That property context affects both compliance documents and levy calculations. A cottage in one council area may follow a different levy rule from a city flat in another.

Separate council rules

Visitor levy is local. This matters more in a multi-property setup.

Edinburgh, Glasgow, Aberdeen, Stirling, and West Dunbartonshire do not all have identical schemes. Rates, start dates, booking cutoffs, night caps, exemptions, and retention rules can differ.

So the portfolio workflow should never ask, "what is our Scottish visitor levy rate?"

It should ask:

• Which council is this property in?
• Which scheme applies?
• Is the stay after the scheme start date?
• Was the booking made after the relevant cutoff?
• Does a night cap apply?
• Is there an exemption or refund note?

That keeps local differences from disappearing into a single spreadsheet formula.

Standardise stay records

Every stay should use the same fields, even if the booking came from a different platform or was entered by a different person.

Use a standard stay record:

• Property.
• Booking reference.
• Booking source.
• Booking date.
• Payment or deposit date.
• Check-in and check-out dates.
• Accommodation-only charge.
• Extras excluded from levy.
• Levy amount.
• Exemption note.
• Return quarter.
• Return status.

This is where multi-property admin often breaks. One property manager writes "N/A", another leaves the cell blank, and another puts the explanation in an email. Standard fields prevent small differences becoming a reconciliation problem.

Watch amended bookings

Amended bookings are awkward because they can change dates, prices, nights, extras, and refund treatment.

For multi-property operators, amended bookings need a simple rule: keep the original booking reference and record what changed.

Track:

• Original booking date.
• New stay dates.
• New accommodation charge.
• Refunds or extra payments.
• Whether the council cutoff position changed.
• Whether the return quarter changed.

Without that history, the final amount may be right but impossible to explain.

Build quarterly returns from stay records

A quarterly return should be the result of checked stay records, not a fresh calculation exercise.

For each property and council area, review:

• Stays included in the quarter.
• Stays excluded and why.
• Total accommodation charge.
• Total levy collected.
• Provider retention.
• Amount due to the council.
• Return status.
• Payment confirmation.

If you manage properties in more than one council area, keep those return summaries separate. Local authorities can have different schemes and submission expectations.

Keep compliance and levy in the same operating view

Visitor levy is not the only deadline in a short-term let portfolio.

You also have:

• Licence renewals.
• Gas safety certificates.
• EICRs.
• PAT reports.
• EPCs.
• Insurance renewals.
• Fire safety evidence.
• Private water tests.
• Planning or control area evidence.

If levy is tracked in one spreadsheet and certificates are tracked somewhere else, the business has two admin systems that can drift apart. A single property view is easier to manage.

Hand-off matters

Multi-property operations often involve more than one person.

That might be an owner, cleaner, co-host, bookkeeper, manager, accountant, or agency admin. The visitor levy process should survive a hand-off.

Make sure someone can see:

• What still needs to be recorded.
• Which return is in draft.
• Which stays have exemption notes.
• Which documents are expiring.
• Which properties have missing evidence.
• Which council rules are provisional or changing.

If the process only works when one person remembers everything, it is too fragile.

FAQ

A better operating habit

For a multi-property operator, the best habit is consistent property-level tracking.

Keep each property, stay, document, and return in a structure that someone else can understand without calling you. That is where LevyTrack helps: less scattered admin, more repeatable evidence, and a clearer path from booking records to return review.