Closing a cashier shift at hotel reception involves more than counting the drawer and entering a total. Cash, card, foreign-currency, refund and paid-out transactions should be compared with their respective sources, and any variance explained before close. A well-designed closing process leaves the next shift a traceable chain of transactions, not just a number.

What you will learn in this article
  • Cashier shift close and PMS business-day close are not the same process; track each with its own status and responsible user.
  • Do not combine cash, card and foreign currency into a single total; compare each system balance with its physical or external source separately.
  • A cashier variance should not be hidden with a silent adjustment; the amount, reason, user, approval and reversing transaction must remain in the audit trail.

Separate cashier shift close from business-day close

A cashier shift covers the financial transactions made by a specific user or cashier ID from opening to close. Night audit is the broader process that advances the property's business date. Closing a cashier does not necessarily sign the employee out, while entering another payment may require reopening the cashier. This distinction prevents cashier close and business-day close from being treated as the same event.

Oracle OPERA Cloud's current cashier-closing documentation describes reviewing shift activity, viewing the closing balance, confirming shift-drop amounts and producing reports within one cashier session. Screen names may differ in RoomFollow or another PMS, but employees should see the business date, cashier ID and opening balance before closing.

  • The active PMS business date and the shift date-and-time range were verified.
  • The cashier ID was matched to the user who processed the transactions.
  • The opening balance and cash float were shown separately.
  • The team knows the rule for entering transactions after cashier close.

Count physical cash independently of the system total

Where possible, count drawer cash in a controlled, interruption-free area without first looking at the system's expected amount. Recording separate counts for banknote and coin denominations makes counting errors easier to locate. Keep the opening float, cash received from guests and the amount to be handed over to the bank or safe separate.

Some systems use a blind count or blind cash drop: the employee enters the physical amount before seeing the difference from the expected balance. Oracle documents that this behavior depends on property configuration. Even without blind counting, the team can finish the physical count before comparing it with the PMS total so the expected figure does not influence the count.

  • The cash drawer was counted only with authorized employees.
  • Denomination counts and the actual cash total were recorded.
  • The opening float was separated from cash received during the shift.
  • Any required deposit envelope or bag number was added to the record.

Reconcile PMS transactions by document and transaction type

The total on a cashier report does not identify which transaction is wrong. Review cash payments, cash refunds, paid-outs, deposits, account receipts and exchange differences by transaction code. If a transaction was voided or reversed, the original and correcting entries should be traceable together. Deleting a record may appear to fix the total, but it breaks the audit trail.

Oracle's financial report catalog can report cashier audits, payment transactions and same-day corrections or voids separately. This does not mean every hotel must use identical report names. The essential control is that every variance can be traced by transaction time, user, folio or document reference and its corresponding entry.

  • Cash inflows and outflows were checked as separate transaction types.
  • Refunds, paid-outs and reversing entries matched their document references.
  • Deposit and revenue transactions were kept separate.
  • Traceable correcting entries were used instead of deleting records.

Do not compare POS totals only with the PMS balance

For card payments, the PMS, POS terminal and bank or payment provider may show the same transaction at different times. At shift close, total PMS card transactions by payment type and currency, then compare them with each terminal's end-of-day or subtotal report. A single combined total can hide a payment posted to the wrong terminal or a duplicate charge.

Transactions authorized but not posted to the PMS, posted to the PMS but declined by the POS, or later voided should be placed on a separate follow-up list. Copying a full card number into a shift note or report is not a solution. PCI SSC explicitly requires card numbers to be masked on screens and reports and prohibits storing sensitive authentication data such as CVV after authorization.

  • Each POS terminal and payment type was compared separately.
  • Approved, declined, voided and refunded transactions were separated.
  • Pending PMS-to-POS items were assigned to an owner.
  • Card data was masked in reports and notes; CVV was not recorded.

Close foreign-currency cash by currency

Count foreign-currency payments such as EUR, USD or GBP in their original currency first. Looking for a difference only in the local-currency equivalent can hide an incorrect rate, currency or denomination. The physical foreign-currency amount, PMS transaction, applied rate and local-currency equivalent should appear in separate fields.

Oracle's cashier reports treat foreign-currency transactions as a separate report type. Even if the property does not buy or sell currency and accepts it only for accommodation payments, document which rate was used for each date and business day. During close, explain the source of a variance rather than silently replacing a historical transaction's rate with a new one.

  • Each currency was counted separately in its physical amount.
  • The exchange-rate date, source and applied value were checked.
  • The foreign-currency amount and local-currency equivalent were reported together.
  • Exchange-rate differences and actual cashier variances were tracked as separate causes.

Do not hide a cashier variance—explain it

If the actual amount does not match the expected amount, count again first. Then investigate an incorrect payment type, missing posting, duplicate transaction, wrong currency, unrecorded paid-out or shift handover. Adding an unexplained income or expense line to force the cashier to balance does not resolve the variance; it only makes the real cause harder to find.

If the discrepancy cannot be resolved, apply the property's tolerance and approval rules. Record the amount, debit or credit direction, currency, likely cause, reviewer and manager approval. Oracle's cashier configuration documentation explains that differences between actual and system amounts can be tracked cumulatively. This makes it easier to identify repeated small variances that may indicate a training or process issue.

  • A second count and transaction-detail review were completed for the discrepancy.
  • Possible incorrect payment types and currencies were investigated.
  • No unauthorized balancing entry was created.
  • The unresolved variance was recorded with its amount, reason and approval details.

Make the closing report part of shift handover

After reconciliation, record the actual handover amount, destination and any bag or envelope number. The cashier closing report should summarize cash, cards, other payments, foreign currency and variances, while detailed transaction reports remain reproducible when needed. Oracle's official guide documents that historical closing reports can be regenerated by closing date, cashier ID and close number.

Instead of telling the next shift that the cashier is simply complete, record any outstanding POS reconciliation, expected refund, unresolved variance or bank-deposit status in a short handover note. The report should also show who created and received it, so accountability is not lost in a shared user account.

  • The report includes the close number, cashier ID and date.
  • The actual handover amount and recipient were recorded.
  • Outstanding financial follow-ups were handed over to the next shift.
  • Historical reports can be reproduced without alteration.

Hotel cashier shift closing checklist

Adapt this list to the property's payment methods, user roles and accounting procedures. A daily cashier close does not replace statutory accounting records, bank reconciliation or the PMS business-day close.

  • The business date, shift range, cashier ID and opening balance were verified.
  • Cash was counted by denomination; the cash float was kept separate.
  • Cash receipts, refunds, paid-outs and adjustments matched their supporting documents.
  • Each POS terminal, payment type and currency was reconciled separately.
  • Foreign currency was checked by physical amount, exchange rate and local-currency equivalent.
  • The cashier variance was reviewed with a second count and transaction check.
  • The unresolved variance was logged with authorization, reason and approval details.
  • The handover amount, recipient and bag or envelope reference were recorded.
  • The closing report was generated and outstanding items were handed over to the next shift.
Short answers

FAQ

Does closing a cashier shift also close the business day?

No. Closing a cashier shift ends a specific cashier user's financial session; night audit is a separate process that advances the PMS business date. Permissions and process order can be configured by property.

Can the cashier be closed if the POS total does not match the PMS?

It depends on the property's approval rules. First review approved, declined, voided and refunded transactions by terminal; record any unresolved variance with its amount, reason, user and follow-up owner.

Can a manual income or expense be posted for a cashier variance?

Only do so when the property's defined permissions and accounting procedure require it, using the correct transaction code and explanation. Do not use an unexplained balancing entry that makes the variance invisible.

Sources and updates

Operational recommendations should be adapted to the property's own conditions. PMS and cashiering details were checked against the following official documents on 17 September 2026.