There's a week every quarter that fund CFOs don't put on their LinkedIn. The reporting week. Trial balances exported from wherever they live, pasted into the master workbook, eliminations done by hand, operating metrics chased down from three community managers, the whole thing PDF'd at 11pm and sent to LPs with a silent prayer that nobody reconciles page 4 against page 11.

The pack itself isn't the problem — investors are entitled to every page of it. The problem is the word assembled. An assembled pack is rebuilt from fragments every quarter; a generated pack is printed from a ledger that already contains everything. This article is the anatomy of the generated version: what goes in an MH fund's reporting pack, and where each page comes from when the portfolio runs on NetSuite.

Key takeaways

• The pack has three layers: financial statements (entity and consolidated), operating metrics (the MH-specific numbers), and capital activity — and all three can source from one system.
• Consolidated statements are trustworthy only if intercompany fees eliminate properly; that's ledger machinery, not spreadsheet discipline.
• The operating layer is where MH funds differ from other real estate: NOI per homesite, physical vs economic occupancy, collections rate, utility recovery and POH book value.
• The drill-down property is the real upgrade: any number an LP questions traces to the transactions behind it in minutes, not days.
• Lenders and LPs want different slices of the same truth — two views, one dataset, never two datasets.

What is an investor reporting pack for an MH fund?

An investor reporting pack is the recurring bundle a manufactured housing fund delivers to its LPs and lenders: entity and consolidated financial statements, portfolio operating metrics — occupancy, NOI per homesite, collections, utility recovery, park-owned home value — and capital activity, typically quarterly for investors and monthly or quarterly for lenders per covenant.

Every fund produces some version of it. The difference between funds is whether producing it takes an afternoon or a week, and whether the numbers survive scrutiny.

The pack, page by page

Layer one: financial statements that agree with each other

The statements layer stands or falls on one thing: the consolidated numbers and the entity numbers must be the same facts at two zoom levels. That happens naturally when each community LLC is a subsidiary with its own ledger and the parent consolidates with intercompany management fees eliminating automatically — the multi-entity structure this series has covered in depth. It cannot happen reliably when the consolidation is a workbook, which is why assembled packs fail their first serious reconciliation: the fund P&L says one thing, the sum of the entities says another, and the difference is someone's forgotten elimination.

The NetSuite financial core treats the entity statements and the consolidation as views of the same transactions — which is the whole trick.

Layer two: the numbers only an MH pack carries

Generic fund software can print a P&L. What it can't print is the operating layer, because the operating layer lives in manufactured housing records:

• NOI per occupied homesite — the portfolio's comparison metric, computable per community when revenue and expense post per entity (the NOI mechanics are their own topic).

• Physical vs economic occupancy — filled homesites versus collected revenue against gross potential. The gap between the two numbers is itself the story: filled lots that aren't paying.

• Collections rate and aging trend — straight from the receivables, because lot rent bills as real invoices.

• Utility recovery rate — billed recovery against utility spend, per community.

• POH book value and conversion progress — home count, cost, accumulated depreciation, net book value, plus conversions closed and gains recognized this period. This schedule is the one buyers and lenders trust least when it arrives from a spreadsheet — and the one that impresses most when it ties to a fixed-asset register.

Each of those exists as a standing report only because the underlying events — invoices, reads, payments, disposals — were captured as structured transactions all quarter. The pack is a byproduct of running the business in one system, not a separate production.

Layer three: capital activity — with an honest boundary

Contributions, distributions and capital balances per investor sit in the fund entity's equity accounts and report cleanly from the ledger. The honest boundary: complex waterfall and promote calculations — tiered hurdles, catch-ups, clawbacks — are usually modeled in dedicated tools or by fund administrators, not computed inside a general ledger. The right architecture is ledger-as-source-of-truth for the cash and balances, waterfall logic fed from it. A vendor telling you their PMS "does waterfalls" deserves the six-questions treatment from earlier in this series.

Where RIOO fits here

RIOO's contribution to the pack is that the MH operating layer and the financial layer are the same system: homesites, leases, billing, utility reads, POH assets and collections all post natively into the NetSuite ledgers that produce the statements — so the dashboards and reports the pack draws from are live views, not quarter-end constructions. The real-time reporting piece covers that architecture generally.

Two audiences, one dataset

Lenders and LPs read different packs, and the temptation is to maintain them separately — which eventually produces the career-limiting moment where the lender's occupancy and the LP deck's occupancy disagree. The discipline: one dataset, two views. The lender gets their collateral entity's statements and covenant certificate; the LPs get the consolidated story and community scorecards; both are filters on the same ledger, so they cannot contradict each other. When a covenant ratio is defined once as a saved calculation, the quarterly certificate is a print job.

The drill-down property

Here's what actually changes the LP relationship. An investor emails: "Community-level NOI at Riverbend dropped 9% in Q3 — why?" The assembled-pack answer involves finding the analyst who built the tab. The generated-pack answer is a drill: Riverbend's P&L → the expense line that moved → the vendor bills behind it → "two water-line repairs in August, here are the invoices." Twenty minutes, with receipts. Funds underestimate how much LP confidence is built not by the pack itself but by the speed and precision of answers to questions about it.

When a spreadsheet pack is honestly fine

One community, a handful of friends-and-family investors, no institutional LPs, no covenant reporting: a clean quarterly spreadsheet and a sincere cover note serve perfectly well, and standing up fund-grade machinery would be ceremony. The generated pack earns its keep at the same threshold everything in this series does — multiple entities, outside capital with expectations, lenders with covenants, an audit on the calendar. The buyer's guide maps that decision.

How RIOO generates the pack on NetSuite

RIOO runs the manufactured housing operation natively on Oracle NetSuite, so the reporting pack's three layers — entity and consolidated statements with eliminations applied, the MH operating metrics from live records, and capital activity from the fund entity — generate from one ledger, with every number drillable to its transactions. To see a quarter's pack produced in an afternoon, Book a demo. Platform context: the mobile home park software guide.

Frequently asked questions

Q1. What should an MH fund's investor reporting pack include?
Three layers: financial statements — consolidated for LPs, entity-level for lenders — with intercompany eliminations applied; manufactured housing operating metrics such as occupancy, NOI per homesite, collections rate, utility recovery and park-owned home book value; and capital activity showing contributions, distributions and balances.

Q2. How often do LPs and lenders expect reporting?
Quarterly is the standard cadence for LP packs, while lenders typically require monthly or quarterly statements and covenant certificates as their loan agreements specify. The practical requirement is that both draw from the same dataset, so the two audiences never receive contradicting numbers.

Q3. What makes consolidated fund financials trustworthy?
Entity statements and the consolidation must be the same transactions at two zoom levels, with intercompany management fees eliminating automatically. When each community LLC keeps its own ledger and the parent consolidates in-system, the fund P&L and the sum of the entities cannot disagree — the failure mode of workbook consolidation.

Q4. Which operating metrics belong in a manufactured housing pack?
NOI per occupied homesite, physical versus economic occupancy, collections rate with aging trend, utility recovery rate per community, and the park-owned home schedule — count, cost, net book value and conversion activity. Each is a standing report when the underlying events post as structured transactions.

Q5. Can the general ledger handle LP waterfall calculations?
Cash movements and capital balances live cleanly in the fund entity's equity accounts, but tiered waterfall and promote logic — hurdles, catch-ups, clawbacks — is usually modeled in dedicated tools or by fund administrators, fed from the ledger. The ledger is the source of truth; the waterfall consumes it.

Q6. What is the fastest sign of a weak reporting pack?
A number that can't be traced. When an investor questions a figure and the answer requires finding whoever built the spreadsheet tab, the pack was assembled; when the figure drills to the vendor bills or invoices behind it in minutes, it was generated — and that response speed is what builds LP confidence.