Guest Accounting, Cashiering and Night Audit

Introduction

Guest accounting is the financial control system through which a hotel records, classifies, authorizes, settles and reports every monetary transaction associated with a guest, company, group or other account. It connects reservations, rooms, food and beverage, retail outlets, telephone services, transport, banquets, payment services and the general ledger. Although the front office often performs the visible work, guest accounting is a cross-functional responsibility involving reception, cashiering, revenue management, outlets, finance, information technology and management.

The central accounting record is the guest folio. A folio is not merely a bill; it is an auditable chronological statement of charges, credits, adjustments, taxes, payments and the outstanding balance. Effective control ensures that revenue is neither omitted nor duplicated, that credit exposure remains within approved limits, that departures are settled correctly, and that operational systems reconcile with financial records.

Night audit is the structured end-of-day procedure that validates transactions, closes the hotel’s business date, produces management information and prepares the property-management system for the next operating day. In a modern hotel, the night auditor is simultaneously a cashier, reconciler, exception analyst and control officer.

Learning Objectives

After studying this chapter, the learner should be able to:

1. Explain the structure and purpose of guest and non-guest folios.
2. Control postings, corrections, allowances, paid-outs and foreign-currency transactions.
3. Calculate balances, credit exposure, taxes and settlement amounts accurately.
4. Apply controls to cash, cards, company accounts, chargebacks and departures.
5. Conduct a systematic night audit and reconcile interfaces.
6. Interpret operational and financial reports for managerial decisions.
7. Evaluate ethical, legal, technological and governance risks in guest accounting.

1. The Accounting Architecture of a Hotel

1.1 Accounts, folios and ledgers

A guest account records the financial relationship with a customer. A folio is the detailed transaction statement for that account. A ledger is a collection or control summary of accounts. Common folio categories include:

A folio normally contains the account name, room or reference number, arrival and departure dates, rate, tax status, transaction date, posting date, description, reference number, debit, credit and running balance. The distinction between transaction date and posting date is important. A service may be consumed on one business date but entered later because of an interface delay or correction. Such differences must be documented rather than concealed.

1.2 Debits, credits and the running balance

In hotel front-office practice, a debit generally increases the amount owed by the guest, while a credit reduces it. The operational balance can be expressed as:

where B₀ is the opening balance, D is total debits or charges, C is total credits such as payments and allowances, and B₁ is the closing balance. All terms must be expressed in the same currency and for the same account and business period. A negative balance usually indicates a credit in favour of the guest or an unapplied deposit.

For a folio containing room charges, outlet charges, taxes, payments and adjustments:

Here, R represents room and package charges, O other service charges, T taxes, X approved miscellaneous debits, P payments, A allowances or credits, and D_p paid-outs or other credits paid on behalf of the guest. The expression is a classification framework, not a substitute for the hotel’s accounting policy. Tax treatment, service charges and paid-outs vary by jurisdiction and must follow law and policy.

1.3 Transaction integrity

Every posting should answer five questions: What was purchased? When was it supplied? To which account does it belong? Who authorized it? What evidence supports it? Source documents may include signed checks, electronic point-of-sale records, vouchers, authorization forms, receipts, folio notes and system audit trails.

A reliable posting has four characteristics:

• Accuracy: amount, tax, currency, department and account are correct.
• Completeness: all valid revenue and payments are recorded.
• Timeliness: the posting is made in the correct business period.
• Traceability: a reviewer can identify the originator, approver and correction history.

2. Posting Controls, Corrections and Allowances

2.1 Automated and manual postings

Room and tax postings may be generated by the property-management system during night audit. Restaurant, minibar, spa, telephone and retail charges may arrive from point-of-sale or other interfaces. Manual postings are appropriate when an interface fails, when a legitimate transaction originates outside an integrated system, or when an authorized correction is required. Manual entry is a higher-risk activity and should require reason codes, supporting documentation and user identification.

The front office should distinguish between a correction, which removes or reverses an incorrectly posted transaction, and an allowance, which grants an approved reduction because of service recovery, a price concession, a disputed service or a policy-based adjustment. A correction should normally reference the original transaction. An allowance should identify the reason, authority level and recipient of the benefit.

2.2 Voids, reversals and transfers

A void usually cancels a transaction before final settlement or posting closure. A reversal offsets an already posted transaction while retaining an audit trail. A transfer moves a charge from one folio to another, such as transferring approved group accommodation to a master folio. Deleting a transaction without an audit record is unacceptable because it destroys evidence and may conceal fraud.

Controls should include sequential receipt numbers, separation of posting and approval rights, daily review of adjustments, restricted access to backdated postings, and exception reports for unusually large or frequent allowances.

2.3 Package rates and tax allocation

A package rate may include accommodation, breakfast, meals or activities. For revenue reporting, the total rate often must be allocated among departments. If a package price is P and the approved allocation proportions are w₁, w₂, …, w_n, then:

where P_i is the allocated value for component i, and the proportions must satisfy:

This allocation is applicable only where the hotel’s accounting policy and tax rules permit the stated method. Rounding differences should be assigned consistently, normally to a designated component, so that the sum of allocations equals the package price.

3. Cashiering and Payment Security

3.1 Cashier accountability

A cashier operates a controlled bank, normally consisting of an opening float plus transactions received during the shift. At closing, the cashier counts physical cash and prepares a settlement. The basic control relationship is:

The cash variance is:

A positive variance is an overage and a negative variance is a shortage. The formula assumes that all cash receipts, paid-outs and refunds have been recorded and that the opening float is not treated as revenue. Every variance should be counted independently, recorded, investigated and approved according to policy.

Cash should be counted away from public view, stored securely, and transferred through documented dual-control procedures. A cashier must not use unrecorded personal funds to conceal a shortage or remove an overage without authorization.

3.2 Card payments and electronic settlement

A card transaction requires authorization, correct folio reference, appropriate guest verification and secure handling of payment data. Authorization confirms that a transaction is approved at that moment; it does not always guarantee final settlement. Hotels should distinguish authorization, capture, settlement, refund and chargeback.

The hotel must never retain sensitive card data outside approved systems. Staff should comply with payment-card security standards, use tokenized or approved terminals, restrict access, and avoid recording full card numbers or security codes in notes.

3.3 Credit limits and exposure

Credit control prevents the guest or account from accumulating an unacceptable unpaid balance. A simple exposure measure is:

The formula assumes that pending charges are reasonably estimated and that approved security, such as a valid deposit or card authorization, is legally and operationally available. A credit exception occurs when exposure exceeds the approved limit or when payment validity is doubtful.

For example, if the current balance is 1,850 monetary units, anticipated charges are 420, and approved security is 1,000, exposure is 1,270 monetary units. If the approved limit is 1,200, the account exceeds the limit by 70. The response may include a new authorization, deposit request, management approval, reduction of unsecured services or immediate settlement. Staff must apply the policy consistently and respectfully; credit control must not become discriminatory treatment.

3.4 Paid-outs and refunds

A paid-out is money disbursed by the hotel on behalf of a guest, such as a taxi payment, postage expense or emergency purchase. It should be supported by a receipt, guest authorization and clear account posting. A paid-out is not hotel revenue. Depending on policy, the hotel may charge a service fee, which must be separately identified.

Refunds require evidence that the original payment was received, the refund is authorized and the recipient is verified. Refunds to cards should normally return through the original payment channel unless law and payment rules permit another method.

4. Foreign Currency and Multi-Currency Control

Hotels serving international guests may accept foreign currency, but the transaction must distinguish the currency received from the hotel’s reporting currency. If an amount F in foreign currency is converted at a rate r expressed as reporting-currency units per foreign-currency unit, then:

For example, 200 foreign units at a rate of 0.92 reporting units per foreign unit equals 184 reporting units. The rate must be the approved rate for the relevant date or transaction, and the same rate convention must be used throughout the calculation.

A hotel should publish or securely communicate its exchange rate, record currency codes, retain the conversion evidence, and explain commissions or service charges. Cash received must be checked for authenticity. Differences between the rate offered to guests and the rate used for bank settlement should be reported as foreign-exchange gain or loss under the hotel’s accounting policy. Staff should not exchange currency informally or use personal rates.

5. Settlement, Departures and Chargebacks

5.1 Departure control

Departure is an accounting event as well as a room-status event. Before finalizing a folio, the cashier should confirm:

1. all outlet and interface charges have arrived;
2. room, tax and package postings are correct;
3. discounts, allowances and transfers are authorized;
4. the payment method is valid and sufficient;
5. deposits and prepayments are applied correctly;
6. the guest has received or can access the final statement;
7. any balance transferred to city ledger has documented approval.

Express check-out is efficient only when authorization, folio review and post-departure controls are reliable. A hotel should not treat speed as a reason to weaken settlement controls.

5.2 Settlement methods

Common settlement methods include cash, card, electronic transfer, approved direct billing, travel-agent voucher, digital wallet and mixed tender. Mixed tender requires careful sequencing: each payment must be posted separately, the total must equal the amount due, and refunds must respect the original tender rules.

The final balance should be zero unless it is legitimately transferred to an approved receivable account or remains as a documented guest credit. Unexplained balances are exceptions, not normal outcomes.

5.3 Chargebacks and disputes

A chargeback occurs when a cardholder or issuer reverses a transaction after settlement. The hotel should maintain a dispute file containing the folio, signed or electronic evidence, authorization record, invoice, cancellation policy, correspondence and proof of service. Prevention depends on accurate descriptors, clear policies, documented authorization, secure payment processes and prompt response to disputes.

Chargebacks reveal a tension between operational evidence and customer experience. A hotel may have technically valid evidence but still face reputational harm if its cancellation or billing communication was unclear. Therefore, chargeback management should be both defensive and preventive.

6. Night Audit: Purpose and Method

Night audit closes one hotel business date and opens another. The exact sequence depends on the property-management system, but the control logic is broadly consistent.

6.1 Pre-audit preparation

The auditor confirms that the business date is correct, verifies that departments have closed their points of sale, checks unresolved cashier sessions, reviews arrivals, departures, no-shows, room moves and open folios, and confirms that interfaces are available. A system backup or recovery procedure should be in place according to organizational policy.

6.2 Transaction and interface reconciliation

The auditor compares source totals with interface totals. For a department:

A zero variance is desirable, but a non-zero result is not automatically an error. Timing differences, rejected transactions, tax mapping, rounding, duplicate prevention and offline postings may explain it. Each variance requires classification and documented resolution.

Examples of interfaces include point-of-sale, telephone, minibar, spa, payment gateway, channel manager and accounting system. Reconciliation should identify transmission status, rejected records, duplicate records, unposted items and transactions posted to the wrong account.

6.3 Room and tax audit

The auditor verifies occupied rooms, vacant rooms, complimentary rooms, house-use rooms, no-shows, rate changes, extensions and room status differences. The expected room revenue can be compared with the room postings, subject to packages, discounts, complimentary treatment and taxation rules. A room-status discrepancy is operationally significant because it may affect both revenue and safety.

6.4 Posting recurring charges and closing the date

After exceptions are addressed, the system posts recurring room and tax charges, generates required reports, balances cashier activity, and closes the business date. The auditor must not force closure while material interface failures or unexplained financial differences remain unresolved. If closure is necessary because of a technical emergency, the exception must be escalated and logged.

6.5 Post-audit review

The next-day team receives reports and unresolved-item logs. The front-office manager reviews unusual adjustments, high balances, negative balances, no-show revenue, complimentary rooms, occupancy discrepancies, payment failures, refunds and chargebacks. Night audit is therefore a control cycle, not merely a software button.

A useful conceptual flow is:

Figure: Night audit as a sequential control cycle.

7. Reports and Managerial Interpretation

A report is useful only when its definitions, period, currency and source are understood. Important reports include:

Managers should interpret reports comparatively rather than in isolation. For example, a rise in average room revenue may reflect higher rates, a change in room mix, package allocation or fewer discounted bookings. A fall in cash collections may reflect greater card usage rather than weaker revenue. Report interpretation requires definitions, trend analysis, operational context and investigation of exceptions.

Useful indicators include average daily rate:

and occupancy:

These measures are meaningful only when rooms available, complimentary rooms, house use, out-of-order rooms and treatment of day-use rooms are defined consistently. They are operational performance indicators, not substitutes for profit analysis.

8. Governance, Ethics and Technology

Guest accounting involves personal, payment and sometimes sensitive travel information. Governance therefore requires least-privilege access, segregation of duties, strong authentication, audit logs, retention controls, incident response and compliance with applicable privacy, tax, employment and payment regulations.

Segregation of duties is especially important: the person who receives money should not independently approve a refund, erase an adjustment and reconcile the same transaction. Where staffing makes complete separation impossible, compensating managerial review and system restrictions are required.

Artificial intelligence can assist in anomaly detection, duplicate identification, cash-variance prediction, invoice classification and natural-language explanations of reports. However, AI outputs should be treated as alerts rather than accounting authority. A model may misclassify legitimate high-value events, reproduce historical bias or expose personal data. Human approval, explainability, access controls, validation and an appeal or correction process remain necessary.

Contemporary systems increasingly use cloud PMS platforms, integrated payment tokens, robotic reconciliation, real-time dashboards and mobile check-out. Integration improves speed but increases concentration risk: one incorrect rate table, tax mapping or interface rule can affect many transactions. Periodic independent reconciliation and controlled change management are therefore more important, not less.

Applied Case: The Unreconciled Group Departure

Background

This illustrative case concerns a 180-room city hotel hosting a three-day corporate conference. Accommodation charges were assigned to a master folio, while personal meals and minibar purchases remained on individual folios. The hotel used a PMS integrated with point-of-sale and a payment gateway.

Problem

At departure, the master folio was 2,400 monetary units higher than the organizer’s approved invoice. The night auditor also found six restaurant checks in the POS system marked as transmitted but absent from the PMS. Two individual guests had negative balances because deposits had been applied twice.

Analysis

The auditor first froze further manual adjustments and exported the PMS, POS and payment reports. The difference was decomposed into three categories:

• 1,500 units of legitimate banquet charges posted to the wrong individual folio;
• 900 units of restaurant charges rejected because of an invalid tax code;
• duplicate deposit applications totaling 2,400 units across two accounts, offsetting part of the apparent difference in a separate report.

The apparent master-folio discrepancy therefore could not be resolved by simply applying a 2,400-unit allowance. That would have hidden classification and interface errors.

Approach and solution

The hotel transferred the banquet charges to the approved master folio with documented authorization, corrected the tax mapping and reposted the six rejected checks, and reversed the duplicate deposit applications. A second employee reviewed the corrected folios. The organizer received a revised statement with supporting detail, while the two guests received corrected balances and explanations.

Management then changed the tax-code validation rule, added a pre-departure group-folio review, and introduced a night-audit exception report for transmitted-but-unposted transactions.

Outcome and learning points

The hotel collected the correct amount, preserved the audit trail and avoided an unjustified allowance. The case demonstrates that reconciliation must be analytical rather than merely arithmetic. A net-zero difference can conceal offsetting errors. Effective control requires transaction-level evidence, account ownership, interface monitoring and independent review.

Challenges and Limitations

Several limitations complicate guest accounting. Systems may operate with different business dates, currencies, tax rules and rounding conventions. Offline terminals can produce delayed transactions. Package rates can obscure departmental revenue. Automated controls may reject legitimate exceptions or accept incorrectly configured data. Small properties may lack adequate segregation of duties. Finally, pressure for rapid check-in and check-out can encourage shortcuts.

The appropriate response is risk-based control: identify high-value and high-risk transactions, automate routine validation, require human review for exceptions, document overrides and periodically test whether controls actually work. Controls should be proportionate, understandable and designed around real hotel operations.

Best-Practice Control Checklist

Before closing a business date, the responsible team should verify that:

• all cashier banks are settled and variances documented;
• all outlet and payment interfaces are reconciled;
• rejected, duplicate and pending transactions are listed;
• room, tax, package and allowance postings are reviewed;
• high-balance and over-limit accounts are addressed;
• departures and city-ledger transfers are authorized;
• refunds, paid-outs and foreign-currency transactions have evidence;
• reports use the correct business date and reporting currency;
• system access and audit trails remain available;
• unresolved exceptions are assigned to named owners and deadlines.

Chapter Summary

Guest accounting provides the financial discipline of front-office operations. Folios record debits, credits, taxes, payments, allowances and transfers, while ledgers aggregate individual and organizational accounts. Posting integrity depends on accuracy, completeness, timeliness and traceability. Cashiering requires controlled banks, documented settlement, secure payment handling and investigation of variances. Credit limits protect the hotel from excessive unsecured exposure, while paid-outs, refunds and foreign-currency transactions require authorization and evidence.

Departure control links the guest experience to financial closure. Chargeback management depends on both transaction evidence and clear customer communication. Night audit reconciles source systems, reviews exceptions, posts recurring charges, produces reports and closes the business date. Managers must interpret occupancy, ADR, revenue, cashier and receivable reports using consistent definitions. Technology and AI can strengthen controls, but governance, segregation of duties, privacy, human review and auditability remain essential.

Key Terms

Allowance: An authorized reduction or credit granted to a guest or account.

Audit trail: A record showing what transaction occurred, who performed it, when it occurred and how it was changed.

Chargeback: A payment reversal initiated through a card issuer or payment network.

City ledger: Approved receivable accounts transferred from the guest ledger after departure.

Credit limit: The maximum approved unsecured exposure for a guest or account.

Debit: A posting that generally increases the amount owed.

Folio: The detailed financial statement for a guest or account.

Guest ledger: Accounts of guests currently staying in the hotel.

House account: An internal or non-guest account used for authorized hotel activity.

Interface reconciliation: Comparison of source-system transactions with transactions received by another system.

Master folio: A folio used to consolidate approved group or event charges.

Night audit: End-of-business-date reconciliation, reporting and system-closing procedure.

Paid-out: Money disbursed by the hotel on behalf of a guest.

Posting: Entering a financial transaction into the appropriate account.

Reversal: An offsetting transaction that corrects a posted entry while retaining its history.

Settlement: Final payment or approved transfer of an account balance.

Source document: Evidence supporting a transaction, such as a receipt, voucher or signed check.

Variance: Difference between an expected amount and an actual amount.

Review Questions

Short Answer Questions

1. What is the difference between a folio and a ledger?
2. Why should a correction be distinguished from an allowance?
3. What controls are required for a cashier’s closing settlement?
4. What is the purpose of interface reconciliation during night audit?
5. Why is an audit trail important in guest accounting?

Long Answer Questions

1. Explain the complete night-audit process from pre-audit preparation to post-audit review.
2. Discuss the controls required for cash, card payments, paid-outs and refunds.
3. Explain how credit limits and exposure calculations support front-office risk management.
4. Analyse the accounting and operational issues created by package rates and departmental allocation.
5. Evaluate the role of technology and AI in guest accounting, including governance risks.

Analytical / Application Questions

1. A guest folio has room charges of 1,200, outlet charges of 460, taxes of 166, an allowance of 80 and payments of 1,500 monetary units. Calculate the closing balance and identify the control checks that should precede departure.
2. A POS report shows 18,750 monetary units, while the PMS contains 18,420. Develop a reconciliation approach that distinguishes timing differences, rejected postings, duplicates and genuine omissions.
3. During group departure, the master folio is overbilled but two individual folios show equal negative balances. Explain why a simple allowance is inappropriate and design an evidence-based corrective procedure.

Multiple Choice Questions with Answers

Question 1

Which record provides the detailed chronological statement of a guest’s charges and credits?

A. Folio

B. Occupancy forecast

C. Room-status report

D. Cashier roster

Correct Answer: A. Folio

Question 2

If opening balance is 500, debits are 900 and credits are 300 monetary units, what is the closing balance?

A. 200

B. 800

C. 1,400

D. 700

Correct Answer: D. 700

Question 3

Which action best preserves transaction integrity when a charge was posted incorrectly?

A. Delete it without a note

B. Reverse or correct it with an audit trail

C. Leave it unchanged until month-end

D. Offset it using an unrelated allowance

Correct Answer: B. Reverse or correct it with an audit trail

Question 4

A cashier has an opening float of 300, cash received of 2,000, paid-outs of 150 and refunds of 100. What is expected cash?

A. 2,050

B. 2,150

C. 2,250

D. 2,350

Correct Answer: A. 2,050

Question 5

What is the primary purpose of a credit limit?

A. To determine room availability

B. To calculate occupancy

C. To control unsecured financial exposure

D. To allocate package revenue

Correct Answer: C. To control unsecured financial exposure

Question 6

A foreign-currency receipt is 200 units and the approved rate is 0.92 reporting-currency units per foreign unit. What is its reporting value?

A. 92

B. 184

C. 217.39

D. 200.92

Correct Answer: B. 184

Question 7

Which night-audit activity directly tests whether an interface lost or rejected transactions?

A. Comparing source-system totals with PMS-posted totals

B. Changing all guest rates

C. Closing the front desk before outlets

D. Removing unresolved folios

Correct Answer: A. Comparing source-system totals with PMS-posted totals

Question 8

Which payment-security practice is appropriate?

A. Writing full card details in guest notes

B. Sharing terminal credentials among all staff

C. Using approved tokenized payment systems

D. Accepting an unsigned manual card number for convenience

Correct Answer: C. Using approved tokenized payment systems

Question 9

Why can a zero net variance still conceal an accounting problem?

A. Taxes are never included in folios

B. Offsetting errors may cancel each other

C. Cashiers cannot post credits

D. All interfaces always duplicate charges

Correct Answer: B. Offsetting errors may cancel each other

Question 10

Which indicator is calculated as room revenue divided by rooms sold?

A. Occupancy percentage

B. RevPAR

C. ADR

D. Cash variance

Correct Answer: C. ADR