Best Way to Track Airbnb Visitor Levy in Scotland

The best way to track Airbnb visitor levy in Scotland is to track it at stay level, not just as a monthly total.

That means every booking should keep the council area, booking date, stay dates, accommodation-only charge, extras, exemption notes, levy amount, and return period together. If you only keep the guest payout total, you will probably have to rebuild the calculation later.

Last checked: 22 May 2026 against VisitScotland and Improvement Service visitor levy guidance.

Why Airbnb payout totals are not enough

Airbnb and other booking platforms are useful for taking bookings, but visitor levy compliance has a few extra questions.

You need to know:

• Which council scheme applies.
• Whether the stay is after the local start date.
• Whether the booking was made after any advance booking cutoff.
• What part of the guest charge is accommodation.
• What extras should be excluded.
• Whether a night cap applies.
• Whether the stay is exempt or refunded.
• Which quarterly return the stay belongs to.

A payout total might help with reconciliation, but it usually does not explain all of that on its own.

The minimum fields to track

For each Airbnb stay, keep:

• Property name.
• Council area.
• Booking reference.
• Booking platform.
• Booking date.
• Payment or deposit date where relevant.
• Check-in and check-out dates.
• Number of nights.
• Accommodation-only charge.
• Extras excluded from levy.
• Levy rate.
• Nights subject to levy.
• Levy amount collected.
• Exemption or refund notes.
• Reporting quarter.
• Return submission status.

This looks like a lot until the first return is due. Then it looks like the difference between a review task and an evening of detective work.

Use the council rule, not a generic tourist tax field

There is no single Scottish visitor levy rate or start date.

Edinburgh has a 5% rate, a 24 July 2026 start, a 1 October 2025 booking cutoff, and a five-night cap. Glasgow uses a 5% rate with a full-stay model. Stirling has a 3% rate and different local exemption detail. West Dunbartonshire has its own 2027 start and booking cutoff.

So the tracking system needs to know which council scheme applies. A generic "tourist tax" column is too thin once you manage more than one property or council area.

Keep accommodation separate from extras

VisitScotland says the visitor levy percentage should be applied to the accommodation part of the stay, with separate or optional extras excluded.

That means your tracking should separate:

• Accommodation.
• Meals and drinks.
• Transport.
• Parking.
• Optional services.
• Manual extras or add-ons.

If you charge everything as one bundled guest total, keep a working note that explains how the accommodation-only amount was calculated.

Track exemptions as evidence, not blank cells

An exemption is not an empty levy amount. It is a decision that should be explainable later.

Keep:

• Why the stay was treated as exempt or outside scope.
• What evidence supported that treatment.
• Whether the guest paid first and was refunded.
• Who recorded the decision.
• When the note was added.

This matters for edge cases such as local residents, carers, longer stays, cancelled stays, bookings made before a cutoff, and stays that cross a scheme start date.

The spreadsheet approach

A spreadsheet can work if you have one property, one council, a small number of bookings, and a careful habit of updating it every time something changes.

The spreadsheet should have columns for the fields above, plus formulas for:

• Nights stayed.
• Nights subject to levy.
• Charge subject to levy.
• Levy amount.
• Provider retention.
• Amount due to the council.
• Return quarter.

The weakness is not the first version of the spreadsheet. It is what happens after amendments, refunds, extra properties, copied formulas, council rule changes, and a busy August.

The software approach

Visitor levy software should reduce the amount of interpretation sitting inside a spreadsheet.

For Scottish hosts, useful software should:

• Store council-specific rules.
• Calculate in pence, not rough decimals.
• Keep booking cutoffs visible.
• Separate accommodation from extras.
• Save exemption notes.
• Group stays into return periods.
• Keep return status visible.
• Support multi-property review.

LevyTrack is built for that middle layer. It does not replace Airbnb, a channel manager, or visitorlevy.scot. It helps turn booking records into cleaner levy evidence before you submit returns through the official service.

FAQ

The practical answer

If you are taking only a few bookings, start with a careful stay-level spreadsheet. If you manage multiple properties, multiple channels, or council-specific rules, use software before the spreadsheet becomes the risk.

You can start with the visitor levy calculator, then use LevyTrack's features to keep calculations, records, and return preparation in one place.