Turkey Accommodation Tax and Metasearch Pricing
Model accommodation tax, VAT, mandatory fees and total-price semantics correctly in hotel metasearch and OTA price comparison for Turkey.
Hotel price accuracy in Turkey is not only about comparing room rates. Accommodation tax, VAT, mandatory fees and the point at which each channel includes those components all change total-price semantics. Two channels can show the same nightly headline while producing different payable totals.
2026 accommodation-tax context
The Turkish accommodation-tax provision covers overnight accommodation and certain services sold together with that stay. The statutory rate is 2%, while Presidential Decision 11263 applies a 1% rate from 1 May 2026 through 31 December 2026.
This is date-sensitive information and should not be hard-coded as a permanent Turkey tax rate.
Tax data model
Price
├─ baseAmount
├─ taxes[]
│ ├─ type
│ ├─ rate
│ ├─ amount
│ ├─ includedInDisplay
│ └─ effectiveFrom / effectiveTo
├─ mandatoryFees[]
├─ optionalFees[]
├─ currency
└─ totalPayableStore tax-rule source, effective period and calculation basis.
Keep VAT separate
Accommodation tax and VAT are not the same tax component. Official tax material defines the accommodation-tax base separately from VAT. Flattening all taxes into one number creates parity and reconciliation errors.
Metasearch display
The right comparison question is not “is the headline rate equal?” but “is the mandatory total payable equal for the same traveler context?”
Differences can include tax inclusion, property-payable fees, service fees, payment-at-property behavior, nationality/market pricing and currency conversion.
Price parity
Treat offers as comparable only when room/rate/meal/cancellation/occupancy and tax-inclusion semantics match. Comparing tax-exclusive and tax-inclusive prices produces false parity anomalies.
Booking handoff
Tax semantics shown in metasearch should survive into landing and booking. If mandatory tax appears only on the landing page, the search result should not be labeled as an all-in amount.
Failure modes
Typical failures include stale tax rate, effective-date timezone errors, double-counting VAT and accommodation tax, merging inclusive/exclusive offers, losing market-specific rules and reconciliation drift between observed and confirmed totals.
Observability
Track total-price mismatch, tax-component mismatch, rule version, landing-vs-observed delta, confirmed booking delta and market/nationality buckets.
Production checklist
- Version and effective-date tax rules.
- Keep VAT and accommodation tax separate.
- Separate mandatory and optional fees.
- Expose total payable.
- Preserve display-inclusion semantics.
- Invalidate caches on tax-rule change.
- Reconcile final booking total.
Planning a similar integration?
We can review requirements, feed/API design and the production approach with you.