How to Record External Rent Payments in RentPayor

Not every rent payment begins with the in-app M-Pesa checkout. A tenant may pay through an arrangement that sits outside that online flow, and the property manager still needs the invoice, receipt and outstanding balance to reflect what really happened.

The practical risk is simple: a payment that exists only in a message, a notebook or someone’s memory is hard to trace later. The solution is to record it against the right invoice with enough context to explain the balance.

This guide explains a disciplined external-payment workflow in RentPayor. It is for landlords and property managers who need a clear record when a payment was received outside the app’s online payment flow.

Start with the invoice, not the payment message

Open the tenant’s invoice before recording anything. Check the tenant, unit or property, billing period, amount due, amount already paid and outstanding amount.

This step prevents a common error: recording a legitimate payment against the wrong month, tenant or unit. It also tells you whether you are recording a full settlement, a partial payment or an amount that could create credit.

For example, if an invoice has an outstanding balance of KES 18,000 and the tenant paid KES 10,000 outside the online flow, the record should be attached to that invoice for KES 10,000. The invoice can then remain partially paid, with KES 8,000 outstanding. A partial payment should not be presented as a fully paid invoice.

Record the payment with the facts you can verify

RentPayor lets a landlord or property manager manually record a direct payment against an invoice. The workflow supports:

• the amount received;
• the transaction date;
• an optional payer name;
• an optional payer reference; and
• optional notes.

Use the actual transaction date rather than the day you happen to enter the record. Add the payer name if the payer is different from the named tenant, and add a useful reference when one exists. Notes are a good place for neutral context such as “paid at office” or “confirmed by landlord,” without turning the notes field into a substitute for the invoice record.

A good record answers a future question quickly: who paid, how much, when, and which invoice did it reduce?

Treat external payments as manual records

The manual payment path is a fallback for payments received outside RentPayor’s online flow. It does not mean RentPayor automatically finds every external M-Pesa or bank transaction, matches screenshots, or reads payment messages.

That boundary matters. Confirm the payment through the process you use before recording it, then enter it deliberately against the relevant invoice. If the details are uncertain, resolve the exception first instead of creating a record that may later need correction.

By contrast, a confirmed in-app online payment is associated with its relevant invoice/payment flow and can reconcile without the landlord re-entering that payment manually. Even then, a payment request or M-Pesa prompt alone is not confirmation that rent has been paid.

Check the balance after recording

After the payment is recorded, revisit the invoice activity and balance. The activity should help explain how the current outstanding amount was reached.

There are three typical outcomes:

1. The payment clears the balance. The invoice can show as paid, and the recorded payment has a receipt.
2. The payment covers only part of the balance. The invoice remains partially paid, and the remaining balance stays visible for follow-up.
3. The payment is larger than the outstanding amount. The excess can be carried forward as lease credit for a later invoice.

The last case is worth checking closely. Do not lose the excess by simply editing the payment down to the invoice balance. A carried-forward credit keeps the overpayment traceable and lets later invoice activity explain why a lower amount was due.

For a fuller explanation of what an invoice history should show, see how to trace an invoice balance. If a payment settles only part of the invoice, the partial rent payment guide has a useful follow-up workflow.

Issue or open the receipt

Receipts are available for recorded payments. Once the payment record is correct, use the receipt as the confirmation tied to that record—not as a replacement for checking the invoice allocation.

A useful receipt trail makes it easier to respond when a tenant asks whether a payment was recorded, when a manager needs to hand over the portfolio, or when a month-end review reveals an unexpected balance. It connects the payment record back to the invoice and the rental context.

A simple review routine for property managers

For teams handling multiple properties, make external-payment recording a small, repeatable routine:

1. Confirm the payment through your normal process.
2. Open the correct tenant invoice.
3. Record the amount, transaction date and any helpful payer reference.
4. Review the invoice balance and activity.
5. Check whether the result is paid, partially paid or a credit.
6. Make the receipt available from the recorded payment.

This routine is intentionally conservative. It separates a received payment from an unverified claim, and it keeps one-off exceptions from weakening the portfolio’s rent records.

When the online flow is a better fit

Where an eligible outstanding invoice is paid through RentPayor’s in-app M-Pesa flow, the tenant opens the invoice, chooses Pay with M-Pesa, and enters the M-Pesa number that will receive the payment prompt. After confirmation, the online payment can update the related invoice and payment records and lead to a receipt.

That does not remove the need for judgment around payments made elsewhere. The manual route remains valuable for direct or external payments, while the in-app flow avoids having to re-enter a confirmed online payment.

The goal is not to force every payment into one method. It is to make sure every recorded payment has a clear place in the invoice history, so the rent balance is understandable when you need it.