Recurring rent and late-fee automation

Set the rent once; the ledger stays current. On Core (the manual community edition) you post charges and assess fees by hand — with every statutory guardrail enforced. On Standard, the automation pack does it for you on schedule.

Recurring rent charges

Each lease takes a recurring charge — amount plus day of month. Posting is idempotent: a charge posts exactly once per month per lease, never doubled, even if triggered twice. On Core you post due charges by hand with the post-due action. On Standard, rent posts itself on schedule — no button, no forgetting.

Late fees with state guardrails

Define your policy as a flat amount or a percentage. Every assessment — manual or automated — is clamped to the property state's statutory limit before it posts: Connecticut's lesser-of-$50-or-5% cap, and Massachusetts' rule that no fee applies until rent is 30 days overdue. On Core you run the assessment by hand; on Standard it runs on schedule. Either way the caps are enforced — compliance guardrails are never paywalled.

Utility splitting (RUBS)

Split a master utility bill across a property's active leases — equally, by bedrooms, or by square footage — and each lease's share posts to its own ledger as a typed charge.

Invoices

Invoices run draft → sent → paid. Sending posts the charge and emails the tenant; marking paid posts the credit. Every invoice prints to PDF.

Common questions

Is utility splitting legal where I operate?

Not everywhere, which is why Stonerow applies a jurisdiction guard rather than letting you split any bill you like. Utility resale and submetering rules make ratio billing unlawful in Connecticut and Massachusetts, while Rhode Island permits it with lease disclosure. Where splitting is allowed, shares allocate exactly — the remainder goes to the last lease — so the parts always sum to the master bill.

Can an invoice double-post to the ledger?

No. Sending an invoice posts the charge, and marking it paid posts the credit. They are two distinct typed entries, and neither can post twice for the same invoice.

Can I trust the automation to run unattended?

On Standard the scheduled jobs post rent, assess late fees, and accrue deposit interest on schedule using the same guardrails and the same once-per-period protection as the manual actions. The automation changes who presses the button, not which rules apply.

What if I want automation for some things but not others?

Core and Standard differ by whether the money jobs run themselves, not by which guardrails exist. If you want to keep posting rent by hand while everything else is automatic, run the post-due action yourself before the scheduled run finds anything due — the idempotency check means the two never conflict.