Accounting and rent management for property owners

Direct answer

PolyAccounts includes a property module for multifamily, commercial and mixed-use assets: a portfolio dashboard, a live rent roll with market variance and delinquency, leases (create, activate, end), an applications pipeline, maintenance triage and a generated property website. It shares the general ledger, so rent, deposits and expenses appear in the same books as everything else.

The revenue engine (polyrm-1.1) sets asking rents for available units and renewal offers for expiring leases. It reads only the operator’s own units, leases, asking rents and demand funnel, public asking rents, and an aged public market dataset. It never reads another operator’s data, every recommendation ships a plain-language driver list and inputs snapshot, and a person approves, overrides or declines every price before use.

Why the design of the pricing engine matters

Algorithmic rent-setting is under active antitrust enforcement in the United States, and several states and cities restrict it. The pattern at issue is pooling competitors’ nonpublic data into shared recommendations. PolyProperty avoids that pattern structurally rather than by policy: no cross-tenant inputs, company scoping on every query, explainability by default, and human approval on every number.

If you are choosing a system for a portfolio and your counsel has asked about rent-setting exposure, this is the section to send them. It is a design description, not legal advice.

Agent access today

Agents have full access to the general ledger, records, reports, budgets, approvals and periods that the property module posts into. Property-specific records (units, leases, applications, maintenance) are managed in the application today and are not yet exposed as agent workflows. That exposure is planned; until then an agent can read the ledger effects of property activity and run the finance workflows around them.