How to Prepare Quarterly Visitor Levy Returns in Scotland

A quarterly visitor levy return is not something you want to build from scratch on the final day of the quarter.

By then, the awkward work has already happened: direct bookings, platform bookings, deposits, amended stays, optional extras, exemptions, refunds, and council-specific rules. The return is just where all of that either lines up or starts arguing with itself.

The visitorlevy.scot service is being developed for registration, returns, and payments. Accommodation providers still need their own booking and levy records ready before they submit.

Here is a practical way to prepare.

1. Confirm the council and return period

Start with the council area. Visitor levy is local, so one property in Edinburgh and one property in Glasgow should not be merged into a single working total.

For each return, confirm:

• Council area.
• Property or properties included.
• Return period.
• Stays that took place during the period.
• Stays that were booked in the period but happen later.
• Stays that were cancelled, refunded, or moved.

For most levy work, stay dates matter more than payment dates. Payment records are still useful, but they do not replace the need to know when the guest actually stayed.

2. Pull the stay-level records

A return total is only as good as the stay records underneath it.

For each stay, pull:

• Booking reference.
• Booking source.
• Booking date.
• Check-in and check-out dates.
• Accommodation-only charge.
• Extras excluded from levy.
• Levy rate.
• Night cap or full-stay rule.
• Exemption or refund notes.
• Levy amount collected.

If your bookings come from more than one channel, do this before the quarter closes. Platform exports rarely have identical columns, and direct bookings often need more manual cleanup.

3. Recalculate a sample before trusting the total

Before submitting, test a few stays manually.

Choose:

• One normal stay.
• One stay near the council start date.
• One booking near the advance booking cutoff.
• One stay with extras.
• One longer stay where a night cap might apply.
• One exempt or refunded stay.

This catches most of the mistakes that matter. A single wrong column can quietly turn into a wrong return total.

4. Separate accommodation from extras

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

That makes reconciliation easier if your booking process already separates:

• Accommodation.
• Meals and drinks.
• Transport.
• Parking.
• Optional services.
• Manual extras.

If your booking platform exports only the guest total, keep a working note showing how you got back to the accommodation-only figure.

5. Check exemptions and out-of-scope stays

A quarterly return should not only contain the stays where levy was charged. It should also make sense of the stays where levy was not charged.

Look for:

• Bookings made before the council cutoff.
• Stays before the scheme start date.
• Cancelled bookings.
• Refunds.
• Exempt visitors.
• Longer stays with local handling.
• Manual adjustments.

Do not leave these as unexplained blanks. A short note now can save a slow search later.

6. Reconcile the money

Once the stays are checked, reconcile the totals.

You want to know:

• Total accommodation charges included in the return.
• Total levy collected.
• Provider retention, if the council scheme allows it.
• Net amount due to the council.
• Any VAT estimate or accounting note you need to pass to your accountant.
• Difference between expected levy and platform/direct payment records.

Small differences should be investigated while the bookings are still fresh. Waiting until the portal asks for a number is how quarter-end becomes a rummage through exports and messages.

7. Submit and save the evidence

When the return is submitted, keep the confirmation beside the working records.

Save:

• Submission date.
• Amount submitted.
• Amount paid.
• Payment date.
• Receipt or confirmation reference.
• Any adjustment note.

If you later need to answer a question about that quarter, you want the return total and the supporting stays in the same place.

FAQ

The calmer way to do it

The best quarterly return process starts at booking level.

If each stay already has the council, dates, accommodation charge, levy amount, exemption note, and return period attached, the return becomes a review. If those details live across calendars, platform exports, inboxes, and memory, the return becomes detective work.

LevyTrack helps with the boring but important middle bit: turning stay-level calculations into return-ready totals before you log into the official portal.