Chapter 35Converting a Hotel From Non-USALI Reporting to USALI

The owner group acquires Riverstone Hotel — profitable, independent, with its own statutory ledger, monthly P&L, PMS report, and spreadsheet dashboard. The acquisition model assumes it can be compared with Blue Moon within three months.

The first close suggests Riverstone has a stronger ADR and lower overhead. But breakfast packages sit inside Rooms Revenue, destination fees sit inside Rooms, banquet contracts post as one line, contract room attendants are invisible in the labor report, and the P&L's "EBITDA" line still contains depreciation. Amara refuses to just rename accounts. She asks Riverstone to prove the source, home, statistic, and reconciliation for every material line.

“A USALI conversion is complete only when the operating event, source system, account, statistic, policy, bridge, and action owner remain connected after go-live.”

Questions this chapter helps answer

• Why is converting a hotel to USALI more than renaming the chart of accounts?
• What should a legacy-to-USALI mapping matrix contain before cutover?
• Why are a clean-base date and parallel close important when historical data or definitions cannot be fully reconstructed?

What this chapter gives you

• How to scope, map, test, and cut over a USALI conversion without confusing a new chart of accounts with a real management system
• Why a renamed report isn't the same thing as a comparable report
• The proof-of-source standard that must be met before any acquired property is trusted for benchmarking

Key concepts

• USALI conversion
• legacy mapping
• source cleanup
• statistics conversion
• clean-base date
• parallel close
• cutover
• training
• post-go-live governance

Records built for tax filing and payment control can be perfectly compliant while still being unusable for a fair operating comparison.

Hotel Financial Reporting in Practice · Manish Gupta, CA