Walk any manufactured housing community's P&L and the water line tells you a story. The community pays one master-meter bill. Somewhere between that bill and the residents' invoices, money leaks — an unbilled vacant lot here, a slow underground drip there, a flat fee set in 2019 that no longer covers 2026 rates. Utility recovery is the most controllable margin lever an operator has, and it's lost or won in the billing system.

Which billing model to run — submetering, RUBS, flat fee — is a strategy-and-compliance decision we've covered in our RUBS vs submetering guide. And the general mechanics of meter data in the ERP are in NetSuite utility billing and meter management. This article is the piece between them: how utility recovery actually runs, month to month, for a manufactured housing portfolio inside NetSuite — reads to invoice lines to general ledger to the recovery-rate report that tells you whether it's working.

Key takeaways

• In NetSuite-based billing, a utility charge is an invoice line on the resident's monthly bill, mapped to its own utility recovery revenue account — so recovery is measurable per community without month-end allocation work.
• Submetered lots bill measured consumption (current read minus prior read, times rate); RUBS lots bill a formula share of the master bill. Both post the same way in the ledger.
• Recovery rate — utility income billed against utility expense paid — becomes a standing report per community per utility, and it's the number that exposes leaks, unbilled lots and meter drift.
• Read validation matters as much as read capture: misreads, rollovers and vacant-lot anomalies caught before billing are corrections; caught after, they're credit memos and angry calls.
• Where RUBS is used, restrictions vary by state and are changing — set the model with the compliance question answered first.

How does utility billing work in NetSuite for manufactured housing?

Utility billing in NetSuite for manufactured housing works by adding utility lines to each resident's monthly invoice: submetered homesites bill measured usage from meter reads, RUBS homesites bill a formula share of the master bill, and every line posts to its own utility recovery revenue account in the community's ledger.

One invoice per resident, with lot rent and utilities together; one ledger entry per line. That structure — utility recovery as first-class revenue lines rather than an offset buried in an expense account — is what makes everything in the rest of this article a report instead of a project.

The data layer: meters, reads, periods

Utility recovery runs on four records:

The hardware side — which meters, remote-read or walk-the-route — is its own decision, and vendors like SimpleSUB Water cover it well from the equipment angle. From the system's side, what matters is that every read lands against the right meter, the right period, and passes validation before it becomes money.

Validation is the unglamorous step that saves you. Before a read run bills, the system should flag: consumption wildly above the lot's history (a leak — or a misread), a current read below the prior one (meter rollover or transposed digits), usage on a vacant lot (someone's connected to something), and zero usage on an occupied lot (a stuck meter). Every one of those caught pre-billing is a quiet correction. Caught post-billing, it's a credit memo, a re-bill, and a resident who now double-checks every invoice you send.

Submetered lots: read to invoice line

The submetered calculation is deliberately boring: current read minus prior read, times the effective rate, plus any fixed service charge — one line on the resident's invoice, labeled with the consumption span so the resident can see the math. The prior read carries automatically from last period's billing, which is why the migration rule in our data-map guides says to carry final reads over: the first bill in a new system needs a real starting point.

Boring is the goal. When the calculation is generated from validated reads and effective-dated rates, nobody keys numbers, rate changes don't require editing fifty leases, and a resident's dispute is answered by showing the two reads and the multiplication.

RUBS lots: master bill to formula shares

Where lots aren't metered, RUBS allocates the community's master bill by formula — occupancy, lot count, or another documented basis. In the system, that means: enter the master bill (it's a vendor bill in AP anyway), apply the community's allocation formula, and generate each participating resident's share as an invoice line.

Two disciplines keep RUBS defensible. The formula is written down and applied by the system, not recalculated in a spreadsheet each month with judgment calls. And the allocation ties out: the sum of billed shares reconciles against the master bill, with the community's own share (common areas, vacant lots) explicitly absorbed rather than silently spread across residents. Whether RUBS is permitted for a given utility in a given state is a moving target — several states restrict it, and the rules change — so settle that with the decision guide and counsel before configuring anything.

Where RIOO fits here

NetSuite brings the invoicing and the ledger; it has no idea what a submeter read or an allocation basis is. RIOO adds the utility layer natively inside NetSuite for manufactured housing operators: meters tied to homesites, read capture with validation, rate tables, RUBS formulas, and the generated lines landing on the same resident invoice as lot rent — posting straight to the community's accounting ledger. The wider platform picture is in the mobile home park software guide.

The ledger view: recovery as revenue

Every utility line posts to a dedicated revenue account — Utility Recovery: Water, Utility Recovery: Sewer, and so on — per community, per entity. The master bills sit in the matching expense accounts. That pairing produces the number this whole operation is managed by:

Recovery rate = utility income billed ÷ utility expense paid, per utility, per community, per month.

No allocation journal at close, no analyst assembling it — the composition was captured at billing time, the same way lot rent, pass-throughs and ancillary income each sit on their own lines.

Reading the recovery-rate report

A recovery rate below where you expect it always has a cause, and the causes are findable because the data is granular:

• The gap is at specific lots: Sort billed consumption against the master meter: vacant lots showing usage, occupied lots showing none, one lot triple its history. Fix the meter, the leak, or the record.

• The gap is everywhere, evenly: Master-meter reads exceed the sum of submeter reads by a consistent margin — line loss or an underground leak between the master and the lots. That's a maintenance ticket, and the report is what justifies the dig.

• The gap is the model: Flat-fee or included-in-rent communities recovering a shrinking share as rates rise. The report turns "we should probably submeter Cedar Grove" from a hunch into a payback calculation.

Run it monthly, trend it quarterly, and it becomes the early-warning system for the second-largest expense line most communities carry.

How RIOO handles utility recovery on NetSuite

RIOO runs the full loop natively on Oracle NetSuite: meters and reads against homesites, validation before billing, submetered and RUBS lines generated onto the resident's monthly invoice, revenue posting by utility per community LLC, and the recovery-rate view standing ready in the same system that pays the master bills. To watch a read file become invoice lines and a recovery report, book a demo. For how this fits the wider platform decision, see the 2026 buyer's guide.

RIOO is a property management platform built natively on Oracle NetSuite, used by manufactured housing community operators to manage homesites, lot rent, park-owned homes, utility recovery and multi-entity accounting in one system.

Frequently asked questions

Q1. How are submeter reads billed in NetSuite?
Each homesite's meter read is validated, then billed as current read minus prior read, times the effective-dated rate — generated as a line on the resident's monthly invoice alongside lot rent, with the consumption span shown. The line posts to that community's utility recovery revenue account at billing time.

Q2. How does a RUBS allocation work in a NetSuite-based system?
The community's master utility bill is entered in accounts payable, a documented formula (occupancy, lot count or another basis) splits it across participating homesites, and each share is generated as an invoice line. The billed total reconciles against the master bill, with common areas and vacant lots absorbed by the community.

Q3. What is a utility recovery rate for a mobile home park?
Utility recovery rate is utility income billed to residents divided by utility expense paid to providers, tracked per utility and per community. Because billing lines and master bills post to paired revenue and expense accounts, the rate is a standing report rather than a month-end calculation.

Q4. Why is my utility recovery rate low?
Three usual causes: specific lots — vacant lots consuming, stuck meters, leaks at one home; system-wide loss — master-meter volume consistently exceeding the sum of submeters, pointing to line loss between master and lots; or the model — flat fees and included-in-rent arrangements falling behind rising utility rates.

Q5. Can utility charges and lot rent go on one invoice?
Yes — that's the standard structure in a NetSuite-based platform: one monthly invoice per resident carrying lot rent, utility lines, pass-throughs and fees, each line mapped to its own revenue account. The resident sees one bill; the P&L sees the composition.

Q6. Do I need to check state rules before billing utilities back?
Yes. Whether and how you may bill residents for utilities — particularly through RUBS — varies by state and utility type, and the rules are actively changing. Settle the compliance question for each community before configuring the billing model, and revisit it when you expand into a new state.