Feature
Property and unit operations
The property and unit records are the spine every lease, charge, work order and statement hangs off. ResidentAxis gets them right first — ownership, obligations, unit types — so nothing downstream has to be re-keyed.
The problem
Most suites treat a property as an address and a rent number.
Then the real questions arrive: who owns 40% of the duplex, when is the HOA due, which units are student housing under a mixed-use roof, and which owner pays the water bill. Those answers live in spreadsheets, and the spreadsheets drift.
- Owner splits and management fees live outside the system, so owner statements are hand-built.
- Taxes, insurance, HOA dues and licences are tracked in calendars nobody audits.
- Mixed-use and small-multi portfolios are forced into a “multifamily” shape that does not fit.
- Custom attributes end up in the notes field.
The workflow
From address to operating record in one pass
- Pick the property type
Single-family, townhome, condo, duplex / small multi, multifamily, student housing or mixed-use. Single-unit types capture beds, baths and rent inline and create their one unit; multi-unit types add units after.
- Add owners and splits
Owners with basis-point splits that must total 100% (the database rejects anything else) and a management fee — percent of collected or flat.
- Record obligations
Taxes, HOA / condo dues, warranty, insurance, escrow, rental licence, owner-paid utilities: payer, handler, due date, autopay status, proof notes.
- Define units
Layout, market rent, status and unit type per door. A mixed-use property can hold residential, retail and student unit types together.
- Extend with custom fields
Org-scoped typed fields on properties, units, leases, people and tickets — filterable and audited.
Illustrative portfolio tiles and rent roll rendered from ResidentAxis UI patterns with demo data.
Capabilities
What is built, what needs configuration, what is planned
Each row is a real capability in the current build. Labels are derived from the codebase and its test suites, not from a roadmap deck.
How to read the labels
- Built
- Implemented in the current build and covered by its test suite.
- With configured integration
- Implemented; a live outcome requires a provider you configure (keys, contract, or credentials).
- Pilot
- Implemented in part and enabled per pilot customer with tuning.
- Planned
- On the roadmap. Not sold or promised today.
-
Type-first property onboarding
BuiltSingle-family, townhome, condo, duplex, multifamily, student and mixed-use — single-unit types create their unit inline; multi-unit types add units after.
-
Owners and percentage splits
BuiltOwner records with basis-point splits that must total 100%, validated in the database, plus a per-property management fee.
-
Property obligations
BuiltTaxes, HOA dues, insurance, warranty, escrow, rental licences and owner-paid utilities with due dates, payer, status and proof notes.
-
Unit records and status
BuiltLayout, market rent, status and unit type per door; mixed unit types inside one property.
-
Custom fields
BuiltOrg-scoped typed fields on properties, units, leases, people and tickets; filterable and audited.
-
Portfolio import
PilotCSV import of properties and units during pilot setup; assisted mapping by the ResidentAxis team.
-
Public unit listings
PilotToken-addressed public listing pages for vacant units; syndication to listing networks is not included.
By role
What each party gets
Property managers
One place for every property fact — and the obligations calendar you would otherwise keep in a spreadsheet.
Owners
Their split, their fee and their doors are structural, not a note on a statement.
Accounting
Management fees and owner splits compute from the record, so month-end starts from the right numbers.
Configuration and pilot notes
Before you rely on it
Things that are set up per operator during a pilot, or that depend on a provider you contract.
- Portfolio import from CSV is done with the ResidentAxis team during pilot setup; a self-serve importer is planned.
- Property and unit type catalogues ship with 13 property types and 16 unit types; additional types are added per operator.
- Public listing pages for vacant units exist; syndication to listing networks is not included.
Questions about this area
Can one property have several owners with different percentages?
Yes. Splits are stored in basis points and must total exactly 100%; owner statements weight net income by each owner’s split.
Do you support mixed-use buildings?
Yes. A property can carry multiple unit types — residential, retail, student, and so on — and reports roll up per type.
What about single-family portfolios with hundreds of houses?
That is a primary use case. Single-unit property types create their unit automatically, and obligations per house (taxes, HOA, insurance) are first-class records.
Related
Connected areas
See property & unit operations on your portfolio.
A pilot starts with a discovery call and your CSV exports. We reply within two business days.