GST Settlement in OTA Platforms: How Tax Is Calculated, Collected and Reconciled

Building a hotel booking platform is not just a checkout and calendar problem. Every booking in an Online Travel Agency (OTA) system carries at least three independent GST streams: accommodation tax that the hotel owes to the government, commission tax that the OTA owes to the government, and a convenience fee tax that the OTA collects from the customer. None of these is the same number, none has the same supplier, and none follows the same reconciliation path.

Teams that model "GST" as a single field on a booking record discover this the hard way when their GSTR-1 does not match their bank settlement, the hotel cannot claim ITC on the right amount, or TCS credits go unclaimed across hundreds of bookings. This guide explains how GST actually flows through an OTA platform, how to model it correctly in your data layer, and where the common mistakes are buried.

The Three GST Streams in Every OTA Booking

When a customer books a hotel room through an OTA, three separate GST obligations are created simultaneously. They have different suppliers, different rates, and different invoice requirements.

Stream 1 and Stream 3 both come from the customer, but they go to different tax ledgers. Stream 1 belongs to the hotel. Stream 3 belongs to the OTA. TCS is not output GST — it is a withholding collected by the OTA and credited to the hotel's electronic cash ledger when the OTA files GSTR-8.

GST on Each Booking Component

Every line item in a hotel booking may carry a different GST rate, a different supplier, and a different place of supply. The table below maps the common components.

Cancellation charges occupy a nuanced zone. Purely penal charges that are damages for breach of contract (not a consideration for any service) are not subject to GST under CBIC Circular No. 178/10/2022-GST. However, hotel cancellation charges that compensate the hotel for holding capacity (which is the common treatment in the industry) are taxable at the same rate as the underlying accommodation service. When in doubt, the hotel's chartered accountant should advise on the correct treatment for a specific cancellation policy.

A Complete Lifecycle Example

The following example traces a single booking from confirmation through settlement. All figures are illustrative.

Setup: Hotel Grand Bengaluru (Karnataka, 18% GST room above ₹7,500). Customer: individual from Delhi (B2C). OTA registered in Maharashtra. Room: ₹8,000 per night × 3 nights. OTA commission: 15%. OTA convenience fee: ₹500 + 18% GST.

Step 1: What the Customer Pays

Step 2: OTA Settlement to Hotel

Step 3: Hotel's Net GST Position

The hotel received ₹23,832 in bank but has a revenue of ₹24,000 (room) and a GST obligation of ₹4,320. The shortfall is funded by the ITC and TCS credits that reduce the cash outgo on the GST payment date.

How GST Fits Into Each Entity in Your Data Model

Each entity in an OTA system stores a different slice of the GST picture. Conflating them is the root cause of most reconciliation failures.

Booking

A booking is the reservation intent. It stores the preliminary GST calculation based on room type and tariff at the time of inquiry. Key GST fields: room_taxable_value, gst_rate, cgst_amount, sgst_amount, igst_amount, total_room_amount, customer_gstin (null for B2C), hotel_state, place_of_supply (= hotel state for accommodation). The GST type flag (B2B or B2C) drives whether the final invoice captures the customer's GSTIN. A booking should never store commission GST — that belongs to the settlement layer.

Order

An order is the confirmed, billable transaction. It locks the final taxable value, all GST components across every line item (accommodation, convenience fee, early check-in fees), and the order-level totals. Orders should carry a tax_liability_date field — for advance-paid bookings, this is the payment date (advance received), not the check-in date, because GST time-of-supply for services is the earlier of invoice date or payment date. A single booking may generate multiple order lines if different components are taxed at different rates.

Payment

A payment records what the customer actually paid. In a partial payment scenario (advance + balance at check-in), each payment event captures its own amount and a proportional GST component derived from the order. Storing the GST proportion per payment lets the system recognize partial GST liability as advance payments flow in — this is required for correct GSTR-1 Table 11A (advance receipts) and Table 11B (advance adjustments when invoice is issued).

OrderTransaction

An order transaction maps a payment event to an order component. It is the reconciliation bridge. Fields: order_id, payment_id, amount_applied, gst_applied, transaction_type (advance / balance / refund), time_of_supply_triggered. When an advance payment is received, create a transaction with type = advance and flag the GST as immediately due. When the final invoice is raised at checkout, create a type = balance transaction and mark the advance portion as adjusted.

Settlement

A settlement is what the hotel actually receives from the OTA after deductions. It must store: gross_booking_amount_incl_gst, ota_commission_excl_gst, gst_on_commission, tcs_deducted, net_payout, settlement_date, gstr8_reference (OTA's TCS filing reference). The settlement is not an invoice — it is a financial statement from the OTA. It does not replace the hotel's GST invoice to the customer. The hotel must still issue a proper tax invoice for the accommodation.

Invoice

Invoices are the formal GST documents. In an OTA booking, at least three invoices exist:

• Customer accommodation invoice: Issued by the hotel to the customer. Shows accommodation taxable value, CGST + SGST (hotel state), total. For B2B: includes customer GSTIN, place of supply explicitly stated.
• OTA convenience fee receipt / invoice: Issued by the OTA to the customer. Shows convenience fee taxable value, IGST (or CGST + SGST of OTA state). This is the OTA's own supply — completely separate from the hotel invoice.
• OTA commission invoice: Issued by the OTA to the hotel. Shows commission taxable value and 18% GST (IGST or CGST+SGST depending on states). The hotel claims ITC on this invoice.

A credit note must be issued (by the respective supplier) any time a refund reduces a previously invoiced amount — Section 34 of the CGST Act. A credit note cannot be used to reverse a cancellation that was never invoiced.

Time of Supply: When Does GST Liability Actually Arise?

This is the most misunderstood aspect of OTA GST, and getting it wrong causes GSTR-1 mismatches at the end of every month.

Under Section 13(2) of the CGST Act, the time of supply for services is the earliest of: (a) date of invoice issuance, or (b) date of payment receipt. For hotel accommodation, this means that when a customer pays an advance through the OTA in January for a March check-in, the hotel's GST liability is triggered in January (at the time of advance receipt by the OTA, which acts as the hotel's collection agent). The hotel must report this advance in GSTR-1 Table 11A for January and adjust it in Table 11B when the final invoice is issued at checkout in March.

OTA systems that track only check-in dates for GST reporting will consistently under-report GST in the advance month and over-report in the stay month, creating GSTR-1 mismatches with GSTR-2B of the counterparty.

CGST, SGST and IGST Across the Three Streams

Which tax type applies depends on which stream you are looking at and the states of the parties involved, not just the location of the hotel.

The practical implication: an OTA registered in Maharashtra handling hotel bookings across multiple states will issue IGST on its commission to hotels in all other states. Its own convenience-fee invoices to B2C customers will always be CGST + SGST of Maharashtra, regardless of where the customer is located.

Cancellations, Refunds, Partial Payments and Amendments

Each of these events touches multiple entities — the Order, the Invoice, the Settlement, and the GSTR-1 period — and must be handled differently depending on where in the lifecycle the change occurs.

Full Cancellation Before Check-in

The hotel issues a credit note under Section 34 of the CGST Act for the full accommodation value (or the refundable portion net of any cancellation charge). The OTA reverses the TCS collected proportionally. In the settlement, the OTA issues a revised settlement statement showing the TCS reversal and the refunded amount. The hotel's GSTR-1 is adjusted in the month the credit note is issued, not the original booking month.

Partial Cancellation or Amendment

If a customer shortens a three-night stay to two nights after check-in, the hotel issues a credit note for one night (with the appropriate GST reversal). The OTA adjusts the settlement — commission reduces proportionally, TCS reverses on the refunded amount. Systems that lock the order amount at confirmation and do not allow order-level amendment triggers will fail to produce the correct GST documents here.

Partial Payment (Advance + Balance)

When a customer pays 30% advance and the balance at check-in, both payments trigger a time-of-supply event. The advance payment triggers GST recognition on the advance proportion. If the final invoice amount differs from what was advance-taxed (because of a price amendment), the adjustment is handled through the invoice at checkout, not through a credit note on the advance.

Settled Orders That Are Later Refunded

The most complex scenario: the hotel received settlement from the OTA in month 1; the guest requests a refund in month 2 (for example, due to a complaint about room quality). The hotel must issue a credit note in month 2, reducing its output GST. The OTA must adjust the commission and TCS accordingly in its month-2 GSTR-8. The bank refund must be linked back to the original order via an OrderTransaction of type refund, with a negative GST component. Systems that store settlement as a final and immovable record cannot handle this correctly.

Common Reconciliation Problems

Most OTA GST reconciliation failures trace back to one of seven root causes, each with a specific fix.

Common Implementation Mistakes

These are the errors that appear most often in OTA booking systems when the team treats GST as an afterthought rather than a first-class data model concern.

• Storing GST as a single field on the booking record. GST spans at least three suppliers and two invoice types. A single gst_amount field on the booking creates reconciliation dead-ends the moment a partial refund or OTA commission adjustment occurs.
• Treating total_amount as taxable_value. The customer pays ₹28,910; the taxable value for accommodation is ₹24,000 and for the convenience fee is ₹500. Using the gross payment amount as taxable value overstates GST.
• Copying the OTA settlement amount as hotel revenue. The hotel's revenue is the room charge (₹24,000), not the net payout (₹23,832). The difference is commission expense (₹3,600) and GST (₹648) and TCS (₹240), each of which must be recorded separately.
• Triggering GST on check-in date, not payment date. Advance payments create GST liability on the date received, not on the service date. Ignoring this produces incorrect GSTR-1 returns.
• Not issuing a credit note on refunds. Bank-reversing a payment without a formal credit note leaves the original invoice standing in GSTR-1 without a corresponding deduction. The tax authority sees unexplained GST output.
• Treating OTA platform coupons as hotel discounts. If the OTA funds a discount from its own marketing budget, the hotel's taxable value is unaffected. Reducing the hotel's invoice for an OTA-funded coupon understates output GST.
• Assuming IGST on hotel accommodation for interstate guests. Hotel accommodation is always CGST + SGST of the hotel's state under Section 12(3) of the IGST Act. Generating IGST invoices for hotel rooms is wrong regardless of the guest's location.
• Not separating room and F&B on the same invoice. Corporate customers cannot claim ITC on food; they can on accommodation. A single invoice for both forces the customer into a guessing game or an ITC disallowance.
• Missing GSTR-8 reconciliation workflow. TCS credit only flows to the hotel after the OTA files GSTR-8. Systems that assume the settlement deduction and the GSTR-8 credit happen simultaneously will show phantom GST credits.

A Recommended Transaction Flow for Correct GST

When a booking is confirmed: create a Booking with preliminary GST split (CGST + SGST per room night, based on actual tariff and hotel state). Validate the customer's GSTIN if provided; set invoice_type = B2B if valid, B2C otherwise. Capture hotel_state and place_of_supply.

When payment is received: create an Order locking the final taxable values and GST components. Create a Payment and a corresponding OrderTransaction with time_of_supply = payment.date. If this is an advance, flag the GST component as advance GST and report in GSTR-1 Table 11A.

At checkout: issue the accommodation Invoice (hotel to customer). Adjust any advance-GST reported in Table 11A in Table 11B. If the stay was shorter than booked, issue a credit note for the unused nights. Update OrderTransaction with type = balance.

At OTA settlement: create a Settlement record with all deduction lines (commission, commission GST, TCS). Verify OTA's commission Invoice arrives with correct GSTIN and IGST/CGST+SGST based on state match. Reconcile TCS deduction with GSTR-8 filing reference. Only mark the settlement as RECONCILED once the TCS credit is visible in the hotel's GST portal cash ledger.

Frequently Asked Questions

Who issues the GST invoice to the hotel guest in an OTA booking?

The hotel issues the accommodation GST invoice because the hotel is the supplier of accommodation. The OTA may issue its own separate invoice or receipt for its convenience fee. The OTA does not issue an accommodation invoice on behalf of the hotel unless it operates as a pure agent under a specific contractual arrangement.

Does the OTA collect GST on the hotel room from the customer?

The OTA collects the money (including the accommodation GST component) from the customer, but it does so as a collection agent. The hotel's GST on accommodation must be remitted by the hotel, not the OTA. The OTA's own tax obligations cover its commission and convenience-fee income. Exception: if the hotel is unregistered (below ₹20 lakh threshold), Section 9(5) shifts the accommodation GST liability to the OTA.

What is the correct taxable value for accommodation when the customer pays the OTA?

The taxable value is the room charge exclusive of GST. If the customer pays ₹11,800 for a room (₹10,000 + 18% GST), the taxable value is ₹10,000. OTA commission is calculated on the taxable value (typically), and TCS is also applied on the net taxable value, not the gross amount including GST.

When should GST be recognized — at booking, at payment, or at check-in?

At the earlier of invoice issuance or payment receipt (Section 13(2), CGST Act). Advance payments trigger GST recognition on the payment date. The final balance triggers recognition when the invoice is issued at checkout. Check-in date is irrelevant for time-of-supply unless the service is provided before payment is received and before an invoice is issued.

Can the hotel claim ITC on the OTA commission GST?

Yes. The OTA commission is a business input (marketing and distribution service) used to make taxable supplies. The hotel can claim ITC on the GST portion of the commission, provided the OTA has filed its returns and the credit appears in the hotel's GSTR-2B.

How does TCS affect the hotel's GST payment?

TCS deducted by the OTA and filed in GSTR-8 through the GST portal flows into the hotel's electronic cash ledger. The hotel can use this credit against its output GST liability, reducing the cash it needs to pay. The credit is only available after the OTA files GSTR-8 for the relevant month, so timing matters for monthly GST reconciliation.

Does the OTA issue a single settlement statement or separate invoices?

Settlement statements and invoices serve different purposes. The settlement statement is a financial record showing how the gross booking amount was decomposed into commission, GST, TCS, and the net payout. It does not replace the OTA's formal commission tax invoice, which is the document that entitles the hotel to claim ITC. Both must exist and be reconciled against each other.

Getting OTA GST Right in Your Hotel Management System

The complexity of OTA GST, from three independent tax streams to TCS reconciliation and advance-payment time-of-supply rules, is exactly what a purpose-built hotel management system is designed to absorb. JHATTSE Business PMS handles GST-compliant billing, separates accommodation and F&B invoices, tracks OTA settlement deductions by channel, and generates GSTR reports that map to the correct invoice dates and supply periods. The free proposal includes a walk through of the billing and OTA settlement workflow. For a broader view of what a complete hotel management system covers, the product walkthrough playlist on YouTube covers the invoicing and channel management screens, and the JHATTSE Business blog has related articles on hotel finance and compliance.

Disclaimer: This article is for general informational and educational purposes only and does not constitute legal, tax, accounting, or software architecture advice. GST rules and CBIC circulars are subject to change. Hotels, OTA operators, and product teams should consult a qualified GST professional or chartered accountant for guidance on specific transactions, compliance obligations, and system implementations.