Chapter 12Protect Revenue and Control Spending

Use practical controls to protect revenue, purchasing, payments and other material spending without turning the hotel into a bureaucracy.

By Manish Gupta, CA · eHMS Press · Updated Aug 28, 2026

Questions this chapter helps answer

How can an independent hotel protect the revenue it earns and control spending without creating excessive bureaucracy?
Which practical controls matter most for purchasing, receiving, inventory, cash, discounts, refunds, settlements, payroll, and OTA reconciliation?
How should exceptions be identified, reviewed, assigned, and followed up so controls lead to action rather than paperwork?

Key concepts

revenue leakage
purchasing controls
receiving
inventory
cash control
discounts and refunds
OTA reconciliation
payroll leakage
exception review

Use practical controls to protect revenue, purchasing, payments and other material spending without turning the hotel into a bureaucracy.

Chapter-end learning

Apply, check, and remember

Apply it to your situation

Connect the chapter to a real hotel decision

As you answer, think about where this issue appears in your own property, team, report, meeting, or control process. Work through one item at a time, check the result, and then continue.

Knowledge check

Question 1 of 3

0 checked

Which statement best reflects the central rule of Chapter 12?

What this tests: Recognise the chapter's central management principle.

Protect value with practical controls that prevent or expose revenue leakage, unauthorised spending and unsupported exceptions without creating unnecessary bureaucracy.Judge the issue from one headline number and act immediately.Add as much reporting detail as possible before deciding what matters.Treat the accounting output as sufficient without testing the operating context.

Show hint

Use the owner-first rule in this chapter.

1 / 3

Memory practice

Flashcard 1 of 4

Revenue leakage

Reveal the answer, decide how confident you are, and then move to the next card.

Continue the discussion

Share how this applies in practice

A repeating exception can become material even when each transaction is small.

The hotel has frequent voids, discounts and OTA settlement differences, but each item is individually small. How should the owner decide what deserves attention?

Trend exceptions by type and value, test authorisation and source records, reconcile settlements, identify repeat patterns and assign corrective action where control failure is evident.

0 responses

Responses are public and may be moderated to keep the exchange professional and useful.

No responses yet. Start the discussion with a practical example or a question raised by the chapter.

ReadAvailable nowListenPlanned editionWatchPlanned edition