# M-Pesa Business Hub for Merchants in Kenya | Veira

> What Safaricom

Canonical: https://veirahq.com/blog/mpesa-business-hub-for-merchants

M-Pesa Business Hub is [Safaricom](https://www.safaricom.co.ke)&#x27;s own portal for merchants: the place a registered business manages its M-Pesa payment services and sees what has come in. If you have a Till or a [Paybill](https://veirahq.com/blog/mpesa-paybill-charges), it is where the authoritative record of your M-Pesa collections lives, and understanding what it does and does not tell you is the difference between reconciling your books and guessing at them.

1. What the Hub is for, and what it is not for
2. Using the Hub as part of a working routine
3. Common mistakes with a merchant portal
4. A worked example: the Tuesday that did not match
5. What Veira is for, next to the Hub
6. Frequently asked questions

## What the Hub is for, and what it is not for

The Hub exists to let a merchant administer their relationship with M-Pesa: the payment services on the account, the users who may act on it, and the transaction record of money received. That record is authoritative in a way nothing else is — it is Safaricom&#x27;s own account of what reached your business.

What it is not is a view of your business. It knows what came in through M-Pesa. It does not know what you sold, what it cost you, what stock left the shelf, which cashier rang it up, or what the customer bought. It has no reason to know any of that, and no merchant portal from any payment provider ever will.

That distinction is the whole reason businesses end up with two sets of numbers. The Hub says KES 180,000 came in on Tuesday. Whether Tuesday&#x27;s sales were KES 180,000 is a question only your own records can answer, and the gap between those two figures is where cash shortages, unrecorded sales and staff discrepancies hide.

Want to see it running in your own business first?

## Using the Hub as part of a working routine

The portal is a source, not a process. These steps are about building the routine around it.

1. 1Get your own access, and keep it yoursThe administrator of a merchant account can see and change payment arrangements. That access belongs to the owner or a named finance person, not to whoever set the shop up. Confirm the current access and user-permission options with Safaricom for your account type.
2. 2Learn what your transaction record actually containsBefore building a reconciliation routine, read a day of your own data and see what fields you get: amount, time, payer, reference. Which of these you reliably receive decides what can be matched automatically and what cannot.
3. 3Pull the record on a fixed cycleDaily if you take meaningful volume, weekly at minimum. The value is in comparison, and comparison needs both sides for the same period. An irregular pull means an irregular comparison and an unexplainable residual.
4. 4Compare it against your own sales record, not against memoryThis is the step that makes the Hub useful rather than merely informative. Collections from the Hub, sales from your POS, same day, same figure expected. A difference is a question with an answer.
5. 5Investigate the difference the same weekThe common causes are a sale rung up without payment recorded, a payment taken without the sale rung up, a refund nobody noted, or a timing difference across the day boundary. All four are identifiable within a week and all four are archaeology within a month.
6. 6Keep the record, do not just read itDownloaded statements are your evidence for an accountant, a lender or a KRA question. Archive them somewhere durable and organised by period, rather than re-downloading history under pressure later.

## Common mistakes with a merchant portal

### Using the Hub as the business&#x27;s management account

It reports M-Pesa, not the business. A shop that also takes cash and card, or that wants to know what it sold rather than what it received, is reading a third of its own numbers.

### Leaving administrator access with a departed employee

Payment administration can change where money goes. Reviewing who holds it should happen when anybody leaves, not when something goes wrong.

### Never comparing the portal against your own sales record

One source cannot be reconciled. The whole point of having an independent sales record is that two figures can be compared and a difference can be explained.

### Assuming a POS can read the portal for you

Be sceptical of any vendor implying their software simply reads your Safaricom merchant data. Ask exactly what is connected, how, and what the business has to authorise — and ask to see it on live data.

### Not keeping statements

The portal is where the record lives today. Your accountant, a lender or an audit will ask for a period you no longer have open, and reconstructing it under time pressure is the expensive way to learn this.

## A worked example: the Tuesday that did not match

A hardware shop in Nairobi took around KES 200,000 a day, most of it M-Pesa. The owner checked the merchant portal every evening, saw a plausible number, and considered the day closed. There was no second figure to compare it against, because the shop recorded sales in a notebook that was totalled weekly.

The gap surfaced only when the shop started recording sales properly at the counter. On the first Tuesday of comparison, collections were about KES 14,000 below the day&#x27;s recorded sales. The cause turned out to be mundane and expensive: a contractor had taken delivery of materials against a promised payment that never arrived, and nobody had flagged it because there was no routine in which an unmatched sale could surface.

Nothing about the portal had been wrong. It had reported exactly what reached the business. What the shop had been missing was the other number — and without two numbers, a KES 14,000 hole looks identical to a normal day.

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 is for, next to the Hub

The boundary first, because it matters: M-Pesa Business Hub is Safaricom&#x27;s product. Veira does not provide it, does not operate M-Pesa, has no official Safaricom partnership to claim, and is not the place to establish your eligibility, tariffs or limits. Safaricom is.

Veira is the independent record on the other side of the comparison. It holds the sale: what was sold, at what price, by which cashier, in which branch, paid by cash, card or M-Pesa, with a compliant KRA [eTIMS](https://veirahq.com/blog/what-is-etims) invoice issued at the time. It reports by day, channel, cashier and branch, and it keeps the audit trail — voids, discounts, refunds and who approved them.

That is what makes a merchant portal reconcilable. The Hub tells you what came in; Veira tells you what you sold. Where those disagree is the most useful number a Kenyan retailer has, and you cannot produce it from one source.

## Frequently asked questions

A merchant portal tells you what reached your business. It cannot tell you what your business did — that needs a record of your own, and the gap between the two is where the money goes missing. [Book a demo](https://veirahq.com/book) and bring one week of statements.

## 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.
