Hotels, bed and breakfasts, guesthouses and serviced apartments are all first-class accommodation types in our product — the calculation engine treats a hotel booking through exactly the same steps as a short-term let booking, but two things come up disproportionately often for this category: VAT registration and bundled breakfast.
The same engine, the same steps
There's no separate "hotel calculation" — every booking, regardless of property type, runs through the same sequence: exemption status, jurisdiction match, scheme version resolution, currency check, booking cutoff, the night cap, eligible amount, any bundled breakfast deduction, then the levy math itself. See How to calculate the Edinburgh Visitor Levy for the full walkthrough. What differs for hotels in practice is which of those steps tend to actually matter.
VAT registration is more often relevant
Hotels and larger B&Bs are more likely to be VAT-registered than an individual host letting a single spare room, which makes the pre-VAT accommodation base (see the VAT guide) a live, everyday concern rather than an edge case. Return Readiness's vat_configuration check specifically confirms every VAT-registered property in scope has a default VAT rate set — worth confirming this is configured correctly on every property in a hotel or B&B portfolio, not just checked once at setup.
Bundled breakfast is common here
A meaningful share of hotel and B&B rates include breakfast, and the levy engine's bundled breakfast deduction exists largely for this category of provider — see Bundled breakfast and the Visitor Levy for the full mechanic and worked example. If your rate includes breakfast and you haven't configured a per-guest-per-night breakfast value on the property, your eligible accommodation amount is currently overstated by whatever portion of your rate actually represents the meal.
Multi-room, multi-property operations
A hotel with many rooms is, from the product's perspective, a property that can have many concurrent reservations, each calculated independently. There's nothing that requires rooms to be tracked as separate "properties" for the levy calculation itself to work correctly — what matters is that each reservation carries the right accommodation amount, dates, guest count and currency, however your rooms are organised in the system. For an operation with genuinely separate legal entities or client relationships (a management company running several hotels, say), our managed-client structure keeps each client's properties and returns fully separated, with a dedicated reporting period per property or client.
Data quality checks worth watching for hotel volumes
At hotel booking volumes, a few of the data quality checks earn their keep more than they might for a single host: suspicious_nightly_rate (a rate outside a plausible range, which can catch a data-entry slip on a busy night), overlapping_duplicate (the same property double-booked in the source data), and unexplained_rate_change (a nightly rate that deviates sharply from the property's recent trailing average). See Mistakes and corrections for the full catalogue of checks the engine runs.
Before you file a hotel's quarter
Run through the quarterly return checklist as normal, but pay particular attention to the VAT configuration and bundled breakfast setup on every property before treating a period's totals as final — these are the two settings most likely to be wrong-by-omission for a hotel or B&B, rather than wrong by a data-entry mistake.