Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
An Indian hotel runs five concurrent revenue streams — direct guest payments, OTA bookings across MakeMyTrip, Goibibo, Booking.com, Agoda and others, corporate billing with TDS 194C and 194I, banquet advances split across two payments, and daily F&B cash deposits — each with its own settlement model, GST slab, and timing. Manual reconciliation across PMS, OTA settlement reports, gateway settlements, and the bank statement is multi-source and cannot reliably classify the OTA gross-to-net gap into commission, TDS 194H, GST on commission, and cancellation adjustments at scale.
Ingest PMS folios from Opera or IDS Next or eZee or Hotelogix, channel manager records from SiteMinder or STAAH, OTA settlement reports per platform, gateway settlements, and the bank statement. Match each bank credit to its source: OTA UTR to OTA settlement report, gateway batch to card and UPI folios, NEFT to corporate invoice. Decompose every OTA settlement variance into typed codes — OTA_COMMISSION, OTA_TDS_194H, GST_ON_COMMISSION, OTA_CANCELLATION — and route any residual to UNCLASSIFIED_OTA_ADJUSTMENT for review. Apply property-level GST classification at the room-tariff slab to F&B revenue.
Property-level GST classification flag (room tariff below ₹7,500 versus at or above ₹7,500), OTA settlement schema with bookings array and variance source fields, banquet advance two-phase matching keyed by event_booking_id, night-audit cut-off timezone, and PMS-to-bank lag tolerance window for gateway settlements.
A reconciled view that shows each PMS folio against its OTA settlement and bank credit, typed variance codes for every gross-to-net gap, deferred revenue tracked separately for banquet advances, GST slab classification applied automatically to F&B, and an exception list cleared in hours instead of the staff days a hotel finance team typically spends on month-end.
A 200-room four-star hotel in Bengaluru can settle, in a single calendar month, against MakeMyTrip, Goibibo, Booking.com, Agoda, Expedia, OYO, Yatra, Cleartrip, three corporate accounts on monthly NEFT, two banquet events with 50 percent advances, daily card-and-UPI gateway batches, and walk-in cash deposits from the restaurant and bar. Each stream settles on a different cycle, deducts a different set of charges, and appears in the bank statement under a different narration. Hotel reconciliation in India is not a single matching exercise but a stack of them, and the stack only resolves when the OTA gross-to-net gap, the PMS night-audit cut-off, the gateway MDR, and the room-tariff GST slab are all reconciled together. This guide covers what the payment mix looks like, where the reconciliation typically breaks, and what audit-grade evidence requires for a property under CARO 2020.
What Hotel Reconciliation in India Involves
Hotel reconciliation in India is the process of matching every PMS folio and every revenue line against its corresponding settlement evidence and bank credit, while classifying the difference between gross revenue and net cash received into typed variance codes. The exercise sits across at least five revenue streams.
- Direct guest payment at check-out (HT-C01) — card or UPI at the front desk, settled by the gateway on T+1 or T+2 net of MDR.
- OTA bookings (HT-C02) — MakeMyTrip, Goibibo, Booking.com, Agoda, Expedia, OYO, Yatra, Cleartrip. The OTA collects from the guest and settles to the hotel net of commission (15 to 25 percent), TDS under Section 194H at 5 percent on the commission, GST on the commission, and any cancellation adjustments. One settlement batch covers many bookings.
- Corporate billing (HT-C03) — invoiced monthly, paid by NEFT, TDS deducted under Section 194C for accommodation services and under 194I if room rental crosses the rent-threshold tests applied by the corporate buyer.
- Banquet and event revenue (HT-C04) — typically a 50 percent advance on confirmation, balance on the event day. Two payments link to one event booking.
- F&B at restaurant and bar (HT-C07) — daily POS settlements and cash deposits.
Three properties of this mix make Indian hotel reconciliation structurally harder than in markets where most rooms are sold direct. First, OTA penetration is high, so the largest single reconciliation challenge is the OTA gross-to-net decomposition. Second, the GST regime is room-tariff dependent, so F&B classification depends on the property’s inventory pricing. Third, statutory audit under CARO 2020 requires a documented bridge from PMS folio to bank credit, which manual reconciliation rarely produces at the level auditors expect.
Where Hotel Reconciliation Breaks
OTA Gross-to-Net Decomposition
A MakeMyTrip settlement of ₹6,42,000 against gross booking value of ₹8,40,000 is a ₹1,98,000 gap. That gap is not an error — it is the sum of OTA commission at the contract rate, TDS at 5 percent under Section 194H on that commission, GST on the commission, and any cancellation refunds netted from the same batch. Without typed decomposition, finance teams either accept the net and lose visibility on whether the contract commission was applied correctly, or hold the entry open as an unresolved variance. With booking volumes of 50 to 200 per settlement batch and three to seven OTAs settling weekly, the unreconciled-but-explainable backlog grows quickly.
PMS Night-Audit Cut-Off Versus Bank Settlement
Property management systems — Opera, IDS Next, eZee, Hotelogix — close the day at the night-audit cut-off, typically between midnight and 6 a.m. local time. Bank statements close on calendar-day cut-offs, and gateway settlements reach the bank on T+1 or T+2 after MDR is deducted. A folio closed in the PMS on the 10th appears in the bank on the 11th or 12th, net of MDR and net of GST on MDR. The hotel’s PMS shows gross; the bank shows net minus a delay; and channel manager records (SiteMinder, STAAH) show a third view of inventory and rate. Without a reconciliation that bridges all three timelines, daily revenue and daily cash never tie out cleanly.
The 12% Versus 18% GST Split
Since the October 2024 rule revisions, hotel rooms attract 12 percent GST with ITC where the room tariff is below ₹7,500 per night, and 18 percent GST with ITC where the tariff is at or above ₹7,500. Restaurant supplies inside a hotel inherit the property’s classification: if any room tariff crosses ₹7,500, restaurant GST is 18 percent with ITC; if no room exceeds ₹7,500, restaurant GST is 5 percent without ITC. Properties with mixed inventory or seasonal pricing sit at the boundary, and a misclassification in F&B GST flows through to GSTR-1 filings, GSTR-3B output liability, and ITC eligibility on procurement. Reconciliation needs the slab classification baked in, not bolted on at month-end.
The Hotel Reconciliation Process: Step by Step
Step 1 — Ingest Source Data
Pull PMS folios (Opera, IDS Next, eZee, Hotelogix), channel manager extracts (SiteMinder, STAAH), OTA settlement reports per platform, gateway settlements (Razorpay, PayU, Pine Labs, etc.), corporate invoices, banquet event registers, and the bank statement. Each source carries its own date convention, currency, and reference field. Standardise into a common record format that preserves the source identifiers — booking ID, folio number, settlement ID, UTR — for downstream traceability.
Step 2 — Match Bank Credits to Their Source
For OTA settlements, the bank narration typically contains the OTA name plus a settlement reference; match by UTR or settlement ID. For gateway batches, match by payout ID and date. For corporate NEFT, match invoice number from the narration to the corporate invoice register, then verify TDS 194C or 194I deducted. For banquet events, link the bank credit to the event_booking_id and tag whether it is the advance or the balance.
Step 3 — Decompose Variances Into Typed Codes
For every OTA settlement, compute (gross_booking_value − net_settlement) and decompose into OTA_COMMISSION, OTA_TDS_194H, GST_ON_COMMISSION, and OTA_CANCELLATION using the OTA’s own settlement report fields. Any residual is UNCLASSIFIED_OTA_ADJUSTMENT and goes to a review queue. For gateway settlements, the typed variance is GATEWAY_MDR plus GST on MDR. For corporate NEFT, CORPORATE_TDS at the relevant section. Typed variance codes are what makes the reconciliation auditable.
Step 4 — Produce Audit-Grade Evidence
For each reconciled folio and each reconciled settlement, the output is a PMS folio reference, the OTA or gateway settlement reference, the bank UTR, the typed variance breakdown, and the GST slab applied. This is the bridge that CARO 2020 auditors test against, and it is what removes the “unreconciled bank credit” line from the trial balance review.
Variance Taxonomy: Hotel Income Streams
| Code | Income stream | Settlement model | Typical variance |
|---|---|---|---|
| HT-C01 | Direct guest payment | Card / UPI, T+1 or T+2 | GATEWAY_MDR + GST on MDR |
| HT-C02 | OTA settlement | Net of commission, batch | OTA_COMMISSION, OTA_TDS_194H, GST_ON_COMMISSION, OTA_CANCELLATION |
| HT-C03 | Corporate billing | Monthly NEFT | CORPORATE_TDS (194C or 194I) |
| HT-C04 | Banquet advance | 50% on booking + 50% on event | Two-phase, BANQUET_ADJUSTMENT on final folio |
| HT-C05 | Travel agent commission | Net of agent commission | AGENT_COMMISSION |
| HT-C06 | Government / PSU | 45 to 90 day cycle | GST_TDS at 2% |
| HT-C07 | F&B cash | Daily POS to deposit | Date + amount within tolerance |
| HT-C09 | Cancellation / no-show | Card charge, separate batch | Reconcile against cancellation register |
The India-Specific GST and TDS Layer
The single biggest difference between hotel reconciliation in India and the generic OTA-commission guides is the regulatory layer. Five rules shape the matching logic.
First, OTAs deduct TDS at 5 percent under Section 194H on the commission they charge the hotel, and that deduction must appear in Form 26AS against the OTA’s TAN within the quarter. Cumulative tds_by_ota across settlements should reconcile to the 26AS view; mismatches typically arise from cross-quarter timing or the OTA filing late.
Second, foreign-currency OTAs such as Booking.com and Agoda often settle in INR but bill commission in foreign currency, which means a forex difference and, in some structures, reverse-charge GST on the imported commission service. The hotel must self-invoice under RCM and claim the ITC, and the reconciliation needs to link the foreign-currency commission line to the RCM payment.
Third, room-tariff GST is 12 percent below ₹7,500 and 18 percent at or above ₹7,500 (both with ITC) since the October 2024 rules. Restaurants inside hotels inherit the property’s classification: 18 percent with ITC if any room exceeds ₹7,500, otherwise 5 percent without ITC.
Fourth, banquet and event advances typically attract GST on receipt of the advance, not on the event date. Reconciliation has to track GST timing on the advance separately from revenue recognition on the event date.
Fifth, government and PSU billing attracts GST TDS at 2 percent and runs on a 45-to-90-day settlement cycle. The reconciliation has to keep these invoices in an aged-receivable view and tie the eventual NEFT credit back to the original invoice and the GST TDS certificate, with reference to filings in the Federation of Hotel & Restaurant Associations of India (FHRAI) format guidance for PSU receivables.
For statutory audit, all of this rolls up into the CARO 2020 evidence requirement: a documented bridge from PMS folio to OTA or gateway settlement to bank credit, with every variance classified.
What Automated Hotel Reconciliation Changes
A purpose-built reconciliation software India platform that handles hotels carries the OTA settlement schema, the gateway batch schema, the banquet two-phase matching, and the property-level GST classification as first-class concepts rather than as spreadsheet conventions. The OTA gross-to-net gap is decomposed automatically into the four typed codes; the gateway MDR is recognised at ingest; the night-audit cut-off and gateway lag are handled in the matching window; and the property’s GST slab is applied to F&B without manual review. Hotels that move from spreadsheet-based reconciliation to structured matching typically see month-end close compress from three to five staff days down to several hours of exception review, with the residual exception list cleanly classified for follow-up. For OTA-heavy properties, this is also the difference between an audit qualification and a clean opinion, because the typed variance trail is what CARO 2020 reviewers test. Hotel finance teams considering payment gateway reconciliation for the gateway side of the stack will find the same pattern applies — typed variance decomposition is what makes the math both fast and audit-defensible. For the broader hotel industry reconciliation surface, see the Hotels & Hospitality industry guide.