OTAiCal feedGlobal

Hopper + VillaTax

Hopper is a mobile booking app built around timing advice and price protection rather than a traditional desktop-style r...

Type
OTA
Region
Global
Connection
iCal feed
Payout
Per booking
Connector details
TypeOTA
RegionGlobal
Connection
iCal feedEmail parser
PayoutPer booking
Confidenceindustry_known
Last verified2026-06-18
Sources4

About Hopper

Hopper is a mobile booking app built around timing advice and price protection rather than a traditional desktop-style reservation flow. Travelers use it when they want the app to tell them when to book, then they lock in a fare or room rate through features such as price freeze. For Bali villa operators, that creates a very specific accounting job: the guest may pay one amount while Hopper later absorbs part of the price movement or reverses part of the freeze. VillaTax treats Hopper as a mobile demand signal plus a settlement record, then strips out the algorithmic adjustments so the final lodging figure reflects the actual stay.

Why this platform matters for a Bali villa

Hopper matters in Bali because it brings in mobile-first guests who expect to book, freeze, and confirm from a phone in one sitting. The business problem is that the algorithm can shift the rate between the time the guest commits and the time the payout is settled, so the tax ledger has to follow the final stay value rather than the app's moving price story. VillaTax reads the Hopper file, removes the freeze subsidy from the room figure, and links the result back to the villa record. That keeps the property team's monthly reporting closer to what was actually sold.

Connecting Hopper to VillaTax

VillaTax ingests Hopper exports from the partner dashboard as spreadsheet files. Hopper is mobile-first, so the usual workflow is to pull the booking summary, the freeze adjustment report, and the payment log, then upload those rows into VillaTax. The import includes reservation codes, stay dates, guest names, gross payment values, and any price-protection adjustment that changed the final amount. VillaTax uses those rows to match the app booking to the correct villa unit and to compare the mobile payout with the actual bank deposit before the monthly filing is assembled.

What data VillaTax imports from Hopper

VillaTax stores the booking code, the guest details, the stay dates, the villa identifier, and the gross payment that ended up on the mobile receipt. The key point is to isolate the real accommodation amount from any rate freeze subsidy or promotional adjustment. If Hopper settled the stay in a foreign currency, VillaTax converts that amount into Indonesian Rupiah using the Ministry of Finance rate for the stay date. Each row is linked to a villa profile so the app booking can be reviewed against the actual property and not just the mobile receipt.

What VillaTax captures

Data fields automatically synchronized

Reservation code
Check-in date
Check-out date
Nights stayed
Guest name
Gross revenue
Platform commission
Net payout
Payout date

How it works

From platform to compliance in 4 steps

1
Connect platform
Sync bookings automatically
2
Ingest data
VillaTax normalizes all records
3
Tax calculation
IDR conversion & obligation mapping
4
Compliance output
Reports, exports, declarations

Things to know

Operational quirks

(1) If a traveler changes the stay dates after the freeze has been applied, the new export has to replace the earlier one so the final amount stays current. (2) When a booking is cancelled and part of the payment is retained, the retained cash should be reviewed separately from the freeze subsidy so the tax base does not drift. (3) Promo codes and mobile-app discounts can sit in a different line from the hotel payout, so the reservation file needs to be checked against the bank statement before filing. A weekly sweep is usually enough to catch those changes early.

Bali-specific watchouts

Bali villa operators using Hopper need to be quick on the guest register because mobile bookings often land late and change again before arrival. The Banjar file still has to match the actual people staying in the villa, and the property count still has to stay within the Pondok Wisata limit on the license. VillaTax compares the app reservation with the final check-in record and the currency conversion basis so the operator can prove what was booked, what was frozen, and what was ultimately received. That matters when local reviewers want the mobile trail and the on-site trail to match.

  • iCal feeds are read-only — cancellations and modifications need to propagate from the source platform.
  • Sync frequency depends on polling interval; there may be a short delay between the event and dashboard update.
  • Currency conversion to IDR may introduce minor rounding differences in tax reports.

Points of vigilance

OTAs typically operate under pricing-parity terms, which limits how much cheaper you can sell on direct channels. Many OTAs also delay payouts (T+30 or longer), so cash-flow planning matters — VillaTax records the booking on check-in date for tax purposes, regardless of when the OTA pays you.

Global platforms expose multi-currency flows. Always reconcile against IDR at the official Kurs Pajak rate, not the platform's internal conversion.

Indonesian fiscal framework that applies regardless of platform

The tax obligations triggered by a villa booking in Bali are defined by Indonesian law and do not depend on which platform produced the reservation. This section lists the applicable provisions with citations to primary sources; for case-by-case computation use the /dashboard/tax cockpit.

• PBJT (Regional Accommodation Tax) at the rate set by each Bali kabupaten — see UU 1/2022 HKPD Pasal 56–61 and Perda Badung Pasal 7–8 for the legal basis. Liability accrues at check-in date and is owed monthly. • PPh Final 4(2) on rental income — when the lessor is a non-corporate Indonesian taxpayer, PP 34/2017 sets a final 10% rate on gross rental. For corporate lessors, PPh Badan applies at the rate fixed in UU 7/2021 HPP. • PPh 21 on staff salaries — TER (effective rate) regime per PP 58/2023 and PMK 168/2023; VillaTax computes monthly withholding for your villa staff. • PPh 26 on cross-border payouts — UU 36/2008 Pasal 26 and PMK 112/2022 — applies when a non-resident receives Indonesia-sourced income; relevant for cross-border OTA commission settlements rather than the host's payout. • PPN (VAT) — UU 7/2021 HPP — only if the lessor is a registered PKP (Pengusaha Kena Pajak). • LKPM quarterly investment report — required for entities with foreign capital, filed via BKPM. None of these obligations depend on which OTA, PMS or channel manager produced the booking.

Sources cited

Platform-specific fiscal points VillaTax tracks

  • Regional lodging tax. Under the UU 1/2022 HKPD framework, a Hopper reservation usually becomes a 10% regional lodging tax item once the final stay amount is known. The tax base is the gross amount paid by the guest after the freeze has been settled, not the app's promotional headline rate. VillaTax keeps the reservation code and the final value on file so the monthly filing reflects the completed stay.
  • Income tax on lodging revenue. Revenue from the realized villa stay is normally subject to PPh Final Pasal 4(2) at 10% under PP 34/2017. For PT PMA structures, that income still needs to be shown in the monthly corporate tax process. VillaTax converts the final booking value to IDR using the relevant Ministry of Finance rate and keeps the freeze adjustment separate from the accommodation revenue.
  • Withholding tax on app commissions. If Hopper or an upstream vendor retains app fees as a foreign counterparty, PPh Pasal 26 withholding may need to be reviewed at the standard 20% level under UU 36/2008. Whether treaty relief applies depends on the vendor's documentation and residence certificate. VillaTax keeps those fee lines in the expense ledger so the operator can review the withholding position without merging it into the stay amount.
  • BKPM investment realization. PT PMA entities in Bali still need quarterly LKPM reporting to BKPM, and that report is easier when mobile booking traffic is separated cleanly by property. VillaTax turns the Hopper rows into a channel view that matches the bank history and the actual villa stay.

Frequently asked questions

Does Hopper calculate local Bali lodging taxes automatically?

No. Hopper is a mobile booking app, not a tax processor. It does not calculate, collect, or remit regional PBJT or PPh for a Bali villa. VillaTax uses the exported rows to separate the final stay value from the rate-freeze adjustment so the property can file against the real booking.

How does VillaTax handle price freeze bookings from Hopper?

VillaTax uses the final stay amount from the Hopper export as the tax base and keeps the algorithmic freeze subsidy separate. It then matches the stay to your calendar entry and converts the currency using the relevant Ministry of Finance rate so the filing reflects what the guest actually paid for the room.

What happens if a guest cancels a Hopper booking?

You need a fresh export. VillaTax replaces the old row so the stay value, dates, and freeze adjustment stay aligned with the final app record.

What currency rate does VillaTax use for Hopper payouts?

VillaTax converts the final payout value to Indonesian Rupiah using the Ministry of Finance rate tied to the stay date, so the ledger follows the actual villa sale rather than the app's moving price estimate.

Explore VillaTax features

Connect this integration to your full compliance workflow

Similar connectors

Automate your Bali villa tax compliance

Start free — connect your channels and let VillaTax compute PBJT, PPh and BPJS automatically.

Create a free account
Editorial review
Reviewed on 2026-06-18 against industry-known information. Some details may be approximate — contact us if you can confirm or correct.
All integrations (310)