Revenue Accounting and the Night Audit

Introduction

Revenue accounting in a hotel is the systematic identification, measurement, recording, reconciliation, and reporting of income earned from rooms, food and beverage, meetings and events, leisure facilities, retail activities, and other guest services. It is more complex than ordinary sales accounting because a hotel operates continuously, serves transient and contracted customers, combines several operating departments, and receives payment through multiple channels.

The night audit is the control process that closes one business day and opens the next. It validates transactions recorded in the property-management system (PMS), point-of-sale (POS) systems, payment gateways, cashier records, and general ledger. Although traditionally performed at night, the function is fundamentally an accounting and internal-control activity rather than merely a shift duty.

A reliable revenue system must answer five questions:

1. What service was provided?
2. On what date and at what price?
3. Which department earned the revenue?
4. What tax, commission, discount, or adjustment applies?
5. How and when will the amount be collected?

Learning Objectives

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

• classify hotel revenue streams and identify the appropriate source record;
• record room, food and beverage, event, ancillary, package, discount, tax, commission, and receivable transactions;
• distinguish revenue, tax liability, cash, card receivables, guest ledger, city ledger, and allowance accounts;
• calculate occupancy, average daily rate, revenue per available room, and departmental revenue totals;
• perform a structured night audit and reconcile PMS, POS, payment, and general-ledger balances;
• investigate exceptions and prepare defensible audit documentation; and
• evaluate control, ethical, technological, and managerial issues in hotel revenue accounting.

1. The Revenue Architecture of a Hotel

1.1 Revenue departments and source systems

Hotel revenue normally originates in operational systems and is transferred to the accounting system through interfaces or controlled journal entries.

The accounting department should not treat an interface total as automatically correct. It must establish whether the transaction is complete, authorized, classified correctly, posted to the correct business date, and supported by an audit trail.

1.2 Revenue recognition in hotel operations

For management and financial reporting, revenue is generally recognized when the hotel has substantially provided the promised service and the amount is measurable and collectible. A room occupied for a night ordinarily produces room revenue for that night, not when the reservation was made. An advance deposit is normally a liability until the related service is provided or the deposit becomes non-refundable under applicable policy and law.

A simplified revenue identity is:

This identity is a classification framework, not a substitute for the applicable accounting standard. Tax collected on behalf of a government is ordinarily recorded as a liability rather than operating revenue. Local accounting standards, contract terms, and tax regulations must be followed.

1.3 Gross and net presentation

A hotel may sell through an online travel agency (OTA), event intermediary, or corporate agent. The accounting question is whether the hotel is the principal or an agent for the service. If the hotel controls the accommodation service before transfer to the guest, room revenue is generally presented gross and the OTA commission is recorded separately as selling or commission expense. If the hotel is merely arranging another provider’s service, net presentation may be appropriate. This is a judgment requiring contract analysis and compliance with the relevant reporting framework.

2. Core Ledger Concepts

2.1 Guest ledger and city ledger

The guest ledger contains amounts owed by guests currently staying in the hotel. Charges may be settled by cash, card, direct billing, or transfer to another approved account. The city ledger contains receivables from departed guests, companies, travel agencies, groups, and other approved accounts.

A transfer from guest ledger to city ledger does not create new revenue. It changes the classification and collection responsibility of an existing receivable.

2.2 Folios and account balances

A folio is the detailed account for a guest, room, group, or company. It records debits, credits, taxes, payments, transfers, and the running balance. A zero-balance folio is not necessarily evidence of correct accounting: an unauthorized allowance or an omitted tax can also produce zero balance. Review must therefore focus on the underlying entries and approvals.

2.3 Common account categories

The chart of accounts should separate revenue by department and, where useful, by outlet, market segment, rate code, tax category, and channel.

3. Recording Major Revenue Transactions

3.1 Room revenue

A room posting usually includes the base room charge and applicable taxes. A standard journal pattern is:

The debit account depends on settlement status. If the guest has not paid, the amount remains in the guest ledger. If a valid card authorization or payment has been captured, a card receivable or cash account may be used.

Room revenue should be supported by the occupied-room report, rate and package code, approved room move or upgrade record, and folio. Complimentary rooms require authorization and should be distinguished from occupied rooms that generate zero-rate revenue.

3.2 Food and beverage revenue

A POS transaction should identify outlet, check number, server or cashier, items sold, discounts, service charges, taxes, payment method, and void history. A simplified posting is:

If a service charge is legally or contractually payable to employees, it should not automatically be treated as hotel revenue. Its classification depends on the applicable accounting and employment rules.

3.3 Events and banquets

An event may involve a deposit, progress billing, room hire, catering, equipment, cancellation terms, and a final settlement. The event contract should specify dates, minimum spend, tax treatment, commission, cancellation liability, and responsibility for incidental charges.

Deposits received before performance are generally recorded as:

When the hotel provides the contracted service, the appropriate amount is transferred from the liability to revenue, with tax recorded according to the time-of-supply rules applicable in the jurisdiction.

3.4 Ancillary services and packages

Spa, parking, laundry, transfers, recreation, telephone, minibar, and retail services require departmental source documents. A package combines two or more promised services, such as room, breakfast, airport transfer, and spa access. The package price should be allocated systematically among components, commonly using relative stand-alone selling prices where required by the applicable accounting framework.

For a package price P and component stand-alone prices s₁, s₂, ..., s_n, the allocation to component i is:

where ∑s_j is the sum of all component stand-alone prices. This method assumes the stated stand-alone prices are reliable and that the package is accounted for as a combined contract. Promotional or complimentary components may require a different policy.

3.5 Discounts, allowances, refunds, and voids

A discount is normally granted before or at the time of sale under an approved rate or promotion. An allowance is a post-sale reduction, often used to correct a service failure or billing dispute. A refund returns money already collected. A void cancels a transaction before settlement or posting, depending on system design.

These terms should not be used interchangeably. Each adjustment should contain:

• original transaction reference;
• reason and amount;
• authorizing employee;
• date and business period;
• tax effect; and
• evidence of guest or manager approval where required.

Unusual discounts, repeated voids, negative checks, and manual postings are high-risk exceptions because they can conceal theft or unauthorized benefits.

3.6 Commissions and receivables

Suppose an OTA sells a room for 10,000 currency units and charges a 15% commission. If the hotel is principal and revenue is reported gross:

The accounting pattern is:

The calculation assumes the commission is calculated on the full room amount and excludes tax. If the contract calculates commission on room revenue excluding tax, the base must be changed. The reconciliation must compare reservation production, OTA statements, commission invoices, deposits, and chargebacks.

4. Taxes and Control of Tax Data

Tax must be separated from revenue whenever the hotel collects it on behalf of a government or other authority. Tax rates, exemptions, inclusions, rounding, place of supply, and invoice requirements vary by jurisdiction. The PMS and POS must therefore contain controlled tax rules rather than relying on manual memory.

For a taxable value B and tax rate r expressed as a decimal:

If a displayed price G is tax-inclusive, the taxable base is:

These formulas assume one tax rate, no tax-on-tax, and no rounding complication. Where multiple taxes apply, each tax must be calculated under local rules. Rounding should be applied consistently at the legally required level—line, transaction, invoice, or daily total—and differences should be documented.

5. Performance Measures Used in Revenue Control

Hotel accountants use operating ratios not only for management but also as reasonableness tests during the night audit.

Let:

• RN = rooms available for sale;
• RO = rooms occupied or sold;
• RR = room revenue, excluding taxes where appropriate;
• D = number of operating days.

Then:

For a period, RN is normally the number of available room nights, not merely the number of physical rooms. Thus, if a 100-room hotel operates for 30 days, has 2,700 available room nights, sells 2,160 room nights, and earns room revenue of 324,000 currency units:

• Occupancy = 2,160 ÷ 2,700 × 100 = 80%;
• ADR = 324,000 ÷ 2,160 = 150 currency units;
• RevPAR = 324,000 ÷ 2,700 = 120 currency units.

The identity RevPAR = ADR × occupancy rate applies when occupancy is expressed as a decimal: 150 × 0.80 = 120. These metrics are analytical indicators, not substitutes for ledger reconciliation. Complimentary rooms, house use, out-of-order rooms, and package allocation can affect interpretation.

6. The Night Audit Process

The night audit should be performed in a controlled sequence. Exact screens differ among systems, but the control logic is stable.

Stage 1: Establish the business date

The auditor confirms the current PMS business date, local time, operating calendar, and cut-off policy. Transactions posted after the cut-off must either belong to the next business date or be supported by an approved late-posting procedure. Time-zone differences and daylight-saving changes require special attention in international properties.

Stage 2: Secure source records

The auditor obtains or electronically locks:

• front-office cashier reports;
• room status and occupancy reports;
• arrivals, departures, no-show, and cancellation reports;
• PMS transaction and adjustment reports;
• POS outlet summaries and payment reports;
• banquet and event revenue reports;
• spa, parking, minibar, laundry, and other ancillary reports;
• card terminal batches and payment gateway reports;
• cash counts and deposit records; and
• interface and exception logs.

Stage 3: Validate room revenue

The auditor compares occupied rooms with room charges, rate codes, packages, room moves, complimentary rooms, house use, no-shows, and early departures. A room occupied but lacking a room charge is a potential leakage exception. A room with several room charges or an unusual rate requires investigation, not automatic correction.

Stage 4: Close POS outlets

Each outlet closes its business date and produces a cashier summary. The auditor compares POS sales with the PMS interface, checks open checks, suspended checks, voids, discounts, refunds, paid-outs, and manual receipts, and confirms that the payment totals agree with cashier declarations.

Stage 5: Reconcile payments

Payment reconciliation is performed by tender type:

• cash counted versus cashier report;
• cards in the POS versus terminal batch;
• terminal batch versus processor settlement;
• bank or payment gateway settlement versus deposit record;
• approved direct billing versus city-ledger transfer; and
• deposits and advance payments versus reservation or event records.

Card settlements may occur on a different date from the sale. The reconciliation should therefore distinguish transaction date, batch date, settlement date, and bank value date.

Stage 6: Post legitimate adjustments

Approved corrections are posted with the original reference and explanation. The auditor should not use a suspense account to conceal an unexplained difference. If a difference cannot be resolved before close, it should be documented, assigned to an owner, and monitored to resolution.

Stage 7: Balance the ledgers and roll the date

The PMS transaction totals are compared with POS interfaces and the general ledger. The auditor confirms that guest ledger balances, city ledger transfers, advance deposits, taxes, allowances, commissions, and receivables are properly classified. Only an authorized user should roll the PMS to the next business date, and the system-generated audit package should be preserved.

7. Reconciliation Framework

A useful control matrix is shown below.

A reconciliation difference can be expressed as:

The equation is a diagnostic identity. A zero difference does not prove that all transactions are valid; two errors can offset one another. Reconciliation must therefore combine numerical agreement with transaction-level sampling and exception review.

8. Illustrative Integrated Case

Background

The illustrative Riverside Hotel has 120 rooms. During one audit date, the PMS reports 96 occupied rooms and room revenue of 864,000 currency units before tax. The restaurant POS reports food sales of 180,000 and beverage sales of 70,000 before tax. The applicable tax rate is 10%. An OTA statement shows 100,000 of room revenue, a 15% commission, and a settlement of 85,000. A card terminal report is 2,000 higher than the POS card total.

Problem

The controller must determine whether the business date can be closed and identify the accounting entries and unresolved exceptions.

Analysis

Room ADR is:

Tax on the reported taxable revenue of 1,114,000 is:

The OTA commission is:

The OTA settlement of 85,000 agrees mathematically with gross revenue less commission. However, the auditor must verify that the 100,000 is included in the PMS room total, that tax is excluded from the commission base as assumed, and that the settlement is not a duplicate of another receipt.

The card difference of 2,000 is not an automatic revenue adjustment. Possible explanations include an offline terminal transaction, a late POS interface, a duplicate terminal batch, a tip or service-charge treatment difference, or an unauthorized transaction. The auditor compares transaction IDs, batch numbers, timestamps, and settlement reports.

Approach and solution

The controller records departmental revenue and tax through the controlled interface, records the OTA commission separately, and attaches the OTA statement to the reconciliation. The 2,000 card variance remains in an exception log until matched to a transaction. If evidence confirms a valid sale omitted from the POS, the sale is posted to the correct department and business date. If the terminal contains a duplicate or unauthorized transaction, the processor is contacted and no revenue is recognized merely because a terminal total is high.

Outcome

The hotel may close the date only after the card exception is either resolved or formally escalated under the property’s close policy. The final audit file contains the reports, reconciliations, approvals, journal references, and explanation of any carried-forward item.

Learning points

1. A mathematically balanced settlement can still be improperly classified.
2. Tax must be calculated on the correct taxable base.
3. Commission expense is distinct from a reduction of gross revenue where gross presentation is appropriate.
4. Differences must be investigated at transaction level.
5. Night audit is both a closing procedure and a fraud-prevention control.

9. Internal Control, Ethics, and Governance

Effective controls follow segregation of duties. The employee who records a sale should not be the sole person who approves an allowance, counts the cash, and reconciles the bank. Important controls include unique user IDs, role-based access, approval limits, immutable audit logs, sequential receipts, independent cash counts, restricted backdating, daily exception reports, and periodic surprise reviews.

Ethical risks include suppressing sales to meet a target, granting unauthorized complimentary rooms, manipulating business dates, delaying chargebacks, misclassifying tax, and using guest data for personal purposes. Management pressure does not justify an unsupported journal entry. Corrections should preserve the original transaction and record the reason for change.

Personal data in folios, payment records, identification documents, and loyalty profiles must be protected. Card data should be tokenized or masked, access should be limited, and retention should follow payment-security and privacy requirements. Local tax law, financial-reporting standards, employment rules concerning service charges, and payment-card requirements must be treated as mandatory control parameters.

10. Technology and Contemporary Practice

Modern hotels increasingly use cloud PMS platforms, integrated POS, application programming interfaces, automated revenue feeds, robotic process automation, and business-intelligence dashboards. These tools reduce manual entry but create new risks: interface mapping errors, duplicate messages, system outages, cyberattack, incorrect master data, and overreliance on automated exception clearing.

Artificial intelligence can help identify unusual void rates, abnormal discounts, implausible occupancy patterns, duplicate card transactions, and deviations from historical outlet behavior. It should support—not replace—professional judgment. An AI alert is not proof of fraud, while the absence of an alert is not proof of correctness. Models require validated data, documented thresholds, access controls, explainability appropriate to the decision, and human review.

Best practice is to maintain a three-level control model:

1. Preventive controls: authorized rate codes, tax tables, access permissions, and interface validation.
2. Detective controls: reconciliations, exception reports, variance analysis, and independent reviews.
3. Corrective controls: documented adjustments, recovery of losses, system remediation, and staff training.

Challenges and Limitations

Revenue accounting is affected by overlapping business dates, multiple currencies, package allocation, changing tax rules, cancellations, no-shows, chargebacks, group billing, split folios, and delayed settlements. Standard ratios can be misleading when inventory is blocked for maintenance or when package revenue is allocated away from rooms. Automated interfaces can transmit errors rapidly. Finally, a night auditor working under time pressure may perform superficial rather than analytical checks.

The appropriate response is not to eliminate judgment but to standardize procedures, define materiality and escalation rules, preserve evidence, rotate review responsibilities, and use trend analysis alongside daily reconciliation.

Chapter Summary

Hotel revenue accounting connects operational activity with reliable financial reporting. Room, food and beverage, event, ancillary, and package transactions must be supported by source documents, posted to the correct department and date, and separated from taxes and other liabilities. Discounts, allowances, refunds, commissions, deposits, and receivables require distinct classifications and documented approvals.

The night audit closes the business date by validating room and outlet activity, reconciling cash and electronic payments, reviewing interfaces and exceptions, balancing guest and city ledgers, and preserving an audit trail. Occupancy, ADR, and RevPAR provide useful reasonableness tests but do not replace transaction-level controls. Strong governance combines segregation of duties, access control, tax compliance, privacy protection, reconciliation, and responsible use of automation and AI.

Key Terms

Revenue recognition: Determining when earned service income is recorded.

Guest ledger: Receivables belonging to current in-house guests.

City ledger: Receivables transferred to accounts for departed guests, companies, or agencies.

Folio: Detailed account record for a guest, room, group, or company.

PMS: Property-management system used to manage reservations, rooms, folios, and hotel operations.

POS: Point-of-sale system used to record outlet sales and payments.

Night audit: Business-date closing and reconciliation process.

Advance deposit: Money received before the related service is provided.

Allowance: Authorized post-sale reduction of a charge.

Void: Cancellation of a transaction under system and control rules.

Commission: Amount paid or payable to an intermediary for generating business.

OTA: Online travel agency or electronic distribution intermediary.

ADR: Room revenue divided by rooms sold.

RevPAR: Room revenue divided by available room nights.

Occupancy: Rooms sold expressed as a percentage of available room nights.

Tax payable: Liability for tax collected on behalf of an authority.

Interface: Electronic transfer of data between operational and accounting systems.

Chargeback: Reversal or dispute of a card transaction.

Exception log: Controlled record of unresolved variances or unusual transactions.

Segregation of duties: Division of recording, custody, approval, and review responsibilities.

Review Questions

Short Answer Questions

1. Distinguish the guest ledger from the city ledger.
2. Why is tax collected from a guest normally separated from hotel revenue?
3. Define ADR and RevPAR.
4. State two documents used to validate food and beverage revenue.
5. Why should a transfer from guest ledger to city ledger not be treated as new revenue?

Long Answer Questions

1. Explain the complete night-audit process from establishing the business date to rolling the PMS forward.
2. Discuss the accounting treatment of room revenue, OTA commissions, and card receivables.
3. Explain the control risks associated with discounts, allowances, refunds, and voids.
4. Describe how package revenue may be allocated among room and ancillary components.
5. Evaluate the role of technology and AI in hotel revenue reconciliation.

Analytical / Application Questions

1. A hotel reports room revenue of 450,000 from 300 sold room nights and has 500 available room nights. Calculate occupancy, ADR, and RevPAR, and explain what each measure indicates.
2. A restaurant’s POS shows card sales of 64,500, while the terminal batch shows 66,000. Design a step-by-step investigation and identify at least four possible causes.
3. An OTA statement shows gross room sales of 80,000, a 12.5% commission, and a settlement of 70,000. Determine whether the settlement agrees with the stated commission, then explain what additional evidence is needed before posting the entry.

Multiple Choice Questions with Answers

Question 1

Which account normally records tax collected by a hotel on behalf of a government authority?

A. Room revenue

B. Tax payable

C. Commission expense

D. Guest allowance

Correct Answer: B. Tax payable

Question 2

A hotel earns room revenue of 240,000 from 1,600 sold room nights. What is the ADR?

A. 120

B. 150

C. 180

D. 240

Correct Answer: B. 150

Question 3

Which transaction normally creates a liability rather than immediate earned revenue?

A. A room occupied tonight

B. A restaurant meal served

C. An advance deposit for a future stay

D. A completed spa treatment

Correct Answer: C. An advance deposit for a future stay

Question 4

If an OTA commission is 15% of 20,000 gross room revenue, what is the commission?

A. 1,500

B. 2,000

C. 3,000

D. 3,500

Correct Answer: C. 3,000

Question 5

What is the principal purpose of the night audit?

A. Set room prices for the next season

B. Close and reconcile the hotel business date

C. Prepare employee schedules

D. Purchase food inventory

Correct Answer: B. Close and reconcile the hotel business date

Question 6

Which comparison most directly reconciles card processing activity?

A. Room status to housekeeping schedule

B. POS card total to terminal batch

C. Banquet contract to employee roster

D. Guest comments to occupancy forecast

Correct Answer: B. POS card total to terminal batch

Question 7

A hotel has 2,000 available room nights and sells 1,500. What is occupancy?

A. 25%

B. 50%

C. 75%

D. 80%

Correct Answer: C. 75%

Question 8

Which practice provides the strongest segregation of duties?

A. One employee records, approves, and reconciles all cash

B. Cashiers approve their own allowances

C. Different employees record transactions and independently review reconciliations

D. Managers share one system login

Correct Answer: C. Different employees record transactions and independently review reconciliations

Question 9

A package price is allocated using relative stand-alone selling prices primarily because it:

A. Eliminates all taxes

B. Assigns consideration systematically among components

C. Converts receivables into cash

D. Guarantees higher room revenue

Correct Answer: B. Assigns consideration systematically among components

Question 10

An unexplained card variance during night audit should initially be:

A. Written off immediately

B. Added to room revenue

C. Investigated using transaction and batch evidence

D. Ignored if the total is small

Correct Answer: C. Investigated using transaction and batch evidence