Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Booking.com bills Indian hotels for commission from its Netherlands B.V. entity in INR or EUR, making the commission an import of service that requires 18% IGST under RCM with self-invoice — while virtual-card versus collect-at-property models, Genius programme discount funding, and forex variance on EUR invoices each create separate reconciliation breakpoints not present in domestic OTA settlements.
Per booking, identify payment model (virtual-card or collect-at-property), match Booking.com confirmation to PMS folio, derive room revenue at the correct GST slab (12% or 18%), book commission expense at invoice-date rupee value, raise a self-invoice for RCM 18% IGST, claim equivalent ITC, recognise forex variance separately on payment date, and split Genius discount funding between hotel and Booking.com per contract.
Booking.com extranet connector for confirmations and invoices; PMS folio adapter; payment-model classifier (virtual-card versus collect); RCM self-invoice generator with GSTR-3B Table 3.1(d) mapping; forex rate master with RBI reference rates; Genius discount split rule per contract.
A reconciled ledger where each Booking.com booking matches a PMS folio at correct GST slab, RCM IGST is paid and claimed, virtual-card MDR is captured, forex variance is recognised separately, and the GSTR-3B return correctly populates Table 3.1(d) for inward supplies under reverse charge.
A 90-room boutique property in Jaipur generates 35% of its revenue from Booking.com. The monthly Booking.com B.V. invoice arrives in EUR for 180 bookings, mixing standard listings with Genius and Preferred Partner placements. Settlement is partly through virtual cards charged at check-in and partly net commission deducted from the hotel’s payable. The finance team must reconcile each booking back to a PMS folio, raise an RCM self-invoice for the import of service, claim equivalent ITC, and recognise forex variance — all while keeping GSTR-1 and GSTR-3B aligned. This article is for hotel controllers reconciling Booking.com settlements in India.
What Booking.com Hotel Settlement Reconciliation Involves
Booking.com hotel settlement reconciliation in India differs from domestic OTA reconciliation in three structural ways. First, the commission supplier is a non-resident entity (Booking.com B.V., Netherlands), which makes the commission an import of service subject to reverse-charge GST rather than a domestic 18% commission with forward-charge GST. Second, two payment models coexist on the same property — virtual-card collected at check-in, and net-commission collected after the guest pays the hotel. Third, where invoices are EUR-denominated, forex variance enters the reconciliation between invoice booking date and payment date.
The reconciliation outputs are: a folio-level revenue ledger at the correct GST slab (12% up to ₹7,500 tariff, 18% above), an RCM self-invoice register feeding GSTR-3B Table 3.1(d), and a forex variance schedule supporting the period’s profit and loss reconciliation under Ind AS 21 or AS 11.
How Booking.com Settlement Reconciliation Works
Identifying the Payment Model Per Booking
The Booking.com extranet flags each booking as virtual-card or collect-at-property. Virtual-card bookings carry an issued one-time card number that the hotel charges through its acquirer at or after check-in — gross room amount lands net of card MDR (typically 1.75% to 2.5% on an international card). Collect-at-property bookings have no Booking.com card; the guest pays directly and the hotel later receives a commission invoice. The reconciliation classifier must run before any matching because the downstream cash flow is structurally different.
Self-Invoice for RCM IGST
For each Booking.com B.V. invoice, the Indian hotel must raise a self-invoice under Section 31(3)(f) of the CGST Act for the import of service. The self-invoice carries a unique series number, the hotel’s GSTIN as recipient and supplier (with Booking.com B.V.’s name and address shown as the foreign supplier), the commission value in INR at the invoice-date RBI reference rate, and 18% IGST. This IGST is paid in cash through GSTR-3B Table 3.1(d) and claimed as ITC in Table 4(A)(3) of the same return — net cash impact is zero if fully creditable, but the audit trail matters.
Booking the Room Revenue at the Correct GST Slab
The hotel’s own output GST is determined per booking by tariff. A room sold to the guest at ₹6,800 net of Genius discount but at a published rate of ₹8,000 — the transaction value is ₹6,800 and falls in the 12% slab, even though the published rate would have triggered 18%. The reconciliation logic reads the actual transaction value from the PMS folio, not the rack rate, and applies the slab accordingly. For Genius discount-funded bookings where Booking.com reimburses part of the discount, the funded amount is treated as a price reduction in some contracts and as a separate reimbursement in others — contract terms govern the GST treatment.
Recognising Forex Variance
If the Booking.com invoice is in EUR, the hotel books the commission expense and the RCM IGST on the invoice-date rupee value (using the RBI reference rate). When the hotel settles in EUR, the actual rupee outflow may differ. The difference is forex gain or loss in the period of settlement. RCM IGST is not re-computed on payment-date rupee value — the original IGST stands.
Booking.com Settlement Reference
| Element | Standard Listing | Genius / Preferred / Visibility Booster |
|---|---|---|
| Commission range | 15% to 18% | Adds 2% to 5% on top of standard |
| Commission GST treatment | RCM IGST 18% (import of service) | RCM IGST 18% (import of service) |
| Self-invoice required | Yes, monthly | Yes, monthly |
| Payment model | Virtual-card or collect-at-property | Same — payment model is independent of programme |
| Forex variance | Applies on EUR invoices | Applies on EUR invoices |
| Genius discount funding | Not applicable | Per-contract split between hotel and Booking.com |
India Compliance Angle: RCM Self-Invoice Audit Trail
A scrutiny assessment for an Indian hotel with material foreign-OTA traffic typically asks for the self-invoice register, the GSTR-3B Table 3.1(d) trail, and the corresponding ITC claim in Table 4(A)(3). Three errors recur. The first is treating the Booking.com invoice as a domestic supply and claiming ITC on a non-existent forward-charge GST. The second is paying RCM IGST but missing the self-invoice — the IGST cash payment has no underlying invoice to support ITC. The third is mismatching the invoice-date rupee value used for RCM IGST against the payment-date rupee value used for expense — which corrupts both the ITC base and the forex variance schedule.
Hotel finance teams using payment gateway reconciliation tooling can ingest Booking.com extranet exports alongside virtual-card acquirer settlements and route the RCM workflow into the same period close. A broader reconciliation software India platform extends this with PMS folio matching, multi-OTA support, and the foreign-supplier RCM detection logic. Industry guidance from FHRAI on cross-border commission GST treatment provides the policy reference for hospitality controllers.
For the broader hotel industry reconciliation surface, see the Hotels & Hospitality industry guide.
The following questions address the Booking.com settlement reconciliation issues hotel finance teams encounter most frequently.