Rent collection system routines should help a property manager answer three questions every day: what money has been confirmed, where it belongs and what still needs attention. A dashboard total is a starting point. Reliable collection work also depends on clear references, explainable balances and a process for reviewing payments that do not fit the normal pattern.
This guide sets out nine daily checks for Kenyan landlords and agencies using M-Pesa, bank payments or other agreed channels. It includes a fictional worked example and a practical handover routine. Adapt it to your own policies and confirmed software configuration. For a RentalDesk demonstration focused on your collection process, call 0725345345.
Rent collection system: define the day’s review
Check 1: set the period and assign the reviewer
Begin by deciding what activity the review covers. A morning check might cover transactions received since yesterday’s closing review, while a month-end report covers a different period. Record the time range clearly so another staff member does not compare two totals that describe different windows of activity.
Assign responsibility for confirming payment records, investigating exceptions and approving corrections. These duties may be shared in a small operation, but the handover should still identify who completed each important review. “Someone checked it” is difficult to rely on when a tenant later asks about a missing payment.
Keep the daily review focused. The aim is to identify confirmed collections, unresolved items and the next actions. It is not necessary to rebuild every historical balance each morning. If an older discrepancy appears, place it on a tracked investigation list with enough context to keep it from being forgotten.
Check 2: confirm the payment source
Use the authorized transaction records for the payment channel. Distinguish a completed payment from a request, a pending status or a failed attempt. A message saying that a tenant intends to pay should not reduce the ledger balance. The record changes when the relevant payment has been confirmed through the agreed process.
Review current channel information through Safaricom’s business payment resources. Confirm applicable arrangements and charges directly with the provider. The daily collection routine should reflect the actual account and integration in use, rather than assumptions copied from another landlord’s setup.
For automated collection, ask the supplier to explain how payment confirmation reaches the system and what happens when it is delayed. Staff should know which status to trust and when to investigate. A delayed update does not automatically mean the tenant must make another payment, so the next action should be verification.
The RentalDesk M-Pesa automation guide is a useful starting point for mapping that process. Confirm the features included in your plan and configuration before treating every step as automatic. Clear expectations prevent staff from creating duplicate manual entries while an existing transaction is still being reviewed.
Check 3: match the transaction to the correct record
Check the transaction reference, amount and available payer context against the tenant and unit. Do not rely on a familiar name alone. A relative may pay on behalf of a tenant, and similar names may appear in different properties. The allocation needs evidence that another reviewer can understand later.
Use a consistent property and unit identifier wherever your payment instructions allow it. A clear reference reduces investigation work, but it does not eliminate the need for review. Tenants can mistype references, reuse an old instruction or pay for more than one obligation in a single transaction.
If the evidence is insufficient, keep the payment in a review queue rather than guessing. Record what is known and what needs confirmation. The person contacting the tenant should have a specific question, such as which unit or period the payment concerns, instead of asking for every detail again.
Explore RentalDesk bank and M-Pesa reconciliation when designing this exception process. The important operational question is whether staff can trace the allocation decision and correct it with appropriate review if new evidence becomes available.
Check 4: calculate the remaining balance
Review the payment against the relevant invoice or balance according to your agreed allocation policy. The amount received and the amount still outstanding should be understandable separately. A tenant who paid part of the rent should not appear identical to someone who has paid nothing, because the next conversation will be different.
For a fictional example, assume a tenant has a KSh 18,000 invoice and no earlier balance. A confirmed payment of KSh 10,000 leaves KSh 8,000 outstanding. A later confirmed KSh 8,000 payment clears that invoice. The example excludes other charges, credits and deposits so the arithmetic is easy to follow.
If other entries exist, explain their effect rather than hiding them inside an unexplained total. An approved adjustment, an earlier credit and a new charge are different kinds of information. Staff need enough context to answer why a displayed balance differs from the tenant’s recollection of the latest rent payment.
Review overpayments deliberately. Do not silently treat every excess amount as rent for a future period without the agreed process and supporting context. The rent collection system should preserve the facts of the transaction while the responsible team decides its correct treatment.
Check 5: inspect possible duplicates and corrections
A repeated amount is not proof of a duplicate payment. Two tenants can pay the same rent, or one tenant can make two separate payments of equal value. Compare transaction identifiers and source records before removing or reversing an entry. The goal is to explain the evidence, not to make the list look tidy.
Duplicate recording can happen when an automated transaction is also entered manually. Ask how staff identify that situation and which correction process preserves the record of what happened. A correction should not erase the explanation needed by a reviewer or cause a tenant’s legitimate payment to disappear.
If a payment was assigned to the wrong tenant, record the reason for the change and review the effect on both balances. Check any receipt or follow-up message already produced from the incorrect allocation. Fixing the ledger alone may leave a confusing communication trail unless the team also addresses the earlier message.
Keep correction permissions limited to the appropriate role. Staff who can view an issue do not necessarily need authority to change financial records. The daily routine should make escalation straightforward so people can report a problem without improvising a solution outside their responsibilities.
Check 6: review receipts and tenant communication
Check that the receipt or payment acknowledgement refers to the correct tenant, amount and transaction context. Where a balance is shown, make sure the reporting time and relevant entries are understood. A receipt should help the tenant recognize their payment rather than introduce another unexplained figure.
Use the RentalDesk arrears tracking guide to discuss how paid, part-paid and overdue records feed into follow-up. Review the latest allocation status before sending a reminder. A payment awaiting investigation should be handled differently from a confirmed unpaid invoice.
Keep reminders factual and respectful. Identify the relevant period and offer a clear route for questions or correction. Avoid sharing tenant balances in group chats or with unrelated occupants. Review your communication process alongside the ODPC guidance resources, and seek appropriate advice for specific compliance questions.
Record the outcome of a conversation in concise, relevant terms. Note the next agreed action and review date without collecting unnecessary personal details. This gives the next staff member enough context to continue the work without repeatedly asking the tenant to explain the same issue.
Check 7: separate collection work from other business records
Some rental portfolios belong to investment groups. A group using TAS chama software may need rental information for member reporting, but the rent ledger and member contribution records serve different purposes. Agree which reviewed figures are transferred and who checks them. Do not assume that a link between websites means automatic data exchange.
Commercial tenants may operate a shop with Vega POS or a salon using PRIM software. Their sales activity is separate from the landlord’s confirmation of rent received. A daily collection review should remain focused on the rental obligation and the evidence relevant to its payment.
If you need a custom reporting connection, discuss the requirement with a provider such as Zama and request a defined scope. Specify the fields, authorized recipients, review steps and support responsibility. A custom integration should be tested independently before it becomes part of the daily closing routine.
The property office also depends on practical infrastructure. Spacekits connectivity services can inform internet planning, while PMS property management software is another product reference for evaluating workflows. These resources do not establish an integration, endorsement or guaranteed performance between the services mentioned.
Check 8: reconcile the daily summary
Compare the confirmed source transactions with the payments recorded for the review period. Explain differences such as an item still awaiting allocation or a transaction outside the selected time window. A total can appear correct by coincidence, so investigate the underlying entries when something does not follow the expected pattern.
Keep separate figures for confirmed money received, money allocated to tenant records and unresolved items. Those categories answer different questions. Combining them too early can make an exception invisible, particularly when a payment has arrived but staff do not yet know which tenant balance it should reduce.
Consider a fictional daily exercise: confirmed source payments total KSh 75,000, of which KSh 68,000 has been allocated and KSh 7,000 remains under review. The review record should explain that difference. It should not quietly report KSh 75,000 as fully allocated or treat the unresolved amount as missing cash without evidence.
Ask a second person to review significant exceptions where practical. They should be able to trace the amount, source and next action from the notes. The daily summary becomes more reliable when it supports a repeatable check instead of relying on one person’s memory of several phone calls.
Check 9: close with a clear handover
End the review with a short action list. For each unresolved item, record the identifier, issue, responsible person and next review time. An item marked “pending” without an owner is easy to overlook. The handover should make it clear what someone needs to do, not simply that a problem exists.
Record when the daily review was completed and which period it covered. If new transactions arrive afterwards, make clear that they belong to the next review or a defined supplementary check. This avoids disputes caused by comparing a saved report with a dashboard that has continued to update.
Keep the working notes in the agreed system or controlled location. Avoid scattering important allocation decisions across personal notebooks and private messages. The collection process should remain understandable when a staff member is away, changes roles or hands the portfolio to another colleague.
Build a routine that fits the size of the portfolio
A small landlord may complete these checks in one sitting, while an agency may divide them between collection, finance and management staff. The structure can vary, but the important distinctions remain: confirmation, allocation, balance review, communication and unresolved exceptions. Each step should have a recognizable result.
Review recurring problems periodically. If many payments arrive with unclear references, improve the instructions. If staff repeatedly enter duplicates, clarify the manual-entry rule. If tenants cannot understand receipts, review the wording. A rent collection system delivers more value when the team improves the process around it rather than repeating the same correction every month.
Do not measure success only by the number of reminders sent. More useful operational measures include the number of unexplained payments, the time taken to resolve an exception and whether staff can explain balances consistently. Use your own observed results rather than adopting a promised improvement percentage without evidence.
Frequently asked questions
Should a payment screenshot be enough to mark rent paid?
Use the agreed verification process and authorized transaction records. A screenshot can help identify a payment to investigate, but the team should confirm the actual transaction before updating the balance. If confirmation is delayed, record the enquiry and investigate rather than automatically requesting another payment.
How should part-paid tenants appear in the daily review?
Show the confirmed amount received and the remaining balance separately, with the relevant period or invoice context. This supports accurate follow-up and makes later payments easier to trace. Include earlier balances or approved adjustments explicitly when they affect the total.
Can automation remove the need for review?
Automation can reduce repetitive work, but unusual references, duplicate entries and disputed allocations still need a clear process. Ask which cases your configuration handles automatically and which remain in a review queue. Keep responsibility for checking those exceptions visible.
Make daily collections easier to explain
A dependable rent collection system supports a routine that staff and tenants can understand. Confirm the source, allocate carefully, explain the balance and give every exception a next action. Book a RentalDesk demo or call 0725345345 to walk through your daily collection process with realistic examples.