HEDNAPULSE

Educational Brief

Taxes, Fees & the Distribution Gap

Understanding how tax complexity disrupts the hotel distribution ecosystem.

The full 13-page PDF is a member benefit. This page walks through what the brief covers and lets you trace a tax record through the chain yourself — no login needed for that.

For the Global Hotel Distribution Community AUGUST 2026

The signature idea

One room night. Three taxes. Four systems that disagree.

A $300 room in New York carries three separate taxes, each with its own name, rate and jurisdiction. The property management system holds all of it correctly. Follow what each system downstream actually carries — then watch the booking come back.

Press Trace the rate to push the property’s tax configuration out through the chain, one system at a time.

Scroll the table sideways to compare all four systems →

The same room night as each system records it — base rate $300.00 per night.
Tax line Property systemPMS — the source Central reservation systemCRS Distribution platformChannel manager Travel sellerWhat the guest pays
Sales TaxNYC Sales Tax · NYC4.500%  $13.50 “Tax 1”4.500%  $13.50Renamed Not carriedno tax lines at all Sales Tax · NYC4.500%  $13.50
State TaxNY State Tax · NY4.000%  $12.00 “State”4.000%  $12.00Renamed Not carried State Tax · NY4.000%  $12.00
City TaxNYC City Tax · NYC5.875%  $17.63 “Occupancy”5.500%  $16.50Renamed + revalued Not carried City Tax · NYC6.000%  $18.00Third different value
Jurisdictionwhich authority levies it Recorded per taxNYC / NY / NYC No fieldnames carry no jurisdiction No field Resolvedfrom the seller’s own table
Remittancewho pays the authority Property remits all three Not recorded Not recordedbase rate + tax-exclusive flag only Splitplatform remits City Tax; property remits the restNever sent upstream
Total per night $343.13 $342.00 $300.00+ “tax exclusive” $343.50

Now the booking comes back

Nothing above is broken. Each party configured its own connection sensibly. But the reservation has to return to the property, and the tax figure it carries is not the tax figure the property holds.

1

The guest books and pays the seller. Room $300.00 plus $43.50 of tax, calculated from the seller’s own rates. Includes City Tax at 6.000%.

$343.50
2

Under its remittance logic, the platform pays City Tax directly to the jurisdiction. Correct behaviour — but no field in the reservation message records that it happened.

−$18.00
3

The seller issues a virtual card for the balance owed to the property. Authorised for the net amount, not the guest total.

$325.50
4

The reservation lands in the PMS, which applies its own tax table and opens the folio. City Tax at 5.875% — and no indication it has already been remitted.

$343.13
5

At checkout the property charges the virtual card the folio total. $343.13 requested against a $325.50 authorisation.

$343.13
×

Virtual card declined. The charge exceeds the authorisation by the full value of a tax the platform had already paid. Short by $17.63 — and the front desk finds out at checkout, with the guest present.

−$17.63

Two faults, and only one of them looks like a problem

  • Remittance. The platform paid City Tax to the jurisdiction and the property billed it again, because no system in the chain carries a field that says who remits. That is the $17.63 — visible, disputed, and somebody spends an afternoon on it.
  • Value. Settle the remittance question and a gap remains: the guest was charged $18.00 of City Tax, the property’s records say $17.63, and the CRS says $16.50. Nobody chases $0.37. It recurs on every booking through this channel.
  • The first fault gets a support ticket. The second gets written off as a rounding error — which is why it is still here.

Illustrative example. The rates and amounts shown are for demonstration only and are not a statement of current New York tax rates, registration requirements, or any party’s obligations.

Inside the brief

Five questions this brief works through

Thirteen pages across nine sections, organised by where the money and the data actually move. If any of these are live questions in your organisation, the answers are in the full brief.

  • The hotel is where the tax obligation originates — so why is the property often the last to know when its tax data has been misrepresented upstream?
  • Two parties agree a connection is “tax-inclusive”. Which taxes, which fees, calculated on which base — and who decides?
  • When an intermediary has already remitted the tax, how does a property avoid paying it a second time without knowing?
  • Four systems each hold part of the tax record. Which one is authoritative?
  • If the mechanics are this well understood, why has the gap not been closed?

Pages

13

Sections

9

Stakeholder views

3

Contributors

6

01Hotel Operations: The Source-Point Problem
02Online Travel Sellers: Configuration Divergence
03Tax Confusion: Disruption Across the Chain
04Intermediaries: Layers of Accountability
05Why the Gap Persists
06Technology: Systems That Don’t Talk
07Who Owns the Record of Truth?
08Industry Considerations by Stakeholder
09Suggested Action Plan

The brief sets out considerations for hotels, travel sellers and technology partners by name, three practical steps any business in the chain can take, and a glossary of the terms this subject keeps blurring.

No party in the distribution chain currently holds an authoritative, updatable, machine-readable tax record that all other parties can rely on.
“The Gap” — HEDNA Pulse, Taxes, Fees & the Distribution Gap, p.9

With thanks to

Contributors

Each contributor described a mechanism from inside their own operation. Specificity is what makes an educational brief usable — and Simone Large of Emerging Travel Group edited the brief as well as contributing to it.

Jeremy MahoneyHEDNA
Julie HoudeWyndham
Daniel ContiHilton
Simone LargeEmerging Travel Group Editor & lead contributor
Tanya PrattOracle
reconcileOTA

Comments are the contributors’ own and do not represent their employers or HEDNA.

The tax is real. The data about it shouldn’t be a guess.

Members are encouraged to use this brief as a starting point. Bring it into your next connectivity discussion, vendor conversation, or tax meeting.

Continuing the conversation at HEDNA Lisbon, 15–17 September 2026.

HEDNA takes no position on how taxes should be structured or regulated. This brief documents the operational realities of tax data in distribution to support informed, proactive review. For informational purposes only. Not legal, tax, or compliance advice. Members should conduct their own independent review.
© 2026 HEDNA · Hotel Electronic Distribution Network Association hedna.org info@hedna.org

Cite this brief: HEDNA Pulse (Aug 2026). Taxes, Fees & the Distribution Gap: An Educational Brief for the Global Hotel Distribution Community. hedna.org

Join HEDNA