The Scottish Visitor Levy: The Accounting Complications the Scheme Design Has Handed Operators

In short: Edinburgh's 5% visitor levy went live on 24 July 2026, making Edinburgh the first Scottish council to switch it on. Highland is consulting on a £5-per-night flat rate through November 2026, with Glasgow (7%, from 1 April 2027) and Aberdeen (7%, year round) queued behind. The accounting-side problems the scheme design creates are still live — VAT treatment, platform remittance mechanics, and a mismatch between VisitScotland's "may or may not" guidance on OTA commissions and Edinburgh Council's insistence that the levy applies on gross. A fixed-rate scheme of the kind Highland has adopted would remove most of the operational pain. This piece walks through what operators need to plan around now.

The Visitor Levy (Scotland) Act 2024 handed each Scottish local authority the power to introduce a per-night charge on paid overnight accommodation. Edinburgh moved first. Others are on the way. For an STL operator, the levy is not the biggest accounting question of the year, but it is one of the most operationally awkward — and the accounting-side complications the sector's own trade bodies flagged during the Bill are, twelve months later, still not resolved.

Where the map now sits

Four councils to have on the radar in the next six months:

• Edinburgh — live from 24 July 2026. 5% of accommodation cost, before VAT, capped at the first five consecutive nights of any stay. Applies to any booking made on or after 1 October 2025 for a stay from 24 July 2026 onwards. Bookings paid in full or in part before 1 October 2025 are outside the scope. Operators retain 2% of the amount collected to offset administrative cost (The Scheme for the Edinburgh Visitor Levy).
• Highland — consultation open 7 September to 30 November 2026 on a proposed £5 per room per night flat rate for hotels, B&Bs, self-catering and short-term lets, £2 per night for hostels and campsites. Full Council decides on 10 December 2026 (Highland Council announcement).
• Glasgow — 7% of accommodation cost, applied to the full length of any stay (no five-night cap), live from 1 April 2027.
• Aberdeen — 7% of accommodation cost, year-round, live in 2027.

The rate structures are already inconsistent — percentage in one place, flat rate in another, capped in one, uncapped in the next. A portfolio operator across multiple Scottish authorities is facing several different levy frameworks in parallel.

Complication one: the VAT treatment nobody has fixed

This is the most consequential accounting question the levy creates, and the one where the sector's professional bodies have been loudest.

HMRC and Edinburgh Council currently take the position that the visitor levy amount an operator collects counts towards their taxable turnover for VAT purposes. It is not, in HMRC's current view, outside the scope of VAT in the way many operators (and their accountants) had assumed by analogy with the Welsh scheme.

The Chartered Institute of Taxation and the Institute of Chartered Accountants of Scotland wrote jointly to HMRC and the Scottish Government in mid-2025 setting out why this is a serious unintended consequence. The core objection: including the levy in taxable turnover pushes many small self-catering operators over the £90,000 VAT registration threshold who would otherwise sit safely below it. A self-caterer at £85,000 of accommodation turnover collecting a 5% levy in Edinburgh is suddenly at close to £89,250 — one busy weekend from mandatory VAT registration on income the operator never treated as their own.

HMRC has agreed to publish clarifying guidance across the UK visitor-levy landscape. As at this writing, that guidance has not landed. In the meantime the safe planning assumption is HMRC's current position: the levy is turnover for VAT registration purposes.

Complication two: the platforms can collect but cannot remit

The Act makes the accommodation provider — not the platform — the liable person. Airbnb, Booking.com and similar can (and in some cases do) collect the levy from guests at booking, but they cannot remit that money to Edinburgh Council on the operator's behalf. The operator is legally on the hook for the quarterly return and quarterly payment, even where the platform has already extracted the cash from the guest (LevyTrack — VAT in Scotland).

The operational implication is that platform-collected levy money flows to the operator in the payout, is not marked as levy in the payout statement, and needs to be actively identified and set aside for quarterly remittance. Where the operator's bookkeeping treats the payout as one line, the levy component silently disappears into working capital — and reappears as a shortfall on the return.

Complication three: bookings that straddled the commencement window

Edinburgh's rule is that a stay from 24 July 2026 onwards is levy-liable if the booking was made on or after 1 October 2025. Any part-payment before that cutoff moves the whole booking outside the scope. This looks clean in principle. In practice it has already produced disputes on:

• Deposit-plus-balance bookings paid in two tranches straddling the cutoff.
• Bookings modified after the cutoff (dates changed, guest numbers changed) — whether a modification is a new booking for levy purposes.
• Rolling multi-year corporate reservations for the Festival period, some of which were originally struck years in advance.

Operators are being pressed to keep evidence of booking date and payment date for every reservation into 2026 and 2027. The bookkeeping side needs to accommodate a "pre-cutoff / post-cutoff" flag on every reservation — most software does not do this out of the box.

Complication four: OTA commissions — the "may or may not" problem

The current statutory reference document — the VisitScotland Local Authority Guidance on the Visitor Levy — leaves the treatment of OTA commissions genuinely unresolved, and does so in language that places the entire burden of evidencing the approach on the accommodation provider.

Paragraph 19 of the guidance, on commission in a percentage-rate scheme:

"Commission may or may not be included in the accommodation portion on which the visitor levy is calculated, and it is for the liable person to be able to evidence the approach taken."

That is not equivocation by accident. It is the operative sentence. Two paragraphs later (paragraph 21), the guidance explains why the equivocation matters in practice — and why the operator's exposure is real:

"OTAs will have different processes for how they manage the visitor levy and commission … Depending on the approach taken, this may affect whether the visitor levy is treated as a non-commissionable charge. In some cases, this could result in the liable person bearing commission costs attributable to the visitor levy."

The tension operators are actually running into is not with the VisitScotland guidance itself — it is with Edinburgh Council. In our experience with Edinburgh operators to date, the Council's collection practice takes the position that the levy applies to the gross accommodation cost inclusive of OTA commission, regardless of the "may or may not" latitude VisitScotland has left in the statutory document. That is a defensible reading of the guidance, but it is not the only one — and the operators who have set their systems up to calculate on the net figure the operator retains are now discovering that Edinburgh's remittance expectation does not match the arithmetic they built.

The operator-facing consequences of this are three, and each of them lands on the accommodation provider, not on the platform:

1. The Edinburgh position may not be the position in Glasgow, Aberdeen or elsewhere. The Council-level enforcement stance is being set locally, on top of a national guidance document that authorises either approach. Portfolio operators across multiple Scottish authorities should assume the interpretation will vary and prepare to defend both readings on the same booking data.

2. The operator may end up paying commission on the levy itself. Paragraph 21's language ("bearing commission costs attributable to the visitor levy") is the tell. Where an OTA does not treat the levy as a non-commissionable charge — and each platform's approach differs — the platform's percentage commission is calculated on the levy-inclusive figure. The operator remits the levy to the council and pays commission to the platform on the same amount. This is a real margin hit, not a theoretical one.

3. The evidencing burden is unlimited. "It is for the liable person to be able to evidence the approach taken" reads simply and imposes broadly. In practice this means every operator should retain, for every OTA booking, a documented workings showing the approach taken to commission, the platform's commission policy on the levy, the levy calculation, and the reasoning. Most bookkeeping set-ups do not capture this today.

Our current position, as an accounting practice: for Edinburgh operators specifically, apply the levy to the gross accommodation price the visitor pays — inclusive of the platform's commission. That matches Edinburgh Council's collection stance and removes the primary dispute risk. For operators elsewhere in Scotland once other councils switch their levies on, take the calculation position that fits the specific council's published enforcement approach at that time, and document the reasoning contemporaneously. Where a client wants to net down for commission to reduce the levy figure — legitimately open on the VisitScotland guidance — we require a documented workings on file, written confirmation of the OTA's treatment of the levy, and, in Edinburgh's case, written council confirmation of the position before we sign off.

Until either VisitScotland tightens the guidance or the Scottish Government brings forward regulations, this remains a live area of operator judgement, not a settled compliance question — and generalist accountants are, in our experience, not yet capturing the evidencing side of it at all.

Complication five: what the ASSC is challenging on Edinburgh's revenue use

The Association of Scotland's Self-Caterers has been openly critical of Edinburgh Council's plan to route a substantial portion of the levy revenue into affordable housing spending. The Act requires levy revenue to be applied to "facilities and services substantially used by business and leisure visitors." The ASSC's position, backed by legal opinion, is that permanent social housing does not obviously fall within that definition — and that the housing use of levy funds could be open to judicial review.

For operators, the point is not the merits of the challenge, which are yet to be tested. The point is that Edinburgh's revenue-use decisions have already introduced legal uncertainty into what the sector was told the levy would be spent on. Any future material change to the scheme (rate, scope, exemptions) becomes materially more likely once the underlying legal architecture is under challenge.

Complication six: multi-night, comp and long-stay corporate treatment

Three specific fact patterns produce recurring accounting questions that neither Edinburgh Council's scheme information for accommodation providers nor the Scottish Government's guidance has cleanly resolved:

• Multi-nights above the five-night cap. Straightforward in Edinburgh (first five nights only). Not in Glasgow, where the 7% is proposed to apply for the full stay. Operators taking long stays (relocations, film crews, medical stays) will see meaningfully different outcomes across authorities on the same booking.
• Complimentary nights and hosted stays. Where an operator hosts a friend, a supplier, or a review guest without charge, HMRC's own line on "consideration" and Edinburgh Council's line on "paid overnight accommodation" do not fully align. In practice the cautious answer is nil-levy for a genuine unpaid stay; the aggressive council interpretation could bite on any stay where any form of value transfer occurs.
• Corporate long-stay contracts. Where a corporate contract prices per stay rather than per night, the "accommodation-only cost" the levy sits on has to be extracted from a bundled price. This is a real bookkeeping exercise on bookings with cleaning fees, extras, or bundled services.

The simpler model the ASSC has been pressing for

Set against every one of the complications above, one alternative would remove most of the accounting-side pain in a single stroke: a fixed per-night rate, applied uniformly, calculated on the room-night rather than on a percentage of a value that has to be extracted from the booking.

This is the model the Association of Scotland's Self-Caterers has advocated for in its published policy work on the Bill. It is also — not coincidentally — the model Highland Council has proposed for its own levy at £5 per room per night.

The case for the fixed-rate model is straightforwardly operational. A fixed rate:

• Removes the OTA commission question entirely — the levy does not depend on the "accommodation portion" of a booking value, and there is nothing to argue about with Booking.com or Airbnb over what they collect and what the operator's cut is.
• Removes the VAT threshold trap — a fixed per-night charge collected on behalf of the council is much more obviously outside the operator's turnover than a percentage of accommodation value.
• Simplifies the reconciliation — total nights × fixed rate is a calculation that survives a spreadsheet and can be checked by anyone.
• Is what every mature European tourist tax (Amsterdam, Paris, Rome, Barcelona) already does, for exactly these reasons.

Edinburgh Council chose a percentage-based scheme. Glasgow and Aberdeen appear to be following it. Highland is going the fixed-rate route. For portfolio operators across multiple Scottish authorities, the resulting patchwork of percentage-vs-fixed, capped-vs-uncapped, differing rates will be genuinely more work to administer than the underlying tax raises for either the operator or the council.

Our own position, as an accounting practice looking at the operational load these schemes actually generate: the ASSC is right on the fixed-rate case. It is the simpler, more proportionate, and better-designed model. Whether it is heard in time for the next wave of council levies is a separate question — Glasgow's percentage-based decision suggests it may not be.

What operators should do

1. If you operate in Edinburgh, reconcile every payout against your bookings for levy component from 24 July onwards. The platform payout will not identify the levy portion separately. Your quarterly return and payment obligation is unaffected by whether you extracted it cleanly.
2. Model the VAT registration threshold with the levy included in turnover. If you are within 15% of £90,000 on accommodation income, get advice before your next busy quarter — the levy could push you over.
3. Keep booking-date and payment-date evidence for every reservation. Pre- and post-1 October 2025 cutoff evidence is the only defence against an Edinburgh dispute.
4. Do not assume the Scottish position mirrors the Welsh one on VAT. They currently do not. The Welsh levy is outside the scope of VAT; the Scottish position is that the levy amount counts towards turnover.
5. If you operate in Highland, respond to the consultation. The Council decides on 10 December 2026 and the £5-per-night flat rate is materially harsher than a percentage on many small self-catering properties (ASSC — Highland Visitor Levy consultation opens).
6. Set up a separate levy liability account in your bookkeeping from day one. The levy is not your income. Treating it as revenue overstates turnover and understates the outstanding remittance liability.

The Scottish visitor levy has been introduced in a form that leaves too many accounting questions to the operator. The ASSC's characterisation — that this is "a well-intentioned policy being badly implemented" — is the sector's line, but on the accounting side specifically it is now our line too.

Book a free consultation to talk through your position.

Sources: VisitScotland — Local Authority Guidance on the Visitor Levy (statutory reference document, current version); VisitScotland — Visitor Levy FAQs for Accommodation Providers; The Scheme for the Edinburgh Visitor Levy; Edinburgh Visitor Levy — timeline for implementing the levy; CIOT — Scottish Visitor Levy, VAT position and GOV.UK guidance; ICAS — Concerns with Scottish government about VAT guidance on new Visitor Levy; ASSC — Association of Scotland's Self-Caterers briefing on the Visitor Levy Bill; ASSC — The introduction of a Visitor Levy in Scotland: a burden on small businesses and tourism; Scottish Housing News — Edinburgh Visitor Levy housing plans could face legal challenge; ASSC — Highland Visitor Levy consultation opens; Highland Council — Draft Visitor Levy Scheme special meeting; LevyTrack — Visitor Levy VAT in Scotland.