Property management, leasing and accounting on one database, with the portals and the field apps reading the same records your office does. This page is about how it fits together; the modules are listed further down.
A tenant payment, the ledger entry it creates, and the owner statement that reports it are the same records. Nothing is copied between systems, so nothing has to be reconciled between them.
Every transaction posts to the accrual and the cash book at the same moment. Neither is derived from the other when a report runs, so either can be trusted on any date.
What you bill decides where it lands. A charge code carries its income account, its receivable account and its cash account, so coding a lease once is what makes every downstream report right.
Every report is the same object on screen, in a PDF, and inside a monthly package. A printed report and the screen it came from cannot disagree, because they are the same report.
Tenant, vendor and owner portals sit on the same records as the back office, on their own authentication. What a tenant sees is what you see, not last night’s export.
Approvals and field work happen away from a desk, so those two have native apps rather than a shrunken web page.
Not separate licenses or separate systems — the same platform, the same database, the same login. Turn a module off for a role and it disappears for them.
The cash journal foots to its own charge-code summary. A balance sheet comparison is the standalone balance sheet run twice, so the two can never disagree. Reports state when a filter has made their own totals partial rather than letting somebody hunt an imbalance they created. Money moves are reversed, never erased.
Each client gets their own application and their own database. Isolation between customers is physical, not a filter somebody has to get right on every query.
Run more than one management company or legal entity inside your own deployment, each with its own users and data.
Hosted in Azure, or installed on hardware you control.
A build shows exactly what a database change would do; only a person starting a release applies it. Nothing reaches your data because a commit landed.
Role, module, property and portal are enforced where data is read. Hiding a menu item is a convenience, not a security control.
Bank account numbers and taxpayer IDs are encrypted in the database and masked in the interface, shown in full only where the work actually needs them.
We will walk through the parts that matter to how you actually run properties.
Get in touch