There is no single best ISP billing software for every provider. The right one fits your network, your subscriber numbers, the services you sell and the way your customers pay, and it removes the manual work your team does today. A wireless ISP with a few hundred subscribers on MikroTik needs something different from a fiber operator with tens of thousands across several towns.
This guide is about choosing: the questions to answer before you look at vendors, the features to test, the costs to compare, and how to trial and switch without disconnecting anyone. If you want to see what a complete system looks like while you read, Centipid Billing is our ISP billing software.
What ISP billing software has to do
Generic invoicing tools produce invoices. ISP billing software is built around a recurring connection, so it ties what a customer pays for to what that customer can use on the network.
Most systems handle the same core jobs:
- Subscriber management: one record per customer, with contacts, package, balance, service history and the access state the network reads.
- Packages and pricing: plans defined by speed, data allowance, duration and price.
- Recurring invoicing: invoices raised on the customer's cycle, with credit notes for corrections.
- Payment collection: mobile money, card, bank and cash payments, each matched to the subscriber and the invoice it settles.
- Network integration: billing status passed to the network, usually through RADIUS or the router's API, so access is opened, limited or suspended without a technician.
- Reporting: revenue, collections, overdue accounts and subscriber growth.
When these work together, nobody has to check payment messages by hand and then log in to a router to switch a customer on or off. That loop, from payment to access, is the main thing you are buying.
Answer five questions before you compare
Asking which ISP billing software is best is like asking which vehicle is best. Answer these about your own operation first, and the shortlist gets short quickly.
How many subscribers do you have, and how fast are you growing? A system that suits 300 subscribers may slow down or become expensive at 30,000. Check that the pricing and the performance scale with your plans, not only your current size.
What network equipment do you run? Many ISPs run MikroTik, Ubiquiti, Cambium, Cisco, Huawei or a mix. Your billing system should work with the equipment you own. Replacing your network to suit your billing software is rarely sensible.
What do you sell? Some providers sell only monthly broadband. Others also sell Hotspot access, prepaid vouchers or dedicated business links. Check that the system can model every product you offer, and that one customer can hold more than one.
How do your customers pay? Payment habits vary by country. In some markets cards and direct debit dominate. In much of Africa and South Asia, mobile money, bank deposits and cash through agents are standard. A system that cannot take your customers' usual channel will cost you late payments and manual reconciliation.
What do your tax and compliance rules require? Invoices may need tax fields, sequential numbering or a local currency format. Data protection rules may affect where customer data is stored.
Spreadsheets, generic billing tools and ISP billing software
Most ISPs move through three stages. Each has its place, but only the last connects the money to the network.
| Spreadsheet | Generic subscription billing | ISP billing software | |
|---|---|---|---|
| Invoicing | By hand, one customer at a time | Automatic on a cycle | Automatic on a cycle, from the subscriber's package |
| Payment matching | Checked against statements or payment messages by hand | Cards and bank transfers, mobile money often missing | Local gateways and mobile money, matched to the account |
| Network access | A technician logs in to the router | A technician logs in to the router | Follows the account automatically |
| Growth | Work grows with every subscriber | Billing scales, network work does not | Both scale together |
A spreadsheet works for a handful of customers. Generic subscription software handles billing cycles well but cannot enforce them: it can send the invoice, not cut off the customer who ignores it. If you are reading this guide, you are probably at the point where that gap costs you money every month.
The features to test
Once you know what you need, compare every candidate against the same list.
The billing cycle runs itself
The main value of ISP billing software is removing manual work. Check that it can:
- raise invoices on schedule from each subscriber's package and billing date;
- send reminders before and after expiry by SMS, WhatsApp or email;
- apply your grace period, then suspend access when an account expires;
- restore access as soon as a payment is confirmed, at any hour.
Automatic suspension and reconnection matter most. Chasing unpaid accounts by hand takes staff time, and every forgotten disconnect is a customer online without paying.
The network follows the bill
Ask exactly how the system talks to your network. The common approaches are RADIUS authentication and accounting, API integration with specific router brands, or both. Find out whether speed profiles, data allowances and fair use limits update as soon as a customer changes package.
Be wary of a vendor who only says "MikroTik integration". The phrase can mean anything. Ask to see PPPoE and Hotspot users created, a speed change reaching the router, and an expired account losing access, all without anyone touching the router.
Payments match themselves
List the payment methods your customers actually use and confirm each one is supported, natively or through a reliable integration. Then check what happens after the money arrives:
- Is the payment matched to the right subscriber and invoice automatically?
- Is the subscriber's access renewed in the same step?
- Where does a payment go when the system cannot match it, and who claims it?
Without automatic matching, staff end up reconciling statements line by line, and customers who paid at night wait until morning to get back online.
Customers can serve themselves
A portal where subscribers see their balance, invoices and receipts, pay, and renew cuts calls and walk-in visits. Most will only ever open it on a phone, so test it on one.
Reports come off the ledger
Good reporting shows which packages earn money, where customers are leaving and how much is overdue. Look for reports you can filter by period, branch and package, and data you can export for your accountant.
Staff, branches and security
If you run several towns or work with resellers, confirm that branches, permissions and reporting work without workarounds. Staff should see and change only what their role needs, and every important change should leave a record of who made it.
Hosted or self-hosted
ISP billing systems come as hosted software or as software you install on your own servers.
- Hosted systems need no server work, include updates and work from anywhere, but you depend on the vendor's uptime and pay an ongoing fee.
- Self-hosted systems give you more control over data and customization, but your team takes on servers, backups, security patches and upgrades.
Neither is better in every case. Choose by your team's technical capacity and how much control you need.
Compare the full cost
The subscription or licence price is only part of what you will pay. When comparing, add up:
- Pricing model: per subscriber, per revenue, flat fee or one-time licence.
- Setup and migration: importing subscribers, packages and balances.
- Payment fees: charged by the gateway, sometimes with a margin added by the billing vendor.
- SMS and WhatsApp: reminders and confirmations cost money per message.
- Support: included or charged separately, and in which time zones.
- Staff time: a cheaper system that leaves more manual work can cost more overall.
A useful exercise: count the hours your team spends each month on invoicing, payment matching and disconnections, then ask how many of those hours each system removes.
A checklist for vendor calls
Take these questions into every demo, and ask the vendor to show the answer rather than describe it.
| What to check | Why it matters | Ask the vendor |
|---|---|---|
| Router integration | Without it, your team still does access by hand. | "Show a PPPoE user created, slowed and suspended on my router model, with no one logging in to it." |
| Payment gateways | Your customers' usual channel decides how fast you get paid. | "Which gateways do you support in my country, and is matching each payment to its invoice automatic?" |
| Self-service | A portal takes routine questions off your support line. | "Can a subscriber see their balance, pay and renew from a phone without calling us?" |
| Reporting | You need to see revenue, collections and growth without a spreadsheet. | "Show me last month's collections by package and by branch." |
| Scale | The system has to hold up as you grow. | "How does the price and the system behave at ten times my subscribers?" |
| Support | Billing problems cut revenue and customers' access. | "What are your support channels and hours, and who helps with the first router?" |
| Pricing | Hidden fees break budgets. | "Give me every cost: setup, monthly, per subscriber, per router and per payment." |
Test it on your own network
Brochures and demos show the ideal case. The best way to know whether ISP billing software fits is to run it against your own routers and your own edge cases. A trial or a test account is enough:
- Connect one live router, or a test router, to the system.
- Create two or three of your real packages and a few test subscribers.
- Run a real payment through your most common channel, including mobile money if your customers use it.
- Let an account expire and confirm access stops. Pay it and confirm access comes back.
- Try your awkward cases: a package change mid-cycle, a partial payment and a payment that cannot be matched.
If the vendor offers no trial, ask for a demo built on those scenarios rather than their script.
Plan the switch
Moving billing systems sounds risky, but most of the risk is in the data, and most of the work happens before go-live.
Clean the data first. Export your subscribers and check every record before importing:
- names and addresses in one format, so no one becomes two accounts;
- phone numbers and emails that work, because reminders and confirmations depend on them;
- every subscriber on a current package, with the right price and billing date;
- balances you have reconciled and trust.
Configure before you import. Recreate your packages with their speeds and prices, connect your payment gateways, and connect your routers.
Pilot, then move in batches. Move staff accounts or a few friendly customers first, and watch a full cycle: invoice, reminder, payment, renewal, expiry. Then move the rest in batches, so any problem touches a small group. Running the old and new systems side by side for one billing cycle is a sensible check before you switch off the old one.
Mistakes to avoid
- Choosing on price alone. The cheapest option is expensive if it leaves the manual work in place.
- Ignoring how customers pay. A system without your customers' payment channel will hurt collections.
- Underestimating migration. Bad balances and wrong packages turn into billing errors and complaints.
- Overbuying. Enterprise platforms with features you will never use add cost and complexity.
- Skipping your own tests. Demos show the happy path. Your edge cases decide whether it works.
Where Centipid fits
Centipid Billing is hosted ISP billing software for ISPs that sell PPPoE, Hotspot and voucher access on MikroTik routers. All three share one subscriber record. Centipid runs RADIUS for your routers, so the router's answer comes from the account's current state: a payment confirmed by mobile money, card or voucher is matched to the subscriber and renews their access, and an expired account loses it under your suspension policy.
Apply the same criteria from this guide to us: check that it works with your routers, confirm your country's gateways on the countries page, see what it costs on the pricing page, and test your own scenarios before you commit.
Frequently asked questions
Which is the best ISP billing software?
No single system is best for everyone. The best choice works with your network equipment, takes your customers' payment methods, automates invoicing, suspension and reconnection, meets your local tax rules and scales with your growth.
What is the difference between ISP billing software and invoicing software?
Invoicing software creates and sends invoices. ISP billing software also manages packages and renewal cycles, matches payments to subscribers, and connects to the network so access is opened, limited or suspended by account status.
Do I need RADIUS?
Many ISPs use RADIUS to authenticate PPPoE and Hotspot users and apply their package. If your network relies on it, your billing system should run RADIUS or work with your RADIUS server. Some systems talk to router APIs instead.
How long does it take to switch ISP billing systems?
It depends on how many subscribers you have, how clean your data is and how many packages you run. Allow time to clean the data, run a pilot and watch one full billing cycle before moving everyone.
Can a small ISP benefit from billing software?
Yes. Even a small provider saves hours when invoicing, reminders, payment matching and disconnections run themselves, and starting on a system that scales avoids a harder migration later.
