Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian hotels close the PMS day every 24 hours through a night-audit routine that has to roll three shifts forward, post room and tax, close F&B and banquet sub-systems, settle minibar and no-show, square the cash float, and bridge to the bank deposit slip plus card terminal batch plus UPI settlement — all before the system date rolls and the prior day locks. Manual checklist execution leaves five recurring exception classes uncleared, which compound into month-end variances accounting cannot reconcile.
Run the close in a fixed sequence — PMS day-close (room and tax), F&B daily-Z per outlet, banquet daily settlement against event register, minibar postings, no-show charges, pending arrivals and departures, float verification — then bridge gross PMS revenue to the bank deposit slip, the credit-card terminal batch (net of MDR and GST on MDR), and the UPI or QR daily settlement. Classify residual gaps as cash short or over, unposted F&B charge, MINIBAR_LATE_POST, settled-but-uncharged, or partial folio.
PMS adapter for Opera or IDS Next or eZee or Hotelogix exposing the day-close sequence and exception list, F&B POS connectors emitting daily-Z totals, banquet event register feed, housekeeping minibar feed, front-desk cash float reconciliation, card terminal batch importer, UPI or QR settlement importer, and a property-level cut-off time that controls the operating day boundary.
A closed PMS day with the system date rolled, every exception class typed and routed for follow-up, a cash-and-card-and-UPI bridge that ties gross PMS revenue to net bank credits across the relevant settlement days, and an opening balance carried forward cleanly so that the next day's audit starts from a reconciled position.
A 180-key business hotel in Hyderabad runs three front-office shifts — morning 7 a.m. to 3 p.m., evening 3 p.m. to 11 p.m., night 11 p.m. to 7 a.m. — and the night auditor inherits everything the previous two shifts could not close. Between midnight and 6 a.m., before the system date rolls, the auditor has to post room and tax to every in-house folio, close five F&B outlets on daily-Z, settle the previous day’s banquet event, post the minibar charges housekeeping flagged after guest checkout, charge the three no-shows against cards on file, clear pending arrivals and departures, verify the front-desk cash float, and bridge the day’s gross revenue to the bank deposit slip, the card terminal batch, and the UPI daily settlement. Hotel night audit close reconciliation is the discipline that makes all of that auditable. This article is for night auditors, front-office managers, and hotel finance teams running daily close at Indian properties.
What Hotel Night Audit Close Reconciliation Involves
Night audit is the daily property-level close in the PMS, run in the lowest-occupancy window so that the system can briefly lock for posting. The auditor executes a fixed sequence — post room and tax, close F&B sub-systems, settle banquet, post minibar and no-show, clear pending folios, verify float, and roll the business date. Once the date rolls, the prior day is locked for posting and any late charge moves to a current-day adjustment with a back-reference to the original folio.
The discipline matters because the bank deposit slip the next morning, the credit-card terminal batch settling on T+1 or T+2, and the UPI or QR daily settlement summary all reference revenue the PMS has already booked to the previous day. If the close is sloppy, the bridge from PMS gross to bank net never closes, and month-end accounting inherits a backlog of unreconciled folios that auditors will flag under CARO 2020.
The Three-Shift Roll-Over
Hotels run three shifts of front-office staff. Each shift hands a tray of work to the next:
- Morning to evening — open arrivals, pending billing for guests still in-house, and any daily-Z that the morning F&B shift could not close.
- Evening to night — late-arriving guests with deposit holds, banquet event handover for the day’s function, room-service late-night runs, and any walk-ins.
- Night to morning — the night auditor is the terminal handler. By the time the morning shift relieves at 7 a.m., the system date has rolled, the previous day’s revenue is finalised, and the cash float is squared.
The Night Audit Checklist
The full checklist runs ten to fifteen items at a typical mid-scale property. The non-negotiable steps are:
- PMS day-close — post room rate plus applicable GST to every occupied folio, run the day’s revenue report, and confirm system totals match outlet sub-totals.
- F&B outlet daily-Z — close each restaurant and bar POS terminal, generate the Z-report, and reconcile each outlet’s gross to its room-charge transfers and cash and card receipts.
- Banquet daily settlement — for events that closed during the day, post the final folio to the master and reconcile the day’s banquet receipts against the event register.
- Minibar postings — pick up the housekeeping minibar consumption sheet for guests who checked out and post the charges before the system date rolls.
- No-show charges — for confirmed reservations that did not arrive, charge the contracted no-show amount (typically one night room rate) to the credit card on file or against the held advance.
- Pending arrivals and departures — clear in-house guests still showing as arrival or departure pending, and decide rolled or cancelled status before the date roll.
- Deposit and float verification — reconcile the front-desk cash drawer to the system-expected cash, including float carried forward.
- Bank deposit and terminal batch — prepare the next-morning bank deposit slip, generate the card-terminal end-of-day batch summary, and pull the UPI or QR daily settlement summary.
PMS Systems and Their Close Routines
| PMS | Close routine highlights |
|---|---|
| Oracle Opera | Enterprise-grade close with detailed exception list, multi-property roll-up, audit trail per posting |
| IDS Next | Indian-market PMS with full F&B integration, banquet module, GST-aware posting |
| eZee Absolute | Cloud-native close routine, channel-manager sync at close |
| Hotelogix | Cloud PMS with simplified close for mid-scale and small properties |
Each PMS exposes the same conceptual sequence — post, close, roll — but the specific exception list and the night-audit report formats differ. Reconciliation tooling that reads the close output has to handle the platform-specific schema for each.
Reconciling Against External Settlements
Once the PMS day is closed, three external settlement views must reconcile to the gross revenue figure:
- Bank deposit slip — physical cash deposited the next working day, net of any cash short or over at the float.
- Credit-card terminal batch — card receipts settled on T+1 or T+2 net of MDR and net of GST on MDR. The terminal batch reference becomes the link between the day’s card folios and the eventual bank credit.
- UPI and QR daily settlement — the gateway summary for QR codes at the front desk, F&B counters, and banquet billing, settled on the gateway’s own cycle.
The bridge is: PMS gross room revenue plus F&B plus banquet plus minibar plus no-show, minus cash deposited the next day, minus card-batch net (after MDR), minus UPI settlement, equals zero — when correctly reconciled. Anything left over is an exception.
Exception Classes
Five exception classes recur at every Indian property and have to be typed for follow-up:
- CASH_SHORT_OVER — front-desk float versus system-expected cash variance.
- UNPOSTED_FB_CHARGE — a guest signed for a restaurant bill, the transfer to the room-folio never executed.
- MINIBAR_LATE_POST — housekeeping inspected after the guest checked out, the minibar charge missed the close.
- SETTLED_BUT_UNCHARGED — payment received without the corresponding charge being posted, leaving an open credit on the folio.
- PARTIAL_FOLIO — some charges hit the master and others the room, typically a routing-rule misconfiguration.
For PSU and corporate-account properties, see also the Federation of Hotel & Restaurant Associations of India (FHRAI) operational guidance on close-routine documentation expected during statutory audit.
System Close Versus Accounting Close
The PMS system close happens daily — every operating day rolls forward at the night-audit cut-off. The accounting close happens monthly — trial balance, GST returns, TDS reconciliation against Form 26AS. These are different exercises operating on different cadences. The opening balance carried forward in the PMS at each daily close becomes the input to the monthly accounting close, and any uncleared exception in the PMS daily ledger compounds into a month-end variance. Properties that run sloppy daily closes end month-end with a backlog that takes finance teams three to five staff days to untangle.
What Automated Night Audit Reconciliation Changes
A platform that reads PMS close exports and bridges them to the bank deposit slip, the card terminal batch, and the UPI settlement carries the five exception classes as first-class concepts. The CASH_SHORT_OVER, UNPOSTED_FB_CHARGE, MINIBAR_LATE_POST, SETTLED_BUT_UNCHARGED, and PARTIAL_FOLIO codes are typed at ingest, routed to the right roles for clearance, and rolled forward only when explicitly cleared. Hotels that move from spreadsheet-based daily close summaries to structured matching typically see the morning hand-over from night auditor to front-office manager arrive with zero open exceptions, and month-end accounting close compress materially because the daily ledger never carries an unexplained gap. Finance teams running bank reconciliation software India for the deposit-slip side and broader reconciliation software India for the OTA, gateway, and corporate streams converge on the same pattern — typed exceptions cleared at the daily boundary keep the property’s revenue auditable. Read the Hotel reconciliation in India pillar for the wider payment-mix taxonomy that the night-audit close feeds. For the broader hotel industry reconciliation surface, see the Hotels & Hospitality industry guide.