Skip to main content

Tourist Tax Configuration in Booking.com Full Sync from AvaiBook

Booking Full Sync | Tourist Tax

Written by Adriana Silva

⚠️ This configuration only applies to Booking.com Full Sync

From AvaiBook, you can configure the specific tourist tax for your listing synchronized with Booking.com directly from:

Property settings → Booking.com → Extras → Tourist tax configuration


What does this configuration allow?

This option allows you to indicate to Booking.com how the tourist tax should be applied to reservations coming from this channel.

You can define:

  • The tourist tax amount.

  • When it should be applied.

  • How it should be displayed to the guest.


How is the tourist tax charged to the guest?

You have two available options:

Additional charge on top of the reservation price

The tourist tax is added separately to the accommodation price, and Booking.com will display it as an additional amount in the reservation.

Included in the reservation price

The tourist tax is included within the total price shown to the guest.


How is each option displayed on Booking.com?

Within the tourist tax settings for the Booking.com Full Sync connection, there are two possible options:

Option 1: The tourist tax is charged separately from the booking price

In this case:

  • Booking.com will display the tourist tax as an additional amount, separate from the accommodation price.

  • During the booking process, the traveller will see that there is an additional charge corresponding to the tourist tax.

  • The accommodation will need to collect this amount separately.

This scenario is commonly used when:

  • the property owner charges the traveller directly,

  • payments are managed through AvaiBook,

  • or the tourist tax needs to be collected upon arrival.

📌 The tourist tax is normally not collected before check-in, as it depends on the actual stay and the final number of guests.

Option 2: The tourist tax is included in the displayed price

In this case:

  • Booking.com will include the tourist tax in the total amount displayed to the traveller.

  • The guest will not see the tourist tax as a separate charge during the booking process.

  • This is the most common option when Booking.com manages payments through:

    • virtual credit card,

    • bank transfer,

    • or Payments by Booking.


Tourist tax display in AvaiBook

If you have a Pro or Elite Plan and have also configured the tourist tax in the accommodation settings, AvaiBook can display a more detailed breakdown of the amounts based on the information received from Booking.com.

In this case:

  • in the booking amounts section,

  • you will be able to see the total amount received from Booking.com,

  • and the tourist tax displayed separately when Booking.com sends this information as a separate amount.

⚠️ How this information is displayed will always depend on how Booking.com sends the financial breakdown of the booking.

On other plans, this detailed breakdown is not available, as certain advanced features related to financial management and the detailed display of amounts are included in the Pro and Elite Plans.


Where does the breakdown shown in the booking details come from?

The financial breakdown displayed in AvaiBook depends on:

  • the information sent by Booking.com,

  • the Full Sync connection model,

  • and the payment method configured on Booking.com.

For this reason, some amounts may vary or be displayed differently depending on:

  • whether Booking.com charges the traveller,

  • whether the accommodation charges the traveller,

  • or whether the tourist tax is included in the total amount.


Important

The setting that determines whether the tourist tax “is paid at the property” or not cannot be configured via API from AvaiBook.

Furthermore, according to Booking.com's official documentation, this setting cannot be modified directly by the accommodation from the Extranet either and must be managed by contacting Booking.com Support.

For more information on how Booking.com manages VAT and local taxes, you can refer directly to the platform's official documentation:

Did this answer your question?