Osaka's Lodging Tax and Who Actually Collects It

Three bands, one nightly threshold, and a collection duty that sits with whoever takes the money. The mechanics matter more than the amount.

Last updated: October 21, 2026

Osaka's lodging tax now reaches private lodging. From 1 July 2026, a stay priced at 10,000 yen or more per person per night carries the tax in one of three bands, at 100, 200 or 300 yen, as announced by the prefecture. The sums are small enough to ignore and the mechanics aren't. The band is set by the nightly rate, and the duty to collect sits with whoever takes the money.

Key Takeaways

• The threshold is per person, per night. Not per room, not per booking, and not against the total the guest pays.
• Three bands, one trigger. Below the first threshold nothing applies. Above it, the band steps up with the rate.
• Whoever takes the money collects. That's the platform, an agency, or you. It follows the payment, not the listing.
• It's a pass-through, not revenue. It arrives in your gross and leaves your account, and the two numbers have to match.
• A month settles it. Count guest-nights by band, once a month, and the return stops being a reconstruction.

How the bands are triggered

The test is made against the nightly rate for each guest. A room let at a rate that works out to 10,000 yen or more per person per night crosses the first threshold, as announced by the prefecture, and the band rises from there as the rate rises.

Two details do most of the damage here. The first is that the threshold is nightly, so a stay's total is irrelevant. Seven nights at 9,000 yen is under the threshold on every night, even though the bill is well past 10,000. One night at 12,000 yen is over it, even though the bill is smaller.

The second is that the comparison is per person. A room sold to four guests at 40,000 yen a night sounds like it clears the threshold comfortably. Whether it does depends on how that rate is attributed across the guests, and that's a question for the municipality rather than for a rule of thumb. Don't assume the room rate is simply divided by the headcount, and don't assume it isn't. Ask, once, and write the answer down.

Above the first threshold the bands step up as the rate rises. The published figures are the three amounts; the exact upper boundaries of each band are a detail to confirm with the municipality, along with the current text. Get that in writing before you build a spreadsheet around it.

Who collects, and when it's remitted

The duty follows the money. If a guest pays you directly, you're the one collecting. If a channel takes the payment and passes you a net figure, the channel is the one that took the money, and whether that makes it the collector is set out in its terms and in the local guidance.

That distinction is worth settling per channel rather than per booking. Most hosts sell through more than one, and the answer isn't always the same across them. A channel that collects the tax, shows it as a separate line and remits it leaves you with a record to keep and nothing to pay. A channel that pays you a gross figure and says nothing about the tax leaves the duty where it started.

Then there's the timing. The tax you collect in a month isn't yours between collection and remittance, and the remittance schedule is set locally rather than by your own accounting cycle. Confirm the dates with the municipality, and put them in the same calendar you use for everything else.

One practical rule survives all of this. Record, per booking, who took the payment and whether the tax was included. Without that line, a month later you're reconstructing a distinction you can't see in the payout report.

An agency adds a third case. If a management company takes the booking and the money, the duty moves with the payment again, and what reaches you is a settlement figure. Read the agreement for the sentence that names who collects, because that sentence decides who files.

What a platform does and doesn't do

A platform can present the tax in a few ways. It might appear as a separate line at checkout, it might be folded into a total the guest sees, or it might not appear at all. Presentation is a product decision. It doesn't move the duty.

So the question to ask a channel isn't "do you show the tax" but "do you collect it and remit it, or do you pay me the money and leave it with me". Those are different answers, and only the second one leaves you with a filing.

localsbnb.com keeps the four connected channels — Airbnb, Booking.com, Agoda and Trip.com — in one calendar. When a month closes and you need every night in one place, that's the view the count starts from: one calendar, four channels, the dates where the guests actually were.

What it doesn't do is decide the band or collect the tax. That stays with the rate you set, the channel's terms and the municipality's guidance.

Reconciling a month of nights

Month-end is where the arithmetic either works or doesn't. It's a short calculation: guest-nights, sorted by band, multiplied by the amount for that band.

Take a three-night stay for two guests at 12,000 yen per person per night. That's six guest-nights. If the rate sits in the lowest band, it's six times the lowest amount. If it sits higher, it's six times that one. What it's never is three nights times an amount, because the guest count is part of the unit.

The two errors that show up most often are the mirror image of the two details above. Counting rooms instead of guests halves the figure on a double occupancy booking. Counting the stay total instead of the nightly rate pulls long, cheap stays into a band they never reached.

There's a third error that's quieter. A booking that spans a rate change, or a stay where the rate was adjusted mid-way, has guest-nights in more than one band. Split it by night rather than averaging it, and note the split.

None of this is hard. It's just monthly, and it's easy to defer until the deferral becomes the work. The hosts who find it simple are the ones who count while the month is still warm.

Keep the working file even when the answer is zero. A month with no taxable nights is a month you may be asked about later, and a nil record holds up better than a gap.

FAQ

Is the tax charged on the whole bill or just the room?

The trigger is the nightly rate per person, as announced by the prefecture, so the bill as a whole isn't the measure. What else sits inside the rate you publish, and whether it's part of the comparison, is a question for the municipality. Confirm the current treatment before you build it into a price.

If the platform collects it, do I still have to file anything?

You may still have to keep records, even where the channel collects and remits. Ask the channel what it remits and what it reports to you, and ask the municipality what it expects from you in that case. Don't assume collection by someone else removes every obligation.

What happens with a stay that crosses a rate change?

Treat it night by night. The guest-nights before the change sit in one band and the ones after sit in another, and averaging them produces a number that matches neither. Note the split in your own record so the figure is defensible later.

The amount per night is small enough that nobody builds a business around it. The count is small enough that it's tempting to skip. Both of those are reasons to put the count on a fixed day each month, in the same sitting where the payouts get reconciled. localsbnb.com is where those nights already sit in one calendar, which is a shorter walk than four payout reports.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Lodging tax thresholds, band amounts, collection duties and remittance dates differ by municipality and are revised over time. Confirm the current rules with the municipality and the current terms of each platform you use before you price a night or file a return.