Indian hotels mix refundable security deposits, advances against room charges, no-show charges, and OTA virtual-card pre-authorisations in the same PMS deposit ledger, each carrying a different revenue trigger and a different GST timing under Section 13 of the CGST Act. Without typed tracking, the deposit ledger drifts, refund flows cross GST return periods uncleared, and CARO 2020 audit reviewers find stale liabilities and weak ageing on the deposit-payable balance.
Track each receipt by type — REFUNDABLE_SECURITY_DEPOSIT (no GST on receipt, balance-sheet liability), DEPOSIT_AGAINST_ROOM_CHARGES (GST on receipt under Section 13, revenue at check-in), NO_SHOW_CHARGE (taxable supply at room-tariff slab), OTA_VIRTUAL_CARD_PREAUTH (timing depends on charge versus pre-auth-only). Reconcile PMS deposit ledger to accounting AR and AP, age every open balance, and emit refund vouchers and credit notes for cancellation flows that cross GST periods.
PMS adapter exposing deposit-type classification, separate ledger accounts in the accounting system for each deposit class, GST advance-adjustment logic per Section 13 CGST, cancellation policy rules per booking source, OTA virtual-card pre-auth-versus-charge feed, ageing thresholds for deposit-payable balances, and refund-voucher generation tied to GSTR-1 advance-and-adjustment table.
A typed deposit ledger with no class-confusion between security deposits and advances, a clean GSTR-1 advance-and-adjustment line every period, no-show charges raising tax invoices at the right slab, refund flows reconciled to bank debits and to credit notes, and a deposit-payable ageing report that satisfies CARO 2020 on long-outstanding balances.
A 220-key luxury hotel in Goa during peak season carries, on any given night, ₹40 to 60 lakh of refundable security deposits, ₹2 to 3 crore of advances against room charges, OTA virtual-card pre-authorisations from Booking.com and Agoda totalling ₹1 to 1.5 crore, and a daily flow of no-show charges and cancellation refunds. The PMS deposit ledger touches all of it. Hotel deposit, refund, and no-show reconciliation in India is where revenue recognition timing, GST time-of-supply under Section 13 of the CGST Act, and CARO 2020 audit evidence intersect — and where a single uncleared receipt class can compound into a six-figure stale liability inside two quarters. This article is for hotel finance, front-office, and statutory-audit teams managing deposit reconciliation at Indian properties.
What Hotel Deposit Reconciliation Involves
Indian hotels collect money before consumption in four distinct ways, each with a different accounting treatment.
- Refundable security deposit — held at check-in against potential damage or incidental usage, refunded on checkout if no charge applies. Sits on the balance sheet as a liability. No GST on receipt because there is no underlying supply.
- Advance against room charges — applied to the contracted stay, used to confirm the booking. Revenue recognises only at check-in, but GST under Section 13 of the CGST Act is triggered on receipt at the applicable room-tariff slab.
- No-show charge — typically one night’s room rate, charged when a confirmed reservation does not arrive. Treated as a taxable supply at the room-tariff slab in most hotel accounting policies.
- OTA virtual-card pre-authorisation — for bookings where the OTA collects from the guest and issues a virtual card the hotel charges at check-in. The pre-auth is not a receipt; the eventual charge is.
These four cannot share one undifferentiated deposit ledger. Each needs its own classification at receipt and its own reconciliation path through the PMS, the accounting system, and the bank statement.
GST Time-of-Supply Under Section 13 of the CGST Act
Section 13 of the CGST Act sets the time of supply for services as the earlier of invoice date or payment receipt. For a hotel:
- Advance receipt triggers GST liability at the time of the advance, at the applicable slab. A receipt voucher is issued, and the tax is reported in GSTR-1 as an advance.
- Final invoice at check-in raises a tax invoice for the full stay value, and the advance and its GST are adjusted against the invoice through the GSTR-1 advance-adjustment table.
- Refundable security deposit is not consideration for a supply and does not trigger GST on receipt.
- Cancellation with refund requires reversing the advance GST through a refund voucher and reflecting it in GSTR-1 advance-and-adjustment for the relevant period.
This timing is unchanged by the new Income Tax Act 2025 — Section 13 of the CGST Act and CARO 2020 continue to govern. Practitioner guidance from the Institute of Chartered Accountants of India (ICAI) on CARO 2020 implementation covers the deposit-payable disclosure expectations.
Refundable Security Deposit Treatment
A refundable security deposit is a balance-sheet liability and stays there until it is refunded or forfeited. The PMS holds it against the guest folio with the receipt reference; the accounting system holds it in a separate liability account distinct from advance-against-room-charges. At checkout, the deposit either refunds in full (debit liability, credit bank or card refund) or partially refunds with the balance applied to incidental damage charges (debit liability, credit revenue for the consumed portion plus output GST, credit bank for the residual refund).
CARO 2020 audit reviewers age the deposit-payable balance. Stale balances — guests checked out months ago with no refund executed — draw audit comments. Properties need a monthly ageing review and a documented retention or refund attempt for every open balance.
No-Show Charge Reconciliation
When a confirmed guest does not arrive and no cancellation was logged, the hotel runs the no-show flow during night audit. The contracted no-show charge — typically one night’s room rate — goes against the credit card on file or against any advance held. The booking moves from arrival-pending to no-show in the PMS, the room is released for resale, and a tax invoice for the no-show charge is raised in the guest’s name at the room-tariff GST slab.
For OTA bookings on the prepaid model, the no-show charge is usually retained from the OTA’s prepayment to the hotel; for direct bookings with credit card on file, the charge is processed through the gateway and shows up on the next day’s terminal batch. Reconciliation has to type the no-show as NO_SHOW_CHARGE separately from regular room revenue so the ageing of cancellation rates and no-show rates is visible at the property level.
Cancellation and Refund Flow
Cancellation policy typically runs in slabs:
- Cancelled outside seven days from arrival — full refund of advance.
- Cancelled three to seven days from arrival — partial refund (often 50 percent or one-night retention).
- Cancelled inside 48 hours — zero refund, advance retained as cancellation revenue or held against no-show.
Refund execution debits the advance liability, credits the bank or card refund, and reverses the advance GST through a refund voucher reflected in GSTR-1 advance-and-adjustment. Reconciliation tracks each cancellation against the original receipt UTR or card transaction, the refund debit in the bank, and the GST reversal entry in the return for the period.
OTA Virtual-Card Pre-Auth Timing
For OTA bookings paid through a virtual card the hotel charges on arrival, the pre-auth is not a receipt and does not trigger GST. The actual charge happens at check-in or at no-show, and that charge is the receipt event. Reconciliation has to distinguish pre-auth-only from charged, because a pre-auth that lapses without conversion never appears in the bank statement and should never sit on the deposit ledger as cash. See the Hotel OTA virtual card reconciliation peer article for the full virtual-card reconciliation pattern.
PMS Deposit Ledger Versus Accounting AR and AP
The PMS deposit ledger holds the operational view — every receipt, its type, the related folio or event, the bank or card credit. The accounting system holds the financial view — separate liability accounts for refundable deposits and advances against room charges, AR for outstanding folios, AP for refunds pending. The two views must reconcile.
| Receipt class | PMS ledger | Accounting account | GST on receipt |
|---|---|---|---|
| Refundable security deposit | Deposit ledger, type SECURITY | Balance-sheet liability (separate) | No |
| Advance against room charges | Deposit ledger, type ADVANCE | Advance-from-guest liability | Yes, at room-tariff slab |
| No-show charge | Folio, type NO_SHOW | Revenue plus output GST | Yes, at room-tariff slab |
| OTA virtual card pre-auth | Pending charges, type VC_PREAUTH | None until charged | No until charged |
| OTA virtual card charge | Folio, type VC_CHARGE | Revenue plus output GST | Yes, at room-tariff slab |
The reconciliation walks each receipt class through PMS to accounting and then to bank, classifying any gap.
What Automated Deposit Reconciliation Changes
A platform that types every receipt at ingest carries REFUNDABLE_SECURITY_DEPOSIT, DEPOSIT_AGAINST_ROOM_CHARGES, NO_SHOW_CHARGE, and OTA_VIRTUAL_CARD as first-class concepts. The GST timing rule under Section 13 of the CGST Act applies automatically — advance receipt triggers tax, security deposit does not. Cancellation refunds emit refund vouchers and reflect in GSTR-1 advance-and-adjustment in the right return period, so refunds that cross periods do not leave open advance lines. Deposit-payable ageing is generated continuously, so CARO 2020 audit reviewers see clean evidence rather than a year-end scramble. Hotels that move from spreadsheet-based deposit tracking to structured matching close cancellation refund cycles materially faster, and the deposit ledger reconciles to the bank cleanly every period. Read the Hotel reconciliation in India pillar for the wider payment-mix taxonomy, and the Banquet event advance reconciliation peer for the same Section 13 timing applied to event advances. Finance teams running payment gateway reconciliation for the gateway side of refunds and reconciliation software India for the broader stack converge on the same pattern — typed receipt classes are what make deposit and refund evidence audit-defensible. For the broader hotel industry reconciliation surface, see the Hotels & Hospitality industry guide.