Ask an operator what their park-owned homes are worth and you'll usually get one of two answers: the number from a spreadsheet nobody has opened since tax season, or a shrug.
That's not a small gap. A community running thirty POH units is holding thirty depreciating capital assets — each with a cost, a book value, and a disposal event coming someday — and in most portfolios those assets live outside the accounting system entirely. The rent shows up in the books. The homes don't.
This guide covers how park owned home depreciation works in NetSuite: what the asset record holds, how the monthly schedule runs, the capitalise-or-expense call on rehabs, and what happens in the ledger the day you sell a home to a resident. It's written for the system side, not the tax side — the tax strategy content is already well covered by specialists like The MHP Accountant, and your CPA owns those decisions.
Key takeaways
- A park-owned home is a capital asset with a depreciation schedule and a book value — not a line on the rent roll. Most property management systems can only model the rent roll half.
- In NetSuite, each POH is a fixed asset record: cost, in-service date, useful life, method, accumulated depreciation and net book value, tied to the homesite it sits on.
- Rehab spend splits at the invoice: repairs hit expense, improvements capitalise onto the asset. A written policy applied at coding time is what keeps this defensible.
- Selling a home to a resident is a disposal event — the asset and its accumulated depreciation come off the books and the gain or loss is recognized, in the same system that starts billing the site as lot-rent-only.
- Because the asset register and the general ledger are one database, "what is our POH portfolio worth right now" is a report, not a quarterly archaeology project.
Why is a park-owned home a fixed asset?
A park-owned home is a fixed asset because the community owns a physical, depreciating structure with a purchase cost, a limited useful life and an eventual disposal — the accounting definition of a capital asset. The homesite under it produces lease revenue; the home itself is property, plant and equipment on the balance sheet.
That single distinction drives everything else in this article. A resident-owned homesite is simple: it earns lot rent, it has no book value, nothing depreciates. The moment the community owns the home, four accounting events enter the picture that a rent roll cannot represent: capitalisation, depreciation, improvement, disposal.
Miss them and two things go wrong. Your NOI is overstated, because the real cost of holding rental homes never hits the P&L in the periods it belongs to. And your balance sheet is fiction, because nobody can say what the rental portfolio is actually worth — which matters intensely the day a lender or a buyer asks.
Buyers do ask. The investment case for and against POH inventory is argued at length in operator circles (Keel Team's asset-or-liability piece is a good example of the genre). Whatever side of that argument you land on, the diligence request is the same: show me cost, accumulated depreciation and net book value per home. If the answer lives in a spreadsheet, expect a discount.
What the POH asset record holds in NetSuite
In NetSuite Fixed Assets Management, every park-owned home is an asset record. Not a row in a units table — a record built for exactly this job:
| Field | Why it matters |
|---|---|
| Acquisition cost | The capitalised basis: purchase price plus transport, set-up and make-ready costs |
| In-service date | Depreciation starts here, not at the purchase date |
| Useful life and method | Set by your written capitalisation policy; confirm tax treatment with your CPA |
| Accumulated depreciation | Runs automatically each period |
| Net book value | Cost minus accumulated depreciation — the number buyers and lenders ask for |
| Homesite link | Which lot the home occupies, connecting the asset to its revenue |
| Home identity | Serial/VIN, HUD label number, make, model, year, section count |
| Subsidiary | Which community LLC owns the asset — this is what makes multi-entity reporting work |
Two of those rows deserve a pause.
The homesite link is what generic fixed-asset tools miss. An accounting-only system can depreciate a home fine, but it doesn't know the home sits on Lot 47, earning $850 a month, in a community owned by your third LLC. NetSuite-based platforms connect the asset to the operating record, so the home's cost and its revenue finally live in the same view.
And the subsidiary field is quietly the most important one. Each community LLC holds its own assets in its own ledger, and the parent rolls them up — so "POH net book value across the portfolio" is one consolidated report even when the homes are spread across nine entities.
Setting it up: from purchase to first depreciation run
The flow is short, and every step is an ordinary NetSuite transaction:
- Buy the home: The vendor bill for the home — plus transport, set-up, skirting, tie-downs and initial make-ready — is coded to a capital account, not to repairs. Getting this right at the bill is the whole game; reclassifying at year-end is where errors breed.
- Create the asset: The asset record is generated from that purchase transaction, carrying the full capitalised cost. Identity fields (serial number, HUD label, section count) are added so the accounting record and the physical home can always be matched.
- Place it in service: When the home is ready for a resident, the in-service date starts the clock. A home sitting in rehab for three months doesn't depreciate yet.
- Let the schedule run: Each period, depreciation posts automatically to the owning LLC's ledger: depreciation expense on the P&L, accumulated depreciation on the balance sheet. Per home, per community, no spreadsheet.
One note on book versus tax. What we're describing is your book depreciation — the schedule your financial statements carry. Tax depreciation (MACRS lives, bonus depreciation, Section 179 elections) follows IRS Publication 946 and your CPA's judgment, and it will often differ from book. NetSuite can carry alternate schedules for that purpose, but the strategy is a tax decision, not a software one.
The rehab question: capitalise or expense?
A home comes back to you rough. You spend $14,000 making it rentable again. How much of that hits this month's P&L, and how much becomes part of the asset?
The answer decides your NOI. Expense everything and this month looks terrible while future months look artificially clean. Capitalise everything and you've flattered today's NOI while burying costs in the balance sheet. Both distortions show up eventually — usually in diligence, at the worst possible moment.
The working rule: a repair restores the home to its existing condition (a failed water heater, a leaking faucet, patching skirting); an improvement extends its life or adds value (a new roof, a re-plumb, a gut renovation). Repairs are expensed. Improvements capitalise onto the asset record and depreciate over their own life.
What makes this survivable at scale isn't the rule — it's where it gets applied. In a NetSuite-based flow, the AP clerk coding the rehab invoice picks the account then and there, guided by a written policy with a dollar threshold. The improvement lands on the home's asset record the week it happens. Compare that to the common alternative: everything coded to "R&M," and an accountant reconstructing capitalisations from memory the following March.
Write the policy down. Set a threshold. Apply it at the invoice. That sentence is most of what an auditor wants to see.
Where RIOO fits here
NetSuite Fixed Assets Management supplies the depreciation engine, but it has no idea what a homesite, a HUD label or a lot lease is. RIOO adds that layer inside NetSuite: the home's asset record connects to its homesite and its resident, rehab bills route to the right asset, and the same platform that runs the asset register also runs the lot rent billing and community operations around it. One system, both halves of the POH problem — the asset and the income.
Disposal: the day a resident buys the home
Selling a park-owned home to its resident is the standard endgame — the conversion play the whole industry runs. In the ledger, it's a disposal event with three parts:
- Retire the asset: Cost and accumulated depreciation come off the balance sheet.
- Recognize gain or loss: Sale price minus net book value, posted in the owning LLC.
- Reclassify the site: From the effective date, the homesite bills as lot-rent-only, and the community's revenue mix shifts toward the land income buyers pay full multiples for.
In NetSuite, those three entries are one disposal transaction against the asset record. Done in a spreadsheet, the same event requires someone to remember the sale happened, find the home's row, compute the gain, journal it manually, and separately fix the rent roll — five chances to get it wrong, repeated for every home in a conversion program.
If you're running conversions at any volume, this is the difference between a program you can report on ("14 homes sold this year, net gain of $61,000, average site now billing $540 in lot rent") and a program you reconstruct annually for the tax return.
Title transfer runs alongside all of this — a state DMV or Secretary of State process with its own paperwork — and the asset record is where the supporting documents belong, attached to the home they concern.
Book value across communities and LLCs
Here's the payoff for doing it in one system. At any moment, you can answer:
- What is the net book value of our entire rental-home portfolio, by community and consolidated?
- Which homes are fully depreciated but still earning?
- What did we capitalise into rehabs this year, versus expense?
- What gains did conversions generate, by entity?
Every one of those is a saved report against the property accounting ledger, because the asset register and the GL are the same database. For portfolios reporting to lenders or LPs, these numbers go straight into the reporting pack. For anyone contemplating a sale, they're the difference between a rent roll a buyer trusts and one they discount.
A point PMS can't produce this view, and it isn't a criticism — it was never built to. A units-and-leases data model has nowhere to put accumulated depreciation. That's the structural argument for running manufactured housing on an ERP, covered in our 2026 buyer's guide and in what NetSuite property management actually means.
How RIOO tracks park-owned homes on NetSuite
RIOO models the homesite and the home as separate records natively on Oracle NetSuite: the homesite carries the lot lease and its billing, and the park-owned home carries a real fixed-asset record — cost, in-service date, depreciation schedule, book value, identity and title documents — inside NetSuite Fixed Assets Management. Rehab invoices code to the asset at AP entry, disposals post as one transaction, and portfolio book value is a report across every community LLC. To see a POH lifecycle run end to end — purchase, rehab, depreciation, sale to a resident — book a demo.
Frequently asked questions
Q1. How is a park-owned home depreciated in NetSuite?
Each park-owned home is a fixed asset record in NetSuite Fixed Assets Management, with an acquisition cost, in-service date, useful life and method set by the operator's capitalisation policy. Depreciation posts automatically each period to the owning community LLC's ledger, building accumulated depreciation and net book value per home.
Q2. What costs are capitalised into a park-owned home?
The purchase price plus the costs of getting the home ready to earn: transport, set-up, skirting, tie-downs and initial make-ready. Later spending splits by policy — repairs that restore existing condition are expensed, while improvements that extend the home's life or add value are capitalised onto the asset.
Q3. What happens in the books when a resident buys a park-owned home?
The sale is a disposal: the home's cost and accumulated depreciation come off the balance sheet, the gain or loss (sale price minus net book value) is recognized in the owning LLC, and the homesite reclassifies to lot-rent-only billing from the effective date. In NetSuite this posts as one disposal transaction.
Q4. Do book depreciation and tax depreciation differ for park-owned homes?
Usually, yes. Book depreciation follows the operator's written policy and appears in the financial statements; tax depreciation follows IRS rules — MACRS lives, bonus depreciation and Section 179 elections per IRS Publication 946 — and is a CPA decision. NetSuite can carry alternate schedules so both views exist without a side spreadsheet.
Q5. Why can't a regular property management system track POH depreciation?
Conventional property management systems model units with leases, which captures rent but has no structure for cost, useful life, accumulated depreciation or disposal. Operators end up tracking home assets in spreadsheets, separated from the ledger. A fixed-asset register inside the ERP keeps the asset and its income in one system.
Q6. Does a vacant park-owned home still depreciate?
A home already in service continues to depreciate while vacant — book depreciation doesn't pause between residents. A newly acquired home that hasn't yet been placed in service (still in transport or rehab) hasn't started depreciating, because the schedule begins at the in-service date, not the purchase date.
Q7. How do I see the total book value of my rental home portfolio?
When each home is an asset record in the ERP, portfolio net book value is a standard report: cost minus accumulated depreciation, by home, by community and consolidated across LLCs. If homes are tracked outside the accounting system, that number has to be rebuilt manually — which is why so few operators can produce it on request.