Tourist Levies Inside the Fee Base: Two Deductions on One Price

A levy assessed on the same figure a platform percentage is taken from leaves two deductions on one price. Most hosts model only one.

Last updated: October 8, 2026

When a tourist levy and a platform percentage both read from the same advertised price, that single number carries two reductions, not one. Many hosts price for the platform cut and forget the second charge sits on the same base. This guide sets out the two deductions, the order they land in, and what to keep in your own records. It's general guidance, not tax advice.

Key Takeaways

• Two reductions can share one base. A levy and a platform percentage can both be calculated from the same advertised figure.
• The base matters more than the order. What changes your number is whether each charge reads the gross price or a figure after another deduction.
• The detail is local. Rates, thresholds and deadlines are set per place, so follow your own authority's current guidance.
• Keep your own record of each deduction. A short table of what came in and what went out beats a memory every time, so build it early.
• Your calendar shows the source figures. LOCALSBNB displays each connected channel's own rate and status, so you can see the number each charge reads from.

Two deductions, one price

Start with the price a guest sees. Call it the advertised price. On that one figure, two charges can apply: a tourist levy set by a local authority, and a platform percentage set by the platform's current terms.

If both read from the same advertised price, they don't cancel each other and they don't merge into one bigger percentage. They're two separate deductions on the same base. That's the part hosts miss. The mental model of "the platform takes its cut, and what's left is mine" quietly skips the levy.

The levy also isn't a cost you can leave for later. Depending on where you are, it may be collected from the guest, remitted by you, or handled by the platform. Which of those applies is a local question, and the answer changes what lands in your account at the end of a stay.

So model both. Picture the advertised price, then subtract the levy as your local rules describe it, then subtract the platform percentage as the platform's current terms describe it. Two steps, one starting number. Getting the starting number wrong is what turns a good-looking booking into a thinner payout.

Working out the order they land in

The order feels like the tricky part, and it usually isn't. What matters is the base each charge reads from, not the sequence alone.

Some charges read the gross price, the full advertised figure, before anything else comes off. Others read a figure after a previous deduction. If your levy reads gross and your platform percentage also reads gross, both land on the same number and neither shrinks the other. If one reads a reduced figure, the order starts to matter.

The way to find out is to read each rule's own definition of the base. A levy rule will say what it's assessed on, and a platform's terms will say the same for its percentage. Don't assume they match. Two charges on one price often read from two different bases, and that's where the arithmetic hides.

Once you know the bases, work the numbers in a fixed order and write the result as a short chain: advertised price, minus levy, minus platform percentage, equals what you keep. Keep it to one line. A one-line chain you can repeat is worth more than a long spreadsheet you open twice a year.

Refine the chain when something changes. When a local rate moves or a platform updates its terms, only one link in the chain changes, and you can see it at a glance. That's the reason to write it down in the first place.

One more habit helps. Rebuild the chain at the start of each season rather than trusting last year's version. A base that was correct then may not be now, and the whole point of a chain is that you can spot which link moved.

Where the numbers differ by locality

Here's the part no general guide can settle: the numbers themselves are local. Rates, thresholds, exemptions and deadlines are set per place, and they change. What one city charges, another may not, and the base each one reads can differ too.

That's why this guide gives you the method, not a figure. A rate quoted in one market means little in another, and a deadline that applies down the road may not apply to you. Treat any specific number you read as a starting point, then confirm it against your own authority's current guidance.

The same applies to how a levy is paid. In some places it's collected with the booking and remitted by the host. In others the platform handles it, or the guest pays it directly at the property. Your local rules decide which, and the answer changes what you need to track.

So build the habit of checking locally, once, and then keeping the detail current. Start from your own authority's published guidance, note what it says about the base and the rate, and refresh it when the season changes. A local answer you've confirmed beats a number you remember from somewhere else.

One more caution. Two nearby places can look similar and still differ on the base, the exemption or the collection method. Don't carry one city's pattern into another just because they sit close on a map.

What to keep in your own records

Records are what let you answer a question months later without guessing. For a levy and a platform percentage, four things are worth keeping.

Keep the advertised price for each booking. Keep the levy you applied, and the rule you applied it under. Keep the platform percentage that was taken, as shown on the platform's own statement. Keep what actually landed in your account.

Those four lines tell the whole story of a single booking. If a figure is ever questioned, you can walk from the guest's price to your payout in four steps, and each step has a source.

Hold the sources too. Save the version of your authority's guidance you relied on, with the date. Save the platform's terms as they stood when the booking was made. These change, and the version from the right date is the one that matters.

Then keep the record simple enough to maintain. A row per booking in one table, with those four figures, is enough. If you manage more than one property, split by property, because each one's local rules can differ.

On the record-keeping side, one view helps. LOCALSBNB shows each connected channel's own rate and status in the calendar, so the source figure behind each charge sits in one place rather than across four tabs. The authority still sets the rate, and you still keep the notes, but the starting number is easier to check when the calendar lays it out for you at localsbnb.com.

FAQ

Why do I see two deductions on one price?

Because a tourist levy and a platform percentage can both be calculated from the same advertised figure. They're separate charges on one base, so neither offsets the other.

Does the order they're deducted change what I keep?

It can, when one charge reads a figure after another deduction has already come off. Check the base each rule names, then apply them in a fixed order you can repeat.

Are the rates the same everywhere?

No. Rates, thresholds and deadlines are set per place and change over time. Confirm the detail against your own authority's current guidance, not a figure from another market.

What records should I keep?

The advertised price, the levy you applied with the rule behind it, the platform percentage from the platform's statement, and your actual payout, one row per booking.

A levy and a platform percentage on the same price come down to one habit: know the base, apply both charges in an order you can repeat, and write the result down. The numbers are local, so check them locally. When the base is clear and the record is one line per booking, the tax question gets smaller. Start with the calendar at localsbnb.com.

---

This is general guidance for hosts, not legal, tax or insurance advice. Local rules and platform terms change, so check the current requirements of your local authority and the terms each platform applies today.