Buy four communities and you don't have four properties. You have four LLCs, probably a management company, maybe a holding entity above all of it — and a finance person spending the second week of every month copying trial balances into a consolidation spreadsheet.

The entity structure isn't the problem. It exists for good reasons, and no attorney is going to tell you to collapse it. The problem is that most property management software has no concept of a legal entity at all, so the structure your lawyer built and the software your team uses never meet. The gap between them is filled with spreadsheets.

This article covers how that structure runs in NetSuite OneWorld: one subsidiary per community LLC, resident billing inside each one, intercompany management fees that eliminate on consolidation, and a close that produces entity-level and portfolio-level financials from the same transactions.

Key takeaways

• Manufactured housing portfolios hold each community in its own LLC for liability isolation and financing — a structure attorneys recommend and lenders expect.
• In NetSuite OneWorld, each LLC is a subsidiary with its own ledger; residents are billed by the entity that owns their community, not by an abstract "portfolio."
• Intercompany management fees post in both entities at once and eliminate automatically on consolidation, so the portfolio view never double-counts.
• The consolidated close stops being a spreadsheet exercise: entity financials for the lender, consolidated financials for the owner, one set of transactions behind both.
• Below roughly a handful of entities, OneWorld can be more structure than you need — the honest threshold question is at the end of this article.

Why do manufactured housing operators use one LLC per community?

Operators hold each manufactured housing community in a separate LLC to isolate liability — a claim arising at one community cannot reach the assets of the others — and because lenders financing an individual community typically require a single-asset entity to hold it. The result is a portfolio of legal entities, each needing its own books.

The reasoning is well covered on the investment side: Keel Team's piece on LLCs as risk-reduction firewalls makes the liability case, and The Real Estate CPA's pros-and-cons rundown covers the cost side honestly — every entity you add is another tax return, another bank account, another set of books.

That last item is the one this article is about. "Another set of books" is trivial advice to give and painful advice to live with. At four entities it's an annoyance. At fourteen it's a full-time job. At forty it's a department — unless the system underneath actually understands entities.

What is NetSuite OneWorld?

NetSuite OneWorld is the multi-entity edition of the NetSuite ERP: it runs any number of subsidiaries — each with its own general ledger, chart of accounts and reporting — inside one system, and consolidates them automatically, including the intercompany eliminations that keep the roll-up honest.

Oracle built it for global companies with subsidiaries in different countries. A manufactured housing portfolio uses maybe a tenth of that machinery — no currencies to translate, no foreign tax regimes — but the tenth it uses is exactly the part that spreadsheet consolidation gets wrong: entity-level ledgers, intercompany transactions, and a consolidation layer that computes rather than copies.

We've written about the general real-estate case in NetSuite multi-entity management for property groups. What follows is the manufactured housing version — which turns out to be the strongest version of the argument, because almost no other asset class fragments into as many small entities as MH does.

Mapping the portfolio: real world to OneWorld

The mapping is nearly one-to-one, which is why this works:

Each community subsidiary owns what it should own: its homesites, its lot leases, its residents' receivables, its bank account, its park-owned home assets, its share of payroll and expenses. Nothing is pooled that the legal structure keeps separate.

That last acquisition row matters more than it looks. When you close on community number nine, the accounting setup is "add a subsidiary" — the chart of accounts, billing logic and reporting come with it. Operators who consolidate in spreadsheets know the alternative: every acquisition makes the monthly workbook one tab bigger and one degree more fragile.

Residents are billed by the entity that owns their community

This is the detail that separates real entity accounting from cosmetic "property groups." When lot rent bills go out, each resident's invoice is issued by the subsidiary that owns their community — the receivable sits in that LLC, the payment lands in that LLC's bank account, the revenue posts to that LLC's P&L. [SERIES-LINK: link "lot rent billing" here to /blog/lot-rent-billing-in-netsuite once live.]

Why care? Three audiences will eventually check:

• The lender: A loan secured by Cedar Grove wants Cedar Grove's financials — real ones, produced from Cedar Grove's own ledger, not carved out of a pooled P&L by allocation.

• The auditor: Commingled cash between entities is one of the fastest ways to weaken the liability protection the LLCs exist to provide. Books that respect entity boundaries are evidence the operation does too.

• The buyer: When you sell one community out of the portfolio, its standalone books already exist. No reconstruction project, no "quality of earnings" surprises.

The same holds for what each entity owns. Park-owned homes sit as fixed assets in the subsidiary that holds their community, depreciating into that entity's P&L. [SERIES-LINK: link "fixed assets" here to /blog/park-owned-homes-fixed-assets-netsuite once live.]

Where RIOO fits here

OneWorld provides the entity machinery; it doesn't know what a homesite or a lot lease is. RIOO adds the manufactured housing layer on top — communities, homesites, residents, lot leases, POH records — each tied to its owning subsidiary, so the operating side and the entity side stay aligned without anyone mapping between them. The 2026 buyer's guide covers where this sits in the wider platform comparison; the short version is that no point PMS carries a subsidiary structure at all.

Intercompany fees and eliminations

Most MH portfolios run a management company that charges each community a fee — commonly a percentage of collections. In a spreadsheet world this is where consolidation quietly breaks, because the fee is revenue in one entity and expense in another, and the roll-up has to remember to cancel them against each other. Forget once, and portfolio income is overstated by every management fee charged.

In OneWorld the fee is an intercompany transaction: it posts as expense in the community LLC and revenue in the management company simultaneously, tagged as intercompany. At consolidation, tagged pairs eliminate automatically. The parent's view shows what the portfolio earned from the outside world — resident payments in, vendor payments out — with internal transfers netted to zero, every month, without anyone remembering anything.

A worked month, three communities:

(Illustrative figures, not benchmarks — your fee structure and expense ratios are your own.) The point is the right-hand column: it computes. The $11,855 the management company "earned" and the $11,855 the communities "spent" cancel, because they were the same money moving between your own pockets.

The consolidated close

With entity billing and intercompany handled, the close changes shape. Instead of exporting three, nine, or forty trial balances into a workbook, the sequence is: close each subsidiary's period, run the consolidation, review. Entity financials and the portfolio roll-up come from the same transactions, so they cannot disagree with each other — the failure mode where the fund P&L says one thing and the sum of the entities says another simply has no mechanism.

Reporting follows the same shape, in both directions. Downward: any community's standalone P&L, balance sheet and property accounting detail on demand. Upward: consolidated statements for owners and LPs, plus the cross-entity views — NOI by community, collections rate by community, occupancy against revenue — that only exist when every entity's data lives in one schema. (More on the reporting side in real-time reporting for real estate businesses using NetSuite.)

When you don't need OneWorld

Honesty section. If you operate one community in one LLC — or two entities you can hold in your head — a subsidiary structure is more machinery than the problem requires, and a well-run single-entity setup with clean books will serve you fine for years. The complete lot rent guide plus disciplined bookkeeping is the honest prescription at that size.

The threshold to watch isn't a number of communities; it's the first month someone spends more than a day assembling the portfolio view, or the first lender who asks for entity financials your system can't produce without surgery. Operators who cross that line describe the same arc: the spreadsheet was fine, until the quarter it wasn't, and by then migrating was harder than it would have been two acquisitions earlier. If you're buying, structure for where you'll be at the end of your acquisition pipeline, not where you are today.

How RIOO runs MH portfolios on NetSuite OneWorld

RIOO is built natively on NetSuite, so a manufactured housing portfolio on RIOO gets the OneWorld structure as its foundation: one subsidiary per community LLC, residents billed by their owning entity, park-owned homes held as fixed assets where they legally sit, intercompany management fees eliminating on consolidation, and lender-ready entity financials alongside the portfolio roll-up — with the community operations layer running in the same system. To see a multi-entity close run live, book a demo.

Frequently asked questions

Q1. What is NetSuite OneWorld used for in manufactured housing?
NetSuite OneWorld runs each community LLC as its own subsidiary with its own general ledger, bills residents from the entity that owns their community, and consolidates the whole portfolio automatically — including eliminating intercompany management fees — so entity-level and portfolio-level financials come from the same transactions.

Q2. Why does each mobile home park need its own LLC?
Attorneys recommend one LLC per community so a liability claim at one property cannot reach the others, and lenders financing a single community typically require a single-asset entity to hold it. The trade-off is administrative: each LLC needs its own books, bank account and tax return.

Q3. How are management fees between my LLCs handled?
As intercompany transactions: the fee posts as an expense in the community LLC and revenue in the management company at the same time, tagged as intercompany. On consolidation the tagged pair eliminates automatically, so the portfolio view never counts money you paid yourself as income.

Q4. Can I get financials for just one community LLC?
Yes — that's the point of the subsidiary structure. Each community's P&L, balance sheet and transaction detail exist in its own ledger, so a lender or a buyer asking for one entity's standalone financials gets real statements, not numbers allocated out of a pooled portfolio.

Q5. What happens when I acquire another community?
The new community's LLC is added as another subsidiary: it inherits the chart of accounts, billing logic and reporting structure, and its residents, homesites and assets are loaded into that entity. The consolidation picks it up automatically — no new workbook tab, no new system.

Q6. Do small operators need NetSuite OneWorld?
Not always. An operator with one or two entities can run clean books without a subsidiary structure. The threshold is practical: when assembling the portfolio view takes days, or a lender asks for entity financials your system can't produce, the entity structure has outgrown the software underneath it.

Q7. How is this different from "property groups" in regular property management software?
Property groups are labels on a shared ledger — useful for filtering reports, invisible to the legal structure. Subsidiaries are separate ledgers with their own receivables, bank accounts and balance sheets, matching the actual LLCs. Only the second kind produces entity financials a lender or auditor will accept.