What Features Should an ISP Billing System Have for the Kenyan Market?

A platform built for Europe or the US and lightly localized isn't the same as one built for Kenya from the ground up. Here's what actually matters — and where "billing system" as a category quietly stops short of what a Kenyan ISP owner actually needs day to day.

M-Pesa as a first-class citizen. Paybill and Till, STK Push, automatic reconciliation — core, not a plugin.

MikroTik-native router management. Connecting a new router shouldn't need a technician driving out with a laptop.

Both PPPoE and hotspot billing in one platform, since many Kenyan ISPs run a hybrid model.

SMS notifications, because email is a poor channel for most residential and hotspot customers in Kenya.

Reseller/agent support, modeled on the wakala structure Kenyans already trust from mobile money.

Mobile-first design, since technicians, agents, and owners check the dashboard from a phone far more often than a desk.

And here's the part most "billing system" reviews skip entirely: running an ISP isn't only about money moving in and access turning on or off. It's also technicians driving to a customer's home to install a router, equipment that needs tracking so it doesn't walk off, complaints that need logging and resolving, and — as you grow — routers across multiple sites that need real-time monitoring so you know about an outage before a customer calls to complain. A tool that only does billing leaves every one of those jobs to a separate app, a paper logbook, or a WhatsApp group.

This is precisely why Beam is built as an ISP management platform with billing as one module, not a billing tool with a few extras bolted on — customer management, plans, MikroTik control, M-Pesa, hotspot vouchers, support tickets, field jobs, inventory, resellers, network monitoring, staff roles, and reporting, all in one dashboard. See the extended list in 10 Must-Have Features in ISP Billing Platforms Used in Kenya, or sign up and try Beam free to see the full list in action.