Resident Portal
Every tenancy has two sides, and they read from one record. A resident sees the rent schedule the lease generated, pays against it, reports a repair that becomes a work order, and answers an inspection — while the operator sees the same events in the console. There is no second database and no nightly sync, so a payment is never posted in one place and missing in the other.
What it does
The rent schedule they were actually billed
Instalments are generated from the tenancy's own frequency — monthly, quarterly, biannual, annual or biennial — so what a resident sees is the schedule the lease produced rather than a figure typed into a reminder.
Pay by gateway or declare an offline payment
Mobile money and bank transfer are the reality in Ghana, so a resident can declare a payment made outside the platform. It is a claim until a person confirms it, and the confirmation is what posts to the ledger.
Repairs that become work orders
A reported repair carries its room, urgency, access preference and photographs, and lands in the operator's maintenance queue as the same record a contractor is later assigned to.
Their own documents
Agreement, tenancy certificate and payment history, held against the tenancy rather than emailed as attachments that go stale.
A complaint that cannot be quietly closed
Raising a complaint starts an append-only history. Closing it requires a written outcome, and the resident sees that outcome.
Notifications that can only come from someone they deal with
In-app, email and SMS, and the platform refuses to deliver a message between two accounts with no tenancy, application, viewing, repair, sponsorship or complaint between them.
How it works
The sequence an operator actually follows, not a feature list rearranged into steps.
- 1
A tenancy is agreed in the console; the rent schedule is generated from its frequency and start date.
- 2
The resident signs in, sees what is due, and either pays through the gateway or declares an offline payment.
- 3
Repairs, inspection responses and complaints raised from the portal appear in the operator's queues as the same records.
- 4
Every consequence — a confirmed payment, a deposit deduction, a closed complaint — is an action a person took, with a reason recorded.
What the database guarantees
These hold whether or not the interface remembers to check.
- A resident reads their own tenancy and no one else's; the rule is a row-level policy, not a hidden menu item.
- One account cannot send another a notification unless the platform can name the dealing between them.
- A declared payment does not post to the ledger until a person confirms it.
- Complaint history is append-only — events cannot be edited or deleted, including by us.
What it does not do yet
You will ask this in an evaluation, so here it is without being asked.
- No native mobile app. The portal is a responsive web application, which is what a Ghanaian renter on a mid-range Android will open anyway.
- No resident-to-resident messaging or community features.
- Rent reminders go out by email and SMS on a schedule; there is no per-resident quiet-hours preference yet.
Works with
These share the same database, so nothing is re-keyed between them.
Leases & Tenancies
Ghana-specific agreements and lifecycle
Facilities & Maintenance
Assets, PPM, SLAs, statutory compliance
Receivables & Arrears
Recurring charges, late fees, ageing
Commercial Leasing & CAM
Service charge, apportionment, reconciliation
Procure-to-Pay
Requisition to payment, three-way matched
Inspections & Deposits
Photographic condition, and a deposit that survives it
See resident portal against your own portfolio
Forty minutes, a property you actually manage, and a written quote after. No card at any point.