Services
Industry
Resources
Company
Summarize this blog post with:
● The USALI 12th Revised Edition became the required standard from 1 January 2026, published by HFTP and AHLA through the Global Finance Committee.
● Key additions include a payroll full-time-equivalent schedule, a schedule for annual mandatory brand and operator costs, expanded energy, water and waste reporting, discrete loyalty programme cost categories, executive lounge reporting and a section for all-inclusive properties.
● USALI reporting is only automatable if the chart of accounts is structured to it. Retrofitting mappings after the fact is where most of the work sits.
● Food and beverage is where cost containment pays fastest, because POS data already exists at the item level and is rarely used.
● The core F&B discipline is comparing theoretical food cost, calculated from recipes and items sold, against actual food cost from purchases and stock movement. The gap is your controllable loss.
● Start with recipe costing on your top 40 selling items. That usually covers 70 to 80 percent of covers.
Most hotel finance teams treat USALI as a reporting format. It is more useful understood as a comparison language.
Its value is that a 200-key property in Jaipur and a 200-key property in Bengaluru produce statements that can be placed side by side, with the same revenue categories, the same expense classifications and the same departmental structure. Owners can benchmark. Asset managers can challenge. Operators can defend.
That comparison only works if everyone applies the same edition. Which is why 1 January 2026 mattered.
The Global Finance Committee, sponsored jointly by HFTP and the AHLA, published the 12th Revised Edition with a mandatory adoption date of 1 January 2026. Early adoption was permitted, and some groups began tracking new categories during 2025 so that comparatives would hold.
The changes that affect finance teams most:
● Payroll full-time-equivalent schedule: A new schedule presenting FTE data, giving owners and asset managers a labour productivity view that previously required separate analysis.
● Annual mandatory brand and operator costs schedule: Costs that owners pay to brands and operators are now presented discretely, which was one of the most requested changes from the ownership side.
● Loyalty programme cost categories: Multiple discrete expense categories, so the true cost of loyalty programme guests can be measured rather than buried in a franchise fee line.
● Executive lounge reporting: Separate treatment for a facility that carries meaningful revenue and cost in upper-upscale properties.
● Energy, water and waste: Expanded environmental reporting, supporting sustainability benchmarking and disclosure to owners, investors and regulators.
● All-inclusive section: New guidance for properties charging a single price covering rooms, food, beverage and activities, so their statements can be benchmarked fairly.
For Indian operators, the loyalty and brand cost changes tend to attract the most attention, because they make the economics of brand affiliation visible in a way earlier editions did not.
Here is the part that gets underestimated.
USALI reporting cannot be automated by adding a report. It is automated by structuring the underlying data so the report is a query rather than a rebuild.
That requires:
● A chart of accounts aligned to USALI departments and line items, not a legacy chart with a mapping spreadsheet on top.
● Department dimensions on every transaction, so rooms, F&B outlets, spa, banquets and undistributed departments separate cleanly.
● Outlet-level detail within F&B, because a combined food and beverage department tells you nothing actionable.
● Statistical accounts for rooms available, rooms sold, covers, FTEs, and energy consumption, so the operating metrics on USALI schedules populate automatically.
● Consistent treatment across properties, which is the requirement most groups fail. One property classifying a cost as undistributed while another puts it in a department destroys comparability, the same discipline that trips up multi-entity financial consolidation everywhere else in a portfolio.
The practical implication of the 12th edition is that a group which never restructured its accounts now needs to, because the new schedules require data that a legacy chart simply does not capture. Schedule 15 cannot report FTEs that were never recorded by department.
Oracle NetSuite and other multi-entity ERP platforms support this through segment or dimension structures applied consistently across properties, with USALI-shaped reporting built on top. Hospitality-specific back office platforms such as Aptech and M3 ship USALI report formats natively, which suits single-brand estates.
Rooms revenue carries high margin and offers limited room for operational improvement. Food and beverage carries lower margin and responds strongly to daily management, which makes it the right place to spend cost containment effort.
A useful way to think about it: a one percentage point improvement in rooms margin needs a rate or occupancy change you may not control. A one percentage point improvement in food cost needs portion discipline, purchase price attention and menu mix decisions, all of which sit inside the hotel.
A typical full-service Indian hotel runs food cost between 28 and 35 percent of food revenue, and beverage cost between 20 and 28 percent of beverage revenue. Those are wide bands because the drivers vary: banquet mix, buffet reliance, outlet type and portion discipline.
The number that matters is not the percentage. It is the gap between what your recipes say the cost should be and what your accounts say it was.
This is the single most useful F&B control, and most hotels do not run it.
Theoretical food cost is calculated from recipe cost multiplied by items sold, taken from POS data.
Actual food cost is opening stock plus purchases minus closing stock, adjusted for transfers.
The variance between them is your controllable loss. It comprises:
● Portion size drift
● Waste and spoilage
● Unrecorded staff meals
● Theft
● Recipe non-compliance
● Incorrect POS item mapping
● Pricing and yield errors on receipts
A well-run outlet holds this variance under 2 percent of food revenue. Between 2 and 4 percent needs attention. Above 4 percent means something structural is wrong, and it is usually either portion control or a mapping error rather than theft.
Running this calculation requires three things: recipes costed in the system, POS item sales exported at item level, and stock movement recorded properly. The first is the effort. The other two mostly exist already provided your POS and purchasing systems talk to your ERP instead of sitting in separate silos.
Every hotel has POS data. Very few use it for anything beyond revenue reporting.
The analyses worth building:
Menu engineering: Classify every item by popularity and contribution margin into four groups: high margin and popular, high margin and unpopular, low margin and popular, low margin and unpopular. Promote the first, reposition the second, re-cost the third, remove the fourth. Do this quarterly.
Cover and average cheque by daypart: A breakfast cover and a dinner cover are different businesses. Tracking them together hides both.
Discount and void analysis: By outlet, by user, by shift. Persistent patterns indicate either a pricing problem or a control problem, and it is worth knowing which.
Complimentary and staff meal tracking: Frequently untracked, frequently material, and it distorts food cost percentage until it is separated out.
Banquet profitability by function: Revenue less direct food, beverage and labour cost per event. Many hotels discover that certain wedding packages, priced years ago, now lose money at current input costs.
Outlet contribution against space cost: The obvious question that rarely gets asked: is this outlet earning its floor area?
None of the above is exotic analysis. It is standard restaurant management. The obstacle is that the data lives in the POS, the costs live in purchasing, the recipes live in a chef's file, and none of them meet without manual work.
Take a 160-key hotel with three outlets and a banquet operation. Food cost reports at 33 percent, which the management company considers acceptable. Once recipes are costed and POS item sales are matched against stock movement, the picture separates. Two outlets run theoretical cost within 1.5 percent of actual. The third runs 6 percent above, and the cause turns out to be two high-volume items whose portions drifted after a chef change, plus buffet items being rung up under a single generic POS code that carried an outdated cost.
Neither problem was theft. Neither was visible in a blended 33 percent. Both were fixable within a month once the data showed where to look.
Once POS, purchasing and inventory post into the same system as the financials:
● Theoretical versus actual food cost becomes a monthly report rather than a project
● Menu engineering uses live cost data instead of last year's prices
● AI-driven purchase price variance alerts flag when an input cost moves enough to affect menu margin
● USALI departmental statements populate from source through SuiteAnalytics and BI dashboards rather than from a controller's spreadsheet
● Outlet managers see their own numbers weekly, which changes behaviour more than any monthly review
1. Confirm your USALI edition position. If you have not adopted the 12th Revised Edition, establish what data the new schedules require and whether you are capturing it.
2. Restructure the chart of accounts to USALI departments and line items, applied identically across every property.
3. Add statistical accounts for rooms, covers, FTEs and utilities so schedules populate automatically.
4. Cost your top 40 menu items. These typically cover 70 to 80 percent of covers. Full menu costing can follow.
5. Establish the theoretical versus actual comparison monthly, by outlet, not hotel-wide.
6. Build menu engineering into a quarterly cycle with the chef and the F&B manager, not as a finance exercise.
7. Push reporting to outlet managers weekly. Cost control happens on the floor, not in the finance office.
When did USALI 12th Revised Edition take effect?
The mandatory adoption date was 1 January 2026, set by the Global Finance Committee sponsored by HFTP and the AHLA. Early adoption was permitted, and some operators began tracking the new categories during 2025 so that year-on-year comparatives would remain valid.
What are the main changes in the 12th edition?
The most significant additions are a payroll full-time-equivalent schedule, a schedule for annual mandatory brand and operator costs, expanded energy, water and waste reporting, discrete loyalty programme expense categories, executive lounge reporting, and a dedicated section for all-inclusive properties.
What is a good food cost percentage for a hotel?
Full-service hotels commonly run food cost between 28 and 35 percent of food revenue, varying with banquet mix and outlet type. The percentage matters less than the variance between theoretical cost calculated from recipes and actual cost from stock movement, which should stay under 2 percent of food revenue.
How do you calculate theoretical food cost?
Multiply the costed recipe for each menu item by the quantity sold from POS data, then total across items. Compare against actual food cost, calculated as opening stock plus purchases minus closing stock adjusted for transfers. The difference is controllable loss.
Does USALI apply to hotels in India?
USALI is a global reporting standard rather than a statutory requirement, and it does not replace Ind AS or Companies Act reporting. Indian hotels use it for management reporting, owner reporting and benchmarking, particularly where international brands, management contracts or institutional investors are involved.
USALI gives hotel finance a shared language. POS data gives it detail. Most properties have both and use neither fully, because the two never meet in the same system.
Connect them and the monthly F&B review changes character. Instead of explaining why food cost moved, the team can point at which items, which shifts and which functions moved it.
SaasWorx works with hotel groups across our hospitality practice on USALI-aligned chart of accounts design, POS and purchasing integration, and departmental reporting across multi-property estates.
