Standardization is often described as a benefit: fewer headaches, cleaner reporting, easier consolidation. What is missing from that conversation, industry-wide, is the actual mapping method, the specific decisions that make a standardized chart of accounts hold up across a portfolio that mixes select-service, full-service, and F&B-heavy properties without breaking USALI comparability. Below is the framework we use to think about it.
Why ‘Just Use the Same Chart of Accounts Everywhere’ Does Not Work
The naive approach to standardization is to pick one property’s chart of accounts and roll it out portfolio-wide. That fails immediately in a mixed portfolio, because a limited-service property with no F&B outlet and a full-service property with three restaurants and a banquet department do not have the same departmental structure to begin with. Forcing identical accounts onto structurally different properties either creates a pile of unused accounts at the simple properties or, worse, forces complex properties to collapse real departmental detail into fewer buckets than USALI comparability requires. The actual goal is not identical charts of accounts. It is a common structural framework that every property maps into consistently, at the level of granularity USALI expects, while allowing each property’s actual account list to reflect what it really operates.
The Three-Tier Mapping Framework
Tier 1: The USALI Schedule Structure (Fixed, Identical Everywhere).
Every property, regardless of type, maps its departmental P&L into the same USALI schedule structure, including Rooms, Food and Beverage, Other Operated Departments, Miscellaneous Income, and the undistributed expense schedules such as Administrative and General, Marketing, Property Operations and Maintenance, and Utilities. This tier never varies by property type. A select-service property with no F&B still has an F&B schedule; it is simply zero or near-zero, because the comparability USALI provides depends on every property reporting into the same schedule set, not on every property having populated every schedule.
Tier 2: The Department-to-Account Mapping (Varies by Property Complexity, Standardized by Rule).
Within each USALI schedule, the specific GL accounts a property uses can vary based on what it actually operates, but the mapping rule for how those accounts roll up is standardized. A full-service property might have separate GL accounts for three distinct F&B outlets, each rolling up into the F&B schedule. A select-service property might have one simple F&B account for a grab-and-go breakfast concession, rolling into the same schedule. Both are correct, because the rule (all F&B revenue and direct expense rolls into the F&B schedule, regardless of how many accounts a given property needs to represent its actual operation) is what is standardized, not the account count.
Tier 3: Cross-Property Comparability Accounts (Identical Everywhere, Regardless of Complexity).
A small set of accounts needs to be genuinely identical, not just mapped to the same schedule, because they are the basis for the owner-facing comparisons a portfolio actually gets used for: room revenue, room nights sold, ADR-driving accounts, and the labor cost accounts tied to cost-per-occupied-room calculations. If one property calls a line “Room Revenue, Transient” and another calls the equivalent line “Rooms, Retail Rate,” a portfolio roll-up can technically consolidate both into the Rooms schedule, but any drill-down comparison of transient rate performance across the two properties breaks, because the underlying accounts are not actually the same thing with different names. They need to be the same account.
Applying the Framework Across a Mixed Portfolio: Worked Example
A five-property portfolio includes two select-service properties, two full-service properties, and one property with a large banquet and conference operation.
- Tier 1: all five properties map into the same USALI schedule set. The select-service properties report near-zero F&B and Other Operated Departments. The banquet property reports substantial detail in F&B and a function-space sub-schedule.
- Tier 2: the banquet property maintains six F&B-related GL accounts across three outlets plus banquet food, banquet beverage, and banquet service charge. The select-service properties maintain one each. All roll into the same F&B schedule under the same mapping rule.
- Tier 3: room revenue, room nights sold, and the labor accounts feeding cost-per-occupied-room are identical account codes across all five properties, with no local variation, because those are the lines an asset manager pulls into a cross-property comparison every month.
The result is that an owner comparing RevPAR and cost-per-occupied-room across all five properties gets a clean, apples-to-apples number, because Tier 3 guarantees it, while each property’s actual books still reflect what it operates, because Tiers 1 and 2 do not force artificial uniformity where it is not needed.
Why This Holds Up Better Than a Single Rigid Chart
A portfolio that forces one identical chart of accounts onto every property either breaks down the first time it acquires a structurally different property, or accumulates workarounds, such as unused accounts or awkward account reuse, that make the standardized chart less accurate than a mixed one would have been. The three-tier approach standardizes exactly what needs to be identical for comparability, and only that, while leaving room for real operational differences everywhere else, which is what actually holds up as a portfolio grows and diversifies across brands and property types. We apply this three-tier mapping automatically across a portfolio’s chart of accounts in our platform, maintaining USALI schedule consistency and cross-property comparability without forcing identical accounts onto structurally different properties. This is also the foundation the folio-level exception detection covered in Hotel Folio Exceptions: The Revenue Leak Multi-Property Owners Rarely See relies on, since exception detection is only as reliable as the account structure underneath it.
The current version of this standard, the 12th Revised Edition of the Uniform System of Accounts for the Lodging Industry, was published by the Hospitality Financial and Technology Professionals association under the oversight of a Global Finance Committee jointly sponsored by AHLA and HFTP, with an adoption date of January 1, 2026. It remains the reference point this mapping framework is built to stay comparable against.
Summary Recap:
- Standardizing a chart of accounts across a mixed portfolio is not about making every property’s accounts identical. It is about a common structural framework every property maps into consistently.
- Tier 1 fixes the USALI schedule structure identically for every property. Tier 2 standardizes the mapping rule while allowing account-level detail to vary by property complexity. Tier 3 locks specific comparability accounts identically everywhere.
- This approach holds up as a portfolio grows and diversifies across brands and property types, unlike a single rigid chart forced onto every property.
- A clean, standardized chart of accounts is also the foundation that folio-level exception detection and intercompany reconciliation depend on.
Ready to see this in your own portfolio?
Schedule time with our team to walk through how Docyt applies this to your properties. Schedule a consultation with Docyt
