ResidentAxis

Product overview

A connected operating model, not a bundle of modules.

ResidentAxis is one record per property, unit, person and lease, one append-only ledger for money, and one audit log for everything else. Modules are views on that record — which is why a work order can end up on an owner statement without anyone re-keying it.

How records flow

Units, leases, payments, maintenance, inspections, accounting and owner reporting — one graph

The diagram is the architecture: operational records on the top and bottom rows, the ledger in the middle, financial views reading from it.

How records connect in ResidentAxis Units and leases feed charges; charges and payments form the ledger; the ledger feeds accounting, owner statements and reports; maintenance and inspections post expenses and deposit dispositions to the same ledger. Properties & unitsowners · splits · obligations Applicants → Leasesterms · amendments · e-sign Chargesrent · fees · HAP split Paymentscard / ACH · Zelle queue Residentsportal · app · messages Append-only ledger + audit loginteger cents · corrections are rows, never edits Maintenancework orders → expenses Inspections & depositsdiff → disposition AccountingGL · trust invariant · close Owner statementsnet to owner · distributions Reports & signalsrent roll · delinquency · renewals
Every operational record posts to one ledger; every financial view reads from it.

Every claim, linked

What we say the product does, and where to check

Each statement below links to the capability row on its feature page, with its status label.

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.

Views on one record

The same rows, four ways

Rent roll, maintenance board, trial balance and owner statement below are all reads of the same ledger and property graph.

Role model

Who sees what

Scoping is enforced in the database and re-checked on every request.

RoleSeesTypical use
Platform adminSubscribers, plans, billing, support mode (org-scoped and audited)Runs the ResidentAxis service itself
Property managerEverything in their organisationOperating admin of a management company
Accounting · leasing · maintenanceTheir area, org-wide, with permission overridesStaff roles
OwnerOnly the properties they hold a stake in, and their shareStatements, distributions, capex approvals
ResidentOnly their leaseBalance, payments, requests, documents, messages
VendorOnly explicitly assigned work, per client organisationWork orders, photos, status
Money in integer cents, never floats Corrections are rows, never edits Every write audited Integrations degrade gracefully behind interfaces

Walk through it on a call.

Forty-five minutes, your portfolio shape, our seeded demo. Then a scoped pilot plan.