Visitor Levy Calculator

About Visitor Levy Calculator

We build calculation and return-preparation tools for accommodation providers affected by Scotland's Visitor Levy — nothing more, nothing less.

We are an independent product, not a council or government service

Visitor Levy Calculator is not operated by, affiliated with, or endorsed by the Scottish Government, any local authority, or the City of Edinburgh Council. We are a private commercial product built to help accommodation providers work out what they owe under the Visitor Levy (Scotland) Act 2024 and prepare accurate figures for their own returns. We do not collect the levy, we do not set rates or rules, and we do not submit anything to a council on your behalf — see how a calculation works and our security & privacy architecture for the full detail on what this product does and does not do.

Why this exists

The Visitor Levy is a new liability for thousands of Scottish accommodation providers — short-term let hosts, hotels, B&Bs, guesthouses, hostels, and the letting agents who manage properties on their behalf. It comes with real detail that a spreadsheet formula gets wrong easily: per-council rates, night caps, VAT treatment, booking-date cutoffs, and pro-rating rules that differ from council to council as more schemes go live.

We built a single calculation engine that every part of this product uses — the free calculator, manual booking entry, and bulk imports — so a figure never drifts depending on which part of the product produced it. Every result comes with a plain-English explanation of how it was reached, not just a total.

Who operates this

Visitor Levy Calculator is operated by Omni Digital Solutions Ltd, a UK company. Full registration details are in our Privacy policy.

What we build on

Verified scheme data only

We only mark a council's scheme “live” once it has been independently verified against official guidance. We never guess a rate, cap or start date.

Guest privacy by design

There is no guest name, email, phone number or address field anywhere in our data model — it isn't filtered out, there is structurally nowhere for it to go.