A Hotel Can Hit Its Revenue Budget and Still Miss the Profit Target
A hotel can look perfectly healthy on the revenue line and still end the month with a disappointing profit.
That is the problem with relying too heavily on budget-versus-actual reporting.
Plan vs. actual tells you what has already happened. Useful? Absolutely. But by the time a serious deviation appears in the month-end report, there may be nothing left to manage. The month is already closed.
A forecast asks a more useful question:
If the business continues from where it is now, where are we actually going to finish?
Budget, actual, and forecast are three different things
Imagine a hotel has budgeted €420,000 in rooms revenue for the month.
Halfway through the month, actual rooms revenue is €190,000.
Is that good or bad?
You cannot really tell yet.
If current reservations, expected occupancy, and average room rates suggest another €215,000 for the rest of the month, the forecast becomes €405,000.
Now there is something management can work with: an expected €15,000 shortfall before the reporting period has ended.
That is the basic distinction:
Budget = where you planned to go.
Actual = where you are now.
Forecast = where current information suggests you will end up.
The budget should normally stay in place as the original target. Changing expectations belong in the forecast. Otherwise, it becomes difficult to tell whether the business actually achieved what it originally set out to do.
Hotels have one big forecasting advantage
A simple business forecast might take revenue earned so far and extrapolate it across the rest of the month.
For hotels, that can be dangerously simplistic.
Hotel demand is uneven. Weekends behave differently from weekdays. Group arrivals matter. Events matter. Seasonality matters. Cancellations matter.
And, crucially, hotels already know quite a lot about the future because bookings exist before the stay happens.
So rooms revenue can be forecast using real operating drivers:
Available rooms × occupancy × ADR
ADR is the average daily rate achieved for rooms sold.
That makes the forecast more useful because a change in expected revenue can be explained.
Is occupancy falling?
Are rates weaker than budgeted?
Has the sales mix changed?
Are there more cancellations?
Are some rooms unavailable?
The forecast stops being “finance's latest number” and starts becoming an explanation of what is happening operationally.
Different parts of the hotel need different logic
You cannot forecast every department with the same formula.
Rooms depend heavily on occupancy and room rates.
Restaurant revenue may depend on the number of covers and average spend.
Breakfast may depend on the number of staying guests and how many take breakfast.
Banquets depend on events, attendees, and expected revenue per guest.
Payroll depends on staffing levels, hours worked, wage rates, and the amount of work the hotel expects to handle.
This matters because revenue and costs move together.
If occupancy rises, rooms revenue may improve — but so can housekeeping workload, laundry, guest supplies, breakfast volumes, and some labour costs.
A forecast that increases revenue without updating the costs required to produce that revenue can give management a very optimistic picture.
Being “over budget” on costs is not always bad
This is one of those financial situations where context changes everything.
Suppose the budget assumed:
10,000 occupied room nights €20,000 of variable operating expense
That works out to €2.00 per occupied room night.
Now the forecast changes to:
12,000 occupied room nights €23,000 of expense
At first glance, expenses are €3,000 over budget.
But cost per occupied room night has actually fallen to about €1.92.
So is that overspending?
Not necessarily.
The hotel is spending more because it is serving more occupied rooms, while the cost per unit has improved.
That is why a useful budget forecast should distinguish between fixed costs, variable costs, and costs that increase only after certain activity levels are reached.
Revenue can beat budget while profit barely moves
Here is another example.
Budgeted total revenue: €1 million.
Latest forecast: €1.1 million.
Great news?
Maybe.
Now look at GOP — gross operating profit, one of the key measures of hotel operating performance.
Budgeted GOP: €350,000.
Forecast GOP: €365,000.
The hotel expects €100,000 of additional revenue but only €15,000 of additional operating profit.
That is the number worth investigating.
Where is the extra revenue going?
Payroll? Commissions? Food costs? Utilities? Other operating expenses?
This is why forecasting only revenue can create false confidence.
The real question is not simply whether sales are ahead of plan, but how much of that additional revenue reaches operating profit.
Where USALI fits into the picture
USALI does not tell a hotel exactly how to build a forecast.
Its value is different: it provides a consistent structure for hotel management reporting.
If the budget is built one way, actuals another way, and the forecast sits in a separate spreadsheet with its own categories, comparison becomes a finance reconciliation exercise.
Using the same structure for all three makes the chain much clearer:
Budget → Actual → Forecast → Variance → Departmental Profit → GOP
Instead of seeing only that the hotel is likely to miss profit by a certain amount, management can see where the difference is forming — rooms, food and beverage, another operating department, or undistributed expenses.
That is much closer to information people can actually manage.
The spreadsheet problem usually appears gradually
There is nothing inherently wrong with Excel.
For many finance tasks, spreadsheets are excellent.
The problem starts when forecasting becomes a recurring collaborative process involving several departments, multiple data sources, repeated imports, copied formulas, several file versions, and manual reconciliations every week or month.
At that point, finance can spend more time assembling the forecast than analysing it.
And putting the same workbook in the cloud does not necessarily change that.
If people still collect, copy, reconcile, consolidate, and update the same information manually, the process has been digitised — not really automated.
What automation should actually do
Automation should not remove financial judgment.
Someone still needs to decide what occupancy is likely to be, whether staffing assumptions are realistic, whether a cost increase is temporary, or whether demand has genuinely weakened.
What automation can remove is the repetitive preparation around those decisions.
Budget data, actual results, operational information, and forecast assumptions can be managed in a consistent process rather than rebuilt manually for each reporting cycle.
That is where CFO-function automation becomes useful. Platforms such as Finoko can support this type of budgeting, forecasting, management reporting, and financial analysis process.
But the important part is not replacing one spreadsheet with another tool.
It is creating a process where finance can spend more time asking why the forecast changed and less time checking whether everyone is using the correct file.
One last thing: keep old forecasts
Do not overwrite every forecast with the latest version.
Previous forecasts tell you something important about the quality of your management process.
Budget vs. actual tells you whether the original plan was achieved.
Latest forecast vs. actual tells you how accurately the business predicted the result.
Current forecast vs. previous forecast tells you when expectations changed.
If a serious drop in GOP only becomes visible during the last few days of every month, the problem may not just be operating performance.
It may also mean the forecasting process is not picking up changes early enough.
A good forecast is not simply a better guess at the final number.
It should show where the business is heading, what is driving the change, and whether management still has time to do something about it.
How early can your current reporting process tell you that the month is going to miss budget — before it actually does?
