Blog›Pricing

Setting Up Taxes and Fees in Your PMS: Inclusive vs. Exclusive, Per Channel

Setting taxes and fees as inclusive or exclusive sounds like one decision, but a PMS has to apply it consistently per channel, and that's where setups usually go wrong.

The Prime Host Partners team22 Nov 2026 · 7 min read

A PMS typically lets you mark a rate as tax-inclusive or tax-exclusive, but that setting has to be applied consistently across every channel the rate reaches, and channels don't always display or calculate it the same way by default. Getting this right once at setup avoids a slow drift where guest-facing prices across channels quietly stop matching.

Full guide on this topic
What inclusive and exclusive actually mean in practice

An inclusive rate already has applicable taxes and fees folded into the number a guest sees as the room price, with the breakdown shown separately for transparency but not added on top. An exclusive rate is the base amount before taxes and fees, which get calculated and added at checkout or on the invoice. Both are legitimate approaches, and which one is standard often depends on local convention and guest expectations as much as on your own preference.

The setup problem isn't choosing one over the other — it's making sure the choice is applied the same way for the same rate plan across every channel that sells it, rather than inclusive on one and exclusive on another without anyone intending that.

Why channels can interpret the same rate differently

Different OTAs have their own extranet conventions for how tax and fee information is submitted and displayed, and a rate pushed from your PMS without the matching setting on the channel side can end up displayed inconsistently with your intent — appearing tax-inclusive on one channel and exclusive on another even though you configured the same underlying rate plan. This is compounded if you manage some channels manually and others through a channel manager, since each layer is a place the setting can be entered differently.

Where inconsistency usually creeps in
1Rate plan configured once, channel settings configured separatelyThe inclusive/exclusive choice has to be set correctly on both the PMS rate plan and the channel's own extranet settings.
2Mixed management across channelsSome channels managed directly, others through a channel manager — each entry point is a chance for the setting to differ.
3Local tax rule changes not reflected everywhereA regulation change updated in one place but not propagated to every channel's configuration.
How to check your current setup

For each rate plan, confirm in your PMS whether it's configured as inclusive or exclusive, then check that same rate plan's guest-facing display on every channel it reaches, comparing the actual breakdown shown rather than trusting the PMS setting alone. Note any channel where the displayed treatment doesn't match what you configured, since that's the specific mapping or channel setting to correct rather than the base rate plan. Repeat this check whenever you add a new rate plan or connect a new channel, since the setting doesn't automatically carry over.

A tax setting that's correct in your PMS and wrong on one channel is still wrong from the guest's side — they only ever see the channel's version.
Getting it consistent and keeping it that way
Decide inclusive or exclusive per rate plan based on local convention and guest expectations, consistently.
Check the actual guest-facing display on every channel the rate plan reaches, not just the PMS setting.
Correct channel-specific settings individually where the display doesn't match your intended configuration.
Recheck the setup whenever you add a new channel or rate plan.
Keep a simple record of which setting applies to which rate plan, since this is easy to forget months later.
How Prime Host stops this from happening again

Read-back verification is built for exactly this kind of configuration drift — when a rate plan, including its tax treatment, is pushed to a channel, the system reads back what the channel actually stored and compares it against what was intended, rather than assuming a push succeeded because it didn't return an error. If inconsistent tax display across channels has been a recurring source of guest confusion or pricing disputes, that check is the structural fix — the public demo at try.primehostpartners.com is open to try without signing up.

Frequently asked
Is tax-inclusive or tax-exclusive pricing better?
Neither is universally better — it depends on local convention and guest expectations. What matters is applying the choice consistently across every channel for the same rate plan.
Why would the same rate plan show differently on two channels?
Each channel has its own extranet settings for tax display, and if those aren't configured to match your PMS rate plan, the guest-facing treatment can differ even though the underlying rate is the same.
How often should I recheck tax display settings?
Whenever you add a new rate plan or connect a new channel, and periodically as a spot-check, since settings don't automatically carry over or stay in sync on their own.
Want to see all of this working for real?
Walk through the actual system in read-only mode. Nothing to fill in.

Read next

© 2026 Prime Host Partners
Privacy PolicyTerms of Service