Collections in a manufactured housing community is a strange discipline, because the textbook playbook — pressure fast, evict fast, re-let fast — is written for apartments, and almost none of it transfers. Your delinquent resident owns the home sitting on your lot. Moving it would cost them more than the arrears. They aren't going anywhere, you don't want them to, and an eviction that ends with an abandoned home on Lot 12 is a loss for everyone including you.

Which means MH collections is really a workflow problem: catch the miss early, make contact predictable, document everything, and give a resident who hit a bad month a structured way back to current. Rental delinquency is common enough that the CFPB studies it as a national dataset; what separates operators isn't whether misses happen, it's whether the response is a system or a mood.

Here's that system, as it runs in NetSuite.

Key takeaways

• The workflow starts with an AR you can trust: every unpaid lot rent invoice ages automatically by resident and community, so "who's behind" is a report, not an investigation.
• The ladder — reminder, late fee, contact, plan, formal notice — runs on configured day-triggers, identically for every resident, which is both an efficiency and a fair-housing protection.
• Late fees are policy objects: grace days and amounts are set per community to match its state's rules, applied by the system, and posted to their own income line.
• Payment plans belong in the system, not in a manager's memory — documented terms, tracked installments, automatic flag on a broken promise.
• Every step timestamps itself, so if a case ever reaches formal proceedings, the record of notices and contacts already exists.

What is a lot rent collections workflow?

A lot rent collections workflow is the automated sequence a billing system runs when a resident's invoice goes unpaid: the receivable ages, reminders and dunning notices send on configured days, late fees apply per the community's policy, contacts and payment plans are logged, and unresolved cases escalate to formal notice — every step recorded with a timestamp.

The strategy questions underneath — how much delinquency to tolerate, when compassion beats escalation, what a healthy collections rate looks like — deserve their own treatment. This article is the machine that executes whatever strategy you choose.

The foundation: aging you don't have to build

Everything downstream depends on one property of the billing architecture: when lot rent is billed as a real invoice in the ledger, an unpaid balance is just an open receivable with an age. The AR aging report — current, 1–30, 31–60, 61–90, over 90, by resident, by community, by entity — exists without anyone maintaining it.

Contrast the spreadsheet version: someone marks payments against a list, someone else keeps the "who's behind" tab, and the two disagree by the second week. Every collections conversation then starts with an argument about the number instead of a plan for the balance.

One separation matters for operators running home financing: a resident's note balance ages on its own track, not blended into rent AR — being behind on the home and behind on the lot are different problems with different remedies. That split is covered in the chattel note servicing guide.

The ladder

The specific days and amounts below are placeholders — every community configures its own, after the state-law homework on grace periods, fee limits and notice requirements is done. The point is the shape:

Two properties make the ladder work. It runs on triggers, not attention — nobody has to remember Day 10, so no one slips through and no one is singled out. And it runs identically for everyone, which is quietly one of your best fair-housing protections: when the sequence is system-driven, "why did she get a call and he get a notice" has a documented, neutral answer.

Late fees done right

A late fee is three decisions — grace period, amount or percentage, and any cap — and all three vary with state law and community policy, so they live as configuration, not as cashier discretion. When the trigger hits, the fee posts as a line on the resident's account, into its own Late Fee Income account. That last detail sounds like accounting fussiness; it isn't. Late fee income is a diagnostic — a community whose late fee line grows quarter over quarter has a collections problem or a fee-dependence problem, and either is worth catching. The complete lot rent guide covers the fee-setting side.

One practice worth stealing: waive strategically, but log the waiver. A first-miss waiver for a ten-year resident is good judgment; the system should record that it happened, who approved it, and why — so generosity stays a policy, not a leak.

Payment plans that survive the month

The most valuable tool on the ladder is the structured plan: arrears split over an agreed number of months, paid alongside current rent. What kills payment plans is informality — a hallway agreement the manager remembers one way and the resident another, invisible to whoever runs the books.

In the system, a plan is a record: total arrears, installment amount, dates, and the resident's acknowledgment. Installments track against it; current rent stays current; a missed installment flags the account the day it happens rather than surfacing three months later as a bigger hole. Residents can watch the balance fall through the resident portal — visible progress is itself a driver of completion.

Where RIOO fits here

NetSuite supplies the receivables, aging and dunning machinery; what it can't know is manufactured housing's context — the grace and notice rules that differ by community, the rent-versus-note split, the manager who needs a call task on Day 15. RIOO configures the whole ladder natively on NetSuite: triggers per community, fees per policy, plans as records, notices generated from real account data, and every payment landing through the same collections flow into the same ledger.

Formal notices and the record that saves you

Most cases never reach a statutory notice. For the few that do, what matters is that the notice is generated from the record — the actual balance, the actual dates — and that its service is documented on the account, because manufactured housing proceedings are unforgiving about process. The operator who arrives with a timestamped history of every invoice, reminder, fee, call and plan offer is in a different position from the one reconstructing events from a manager's recollection. What the notice must say and when it may be served is state law — build the templates with counsel, then let the system fill and file them.

And when a balance is truly gone — the resident left, the home was abandoned — the write-off is its own disciplined step: approved, documented, posted, so the AR stays honest instead of carrying ghosts.

The numbers that tell you it's working

Three metrics, standing, per community: collections rate (collected against billed, the headline), aging trend (is the over-30 bucket growing or shrinking — the early warning), and cure rate (what share of misses return to current within the month — the measure of whether the ladder's early rungs are doing their job). When billing, fees, plans and write-offs all post in one system, all three are saved reports. Portfolio-wide, they're also the collections story a lender or buyer will ask for — with the data to back it.

How RIOO runs collections on NetSuite

RIOO runs the full ladder natively on Oracle NetSuite: automatic aging from real invoices, per-community dunning schedules and late-fee policy, payment plans as tracked records, statutory notices generated from account data with service logged, separate rent and note aging, and the collections metrics standing by community and consolidated. To see a delinquent account walk the ladder, Book a demo. Platform context is in the mobile home park software guide and the 2026 buyer's guide.

Frequently asked questions

Q1. How does a lot rent dunning sequence work?
On configured day-triggers after the due date: a courtesy reminder first, a late fee after the community's grace period, a formal past-due notice, then a logged human contact with a payment-plan offer — each step generated automatically from the open receivable and timestamped on the resident's account.

Q2. When should a late fee be charged on lot rent?
After the grace period the community has configured, which is set to match its state's rules and the lease terms. The fee posts automatically as its own line into a dedicated late-fee income account, and any waiver is logged with who approved it — the fee is policy, never processor discretion.

Q3. How are payment plans tracked in a collections workflow?
As records with defined terms: total arrears, installment amount, dates and the resident's acknowledgment. Installments track against the plan while current rent bills normally, and a missed installment flags the account immediately instead of surfacing months later as a larger balance.

Q4. Why should collections run identically for every resident?
Consistency is both efficiency and protection: a trigger-driven ladder means no account slips through, and because every resident moves through the same documented sequence, the operator can show that treatment differences never depended on who the resident was — a meaningful fair-housing safeguard.

Q5. Is delinquency handled differently in manufactured housing than apartments?
Structurally, yes. Most residents own their homes and face high costs to move them, so cure and payment-plan rates run high and eviction is a poor outcome for both sides. Effective MH collections leans on early contact and structured plans, with formal process as the documented last resort.

Q6. What records matter if a case goes to formal proceedings?
The timestamped account history: every invoice, reminder, late fee, dunning notice, call log, plan offer and the statutory notice with its service documentation. When each step of the ladder logs itself as it runs, that record already exists the day counsel asks for it.