The hotel night audit in India: what it is, what it should catch, and how to do it in 30 minutes.

What the night audit actually does — and why it matters

The night audit is the process of closing the current business day, posting all outstanding room charges, reconciling payments against bookings, verifying GST calculations, and producing the financial reports that start the next day's operations with a clean, accurate baseline.

It typically happens between midnight and 6am — after the last late check-ins and before the first early check-outs. The person conducting it (the night auditor, or in smaller Indian hotels, a front desk team member on the night shift) is essentially closing the hotel's accounts for the day.

Why it matters: every financial discrepancy that is not caught in the night audit compounds. A room charge that was not posted on Tuesday will either be lost or cause a billing dispute at checkout on Wednesday. A GST calculation error that goes undetected for a week is a week of incorrect tax liability. The night audit is the safety net that catches errors before they become problems.

The 10-step night audit checklist for Indian hotels

1. Verify no-shows and update inventory: For every reservation marked as "expected arrival" that did not check in, update the room status to no-show, apply the no-show charge per the booking policy, and release the room for same-night walk-ins if applicable.
2. Post room charges for all in-house guests: Automatically post the room rate for the current night to every occupied room folio. In a modern PMS, this is a single action. In older systems, it may require manual posting per room.
3. Post tax: Apply the correct GST slab (12% on rooms priced Rs 1,000-7,499, 18% on rooms priced Rs 7,500+) to each room charge posted. Verify that tariff-based slab assignment is correct — room charges should apply GST on the declared tariff, not the discounted rate actually charged.
4. Reconcile OTA bookings: Match every OTA booking that checked in against the corresponding entry in the channel manager. Any booking present in the PMS but not in the channel manager report (or vice versa) is a reconciliation discrepancy requiring investigation.
5. Reconcile payments: Match every payment recorded in the PMS against the payment gateway settlement report (Razorpay, UPI, card terminal). Any PMS payment without a matching gateway transaction, or gateway transaction without a PMS record, is a discrepancy.
6. Check outstanding folios: Review all folios with open balances — guests who have not pre-paid or who have running charges (room service, restaurant, etc.) that have not been settled. Flag any folio where the outstanding balance exceeds the credit card authorisation or deposit held.
7. Verify room status against housekeeping: Confirm that every room shown as "occupied" in the PMS has a corresponding check-in record. Any room showing occupied without a guest record is an inventory discrepancy.
8. Run the daily revenue report: Generate the daily summary showing room revenue, F&B revenue, other revenue, and total revenue by segment. Compare against the same date last week and last month to flag unusual variances.
9. Close the business day: Mark the business day as closed in the PMS, preventing further postings to the closed date. This is the formal end of the night audit.
10. Distribute reports: Send the daily revenue report, occupancy report, and any discrepancy summary to the GM and owner. Most modern PMS systems do this automatically via email at the close of audit.

Common night audit discrepancies and how to catch them

Understated room revenue: A room that was sold at Rs 4,800 but posted at Rs 4,500 because a manual rate change was entered incorrectly. Caught by: comparing posted room charges against reservation rate cards during the audit.

Missing tax posting: A room charge posted without the corresponding GST, often due to a tax configuration error in the PMS or a manually entered rate that bypassed the tax calculation. Caught by: verifying that every room revenue posting has a corresponding tax line of the correct amount.

OTA booking not imported: A booking that arrived on MakeMyTrip after the channel manager sync and was not manually entered into the PMS. The room is occupied but the folio is missing. Caught by: comparing room status (occupied) against folio records (should have one per occupied room).

Payment without folio entry: A guest who paid at the restaurant by card, and the payment was processed by the POS but never transferred to the room folio. The payment gateway shows the transaction; the folio does not. Caught by: POS-to-folio reconciliation as part of the F&B close.

GST compliance in the night audit

The night audit is the last opportunity to catch GST errors before they are embedded in finalised folios. The three most common GST errors in Indian hotel night audits:

• Wrong slab applied: A room with a declared tariff of Rs 7,600 (18% GST) is applying 12% GST because the tariff was entered as Rs 7,400 in the PMS. The difference: Rs 456 per night in incorrectly collected tax. Caught by: auditing room tariff configurations quarterly.
• IGST vs SGST/CGST error: A domestic guest from another state should generate IGST (single integrated tax), not the SGST+CGST split applied to intrastate transactions. Some PMS systems apply the wrong split if the guest's billing state is not correctly captured. Caught by: verifying billing state capture on corporate folios during the audit.
• F&B GST applied to room revenue: A restaurant charge that was posted to the room folio at the restaurant GST rate (5%) instead of being kept separate from the accommodation GST. Caught by: reviewing all folio lines where F&B charges appear alongside room charges.

How long a night audit should take in 2026

A hotel running a modern cloud PMS with automated charge posting, OTA sync, and payment reconciliation should complete the night audit in 20-40 minutes. A hotel running legacy software with manual charge posting and spreadsheet reconciliation typically takes 90 minutes to 3 hours.

The time difference is not about the complexity of the audit — it is about how much of it is manual. Every step that requires a human to enter data from one system into another (copying OTA booking confirmations into the PMS, manually posting room charges, entering payment totals from a terminal printout into a spreadsheet) adds time and introduces error opportunities.

Automating the night audit — what changes and what stays manual

A modern PMS automates: room charge posting, tax calculation and posting, OTA booking import, and report generation. The auditor's role shifts from data entry to exception review — looking at what the system flagged as unusual rather than generating every record manually.

What stays manual (and should): review of discrepancies flagged by the system, investigation of any no-show charges where guest communication may change the outcome, and the final sign-off that confirms the business day is accurate before closing. Human judgment on exceptions is irreplaceable. Human data entry of routine transactions is not.