Who collects tourist tax on Airbnb, Booking.com, and Vrbo (2026)

Two summers ago a host I work with in Valencia got a letter from the Generalitat asking why no tourist tax had been remitted for the 47 stays they'd booked through Booking.com that quarter. The host had assumed Booking handled it the same way Airbnb did. Airbnb auto-collected and remitted the €0.90 per guest per night to the regional authority; Booking.com had quietly listed it as "to be paid at the property" on every reservation and left the host to file and pay it themselves. Six quarters of unfiled tax, €2,840 in back-tax, plus €1,100 in penalties. The host had been a host for four years and didn't know.

This post is the practical map. Which platform auto-collects in which jurisdiction, which leaves it on you, and what to look for in the host fee report to prove what got collected. Numbers, jurisdictions, the line items you can actually search for in your payout history.

The two ways platforms handle tourist tax

There are exactly three states a tax can be in for any given (platform, jurisdiction) pair, and only three. Getting this straight is the entire game.

State 1: platform collects and remits. The platform adds the tax to the guest's checkout, withholds it from your payout, and sends it directly to the tax authority. The host's job is zero — you file an annual return that shows the platform-collected amounts, and the authority cross-checks against the platform's filing. This is what Airbnb does in California, New York City, Paris, Lisbon, Barcelona, and most of mainland Portugal. It is the cleanest outcome.

State 2: platform collects, host remits. The platform adds the tax to the guest's checkout and pays it to you alongside the rest of the payout. You see a "tax collected" line in the payout report; you remit it to the authority on your own schedule (monthly, quarterly, or annually depending on the jurisdiction). This is Booking.com's default in most EU markets, and it is the trap. Hosts see "tax collected" and assume the platform handled the remittance. It didn't. You did.

State 3: platform does nothing. The platform leaves the tax line blank on the reservation. The guest pays the platform's nightly rate; you collect the tax from the guest in cash on arrival, or you absorb it from the nightly rate. You file and remit. This is the default for most Vrbo bookings outside the US, and for Booking.com bookings in jurisdictions where the platform hasn't signed a marketplace agreement.

The single sentence to memorise: "collected" is not "remitted". The two words look identical in the payout report and they mean radically different things in the eyes of the tax authority.

Where Airbnb auto-collects (state 1)

Airbnb has the broadest auto-collection coverage of any platform. As of 2026, Airbnb auto-collects and auto-remits in:

United States — approximately 30 states either through a state-level marketplace facilitator law or city-by-city agreements. The full list is in Airbnb's "Occupancy tax collection" help page under the "In which jurisdictions does Airbnb collect and remit occupancy taxes" section. The high-volume ones to know:

European Union and EFTA — auto-collection covers approximately 35 countries and regions:

The list is moving. New cities sign on quarterly; a few have rolled back. The single authoritative source is the Airbnb help page above; do not trust any blog post (this one included) as a substitute for checking it before filing.

Where Booking.com auto-collects (state 1) — the much shorter list

Booking.com's marketplace-facilitator coverage is dramatically smaller than Airbnb's. As of 2026:

• Italy (some cities, including Rome, Florence, Venice, Milan) — Booking auto-collects and remits the tassa di soggiorno.
• France (since 2019) — Booking auto-collects and remits the taxe de séjour in cities that have opted in.
• Netherlands (Amsterdam) — Booking auto-collects and remits toeristenbelasting.
• United Kingdom (no national tourist tax yet; Manchester and Edinburgh have local levies Booking does collect).
• Approximately 12 US cities and 4 US states — full list on Booking's partner help page, search "marketplace facilitator."

Outside that list, Booking.com's behaviour is state 2 — the platform may or may not collect, but it does not remit. The tax flows to your payout; the authority expects you to file.

The trap: in Spain, Portugal, Germany, Austria, Switzerland, and most of Eastern Europe, Booking marks every reservation with a "City tax" or "Tourist tax" line that the guest pays — but the money lands on your payout, not the city's account. The host must file and remit. Most hosts I audit are six or more quarters behind on this and don't know.

Where Vrbo auto-collects (state 1)

Vrbo's auto-collection coverage in the US roughly matches Airbnb's — both platforms have signed marketplace-facilitator agreements in the same states because the state laws apply equally to "online travel marketplaces."

In Europe, Vrbo's coverage is patchy. Vrbo auto-collects in:

• France (most cities), Italy (Rome, Florence, Venice), Spain (Catalonia, Balearics), Portugal (Lisbon, Porto).
• Approximately 6 German cities, including Berlin and Hamburg.

Outside that list, Vrbo's default is state 3 — no tax line on the reservation at all. The guest sees only the nightly rate plus Vrbo's service fee. You collect the tax on arrival or absorb it. This is the worst of the three states because there is no "tax collected" line in the payout to even surface the obligation; you have to know the local tax exists and remit it from your own pocket.

To check a specific Vrbo listing: open the dashboard, click the listing, click Property setup → Rates and fees, then look for the "Lodging tax" section. If it shows "Vrbo collects on your behalf," you are in state 1. If it shows "Add a lodging tax" with a blank field, you are in state 3 and Vrbo expects you to set the rate manually.

The remittance receipt: prove what got collected

Once a quarter, pull each platform's tax report. The line items you are looking for:

Airbnb. Under Performance → Earnings → Transaction history, filter by date range and click Download CSV. The exported file has a Withheld Tax column. Sum that column for the period. The corresponding "Tax remitted" line in the Airbnb annual tax summary tells you whether Airbnb sent it to the authority. Where the two match, you are clean. Where they diverge, the platform collected but did not remit — that money is on your payout and needs to be filed by you. Read Airbnb's tax document guide for the exact terminology, which has changed twice in 2024–2025.

Booking.com. Under Finance → Invoices and reports → Reservation statement, the line per reservation is City tax / Local taxes. The amount is split between "Guest pays" and "Booking collects for remittance." The latter is almost always zero outside the few cities listed earlier. The "Guest pays" amount went to your payout. Cross-check against the city authority's portal to confirm you remitted it on your own.

Vrbo. Under Reservation manager → Reservation history, export to CSV. Filter by Lodging tax collected and Lodging tax remitted by Vrbo. The difference is the host-remittance gap.

The reconciliation takes 15–30 minutes per platform per quarter. It is the single highest-leverage compliance task a multi-platform host can do; missing it once is the difference between a clean audit and a five-figure back-tax assessment.

For the broader operational picture once you start tracking tax line items alongside everything else, see GDPR for vacation rental hosts — the same quarterly cadence works for data-protection compliance.

What you do when the platform doesn't collect

For every (platform, jurisdiction) pair in state 2 or state 3, the host has three jobs:

1. Register with the authority. In the EU, this is the municipal tourism office or the national tax agency; in the US, it is the state Department of Revenue plus, for some cities, a separate city license. Registration is one-time and typically free; doing it after the first booking is what triggers the "back-tax + penalty" letter.

1. Set the rate on the listing. On Booking.com, this is Property → Property setup → Taxes and charges. Add a city tax line at the local rate. The guest sees it at checkout, the money flows to your payout. On Vrbo, this is Property setup → Rates and fees → Lodging tax.

1. File on the local cadence. EU cities are usually monthly or quarterly; US states are usually monthly, quarterly, or annually depending on volume. The portal accepts a CSV upload of the reservation list; total tax owed is the per-night rate × occupied nights × guest count for per-guest taxes, or the percentage × room revenue for percentage taxes. The portal calculates, you pay.

If you have only one or two listings and the jurisdiction has a per-night flat-rate tax like Portugal (€2/night), you can do the math on a napkin. If you have five or more listings, or any percentage-based tax that depends on the nightly rate, the napkin breaks and you need a per-reservation export.

The three failure modes that cost hosts money

Failure mode one: assuming Airbnb's behaviour generalises. Airbnb auto-remits in ~150 cities. Hosts who book primarily through Airbnb develop a mental model that "the platform handles tax." They then list on Booking.com or Vrbo and the model is wrong — the same property is now in state 2 on Booking.com and the host is six months behind on filing before they notice. The mitigation is the quarterly reconciliation above.

Failure mode two: tax-on-cleaning-fee oversights. Most US states tax the cleaning fee at the same rate as the nightly rate; most EU per-night tourist taxes do not. The platform-collected amount on Airbnb reflects the correct logic for the jurisdiction; the platform-collected amount on Booking is sometimes wrong because the host set the rate at "X% of nightly" without realising the cleaning fee should also be in scope. The error is small per reservation (a few dollars) and large at the annual level for a high-volume listing. Read the city's tax-base definition once; fix the Booking config.

Failure mode three: the rate change you missed. EU tourist taxes have been moving upward by 10–30% every 18–36 months as cities try to fund tourism-management programs. Lisbon went from €1 to €2 in 2019; Amsterdam went from 12.5% flat to a tiered structure in 2024; Venice introduced day-tripper fees in 2024 that affect overnight stays differently from before. Hosts who set the rate once and don't revisit it are under-collecting from the guest and remitting at the new higher rate from their own pocket. Build a calendar reminder to re-check rates in January each year.

One opinionated take

The two-word distinction "collected versus remitted" is the difference between hosts who survive their first tourist-tax audit and hosts who don't. Most platform UIs blur the two terms deliberately — "Booking collects city tax from your guests" reads as if the platform is also remitting, when in 90% of cases it is not. The remediation is a 30-minute quarterly task that costs you nothing and protects you from a five-figure liability that compounds with interest from the day the first under-filing landed. If you have been hosting for more than 12 months across multiple platforms and you have never pulled the per-platform tax report and cross-checked it against the city portal, the single highest-leverage thing you can do this week is the reconciliation. The tax-authority letter does not warn you in advance — it arrives once the gap is already four quarters deep. The platform's compliance team will not call to remind you, either; that is not the deal. For the bookkeeping side of the same problem, see when do Airbnb and Booking.com actually pay you — the cash-flow timing intersects with the tax-filing cadence in ways that catch hosts who reconcile only once a year. For the broader operational picture once you start tracking platform-collected lines alongside guest data, RentTools surfaces them next to the rest of your operations log.