The Number You Feed It Matters More: Accommodation Tax Bands, Cleaning Fees, and Why We Open-Sourced japan-stay-tax
Table of Contents
Most of the work of calculating Japanese accommodation tax (宿泊税) happens before you do any arithmetic. You need to know which local jurisdiction’s rules apply and which nightly rate falls into which band. After that, the sum is easy. If you use the wrong taxable accommodation charge, the stay can land in the wrong band, and careful multiplication won’t fix that.
This is a product spotlight, so I’ll say it up front: we built and open-sourced a library called japan-stay-tax that does the calculation part. I’ll spend most of this post on the problem, because the thinking applies whether you use our code, a spreadsheet, or a notebook by the front door.
TL;DR
- Japan has no national accommodation tax. Prefectures and municipalities levy it, each with its own structure, and both levels can apply to the same stay. Most fixed-amount systems charge per person, per night.
- The structures differ. Some use price bands with a tax-free floor. Some have no minimum-price exemption and use brackets that rise at higher rates. Some charge a percentage.
- Whether the guest has already paid the accommodation tax depends on the platform, your listing settings and the payment arrangement. Check reservation breakdowns and tax payouts before you collect anything yourself.
- If you use the wrong taxable accommodation charge, for example by leaving out a cleaning fee that the jurisdiction counts, a stay can end up in the wrong band.
- japan-stay-tax is an open-source library that calculates the tax across jurisdictions with flat, banded and percentage structures. It doesn’t decide your taxable base for you, and it doesn’t file anything.
Why Is Japanese Accommodation Tax So Easy to Get Wrong?
It’s easy to get wrong because each prefecture or municipality writes its own rules, and the rules don’t share a shape.
-
Tokyo Metropolis uses price bands. As of 2026-11-07, it taxes stays at licensed hotels and ryokan:
- below ¥10,000 per person per night: exempt
- ¥10,000 to under ¥15,000: ¥100
- ¥15,000 or more: ¥200
Simple lodgings and minpaku come into scope on 2027-04-01. On that date the system changes to 3%, with an exemption below ¥13,000 (Tokyo Metropolitan Government: 宿泊税に係る総務大臣の同意及び施行日について).
-
Kyoto City has no minimum-price exemption. Qualifying school trips and specified preschool/nursery events are exempt, including eligible accompanying staff. Its brackets rise for higher rates (Kyoto City FAQ for accommodation operators).
-
Osaka Prefecture uses bands with a tax-free floor (Osaka Prefecture: 宿泊税のごあんない).
-
Kutchan charges a percentage instead of bands. From 2026-04-01 its combined town and prefectural tax is 3%, collected through the town. The accommodation charge can be expressed per person, per room or per building, depending on how the facility prices its stays (Kutchan Town: 倶知安町の宿泊税について).
-
Fukuoka City shows how levies can overlap. Its ¥200 and ¥500 totals are ¥50 of prefectural tax plus ¥150 or ¥450 of city tax (Fukuoka Prefecture: 宿泊税の概要について).
One location is easier to manage, but you still need to check which rules apply and when they take effect. The trouble starts when you run properties in two or three jurisdictions, or when a new municipality adopts the tax. That happens almost every year. Each jurisdiction’s rule is fine on its own. Mixing them up is where it goes wrong.
The other trap is quieter. Whether the guest has already paid the tax depends on the platform, your listing settings and the payment arrangement. Payments taken through a reservation site can include accommodation tax. Eligible Airbnb custom taxes are collected from guests and paid to the host separately, so the host can remit them. Check the reservation breakdowns and tax payouts before you collect anything from the guest. If you skip that check, you can charge a guest twice. Or you can under-collect, and the shortfall comes out of your margin when you remit.
Which Nightly Rate Decides the Band?
You decide the band by applying your jurisdiction’s definition of the taxable charge, so the first job is to find out exactly what that definition includes. The classic error is the cleaning fee. A booking shows a nightly rate and a separate cleaning fee. Add the fee to the rate and the stay can jump into a higher band. Leave it out and the stay might sit below the threshold. If you use the wrong taxable accommodation charge, the stay can end up in the wrong band.
For the jurisdictions in this post, the answer is concrete. Kyoto City includes cleaning charges, and Osaka Prefecture explicitly includes mandatory cleaning charges. Listing the fee separately doesn’t exclude it. Meals and consumption tax are excluded.
Here’s a worked Osaka example. Two guests stay one night. The room charge is ¥9,000 and the mandatory cleaning fee is ¥2,000, both excluding consumption tax. That’s ¥11,000 in total, or ¥5,500 per person. Under Osaka’s band for charges from ¥5,000 to under ¥15,000 per person per night, each guest’s share attracts ¥200, so the tax is ¥400 in total.
Here’s how I’d approach it, with or without any software:
- Write down each jurisdiction’s definition in plain words. For every prefecture or municipality you operate in, note what counts toward the rate used for banding. Get it from the jurisdiction’s own guidance, not a blog post (including this one).
- Follow the jurisdiction’s allocation rules to work out the taxable charge for each person and night. Most fixed-amount systems set the band per person, per night, so you have to split a room-priced booking across the guests before you classify it.
- Kyoto City’s own example splits a ¥20,000 room shared by two guests into ¥10,000 each. Under the current bands, that’s ¥400 per guest per night.
- Discounts follow rules too. Osaka Prefecture treats a discount tied to one night differently from a discount on the whole stay. You can’t simply decide to average the booking total.
- In a percentage system the unit can differ. If a Kutchan-style tax is calculated on a room charge, don’t automatically multiply the result by the number of guests.
- Keep the rate you classified on next to the tax you calculated. When something looks off at remittance time, you want to see which number put the stay in which band.
- Recheck when a jurisdiction changes its rules. New jurisdictions adopt the tax and existing structures get revised. Tokyo’s switch on 2027-04-01 is one example. A table you copied two years ago is a liability.
None of that needs code. A careful spreadsheet with one tab per jurisdiction will get a small operator a long way.
What Did We Build, and How Does It Work?
We built japan-stay-tax, an open-source library that calculates Japanese accommodation tax across jurisdictions with flat, banded and percentage structures. You give it the jurisdiction and the stay details, and it applies that jurisdiction’s structure. You don’t need separate branching logic for Tokyo-style bands, Kyoto-style brackets and percentage-based jurisdictions.
We wrote it for the reason above. Once we had properties under more than one jurisdiction’s rules, our own calculation logic became a pile of special cases. Pulling it into one library put each jurisdiction’s structure in one place, where it could be read and fixed. We open-sourced it because the problem isn’t unique to us. Everyone running stays in Japan works from the same public rules, and a shared, inspectable implementation seemed more useful than everyone keeping their own private copy.
The code is here: github.com/benstaydev/japan-stay-tax
Where Does It Fit, and Where Doesn’t It?
It fits as the calculation step inside a process you already understand. Maybe you run stays across several jurisdictions, or you’re building booking or accounting software that has to handle more than one structure. Either way, a library that already models flat, banded and percentage taxes saves you from writing and maintaining that branching yourself.
It does not decide your taxable base. You have to answer the cleaning-fee and allocation questions from earlier for each jurisdiction yourself. The library calculates from the numbers you give it, so the wrong rate still gives you the wrong band. It doesn’t collect tax from guests or remit it to anyone. And it isn’t an authority. Prefectures and municipalities change their rules, so check the results against official guidance, especially for a jurisdiction that has just adopted or revised its tax.
If you have one property in one location and a spreadsheet you trust, you may not need it at all. That’s a perfectly good answer.
FAQ
Q: Is accommodation tax included in my Airbnb or Booking.com payout?
It depends on the platform, your listing settings and the payment arrangement. Payments taken through a reservation site can include accommodation tax. Eligible Airbnb custom taxes are collected from guests and paid to the host separately, so the host can remit them. Check the reservation breakdown and any tax payouts before you collect an unpaid balance from the guest. Remitting the tax to the prefecture or municipality is generally still the operator’s job.
Q: Should the cleaning fee count toward the rate used for the tax band?
It depends on how the jurisdiction defines the taxable charge, so confirm it with official guidance. Kyoto City includes cleaning charges, and Osaka Prefecture explicitly includes mandatory cleaning charges. Listing the fee separately doesn’t exclude it. Meals and consumption tax are excluded. If you use the wrong taxable charge, a stay can end up in the wrong band.
Q: Does japan-stay-tax file or remit the tax for me?
No. It’s an open-source calculation library. Collecting, recording and remitting the tax are still your job.
This post is for informational purposes only and does not constitute legal or tax advice. Please consult a qualified professional for your specific situation.
Comments