Visitor Levy Recordkeeping Checklist for Scottish Airbnb Hosts

Visitor levy recordkeeping is where a simple percentage turns into real admin.

For a Scottish Airbnb host, the question is not only "did I charge the right amount?" It is "can I still explain that amount when the quarterly return is due, when a booking changes, or when the council asks how a figure was worked out?"

VisitScotland's visitor levy guidance says accommodation businesses must keep accurate records and submit returns as required by the local authority. Edinburgh's scheme material also points to a five-year record retention period under the Visitor Levy (Scotland) Act 2024.

So the practical aim is simple: keep enough information beside each stay that you do not have to rebuild the story later.

Booking details

Start with the booking basics. These are the fields that connect the guest stay to the return period and the council scheme.

• Property name or internal property reference.
• Council area.
• Booking platform or direct booking source.
• Booking reference.
• Guest name or anonymised guest reference.
• Booking date.
• Payment or deposit date where the local cutoff depends on payment.
• Check-in date.
• Check-out date.
• Number of nights.

The booking date matters more than many hosts expect. Edinburgh, Stirling, Glasgow, and West Dunbartonshire all have advance booking rules or cutoffs that can decide whether a future stay is in scope.

Money fields

Do not keep only the final guest total. That number is usually too blunt for levy work.

Keep:

• Accommodation-only charge.
• Extras excluded from the levy calculation.
• Cleaning or standard accommodation costs included in the reasonable accommodation cost.
• Discounts or manual adjustments.
• Levy rate used.
• Nights subject to levy.
• Levy amount charged.
• VAT treatment or VAT estimate if relevant.
• Provider retention amount where the local scheme allows it.
• Amount due to the council.

VisitScotland says the percentage charge should only be applied to the accommodation part of the stay, with separate or optional extras excluded. If your booking export bundles everything together, add a working column or note that shows how you split the amount.

Council rule evidence

For each stay, you should be able to answer why the levy did or did not apply.

Record:

• The council scheme used.
• Scheme start date.
• Advance booking cutoff.
• Whether the booking was before or after the cutoff.
• Whether the stay started before, during, or after the scheme start date.
• Any night cap or long-stay rule.
• Any local exemption or refund route.

This is especially important if you operate in more than one council area. A rule that is correct for Edinburgh may be wrong for Glasgow or Stirling.

Exemption and refund notes

Do not treat exemptions as blank rows.

If a stay is exempt, refunded, or outside scope, keep a clear note beside it. A useful note should explain:

• The reason the stay was treated differently.
• Whether the guest paid first and later reclaimed the levy.
• What evidence was provided.
• Who made the decision.
• When the decision was recorded.

Some hosts will be tempted to keep exemption evidence in email threads or message apps. That might work while the booking is fresh, but it gets painful later. Keep the note close to the booking record.

Return and payment evidence

The Improvement Service says visitorlevy.scot is being developed as a secure way to register, submit returns, and make payments where councils have approved schemes.

That portal is for reporting and collection from accommodation providers to local authorities. It is not your guest checkout system.

For each return period, keep:

• Council area.
• Reporting quarter or period.
• Stays included.
• Stays excluded and why.
• Total accommodation charge.
• Total levy collected.
• Provider retention.
• Amount paid to the council.
• Return submission date.
• Payment date.
• Receipt or confirmation reference.

That might sound like a lot. In practice, most of it can be captured automatically if your booking records are clean from the start.

A simple example

Imagine a three-night Edinburgh booking after 24 July 2026.

The guest paid £420 for accommodation and £30 for optional extras. The booking was made after 1 October 2025, so it is inside the Edinburgh cutoff. Edinburgh's rate is 5%, and the stay is shorter than the five-night cap.

Your record should not just say "levy: £21".

It should show:

• Accommodation charge: £420.
• Extras excluded: £30.
• Booking date: after 1 October 2025.
• Stay dates: after 24 July 2026.
• Nights subject to levy: 3.
• Levy rate: 5%.
• Levy amount: £21.
• Reason: eligible Edinburgh stay, no exemption.

That is the difference between a number and an audit trail.

What not to rely on

Avoid relying only on:

• Platform payout totals.
• Calendar blocks.
• Guest message threads.
• Bank deposits.
• Memory of why a booking was excluded.
• One spreadsheet cell with no calculation note.

Those records may help, but they rarely explain the whole levy position on their own.

FAQ

Where LevyTrack fits

LevyTrack is designed for the gap between your booking platform and the council return.

Use the visitor levy calculator to check a stay, then keep the result alongside the booking details, exemption notes, and quarterly return status. For council-specific rules, start with the Scottish visitor levy guides.