CAPEX vs OPEX in Hotel Development: Why FF&E and OS&E aren't That Simple.
CAPEX (Capital Expenditures) covers long-term investments capitalized on the balance sheet; OPEX (Operational Expenditures) covers the recurring costs of running the property day to day. In hotel projects, people shortcut this into "FF&E is CAPEX, OS&E is OPEX" a rule of thumb that holds often enough to feel true, and breaks often enough to cost real money.
Why the FF&E = CAPEX shortcut breaks
The split isn't defined by category, it's defined by the operator's capitalization threshold, the asset's expected lifespan, and the tax rules of the country you're building in. A Back-of-House piece of furniture can get expensed as OPEX. A large volume of "small" OS&E items : linens, tableware, even uniforms in some jurisdictions can cross the threshold and get capitalized instead. The category on the invoice doesn't decide the accounting treatment; the operator's own policy does.
That's exactly why Figurz builds scope of service limits into its tool a clear responsibility matrix, item by item, instead of a rule of thumb that only works until it doesn't. Start by testing the free version.
What CAPEX and OPEX actually mean in a hotel project
CAPEX covers investments expected to deliver value over multiple years, construction, major fit-out, and most FF&E. These are capitalized and depreciated over time rather than expensed in the year they're purchased.
OPEX covers the costs of keeping the hotel running, most OS&E, along with staffing, utilities, and maintenance. These are expensed as incurred, directly against operating income.
The distinction matters beyond bookkeeping: CAPEX is usually financed differently than OPEX (project loans vs. operating cash flow), and misclassifying an item can distort both the investment case and the day-to-day P&L.
Where the "FF&E = CAPEX" rule actually fails
Three situations break the shortcut most often:
Capitalization thresholds vary by operator and by country. An item that's capitalized under one brand's accounting policy might be expensed under another's, same item, different hotel, different treatment.
Bulk OS&E can cross into CAPEX. A large opening order of glassware, linens, or kitchenware can be capitalized as a single fit-out cost rather than expensed piece by piece, depending on how the operator's finance team structures the opening budget.
Custom or built-in FF&E can blur into construction. Millwork and bespoke joinery sit in a genuine gray zone between FF&E and building fabric and that classification affects which budget line absorbs the cost (see our dedicated article on millwork vs. bespoke FF&E).
Why this isn't just an accounting detail
Get the classification wrong at the feasibility stage, and the consequences aren't theoretical. A CAPEX budget built on the assumption that OS&E is "someone else's OPEX problem" underestimates the true cost of opening the property and by the time finance discovers the gap, the loan is already sized, the equity is already committed, and the only place left to cut is quality.
This is the same root problem behind FF&E and OS&E budgets in general: nobody upstream is incentivized to flag the gap early. The architect isn't measured on OPEX. The operator's finance team isn't in the room when FF&E gets specified. The investor sees a clean CAPEX number and assumes OPEX will sort itself out.
Investors who get an independent FF&E and OS&E budget before signing avoid discovering this gap after the loan is already sized.
The real fix: responsibility matrix, not category labels
The actual question isn't "is this CAPEX or OPEX" it's "who is responsible for specifying, budgeting, and procuring this item, and has that been written down anywhere." Most budget blowouts don't come from a wrong accounting entry; they come from an item nobody claimed ownership of, discovered three months before opening.
A clear scope of service, a responsibility matrix that assigns every line item to a party before the project starts, closes that gap regardless of which budget line the item eventually lands in. Architects working from a clear scope of service close this gap at the design stage, before it becomes a line item nobody owns.
That's exactly why Figurz builds scope of service limits into its FF&E and OS&E estimator: not just a number, but clarity on who owns what, before it becomes a last-minute scramble.
Are your CAPEX and OPEX budgets built on the same assumptions? Check it here!
