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.
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.
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.
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.
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.
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.