# M-Pesa Bill Manager for Kenyan Businesses | Veira

> What Safaricom

Canonical: https://veirahq.com/blog/mpesa-bill-manager-for-businesses

M-Pesa Bill Manager is [Safaricom](https://www.safaricom.co.ke)&#x27;s billing service built on top of [Paybill](https://veirahq.com/blog/mpesa-paybill-charges): instead of a customer simply paying a number, the business issues a bill the customer receives and settles, and the business can see which bills are outstanding. For any business that invoices rather than sells over a counter, that is a different proposition from a plain collection account.

1. The difference between collecting money and managing receivables
2. Deciding whether billing or plain collection fits your business
3. Where billing services get misused
4. A worked example: a cleaning company with 60 contracts
5. Where Veira fits around a billing service
6. Frequently asked questions

## The difference between collecting money and managing receivables

A plain Paybill answers one question: did money arrive? That is enough for a business where payment and delivery happen together. It is not enough for one that issues an invoice and waits, because the useful question there is the opposite — which invoices have not been paid?

A plain Paybill cannot answer that, because it has no idea what was billed. It sees payments, not expectations. So businesses in this position end up maintaining the expectation side by hand, usually in a spreadsheet, and reconciling it against payments at month end. The spreadsheet is where the errors live.

A billing service closes part of that loop by holding the bill as well as the payment, so outstanding becomes a thing the system knows rather than a thing a person maintains. That is genuinely useful. What it does not do is become your accounting system, your sales record or your tax compliance — and treating it as any of those is the common mistake.

Want to see it running in your own business first?

## Deciding whether billing or plain collection fits your business

This is a fit question before it is a setup question. The wrong choice costs months of unnecessary process.

1. 1Work out whether you invoice or you sellIf payment and delivery happen at the same moment, you sell, and a Till or plain Paybill is the right shape. If you deliver and then wait to be paid, you invoice, and the thing you need help with is receivables, not collection.
2. 2Confirm eligibility and terms with SafaricomWhich businesses can use the service, what it costs, how bills reach customers and what account types are required are Safaricom&#x27;s to state, and they change. Confirm directly before designing anything around it. Veira is not Safaricom and cannot speak for it.
3. 3Settle your customer reference scheme firstEvery billing arrangement stands or falls on whether a payment can be tied to the bill it settles. Decide the reference scheme before the first bill goes out, and make it unique and stable per customer.
4. 4Decide what happens on a partial paymentCustomers pay part of a bill constantly, and the policy question — does it clear the oldest invoice, the named one, or sit unallocated — needs answering once, in advance, rather than per incident by whoever is looking.
5. 5Keep issuing your own compliant invoiceA billing notification is not a KRA [eTIMS](https://veirahq.com/blog/what-is-etims) invoice. The tax invoice for the supply remains your obligation and should be issued from wherever you record the sale. Confirm the treatment of your specific arrangement with current KRA guidance or your tax adviser.
6. 6Reconcile billed against received, weeklyEven with the loop partly closed, somebody has to look at what is outstanding and act on it. Weekly, because a bill chased in week two gets paid and a bill chased in month three gets argued about.

## Where billing services get misused

### Choosing billing when you actually sell over a counter

A shop whose customers pay as they buy gains nothing from an invoicing loop and adds a step. The fit question is worth answering honestly before setup.

### Treating a bill notification as a tax invoice

They are different documents doing different jobs. A customer-facing bill does not discharge your KRA eTIMS obligation for the supply.

### Running billing and a spreadsheet in parallel

Two records of what is outstanding will disagree within a month, and staff will trust whichever is nearer. Pick one place where outstanding lives.

### Having no partial-payment policy

Without one, allocation becomes a judgement call made differently by different people, and customer balances drift in ways nobody can later reconstruct.

### Assuming it replaces your sales records

It holds bills and payments. It does not hold what you sold, what it cost, what stock moved or which branch did the work. Those remain yours to record.

## A worked example: a cleaning company with 60 contracts

A commercial cleaning company serving about 60 business clients billed monthly in arrears and collected through a Paybill. The expectation side lived in a spreadsheet maintained by one person, and the monthly routine was to export Paybill payments, match them by eye against the sheet, and chase whatever looked unpaid.

Two failures were structural rather than careless. Clients who paid part of an invoice were recorded inconsistently — sometimes against the invoice, sometimes as a credit on the account — so a handful of balances were simply wrong. And when the person maintaining the sheet was on leave, the chase did not happen at all, which was visible two months later as a cluster of aged debt.

Moving the outstanding list out of the spreadsheet fixed the second problem structurally: outstanding became something the system knew rather than something a person maintained. The first problem was fixed by policy, not software — the company wrote down that a partial payment clears the oldest invoice first, and applied it consistently from that month. The lesson worth taking is that one of those two fixes was technical and the other was a decision, and the decision was the one that had been costing more.

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.

## Where Veira fits around a billing service

The boundary, plainly: M-Pesa Bill Manager is a Safaricom service. Veira does not provide it, does not resell it, does not operate M-Pesa, and is not the authority on its eligibility, pricing or how bills reach customers. Safaricom is, and those details change.

What Veira holds is the sale behind the bill. It records what was supplied, to which customer, at what price, with a compliant KRA eTIMS invoice issued from the record rather than reconstructed later. It tracks customer balances and partial payments against them, so a repayment lands on an account rather than in a pile. It reports collections by period and keeps the audit trail of who changed, discounted or voided what.

For an invoicing business the practical shape is: your own system is the source of what was supplied and what is owed, and the payment service moves the money. Keeping those roles distinct is what stops you running two disagreeing versions of the same customer balance.

## Frequently asked questions

If your problem is "which invoices are unpaid" rather than "did the money arrive", you need the expectation side held somewhere reliable — and a policy for partial payments. [Book a demo](https://veirahq.com/book) and bring your receivables spreadsheet; it usually tells the story in a minute.

## Keep reading

[See all M-Pesa guides](https://veirahq.com/blog/mpesa)

## Veira for your business

[Browse Veira by business type](https://veirahq.com/solutions) · [Who we serve](https://veirahq.com/industries)

Veira files a compliant invoice on every sale and keeps selling when the line drops.
