Why rent books and spreadsheets stop working
As soon as a portfolio grows past a handful of units, the same problems appear. A payment arrives with the wrong reference and nobody can tell which tenant sent it. A tenant pays half, and the half is allocated one way this month and another way the next. Arrears live in one person's head. Landlords ring the office to ask what came in.
None of this is a technology problem at first. It is bookkeeping that gets harder with every unit you add. A rental management system earns its keep by making that bookkeeping automatic, and the same every time.
1. M-Pesa payments should match themselves
In Kenya most rent arrives through M-Pesa, so this is the first test of any rental management system. Each tenant should have a personal account number for your paybill. When a payment clears, the system should receive it automatically through Safaricom's Daraja API, match the account number to the tenant's lease and apply the money — without anyone copying transaction codes into a spreadsheet.
Two questions separate a careful system from a careless one:
- What happens when a tenant types the wrong account number? The payment should be flagged and the office alerted, not silently lost or guessed.
- What happens when the same payment notice arrives twice? It should be counted once. Duplicate notices happen, and a system that double-counts them will overstate what you have collected.
2. Partial payments and arrears need one fixed rule
Tenants rarely pay exactly what is owed. Decide the order in which money is applied — for example penalties first, then water, electricity and service charge, then rent — and the system should apply every payment in that order. Shortfalls carry forward as arrears, surpluses are held as credit, and each receipt shows the balance carried forward.
One detail matters more than it sounds: payments should attach to the lease, not to the person. When a tenant moves to another unit, their old balance stays with the old lease and their new history starts clean.
3. Everyone should see only their own slice
A property manager, a landlord, an agent and a tenant need very different views of the same records:
- The property manager's office sees the whole book and runs the exports.
- Landlords see their own properties and account, read-only, so they stop calling for updates.
- Agents see only the units assigned to them, with the tickets, readings and charges for those units.
- Tenants see their own lease and payments, and raise maintenance requests.
Ask who can edit or delete a payment. In a well-run system day-to-day staff cannot change payments at all, deleted records are kept rather than erased, and every change is written to an audit trail.
4. The rest of property management, in one place
Rent is the core, but the system should also carry the work around it, so that nothing lives in a separate notebook:
- Utility readings and the water, electricity and service charges that follow from them.
- Invoices and printable statements for tenants and landlords.
- Maintenance tickets that go straight to the agent responsible for the unit.
- Expenses, suppliers and purchase orders with approval.
- Receipts and reminders sent by WhatsApp, SMS or email.
Questions to ask before you buy
- Does it connect to my own paybill, or does the money pass through someone else first?
- Can I bring in my existing spreadsheets of properties, tenants and balances?
- How are payments that match no tenant handled, and who is told?
- What exactly does a landlord see, and can they download a statement themselves?
- Does it work on a phone for agents in the field?
- Who owns the data, and can I export all of it?
- What happens to a record when someone deletes it?
If a vendor cannot answer these clearly, the gaps will show up in your books later.
Off-the-shelf or built for you?
An off-the-shelf product is the right choice when your process already matches it. A system built for you makes sense when your rules are your own: several landlords on different terms, service charges and utilities that standard tools handle badly, or an allocation order your tenants and landlords already expect. It costs more up front, and the return comes from fewer disputes, faster month-end and landlords who trust the numbers.
We built a rental management system around exactly these rules — automatic M-Pesa matching, a fixed allocation order, one view per role and a full audit trail. Its system manual walks through each part.
Where to start
Start with the rules, not the screens. Write down how a payment should be applied, who should see what, and what a landlord's statement must show. Those three pages decide most of what the system needs to do, whichever route you take. If you would like a second opinion on them, tell us how you work today and we will reply within one business day.
Frequently asked questions
What is a rental management system?
Software that keeps your properties, units, tenants and leases in one place, collects and matches rent payments, tracks arrears and credit, issues receipts and statements, and gives landlords, agents and tenants their own view of the records.
Can a rental management system receive M-Pesa payments automatically?
Yes. Connected to your paybill through Safaricom's Daraja API, each payment arrives as soon as it clears and is matched to the tenant's lease by the account number they used. Payments that match no tenant should be flagged for the office.
How do you move from spreadsheets to a rental management system?
Most of the work is cleaning the existing records: properties, units, tenants, leases and opening balances. With a bulk import, those spreadsheets become records in one step, and the new system takes over from the next payment.
Want this checked on your own site?
We will look at it and write back within one business day — speed, search visibility, and what the AI assistants currently say about you.
Start a conversation →
Comments