Every time I’ve talked to another operator or a developer building something for Japanese hospitality, the same complaint comes up: accommodation tax math. Not the concept — everyone understands “some cities tax overnight stays.” The trouble is that local governments calculate it differently. When building our tool, we did not find an official national dataset covering the rules our software needed, so we checked each jurisdiction’s guidance. Official nationwide summaries do exist (for example, 宿泊税をめぐる税制上の諸論点), but for our purposes they didn’t replace each local government’s own ordinance and guidance.

TL;DR

  • Japan has no national accommodation tax. Local governments levy it one by one, including prefectures, cities and towns, and each sets its own structure.
  • Tokyo uses price bands with a tax-free floor today, but is scheduled to switch to a 3% rate for higher-priced stays from April 1, 2027. Kyoto also uses fixed amounts by price band, but unlike Tokyo and Osaka, it has no price-based exemption threshold for paid, non-exempt stays. Kutchan Town charges 3% from April 1, 2026, and Niseko Town is scheduled to adopt percentage taxation from November 1, 2026.
  • A common mistake we see is using the wrong taxable accommodation charge: treating mandatory cleaning or service charges as excluded when major regimes like Tokyo, Kyoto and Osaka include them in the tax base.
  • Don’t assume OTA payouts include accommodation tax. Coverage varies by platform, facility and municipality, so operators need to confirm it and file separately.
  • We open-sourced the calculation logic as japan-stay-tax on GitHub so anyone building booking or pricing tools doesn’t have to rebuild it from scratch.

Why Does Japan’s Accommodation Tax Vary by City?

Because no national law sets one rate or structure. Accommodation tax (宿泊税) in Japan is a local option tax, adopted city by city or prefecture by prefecture, and each one designs its own rules. Tokyo was an early adopter and uses price bands: stays below a nightly-rate threshold pay nothing, and above it the tax steps up in flat amounts per band. As of September 19, 2026, Tokyo taxes ¥10,000 to under ¥15,000 at ¥100 and ¥15,000 and up at ¥200 per person per night. From April 1, 2027 it is scheduled to change to a flat 3% for stays of ¥13,000 or more per person per night, and to widen the taxable scope beyond hotels and ryokan to include simple lodgings and minpaku (宿泊税の見直し).

Kyoto also uses fixed amounts by price band, but unlike Tokyo and Osaka, it has no price-based exemption threshold for paid, non-exempt stays. As of March 1, 2026, the per-person, per-night amounts are:

  • under ¥6,000: ¥200
  • ¥6,000 to under ¥20,000: ¥400
  • ¥20,000 to under ¥50,000: ¥1,000
  • ¥50,000 to under ¥100,000: ¥4,000
  • ¥100,000 and up: ¥10,000

(京都市:宿泊税について)

Osaka also bands its rates, but starts from a tax-free floor (大阪府の宿泊税). Some local governments drop fixed amounts altogether: Kutchan Town charges 3% from April 1, 2026 (倶知安町の宿泊税について), and Niseko Town is scheduled to adopt percentage taxation from November 1, 2026 (宿泊税を定率制に変更します).

More local governments have been introducing, revising or considering accommodation tax, so rule sets need periodic review. If you’re managing bookings across even two or three cities, you’re not applying one formula. You’re applying three or four, each with its own thresholds and its own edge cases.

What Calculation Mistake Do We Often See?

A common mistake we see is using the wrong taxable accommodation charge. In major regimes such as Tokyo, Kyoto and Osaka, mandatory cleaning or service charges count as part of the taxable accommodation charge. Meals, consumption tax, local consumption tax, bathing tax and separately charged non-accommodation services do not (宿泊税改正に関するよくあるご質問, 大阪府の宿泊税). Banded systems key off that taxable charge, so treating an included cleaning fee as excluded (or the reverse) can push a stay into the wrong band. Get that wrong and you either under-collect, and the shortfall comes out of your margin at remittance time, or over-collect, and now you owe a guest a correction.

Another common issue is simpler but just as costly: don’t assume accommodation tax is folded into what OTAs pay out. Some booking-site or travel-agency payments may include it, but that isn’t guaranteed and it varies by platform and municipality. The operator has to:

  • confirm how the platform handles it
  • work out the correct amount if needed
  • collect it, often at check-in, in cash or as a separate line item
  • file it with the local government on that government’s schedule

Miss that step and you’re not looking at a rounding error. You’re looking at a compliance gap with a real municipal filing deadline behind it.

How Do Flat, Banded, and Percentage Structures Actually Differ?

They differ in what triggers the tax and how the amount scales with price.

  • Flat: the same yen amount per person per night, sometimes with a price threshold or personal exemptions. Atami, for example, charges ¥200 per person per night with no price threshold, subject to personal exemptions (宿泊税の概要).
  • Banded: used by Osaka, Kyoto and (until its scheduled change) Tokyo. Accommodation charges are divided into tiers, and each tier has its own fixed charge. In Osaka, taxable accommodation charges of ¥15,000 and ¥30,000 per person per night attract ¥400 and ¥500 respectively. Kyoto also uses fixed amounts by price band, but unlike Tokyo and Osaka, it has no price-based exemption threshold for paid, non-exempt stays.
  • Percentage: no fixed amounts at all, just a set percent of the accommodation charge, so the tax rises continuously instead of jumping between bands.

None of these are interchangeable. Hardcoding one city’s logic and assuming it will work for the next city is exactly how operators and developers end up with quiet, compounding errors.

What We Built

We ran into this repeatedly while managing our own properties, so we extracted the logic into a standalone, open-source library: japan-stay-tax. It calculates Japanese accommodation tax for cities that use flat, banded or percentage structures. Instead of every operator or developer writing their own city-by-city lookup table and getting the band boundaries wrong in slightly different ways, that logic lives in one place.

To be honest about where this fits: it’s a calculation library, not a full compliance system. It’s most useful if you build or maintain your own booking, pricing or accounting tools and need accurate per-city tax figures, rather than a full-service filing product. If you just want an estimate for one property and don’t touch code, this probably isn’t the right tool for you. The logic is public, though, so you can at least see exactly how a given city’s calculation works. Because it’s open source, anyone can inspect it, use it, or contribute a city we haven’t covered yet.

FAQ

Q: Does OTA payout include accommodation tax?

Not necessarily. Some booking-site or travel-agency payments may include accommodation tax, but this varies by platform and municipality. Operators should confirm directly rather than assume either way.

Q: Why do flat and banded structures give different tax amounts for similar room rates?

A banded structure divides accommodation charges into tiers with a fixed charge per tier. A rate near a band boundary can land in a different tier, and pay a different flat amount, than a very similar rate just on the other side of that line.

Q: Is japan-stay-tax a filing or remittance tool?

No. It’s an open-source calculation library for working out the correct tax amount across cities with different structures. It doesn’t handle collection, filing or remittance to municipalities.

Sources


This post is for informational purposes only and does not constitute legal or tax advice. Please consult a qualified professional for your specific situation.