Google Hotels & Vacation Rentals is best understood as a discovery layer, not as the place where the reservation is actu...
Google Hotels & Vacation Rentals is best understood as a discovery layer, not as the place where the reservation is actually completed. It surfaces villa listings, rates, and map placement inside Google Search and Google Maps, then sends the traveler onward through a referral link to the property's own checkout path or to another booking site. For Bali villa operators, that search visibility can create high-intent traffic without the usual OTA commission stack, but the accounting logic is different because the final transaction happens elsewhere. VillaTax treats Google Hotels as a referral source and a visibility signal, then ties the downstream booking back to the physical villa unit so the tax record reflects the completed stay rather than the click path.
Google Hotels matters in Bali because it can place a villa in front of a traveler at the exact moment of intent, which is often before that traveler even opens an OTA. The commercial value is visibility, not merchant settlement, so the operator still has to own the final guest record, the Banjar registration, and the lodging tax file. That makes the referral trail worth preserving: the search click explains where the guest came from, but the final invoice explains what was actually sold. VillaTax keeps those two layers separate so the direct-search traffic can be reviewed without confusing it with OTA inventory.
VillaTax reads Google Hotels activity through referral logs and the reservation exports produced by the property's own checkout system. Managers usually download CSV or Excel files from the website engine or channel dashboard, because Google itself is only passing traffic through, not settling the booking. Those files contain click-through identifiers, final booking dates, guest details, and the room values captured at checkout. VillaTax uses them to connect the search referral to the completed reservation and to keep the lodging ledger aligned with the actual guest arrival.
VillaTax records the booking reference, guest details, occupancy dates, villa listing identifiers, and the room value that appears in the property's own checkout records. The important point is to follow the finished reservation, not just the search click, because the tax file needs the actual accommodation amount and not the referral impression. When the booking settles in a foreign currency, VillaTax converts that amount into Indonesian Rupiah using the Ministry of Finance rate for the stay date. Each row is tied back to the villa profile so the search referral can be reviewed against the final lodging declaration.
Data fields automatically synchronized
From platform to compliance in 4 steps
(1) Referral traffic can stay visible in Google even after the guest changes the booking flow on the property site, so the final export has to be refreshed before filing. (2) If a non-refundable fee is kept after cancellation, the checkout record should be adjusted separately from the referral click so the tax base reflects the real cash retained. (3) Search-query logs, click-through reports, and bank settlements do not always move at the same pace, so the file set should be checked together before month-end. A weekly review is usually enough to catch mismatches early.
Bali operators using Google Hotels need to keep the booking path and the guest record in sync, because the search listing itself does not create the legal stay record. Local currency display, Banjar registration, and Pondok Wisata capacity still have to be managed by the property team once the traveler lands on the site. VillaTax cross-checks the referral traffic against the actual reservation and the stay currency so the operator can prove where the guest came from and what was ultimately billed. That separation matters during inspections because the referral source is useful for SEO, but the tax file needs the completed stay.
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.
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.
No. Google Hotels is a search directory, not a merchant of record. It does not collect or remit regional PBJT or PPh for a Bali villa. VillaTax uses the referral data only to connect the search click to the completed reservation so the property can file against the actual stay.
VillaTax matches the referral code with the final invoice from your own checkout flow. If the guest arrives through Google search and completes the stay on your site, the record is stored as referral-led direct demand rather than as an OTA booking.
A fresh export is needed. VillaTax replaces the earlier row so the referral path and the final booking value stay aligned with the completed stay.
VillaTax converts the completed booking 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 search listing itself.
Connect this integration to your full compliance workflow
Start free โ connect your channels and let VillaTax compute PBJT, PPh and BPJS automatically.
Create a free account