USALI-Standard Hotel P&L — How Owners and Boards Read the True Profit Picture

10/08/2026

Every month, the owner receives a file of reports. One property calls it "revenue", another calls it "total takings"; one has already deducted tax, another has not; utility costs sit inside departmental expenses here and inside overheads there. The result is a board meeting that argues about what the number means instead of arguing about what to do next. The answer to this has existed for nearly a century and is the common language of the global lodging industry: the USALI-standard hotel P&L.

This article explains what USALI is, the structure of a hotel operating statement from departmental revenue down to GOP, two metrics that complement RevPAR — TRevPAR and ALOS — and then spells out exactly where DiOwner — the view-only reporting app for owners and boards — stands in that picture. Every figure DiOwner shows is generated by the underlying AI hotel management software DiHotel. Multi-property comparison, how RevPAR is computed and the figure-reconciliation commitment were covered in the previous article on hotel chain management; this one moves to the financial framework.

Part 1: What Is USALI — the Common Language of the Hotel Industry

USALI stands for the Uniform System of Accounts for the Lodging Industry. It is not a statutory accounting standard like VAS or IFRS, but a presentation framework for management reporting, drawn up by international hotel and hotel-finance associations, first published in the 1920s and revised many times up to the current edition.

USALI answers a very practical question

• How do you compare two different hotels? If each names its own line items, every comparison is meaningless. USALI dictates which department revenue and cost belong to, and in what order.
• How do you measure the management team's performance, separate from the owner's decisions? USALI builds the report in layers; the GOP layer separates operations from what belongs to the owner — interest, depreciation, ground rent.
• How do you talk to the outside world? International management contracts, asset valuations, loan files and transaction due diligence all read the P&L in the USALI structure by default.

Two core conventions to remember

• Revenue recorded net — before value-added tax and amounts collected on behalf of the state. The "tax and fees included" figure is for the guest, not for the P&L; using it to compute metrics inflates everything.
• Revenue and cost land in the department where they arise — breakfast belongs to F&B, not rooms; housekeeping wages belong to the rooms department cost, not overheads. Post to the wrong department at the operating stage and you can never rebuild a standard-compliant P&L afterward.

Part 2: The Structure of a Hotel P&L — from Departmental Revenue Down to GOP

What makes the USALI-standard hotel P&L powerful is that it goes layer by layer, each layer answering a different management question:

Layer 1 — Revenue by Department

• Rooms — usually the highest-margin department.
• F&B — restaurant, bar, room service, banquets and conferences.
• Other operated departments — spa, laundry, golf course, recreation, space rental.
• Other income — cancellation fees, no-show fees, commissions, long-term rentals.

Layer 2 — Direct Costs and Departmental Profit

Each department subtracts its own direct costs (labour, cost of goods sold, supplies, channel commissions) to arrive at departmental profit. This is where an uncomfortable truth surfaces: a restaurant with large revenue can still be a department dragging the whole hotel down if its cost of goods and labour exceed the threshold.

Layer 3 — Undistributed Expenses

• Administrative & general
• Information technology & telecommunications
• Sales & marketing
• Property operations & maintenance
• Energy (electricity, water, fuel)

Layer 4 — GOP, the Most Important Boundary

Total departmental profit minus undistributed expenses gives GOP — Gross Operating Profit. GOP is the fairest yardstick for the management team, because it contains exactly what they can control. Divide GOP by available room-nights and you get GOPPAR, profit per available room.

Layer 5 — Below GOP Is the Owner's Territory

Management fees, ground rent, property taxes, insurance, then EBITDA; after that depreciation, interest and finally net profit. These items mostly arise from investment decisions and capital structure, not from how many rooms were sold yesterday.

Part 3: What Is TRevPAR — When RevPAR No Longer Tells the Whole Story

TRevPAR (Total Revenue Per Available Room) is total revenue across all departments divided by available room-nights in the period. Where RevPAR speaks only of rooms revenue, TRevPAR speaks of all the money each available room brings the hotel.

• Why 4–5 star hotels and resorts need TRevPAR: at properties strong in F&B, weddings, conferences and spa, non-rooms revenue can approach rooms revenue. Ranking a portfolio by RevPAR alone underrates exactly those properties exploiting services best.
• Two properties with the same RevPAR can differ greatly: a city hotel that is rooms-only and a resort with a conference centre will show markedly different TRevPAR even if they sell rooms equally.
• A necessary warning: high TRevPAR does not automatically mean high profit — F&B and banquets have far thinner margins than rooms. TRevPAR must be read alongside departmental profit, or it leads to expanding services in the wrong place.
• Conditions for TRevPAR to be correct: every revenue line must be tied to the right department at the moment it arises, computed on detail lines rather than aggregated by invoice, room type and complimentary services set apart, cancelled lines removed, and walk-in revenue still counted — this group makes up a very significant share at F&B-strong properties.

Part 4: What Is ALOS — the Metric That Explains the Hidden Cost Behind Every Room-Night

ALOS (Average Length of Stay) is total occupied room-nights divided by the number of bookings arising in the period. It rarely appears on the scoreboard yet directly affects GOP.

• A short ALOS costs more than a long ALOS. For the same room-nights sold, the more check-ins and check-outs, the more departure cleans, the more linen to launder, the more reception staff, the more transaction cost and channel commission.
• ALOS explains the ADR paradox. A group contract or long-staying guest with a lower ADR than rack rate can still be better on profit, because the cost of service per night falls significantly. Looking at ADR alone concludes the opposite.
• ALOS is an input for pricing strategy. Minimum-night restrictions in peak season, long-stay packages in low season — all these policies can only be evaluated if ALOS is tracked continuously.
• Computing ALOS correctly requires clean booking data: mid-stay room changes, stay extensions, splitting and merging invoices, groups splitting into individuals, no-shows — each situation can skew the denominator if the system does not handle it correctly.

Part 5: Where DiOwner Stands in the P&L Picture

To be plain so no one misunderstands: DiOwner does not produce a full P&L report. DiOwner is a phone app, view-only, reading real-time from the underlying management system, and it handles the revenue layer — the top layer of the USALI-standard P&L, plus receivables.

What DiOwner shows today, and by what formula

• Revenue by source — rooms, F&B, spa and other services, with walk-in revenue set apart. All is net revenue before value-added tax, per the USALI convention.
• ADR = net rooms revenue ÷ occupied room-nights.
• RevPAR = net rooms revenue ÷ available room-nights.
• Occupancy = occupied rooms ÷ (total rooms − out-of-order OOO rooms) × 100. When consolidating multiple properties, the system sums the rooms of the entire portfolio first, then divides — it does not average the percentages, because that distorts the result when properties differ in size.
• Receivables by travel company and sales channel, with ageing. This data comes from the accounting module, so it always carries the label "accounting figure through MM/yyyy" — deliberately lagged and stated as lagged, rather than pretending to be real-time.
• 30/60/90-day forecast based on rooms already booked (on-the-books). This is a sum of what is already on the books, not a machine-learning prediction model — stated honestly, the owner knows exactly what basis they are trusting.

Reconciliation table: USALI P&L lines and their status in DiOwner

Part 6: Hotel Internal Control — One Set of Figures That Protects Both Sides

Hotel internal control is often misunderstood as hunting for someone's mistake. In reality it is a mechanism for the owner, the board and the management team to look at one set of figures, with one definition, at one point in time. When that mechanism works well, both sides benefit — and the side that benefits most clearly is usually the management team itself.

For the management team: good results proven by source data

• A quarter of good growth needs no presentation to be recognised — the figures are already on the board's screen, per the definition both sides agreed.
• When the market turns bad, the same figures show the objective cause: seasonality, source-market mix, a group contract ending. Without data, a quarter of decline is easily blamed on management error.
• No more nights rushing to compile reports before a meeting, no more each side bringing a different Excel file into the room.

For the owner and the board: a basis for allocating capital

• Seeing the situation in real time rather than waiting for a manual period-end compilation, so decisions to renovate, expand or reallocate resources come earlier.
• An equity investor in a specific property is granted view rights to exactly that property — transparency with partners without opening the entire system.

Four mechanisms that keep this from becoming surveillance

• Read-only, no writing: DiOwner cannot edit operating data, cannot create orders, cannot intervene in the team's daily work.
• A single metric definition: everyone views the same formula, so debate happens at the action layer, not at the "whose number is right" layer.
• Alert thresholds agreed by both sides: alerts exist to react early to a situation, not to build a file on a person.
• The edit trail sits in the management system: every cancellation, edit and discount is logged at the operating layer — this is precisely what lets independent audit confirm results, which is to say it protects the operator's reputation.

Part 7: Managing Multiple Hotel Branches Without Being Present

An owner with four or five properties in different provinces cannot be everywhere, and should not be. What they need is to manage multiple hotel branches without being present while still holding a firm grip on the situation:

• The whole portfolio on one phone screen — revenue, metrics and receivables of each property and the consolidated figure, updated in real time; viewable right before a meeting or while travelling.
• Consolidating correctly — sum the rooms of the whole portfolio first, then divide, so the consolidated figure reflects true scale rather than being skewed by a small property.
• Proactive alerts pushed to the device — revenue dropping below threshold, abnormal occupancy, overdue receivables. The owner need not remember to open the app daily; the app speaks up when there is something to know.
• Permissions by property and by role — each board member, each equity investor sees exactly their own scope, with biometric authentication on the device.

How to compare rankings across properties and the detailed reasoning on RevPAR were covered in the article on hotel chain management software for boards. For smaller properties in the same portfolio, the equivalent role is filled by the cloud AI hotel management software DiCloud, and the same DiOwner app reads figures from both platforms.

Part 8: Why the Underlying Platform Determines the Report's Entire Value

There is a technical truth we repeat in every document about DiOwner: the app only displays; every calculation sits in the underlying management system. Which means a beautiful dashboard on top of a miscalculating system only helps the owner make wrong decisions faster. At group scale, a small deviation at each property multiplies into a large deviation when consolidated.

Where the hotel P&L often goes wrong, invisibly on the report

• Splitting and merging invoices — a group pays the rooms portion, individuals pay the services portion; if the system aggregates by invoice instead of computing on detail lines, revenue lands in the wrong department.
• Mid-stay room changes — room class changes, so price changes; misallocating by day skews both ADR and RevPAR.
• Complimentary rooms, internal-use rooms, cancelled transactions — must be excluded, or occupancy improves while ADR worsens absurdly.
• Debit consolidated to rooms and travel-agent receivables — revenue has arisen but the money has not arrived; this is when cash flow and profit tell two different stories.
• Point-of-sale revenue not tied to the right department — if the sales system does not push revenue to the correct outlet at the moment it arises, no reporting software can rebuild a USALI-standard P&L afterward.

This is why DiOwner's revenue layer is built on the comprehensive hotel management solution DiHotel, where the edge cases above have been handled at the business layer for over twenty years. The figures shown in the app have been verified on real hotel data and reconciled exactly with the system's source reports — the mandatory condition for a figure to dare enter the boardroom or go to audit.

Conclusion

The USALI-standard hotel P&L is not an accounting procedure but a common language that lets owner, board and management team speak the same tongue: revenue recorded net and landing in the right department, costs sorted into the right layers, GOP as a clear boundary of responsibility. Add TRevPAR to see the full value each room brings and ALOS to see the hidden cost behind each room-night, and the picture is finally enough to make capital-allocation decisions.

DiOwner takes its share of the work squarely: providing the real-time revenue layer of that picture on the phone — revenue by source, ADR, RevPAR, occupancy, receivables — computed on the net-revenue convention and reconciled exactly with the system; the cost layer, GOP and GOPPAR sit on the roadmap and will only appear once there is enough basis to compute them correctly. All of it runs on the AI hotel management software DiHotel for the upscale segment and the online AI hotel management software DiCloud for smaller properties in the same portfolio. The view for small hotel owners on this same theme of figure transparency is in the article controlling revenue leakage.