Somewhere in every MH fund's first audit, the same exchange happens. The auditor asks about ASC 842. The controller's stomach drops, picturing thousands of lot leases each needing a right-of-use asset on the balance sheet. And then the auditor explains the part nobody had told the operator: for the leases you were worried about, 842 mostly leaves you alone.
The standard bites manufactured housing operators in a different place than they expect. This article maps where — the lessor side you run at scale, the lessee side that actually lands on your balance sheet, and how both live in NetSuite so the audit conversation is a report review instead of a scramble.
One framing note before anything else: this is orientation, not accounting advice. The treatment of your specific leases is a conversation between your controller and your auditor — this page exists so you walk into that conversation knowing the shape of it.
Key takeaways
- MH operators wear two hats under ASC 842: lessor on thousands of lot leases to residents, lessee on the handful of leases the business holds (offices, equipment, occasionally the ground under a community).
- The lessor side is the relief: lot leases to residents are typically operating leases, and the lessor keeps recognizing rental income — no right-of-use assets for resident leases on your balance sheet.
- The lessee side is where balance sheets change: leases you hold generally go on-book as a right-of-use asset and lease liability, with a short-term exemption for 12-month-or-less commitments.
- Fixed escalations in longer lot leases raise the straight-line rent question — recognizing income evenly across the term rather than as billed.
- The audit deliverable is a complete lease inventory with terms and escalations documented — which is a database property, not an accounting heroic.
Does ASC 842 apply to mobile home park lot leases?
ASC 842 applies, but gently: the community is the lessor on its lot leases, and lessor accounting for operating leases keeps rental income recognition largely as it was — the operator does not put right-of-use assets on its balance sheet for leases where residents rent homesites. The standard's balance-sheet impact falls on leases the operator holds as lessee.
That answer-first paragraph is the one to remember. Now the two hats, one at a time. (For the standard's full machinery — classification tests, discount rates, disclosures — a dedicated reference like FinQuery's ASC 842 guide covers the general case well; our lease accounting primer covers the property-management basics.)
Hat one: lessor on every homesite
Your core business — leasing land to residents for lot rent — sits on the lessor side of 842, and lessor operating-lease accounting is deliberately close to the old world: the land stays on your books as land, the lease income recognizes over the lease term, and the resident's obligation doesn't become an asset you capitalize.
Two things still matter operationally:
-
Classification is a test, not an assumption
Lot leases to residents — month-to-month or annual, for land, with no transfer of ownership — land in operating-lease territory in the ordinary case. But "we assumed" is not a workpaper; the classification logic gets documented once, applied consistently, and shown to the auditor. Unusual arrangements (very long fixed terms, purchase features) get individual attention. -
Escalations raise the straight-line question
A month-to-month lease billed at the current rate is simple. A multi-year lot lease with fixed escalations written in — $500 in year one, $520 in year two — is where GAAP asks whether income should recognize evenly over the term rather than as billed, with a deferred rent balance carrying the difference. We've covered the mechanics in what straight-line rent is and how it's calculated; whether it's material for your portfolio (given how many MH leases are short-term) is exactly the kind of call your auditor weighs in on. The system's job is to make either treatment computable — which it is, when every lease's terms and escalations are structured data.
Hat two: lessee on the leases you forget you have
Here's where 842 changed balance sheets. As a lessee, the operator generally books leases longer than twelve months as a right-of-use (ROU) asset and a matching lease liability. Walk the portfolio and the list is longer than expected:
| Lease you hold | 842 posture (ordinary case — confirm each with your auditor) |
|---|---|
| Ground lease under a community whose land you don't own | The big one — long-term, on-balance-sheet, potentially large numbers |
| Regional office space | On-book if term exceeds 12 months |
| Equipment: mowers, trucks, office copiers | On-book past 12 months; the short-term exemption covers true short rentals |
| Solar, cell tower or billboard ground positions you grant | Careful — you may be lessor there, a happy income story |
| Month-to-month arrangements | Short-term exemption typically available — an accounting policy election |
The ground-lease row deserves its own sentence: communities operated on leased land exist, and a 40-year ground lease under an operating community is a material ROU asset and liability with amortization schedules and disclosure obligations attached. If that's you, this is the single biggest 842 item in your books.
Where RIOO fits here
NetSuite carries lease accounting machinery within its financial core — schedules, amortization, the lessee-side postings — alongside Fixed Assets Management. What RIOO adds is the manufactured housing lessor side at scale: every lot lease as a structured record with terms, escalations and billing history in the same system, per community LLC. The result is that both hats live in one ledger — the ROU schedules for the leases you hold, and the complete, queryable inventory of the thousands you grant — posting into the same accounting core.
What the auditor actually asks for
Strip away the standard's vocabulary and the audit request is a data request:
- A complete lease inventory — every lease you hold and a summarized view of leases you grant, with none missing. ("Completeness" is the word auditors use when they suspect the copier lease lives in a drawer.)
- Terms, documented — start, end, renewal options, escalations, for each.
- The classification memo — why lot leases are treated as they are, applied consistently.
- Schedules for lessee leases — ROU amortization and liability runoff, tying to the balance sheet.
- Disclosure data — maturity analyses and lease cost detail for the footnotes.
Every item on that list is painful exactly in proportion to how scattered the lease data is. An operator whose lot leases are structured records and whose held leases are scheduled in the same system answers with saved reports. An operator with leases in filing cabinets answers with a six-week project, annually.
The honest sizing note
For a small operator — one community, land owned, month-to-month resident leases, no audit requirement — ASC 842 is close to a non-event, and building compliance machinery for it would be solving a problem you don't have. The standard becomes real alongside the things that make audits real: a fund structure, institutional LPs, lender covenants requiring GAAP financials, a ground lease. Which is the same threshold at which the rest of this series' ERP argument turns on — the buyer's guide maps that decision honestly.
How RIOO supports lease accounting on NetSuite
RIOO keeps both sides of 842 in one system on Oracle NetSuite: lot leases as structured lessor records — terms, escalations, classification documentation, billing history — across every community LLC, and the lessee-side schedules for ground, office and equipment leases running in the same ledger that produces the financial statements and footnote data. To see the lease inventory an auditor dreams about, Book a demo. Platform context: the mobile home park software guide.
Frequently asked questions
Q1. Do lot leases to residents go on my balance sheet under ASC 842?
No — as the lessor on operating lot leases, the community keeps the land on its books and recognizes rental income over the lease term. Right-of-use assets and lease liabilities are a lessee-side requirement, applying to leases the operator holds rather than the leases it grants to residents.
Q2. Which of my leases does ASC 842 actually put on the books?
Leases you hold as lessee with terms beyond twelve months: ground leases under communities on leased land, office space, and longer equipment leases. Each generally books as a right-of-use asset and matching liability with an amortization schedule. Month-to-month and short-term commitments typically qualify for the short-term exemption.
Q3. When does straight-line rent apply to lot leases?
When a lease has fixed escalations over a multi-year term, GAAP asks whether income should recognize evenly across the term rather than as billed, with the difference carried as deferred rent. Many MH lot leases are short-term and unaffected; whether it's material for longer leases is a call to make with your auditor.
Q4. What does an auditor request for ASC 842 compliance?
A complete lease inventory, documented terms and escalations for each lease, the classification rationale applied consistently, amortization and liability schedules for lessee leases that tie to the balance sheet, and the maturity and cost data behind the footnote disclosures. All of it is a data problem before it's an accounting problem.
Q5. Does a small mobile home park need to worry about ASC 842?
Usually very little: an owner-operator with owned land, month-to-month resident leases and no audited financials has almost no 842 surface. The standard becomes significant alongside audits, GAAP-basis lender or investor reporting, or a ground lease under a community — the points where books have to hold up to outside scrutiny.
Q6. Can NetSuite handle both the lessor and lessee sides for an MH portfolio?
Yes — NetSuite's financial core carries the lessee-side schedules and postings, and a manufactured housing layer on top holds every lot lease as a structured lessor record with terms and escalations. Both sides then live in the ledger of the entity they belong to, producing statement and disclosure data from one system.
.svg)
.svg)
.svg)
