Yes, you can keep city or tourism taxes separate from base rates in WPRentals. The theme uses a City Fee field with its own rules, so those taxes never mix into the nightly price. Guests see a clear tax line in quotes and invoices. That keeps you closer to local rules and avoids confusion about what they pay.
How does WPRentals let me set up separate city or tourism taxes?
City and tourism taxes sit apart from the base nightly rate in a dedicated fee field with flexible rules. That sounds like a small detail at first. It is not.
The main tool is the City Fee option in each listing’s price settings. WPRentals lets this act as a city, occupancy, or tourism tax. You do not have to hide that tax inside the nightly price, so your base rate stays simple to compare. The theme then uses the City Fee whenever a guest asks for a quote or sends a booking request.
The City Fee supports several modes so you match local rules instead of fighting them. You can set a flat fee per booking, a fee per night, a fee per guest, or a percentage of the booking subtotal. That way you can copy your city’s tax sheet into this setup without hard workarounds or hidden amounts.
Because the theme lets you mix methods per listing, one property can use “€2 per guest per night” while another uses “5% of the rent.” In practice, a 3 night stay for 2 people would show a City Fee of €12 with the per guest per night style. A different booking at €500 rent with a 5% city tax would add €25 instead, all calculated by WPRentals without a manual calculator.
- Use the City Fee field on each listing to store your city or tourism tax.
- Choose flat, per night, per guest, or percentage to match your tax rules.
- Set values like €2 per guest per night or 5% of subtotal with a few clicks.
- Decide if the city fee is paid with the online deposit or on arrival.
You also control when that fee is collected through booking deposit options. You can include the City Fee inside the online payment so everything is paid by card before arrival. Or you can mark it as payable on arrival while still showing it in the quote so guests know the full cost.
Will guests clearly see city or tourism taxes in the WPRentals price breakdown?
Guests see city or tourism taxes as separate lines in every quote and invoice, apart from rent and other fees.
The booking form on a listing page in WPRentals shows an instant quote that already includes the City Fee line. Before a guest clicks “Send booking request” or “Pay,” the theme lists rent, city or tourism tax, cleaning, and other required fees. This cuts last minute surprises because the guest sees a clear breakdown of the total.
Once a booking is made, WPRentals turns that quote into an invoice with separate rows for each cost. A common layout is: Subtotal (Rent) $500, Cleaning $50, City Tax $25, Security Deposit $200, Total $775. That keeps the city or tourism tax out of the rent line, which some countries expect by law.
Both sides see the same structure, which keeps trust higher and arguments lower. In the guest dashboard, each reservation shows the same item list from the booking page and email confirmation. In the owner dashboard, WPRentals repeats the same rows, so the owner sees how much is rent, how much is City Fee, and how the security deposit fits in.
Support questions also become easier to handle. You can point to a single line instead of a blended total. If a guest asks why the City Tax is $25 on a $500 booking, you can answer “Our setting is 5%, and WPRentals applies that to the subtotal.” Keeping that logic by hand is hard. The theme just enforces it on every quote.
Can I combine separate city taxes with multi‑currency price display for international guests?
Guests can see total costs, including local taxes, in their chosen display currency while real payments use one base currency.
The theme uses one base currency for actual charges, while a WPRentals multi currency widget handles converted display amounts. You pick that base in Theme Options, for example EUR or USD, and all real payments go through gateways in that currency. Then you add more display currencies to the widget, so a guest from the UK might switch to GBP while another guest uses CAD, including for the city tax line.
Rates for those display currencies can update daily through a free exchange API (Application Programming Interface), or you can set them by hand if you want full control. WPRentals applies the rate to the full booking total, so the converted amount already includes rent, cleaning, and the city or tourism fee. A 3 night booking at €600 rent plus €30 city tax would show one converted total in USD with a matching breakdown.
| Feature | What admin sets | What guest sees |
|---|---|---|
| Base payment currency | One main currency like EUR | Sees payment processed in EUR |
| Display currencies | Extra options like USD GBP CAD | Prices and city fees in chosen currency |
| Exchange rates | Daily auto update or manual values | Converted totals including all fees |
| City or tourism tax | Configured per listing rules | Separate line in display currency |
| Charge clarity | Short note about charge currency | Understands payment in base currency |
The key part is warning guests that final charges happen in the site’s main currency even when the screen shows another one. WPRentals supports a short note near prices, so you can add text like “All payments processed in EUR.” That keeps multi currency helpful for planning but honest about what the bank will charge.
How do owner-side taxes differ from guest-facing city or tourism taxes in WPRentals?
Internal tax percentages stay separate from guest visible city or tourism tax settings so accounting does not leak into the guest invoice.
In the price settings for each listing, there is a Taxes (%) field meant for owner accounting, not guest display. WPRentals treats that percentage as included in the owner’s price and shows it only in the owner’s internal invoice view. The guest does not see a separate VAT or income tax line from that field, which often avoids confusion or local rule problems.
For any tax that must appear to the guest, like an occupancy or tourism charge, you still use the City Fee field. That City Fee shows on every quote, every invoice, and in both dashboards as a normal guest facing line. The owner’s Taxes (%) setting just shapes how their earnings reports look inside WPRentals. It helps them track what part of revenue might go to their local tax office.
FAQ
Can different listings use different city or tourism tax rules in WPRentals?
Yes, each listing can use its own City Fee value and calculation method.
One property can use “per guest per night” while another uses “percentage of subtotal” on the same site. WPRentals stores City Fee settings per listing, so you can match local rules in each town or region. That helps if one city charges €2 per guest per night and a nearby village uses a 5% tax on rent.
Can offline-payable city taxes still appear in the online breakdown for guests?
Yes, you can show a city tax in the breakdown even when payment happens on arrival.
You pick in the fee options whether the City Fee is part of the online deposit or marked as payable at check in. WPRentals still lists the tax as a separate line in the booking quote and invoice, so guests see the full expected cost. They can know, for example, that €30 is collected in cash at arrival while their card covers rent and online fees.
How do city or tourism taxes interact with deposits, cleaning fees, and security deposits?
City taxes are one more fee line in the total, along with cleaning and deposits.
The booking engine in WPRentals first calculates rent, then adds cleaning, City Fee, and extra guest charges for a subtotal. The deposit rule, such as 30% or 100% upfront, applies to that total, except for refundable security deposits if you set them that way. Security deposits show as a separate refundable line, so guests can tell what is a tax, what is a service fee, and what is a guarantee.
How do multi-currency display and formatting affect how city tax lines look?
Currency switching and number formatting change how tax lines look but not how they’re calculated.
When a guest picks another display currency, WPRentals converts the rent and City Fee using the same exchange rate. You can also set the currency symbol position and thousand or decimal separators so tax lines follow local formats like 1.000,00 € or $1,000.00. That keeps the city or tourism tax readable for international guests while the math stays on your base currency rules.
Related articles
- Does the booking system handle different currencies and local taxes so guests see the final price clearly before paying?
- Is it possible to show prices in a visitor’s local currency but still charge and settle in my base currency without confusing guests?
- Can I set different tax rules (local occupancy tax, VAT, city tax) based on location and ensure they are clearly shown in the booking breakdown for guests and hosts?



