M-Pesa

M-Pesa Ratiba for Business Collections (2026)

K By Kev 22 November 2026 9 min read
Share
M-Pesa guide

M-Pesa Ratiba is Safaricom's standing-order service: it lets an M-Pesa customer schedule a recurring payment instead of remembering to send it. For a business collecting the same amount from the same people every month — rent, school fees, a gym membership, a service retainer — that changes the hardest part of the job, which was never the payment itself but the chasing.

On this page▾
  1. Why recurring collection is a different problem from one-off payment
  2. Setting up recurring collection properly
  3. Where recurring collection goes wrong
  4. A worked example: a gym with 140 members
  5. What Veira does, and does not do, alongside Ratiba
  6. Frequently asked questions

Why recurring collection is a different problem from one-off payment

A shop takes payment at the moment of sale, and if it does not arrive the goods do not leave. A business collecting monthly has no such leverage. The service was already delivered, or the tenant is already living there, and the money arrives when the customer remembers. Most of the operational cost of these businesses is in the reminding.

A standing order moves the decision from every month to once. The customer authorises a recurring instruction from their own M-Pesa, and it runs until they change or cancel it. That is a meaningful shift in collection reliability, and it is the customer who holds the instruction — not the business, which matters both for consent and for what you can and cannot control.

What it does not change is reconciliation. Money arriving on a schedule still has to be matched to the right account, and a scheduled payment that fails — insufficient funds being the common case — becomes an exception somebody has to notice. A business that treats a standing order as "collection solved" discovers the gap three months later, when it finds four tenants whose instruction stopped running.

Want to see it running in your own business first?

Sign Up

Setting up recurring collection properly

The sequence matters because the parts you control and the parts the customer controls are different, and so are the parts that need checking.

  1. 1

    Confirm the service and its current terms with Safaricom

    Eligibility, charges, limits and exactly which collection channels a standing order can pay into are Safaricom's to state and they change. Confirm them directly for your account before you build a process on them. Nothing on this page is a substitute for that, and Veira is not Safaricom.

  2. 2

    Decide what each customer's reference will be

    This is the step that decides whether reconciliation is five minutes or an afternoon. A recurring payment that arrives with a consistent, unique account reference per customer can be matched automatically. One that arrives with a name or nothing cannot.

  3. 3

    Ask the customer, do not assume the customer

    The instruction lives in the customer's M-Pesa and is theirs to authorise. Explain the amount, the date and how to cancel before they set it up. A recurring charge somebody does not remember agreeing to is a dispute and a lost customer, whatever the paperwork says.

  4. 4

    Record the expected schedule in your own system

    You need a list of who is supposed to pay what and when, held somewhere you control. Without it you cannot tell a payment that did not arrive from a payment you did not notice — and the whole value of recurring collection is in spotting the first.

  5. 5

    Review failures weekly, not monthly

    Insufficient funds is the usual cause and it is often temporary. Caught in the same week, it is a text message. Caught at month end, it is arrears, and arrears are what turn a collection problem into a relationship problem.

  6. 6

    Reconcile the schedule against what actually landed

    Expected versus received, per customer, per month. This is ordinary reconciliation and the fact that the payments were scheduled does not remove it. It does make it faster, because the expected side is now a known list rather than a guess.

Where recurring collection goes wrong

Treating a standing order as a guarantee

It is an instruction that can fail, be changed or be cancelled, and all three happen without anybody telling you. The schedule is a plan, not a receipt.

Not giving each customer a stable reference

Recurring money with no reliable reference is recurring reconciliation work. Decide the reference scheme before the first customer signs up, because changing it later means matching two schemes.

Setting it up without the customer understanding it

The instruction is theirs. A customer who feels charged without consent will cancel and complain, and they will be right to. Clarity up front costs nothing and prevents the one outcome that actually loses revenue.

Assuming a POS can create or cancel a customer's standing order

It cannot, and Veira does not. The instruction is set up by the customer in their own M-Pesa. What a business system can do is record what was expected and show you what arrived.

Reviewing failures monthly

A failed payment found in week one is a reminder. Found in week five it is arrears, and the conversation is harder for both sides.

A worked example: a gym with 140 members

Worked example

A Nairobi gym with roughly 140 monthly members was spending most of the first week of every month on collection. Two staff worked through a list, sent reminders, took payments in person, and still finished the week with twenty-odd members unpaid and no clear record of which reminders had gone out.

Moving regular members onto standing orders changed the shape of that week rather than eliminating it. Most members paid on schedule without contact. What the staff now did instead was work an exception list: the handful of instructions that had failed, and the smaller handful of members whose payment had arrived without a usable reference and had to be matched by hand.

The important discovery was in the second month. Six instructions had quietly stopped running, and because the gym was now comparing an expected schedule against received payments rather than chasing a list from memory, it found all six in week one rather than at the next renewal. That is the actual benefit: not that the money arrives by itself, but that you can see immediately when it does not.

Business impact

When M-Pesa payments are not matched to sales, a missing payment, a staff shortfall or a double charge can slip past you until the money is already gone.

Veira reconciles M-Pesa Till and Paybill against every sale, so a mismatch surfaces the same day instead of at month end.

What Veira does, and does not do, alongside Ratiba

To be direct about the boundary: M-Pesa Ratiba is a Safaricom service. Veira does not provide it, does not create or cancel a customer's standing order, and has no part in whether a scheduled payment succeeds. For eligibility, charges and limits, Safaricom is the only correct source, and those details change.

What Veira does is the other half. It records what each customer owes and what has been received against it, so a recurring payment lands against a customer account rather than in an undifferentiated pile. It tracks outstanding balances, so the exception list — who has not paid this month — is something you can read rather than reconstruct. It issues a compliant KRA eTIMS invoice for the sale, and it reports collections by period so expected can be compared with actual.

That is the division of labour worth understanding before you set any of this up: Safaricom moves the money on a schedule, and your own records tell you whether the schedule held.

Frequently asked questions

What is M-Pesa Ratiba?
Safaricom's standing-order service for M-Pesa: a customer schedules a recurring payment once instead of sending it manually each time. Confirm the current terms, eligibility and charges with Safaricom directly — Veira is not Safaricom and those details change.
Which businesses benefit most from recurring M-Pesa collection?
Any business billing the same customers the same amount on a cycle: landlords, schools, gyms, subscription services, retainer-based professional firms. The more of your revenue is recurring, the more of your month is currently spent chasing it.
Can my POS set up a standing order for a customer?
No. The instruction belongs to the customer and is set up in their own M-Pesa. Veira does not create, change or cancel one. What it can do is hold the expected schedule and show what actually arrived against it.
What happens when a scheduled payment fails?
The common cause is insufficient funds on the day. The practical answer is process rather than technology: compare expected against received weekly so a failure is found while it is still a reminder rather than arrears.
How do I match recurring payments to the right customer?
Give every customer a stable, unique account reference and use it consistently from the first sign-up. This single decision determines whether monthly matching takes minutes or hours.
Do I still need to reconcile if payments are scheduled?
Yes. Scheduling makes reconciliation faster because the expected side becomes a known list, but money still has to be matched to accounts and failures still have to be found. A standing order collects; it does not account.
Can a customer cancel without telling me?
Yes, and this is the main operational risk. It is why the expected-versus-received comparison matters more with standing orders than without them: a cancellation is invisible until you look for the missing payment.

Recurring collection stops being a weekly chase and becomes a short exception list — but only if you hold the expected schedule somewhere and check it. If most of your revenue is the same customers every month, book a demo and bring your current collection list.

Need help, or want to talk it through first? Chat with us on WhatsApp
Terms explained

Keep reading

See all M-Pesa guides

Veira for your business

Browse Veira by business type · Who we serve