Properties
Portfolio records
Properties are not a static setup screen. In Abode they are the base layer for leases, maintenance, accounting, reports, statements, and portal visibility. Model them carefully and the rest of the system stays coherent.
Core entities
Properties, units, owners, tenancies, associations
Setup paths
Single-record entry plus bulk import workflows
Downstream dependency
Every report and ledger action uses these records
Context
Maintenance, leases, trust balances, and reports all become easier when the base records are accurate.
Portfolio hierarchy
Abode's object model is simple, but it is strict enough to keep downstream workflows aligned.
| Record | Purpose | What depends on it |
|---|---|---|
| Property | Top-level rental asset | Tenancies, maintenance, accounting, owner statements |
| Unit | Occupiable space within a property | Leases, vacancies, maintenance, rent roll |
| Tenancy | Resident + unit relationship | Balances, payments, portal access, lease history |
| Owner | Client or ownership relationship | Statements, trust sub-ledgers, distributions |
| Association | HOA / community entity | Dues, violations, architectural requests, committees |
Bulk setup versus ongoing edits
The first import is only half the job. Portfolio records need to stay operationally useful after onboarding.
- 1Import or create the property shell first, then attach units and owners.
- 2Create lease-bearing tenancies only after the unit and ownership structure is correct.
- 3Use association records when the entity has board, dues, or compliance workflows beyond plain rent collection.
- 4Keep payment settings and banking configuration attached to the entity that actually owns the money flow.
Do not flatten mixed portfolios
Associations behave differently than rentals. When dues, violations, or architectural approvals exist, model the association explicitly instead of forcing it into a rental-only shape.